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: Large analog_bridge.log
The change to fix the log fill and high CPU was a "hot patch" to
Analog_Bridge. I will be building updated apt packages on Monday for
all platforms.
toggle quoted messageShow quoted text
On 5/15/21 9:55 AM, Komkit Listisard
via groups.io wrote:
Steve,
|
|
|
|
Re: Large analog_bridge.log
Komkit Listisard
Steve,
so far so good. The only remain issue is the "P25 Net" never showed up as linked. Most likely is on my dashboard setup. Otherwise all seem to be working now. Any new was change to the Analog_Bridge binary? Again, thank you for the help. 73, Kit
|
|
|
|
Re: Large analog_bridge.log
Komkit Listisard
Okay, P25 is now fixed as well.
All seem well now, both AB does not use much CPU now. Both are now down at the bottom of top -o %CPU Thank you for sticking around and help with the issue. 73, Kit
|
|
|
|
Re: Large analog_bridge.log
Komkit Listisard
Okay, I did that. Brought MB/ABs back up, seem to be okay.
Now seem like my P25 is not working but that probably have nothing to do with it. I have DVSwitch dashboard up for P25, I can see data coming in but hear nothing on the radio and I could not transmit out from P25 side. But as long as my CPU does not goes up and log size does not go up, I am okay for now. Just have to debug the P25 reflector now. 73, Kit
|
|
|
|
Re: Large analog_bridge.log
OK,
toggle quoted messageShow quoted text
Stop ALL instances of AB. cd /tmp wget https://github.com/DVSwitch/Analog_Bridge/raw/master/bin/Analog_Bridge.amd64 chmod +x Analog_Bridge.amd64 mv Analog_Bridge.amd64 Analog_Bridge copy Analog_Bridge over the top of each Analog_Bridge binary. Steve N4IRS
On 5/15/21 8:43 AM, Komkit Listisard
via groups.io wrote:
Linux w3kit-xlx1 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux
|
|
|
|
Re: Large analog_bridge.log
Komkit Listisard
Oh, not all Steve.
No, I do not have any AB running at all. I do not use AB outside of trying to bridge P25 <> DMR. If you wish and do not mind or have time. I can send you the access to my TeamViewer and you can have at it. 73, Kit
|
|
|
|
Re: Large analog_bridge.log
I am not saying you are doing anything wrong. I'm trying to
understand your config. With the MMDVM_Bridge to XLX shut down, how
many instances of AB do you have running?
toggle quoted messageShow quoted text
On 5/15/21 8:41 AM, Komkit Listisard
via groups.io wrote:
No, I do not.
|
|
|
|
Re: Large analog_bridge.log
Komkit Listisard
Linux w3kit-xlx1 4.19.0-14-amd64 #1 SMP Debian 4.19.171-2 (2021-01-30) x86_64 GNU/Linux
|
|
|
|
Re: Large analog_bridge.log
Komkit Listisard
No, I do not.
I was trying to bridge P25 to XLX, I followed you diagram from https://dvswitch.groups.io/g/main/wiki/9379 73, Kit
|
|
|
|
Re: Large analog_bridge.log
Show me the output of uname -a
toggle quoted messageShow quoted text
On 5/15/21 8:37 AM, Komkit Listisard
via groups.io wrote:
Yes, I did - it grew to 200M in no time and CPU went up. My SSH terminals got all sluggish because of the CPU was maxed out.
|
|
|
|
Re: Large analog_bridge.log
With the AB/MB for XLX shut down, Do you have another AB running?
toggle quoted messageShow quoted text
On 5/15/21 8:34 AM, Komkit Listisard
via groups.io wrote:
MB/AB up but logs and CPU are going up.
|
|
|
|
Re: Large analog_bridge.log
Komkit Listisard
Yes, I did - it grew to 200M in no time and CPU went up. My SSH terminals got all sluggish because of the CPU was maxed out.
73, Kit
|
|
|
|
Re: DVSwotch Mobile on Motorola Ion
f0dei
What do you have in config screen ?
|
|
|
|
Re: Large analog_bridge.log
OK, shut it down.
toggle quoted messageShow quoted text
On 5/15/21 8:34 AM, Komkit Listisard
via groups.io wrote:
MB/AB up but logs and CPU are going up.
|
|
|
|
Re: Large analog_bridge.log
Komkit Listisard
MB/AB up but logs and CPU are going up.
73, Kit
|
|
|
|
Re: Large analog_bridge.log
Are you using Analog_Reflector?
toggle quoted messageShow quoted text
On 5/15/21 8:24 AM, Komkit Listisard
via groups.io wrote:
No, not at this time. I disabled it.
|
|
|
|
Re: DVSwotch Mobile on Motorola Ion
Hi,
Got my Motorola ION Yesterday, not set for now. Do not use side PTT, it seems it will trigg the DMR radio... For screen PTT, it should work since i know few OM using it on the ION. Can you try to disable Big PTT in dvswitch config to see what happend. Another thing, try to reconnect to the server. Check connect/hangup on the top of the screen 73 Toufik, F0DEI
|
|
|
|
Re: Large analog_bridge.log
start the MB/AB that is connected to XLX and watch the AB log
toggle quoted messageShow quoted text
On 5/15/21 8:24 AM, Komkit Listisard
via groups.io wrote:
No, not at this time. I disabled it.
|
|
|
|
Re: Large analog_bridge.log
Komkit Listisard
No, not at this time. I disabled it.
I have one instance of MB running but that is for my NXDN which is logged in through BM USA not to my local XLX. My DMR <> XLX and YSF <> XLX are done by BM USA, so basically nothing is logging in directly to XLX. 73, Kit
|
|
|
|
Re: Large analog_bridge.log
So,
toggle quoted messageShow quoted text
Right now, do you have a instance of MB/AB (DMR) logged into the XLX reflector?
On 5/15/21 7:37 AM, Komkit Listisard
via groups.io wrote:
Steve,
|
|
|