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).
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) WHEREAS47 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.
Tom,
The quote below is from my description of using DVM connected directly to Analog_Bridge using the USRP protocol. the flow diagram would look like this:
DVSwitch Mobile <->
Tom,
The quote below is from my description of using DVM connected directly to Analog_Bridge using the USRP protocol. the flow diagram would look like this:
DVSwitch Mobile <->
Hello Steve,
another question related to DVM ... I wasn't aware that I could connect directly DVM <-> Analog_Bridge <-> MMDVM_Bridge <-> DMR. Presumably no need for an ASL node in my cloud instance
Hello Steve,
another question related to DVM ... I wasn't aware that I could connect directly DVM <-> Analog_Bridge <-> MMDVM_Bridge <-> DMR. Presumably no need for an ASL node in my cloud instance
Hi, a group of friends are unifying platforms which we have. So far we have managed to unify some of the platforms but others have not. With success we have managed to see that all HBlink accepts them
Hi, a group of friends are unifying platforms which we have. So far we have managed to unify some of the platforms but others have not. With success we have managed to see that all HBlink accepts them
Supported? Well not really, it's from someone else. I have not built a install package for it. It can be built from source or I think someone has packages available.
Supported? Well not really, it's from someone else. I have not built a install package for it. It can be built from source or I think someone has packages available.
DSTAR<------> <---ircDDBGateway---> <---MMDVM_Bridge------> <-----Analog_Bridge_Dstar.ini----> <----Analog_Bridge_DMR.ini----> <----MMDVM_Bridge<------>DMR
So this is the correct illustration
DSTAR<------> <---ircDDBGateway---> <---MMDVM_Bridge------> <-----Analog_Bridge_Dstar.ini----> <----Analog_Bridge_DMR.ini----> <----MMDVM_Bridge<------>DMR
So this is the correct illustration
Depends on how you're starting the service. If you're using the systemd scripts, this is how I would do it:
Make a copy of the existing AB systemd script, make it identifiable as a different script
cd
Depends on how you're starting the service. If you're using the systemd scripts, this is how I would do it:
Make a copy of the existing AB systemd script, make it identifiable as a different script
cd
Hi guys:
Its me again, This time i am assisting a friend of mines in setting up DStar to DMR link i did some reading and want to make sure i understand the instructions and doing it correctly.
this is
Hi guys:
Its me again, This time i am assisting a friend of mines in setting up DStar to DMR link i did some reading and want to make sure i understand the instructions and doing it correctly.
this is
Gary,
Thanks for the update. Working with the Ohio Link team was a pleasure. The back and forth helped us learn a few things and find a bug or two. I expect the changes will be incorporated
Gary,
Thanks for the update. Working with the Ohio Link team was a pleasure. The back and forth helped us learn a few things and find a bug or two. I expect the changes will be incorporated
Just wanted to give you an update on Ohio Link. Prior to Dayton the DVSwitch team setup a demo bridge as our previous YSF to DMR solution was having some issues. I've been running our own DVSwitch
Just wanted to give you an update on Ohio Link. Prior to Dayton the DVSwitch team setup a demo bridge as our previous YSF to DMR solution was having some issues. I've been running our own DVSwitch
All of that is in /usr/local/bin/ put I put my ini and .sh script there as well.
(same with NXDN)
You must correct the config to reflect that if you choose to do it as
All of that is in /usr/local/bin/ put I put my ini and .sh script there as well.
(same with NXDN)
You must correct the config to reflect that if you choose to do it as
