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: YSFn and YSFw
Michael KD5DFB
So if I build a YSF reflector, will both modes work with it? My end goal it to connect it to my P25 reflector
|
|
Re: YSFn and YSFw
Yes,
toggle quoted messageShow quoted text
YSFn is narrow. I do not remember what Yaesu calls it. It uses a AMBE Vocoder (DMR, NXDN). YSFw is wide. It ises a IMBE Vocoder (P25) Steve N4IRS
On 07/15/2018 09:52 PM, KD5DFB wrote:
Okay, I have surfed the internet high and low. I cannot find what the n and w stand for. Is it just as simple as narrowband and wideband?
|
|
YSFn and YSFw
Michael KD5DFB
Okay, I have surfed the internet high and low. I cannot find what the n and w stand for. Is it just as simple as narrowband and wideband?
Michael KD5DFB
|
|
Re: Question....
We have been using the md380-emu. The system been up for a month. It has not missed a beat. Done zero maintenance and is connected to a large linked repeater system with 900+ ppt's per day. You all know the tribulations of and large analog system:) Thanks for all the great work! David KG5RDF
-------- Original message -------- From: Steven Blackford <kb7sqi@...> Date: 7/14/18 5:03 PM (GMT-06:00) To: main@dvswitch.groups.io Subject: Re: [DVSwitch] Question.... Hey Steve, The md380-emu has been rock solid in all the bridges I have running. 73 de K4SQI! Steve, K4SQI On Sat, Jul 14, 2018 at 17:34 Steve Siesel [K4KSA] <steve@...> wrote:
|
|
Re: Question....
Steven Blackford
Hey Steve, The md380-emu has been rock solid in all the bridges I have running. 73 de K4SQI! Steve, K4SQI
On Sat, Jul 14, 2018 at 17:34 Steve Siesel [K4KSA] <steve@...> wrote:
--
|
|
Question....
Steve Siesel [K4KSA]
I am rebuilding my ASL <> Brandmeister bridge…..
Should I continue to use the DV3000 or have you found that emu380 is doing a better job?
Steve K4KSA
|
|
Re: HB_link
Bob kc2cwt
thanks i may have to add a master ,
toggle quoted messageShow quoted text
As i did add the HB-Bridge.cfg file
On 07/12/2018 09:16 PM, Jon K1IMD wrote:
Hi Bob, --
Bob KC2CWT kc2cwt@kc2cwt.net (914)497-5502
|
|
Re: HB_link
Jon K1IMD
Hi Bob,
toggle quoted messageShow quoted text
No or Maybe... If you did nothing to change the TS/TG routing and let the c-Bridge handle the TG "distribution" then no you don't. If you monkeyed with the TG/TS routing then yes and maybe another instance all together. The hotspot or DMO device can act a little wonky handling both TSs. 73 Jon K1IMD
On 7/12/2018 21:01, Bob kc2cwt wrote:
I have HB_link set up for my open spot to the C bridge
|
|
HB_link
Bob kc2cwt
I have HB_link set up for my open spot to the C bridge
Now i what to and a mmdvm repeater do i have to make a new Master . thanks -- Bob KC2CWT kc2cwt@kc2cwt.net (914)497-5502
|
|
Re: DMR <-> P25
Change to AUDIO_USE_GAIN and set the value to less then 1. I would
start with .5 if it's hot and adjust up or down as needed.
toggle quoted messageShow quoted text
Steve
On 07/12/2018 06:49 PM,
va3czk@... wrote:
Hi Steve,
|
|
Re: DMR <-> P25
va3czk@...
Hi Steve,
is there any recommended value for the audio level between DMR and P25 that works best? Getting a little bit of distortion on both sides ? Thanks, J [USRP]
server = 127.0.0.1 ; IP address of Allstar/Asterisk
toASLPort = 34001 ; Analog_Bridge <-- ASL
fromASLPort = 32001 ; Analog_Bridge --> ASL
aslAudio = AUDIO_UNITY ; Audio to ASL (AUDIO_UNITY, AUDIO_USE_AGC, AUDIO_USE_GAIN)
agcGain = -20 ; Gain (in db) of the AGC filter
dmrAudio = AUDIO_UNITY ; Audio from ASL (AUDIO_UNITY, AUDIO_USE_GAIN, AUDIO_BPF)
dmrGain = 0.35 ; Gain factor of audio from ASL (0.0-1.0)
|
|
Re: Allstarling.org Contact
Chris,
toggle quoted messageShow quoted text
My explanation is not in defense of your comment, and I'm not offended. While I don't remember seeing your post or the response to it, that isn't the answer you should have received. As I indicated, there are plenty of things we need to address and make better, and everyone should expect that we'll do just that - over time. Certainly there were instances in the past that our servers had some issues, but a while ago we purchased some new ones, and they've been running for some time - a few months now. I have over 50 nodes publicly registered at ASL, so I know immediately when there are registration issues. Since the upgrade, I've helped troubleshoot and resolve registration problems on several nodes, and none of them were because the ASL server networks were unstable or unreachable. I haven't personally had any registration issues since the upgrade. In closing, currently it's my recommendation that folks post their problems to the app_rpt email list. It's the best place to get answers and resolve to issues pertaining to ASL. Thanks, Kevin W3KKC
On 7/11/2018 6:11 PM, Chris WB4ULK via Groups.Io wrote:
Kevin,
|
|
Re: MMDVM User Authentication
Cort N0MJS <n0mjs@...>
Alright boys… give that a shot.
-- Cort Buffington H: +1-785-813-1501 M: +1-785-865-7206
|
|
Re: Allstarling.org Contact
Kevin,
I'm sorry if I offended you with that light hearted comment. I can only imagine what work goes into keeping this thing up. I was not looking for someone to hold my hand when I wrote an email asking what was going on with the registration server several months ago. I was writing asking about it because the registration server is completely out of my control. The answer I got back did not answer to my question, instead I was told to get a mentor. I took this with a grain of salt and waited the issue out with nothing else said. What else could I do? The comment above was nothing more than a making light of the situation, as I figure with such a tremendous load on whomever is maintaining the system, you are not going to get great explanations sometimes. Again, I am sorry that that offended you. Chris WB4ULK
|
|
Re: DMRLink - bridge streams over writing.
Peter M0NWI
Ah OK, I didn't get that from the config text I was hoping to link pairs or Masters as trunk group, will have to look again. Sent from Outlook From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Cort N0MJS via Groups.Io <n0mjs@...>
Sent: 11 July 2018 20:51:17 To: main@DVSwitch.groups.io Subject: Re: [DVSwitch] DMRLink - bridge streams over writing. Any system you designate as “TRUNK” will become one. There was never a limitation to one. All “TRUNK” does is remove the contention handler completely. I don’t use it a lot, but N3FE who
hangs out on here is kinda the TRUNK guru. If I screw up something with the TRUNK code, Corey is the one who usually finds it first :)
--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206
|
|
Re: DMRLink - bridge streams over writing.
Cort N0MJS <n0mjs@...>
Any system you designate as “TRUNK” will become one. There was never a limitation to one. All “TRUNK” does is remove the contention handler completely. I don’t use it a lot, but N3FE who hangs out on here is kinda the TRUNK guru. If I screw up something with the TRUNK code, Corey is the one who usually finds it first :)
-- Cort Buffington H: +1-785-813-1501 M: +1-785-865-7206
|
|
Re: DMRLink - bridge streams over writing.
Peter M0NWI
Hehe, yes got that after looking at it for a bit, all rebuilt now just under 1000 lines in my config! Swapped over into operation, and seems OK from my limited testing. Best not to tell the users or they'll point out every error, and see if anyone shouts about the crashing TG being fixed? What would have been nice, would have been to have more than one TRUNKS section, is that possible? Thanks Cort.
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io> on behalf of Cort N0MJS via Groups.Io <n0mjs@...>
Sent: 11 July 2018 20:25:54 To: main@DVSwitch.groups.io Subject: Re: [DVSwitch] DMRLink - bridge streams over writing. You just have to switch thinking that the configuration is centered on a group of arbitrarily named “conference bridges”. Each conference bridge is just like a telephone conference bridge
– anyone may “dial into” it. Just think about, for each system (master peer or peer), which TS/TGID combination do you want to be part of a bridge?
I always thought bridge.py was ok, too – but an overwhelming majority had asked for an easier to configure version, and two was a bit too much to keep maintaining :)
--
Cort Buffington
H: +1-785-813-1501
M: +1-785-865-7206
|
|
Re: Shameless Request
DO NOT junk the HSOs I'll take them.
toggle quoted messageShow quoted text
Steve
On 7/11/2018 3:27 PM, Cort N0MJS via
Groups.Io wrote:
I’ll take the PAs and you can junk the rest :)
|
|
Re: Shameless Request
Cort N0MJS <n0mjs@...>
I’ll take the PAs and you can junk the rest :)
-- Cort Buffington H: +1-785-813-1501 M: +1-785-865-7206
|
|
Re: Shameless Request
Cort N0MJS <n0mjs@...>
Oh hell – yes, it would be less expensive to just buy one than to ship one of those monsters – Peter, you’re off the hook for now, but someday I’ll need some trinket you have that weighs less!
-- Cort Buffington H: +1-785-813-1501 M: +1-785-865-7206
|
|