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: Dvswitch bridge help
What is not working? Where does it stop?
toggle quoted messageShow quoted text
On 1/4/2019 11:27 AM, Ke4tlc wrote:
Yes I used that document . I did the checks and it looked to me it was correct. I think it is something I am missing.
|
|
|
|
Re: Dvswitch bridge help
Yes I used that document . I did the checks and it looked to me it was correct. I think it is something I am missing.
|
|
|
|
Re: Dvswitch bridge help
What are you trying to accomplish?
toggle quoted messageShow quoted text
If you are using this document <https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg/edit> At each major step you will check your work. Do not continue until you complete the check. Steve N4IRS
On 1/4/2019 10:30 AM, Ke4tlc wrote:
I would like for someone to remote in to my system to try to help me figure out where I went wrong . I followed the steps by steps.. I don't know where to begin to explain.
|
|
|
|
Re: Allstarlink to Echolink showing an error??
Corey Dean N3FE <n3fe@...>
Any chance you are using the allow list in the echolink.conf file? I know if I have the allow list turned on I can't make any outgoing echolink calls, but I can receive incoming. If I comment out the allow line then it works fine in both directions. Isn't this more of an allstar question than a DVswitch question? Corey N3FE
On Fri, Jan 4, 2019 at 11:17 AM <jeff@...> wrote: When Connecting to an Echolink Node Number I receive this message on the console., But the echolink node "does" connect...
|
|
|
|
Allstarlink to Echolink showing an error??
Jeff Wood
When Connecting to an Echolink Node Number I receive this message on the console., But the echolink node "does" connect...
any idea what this error is and how to correct it?? 
|
|
|
|
Dvswitch bridge help
I would like for someone to remote in to my system to try to help me figure out where I went wrong . I followed the steps by steps.. I don't know where to begin to explain.
My email is ke4tlc@....
|
|
|
|
Re: Potential Openbridge usage
Peter M0NWI
To confirm what Corey is saying on sizing, I have ~10 Moto repeaters, a few MMDVM via IPSC_Bridge, and a second IPSC_Bridge for hotspots, plus all the normal LAMP stuff for a web live monitor etc., my VM spec is below;
 I have recently cleared the logs down though!
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Corey Dean N3FE <n3fe@...>
Sent: 04 January 2019 02:55 To: main@dvswitch.groups.io Subject: Re: [DVSwitch] Potential Openbridge usage I am using the minimal single core and 1 gig of ram with 3 different OB connections and many talkgroups at that, some repeaters, and a cbridge ipsc connection and The virtual machine is pretty much sitting idle.
Corey n3fe
On Thu, Jan 3, 2019 at 9:00 PM Bill N2WNS <n2wns.radio@...> wrote:
I'm looking to spin up 2 C-Bridges in two different geographic areas that will have different traffic needs. To ease administration on the upstream the BM/MARC providers, should I implement OB to get the TG traffic, then distribute the traffic from OB to the C-Bridges? What kind of processing power and memory would be required in a virtual environment for such an install?
|
|
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Corey Dean N3FE <n3fe@...>
It sounds like you are pulling the main branch and not the ipsc-Bridge branch.
On Thu, Jan 3, 2019 at 11:02 PM Jason Johnston <kc5hwb@...> wrote: As originally stated, not ALL of the files came down. Some did, some did not. Among those that did not were the *_Bridge files. But the dmrlink-SAMPLE.cfg and such files all came down, along with the directories listed in the repo.
|
|
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Jason Johnston
I think I see what I did wrong and it worked this time. Onward....
|
|
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Jason Johnston
As originally stated, not ALL of the files came down. Some did, some did not. Among those that did not were the *_Bridge files. But the dmrlink-SAMPLE.cfg and such files all came down, along with the directories listed in the repo.
I just removed everything from the /opt folder and I am trying again now.
|
|
|
|
Re: C-Bridge to P25 Reflector Bridge
Michael KD5DFB
So it would look like this? cbridge <-> ipsc_bridge <-> hb_confbridge <-> AB1 <-> AB2 <-> MMDM_bridge Or I guess it could go like this? cbridge <-> ipsc_bridge <-> hb_confbridge <-> MMDM_bridge
On Thu, Jan 3, 2019 at 9:47 PM Steve N4IRS <szingman@...> wrote:
|
|
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
So, which was it? No files came down or 2/3 of the repo? Have
you looked at the branches in question?
toggle quoted messageShow quoted text
On 1/3/19 10:58 PM, Jason Johnston
wrote:
It cloned about 2/3 of the files listed in the github repositories. No errors. I assumed it was by design.
|
|
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Jason Johnston
It cloned about 2/3 of the files listed in the github repositories. No errors. I assumed it was by design.
toggle quoted messageShow quoted text
On Thu, Jan 3, 2019, 9:54 PM Steve N4IRS <szingman@...> wrote:
--
73 de Jason - KC5HWB
|
|
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
no error message? no nothing? Don't know what to tell ya. google
cloning a git branch.
toggle quoted messageShow quoted text
On 1/3/19 10:51 PM, Jason Johnston
wrote:
Nope. I put them in the /opt folder, there were no subdirectories.
|
|
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Jason Johnston
Nope. I put them in the /opt folder, there were no subdirectories.
toggle quoted messageShow quoted text
On Thu, Jan 3, 2019, 9:50 PM Steve N4IRS <szingman@...> wrote:
--
73 de Jason - KC5HWB
|
|
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Did dmrlink and hblink directories already exist?
toggle quoted messageShow quoted text
On 1/3/19 10:45 PM, Jason Johnston
wrote:
I did that already. Not all files came down.
|
|
|
|
Re: C-Bridge to P25 Reflector Bridge
Since you already have a IPSC_Bridge <-> HB_Bridge built
for feeding your MMDVM you may be able to add hb_confbridge. The
get your MMDVM and MMDVM_Bridge connection from there.
toggle quoted messageShow quoted text
On 1/3/19 10:43 PM, KD5DFB wrote:
|
|
|
|
Re: Setting up DMRLink <-> KBLink
#best_practices
#dmrlink
#hblink
Jason Johnston
I did that already. Not all files came down.
toggle quoted messageShow quoted text
On Thu, Jan 3, 2019, 9:28 PM Steve N4IRS <szingman@...> wrote:
--
73 de Jason - KC5HWB
|
|
|
|
Re: C-Bridge to P25 Reflector Bridge
Michael KD5DFB
Can I use confbridge_rules.py to limit it?
On Thu, Jan 3, 2019 at 9:39 PM Steve N4IRS <szingman@...> wrote:
|
|
|
|
Re: C-Bridge to P25 Reflector Bridge
Michael KD5DFB
I guess it could be. I do not own the cbridge and didn't really want to burn another port. Right now both my real repeater and MMDVM connect to the same port
On Thu, Jan 3, 2019 at 9:39 PM Steve N4IRS <szingman@...> wrote:
|
|
|
