Date   

Best Route - TG31550 to XLX273 - limited knowledge

Greg Hovland <greg@...>
 

I have successfully connected an Allstar node to BMTG31550 using the DVSwitch programs. This is done in the cloud. I have set up XLX273 using XLXD separately in the cloud.

I would now like to add and interconnect between  XLX273A and BM TG31550.  I get through Linux by Google and reading a bunch of forums, but I still consider myself new.  What would be the simplest way for me to add this interconnect?

I do have two AMBE3000 USBs available at home with a Raspberry Pi if needed.

I have seen some instructions laid dated 2019 and new ones for 2020 in this group. I'm wondering if things have changed.

Thank you in advance for your help.


Greg Hovland
W9IKU


Re: Allstar <--> DMR & DVSWITCH Was working... #brandmeister #mmdvm_bridge #analog_bridge

 

Hmm, I've never seen that problem.  All of my hotspots, instances of DVSwitch, etc connect to the same BM master.  But each one has a different 2 digit suffix on its login ID.

On 31/1/21 7:14 am, Mark Simon via groups.io wrote:
You can check if your node is connecting to Brandmeister by logging on to the Brandmeister.network  home page.  Entering your logon/password (BM password not Hotspot password) and clicking on My Hotspots in the left margin.  I saw that my DMR/Allstarlink/DVSwitch was not connecting and figured out that the hotspot that I use in my home network and DVSwitch were set for the same server.  I changed the hotspot (Zumspot) and it started working again.  One BM server per network makes sense.  Just FYI....     Mark 


-- 
73 de Tony VK3JED/VK3IRL
http://vkradio.com


Re: Allstar <--> DMR & DVSWITCH Was working... #brandmeister #mmdvm_bridge #analog_bridge

Mark Simon
 

You can check if your node is connecting to Brandmeister by logging on to the Brandmeister.network  home page.  Entering your logon/password (BM password not Hotspot password) and clicking on My Hotspots in the left margin.  I saw that my DMR/Allstarlink/DVSwitch was not connecting and figured out that the hotspot that I use in my home network and DVSwitch were set for the same server.  I changed the hotspot (Zumspot) and it started working again.  One BM server per network makes sense.  Just FYI....     Mark 


Re: Need help please have issues with connecting to 1999

Steve N4IRS
 

No, you are fine. I am starting a discussion and I think we should have it in the AllStarLink subgroup. Sorry I was not clear enough.

On 1/30/21 9:57 AM, Mike KB8JNM wrote:

I did not have a discussion, just a one post answer to the multi post problem.

Should I not answer when the answer is not in the right category as the question ?

On 1/30/2021 9:42 AM, Steve N4IRS wrote:
Mike,
Lets move the discussion of a scheme for private node numbers to the AllStarLink subgroup.

On 1/29/21 5:12 PM, Mike KB8JNM wrote:

Could it be that a node you were connected to or a node connected to you also had a 1999 private node ?

If so, it will not allow you to connect as long as one is present in the 'connected network'.

Suggest using a odd number like 1325. everyone seems to use 1999 for there first private node.

Something to look for next time.


On 1/29/2021 5:02 PM, Vince Pimentel wrote:

Yep, looks good.

[radio-secure]

exten => ${NODE},1,rpt,${NODE}

exten => ${NODE1},1,rpt,${NODE1}

The auto connect on boot works fine and that is done via macro *31999 in rpt.conf so I'm confused as to why it won't connect after a disconnect.

startup_macro = *31999

I've also searched through the logs for 1999 and the only relevant lines that come back are 

/var/log/asterisk/messages.1:[Jan 28 18:51:19] NOTICE[480] app_rpt.c: Normal Repeater Init  1999    

/var/log/asterisk/messages.1:[Jan 28 20:01:16] NOTICE[480] app_rpt.c: Normal Repeater Init  1999    

 

/var/log/asterisk/messages.1:[Jan 29 02:30:16] NOTICE[481] app_rpt.c: Normal Repeater Init  1999

Which seem to be normal for boot.

 

Welp, I just tried to connect to it again to see if I could get anything to show in the logs that would easier to find and it worked. Disconnected and reconnected like 5 times with success. No file changes, reboots or anything like that.

 

