It's easy to steer your DMRGateway via DTMF or CLI or AllMon or AndroidIAX. Consider the following snip from ambe_audio.cfg section = BM # Use BM section values # order of precedence: dmrlink.cfg, section=, DEFAULTS [BM] # Listen to all, TX on TG3100 TS1 tgFilter = 3100,3106,31094 # A list of TG IDs to monitor. All TGs will be passed to DMRGateway txTg = 3100 # TG to use for all frames received from DMRGateway -> IPSC txTs = 2 # Slot to use for frames received from DMRGateway -> IPSC [BM3100] # Brandmeister tgFilter = 3100 # USA Nationwide txTg = 3100 txTs = 1 [BM3106] # Brandmeister tgFilter = 3106 # California Statewide txTg = 3106 txTs = 2 [BM31094] # Brandmeister tgFilter = 31094 # US call area 4 txTg = 31094 txTs = 1 [Sandbox] # Sandbox network tgFilter = 3120 txTg = 3120 txTs = 2 [LOCAL] # Local network tgFilter = 3 txTg = 3 txTs = 2 [Shutup] # Be quiet tgFilter = 0 txTg = 0 txTs = 2 /etc/asterisk/rpt.conf ; DMRGateway Commands 73 = cmd,/bin/bash -c 'echo -n "section=Shutup" | nc 127.0.0.1 31002' 74 = cmd,/bin/bash -c 'echo -n "section=BM" | nc 127.0.0.1 31002' 76 = cmd,/bin/bash -c 'echo -n "section=DMR-MARC" | nc 127.0.0.1 31002' 77 = cmd,/bin/bash -c 'echo -n "section=BM3100" | nc 127.0.0.1 31002' 78 = cmd,/bin/bash -c 'echo -n "section=BM3106" | nc 127.0.0.1 31002' 79 = cmd,/bin/bash -c 'echo -n "section=BM31094" | nc 127.0.0.1 31002' Issue a *73 from a radio (simplified for example) and ambe_audio will use the section [Shutup] Issue a *77 from a radio (simplified for example) and ambe_audio will use the section [BM3100] Replace radio with CLI or AllMon or AndroidIAX. Add a script to cron ... Available remote control commands: 'reread_subscribers' 'reread_config' 'txTg' 'txTs' 'section' 'gateway_dmr_id' 'gateway_peer_id' 'restart' 'playbackFromFile' 'tgs' 'dump_template' 'get_info' See: <https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayDiagram.pdf> <https://github.com/N4IRS/DMRGateway/blob/master/DMRGateway.rtf> <https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayTechOverview.pdf> For INAD, 73 Steve N4IRS -- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
I get it kind of... I'm still a little confused. I currently have the named section defined as. I use TG 42657 as my ID to access ASL. [AMBE_PEER] gatewaydmrId = 312307 tgFilter = 42657 txTg = 42657 txTs = 2 I put this right above what was already in the file so the next section is [BM] tgFilter = 3100, 31094 txTg = 3100 txTx = 2 So am I to assume that in my /opt/dmrlink/ambe_audio/dmrlink.cfg that I should ass a section for BM with the relevant connection information? currently the only thing enabled is AMBE_PEER. Will this be an issue since I already have a connection to Brandmeister already defined in /opt/dmrlink/bridge/dmrlink/cfg Thank you. On Wed, May 11, 2016 at 12:49 PM, Steve Zingman <szingman@msgstor.com> wrote:
It's easy to steer your DMRGateway via DTMF or CLI or AllMon or AndroidIAX. Consider the following snip from ambe_audio.cfg
section = BM # Use BM section values
# order of precedence: dmrlink.cfg, section=, DEFAULTS
[BM] # Listen to all, TX on TG3100 TS1 tgFilter = 3100,3106,31094 # A list of TG IDs to monitor. All TGs will be passed to DMRGateway txTg = 3100 # TG to use for all frames received from DMRGateway -> IPSC txTs = 2 # Slot to use for frames received from DMRGateway -> IPSC
[BM3100] # Brandmeister tgFilter = 3100 # USA Nationwide txTg = 3100 txTs = 1
[BM3106] # Brandmeister tgFilter = 3106 # California Statewide txTg = 3106 txTs = 2
[BM31094] # Brandmeister tgFilter = 31094 # US call area 4 txTg = 31094 txTs = 1
[Sandbox] # Sandbox network tgFilter = 3120 txTg = 3120 txTs = 2
[LOCAL] # Local network tgFilter = 3 txTg = 3 txTs = 2
[Shutup] # Be quiet tgFilter = 0 txTg = 0 txTs = 2
/etc/asterisk/rpt.conf
; DMRGateway Commands
73 = cmd,/bin/bash -c 'echo -n "section=Shutup" | nc 127.0.0.1 31002' 74 = cmd,/bin/bash -c 'echo -n "section=BM" | nc 127.0.0.1 31002' 76 = cmd,/bin/bash -c 'echo -n "section=DMR-MARC" | nc 127.0.0.1 31002' 77 = cmd,/bin/bash -c 'echo -n "section=BM3100" | nc 127.0.0.1 31002' 78 = cmd,/bin/bash -c 'echo -n "section=BM3106" | nc 127.0.0.1 31002' 79 = cmd,/bin/bash -c 'echo -n "section=BM31094" | nc 127.0.0.1 31002'
Issue a *73 from a radio (simplified for example) and ambe_audio will use the section [Shutup] Issue a *77 from a radio (simplified for example) and ambe_audio will use the section [BM3100] Replace radio with CLI or AllMon or AndroidIAX. Add a script to cron ...
Available remote control commands: 'reread_subscribers' 'reread_config' 'txTg' 'txTs' 'section' 'gateway_dmr_id' 'gateway_peer_id' 'restart' 'playbackFromFile' 'tgs' 'dump_template' 'get_info'
See: <https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayDiagram.pdf> <https://github.com/N4IRS/DMRGateway/blob/master/DMRGateway.rtf> < https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayTechOverview.pdf
For INAD, 73 Steve N4IRS
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
The names I posted are only a example. use anything you want. On 5/11/2016 1:59 PM, Robert Newberry wrote:
I get it kind of... I'm still a little confused.
I currently have the named section defined as. I use TG 42657 as my ID to access ASL.
[AMBE_PEER] gatewaydmrId = 312307 tgFilter = 42657 txTg = 42657 txTs = 2
I put this right above what was already in the file so the next section is
[BM] tgFilter = 3100, 31094 txTg = 3100 txTx = 2
So am I to assume that in my /opt/dmrlink/ambe_audio/dmrlink.cfg
that I should ass a section for BM with the relevant connection information? currently the only thing enabled is AMBE_PEER.
Will this be an issue since I already have a connection to Brandmeister already defined in /opt/dmrlink/bridge/dmrlink/cfg
Thank you.
On Wed, May 11, 2016 at 12:49 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
It's easy to steer your DMRGateway via DTMF or CLI or AllMon or AndroidIAX. Consider the following snip from ambe_audio.cfg
section = BM # Use BM section values
# order of precedence: dmrlink.cfg, section=, DEFAULTS
[BM] # Listen to all, TX on TG3100 TS1 tgFilter = 3100,3106,31094 # A list of TG IDs to monitor. All TGs will be passed to DMRGateway txTg = 3100 # TG to use for all frames received from DMRGateway -> IPSC txTs = 2 # Slot to use for frames received from DMRGateway -> IPSC
[BM3100] # Brandmeister tgFilter = 3100 # USA Nationwide txTg = 3100 txTs = 1
[BM3106] # Brandmeister tgFilter = 3106 # California Statewide txTg = 3106 txTs = 2
[BM31094] # Brandmeister tgFilter = 31094 # US call area 4 txTg = 31094 txTs = 1
[Sandbox] # Sandbox network tgFilter = 3120 txTg = 3120 txTs = 2
[LOCAL] # Local network tgFilter = 3 txTg = 3 txTs = 2
[Shutup] # Be quiet tgFilter = 0 txTg = 0 txTs = 2
/etc/asterisk/rpt.conf
; DMRGateway Commands
73 = cmd,/bin/bash -c 'echo -n "section=Shutup" | nc 127.0.0.1 31002' 74 = cmd,/bin/bash -c 'echo -n "section=BM" | nc 127.0.0.1 31002' 76 = cmd,/bin/bash -c 'echo -n "section=DMR-MARC" | nc 127.0.0.1 31002' 77 = cmd,/bin/bash -c 'echo -n "section=BM3100" | nc 127.0.0.1 31002' 78 = cmd,/bin/bash -c 'echo -n "section=BM3106" | nc 127.0.0.1 31002' 79 = cmd,/bin/bash -c 'echo -n "section=BM31094" | nc 127.0.0.1 31002'
Issue a *73 from a radio (simplified for example) and ambe_audio will use the section [Shutup] Issue a *77 from a radio (simplified for example) and ambe_audio will use the section [BM3100] Replace radio with CLI or AllMon or AndroidIAX. Add a script to cron ...
Available remote control commands: 'reread_subscribers' 'reread_config' 'txTg' 'txTs' 'section' 'gateway_dmr_id' 'gateway_peer_id' 'restart' 'playbackFromFile' 'tgs' 'dump_template' 'get_info'
See: <https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayDiagram.pdf> <https://github.com/N4IRS/DMRGateway/blob/master/DMRGateway.rtf> <https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayTechOverview.pdf>
For INAD, 73 Steve N4IRS
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
I figured the names were arbitrary. I was mostly wondering if I was going to have a conflict having a brandmeister connection defined in /opt/dmrlink/bridge/drmlink.cfg and /opt/dmrlink/ambe_audio/dmrlink.cfg On Wed, May 11, 2016 at 2:21 PM, Steve Zingman <szingman@msgstor.com> wrote:
The names I posted are only a example. use anything you want.
On 5/11/2016 1:59 PM, Robert Newberry wrote:
I get it kind of... I'm still a little confused.
I currently have the named section defined as. I use TG 42657 as my ID to access ASL.
[AMBE_PEER] gatewaydmrId = 312307 tgFilter = 42657 txTg = 42657 txTs = 2
I put this right above what was already in the file so the next section is
[BM] tgFilter = 3100, 31094 txTg = 3100 txTx = 2
So am I to assume that in my /opt/dmrlink/ambe_audio/dmrlink.cfg
that I should ass a section for BM with the relevant connection information? currently the only thing enabled is AMBE_PEER.
Will this be an issue since I already have a connection to Brandmeister already defined in /opt/dmrlink/bridge/dmrlink/cfg
Thank you.
On Wed, May 11, 2016 at 12:49 PM, Steve Zingman <szingman@msgstor.com> wrote:
It's easy to steer your DMRGateway via DTMF or CLI or AllMon or AndroidIAX. Consider the following snip from ambe_audio.cfg
section = BM # Use BM section values
# order of precedence: dmrlink.cfg, section=, DEFAULTS
[BM] # Listen to all, TX on TG3100 TS1 tgFilter = 3100,3106,31094 # A list of TG IDs to monitor. All TGs will be passed to DMRGateway txTg = 3100 # TG to use for all frames received from DMRGateway -> IPSC txTs = 2 # Slot to use for frames received from DMRGateway -> IPSC
[BM3100] # Brandmeister tgFilter = 3100 # USA Nationwide txTg = 3100 txTs = 1
[BM3106] # Brandmeister tgFilter = 3106 # California Statewide txTg = 3106 txTs = 2
[BM31094] # Brandmeister tgFilter = 31094 # US call area 4 txTg = 31094 txTs = 1
[Sandbox] # Sandbox network tgFilter = 3120 txTg = 3120 txTs = 2
[LOCAL] # Local network tgFilter = 3 txTg = 3 txTs = 2
[Shutup] # Be quiet tgFilter = 0 txTg = 0 txTs = 2
/etc/asterisk/rpt.conf
; DMRGateway Commands
73 = cmd,/bin/bash -c 'echo -n "section=Shutup" | nc 127.0.0.1 31002' 74 = cmd,/bin/bash -c 'echo -n "section=BM" | nc 127.0.0.1 31002' 76 = cmd,/bin/bash -c 'echo -n "section=DMR-MARC" | nc 127.0.0.1 31002' 77 = cmd,/bin/bash -c 'echo -n "section=BM3100" | nc 127.0.0.1 31002' 78 = cmd,/bin/bash -c 'echo -n "section=BM3106" | nc 127.0.0.1 31002' 79 = cmd,/bin/bash -c 'echo -n "section=BM31094" | nc 127.0.0.1 31002'
Issue a *73 from a radio (simplified for example) and ambe_audio will use the section [Shutup] Issue a *77 from a radio (simplified for example) and ambe_audio will use the section [BM3100] Replace radio with CLI or AllMon or AndroidIAX. Add a script to cron ...
Available remote control commands: 'reread_subscribers' 'reread_config' 'txTg' 'txTs' 'section' 'gateway_dmr_id' 'gateway_peer_id' 'restart' 'playbackFromFile' 'tgs' 'dump_template' 'get_info'
See: <https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayDiagram.pdf> <https://github.com/N4IRS/DMRGateway/blob/master/DMRGateway.rtf> < https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayTechOverview.pdf
For INAD, 73 Steve N4IRS
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
The two dmrlink files are totally separate. One controls your bridge rules and the other controls ambe_audio. The ambe_audio version should only enable the network you want ambe_audio to connect to. So, if you have a [FOO] section in ambe_audio/dmrlink.cfg, you should also have one in ambe_audio.cfg On Wed, May 11, 2016 at 2:40 PM, Robert Newberry <N1XBM@amsat.org> wrote:
I figured the names were arbitrary. I was mostly wondering if I was going to have a conflict having a brandmeister connection defined in /opt/dmrlink/bridge/drmlink.cfg and /opt/dmrlink/ambe_audio/dmrlink.cfg
On Wed, May 11, 2016 at 2:21 PM, Steve Zingman <szingman@msgstor.com> wrote:
The names I posted are only a example. use anything you want.
On 5/11/2016 1:59 PM, Robert Newberry wrote:
I get it kind of... I'm still a little confused.
I currently have the named section defined as. I use TG 42657 as my ID to access ASL.
[AMBE_PEER] gatewaydmrId = 312307 tgFilter = 42657 txTg = 42657 txTs = 2
I put this right above what was already in the file so the next section is
[BM] tgFilter = 3100, 31094 txTg = 3100 txTx = 2
So am I to assume that in my /opt/dmrlink/ambe_audio/dmrlink.cfg
that I should ass a section for BM with the relevant connection information? currently the only thing enabled is AMBE_PEER.
Will this be an issue since I already have a connection to Brandmeister already defined in /opt/dmrlink/bridge/dmrlink/cfg
Thank you.
On Wed, May 11, 2016 at 12:49 PM, Steve Zingman <szingman@msgstor.com> wrote:
It's easy to steer your DMRGateway via DTMF or CLI or AllMon or AndroidIAX. Consider the following snip from ambe_audio.cfg
section = BM # Use BM section values
# order of precedence: dmrlink.cfg, section=, DEFAULTS
[BM] # Listen to all, TX on TG3100 TS1 tgFilter = 3100,3106,31094 # A list of TG IDs to monitor. All TGs will be passed to DMRGateway txTg = 3100 # TG to use for all frames received from DMRGateway -> IPSC txTs = 2 # Slot to use for frames received from DMRGateway -> IPSC
[BM3100] # Brandmeister tgFilter = 3100 # USA Nationwide txTg = 3100 txTs = 1
[BM3106] # Brandmeister tgFilter = 3106 # California Statewide txTg = 3106 txTs = 2
[BM31094] # Brandmeister tgFilter = 31094 # US call area 4 txTg = 31094 txTs = 1
[Sandbox] # Sandbox network tgFilter = 3120 txTg = 3120 txTs = 2
[LOCAL] # Local network tgFilter = 3 txTg = 3 txTs = 2
[Shutup] # Be quiet tgFilter = 0 txTg = 0 txTs = 2
/etc/asterisk/rpt.conf
; DMRGateway Commands
73 = cmd,/bin/bash -c 'echo -n "section=Shutup" | nc 127.0.0.1 31002' 74 = cmd,/bin/bash -c 'echo -n "section=BM" | nc 127.0.0.1 31002' 76 = cmd,/bin/bash -c 'echo -n "section=DMR-MARC" | nc 127.0.0.1 31002' 77 = cmd,/bin/bash -c 'echo -n "section=BM3100" | nc 127.0.0.1 31002' 78 = cmd,/bin/bash -c 'echo -n "section=BM3106" | nc 127.0.0.1 31002' 79 = cmd,/bin/bash -c 'echo -n "section=BM31094" | nc 127.0.0.1 31002'
Issue a *73 from a radio (simplified for example) and ambe_audio will use the section [Shutup] Issue a *77 from a radio (simplified for example) and ambe_audio will use the section [BM3100] Replace radio with CLI or AllMon or AndroidIAX. Add a script to cron ...
Available remote control commands: 'reread_subscribers' 'reread_config' 'txTg' 'txTs' 'section' 'gateway_dmr_id' 'gateway_peer_id' 'restart' 'playbackFromFile' 'tgs' 'dump_template' 'get_info'
See: <https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayDiagram.pdf> <https://github.com/N4IRS/DMRGateway/blob/master/DMRGateway.rtf> < https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayTechOverview.pdf
For INAD, 73 Steve N4IRS
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
If you have a active network in /opt/dmrlink/ambe_audio/dmrlink.cfg named [LSMFT] and a section named [LSMFT] in ambe_audio.cfg without a section= in the default ambe_audio.py will use the section [LSMFT] in ambe_audio.cfg If you then add a section [yoursectionhere] with different gatewaydmrId, TgFilter, txTg, txTs those new values will be selected if you issue a echo -n "section=yoursectionhere" | nc 127.0.0.1 31002 from the Linux shell prompt. On 5/11/2016 2:40 PM, Robert Newberry wrote:
I figured the names were arbitrary. I was mostly wondering if I was going to have a conflict having a brandmeister connection defined in /opt/dmrlink/bridge/drmlink.cfg and /opt/dmrlink/ambe_audio/dmrlink.cfg
On Wed, May 11, 2016 at 2:21 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
The names I posted are only a example. use anything you want.
On 5/11/2016 1:59 PM, Robert Newberry wrote:
I get it kind of... I'm still a little confused.
I currently have the named section defined as. I use TG 42657 as my ID to access ASL.
[AMBE_PEER] gatewaydmrId = 312307 tgFilter = 42657 txTg = 42657 txTs = 2
I put this right above what was already in the file so the next section is
[BM] tgFilter = 3100, 31094 txTg = 3100 txTx = 2
So am I to assume that in my /opt/dmrlink/ambe_audio/dmrlink.cfg
that I should ass a section for BM with the relevant connection information? currently the only thing enabled is AMBE_PEER.
Will this be an issue since I already have a connection to Brandmeister already defined in /opt/dmrlink/bridge/dmrlink/cfg
Thank you.
On Wed, May 11, 2016 at 12:49 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
It's easy to steer your DMRGateway via DTMF or CLI or AllMon or AndroidIAX. Consider the following snip from ambe_audio.cfg
section = BM # Use BM section values
# order of precedence: dmrlink.cfg, section=, DEFAULTS
[BM] # Listen to all, TX on TG3100 TS1 tgFilter = 3100,3106,31094 # A list of TG IDs to monitor. All TGs will be passed to DMRGateway txTg = 3100 # TG to use for all frames received from DMRGateway -> IPSC txTs = 2 # Slot to use for frames received from DMRGateway -> IPSC
[BM3100] # Brandmeister tgFilter = 3100 # USA Nationwide txTg = 3100 txTs = 1
[BM3106] # Brandmeister tgFilter = 3106 # California Statewide txTg = 3106 txTs = 2
[BM31094] # Brandmeister tgFilter = 31094 # US call area 4 txTg = 31094 txTs = 1
[Sandbox] # Sandbox network tgFilter = 3120 txTg = 3120 txTs = 2
[LOCAL] # Local network tgFilter = 3 txTg = 3 txTs = 2
[Shutup] # Be quiet tgFilter = 0 txTg = 0 txTs = 2
/etc/asterisk/rpt.conf
; DMRGateway Commands
73 = cmd,/bin/bash -c 'echo -n "section=Shutup" | nc 127.0.0.1 31002' 74 = cmd,/bin/bash -c 'echo -n "section=BM" | nc 127.0.0.1 31002' 76 = cmd,/bin/bash -c 'echo -n "section=DMR-MARC" | nc 127.0.0.1 31002' 77 = cmd,/bin/bash -c 'echo -n "section=BM3100" | nc 127.0.0.1 31002' 78 = cmd,/bin/bash -c 'echo -n "section=BM3106" | nc 127.0.0.1 31002' 79 = cmd,/bin/bash -c 'echo -n "section=BM31094" | nc 127.0.0.1 31002'
Issue a *73 from a radio (simplified for example) and ambe_audio will use the section [Shutup] Issue a *77 from a radio (simplified for example) and ambe_audio will use the section [BM3100] Replace radio with CLI or AllMon or AndroidIAX. Add a script to cron ...
Available remote control commands: 'reread_subscribers' 'reread_config' 'txTg' 'txTs' 'section' 'gateway_dmr_id' 'gateway_peer_id' 'restart' 'playbackFromFile' 'tgs' 'dump_template' 'get_info'
See: <https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayDiagram.pdf> <https://github.com/N4IRS/DMRGateway/blob/master/DMRGateway.rtf> <https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayTechOverview.pdf>
For INAD, 73 Steve N4IRS
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
Ya I suppose I better save copies of everything and try it. This would be the perfect ticket at home, I had a bunch of Motorola local remotes. I ended up connecting them directily to the USB FOB and made a "home radioless node" They sound superb on the air, I could monitor other DMR TG's besides my ASL ID. On Wed, May 11, 2016 at 2:48 PM, Steve Zingman <szingman@msgstor.com> wrote:
If you have a active network in /opt/dmrlink/ambe_audio/dmrlink.cfg named [LSMFT] and a section named [LSMFT] in ambe_audio.cfg without a section= in the default ambe_audio.py will use the section [LSMFT] in ambe_audio.cfg If you then add a section [yoursectionhere] with different gatewaydmrId, TgFilter, txTg, txTs those new values will be selected if you issue a echo -n "section=yoursectionhere" | nc 127.0.0.1 31002 from the Linux shell prompt.
On 5/11/2016 2:40 PM, Robert Newberry wrote:
I figured the names were arbitrary. I was mostly wondering if I was going to have a conflict having a brandmeister connection defined in /opt/dmrlink/bridge/drmlink.cfg and /opt/dmrlink/ambe_audio/dmrlink.cfg
On Wed, May 11, 2016 at 2:21 PM, Steve Zingman <szingman@msgstor.com> wrote:
The names I posted are only a example. use anything you want.
On 5/11/2016 1:59 PM, Robert Newberry wrote:
I get it kind of... I'm still a little confused.
I currently have the named section defined as. I use TG 42657 as my ID to access ASL.
[AMBE_PEER] gatewaydmrId = 312307 tgFilter = 42657 txTg = 42657 txTs = 2
I put this right above what was already in the file so the next section is
[BM] tgFilter = 3100, 31094 txTg = 3100 txTx = 2
So am I to assume that in my /opt/dmrlink/ambe_audio/dmrlink.cfg
that I should ass a section for BM with the relevant connection information? currently the only thing enabled is AMBE_PEER.
Will this be an issue since I already have a connection to Brandmeister already defined in /opt/dmrlink/bridge/dmrlink/cfg
Thank you.
On Wed, May 11, 2016 at 12:49 PM, Steve Zingman < <szingman@msgstor.com> szingman@msgstor.com> wrote:
It's easy to steer your DMRGateway via DTMF or CLI or AllMon or AndroidIAX. Consider the following snip from ambe_audio.cfg
section = BM # Use BM section values
# order of precedence: dmrlink.cfg, section=, DEFAULTS
[BM] # Listen to all, TX on TG3100 TS1 tgFilter = 3100,3106,31094 # A list of TG IDs to monitor. All TGs will be passed to DMRGateway txTg = 3100 # TG to use for all frames received from DMRGateway -> IPSC txTs = 2 # Slot to use for frames received from DMRGateway -> IPSC
[BM3100] # Brandmeister tgFilter = 3100 # USA Nationwide txTg = 3100 txTs = 1
[BM3106] # Brandmeister tgFilter = 3106 # California Statewide txTg = 3106 txTs = 2
[BM31094] # Brandmeister tgFilter = 31094 # US call area 4 txTg = 31094 txTs = 1
[Sandbox] # Sandbox network tgFilter = 3120 txTg = 3120 txTs = 2
[LOCAL] # Local network tgFilter = 3 txTg = 3 txTs = 2
[Shutup] # Be quiet tgFilter = 0 txTg = 0 txTs = 2
/etc/asterisk/rpt.conf
; DMRGateway Commands
73 = cmd,/bin/bash -c 'echo -n "section=Shutup" | nc 127.0.0.1 31002' 74 = cmd,/bin/bash -c 'echo -n "section=BM" | nc 127.0.0.1 31002' 76 = cmd,/bin/bash -c 'echo -n "section=DMR-MARC" | nc 127.0.0.1 31002' 77 = cmd,/bin/bash -c 'echo -n "section=BM3100" | nc 127.0.0.1 31002' 78 = cmd,/bin/bash -c 'echo -n "section=BM3106" | nc 127.0.0.1 31002' 79 = cmd,/bin/bash -c 'echo -n "section=BM31094" | nc 127.0.0.1 31002'
Issue a *73 from a radio (simplified for example) and ambe_audio will use the section [Shutup] Issue a *77 from a radio (simplified for example) and ambe_audio will use the section [BM3100] Replace radio with CLI or AllMon or AndroidIAX. Add a script to cron ...
Available remote control commands: 'reread_subscribers' 'reread_config' 'txTg' 'txTs' 'section' 'gateway_dmr_id' 'gateway_peer_id' 'restart' 'playbackFromFile' 'tgs' 'dump_template' 'get_info'
See: <https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayDiagram.pdf> <https://github.com/N4IRS/DMRGateway/blob/master/DMRGateway.rtf> < https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayTechOverview.pdf
For INAD, 73 Steve N4IRS
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
Each dv3000 can only decode one TG at a time. On Wednesday, May 11, 2016, Robert Newberry <N1XBM@amsat.org> wrote:
Ya I suppose I better save copies of everything and try it. This would be the perfect ticket at home, I had a bunch of Motorola local remotes. I ended up connecting them directily to the USB FOB and made a "home radioless node" They sound superb on the air, I could monitor other DMR TG's besides my ASL ID.
On Wed, May 11, 2016 at 2:48 PM, Steve Zingman <szingman@msgstor.com <javascript:_e(%7B%7D,'cvml','szingman@msgstor.com');>> wrote:
If you have a active network in /opt/dmrlink/ambe_audio/dmrlink.cfg named [LSMFT] and a section named [LSMFT] in ambe_audio.cfg without a section= in the default ambe_audio.py will use the section [LSMFT] in ambe_audio.cfg If you then add a section [yoursectionhere] with different gatewaydmrId, TgFilter, txTg, txTs those new values will be selected if you issue a echo -n "section=yoursectionhere" | nc 127.0.0.1 31002 from the Linux shell prompt.
On 5/11/2016 2:40 PM, Robert Newberry wrote:
I figured the names were arbitrary. I was mostly wondering if I was going to have a conflict having a brandmeister connection defined in /opt/dmrlink/bridge/drmlink.cfg and /opt/dmrlink/ambe_audio/dmrlink.cfg
On Wed, May 11, 2016 at 2:21 PM, Steve Zingman <szingman@msgstor.com <javascript:_e(%7B%7D,'cvml','szingman@msgstor.com');>> wrote:
The names I posted are only a example. use anything you want.
On 5/11/2016 1:59 PM, Robert Newberry wrote:
I get it kind of... I'm still a little confused.
I currently have the named section defined as. I use TG 42657 as my ID to access ASL.
[AMBE_PEER] gatewaydmrId = 312307 tgFilter = 42657 txTg = 42657 txTs = 2
I put this right above what was already in the file so the next section is
[BM] tgFilter = 3100, 31094 txTg = 3100 txTx = 2
So am I to assume that in my /opt/dmrlink/ambe_audio/dmrlink.cfg
that I should ass a section for BM with the relevant connection information? currently the only thing enabled is AMBE_PEER.
Will this be an issue since I already have a connection to Brandmeister already defined in /opt/dmrlink/bridge/dmrlink/cfg
Thank you.
On Wed, May 11, 2016 at 12:49 PM, Steve Zingman < <javascript:_e(%7B%7D,'cvml','szingman@msgstor.com');> szingman@msgstor.com <javascript:_e(%7B%7D,'cvml','szingman@msgstor.com');>> wrote:
It's easy to steer your DMRGateway via DTMF or CLI or AllMon or AndroidIAX. Consider the following snip from ambe_audio.cfg
section = BM # Use BM section values
# order of precedence: dmrlink.cfg, section=, DEFAULTS
[BM] # Listen to all, TX on TG3100 TS1 tgFilter = 3100,3106,31094 # A list of TG IDs to monitor. All TGs will be passed to DMRGateway txTg = 3100 # TG to use for all frames received from DMRGateway -> IPSC txTs = 2 # Slot to use for frames received from DMRGateway -> IPSC
[BM3100] # Brandmeister tgFilter = 3100 # USA Nationwide txTg = 3100 txTs = 1
[BM3106] # Brandmeister tgFilter = 3106 # California Statewide txTg = 3106 txTs = 2
[BM31094] # Brandmeister tgFilter = 31094 # US call area 4 txTg = 31094 txTs = 1
[Sandbox] # Sandbox network tgFilter = 3120 txTg = 3120 txTs = 2
[LOCAL] # Local network tgFilter = 3 txTg = 3 txTs = 2
[Shutup] # Be quiet tgFilter = 0 txTg = 0 txTs = 2
/etc/asterisk/rpt.conf
; DMRGateway Commands
73 = cmd,/bin/bash -c 'echo -n "section=Shutup" | nc 127.0.0.1 31002' 74 = cmd,/bin/bash -c 'echo -n "section=BM" | nc 127.0.0.1 31002' 76 = cmd,/bin/bash -c 'echo -n "section=DMR-MARC" | nc 127.0.0.1 31002' 77 = cmd,/bin/bash -c 'echo -n "section=BM3100" | nc 127.0.0.1 31002' 78 = cmd,/bin/bash -c 'echo -n "section=BM3106" | nc 127.0.0.1 31002' 79 = cmd,/bin/bash -c 'echo -n "section=BM31094" | nc 127.0.0.1 31002'
Issue a *73 from a radio (simplified for example) and ambe_audio will use the section [Shutup] Issue a *77 from a radio (simplified for example) and ambe_audio will use the section [BM3100] Replace radio with CLI or AllMon or AndroidIAX. Add a script to cron ...
Available remote control commands: 'reread_subscribers' 'reread_config' 'txTg' 'txTs' 'section' 'gateway_dmr_id' 'gateway_peer_id' 'restart' 'playbackFromFile' 'tgs' 'dump_template' 'get_info'
See: <https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayDiagram.pdf> <https://github.com/N4IRS/DMRGateway/blob/master/DMRGateway.rtf> < https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayTechOverview.pdf
For INAD, 73 Steve N4IRS
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <javascript:_e(%7B%7D,'cvml','Allstar-Digital@lists.keekles.org');> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.org <javascript:_e(%7B%7D,'cvml','Allstar-Digital@lists.keekles.org');>http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <javascript:_e(%7B%7D,'cvml','Allstar-Digital@lists.keekles.org');> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.org <javascript:_e(%7B%7D,'cvml','Allstar-Digital@lists.keekles.org');>http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <javascript:_e(%7B%7D,'cvml','Allstar-Digital@lists.keekles.org');> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
Now, it might be interesting to add the ability to direct a specific TG being decoded to a specific node number. TG3100 <-----> Node 1999 TG3106 <-----> Node 1998 Etc Just thinking out loud Mike On Wednesday, May 11, 2016, Mike Zingman <mike.zingman@gmail.com> wrote:
Each dv3000 can only decode one TG at a time.
On Wednesday, May 11, 2016, Robert Newberry <N1XBM@amsat.org <javascript:_e(%7B%7D,'cvml','N1XBM@amsat.org');>> wrote:
Ya I suppose I better save copies of everything and try it. This would be the perfect ticket at home, I had a bunch of Motorola local remotes. I ended up connecting them directily to the USB FOB and made a "home radioless node" They sound superb on the air, I could monitor other DMR TG's besides my ASL ID.
On Wed, May 11, 2016 at 2:48 PM, Steve Zingman <szingman@msgstor.com> wrote:
If you have a active network in /opt/dmrlink/ambe_audio/dmrlink.cfg named [LSMFT] and a section named [LSMFT] in ambe_audio.cfg without a section= in the default ambe_audio.py will use the section [LSMFT] in ambe_audio.cfg If you then add a section [yoursectionhere] with different gatewaydmrId, TgFilter, txTg, txTs those new values will be selected if you issue a echo -n "section=yoursectionhere" | nc 127.0.0.1 31002 from the Linux shell prompt.
On 5/11/2016 2:40 PM, Robert Newberry wrote:
I figured the names were arbitrary. I was mostly wondering if I was going to have a conflict having a brandmeister connection defined in /opt/dmrlink/bridge/drmlink.cfg and /opt/dmrlink/ambe_audio/dmrlink.cfg
On Wed, May 11, 2016 at 2:21 PM, Steve Zingman <szingman@msgstor.com> wrote:
The names I posted are only a example. use anything you want.
On 5/11/2016 1:59 PM, Robert Newberry wrote:
I get it kind of... I'm still a little confused.
I currently have the named section defined as. I use TG 42657 as my ID to access ASL.
[AMBE_PEER] gatewaydmrId = 312307 tgFilter = 42657 txTg = 42657 txTs = 2
I put this right above what was already in the file so the next section is
[BM] tgFilter = 3100, 31094 txTg = 3100 txTx = 2
So am I to assume that in my /opt/dmrlink/ambe_audio/dmrlink.cfg
that I should ass a section for BM with the relevant connection information? currently the only thing enabled is AMBE_PEER.
Will this be an issue since I already have a connection to Brandmeister already defined in /opt/dmrlink/bridge/dmrlink/cfg
Thank you.
On Wed, May 11, 2016 at 12:49 PM, Steve Zingman <szingman@msgstor.com> wrote:
It's easy to steer your DMRGateway via DTMF or CLI or AllMon or AndroidIAX. Consider the following snip from ambe_audio.cfg
section = BM # Use BM section values
# order of precedence: dmrlink.cfg, section=, DEFAULTS
[BM] # Listen to all, TX on TG3100 TS1 tgFilter = 3100,3106,31094 # A list of TG IDs to monitor. All TGs will be passed to DMRGateway txTg = 3100 # TG to use for all frames received from DMRGateway -> IPSC txTs = 2 # Slot to use for frames received from DMRGateway -> IPSC
[BM3100] # Brandmeister tgFilter = 3100 # USA Nationwide txTg = 3100 txTs = 1
[BM3106] # Brandmeister tgFilter = 3106 # California Statewide txTg = 3106 txTs = 2
[BM31094] # Brandmeister tgFilter = 31094 # US call area 4 txTg = 31094 txTs = 1
[Sandbox] # Sandbox network tgFilter = 3120 txTg = 3120 txTs = 2
[LOCAL] # Local network tgFilter = 3 txTg = 3 txTs = 2
[Shutup] # Be quiet tgFilter = 0 txTg = 0 txTs = 2
/etc/asterisk/rpt.conf
; DMRGateway Commands
73 = cmd,/bin/bash -c 'echo -n "section=Shutup" | nc 127.0.0.1 31002' 74 = cmd,/bin/bash -c 'echo -n "section=BM" | nc 127.0.0.1 31002' 76 = cmd,/bin/bash -c 'echo -n "section=DMR-MARC" | nc 127.0.0.1 31002' 77 = cmd,/bin/bash -c 'echo -n "section=BM3100" | nc 127.0.0.1 31002' 78 = cmd,/bin/bash -c 'echo -n "section=BM3106" | nc 127.0.0.1 31002' 79 = cmd,/bin/bash -c 'echo -n "section=BM31094" | nc 127.0.0.1 31002'
Issue a *73 from a radio (simplified for example) and ambe_audio will use the section [Shutup] Issue a *77 from a radio (simplified for example) and ambe_audio will use the section [BM3100] Replace radio with CLI or AllMon or AndroidIAX. Add a script to cron ...
Available remote control commands: 'reread_subscribers' 'reread_config' 'txTg' 'txTs' 'section' 'gateway_dmr_id' 'gateway_peer_id' 'restart' 'playbackFromFile' 'tgs' 'dump_template' 'get_info'
See: <https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayDiagram.pdf
<https://github.com/N4IRS/DMRGateway/blob/master/DMRGateway.rtf> < https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayTechOverview.pdf
For INAD, 73 Steve N4IRS
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
How about giving them DID's as well (with an access code). On Wed, May 11, 2016 at 1:51 PM, Mike Zingman <mike.zingman@gmail.com> wrote:
Now, it might be interesting to add the ability to direct a specific TG being decoded to a specific node number.
TG3100 <-----> Node 1999 TG3106 <-----> Node 1998 Etc
Just thinking out loud Mike
On Wednesday, May 11, 2016, Mike Zingman <mike.zingman@gmail.com> wrote:
Each dv3000 can only decode one TG at a time.
On Wednesday, May 11, 2016, Robert Newberry <N1XBM@amsat.org> wrote:
Ya I suppose I better save copies of everything and try it. This would be the perfect ticket at home, I had a bunch of Motorola local remotes. I ended up connecting them directily to the USB FOB and made a "home radioless node" They sound superb on the air, I could monitor other DMR TG's besides my ASL ID.
On Wed, May 11, 2016 at 2:48 PM, Steve Zingman <szingman@msgstor.com> wrote:
If you have a active network in /opt/dmrlink/ambe_audio/dmrlink.cfg named [LSMFT] and a section named [LSMFT] in ambe_audio.cfg without a section= in the default ambe_audio.py will use the section [LSMFT] in ambe_audio.cfg If you then add a section [yoursectionhere] with different gatewaydmrId, TgFilter, txTg, txTs those new values will be selected if you issue a echo -n "section=yoursectionhere" | nc 127.0.0.1 31002 from the Linux shell prompt.
On 5/11/2016 2:40 PM, Robert Newberry wrote:
I figured the names were arbitrary. I was mostly wondering if I was going to have a conflict having a brandmeister connection defined in /opt/dmrlink/bridge/drmlink.cfg and /opt/dmrlink/ambe_audio/dmrlink.cfg
On Wed, May 11, 2016 at 2:21 PM, Steve Zingman <szingman@msgstor.com> wrote:
The names I posted are only a example. use anything you want.
On 5/11/2016 1:59 PM, Robert Newberry wrote:
I get it kind of... I'm still a little confused.
I currently have the named section defined as. I use TG 42657 as my ID to access ASL.
[AMBE_PEER] gatewaydmrId = 312307 tgFilter = 42657 txTg = 42657 txTs = 2
I put this right above what was already in the file so the next section is
[BM] tgFilter = 3100, 31094 txTg = 3100 txTx = 2
So am I to assume that in my /opt/dmrlink/ambe_audio/dmrlink.cfg
that I should ass a section for BM with the relevant connection information? currently the only thing enabled is AMBE_PEER.
Will this be an issue since I already have a connection to Brandmeister already defined in /opt/dmrlink/bridge/dmrlink/cfg
Thank you.
On Wed, May 11, 2016 at 12:49 PM, Steve Zingman <szingman@msgstor.com> wrote:
It's easy to steer your DMRGateway via DTMF or CLI or AllMon or AndroidIAX. Consider the following snip from ambe_audio.cfg
section = BM # Use BM section values
# order of precedence: dmrlink.cfg, section=, DEFAULTS
[BM] # Listen to all, TX on TG3100 TS1 tgFilter = 3100,3106,31094 # A list of TG IDs to monitor. All TGs will be passed to DMRGateway txTg = 3100 # TG to use for all frames received from DMRGateway -> IPSC txTs = 2 # Slot to use for frames received from DMRGateway -> IPSC
[BM3100] # Brandmeister tgFilter = 3100 # USA Nationwide txTg = 3100 txTs = 1
[BM3106] # Brandmeister tgFilter = 3106 # California Statewide txTg = 3106 txTs = 2
[BM31094] # Brandmeister tgFilter = 31094 # US call area 4 txTg = 31094 txTs = 1
[Sandbox] # Sandbox network tgFilter = 3120 txTg = 3120 txTs = 2
[LOCAL] # Local network tgFilter = 3 txTg = 3 txTs = 2
[Shutup] # Be quiet tgFilter = 0 txTg = 0 txTs = 2
/etc/asterisk/rpt.conf
; DMRGateway Commands
73 = cmd,/bin/bash -c 'echo -n "section=Shutup" | nc 127.0.0.1 31002' 74 = cmd,/bin/bash -c 'echo -n "section=BM" | nc 127.0.0.1 31002' 76 = cmd,/bin/bash -c 'echo -n "section=DMR-MARC" | nc 127.0.0.1 31002' 77 = cmd,/bin/bash -c 'echo -n "section=BM3100" | nc 127.0.0.1 31002' 78 = cmd,/bin/bash -c 'echo -n "section=BM3106" | nc 127.0.0.1 31002' 79 = cmd,/bin/bash -c 'echo -n "section=BM31094" | nc 127.0.0.1 31002'
Issue a *73 from a radio (simplified for example) and ambe_audio will use the section [Shutup] Issue a *77 from a radio (simplified for example) and ambe_audio will use the section [BM3100] Replace radio with CLI or AllMon or AndroidIAX. Add a script to cron ...
Available remote control commands: 'reread_subscribers' 'reread_config' 'txTg' 'txTs' 'section' 'gateway_dmr_id' 'gateway_peer_id' 'restart' 'playbackFromFile' 'tgs' 'dump_template' 'get_info'
See: < https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayDiagram.pdf > <https://github.com/N4IRS/DMRGateway/blob/master/DMRGateway.rtf> < https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayTechOverview.pdf >
For INAD, 73 Steve N4IRS
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing listAllstar-Digital@lists.keekles.orghttp://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- ------------------------------ John D. Hays K7VE PO Box 1223, Edmonds, WA 98020-1223 <http://k7ve.org/blog> <http://twitter.com/#!/john_hays> <http://www.facebook.com/john.d.hays>
OK, Let's take this from another direction. Yo are currently configured like this: tgFilter = 42657 txTg = 42657 txTs = 2 You want to change to this without restarting ambe_audio: tgFilter = 3100 txTg = 3100 txTs = 2 From a Linux prompt you issue 3 commands: echo -n "tgFilter = 3100" | nc 127.0.0.1 31002 echo -n "txTg = 3100" | nc 127.0.0.1 31002 echo -n "txTs = 2" | nc 127.0.0.1 31002 You are now connected to TS2 TG3100 and will transmit on TG3100. Done! Now let's do the same thing in 1 command: You have a section in ambe_audio.cfg [NoisyPlace] tgFilter = 3100 txTg = 3100 txTs = 2 Issue the command from the Linux prompt: echo -n "section=NoisyPlace" | nc 127.0.0.1 31002 You are now connected to TS2 TG3100 and will transmit on TG3100. For INAD, 73 Steve N4IRS On 05/11/2016 03:50 PM, Robert Newberry wrote:
Ya I suppose I better save copies of everything and try it. This would be the perfect ticket at home, I had a bunch of Motorola local remotes. I ended up connecting them directily to the USB FOB and made a "home radioless node" They sound superb on the air, I could monitor other DMR TG's besides my ASL ID.
On Wed, May 11, 2016 at 2:48 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
If you have a active network in /opt/dmrlink/ambe_audio/dmrlink.cfg named [LSMFT] and a section named [LSMFT] in ambe_audio.cfg without a section= in the default ambe_audio.py will use the section [LSMFT] in ambe_audio.cfg If you then add a section [yoursectionhere] with different gatewaydmrId, TgFilter, txTg, txTs those new values will be selected if you issue a echo -n "section=yoursectionhere" | nc 127.0.0.1 31002 from the Linux shell prompt.
On 5/11/2016 2:40 PM, Robert Newberry wrote:
I figured the names were arbitrary. I was mostly wondering if I was going to have a conflict having a brandmeister connection defined in /opt/dmrlink/bridge/drmlink.cfg and /opt/dmrlink/ambe_audio/dmrlink.cfg
On Wed, May 11, 2016 at 2:21 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
The names I posted are only a example. use anything you want.
On 5/11/2016 1:59 PM, Robert Newberry wrote:
I get it kind of... I'm still a little confused.
I currently have the named section defined as. I use TG 42657 as my ID to access ASL.
[AMBE_PEER] gatewaydmrId = 312307 tgFilter = 42657 txTg = 42657 txTs = 2
I put this right above what was already in the file so the next section is
[BM] tgFilter = 3100, 31094 txTg = 3100 txTx = 2
So am I to assume that in my /opt/dmrlink/ambe_audio/dmrlink.cfg
that I should ass a section for BM with the relevant connection information? currently the only thing enabled is AMBE_PEER.
Will this be an issue since I already have a connection to Brandmeister already defined in /opt/dmrlink/bridge/dmrlink/cfg
Thank you.
On Wed, May 11, 2016 at 12:49 PM, Steve Zingman <szingman@msgstor.com <mailto:szingman@msgstor.com>> wrote:
It's easy to steer your DMRGateway via DTMF or CLI or AllMon or AndroidIAX. Consider the following snip from ambe_audio.cfg
section = BM # Use BM section values
# order of precedence: dmrlink.cfg, section=, DEFAULTS
[BM] # Listen to all, TX on TG3100 TS1 tgFilter = 3100,3106,31094 # A list of TG IDs to monitor. All TGs will be passed to DMRGateway txTg = 3100 # TG to use for all frames received from DMRGateway -> IPSC txTs = 2 # Slot to use for frames received from DMRGateway -> IPSC
[BM3100] # Brandmeister tgFilter = 3100 # USA Nationwide txTg = 3100 txTs = 1
[BM3106] # Brandmeister tgFilter = 3106 # California Statewide txTg = 3106 txTs = 2
[BM31094] # Brandmeister tgFilter = 31094 # US call area 4 txTg = 31094 txTs = 1
[Sandbox] # Sandbox network tgFilter = 3120 txTg = 3120 txTs = 2
[LOCAL] # Local network tgFilter = 3 txTg = 3 txTs = 2
[Shutup] # Be quiet tgFilter = 0 txTg = 0 txTs = 2
/etc/asterisk/rpt.conf
; DMRGateway Commands
73 = cmd,/bin/bash -c 'echo -n "section=Shutup" | nc 127.0.0.1 31002' 74 = cmd,/bin/bash -c 'echo -n "section=BM" | nc 127.0.0.1 31002' 76 = cmd,/bin/bash -c 'echo -n "section=DMR-MARC" | nc 127.0.0.1 31002' 77 = cmd,/bin/bash -c 'echo -n "section=BM3100" | nc 127.0.0.1 31002' 78 = cmd,/bin/bash -c 'echo -n "section=BM3106" | nc 127.0.0.1 31002' 79 = cmd,/bin/bash -c 'echo -n "section=BM31094" | nc 127.0.0.1 31002'
Issue a *73 from a radio (simplified for example) and ambe_audio will use the section [Shutup] Issue a *77 from a radio (simplified for example) and ambe_audio will use the section [BM3100] Replace radio with CLI or AllMon or AndroidIAX. Add a script to cron ...
Available remote control commands: 'reread_subscribers' 'reread_config' 'txTg' 'txTs' 'section' 'gateway_dmr_id' 'gateway_peer_id' 'restart' 'playbackFromFile' 'tgs' 'dump_template' 'get_info'
See: <https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayDiagram.pdf> <https://github.com/N4IRS/DMRGateway/blob/master/DMRGateway.rtf> <https://github.com/N4IRS/DMRGateway/blob/master/DMRGatewayTechOverview.pdf>
For INAD, 73 Steve N4IRS
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org <mailto:Allstar-Digital@lists.keekles.org> http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- N1XBM Apparare Scientor Paratus Communicare Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657 www.radioguysrepeaternetwork.com <http://www.radioguysrepeaternetwork.com>
_______________________________________________ Allstar-Digital mailing list Allstar-Digital@lists.keekles.org http://lists.keekles.org/cgi-bin/mailman/listinfo/allstar-digital
-- "Anything is possible if you don't know what you are talking about." 1st Law of Logic
participants (4)
-
John D. Hays -
Mike Zingman -
Robert Newberry -
Steve Zingman