Welcome to DVSwitch
DVSwitch is a set of tools and programs related to provisioning and operating Amateur Radio digital voice networks.
Purpose
The purpose of DVSwitch is as follows:
1) Allows “local” networking during an outage of the regional national/international network server.
2) Allows a local network operator to “blend” upstream feeds from different Networks (capital N on purpose). These Networks can’t get their act together and learn how to play nice with each other (everyone guilty as far as we are concerned). They may not like people doing this, but the solution is to grow up and work with each other, and not keep trying to force people to take sides.
3) Allows local segregation of localized traffic with more flexibility.
4) Allows experimentation with linking and how it’s done (part 97 specifies experimentation and advancement of the radio art are a core part of amateur radio).
1) Allows “local” networking during an outage of the regional national/international network server.
2) Allows a local network operator to “blend” upstream feeds from different Networks (capital N on purpose). These Networks can’t get their act together and learn how to play nice with each other (everyone guilty as far as we are concerned). They may not like people doing this, but the solution is to grow up and work with each other, and not keep trying to force people to take sides.
3) Allows local segregation of localized traffic with more flexibility.
4) Allows experimentation with linking and how it’s done (part 97 specifies experimentation and advancement of the radio art are a core part of amateur radio).
Mission Statement/Position
Our stated position is:
WHEREAS the Networks continue to be largely islands and are not working together to create a unified network of Networks.
WHEREAS no firm reason has been given by any of the Networks why a *competent* local network operator cannot make this work effectively.
(US ONLY)
WHEREAS 47 CFR 97 (Amateur Radio Service) specifies that a core component of amateur radio is experimentation and advancement of the radio art [97.1(b)].
BE IT RESOLVED the core group of US amateur radio operators and experimenters organized around the DVSwitch project, and in the spirit of USA 47 CFR 97 and its intentions, support the *responsible* and *thoughtful* use of digital voice networking tools to create localized networks that will interconnect to the national/international Networks, and will support users of its tools in order to do this in the most effective and sustainable way possible.
WHEREAS the Networks continue to be largely islands and are not working together to create a unified network of Networks.
WHEREAS no firm reason has been given by any of the Networks why a *competent* local network operator cannot make this work effectively.
(US ONLY)
WHEREAS 47 CFR 97 (Amateur Radio Service) specifies that a core component of amateur radio is experimentation and advancement of the radio art [97.1(b)].
BE IT RESOLVED the core group of US amateur radio operators and experimenters organized around the DVSwitch project, and in the spirit of USA 47 CFR 97 and its intentions, support the *responsible* and *thoughtful* use of digital voice networking tools to create localized networks that will interconnect to the national/international Networks, and will support users of its tools in order to do this in the most effective and sustainable way possible.
|
Re: Controlling DVSwitch from AllStar
inmarex@...
Tony , I have a short question: How can I install a Allstar on the same RasPi (4) where DVSwitch Server is ? What flavor of AllStar do I need ?
|
|
|
|
YSF and DMR bridging
Aaron Groover
I know I’m sorry this a repeated subject however today blue ridge is just giving tons of issues with the internet and I cannot load the forums/threads page to find the answers before asking. So I apologize for that.
So I have a ysf reflector and a dmr reflector that I want them to both communicate (bridge) with each other.
I do have asl to dmr working no issues but just don’t know how to make them BOTH communicate.
From what i was told you don’t need analog bridge, but just run the MMDVM bridge. Now my question is in dvswitch what is the TG I’m exporting? 9, my dmr TG or fusion? Obviously the fallback ID is self explanatory.
Steve if your seeing this, really sorry you have to repeat it again....
--
Thank You,
Aaron Groover
The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future. **This message has been composed on a mobile application. Please excuse any grammatical errors**
|
|
|
|
Re: Controlling DVSwitch from AllStar
On 10/11/20 11:58 am, Steve N4IRS wrote:
Tony,Just issued that command manually, seemed to work. However, looks like there needs to be some more "idiot proofing" required. As things stand, it's too easy to remain linked up to something when switching modes, so I might implement a "disconnect before mode switch" command using one of the unused command codes (simply switching modes may still be useful in some corner cases). -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
|
|
Re: XLX899 <> Allstar 40171
On 10/11/20 5:30 am, Patrick Perdue wrote:
Yes, I've just finished integrating DVSwitch with ASL and it's fairly straightforward. Just got the final pieces of the puzzle from Steve, and I now have a working multimode AllStar node, that needs only an analog FM radio with DTMF to access any of the modes the system supports (currently YSF, DMR and P25). -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
|
|
Re: Controlling DVSwitch from AllStar
Tony,
toggle quoted messageShow quoted text
That was my mistake, use disconnect rather then unlink. Let me know. Steve
On 11/9/20 7:55 PM, Tony Langdon wrote:
On 10/11/20 12:10 am, Steve N4IRS wrote:Tony,Thanks Steve, that worked perfectly. Tested connections to DMR, YSF and
|
|
|
|
Re: Controlling DVSwitch from AllStar
On 10/11/20 12:10 am, Steve N4IRS wrote:
Tony,Thanks Steve, that worked perfectly. Tested connections to DMR, YSF and P25, all working well. :) Only thing I've noticed is that the disconnect command (dvswitch.sh tune unlink) really doesn't seem to do much, but all the others are working. In a sense, it's no biggie, because I can always take down the private node link when issuing the unlink command and bring it up when selecting a DV mode. -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
|
|
Re: Controlling DVSwitch from AllStar
On 10/11/20 8:25 am, Steve N4IRS wrote:
It was in the first message, but here it is again: Ahh OK sorry, must have been half asleep when I read your first reply. Thanks again. I'm about to have some fun with my scripting. :) -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
|
|
Re: Controlling DVSwitch from AllStar
dvswitch,sh is installed with MMDVM_Bridge. it's in /opt/MMDVM_Bridge.
toggle quoted messageShow quoted text
No, you can install DVSwitch Server on ASL 1.01. You do not need a second RPi Yes, you can have python 3.7 and 3.x on the same machine. As to controlling DVSwitch with voice, if you can run a bash script and pass a parameter, you should be able to control DVSwitch Server.
On 11/9/20 5:24 PM, Neil k8it wrote:
|
|
|
|
Re: Controlling DVSwitch from AllStar
Neil k8it
Hi, I have two questions. Where can I download switch.sh? Is it included in the package allready released? Question 2. With a RPI3 plus, do I need two PI boards to run Allstar 1.0, DVSWITCH, Python 2.7 at the same time? The purpose of Python is to interface with remote USe GPIO. IT allows me to have a low voltage data bus between a A LLSTAR node and an Amazon Alexa Echo Dot. I use the Dot Routine functions to control the bus, allowing voice commands for Allstar. Now I want to expand it for the digital modes. As I am totatlly blind, the voice control is a huge help. It will also work for mobile users.
From: "Steve N4IRS" <szingman@msgstor.com> Sent: Monday, November 09, 2020 8:10 AM To: <main@DVSwitch.groups.io> Subject: Re: [DVSwitch] Controlling DVSwitch from AllStar Tony,
|
|
|
|
Re: Controlling DVSwitch from AllStar
It was in the first message, but here it is again:
toggle quoted messageShow quoted text
Now, lets add some commands to control the modes from ASL. Add this to your [functions stanza]. I chose 0 as a first character since it's not used in the default ASL. ; 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
On 11/9/20 4:15 PM, Tony Langdon wrote:
On 10/11/20 12:10 am, Steve N4IRS wrote:Tony,Thanks Steve. I think I'm pretty close, as I took my AllStar settings
|
|
|
|
Re: Controlling DVSwitch from AllStar
On 10/11/20 12:10 am, Steve N4IRS wrote:
Tony, Thanks Steve. I think I'm pretty close, as I took my AllStar settings from my working multimode gateway, which I know I turned off all the telemetry stuff on. Will take a look at the rest and set it up. And the other question is how can I add other modes (YSF, etc) to this? -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
|
|
Re: XLX899 <> Allstar 40171
Patrick Perdue
If you're using HamVoIP, it's much, much easier to dedicate a second Pi to DVSwitch and connect USRP between them on the LAN. I've done this, and it works well. I also have a couple of ASL 1.01 systems. Once you have ASL up and running, it's a lot easier to integrate DVSwitch on the same hosting machine than with HamVoIP.
On 11/9/2020 1:24 PM, Daren. 2E0LXY. wrote:
Ah OK many thanks for the reply.
|
|
|
|
Re: XLX899 <> Allstar 40171
Ah OK many thanks for the reply.
I installed HAMVOIP as it was so much easier than installing the other system. I actually can't do the other system after trying so many times I gave up. Looks like I may have to lock myself in a padded room and try again! 😂
|
|
|
|
Re: Controlling DVSwitch from AllStar
Tony,
toggle quoted messageShow quoted text
I'm working out a issue with changing TGs now. I hope you have been using dvswitch.sh to control the server. If you have not, you need to be. dvswitch.sh was built for just this thing in mind. I have to do a updated write up but here is most of it in message form. First, let's make sure you have the private node setup to work best with DVSwitch. These are the recommended settings you should have. You may have other parameters: [1XXX] 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 Allison STILL talks! 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 from connected nodes ; except when an ID needs to be done and there is a signal coming from a connected node. telemdefault = 0 ; 0 = telemetry output off. Don't send Allison to DMR !!!!!!!!!!!!!!!!! Trust me. telemdynamic = 0 ; 0 = disallow users to change the local telemetry setting with a COP command, linktolink = no ; disables forcing physical half-duplex operation of main repeater while ; 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 180000 ms) idrecording = |ie ; id recording or morse string see http://ohnosec.org/drupal/node/87 idtalkover = |ie ; Talkover ID (optional) default is none see http://ohnosec.org/drupal/node/129 Now, lets add some commands to control the modes from ASL. Add this to your [functions stanza]. I chose 0 as a first character since it's not used in the default ASL. ; 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 To dial a TG number or reflector number, we need to pass a arbitrary number of string to dvswitch.sh ; This nice simple one line function (and dialplan) was written by Mike KB8JNM. It will allow you to pass arbitrary string of digits to a external script for processing. ; We are going to use this to pass a TG or reflector number (DMR, NXDN, P25 YSF) to Analog_Bridge so that you can change the TG you are connected to from the DTMF pad on your analog ; radio. Example: If you dial *093100 (read this as *09 3100) you can tell dvswitch.sh to tune to TG 3100 on the current digital mode. 09=autopatchup,context=tgtune,dialtime=90000,farenddisconnect=1,noct,quiet=1 Add this to extensions.conf This is a work in progress and I will post a update when I'm ready. [tgtune] exten = _X.,1,noop ; Wait,1 exten = _X.,n,System(/opt/MMDVM_Bridge/dvswitch.sh mute TLV) 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
On 11/8/2020 11:13 PM, Tony Langdon wrote:
I've installed an instance of DVSwitch on my AllStar node, and I've been
|
|
|
|
Controlling DVSwitch from AllStar
I've installed an instance of DVSwitch on my AllStar node, and I've been
able to link it to Brandmeister and select talkgroups from the commend line. I'm yet to get it working via AllStar commands. The USRP interface is working well. I have it running on a private node, so I can isolate the digital gateway from the node, when it's not in use by disconnecting the private node from my main AllStar node. In addition to getting the AllStar side working (for future control from remote stations), I'd also like to be able to link to the other modes - YSF, P25, etc, again ideally using DTMF comands. Is there any documentation that I can look up? I am running ASL and DVSwitch on a Debian 9 PC. -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
|
|
Re: Pass callsigns YSF<>DMR via MMDVM_Bridge
#mmdvm_bridge
I: 2020-11-08 20:48:44.634 MMDVM_Bridge:
toggle quoted messageShow quoted text
I: 2020-11-08 20:48:44.634 Portions Copyright (C) 2018, 2019, 2020 DVSwitch, INAD. I: 2020-11-08 20:48:44.634 Hacks by Mike N4IRR and Steve N4IRS I: 2020-11-08 20:48:44.634 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I: 2020-11-08 20:48:44.634 This software is for use on amateur radio networks only, I: 2020-11-08 20:48:44.634 it is to be used for educational purposes only. Its use on I: 2020-11-08 20:48:44.634 commercial networks is strictly prohibited. I: 2020-11-08 20:48:44.634 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others M: 2020-11-08 20:48:44.634 MMDVM_Bridge-20201031_V1.6.0 is starting M: 2020-11-08 20:48:44.634 Built 15:53:02 Oct 28 2020 (GitID #008e177)
On 11/8/20 5:26 PM, hello@...
wrote:
Thanks a lot Steve. I'm super happy now.
|
|
|
|
Re: Pass callsigns YSF<>DMR via MMDVM_Bridge
#mmdvm_bridge
@hamzahradio
Thanks a lot Steve. I'm super happy now.
Appreciate the help. Are you a developer of this software? 73
|
|
|
|
Re: Pass callsigns YSF<>DMR via MMDVM_Bridge
#mmdvm_bridge
http://www.pistar.uk/downloads/DMRIds.dat
toggle quoted messageShow quoted text
I suggest you build your bridge with DVSwitch Server so that the files are downloaded daily.
|
|
|
|
Re: Pass callsigns YSF<>DMR via MMDVM_Bridge
#mmdvm_bridge
@hamzahradio
Ah OK, where can I download the new file from?
|
|
|
|
Re: Pass callsigns YSF<>DMR via MMDVM_Bridge
#mmdvm_bridge
MB was unable to resolve DMRID 2680070 so it passed it to YSF as a
callsign.
toggle quoted messageShow quoted text
If you get the DMR ID from from github, it's not current. Steve M: 2020-11-08 21:19:41.225 DMR Slot 2, received network voice header from 2680070 to TG 73583 M: 2020-11-08 21:19:41.226 YSF, TX state = ON I: 2020-11-08 21:19:41.226 YSF, Begin TX: src=2680070 rpt=0 dst=73583 slot=2 cc=0 metadata=2680070
On 11/8/20 4:22 PM, hello@...
wrote:
Just did a tail command of the log, it has the callsign of the person who TX'd CT1ERY, but it just passed through his DMRID to yaesu not the callsign.
|
|
|