Thanks for the replies and help but it's a mystery still. Will see if I can learn anything more if it happens again. Any further thoughts or things to check/confirm are welcome but with it working. We won't be able to confirm that it was a fix.

Until it acts up again.
73




Re: Need help please have issues with connecting to 1999

Mike KB8JNM
 

I did not have a discussion, just a one post answer to the multi post problem.

Should I not answer when the answer is not in the right category as the question ?

On 1/30/2021 9:42 AM, Steve N4IRS wrote:
Mike,
Lets move the discussion of a scheme for private node numbers to the AllStarLink subgroup.

On 1/29/21 5:12 PM, Mike KB8JNM wrote:

Could it be that a node you were connected to or a node connected to you also had a 1999 private node ?

If so, it will not allow you to connect as long as one is present in the 'connected network'.

Suggest using a odd number like 1325. everyone seems to use 1999 for there first private node.

Something to look for next time.


On 1/29/2021 5:02 PM, Vince Pimentel wrote:

Yep, looks good.

[radio-secure]

exten => ${NODE},1,rpt,${NODE}

exten => ${NODE1},1,rpt,${NODE1}

The auto connect on boot works fine and that is done via macro *31999 in rpt.conf so I'm confused as to why it won't connect after a disconnect.

startup_macro = *31999

I've also searched through the logs for 1999 and the only relevant lines that come back are 

/var/log/asterisk/messages.1:[Jan 28 18:51:19] NOTICE[480] app_rpt.c: Normal Repeater Init  1999    

/var/log/asterisk/messages.1:[Jan 28 20:01:16] NOTICE[480] app_rpt.c: Normal Repeater Init  1999    

 

/var/log/asterisk/messages.1:[Jan 29 02:30:16] NOTICE[481] app_rpt.c: Normal Repeater Init  1999

Which seem to be normal for boot.

 

Welp, I just tried to connect to it again to see if I could get anything to show in the logs that would easier to find and it worked. Disconnected and reconnected like 5 times with success. No file changes, reboots or anything like that.

 

Thanks for the replies and help but it's a mystery still. Will see if I can learn anything more if it happens again. Any further thoughts or things to check/confirm are welcome but with it working. We won't be able to confirm that it was a fix.

Until it acts up again.
73



Re: Need help please have issues with connecting to 1999

Steve N4IRS
 

Mike,
Lets move the discussion of a scheme for private node numbers to the AllStarLink subgroup.

On 1/29/21 5:12 PM, Mike KB8JNM wrote:

Could it be that a node you were connected to or a node connected to you also had a 1999 private node ?

If so, it will not allow you to connect as long as one is present in the 'connected network'.

Suggest using a odd number like 1325. everyone seems to use 1999 for there first private node.

Something to look for next time.


On 1/29/2021 5:02 PM, Vince Pimentel wrote:

Yep, looks good.

[radio-secure]

exten => ${NODE},1,rpt,${NODE}

exten => ${NODE1},1,rpt,${NODE1}

The auto connect on boot works fine and that is done via macro *31999 in rpt.conf so I'm confused as to why it won't connect after a disconnect.

startup_macro = *31999

I've also searched through the logs for 1999 and the only relevant lines that come back are 

/var/log/asterisk/messages.1:[Jan 28 18:51:19] NOTICE[480] app_rpt.c: Normal Repeater Init  1999    

/var/log/asterisk/messages.1:[Jan 28 20:01:16] NOTICE[480] app_rpt.c: Normal Repeater Init  1999    

 

/var/log/asterisk/messages.1:[Jan 29 02:30:16] NOTICE[481] app_rpt.c: Normal Repeater Init  1999

Which seem to be normal for boot.

 

Welp, I just tried to connect to it again to see if I could get anything to show in the logs that would easier to find and it worked. Disconnected and reconnected like 5 times with success. No file changes, reboots or anything like that.

 

Thanks for the replies and help but it's a mystery still. Will see if I can learn anything more if it happens again. Any further thoughts or things to check/confirm are welcome but with it working. We won't be able to confirm that it was a fix.

Until it acts up again.
73



DVSwitch voice works just fine on C4FM but it's not allowed on Wires-x

IK7VXC Mike
 

