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: ASL to P25 bridge
#analog_bridge
Yes it is there in the downloaded P25Hosts.txt file
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
show me the entry.
toggle quoted messageShow quoted text
On 8/10/20 6:44 PM, Tom wrote:
Yes in PrivateHost file
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Yes in PrivateHost file
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
in /var/lib/mmdvm/private_P25Hosts.txt
toggle quoted messageShow quoted text
10888 reflector.ip.address reflector.udp.port restart the gateway
On 8/10/20 6:39 PM, Tom wrote:
The P25Gateway log says: No response from 10888, unlinking. It doesn't seem to be able to connect to the reflector (10888).
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Is 10888 in the host file?
toggle quoted messageShow quoted text
On 8/10/20 6:39 PM, Tom wrote:
The P25Gateway log says: No response from 10888, unlinking. It doesn't seem to be able to connect to the reflector (10888).
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
If you see no activity ASL --> AB the something is wrong here:
toggle quoted messageShow quoted text
Analog_Bridge.ini DVSwitch.ini [AMBE_AUDIO] [P25] address = 127.0.0.1 <-> Address = 127.0.0.1 txPort = 34103 <------> RXPort = 34103 rxPort = 34100 <------> TXPort = 34100
On 8/10/20 6:30 PM, Tom wrote:
OK, I changed the AB ini file.
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
The P25Gateway log says: No response from 10888, unlinking. It doesn't seem to be able to connect to the reflector (10888).
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
OK, I changed the AB ini file.
I can see ASL activity on AB log. I see no corresponding changes in mmdvm log. The mmdvm log also states: Remote Gateway: no Is that correct? How do I test beyond AB to see ASL originated activity. Also Activity on the Reflector don't seem to interact with the Gateway. Tom
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Tom,
toggle quoted messageShow quoted text
The flow looks like this: AB <-> MB <-> P25Gateway Analog_Bridge.ini DVSwitch.ini [AMBE_AUDIO] [P25] address = 127.0.0.1 <-> Address = 127.0.0.1 txPort = 34103 <------> RXPort = 34103 rxPort = 34100 <------> TXPort = 34100 MMDVM_Bridge.ini P25Gateway.ini [P25 Network] [GENERAL] GatewayAddress=127.0.0.1 <-> RptAddress=127.0.0.1 GatewayPort=42020 <--------> LocalPort=42010 LocalPort=32010 <----------> RptPort=32010 You had AB pointed at P25Gateway etc.
On 8/10/20 5:50 PM, Tom wrote:
Attached are all 5 ini files.
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Attached are all 5 ini files.
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Show me your DVSwitch.ini
toggle quoted messageShow quoted text
On 8/10/20 5:40 PM, Tom wrote:
Attached
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Attached
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
I need to see both logs from a fresh start to waiting for traffic.
Do not truncate.
toggle quoted messageShow quoted text
On 8/10/20 5:34 PM, Tom wrote:
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
root@P25reflector:/var/log/dvswitch # tail -f Analog_Bridge.log
M: 2020-08-10 21:29:52.793 Connecting to DV3000 hardware......
W: 2020-08-10 21:29:53.800 DV3000 not found at 127.0.0.1:2460
I: 2020-08-10 21:29:54.706 Subscriber IDs loaded: 169853
I: 2020-08-10 21:29:54.706 Default extended metadata <K5TRA>
W: 2020-08-10 21:29:54.706 Using software MBE decoder version 1.2.3
W: 2020-08-10 21:29:54.706 Using software OP25 IMBE/AMBE vocoder
I: 2020-08-10 21:29:54.707 Sending to USRP clients at 127.0.0.1 on port(s) 32001
E: 2020-08-10 21:29:54.707 Can not bind port 42020, error code = 98 (Address already in use)
I: 2020-08-10 21:29:54.707 Starting TLV --> Analog_Bridge (decoder) --> USRP thread
I: 2020-08-10 21:29:54.707 Starting USRP --> Analog_Bridge (encoder) -> TLV thread root@P25reflector:/var/log/mmdvm # tail -f MMDVM_Bridge-2020-08-10.log
I: 2020-08-10 21:24:52.615 Loaded 169853 Ids to the DMR callsign lookup table
I: 2020-08-10 21:24:52.615 P25 RF Parameters
I: 2020-08-10 21:24:52.615 Started the DMR Id lookup reload thread
I: 2020-08-10 21:24:52.615 Id: 3148777
I: 2020-08-10 21:24:52.615 NAC: $293
I: 2020-08-10 21:24:52.615 UID Override: no
I: 2020-08-10 21:24:52.615 Self Only: no
I: 2020-08-10 21:24:52.615 Remote Gateway: no
I: 2020-08-10 21:24:52.615 Mode Hang: 10s
M: 2020-08-10 21:24:52.615 MMDVM_Bridge-20200309_V1.5.1 is running
Looks like AMBE audio port issue in AB. Should that be 34100, 34103 ?
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
stop Analog_Bridge and MMDVM_Bridge. remove both logs. start
Analog_Bridge and MMDVM_Bridge. Post both logs.
toggle quoted messageShow quoted text
On 8/10/20 5:21 PM, Tom wrote:
Are these ports correct?
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Are these ports correct?
ASL ( USRP) 32001 RX, 34001 TX AB (USRP) TX 32001, RX 34001 (AMBE AUDIO) 32010 TX , 42020 RX MMDVM (P25 network) Gateway 42020, Local 32010 DVSwitch (P25) TX 34100, RX 34103 P25Gateway Repeater port 32010 Local port 42020 (Network) Port = 42010 __________________________ Should I use my static LAN IP in all the ini files (or loopback)? The reflector on 10888 works; so why doesn't this gateway see it? It's not clear at all where DVSwitch [P25] 34100, 34103 fits in (documentation)? Only ASL talks to Analog_Bridge, then it breaks. Thanks for your help Tom
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
stop Analog_Bridge and MMDVM_Bridge. remove both logs. start
Analog_Bridge and MMDVM_Bridge. Post both logs.
toggle quoted messageShow quoted text
On 8/10/20 4:25 PM, Tom wrote:
Steve,
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Steve,
systemctl status shows all services running (asl, analog_bridge, mmdvm, p25gateway, and p25reflector). ASL talks to analog_bridge, and p25reflector talks to the internet; but nothing else mutually communicates. I believe I have all the ports set correctly. Tom
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
P25eflector works and ASL <-> Analog_Bridge works; but that's all.
Tom
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Here are logs from MMDVM_Bridge, P25Gateway, and P25Reflector:
root@P25reflector:/var/log/mmdvm # tail -f MMDVM_Bridge-2020-08-10.log
I: 2020-08-10 18:14:20.372 Loaded 169853 Ids to the DMR callsign lookup table
I: 2020-08-10 18:14:20.372 P25 RF Parameters
I: 2020-08-10 18:14:20.372 Started the DMR Id lookup reload thread
I: 2020-08-10 18:14:20.372 Id: 3148777
I: 2020-08-10 18:14:20.372 NAC: $293
I: 2020-08-10 18:14:20.372 UID Override: no
I: 2020-08-10 18:14:20.372 Self Only: no
I: 2020-08-10 18:14:20.372 Remote Gateway: no
I: 2020-08-10 18:14:20.372 Mode Hang: 10s
M: 2020-08-10 18:14:20.372 MMDVM_Bridge-20200309_V1.5.1 is running
^C
root@P25reflector:/var/log/mmdvm # tail -f P25Gateway-2020-08-10.log
W: 2020-08-10 17:43:01.267 No response from 10888, unlinking
I: 2020-08-10 18:14:19.459 Opening P25 network connection
I: 2020-08-10 18:14:19.464 Opening P25 network connection
I: 2020-08-10 18:14:19.751 Loaded 13 P25 reflectors
I: 2020-08-10 18:14:19.751 Loaded P25 parrot (TG10)
I: 2020-08-10 18:14:20.223 Loaded 169853 Ids to the callsign lookup table
M: 2020-08-10 18:14:20.223 Starting P25Gateway-20180409
I: 2020-08-10 18:14:20.223 Started the DMR Id lookup reload thread
M: 2020-08-10 18:14:20.223 Linked at startup to reflector 10888
W: 2020-08-10 18:16:20.246 No response from 10888, unlinking
^C
root@P25reflector:/var/log/mmdvm # tail -f P25Reflector-2020-08-10.log
M: 2020-08-10 18:54:20.263 K5TRA (192.168.0.1:42010) 2/120
M: 2020-08-10 18:56:20.265 Currently linked repeaters:
M: 2020-08-10 18:56:20.265 K5TRA (192.168.0.1:1088) 4/120
M: 2020-08-10 18:56:20.265 K5TRA (192.168.0.1:42010) 2/120
M: 2020-08-10 18:56:54.179 Transmission started from K5TRA (192.168.0.1:42010)
M: 2020-08-10 18:56:54.190 Transmission from K5TRA at K5TRA to TG 10888
M: 2020-08-10 18:56:55.098 Received end of transmission
M: 2020-08-10 18:58:20.273 Currently linked repeaters:
M: 2020-08-10 18:58:20.273 K5TRA (192.168.0.1:1088) 4/120
M: 2020-08-10 18:58:20.273 K5TRA (192.168.0.1:42010) 2/120
|
|
|