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
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
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
When I tail -f /var/log/dvswitch/Analog_Bridge.log I see PTT on and PTT off response
In /var/log/mmdvm, when I tail -f the MMDVM_Bridge log I don't see any responses from AB: 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
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
One step at a time. Get AB talking to ASL. You should be able to see
the traffic from ASL to AB.
toggle quoted messageShow quoted text
This is an ASL <-> DMR document. The concepts are the same. It's old (needs updating) so toy will see toDMR etc but the concept is the same. You: ASL <-> AB <-> MB <-> P25Gateway Document <ASL <-> AB <-> MB <https://dvswitch.groups.io/g/allstarlink/files/ASL%20to%20DMR%20Bridge.pdf>
On 8/10/2020 1:47 PM, Tom wrote:
Any tips on monitoring / verifying those data connections?
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Any tips on monitoring / verifying those data connections?
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
reboot did it! ASL is OK.
Now I'll work on the analog_bridge path to the reflector. Thanks! I'll keep you posted on progress. Tom
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Yes, it looks like it is on the network. I checked the external nodes file on another box.
The remaining problem is to get that file to get updates on this server. I'll try a reboot.
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Do this as root so that you don't have to rebuild DAHDI again:
toggle quoted messageShow quoted text
apt-mark hold raspberrypi-kernel-headers raspberrypi-kernel You will then be able to do a apt-get update / apt-get upgrade without need ing to rebuild DAHDI. Steve
On 8/10/2020 1:22 PM, Tom wrote:
It looks like ASL is running; but this node 46715 isn't in the external nodes list (not registered). -- can't connect.
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
toggle quoted messageShow quoted text
On 8/10/2020 1:22 PM, Tom wrote:
It looks like ASL is running; but this node 46715 isn't in the external nodes list (not registered). -- can't connect.
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Is 46715 the node you are working on now?
toggle quoted messageShow quoted text
On 8/10/2020 1:22 PM, Tom wrote:
It looks like ASL is running; but this node 46715 isn't in the external nodes list (not registered). -- can't connect.
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
It looks like ASL is running; but this node 46715 isn't in the external nodes list (not registered). -- can't connect.
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
root@K5TRA_ASL_testserver:/etc/asterisk # dahdi_scan
[1]
active=yes
alarms=UNCONFIGURED
description=DAHDI_DUMMY/1 (source: HRtimer) 1
name=DAHDI_DUMMY/1
manufacturer=
devicetype=DAHDI Dummy Timing
location=
basechan=1
totchans=0
irq=0
root@K5TRA_ASL_testserver:/etc/asterisk # dahdi_test -c 10
Opened pseudo dahdi interface, measuring accuracy...
99.986% 99.944% 99.959% 99.958% 99.992% 99.993% 99.992% 99.993%
99.991% 99.991%
--- Results after 10 passes ---
Best: 99.993% -- Worst: 99.944% -- Average: 99.979834%
Cumulative Accuracy (not per pass): 99.980 chan_dahdi.conf was missing; but it's there now. simpleusb and usbradio are loaded in modules; but I will fix that (focused on dahdi now).
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Show output:
toggle quoted messageShow quoted text
dahdi_scan dahdi_test -c 10
On 8/10/2020 12:59 PM, Tom wrote:
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Do you have chan_dahdi.conf in /etc/asterisk?
toggle quoted messageShow quoted text
Do you have simple usb and usbradio enabled on /etc/asterisk/modules?
On 8/10/2020 12:32 PM, Tom wrote:
.[Aug 10 11:21:52] ERROR[13888]: chan_dahdi.c:11711 setup_dahdi: Unable to load chan_dahdi.conf
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
root@K5TRA_ASL_testserver:/usr/src # lsmod | grep dahdi
dahdi_dummy 3432 0
dahdi 229497 1 dahdi_dummy
crc_ccitt 1771 1 dahdi
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
lsmod | grep dahdi
toggle quoted messageShow quoted text
Show result. Did you do a apt-get update / apt-get upgrade since starting ASL?
On 8/10/2020 12:32 PM, Tom wrote:
Steve,
|
|
|
|
Re: ASL to P25 bridge
#analog_bridge
Steve,
Last night I installed everything and ran into a problem with ASLerrors. Today, I started with a known good ASL install and overlayed the DVSwitch stuff. No errors on installs. This is the closest to working so far. I'm now having a dahdi related error on ASL startup. I did do a /usr/src/asl-dahdi-linux-2.11.1 make (no errors) and make install (no errors). Here's what I get from asterisk -cv : [ Initializing Custom Configuration Options ] [Aug 10 11:21:52] NOTICE[13888]: dnsmgr.c:394 do_reload: Managed DNS entries will be refreshed every 300 seconds.
[Aug 10 11:21:52] NOTICE[13888]: cdr.c:1416 do_reload: CDR simple logging enabled.
[Aug 10 11:21:52] NOTICE[13888]: loader.c:874 load_modules: 56 modules will be loaded.
............[Aug 10 11:21:52] ERROR[13888]: chan_dahdi.c:11711 setup_dahdi: Unable to load chan_dahdi.conf
...[Aug 10 11:21:52] NOTICE[13888]: chan_simpleusb.c:4242 load_module: Unable to load config simpleusb.conf
[Aug 10 11:21:52] NOTICE[13888]: chan_usbradio.c:5790 load_module: Unable to load config usbradio.conf
....[Aug 10 11:21:52] ERROR[13888]: codec_dahdi.c:432 find_transcoders: Failed to open /dev/dahdi/transcode: No such file or directory Tom
|
|
|
|
Re: DMRIds.dat not updating
Thank you, I found it after I made the post thank you for responding. 73.
|
|
|