Hi guys. This is an issue I ran across while having a QSO in the Italian "Room Italy" (IT-YSFROOM-ITALY). Some hams (on C4FM) hear me just fine (and with excellent audio as well), while others (on Wires-x) claim they hear nothing.
Someone pointed out that transmissions through DVSwitch are not allowed on the Wires-x platform (which to me it's really unfair!). And that's probably a matter of RADIO ID missing or something. Is this true?
Isn't there anything that can be implemented to solve this issue?

Thank you


Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ? #mmdvm_bridge

KC1JFN
 

I did some experiment, since the bridge and the YSF reflector are on the same LAN. I change the GatewayAddress=to the local ip address of the YSF Reflector server, which is also on the same network with the YSF to DMR Bridge.

KC1JFN


Re: Need help please have issues with connecting to 1999

Vince Pimentel
 

OH! I think you gents nailed it! Yes, I was on a substantial sized network and yes there were two other nodes that had 1999 running that I know of. Also DVSwitch bridges I believe. I'm still on that network but those nodes are no longer connected.

I'll give that a go but would put money on it that you're right.

Huge thank you!


Re: Need help please have issues with connecting to 1999

Steve N4IRS
 

Valid point. Need to test and come up with a unique private or number.

Sent by smoke signal (AT&T)


From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Mike KB8JNM <groupio@...>
Sent: Friday, January 29, 2021 5:12:25 PM
To: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
Subject: Re: [DVSwitch] Need help please have issues with connecting to 1999
 

Could it be that a node you were connected to or a node connected to you also had a 1999 private node ?

If so, it will not allow you to connect as long as one is present in the 'connected network'.

Suggest using a odd number like 1325. everyone seems to use 1999 for there first private node.

Something to look for next time.


On 1/29/2021 5:02 PM, Vince Pimentel wrote:

Yep, looks good.

[radio-secure]

exten => ${NODE},1,rpt,${NODE}

exten => ${NODE1},1,rpt,${NODE1}

The auto connect on boot works fine and that is done via macro *31999 in rpt.conf so I'm confused as to why it won't connect after a disconnect.

startup_macro = *31999

I've also searched through the logs for 1999 and the only relevant lines that come back are 

/var/log/asterisk/messages.1:[Jan 28 18:51:19] NOTICE[480] app_rpt.c: Normal Repeater Init  1999    

/var/log/asterisk/messages.1:[Jan 28 20:01:16] NOTICE[480] app_rpt.c: Normal Repeater Init  1999    

 

/var/log/asterisk/messages.1:[Jan 29 02:30:16] NOTICE[481] app_rpt.c: Normal Repeater Init  1999

Which seem to be normal for boot.

 

Welp, I just tried to connect to it again to see if I could get anything to show in the logs that would easier to find and it worked. Disconnected and reconnected like 5 times with success. No file changes, reboots or anything like that.

 

Thanks for the replies and help but it's a mystery still. Will see if I can learn anything more if it happens again. Any further thoughts or things to check/confirm are welcome but with it working. We won't be able to confirm that it was a fix.

Until it acts up again.
73


Re: Need help please have issues with connecting to 1999

Mike KB8JNM
 

Could it be that a node you were connected to or a node connected to you also had a 1999 private node ?

If so, it will not allow you to connect as long as one is present in the 'connected network'.

Suggest using a odd number like 1325. everyone seems to use 1999 for there first private node.

Something to look for next time.


On 1/29/2021 5:02 PM, Vince Pimentel wrote:

Yep, looks good.

[radio-secure]

exten => ${NODE},1,rpt,${NODE}

exten => ${NODE1},1,rpt,${NODE1}

The auto connect on boot works fine and that is done via macro *31999 in rpt.conf so I'm confused as to why it won't connect after a disconnect.

startup_macro = *31999

I've also searched through the logs for 1999 and the only relevant lines that come back are 

/var/log/asterisk/messages.1:[Jan 28 18:51:19] NOTICE[480] app_rpt.c: Normal Repeater Init  1999    

/var/log/asterisk/messages.1:[Jan 28 20:01:16] NOTICE[480] app_rpt.c: Normal Repeater Init  1999    

 

/var/log/asterisk/messages.1:[Jan 29 02:30:16] NOTICE[481] app_rpt.c: Normal Repeater Init  1999

Which seem to be normal for boot.

 

Welp, I just tried to connect to it again to see if I could get anything to show in the logs that would easier to find and it worked. Disconnected and reconnected like 5 times with success. No file changes, reboots or anything like that.

 

Thanks for the replies and help but it's a mystery still. Will see if I can learn anything more if it happens again. Any further thoughts or things to check/confirm are welcome but with it working. We won't be able to confirm that it was a fix.

Until it acts up again.
73


Re: Need help please have issues with connecting to 1999

Vince Pimentel
 

Yep, looks good.

[radio-secure]

exten => ${NODE},1,rpt,${NODE}

exten => ${NODE1},1,rpt,${NODE1}

The auto connect on boot works fine and that is done via macro *31999 in rpt.conf so I'm confused as to why it won't connect after a disconnect.

startup_macro = *31999

I've also searched through the logs for 1999 and the only relevant lines that come back are 

/var/log/asterisk/messages.1:[Jan 28 18:51:19] NOTICE[480] app_rpt.c: Normal Repeater Init  1999    

/var/log/asterisk/messages.1:[Jan 28 20:01:16] NOTICE[480] app_rpt.c: Normal Repeater Init  1999    

 

/var/log/asterisk/messages.1:[Jan 29 02:30:16] NOTICE[481] app_rpt.c: Normal Repeater Init  1999

Which seem to be normal for boot.

 

Welp, I just tried to connect to it again to see if I could get anything to show in the logs that would easier to find and it worked. Disconnected and reconnected like 5 times with success. No file changes, reboots or anything like that.

 

Thanks for the replies and help but it's a mystery still. Will see if I can learn anything more if it happens again. Any further thoughts or things to check/confirm are welcome but with it working. We won't be able to confirm that it was a fix.

Until it acts up again.
73


Re: Need help please have issues with connecting to 1999

Steve N4IRS
 

Check for:
[radio-secure]
exten => ${NODE1},1,rpt,${NODE1}

In extensions.conf

On 1/29/2021 3:52 PM, Vince Pimentel wrote:
Copy that, and that is also present. Sorry, didn't even think about that. #doh

1999 = radio@....0.1:4569/1999,NONE   ; and iax port number if not the default



Re: Need help please have issues with connecting to 1999

Vince Pimentel
 

Copy that, and that is also present. Sorry, didn't even think about that. #doh

1999 = radio@....0.1:4569/1999,NONE   ; and iax port number if not the default


Re: Need help please have issues with connecting to 1999

Steve N4IRS
 

You need to have 1999 in your nodes stanza or rpt.conf
Search rpt.conf for "[nodes]
Add:
1999 = radio@....0.1:4569/1999,NONE ; assuming you are using 4569 as your IAX port.

On 1/29/2021 2:57 PM, Vince Pimentel wrote:
Greetings,
I'm having a similar issue and found this thread via search, since the OP didn't come back figured I'd continue the thread. My issue only occurs if I need to drop 1999 for some reason and then try to reconnect to it.

My extensions.conf have a line for 1999 in the globals stanza

[globals]

NODE1 = 1999; This is a private node

and rpt.conf also has a stanza

[1999]

rxchannel = USRP/127.0.0.1:34001:32001  ; Use the USRP channel driver. Must be enabled in modules.conf

                                        ; 127.0.0.1 = IP of the target application

                                        ; 34001 = UDP port the target application is listening on

                                        ; 32001 = UDP port ASL is listening on

 

duplex = 0                              ; 0 = Half duplex with no telemetry tones or hang time. Ah, but $

 

hangtime = 0                            ; squelch tail hang time 0

althangtime = 0                         ; longer squelch tail hang time 0

 

holdofftelem = 1                        ; Hold off all telemetry when signal is present on receiver or f$

                                        ; except when an ID needs to be done and there is a signal comin$

 

telemdefault = 0                        ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!$

 

telemdynamic = 0                        ; 0 = disallow users to change the local telemetry setting with $

 

linktolink = no                         ; disables forcing physical half-duplex operation of main repeat$

                                        ; still keeping half-duplex semantics (optional)

 

nounkeyct = 1                           ; Set to a 1 to eliminate courtesy tones and associated delays.

 

totime = 180000                         ; transmit time-out time (in ms) (optional, default 3 minutes 18$

 

idrecording = |ie                       ; id recording or morse string see http://ohnosec.org/drupal/nod$

idtalkover = |ie                        ; Talkover ID (optional) default is none see http://ohnosec.org/$

Is something missing from these elements or do I need to add anything else?

 

 



Re: Need help please have issues with connecting to 1999

Vince Pimentel
 
Edited

Greetings,
I'm having a similar issue and found this thread via search, since the OP didn't come back figured I'd continue the thread. My issue only occurs if I need to drop 1999 for some reason and then try to reconnect to it.

My extensions.conf have a line for 1999 in the globals stanza

[globals]

NODE1 = 1999; This is a private node

and rpt.conf also has a stanza

[1999]

rxchannel = USRP/127.0.0.1:34001:32001  ; Use the USRP channel driver. Must be enabled in modules.conf

                                        ; 127.0.0.1 = IP of the target application

                                        ; 34001 = UDP port the target application is listening on

                                        ; 32001 = UDP port ASL is listening on

 

duplex = 0                              ; 0 = Half duplex with no telemetry tones or hang time. Ah, but $

 

hangtime = 0                            ; squelch tail hang time 0

althangtime = 0                         ; longer squelch tail hang time 0

 

holdofftelem = 1                        ; Hold off all telemetry when signal is present on receiver or f$

                                        ; except when an ID needs to be done and there is a signal comin$

 

telemdefault = 0                        ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!$

 

telemdynamic = 0                        ; 0 = disallow users to change the local telemetry setting with $

 

linktolink = no                         ; disables forcing physical half-duplex operation of main repeat$

                                        ; still keeping half-duplex semantics (optional)

 

nounkeyct = 1                           ; Set to a 1 to eliminate courtesy tones and associated delays.

 

totime = 180000                         ; transmit time-out time (in ms) (optional, default 3 minutes 18$

 

idrecording = |ie                       ; id recording or morse string see http://ohnosec.org/drupal/nod$

idtalkover = |ie                        ; Talkover ID (optional) default is none see http://ohnosec.org/$

USRP is also set to load in modules.conf

Is something missing from these elements or do I need to add anything else?

 

 


Re: Allstar <--> DMR & DVSWITCH Was working... #brandmeister #mmdvm_bridge #analog_bridge

Brad N8PC
 



On 1/29/2021 11:28 AM, Peter Buckley via groups.io wrote:
I had a working DVSWITCH  Allstar <--> DMR/BrandMeister Gateway.  Only using Allstar to DMR Gateway to Brandmeister....

I believe my configuration (error?) has to do with how   MMDVM_Bridge.ini    is trying to connect to BrandMeister TG 31085
(since confirmed the Allstar side & node working OK)

From  MMDVM_Bridge.ini

[General]
Callsign=N0ECT
Id=110824502         (question should this just be  1108245 ) <this should be update to a new ID but add 2 numbers to the end
Timeout=180
Duplex=0
ModeHang=0
RFModeHang=0
NetModeHang=0
Display=None
Daemon=0

[DMR Network]
Enable=0  < this needs changed to a 1 to use it
Address=127.0.0.1
Port=62031
Jitter=360
Local=62032
Password=passw0rd     (question should this be my BM Talk Group new password I created at BrandMeister) if it is a repeater then password is passw0rd. if it is a hotspt then it is the password that you set in the self care
Slot1=1
Slot2=1
ModeHang=0
Debug=0

Any HINTS?  Configuration TIPs greatly appreciated.
73s  N0ECT


Re: Allstar <--> DMR & DVSWITCH Was working... #brandmeister #mmdvm_bridge #analog_bridge

Steve N4IRS
 

The ID is your DMRID + the SSID that identifies the hot spot that you are logging into BM as.
The password is the HotSpot password you setup.

Steve N4IRS

On 1/29/2021 11:28 AM, Peter Buckley via groups.io wrote:
I had a working DVSWITCH  Allstar <--> DMR/BrandMeister Gateway.  Only using Allstar to DMR Gateway to Brandmeister....

I believe my configuration (error?) has to do with how   MMDVM_Bridge.ini    is trying to connect to BrandMeister TG 31085
(since confirmed the Allstar side & node working OK)

From  MMDVM_Bridge.ini

[General]
Callsign=N0ECT
Id=110824502         (question should this just be  1108245 )
Timeout=180
Duplex=0
ModeHang=0
RFModeHang=0
NetModeHang=0
Display=None
Daemon=0

[DMR Network]
Enable=0
Address=127.0.0.1
Port=62031
Jitter=360
Local=62032
Password=passw0rd     (question should this be my BM Talk Group new password I created at BrandMeister)
Slot1=1
Slot2=1
ModeHang=0
Debug=0

Any HINTS?  Configuration TIPs greatly appreciated.
73s  N0ECT


Allstar <--> DMR & DVSWITCH Was working... #brandmeister #mmdvm_bridge #analog_bridge

Peter Buckley
 

I had a working DVSWITCH  Allstar <--> DMR/BrandMeister Gateway.  Only using Allstar to DMR Gateway to Brandmeister....

I believe my configuration (error?) has to do with how   MMDVM_Bridge.ini    is trying to connect to BrandMeister TG 31085
(since confirmed the Allstar side & node working OK)

From  MMDVM_Bridge.ini

[General]
Callsign=N0ECT
Id=110824502         (question should this just be  1108245 )
Timeout=180
Duplex=0
ModeHang=0
RFModeHang=0
NetModeHang=0
Display=None
Daemon=0

[DMR Network]
Enable=0
Address=127.0.0.1
Port=62031
Jitter=360
Local=62032
Password=passw0rd     (question should this be my BM Talk Group new password I created at BrandMeister)
Slot1=1
Slot2=1
ModeHang=0
Debug=0

Any HINTS?  Configuration TIPs greatly appreciated.
73s  N0ECT


Addressing D-STAR reflectors via dvswitch.sh

 

I have a (mostly) working ASL to DVSwitch working.  I have discovered an
issue that I can't resolve with DTMF handling.  As I normally drive the
system from the commandline, I can work around that issue by calling
dvswitch.sh directly, which works perfectly.

However, when I use

asterisk -rx "rpt fun $SRCNODE $CMD"

to link to the TG I want, I sometimes get "3199" appended to the TG.  I
have no idea where that 3199 is coming from.  My AllStar ($SRCNODE) node
is 2199.  For example, when connecting to P25 TG 10400, DVSwitch
attempts to connect to 104003199.  This appears to happen within AllStar
(any AllStar gurus here?).  However, if I directly call "dvswitch.sh
tune <tg>" from the same script, I am linked to the correct talkgroup. 
At this point in time, this is of no consequence, because I have changed
the script that I run to call dvswitch.sh directly.  However, if I
change to directly using DTMF (or calling Asterisk to make the change),
then I will have an issue.  But even that's not certain, because I may
process DTMF via a different route.

The other thing I'm wanting to know is how to link to D-STAR reflectors
using dvswitch.sh.  I haven't yet worked out how to do that.  Any ideas?

For reference, here's the relevant section of my rpt.conf

Under the [functions] stanza

; DVSwitch mode commands sent via DTMF
00 = cmd, /opt/MMDVM_Bridge/dvswitch.sh ; unused
01 = cmd, /opt/MMDVM_Bridge/dvswitch.sh ; unused
02 = cmd, /opt/MMDVM_Bridge/dvswitch.sh ; unused
03 = cmd, /opt/MMDVM_Bridge/dvswitch.sh tune unlink  ; Unlink from last
TG / reflector
04 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode DMR
05 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode DSTAR
06 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode YSF
07 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode P25
08 = cmd, /opt/MMDVM_Bridge/dvswitch.sh mode NXDN

; connect to TG/REF on current DV mode
09=autopatchup,context=tgtune,dialtime=90000,farenddisconnect=1,noct,quiet=1
; end of DVSwitch commands

And in extensions.conf, I have:

[tgtune]
exten = _X.,1,noop ; Wait,1
exten = _X.,n,System(/opt/MMDVM_Bridge/dvswitch.sh mute TLV)
exten = _X.,n,Playback(connecting)
exten = _X.,n,SayDigits(${EXTEN})
exten = _X.,n,System(/opt/MMDVM_Bridge/dvswitch.sh tune ${EXTEN})
exten = _X.,n,System(/opt/MMDVM_Bridge/dvswitch.sh mute OFF)
exten = _X.,n,Hangup

And the node does speak the extra "3199", suggesting that ${EXTEN}
contains these extra digits.  Odd thing is my first attempt today via
AllStar worked perfectly, but subsequent attempts had the extra "3199".

--
73 de Tony VK3JED/VK3IRL
http://vkradio.com

1541 - 1560 of 9884