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: MMDVM_Bridge timeout to DMRGateway
post the relevant sections of each config file.
toggle quoted messageShow quoted text
On 1/31/2019 3:34 PM, Steve KC1AWV
wrote:
Bridge log. This is the DMRGateway log
|
|
|
|
Re: MMDVM_Bridge timeout to DMRGateway
Bridge log. This is the DMRGateway log
M: 2019-01-31 20:23:58.186 MMDVM Network, The connected MMDVM is closing down M: 2019-01-31 20:25:04.889 MMDVM Network, The connected MMDVM is closing down M: 2019-01-31 20:26:08.251 MMDVM Network, The connected MMDVM is closing down M: 2019-01-31 20:27:14.977 MMDVM Network, The connected MMDVM is closing down M: 2019-01-31 20:28:18.317 MMDVM Network, The connected MMDVM is closing down M: 2019-01-31 20:29:25.041 MMDVM Network, The connected MMDVM is closing down M: 2019-01-31 20:30:28.382 MMDVM Network, The connected MMDVM is closing down M: 2019-01-31 20:31:35.104 MMDVM Network, The connected MMDVM is closing down M: 2019-01-31 20:32:38.434 MMDVM Network, The connected MMDVM is closing down M: 2019-01-31 20:33:45.181 MMDVM Network, The connected MMDVM is closing down
|
|
|
|
Re: MMDVM_Bridge timeout to DMRGateway
Is this he bridge log or the gateway log?
toggle quoted messageShow quoted text
Yes, I have used MMDVM_Bridge with DMRGateway.
On 1/31/2019 3:30 PM, Steve KC1AWV
wrote:
Has anyone else seen or fixed an issue with MMDVM_Bridge successfully logging into DMRGateway, then timing out? Here's the relevant logs:
|
|
|
|
MMDVM_Bridge timeout to DMRGateway
Has anyone else seen or fixed an issue with MMDVM_Bridge successfully logging into DMRGateway, then timing out? Here's the relevant logs:
M: 2019-01-31 20:18:44.725 DMR, Logged into the master successfully E: 2019-01-31 20:20:44.760 DMR, Connection to the master has timed out, retrying connection M: 2019-01-31 20:20:44.760 DMR, Closing DMR Network M: 2019-01-31 20:20:44.761 DMR, Opening DMR Network M: 2019-01-31 20:20:54.794 DMR, Logged into the master successfully E: 2019-01-31 20:22:54.822 DMR, Connection to the master has timed out, retrying connection M: 2019-01-31 20:22:54.822 DMR, Closing DMR Network M: 2019-01-31 20:22:54.824 DMR, Opening DMR Network M: 2019-01-31 20:23:04.852 DMR, Logged into the master successfully E: 2019-01-31 20:25:04.884 DMR, Connection to the master has timed out, retrying connection M: 2019-01-31 20:25:04.884 DMR, Closing DMR Network M: 2019-01-31 20:25:04.884 DMR, Opening DMR Network M: 2019-01-31 20:25:14.918 DMR, Logged into the master successfully From what I can see, the connection is made and everything looks good on the reflector, but every 130 seconds, MMDVM times out. I did set Timeout=0 in the ini file. Steve KC1AWV
|
|
|
|
Re: Blog with P25<->DMR Info
Well, I got the P25 bridge uniquely named. hmm it still doesn't appear to be bridged?
On Wed, Jan 30, 2019 at 4:38 PM <mike@...> wrote:
|
|
|
|
Re: Blog with P25<->DMR Info
mike@...
OK - a couple of things... your Analog Bridges need to be uniquely named, and have uniquely named .ini files. The .ini files are different for each as well. Review the Build and Configure sections on blog.927.org for how to create the needed files and tweak the ini files. Also - In the log snippet you just posted, P25 is the indicated mode, but you're supplying DMR-ID info. No need to do that for the P25 ini file. Also v2.0: The DMR-ID in your log has an extra digit in it - 313666507 - which might be causing the BM master connection issues if that's what you're using elsewhere in the setup.
On Wed, Jan 30, 2019 at 2:28 PM Russell, KV4S <russelljthomas@...> wrote:
|
|
|
|
Re: Blog with P25<->DMR Info
I: 2019-01-30 22:25:57.822 Analog Bridge is starting M: 2019-01-30 22:25:57.823 Setting [GENERAL] logLevel -> 2 M: 2019-01-30 22:25:57.823 Setting [GENERAL] exportMetadata -> true M: 2019-01-30 22:25:57.823 Setting [GENERAL] subscriberFile -> /var/lib/dvswitch/subscriber_ids.csv M: 2019-01-30 22:25:57.823 Setting [GENERAL] decoderFallBack -> true M: 2019-01-30 22:25:57.823 Setting [GENERAL] useEmulator -> true M: 2019-01-30 22:25:57.824 Setting [GENERAL] emulatorAddress -> 127.0.0.1:2470 M: 2019-01-30 22:25:57.824 Setting [GENERAL] outputAudioDevice -> /dev/null M: 2019-01-30 22:25:57.824 Setting [GENERAL] inputAudioDevice -> /dev/null M: 2019-01-30 22:25:57.824 Setting [GENERAL] useMicrophone -> false M: 2019-01-30 22:25:57.824 Setting [GENERAL] useVox -> false M: 2019-01-30 22:25:57.824 Setting [GENERAL] voxDecay -> 2 M: 2019-01-30 22:25:57.824 Setting [GENERAL] voxTrigger -> 200 W: 2019-01-30 22:25:57.824 Using deprecated option "server" M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] server -> 127.0.0.1 W: 2019-01-30 22:25:57.824 Using deprecated option "fromDMRPort" M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] fromDMRPort -> 34100 W: 2019-01-30 22:25:57.824 Using deprecated option "toDMRPort" M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] toDMRPort -> 34103 M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] ambeMode -> P25 M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] minTxTimeMS -> 2000 M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] gatewayDmrId -> 3136665 M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] repeaterID -> 313666507 M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] txTg -> 31777 M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] txTs -> 2 M: 2019-01-30 22:25:57.824 Setting [AMBE_AUDIO] colorCode -> 1 W: 2019-01-30 22:25:57.824 Using deprecated option "server" M: 2019-01-30 22:25:57.824 Setting [USRP] server -> 127.0.0.1 W: 2019-01-30 22:25:57.824 Using deprecated option "toASLPort" M: 2019-01-30 22:25:57.824 Setting [USRP] toASLPort -> 34001 W: 2019-01-30 22:25:57.824 Using deprecated option "fromASLPort" M: 2019-01-30 22:25:57.824 Setting [USRP] fromASLPort -> 32001 M: 2019-01-30 22:25:57.824 Setting [USRP] aslAudio -> AUDIO_USE_GAIN M: 2019-01-30 22:25:57.824 Setting [USRP] agcGain -> 5.0 M: 2019-01-30 22:25:57.824 Setting [USRP] dmrAudio -> AUDIO_USE_GAIN M: 2019-01-30 22:25:57.824 Setting [USRP] dmrGain -> 0.17 W: 2019-01-30 22:25:57.824 Using deprecated option "server" M: 2019-01-30 22:25:57.824 Setting [DV3000] server -> 127.0.0.1 W: 2019-01-30 22:25:57.824 Using deprecated option "port" M: 2019-01-30 22:25:57.824 Setting [DV3000] port -> 2460 W: 2019-01-30 22:25:57.824 ioctl reset error W: 2019-01-30 22:25:57.824 ioctl speed error W: 2019-01-30 22:25:57.824 ioctl stereo error W: 2019-01-30 22:25:57.824 ioctl setfmt error M: 2019-01-30 22:25:57.824 Audio In/Out Device: /dev/null I: 2019-01-30 22:25:57.824 Open UDP listener on 127.0.0.1:34100 I: 2019-01-30 22:25:57.824 Open USRP on 127.0.0.1:34001 M: 2019-01-30 22:25:57.824 Connecting to DV3000 hardware...... W: 2019-01-30 22:25:58.845 DV3000 not found at 127.0.0.1:2460 I: 2019-01-30 22:25:59.455 Subscriber IDs loaded: 120633 I: 2019-01-30 22:25:59.455 Default extended metadata <K2HZE> I: 2019-01-30 22:25:59.455 Connecting to emulator on host 127.0.0.1:2470 W: 2019-01-30 22:25:59.455 Using software MBE decoder version 1.2.3 W: 2019-01-30 22:25:59.455 Using software OP25 IMBE/AMBE vocoder I: 2019-01-30 22:25:59.456 Starting Analog_Bridge --> USRP thread I: 2019-01-30 22:25:59.459 Open UDP listener on 127.0.0.1:32001 I: 2019-01-30 22:25:59.459 Starting USRP --> IPSC_Bridge thread
On Wed, Jan 30, 2019 at 4:27 PM Russell Thomas <russelljthomas@...> wrote:
|
|
|
|
Re: Blog with P25<->DMR Info
never mind, i think I fixed that. let me keep testing and see if i get further.
On Wed, Jan 30, 2019 at 4:21 PM Russell, KV4S via Groups.Io <russelljthomas=gmail.com@groups.io> wrote:
|
|
|
|
Re: Blog with P25<->DMR Info
great catch i had got interrupted and did not finish setting up the second analog bridge's service file to make it start. I started it in the foreground and it's getting this?: 2019-01-30 22:16:18.817 Repeater ID can not be the same as subscriber ID where can i find the P25Hosts.txt and what should it be set to?
On Wed, Jan 30, 2019 at 3:49 PM <mike@...> wrote:
|
|
|
|
Re: Blog with P25<->DMR Info
mike@...
According the logs, you only have one instance of Analog_Bridge running. You need 2. One for DMR and one for P25 (or perhaps didn't include that log) I also see that you're loading 17 P25 Reflectors. While probably not critical, your P25Hosts.txt only needs the localhost reflector information, as it isn't meant to connect to others... Network Access Control (NAC) is analogous to CTCSS for P25.
On Wed, Jan 30, 2019 at 1:12 PM Russell, KV4S <russelljthomas@...> wrote:
|
|
|
|
Re: Blog with P25<->DMR Info
I have been following the blog working on a Bridge for a fellow in NY and I don't think somethings is linked up correctly but nothing is jumping out at me in the logs. Logs are located here for review: https://we.tl/t-LYRjUm1WpC let me know what i'm missing. Also, what is NAC?
On Tue, Jan 29, 2019 at 11:30 AM Steve N4IRS <szingman@...> wrote: Make these both true.
|
|
|
|
Re: Deployment Question for the group
Ben Fogt
This should work. Essentially the VPN will be an extension of your network where people would connect inbound. I will use a cloud server as an example INTERNET <-> Cloud server <-> VPN <-> Hospital site On your cloud server you can manually add static routes to the VPN network so when traffic comes in on X port, it routes to the VPN network. This will be much simpler I think, using a router or a gateway device as you can simply configure all your routes in there to immediately forward to the VPNs first hop address. INTERNET <-> Gateway/Router <-> LAN <-> VPN Server <-> Hospital device | | |-----------------------------------| Static route to VPN pseudo routes/port forward would look like: UDP port 62031 forwards to 10.0.1.13 (IP of device at hosp) UDP port 10100 forwards to 10.0.1.13 (IP of device at hosp) etc etc etc .... 10.0.1.0/24 routes to 172.16.32.1 (VPN IP local on your side, aka next hop) This is rough, but hopefully it gives you an idea.
On Tue, Jan 29, 2019 at 6:56 PM Mike AE4ML <mike.lussier@...> wrote: I have a site at a local hospital. I have recently obtained a wired internet connection for the Quantar and RMS Gateway on their guest network. Because of hipa and other issues I found that I can pass traffic out to the talkgroups but nothing is making it back to me. --
Ben Fogt N5AMD
|
|
|
|
Re: P25 Reflector
Oren,
toggle quoted messageShow quoted text
When you installed the P25Reflector with apt-get install, you got the systemd unit for starting, stopping and starting the reflector at boot. here are the commands: systemctl status p25reflector is the service running. systemctl stop p25reflector stop the service running. systemctl start p25reflector start the service running. systemctl status p25reflector enable the service to run at boot. systemctl status p25reflector disable the service at boot The service should be installed and starting at boot. The reflector uses the log entry in /opt/P25Reflector/P25Reflector.ini to control where the log file is placed. Should be /var/log/mmdvm Hope this helps. 73, Steve N4IRS
On 1/29/19 8:46 PM, Oren K5LPD wrote:
|
|
|
|
Re: Deployment Question for the group
David Uzzell
I have a Satellite 2 way link that is on a nat’ed private range ip’s so I can’t route traffic in. I have a cloud machine on Vultr.com for $5/m that is my VPN server running OpenVPN using iptables to route the needed ports over the VPN and have no problems at all with IRLP, about to build ASL and do the same thing, at least there are less ports to forward. David
|
|
|
|
Re: P25 Reflector
Oren K5LPD <ohaydel@...>
One additional question... I suppose I can create a startup script to where the Reflector starts automatically if the computer reboots right? Also, once the reflector is started, can I close the terminal window? It looks like the logs run on the screen and I was not sure how to keep the reflector running. Also, how to safely shut down the reflector if needed? Thanks!
|
|
|
|
Deployment Question for the group
I have a site at a local hospital. I have recently obtained a wired internet connection for the Quantar and RMS Gateway on their guest network. Because of hipa and other issues I found that I can pass traffic out to the talkgroups but nothing is making it back to me.
Q1. Has anyone run into this before and what was the solution ? Q2. has anyone attempted to run a VPN tunnel on the pi that is handling QB, MMDVM & P25gateway ? I don't even know if I can establish a VPN over this network. I decided its worth a try. Mike
|
|
|
|
Re: P25 Reflector
Oren K5LPD <ohaydel@...>
Looks like I have it working. Thanks a bunch guys. Do you have a quick tutorial on getting the dashboard up an running?
ohaydel@ubuntu:~/opt/P25Reflector$ sudo ./P25Reflector P25Reflector.ini
I: 2019-01-30 00:39:42.676 Opening P25 network connection
I: 2019-01-30 00:39:42.809 Loaded 123007 Ids to the callsign lookup table
M: 2019-01-30 00:39:42.809 Starting P25Reflector-20161101
I: 2019-01-30 00:39:42.809 Started the DMR Id lookup reload thread
M: 2019-01-30 00:41:42.826 No repeaters linked
|
|
|
|
Re: P25 Reflector
The file is either there or it's not. The Reflector does not
download the file.
toggle quoted messageShow quoted text
On 1/29/19 6:32 PM, Mike, KI0IK wrote:
Try restarting the P25Reflector. I think I remember getting that error the first time I ran it too. Probably because the file didn't exist yet.
|
|
|
|
Re: P25 Reflector
Try restarting the P25Reflector. I think I remember getting that error the first time I ran it too. Probably because the file didn't exist yet.
|
|
|
|
Re: P25 Reflector
Check where the file is pointed to in P25Reflector.ini
toggle quoted messageShow quoted text
If the path does not exist create it. get the file from wget https://github.com/g4klx/P25Clients/raw/master/P25Reflector/DMRIds.dat it's old but it will get you started.
On 1/29/19 4:34 PM, Oren K5LPD wrote:
|
|
|