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: What is an ISPC2 Server?
I have submitted the pull request to HBLink-org
|
|
Re: ircddbgateway to XLX reflector
Patrick Perdue
I thought about that, but there is so much stuff linked to module A, and comparatively few D-STAR users that it is probably easier to just move D-STAR to module B and have those few people reprogram their radios.
toggle quoted messageShow quoted text
D-STAR is one of the least popular modes on my system, the least being WIRES x. I have an analog WIRES x bridge connected using a Yaesu HRI-200 interfaced to a private ASL node. Most are using Allstar.
On 12/13/2021 1:28 AM, Tony Langdon wrote:
Yep sounds like a plan. The main thing is to ensure ircDDBGateway and
|
|
Re: Good morning to all
Take a look at HBlink playback.py
<https://github.com/HBLink-org/hblink3> discussion here
<https://dvswitch.groups.io/g/HBlink>
toggle quoted messageShow quoted text
On 12/13/2021 9:40 AM, Mike AE4ML
wrote:
I hope where I'm posting this is correct.
|
|
Good morning to all
I hope where I'm posting this is correct.
how do I build a Parrot of on the DMR system for local users in our group ? There are issues with Parrot on the network and I would like to keep this as a local device. Possibly just setup a raspberry pi to handle this simple task. I hope. Mike AE4ML
|
|
Re: What is an ISPC2 Server?
DO1KBL, Kim
thx, for groupcall its very nice tool it work without problems
|
|
Re: What is an ISPC2 Server?
There may be more work done on IPSC_Bridge and HB_Bridge still to
come. I'll do some testing.
toggle quoted messageShow quoted text
Steve
On 12/13/2021 9:15 AM, Kim-Benjamin
Lütkemeier via groups.io wrote:
yes Steve
|
|
Re: I'm stumped....
David,
toggle quoted messageShow quoted text
I don't think the dashboard takes STFU into account. I'll look into that for the next update. Steve
On 12/13/2021 9:16 AM, David - W9DWH
via groups.io wrote:
Thanks Steve. It appears I have it working now:
|
|
Re: I'm stumped....
David - W9DWH
Thanks Steve. It appears I have it working now:
● stfu.service - STFU Service
Loaded: loaded (/lib/systemd/system/stfu.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2021-12-13 08:42:19 EST; 25min ago
Process: 510 ExecStartPre=/bin/sh -c echo "Starting STFU: [`date +%T.%3N`]" >> /var/log/netcheck (code=exited, status=0/SUCCESS)
Main PID: 558 (STFU)
Tasks: 3 (limit: 1150)
Memory: 952.0K
CGroup: /system.slice/stfu.service
└─558 /opt/STFU/STFU /opt/MMDVM_Bridge/DVSwitch.ini
Dec 13 08:42:19 dvswitch systemd[1]: Starting STFU Service...
Dec 13 08:42:19 dvswitch systemd[1]: Started STFU Service. I have STFU set for 3104.repeater.net. However the DVS dashboard is still showing me as connected to the Mexico master (which I was using previously). Brandmeister is also still showing me on the Mexico master as well (when I look up my hotspot).
|
|
Re: What is an ISPC2 Server?
DO1KBL, Kim
yes Steve
Unit / Private call is the same, I try to find a solution for this hb_bridge (connected on a hblink3 server) receives corrrectly the Unit call i think it was 0x80 for groupcall and 0x81 for unit-call but ipsc_bridge will transmit as like a groupcall with unit id. Other direction IPSC_Bridge to hblink its not programmed in the def private_call its only print('private call') maybe you have some information about the tlv protocol or its small work for mike he can maybe update it?
|
|
Re: What is an ISPC2 Server?
Is unit call the same as private call? If so, I have not tested it.
I will submit a pull request to HBlink soon.
toggle quoted messageShow quoted text
On 12/13/2021 8:59 AM, Kim-Benjamin
Lütkemeier via groups.io wrote:
It’s unit call support also working in ipsc_bridge / hb_bridge ?
|
|
Re: What is an ISPC2 Server?
DO1KBL, Kim
It’s unit call support also working in ipsc_bridge / hb_bridge ?
toggle quoted messageShow quoted text
Where I can find the pull of this fix ? Von meinem iPhone gesendet
Am 13.12.2021 um 14:28 schrieb Steve N4IRS <szingman@...>:
|
|
Re: What is an ISPC2 Server?
The issue with dual time slots in a HB_Bridge <-> IPSC_Bridge configuration is fixed. It turns out the changed that needed to be made was in dmr_utils, not a bug in DMRlink or HBlink. Mike N4IRR fixed it over the weekend and I'll submit a pull request to HBlink soon.
|
|
Re: General support for all things MMDVM
Kevin Halton
Don’t forget if sending, send it as friends and family so no fees charged.
toggle quoted messageShow quoted text
On Dec 13, 2021, at 8:13 AM, Steve N4IRS <szingman@...> wrote:
|
|
General support for all things MMDVM
Jonathan, G4KLX has posted on the OpenDV group a request for support. Without his work on MMDVM related projects, we would all be a LOT worse off. If you were around pre MMDVM days you know basic things were. Here is a link to his post: A little favour to ask..... We encourage everyone using any of the MMDVM based project to consider Jonathans request.
|
|
Re: ircddbgateway to XLX reflector
Yep sounds like a plan. The main thing is to ensure ircDDBGateway and
toggle quoted messageShow quoted text
xlxd are on different IPs. One little query though is whether it might not be better to move the non D-STAR users, since this could possibly be done a bit more transparently, rather than relying on users to reprogram their radios or remember to change their destination?
On 13/12/21 2:36 pm, Patrick Perdue wrote:
That is exactly what I plan to do -- move D-STAR users to module B,
|
|
Re: ircddbgateway to XLX reflector
Patrick Perdue
That is exactly what I plan to do -- move D-STAR users to module B, and keep all the other digital stuff on module A, then take the XLX transcoder offline. Ideally, this wouldn't be necessary, but as you said, there is no PCM stream from XLXD.
toggle quoted messageShow quoted text
I've got plenty of IP's and network interfaces to play with, no big deal there.
On 12/12/2021 3:47 PM, Tony Langdon wrote:
On 12/12/21 2:24 am, Patrick Perdue wrote:Hi:Unfortunately, the problem here is xlxd itself. The PCM stream isn't
|
|
Re: I'm stumped....
David,
toggle quoted messageShow quoted text
"systemctl start stfu" starts the stfu service in the background. To see if it's tunning: systemctl status stfu To run stfu in the foreground: (Make sure it's not running in the background) cd /opt/STFU ./stfu /opt/MMDVM_Bridge/DVSwitch.ini Steve N4IRS
On 12/12/21 4:30 PM, David - W9DWH via
groups.io wrote:
I'm trying to get STFU up and running. I've installed it and it's present in /opt/STFU. I edited the STFU stanza in dvswitch.ini as follows:
|
|
Re: I'm stumped....
David - W9DWH
I'm trying to get STFU up and running. I've installed it and it's present in /opt/STFU. I edited the STFU stanza in dvswitch.ini as follows:
[STFU] ; Brandmeister Open DMR Terminal (ODMRT) Protocol
BMAddress = 3104.repeater.net ; Brandmeister ODMRT server address
BMPort = 54006 ; Brandmeister ODMRT port
BMPassword = <redacted> ; Your Brandmeister password
Address = 127.0.0.1 ; Address to send AMBE TLV frames to (export)
txPort = 36100 ; Port to send AMBE TLV frames to (export)
rxPort = 36103 ; Port to listen on (import)
UserID = 311898302 ; Your DMR ID + SSID
TalkerAlias = [ASL] ; Max 27 characters
StartTG = 3118983 ; Startup talk group
LogLevel = 3 ; STFU log level (0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error)
If I run systemsctl start stfu I get nothing. It just goes right back to a prompt again. If I change to the STFU directory and try to start in manually ./STFU I get this error: E: 2021-12-12 21:13:26.758 DMR, ini file "DVSwitch.ini" was not found. Fatal error exiting At this point I'm at a loss. I have my Allstar node at home bridged to my DVSwitch in the cloud.
|
|
Re: ircddbgateway to XLX reflector
On 12/12/21 2:24 am, Patrick Perdue wrote:
Hi:Unfortunately, the problem here is xlxd itself. The PCM stream isn't made available to the outside world. The ideal solution is to add USRP support to xlxd, which would allow it to be linked directly to Analog_Reflector, AllStar, etc. Of course, you'd still need both AMBE dongles. I suspect adding USRP would be a complicated undertaking, because of how the transcoding is used dynamically between modules as needed. While there's a lot to like about xlxd, it can also be a pain to integrate into more complex networks. A workaround is to use different modules for D-STAR and DMR/Fusion. Each with its own instance of Analog_Bridge and MMDVM_Bridge, with ircDDBGateway linking to the D-STAR module. Note that you need to use a different IP for ircDDBGateway and xlxd, because both listen on the same ports. I use a variation of this idea for my main multimode reflector. XLX432 D is the D-STAR reflector. Fusion (Same codec as DMR) has its own reflector. -- 73 de Tony VK3JED/VK3IRL http://vkradio.com
|
|
ircddbgateway to XLX reflector
Patrick Perdue
Hi:
I know this isn't a forum for ircddbgateway, but I am trying to get it connected to my XLX reflector on module B. Currently, I have a setup involving XLX with a pair of AMBE dongles, which I set up before implementing ASL and DVSwitch over two years ago. This means there is a second layer of transcoding between Allstar and D-STAR. I want to attach this to an instance of Analog_Bridge, and thus, Analog_Reflector, to remove this layer of transcoding, and free up one of my AMBE dongles in the process. However, I'm not familiar enough with ircddbgateway to really know what I'm doing, and have read so many forum posts that nothing makes sense anymore. If you can help, please feel free to write to me off-list, as this isn't exactly a DVSwitch issue. Thanks and 73 N2DYI
|
|