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.
|
HB_Bridge & IPSC_Bridge
Bob kc2cwt
I had some one ask me , what is the # of mmdvm Devices that can be connected to one hb_Bridge
-- Bob KC2CWT Carmel NewYork USA (914)497-5502
|
|
|
|
Re: Analog Bridge and DStar
I doubt it matters which is which. I would keep the working hotspot
and configure the second repeater for DummyRepeater.
toggle quoted messageShow quoted text
On 11/30/2017 10:00 PM, Mike
Swiatkowski via Groups.Io wrote:
So, the solution is to swap Repeater 1 and Repeater 2 on the gateway so Dummy is repeater 1 and Hotspot repeater is repeater 2?
|
|
|
|
Re: Analog Bridge and DStar
Mike, AA9VI
So, the solution is to swap Repeater 1 and Repeater 2 on the gateway so Dummy is repeater 1 and Hotspot repeater is repeater 2?
I had set Dummy to use port 20012 on Repeater 2. It's easy to make the swap. I'll try it.
|
|
|
|
Re: Analog Bridge and DStar
Based on the fact that DummyRepeater and ircDDBGateway are on 2
different computers I see the default for Repeater 1 set to port
20011 and DummyRepeater sets the local port to 20011 It make sense
that DummyRepeater can't be listening on localhost.
toggle quoted messageShow quoted text
On 11/30/2017 08:56 PM, Mike
Swiatkowski via Groups.Io wrote:
sysop@allstar:~$ sudo netstat -unap | grep dummy
|
|
|
|
Re: Analog Bridge and DStar
Mike, AA9VI
sysop@allstar:~$ sudo netstat -unap | grep dummy
udp 0 0 127.0.0.1:20012 0.0.0.0:* 2254/dummyrepeater sysop@allstar:~$ sudo netstat -unap | grep irc sysop@allstar:~$ sudo netstat -unap | grep nalog udp 0 0 0.0.0.0:39102 0.0.0.0:* 1775/Analog_Bridge udp 0 0 0.0.0.0:31000 0.0.0.0:* 1775/Analog_Bridge udp 0 0 0.0.0.0:34002 0.0.0.0:* 1775/Analog_Bridge sysop@allstar:~$ Again, DummyRepeater is not working as configured with 127.0.0.1, as shown here, as the local address. Dummy Repeater: 192.168.1.10 Analog Bridge: 192.168.1.10 IrcddbGW: 192.168.1.9 DMR--> Allstar using 192.168.1.10:34002 and 32002 DStar--> Allstar trying to use 192.168.1.10:34001 and 32001 Does ircddbGw need the Dummy to be set on repeater 1? Why does the LAN address work for DummyRepeater but not the local loopback 127.0.0.1? Mike
|
|
|
|
Re: Analog Bridge and DStar
Maybe this will help:
toggle quoted messageShow quoted text
root@bridge:~# netstat -unap | grep dummy udp 0 0 0.0.0.0:34001 0.0.0.0:* 404/dummyrepeater udp 0 0 0.0.0.0:56635 0.0.0.0:* 404/dummyrepeater udp 0 0 127.0.0.1:20011 0.0.0.0:* 404/dummyrepeater root@bridge:~# netstat -unap | grep irc udp 0 0 0.0.0.0:1234 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:30001 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:30002 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:30003 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:30004 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:30005 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:30006 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:30007 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:30051 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:30052 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:30053 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:30054 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:30055 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:30056 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:30057 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:30062 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:20001 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:20002 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:20003 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:20004 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:20005 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:20006 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:20007 0.0.0.0:* 402/ircddbgatewayd udp 0 0 127.0.0.1:20010 0.0.0.0:* 402/ircddbgatewayd udp 0 0 0.0.0.0:40000 0.0.0.0:* 402/ircddbgatewayd root@bridge:~# netstat -unap | grep nalog udp 0 0 0.0.0.0:44800 0.0.0.0:* 394/Analog_Bridge udp 0 0 0.0.0.0:32001 0.0.0.0:* 394/Analog_Bridge udp 0 0 0.0.0.0:31000 0.0.0.0:* 394/Analog_Bridge udp 0 0 0.0.0.0:45527 0.0.0.0:* 394/Analog_Bridge
On 11/30/2017 07:12 PM, Mike
Swiatkowski via Groups.Io wrote:
If I put 127.0.0.1 in the Edit--> Preferences--> Network --> Local address no traffic will flow to the dummy repeater. The transmit button will not send traffic to another repeater/hotspot on the LAN. If I use 192.168.1.10 then everything works as expected.
|
|
|
|
Re: Analog Bridge and DStar
You may want to list the machines and addresses involved. What is
the IP of the DummyRepeater machine? What is the IP address of the
Gateway? What is the result of netstat -unap?
toggle quoted messageShow quoted text
On 11/30/2017 07:12 PM, Mike
Swiatkowski via Groups.Io wrote:
If I put 127.0.0.1 in the Edit--> Preferences--> Network --> Local address no traffic will flow to the dummy repeater. The transmit button will not send traffic to another repeater/hotspot on the LAN. If I use 192.168.1.10 then everything works as expected.
|
|
|
|
Re: Analog Bridge and DStar
Mike, AA9VI
If I put 127.0.0.1 in the Edit--> Preferences--> Network --> Local address no traffic will flow to the dummy repeater. The transmit button will not send traffic to another repeater/hotspot on the LAN. If I use 192.168.1.10 then everything works as expected.
So, I'd like to use 127.0.0.1 in that Local Port field on Dummy Repeater since the ThumbDV and AB are on that same machine but DummyRepeater is simply not functional with that setting. It will launch fine but not traffic will flow to/from it.
|
|
|
|
Re: Analog Bridge and DStar
Mike,
I'm not sure what you mean when you say 127.0.0.1 does not work with DummyRepeater Just to make sure you understand the data flow: ircDDBGateway <---> DummyRepeater <---> Analog_Bridge <---> asterisk I understand you have ircDDBGateway on a separate machine so the actual address is going to be needed for DummyRepeater to talk to ircDDBGateway DummyRepeater needs to talk to Analog_Bridge. This is where the environment variables come into play. DummyRepeater uses the environment variables to know how to communicate with Analog_Bridge. If DR and AB are on the same machine, 127.0.0.1 is fine. Analog_Bridge uses the Analog_Bridge.ini [USRP] section to know how to talk to the asterisk channel driver. If Analog_Bridge and Asterisk are on the same machine, 127.0.0.1 is fine. 73, Steve N4IRS
|
|
|
|
Re: Invalid command from BrandMeister
#brandmeister
In the screen shots is seen the undefined connection state after I have reseted the connection at BrandMeister Dashboard.
|
|
|
|
Re: Invalid command from BrandMeister
#brandmeister
Thank You Matthew,
I'm running a HBlink server which is connected to three BrandMeister servers, Finland, Sweden and Hungary. Handling the beacon message at MMDVM host side seems to be necessary. If the BM server disconnects the HBlink client hangs on the server in undefined state. Restarting the HBlink solves the issue but reconnection could be done at HBlink side when it does not receive beacons sent from the BM server. 73 de Veijo
|
|
|
|
Re: Analog Bridge and DStar
Mike, AA9VI
Steve,
127.0.0.1 on Dummy Repeater does not work. 192.168.1.10 does. Presumably this is because the ircddbgateway is on 192.168.1.9 and in the repeater 2 settings I could not specify 127.0.0.1 (that would be the local loopback on the same machine). I needed a LAN address to specify repeater 2 since it is on a different machine on the same LAN. Why would 127.0.0.1 not work and 192.168.1.10 work for the Dummy Repeater? I tried netstat but about 50 things come up, nothing stands out to me.
|
|
|
|
Re: Analog Bridge and DStar
Create a script that sets the variables and runs dummyrepeater Sent via smoke signal (AT&T) On Nov 29, 2017 9:52 AM, "Mike Swiatkowski via Groups.Io" <mjswiatk="You can put this in the script that starts DummyRepeater or just a
script by itself.
The command env will show you your existing environment" Is this in /usr/bin/dummyrepeater or where? I thought that was the binary and you could not edit it. Are you suggesting I create a bash script to add those 3 lines in and then launch dummyrepeater? Mike
|
|
|
|
Re: Analog Bridge and DStar
Mike, AA9VI
"You can put this in the script that starts DummyRepeater or just a
script by itself.
The command env will show you your existing environment" Is this in /usr/bin/dummyrepeater or where? I thought that was the binary and you could not edit it. Are you suggesting I create a bash script to add those 3 lines in and then launch dummyrepeater? Mike
|
|
|
|
Re: Analog Bridge and DStar
On 11/28/2017 11:31 PM, Mike
Swiatkowski via Groups.Io wrote:
Steve,You can put this in the script that starts DummyRepeater or just a script by itself. The command env will show you your existing environment Yes it will work with 127.0.0.1 netstat is your friend Yes you can. Each node can have it's own instnace: [1234] rxchannel = USRP/192.168.1.10:34001:32001 [4321] rxchannel = USRP/192.168.1.10:35001:36001
|
|
|
|
Re: Invalid command from BrandMeister
#brandmeister
Matthew 2E0SIP
Hi Veijo, Personally I think its worth logging it on a debug level rather than dropping it silently, however as the end user can enable beaconing in the MMDVM.ini I don't think it needs to be handled in HBlink.
|
|
|
|
Re: Analog Bridge and DStar
Mike, AA9VI
Steve,
I read "If you need to use other ports or addresses, you can define them in the environment before you start dummyrepeter." Where do I make these changes if needed? USRP_IP="127.0.0.1";export USRP_IP
USRP_TXPORT=34001;export USRP_TXPORT
USRP_RXPORT=32001;export USRP_RXPORT (I have an Allstar-DMR USRP on ports 34002:32002, and am working on this USRP for Allstar-DStar using 34001:32001). What I noticed is the configuration of ircddbgateway and dummyrepeater is VERY, VERY, particular. I had to use the LAN address in ircddbgateway's repeater 2 address and dummyrepeater's local address. I'm thinking I have to modify that USRP IP to the LAN address now to match it since Allstar isn't seeing anything from it despite the modification in /etc/asterisk/rpt.conf to contain rxchannel = USRP/192.168.1.10:34001:32001 192.168.1.10 is necessary (I think) since Dummy repeater won't work with the 127.0.0.1 address (or am I wrong?) -- can I have two instances of USRP running on the same box as long as the ports are different? IRCDDBGATEWAY: 192.168.1.9 REPEATER 1: 127.0.0.1 (located on same box as ircddbgateway) DUMMYREPEATER (REPEATER 2): 192.168.1.10 192.168.1.10 has the Allstar - DMR gateway 192.168.1.10 working on adding Allsatr-DMR on the same box Mike
|
|
|
|
Re: More weird testing
Bob,Analog_Bridge has several audio shaping methods available (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN). The initial P25 code ad this turned off, but we can now use these to help get the audio levels correct from ASL to P25. Ideally, I would like for the AGC to be used as it will help limit the loud users but the algorithm I am using seems to pump more than I would like it to. We will keep working to get the levels and quality right, but it will take time.
|
|
|
|
Re: More weird testing
Bob,
toggle quoted messageShow quoted text
Thanks for the input, that's what I heard as well. Steve was on DMR, so it was DMR <---> ASL <---> P25 We have to do more testing of ASL ---> P25 to get the audio dialed in. There are also some code changes that need to be tested. Thanks for the report. Steve
On 11/27/2017 11:58 AM, Bob N1XBM
wrote:
|
|
|
|
Re: More weird testing
Steve Siesel [K4KSA]
I was on DMR, and I have been told my radio has always sounded robust or hot….However I do know there is a lot of audio processing going on from DMR<>Allstar<>P25……
Steve
From: DVSwitch@groups.io [mailto:DVSwitch@groups.io] On Behalf Of Bob N1XBM
Steve,
Not sure if your looking for input, but I was listening to Steve K4KSA on P25. His audio sounded a little over driven. I assume he was on analog??? Maybe it was the audio he was putting in on his side.
So far pretty good, I was listening from my end on Allstar, but I dropped the link because "everything" I got going here, a zello user on my end got in and I just didn't want to add that layer of confusion. N1XBM
On Nov 27, 2017 8:14 AM, "Bob kc2cwt" <kc2cwt@...> wrote:
|
|
|