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 Segmentation Fault on Debian 10 amd64
#mmdvm_bridge
Np problem. It brings up a issue. It is a configuration problem to
have the mode enabled but not the networking. MMDVM_Bridge should
exit gracefully and try to give the user an idea of the problem.
toggle quoted messageShow quoted text
We have a few tweaks happening to the next version of MMDVM_Bridge We can try to cover that in the future. Thanks, Steve
On 3/22/2021 8:05 AM, Kimberly wrote:
Well now, that fixed it. I could have sworn I had that enabled in config, but apparently, there was another one I had to enable. Thanks so much for helping me resolve this puzzling issue! This had me scratching my head for days.
|
|
|
|
Re: #mmdvm_bridge Segmentation Fault on Debian 10 amd64
#mmdvm_bridge
Kimberly (KJ7OMO)
Well now, that fixed it. I could have sworn I had that enabled in config, but apparently, there was another one I had to enable. Thanks so much for helping me resolve this puzzling issue! This had me scratching my head for days.
|
|
|
|
Re: #mmdvm_bridge Segmentation Fault on Debian 10 amd64
#mmdvm_bridge
This is good, getting closer.
toggle quoted messageShow quoted text
Please check you MMDVM_Bridge.ini Verify this is set, if not set it to 1 [DMR Network] Enable=1 Please retest, if you are still getting the error, post your MMDVM_Bridge.ini Thanks, Steve
On 3/22/2021 7:22 AM, Kimberly wrote:
|
|
|
|
Re: #mmdvm_bridge Segmentation Fault on Debian 10 amd64
#mmdvm_bridge
Kimberly (KJ7OMO)
root@localhost:~# cd /opt/MMDVM_Bridge
root@localhost:/opt/MMDVM_Bridge# ./MMDVM_Bridge MMDVM_Bridge.ini
I: 2021-03-22 11:21:26.014 MMDVM_Bridge:
I: 2021-03-22 11:21:26.014 Portions Copyright (C) 2018, 2019, 2020, 2021 DVSwitch, INAD.
I: 2021-03-22 11:21:26.014 Hacks by Mike N4IRR and Steve N4IRS
I: 2021-03-22 11:21:26.014 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2021-03-22 11:21:26.014 This software is for use on amateur radio networks only,
I: 2021-03-22 11:21:26.014 it is to be used for educational purposes only. Its use on
I: 2021-03-22 11:21:26.014 commercial networks is strictly prohibited.
I: 2021-03-22 11:21:26.014 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2021-03-22 11:21:26.014 MMDVM_Bridge-20210223_V1.6.3 is starting
M: 2021-03-22 11:21:26.014 Built 11:40:14 Mar 1 2021 (GitID #bb741c3)
I: 2021-03-22 11:21:26.014 General Parameters
I: 2021-03-22 11:21:26.014 Callsign: KJ7OMO
I: 2021-03-22 11:21:26.014 Id: 316809400
I: 2021-03-22 11:21:26.014 Duplex: no
I: 2021-03-22 11:21:26.014 Timeout: 180s
I: 2021-03-22 11:21:26.014 D-Star: disabled
I: 2021-03-22 11:21:26.014 DMR: enabled
I: 2021-03-22 11:21:26.014 YSF: disabled
I: 2021-03-22 11:21:26.014 P25: disabled
I: 2021-03-22 11:21:26.014 NXDN: disabled
I: 2021-03-22 11:21:26.014 Modem Parameters
I: 2021-03-22 11:21:26.014 Port: /dev/null
I: 2021-03-22 11:21:26.014 RX Invert: no
I: 2021-03-22 11:21:26.014 TX Invert: no
I: 2021-03-22 11:21:26.014 PTT Invert: no
I: 2021-03-22 11:21:26.014 TX Delay: 100ms
I: 2021-03-22 11:21:26.014 RX Offset: 0Hz
I: 2021-03-22 11:21:26.014 TX Offset: 0Hz
I: 2021-03-22 11:21:26.014 RX DC Offset: 0
I: 2021-03-22 11:21:26.014 TX DC Offset: 0
I: 2021-03-22 11:21:26.014 RF Level: 100.0%
I: 2021-03-22 11:21:26.014 DMR Delay: 0 (0.0ms)
I: 2021-03-22 11:21:26.015 RX Level: 50.0%
I: 2021-03-22 11:21:26.015 CW Id TX Level: 50.0%
I: 2021-03-22 11:21:26.015 D-Star TX Level: 50.0%
I: 2021-03-22 11:21:26.015 DMR TX Level: 50.0%
I: 2021-03-22 11:21:26.015 YSF TX Level: 50.0%
I: 2021-03-22 11:21:26.015 P25 TX Level: 50.0%
I: 2021-03-22 11:21:26.015 NXDN TX Level: 50.0%
I: 2021-03-22 11:21:26.015 RX Frequency: 0Hz (0Hz)
I: 2021-03-22 11:21:26.015 TX Frequency: 0Hz (0Hz)
M: 2021-03-22 11:21:26.015 Opening the MMDVM
I: 2021-03-22 11:21:26.015 Display Parameters
I: 2021-03-22 11:21:26.015 Type:
I: 2021-03-22 11:21:26.015 RSSI
I: 2021-03-22 11:21:26.015 Mapping File: /dev/null
I: 2021-03-22 11:21:26.015 Loaded 0 RSSI data mapping points from /dev/null
I: 2021-03-22 11:21:26.015 DMR Id Lookups
I: 2021-03-22 11:21:26.015 File: /var/lib/mmdvm/DMRIds.dat
I: 2021-03-22 11:21:26.015 Reload: 24 hours
I: 2021-03-22 11:21:26.138 Loaded 191386 Ids to the DMR callsign lookup table
I: 2021-03-22 11:21:26.138 DMR RF Parameters
I: 2021-03-22 11:21:26.138 Id: 316809400
I: 2021-03-22 11:21:26.138 Color Code: 1
I: 2021-03-22 11:21:26.138 Self Only: no
I: 2021-03-22 11:21:26.138 Embedded LC Only: yes
I: 2021-03-22 11:21:26.138 Dump Talker Alias Data: no
I: 2021-03-22 11:21:26.138 Prefixes: 0
I: 2021-03-22 11:21:26.138 Call Hang: 4s
I: 2021-03-22 11:21:26.138 TX Hang: 4s
I: 2021-03-22 11:21:26.138 Mode Hang: 10s
M: 2021-03-22 11:21:26.138 DMR, Opening INI file: DVSwitch.ini
M: 2021-03-22 11:21:26.138 DMR, Setting [DMR] address -> 127.0.0.1
M: 2021-03-22 11:21:26.138 DMR, Setting [DMR] txPort -> 31100
M: 2021-03-22 11:21:26.138 DMR, Setting [DMR] rxPort -> 31103
M: 2021-03-22 11:21:26.138 DMR, Setting [DMR] slot -> 2
M: 2021-03-22 11:21:26.138 DMR, Setting [DMR] exportTG -> 0
M: 2021-03-22 11:21:26.138 DMR, Setting [DMR] hangTimerInFrames -> 0
M: 2021-03-22 11:21:26.138 DMR, Setting [DMR] talkerAlias -> %callsign %location %description
M: 2021-03-22 11:21:26.138 DMR, Transmitting on 127.0.0.1:31100, and listening on port 31103. Result = 1
Segmentation fault
root@localhost:/opt/MMDVM_Bridge#
|
|
|
|
Re: #mmdvm_bridge Segmentation Fault on Debian 10 amd64
#mmdvm_bridge
OK,
toggle quoted messageShow quoted text
So it's not segfaulting with -v good! Please make sure MMDVM_Bridge is not running in the background. systemctl stop mmdvm_bridge verify it's stopped ps ax | grep MMDVM If it's stopped cd /opt/MMDVM_Bridge ./MMDVM_Bridge MMDVM_Bridge.ini Show the output.
On 3/22/21 7:04 AM, Kimberly wrote:
|
|
|
|
Re: #mmdvm_bridge Segmentation Fault on Debian 10 amd64
#mmdvm_bridge
Kimberly (KJ7OMO)
root@localhost:~# /opt/MMDVM_Bridge/MMDVM_Bridge -v
MMDVM_Bridge version 20210223_V1.6.3 git #bb741c3
|
|
|
|
Re: Cloud based Dstar Ambe Server Audio Quality
Hello Ken,
for my benefit ... DVS running on cloud server Client (DVSM/PyUC/hUC) running remote (in your vehicle AMBEserver running on RPi at your home DV3000 stanza in AB.ini address = 192.168.x.xxx (IP of AMBEserver on your home Network) correct? Tnx .... Tom VE3NY -- Tom VE3NY
|
|
|
|
Re: #mmdvm_bridge Segmentation Fault on Debian 10 amd64
#mmdvm_bridge
Please show me the output of /opt/MMDVM_Bridge/MMDVM_Bridge -v
toggle quoted messageShow quoted text
On 3/22/21 4:00 AM, Kimberly wrote:
On Sun, Mar 21, 2021 at 03:26 AM, Steve N4IRS wrote:
|
|
|
|
Re: Bridge
As I said, I'm not going to dig through over 100 messages.
toggle quoted messageShow quoted text
1: What are you trying to bridge? 2: What hardware / OS are you running on? Start there.
On 3/22/21 12:26 AM,
ibjosh1985@... wrote:
not looking for some one to do it for me just answer questions i have sent my files , logs and copy and past so the audio bridge file for dmr once launched it says it cannot bind a port but when changing ports it still say's the samething and then i'm getting this Your gatewayDmrId 3174494 is NOT in the subscriber file.
|
|
|
|
Re: #mmdvm_bridge Segmentation Fault on Debian 10 amd64
#mmdvm_bridge
Kimberly (KJ7OMO)
On Sun, Mar 21, 2021 at 03:26 AM, Steve N4IRS wrote:
Kimberly, Ok, I ran the commands you suggested, here is the output: root@localhost:/opt/MMDVM_Bridge# uname -a
Linux localhost 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux
root@localhost:/opt/MMDVM_Bridge# file /opt/MMDVM_Bridge/MMDVM_Bridge
/opt/MMDVM_Bridge/MMDVM_Bridge: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.32, BuildID[sha1]=a0d5832b67656402132de72bf9ecce57320e73e9, with debug_info, not stripped
|
|
|
|
Re: Bridge
Joshua Johnson - KC5JMJ
not looking for some one to do it for me just answer questions i have sent my files , logs and copy and past so the audio bridge file for dmr once launched it says it cannot bind a port but when changing ports it still say's the samething and then i'm getting this Your gatewayDmrId 3174494 is NOT in the subscriber file.
|
|
|
|
Re: Cloud based Dstar Ambe Server Audio Quality
Would anyone in the group with a VPS Cloud installation of Debian 10 Buster running a current DvSwitch install be able to point their VPS Cloud Server to the domain name, and port # of my Zum Ambe Server and let me know how the audio sounds on Dstar and Dmr?
Thanks, Ken
|
|
|
|
Re: Cloud based Dstar Ambe Server Audio Quality
Tom,
Using DVSM on T mobile thru cell towers.
|
|
|
|
Re: Bridge
On Sat, Mar 20, 2021 at 01:42 PM, Steve N4IRS wrote:
So that I don't have to go through 142 messages, what are you trying to do and what is your problem?As far as I can tell, this is an individual who is in over their head with the network port arrangements. Something isn't plumbed together correctly and it's not working. I would insist that we get a diagram from them describing what they think is being configured. If all they provide is log files, that might not be enough to understand/comprehend the data flows properly. My two cents, anyway. --R -- Randy Hall AA6RH (not K7AGE, quit asking) 😁
|
|
|
|
Re: Bridge
On Sat, Mar 20, 2021 at 01:40 PM, <ibjosh1985@...> wrote:
can i get any assistance pleaseI strongly suggest that you spend a bit of time diagramming this in order to make sense of the interconnection between services. I scanned the thread and haven't seen you provide this, and looking at screenshots and copy-pasted logs is not helping right now (i.e. very, VERY hard to read and follow). DV Switch is not an off-the-shelf product that you can just plug in and expect it to work flawlessly. You as an individual user also need to step up and make it a priority to learn how UDP networking functions in the real world. Your questions and responses have shown that you're not quite there (though I'm open to the possibility that you're actually very experienced with UDP and just want someone to do the work for you). UDP sockets can be confusing; go slow and take your time. This is not to be mean-spirited, but you can't reasonably expect someone else to configure your software for you. All we can do is offer suggestions. --R -- Randy Hall AA6RH (not K7AGE, quit asking) 😁
|
|
|
|
Re: #mmdvm_bridge Segmentation Fault on Debian 10 amd64
#mmdvm_bridge
The only reason to do this is if you are running MMDVM_Bridge in
daemon mode. We use systemd so this is not needed.
toggle quoted messageShow quoted text
Steve N4IRS
On 3/21/21 1:03 AM, Lily W. wrote:
|
|
|
|
Re: #mmdvm_bridge Segmentation Fault on Debian 10 amd64
#mmdvm_bridge
Kimberly,
toggle quoted messageShow quoted text
I'll need to see a few things to help determine the cause of the issue. As root, please post the result of the following: uname -a file /opt/MMDVM_Bridge/MMDVM_Bridge Steve N4IRS
On 3/20/21 11:50 PM, Kimberly wrote:
Hello, everyone. I'm having trouble getting MMDVM_Bridge to run on a Debian 10 VPS running the AllstarLink 2.0 Beta 5 image, which is based off Debian 10. Each time I try to run it, it gives me a "Segmentation Fault" error with no other clues to help me determine what went wrong. I tried some solutions out there, but none of them worked for me. Any ideas?
|
|
|
|
Re: #mmdvm_bridge Segmentation Fault on Debian 10 amd64
#mmdvm_bridge
Create a user named “mmdvm”, password mmdvm, and give it write access to /var/log/mmdvm (MMDVM_Bridge needs this to write log files.) I’ve had to manually do that to all of my Quantar_Bridge installs.
From: main@DVSwitch.groups.io [mailto:main@DVSwitch.groups.io] On Behalf Of Kimberly
Hello, everyone. I'm having trouble getting MMDVM_Bridge to run on a Debian 10 VPS running the AllstarLink 2.0 Beta 5 image, which is based off Debian 10. Each time I try to run it, it gives me a "Segmentation Fault" error with no other clues to help me determine what went wrong. I tried some solutions out there, but none of them worked for me. Any ideas?
|
|
|
|
#mmdvm_bridge Segmentation Fault on Debian 10 amd64
#mmdvm_bridge
Kimberly (KJ7OMO)
Hello, everyone. I'm having trouble getting MMDVM_Bridge to run on a Debian 10 VPS running the AllstarLink 2.0 Beta 5 image, which is based off Debian 10. Each time I try to run it, it gives me a "Segmentation Fault" error with no other clues to help me determine what went wrong. I tried some solutions out there, but none of them worked for me. Any ideas?
|
|
|
|
Re: Bridge
So that I don't have to go through 142 messages, what are you trying
to do and what is your problem?
toggle quoted messageShow quoted text
Steve N4IRS
|
|
|