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: DMR Time out
Joshua Johnson - KC5JMJ
i'm using the hotspot password yes and verified i do have it correct am i suppose to setup an air security password as well
|
|
|
|
Re: DMR Time out
Jeff Lehman, N8ACL
Double check you are using the correct air security password.
it's not your account password for BM, it should be a different
one you have to setup... that's the usual culprit for not
connecting...
On 11/16/21 12:24, Steve N4IRS wrote:
I don't know of any other reports of the problem. Not much else I can tell you.
|
|
|
|
Re: DMR Time out
I don't know of any other reports of the problem. Not much else I
can tell you.
toggle quoted messageShow quoted text
On 11/16/2021 12:23 PM, Joshua Johnson
- KC5JMJ wrote:
the only thing i have tried was changing server's and ping that's it
|
|
|
|
Re: DMR Time out
Joshua Johnson - KC5JMJ
the only thing i have tried was changing server's and ping that's it
|
|
|
|
Re: DMR Time out
So, to save me a number of useless messages, what else did you
already try?
toggle quoted messageShow quoted text
On 11/16/2021 12:17 PM, Joshua Johnson
- KC5JMJ wrote:
did that for both 3102 and 3103 and no time out on the ping for both ran them for an hour
|
|
|
|
Re: DMR Time out
Joshua Johnson - KC5JMJ
did that for both 3102 and 3103 and no time out on the ping for both ran them for an hour
|
|
|
|
Re: DMR Time out
I would log into the server and start a ping to the master. See if
you are loosing a connection.
toggle quoted messageShow quoted text
On 11/16/2021 12:12 PM, Joshua Johnson
- KC5JMJ wrote:
already have went from 3102 to 3103 still the same
|
|
|
|
Re: DMR Time out
Joshua Johnson - KC5JMJ
already have went from 3102 to 3103 still the same
|
|
|
|
Re: DMR Time out
Try a different master
toggle quoted messageShow quoted text
On 11/16/2021 12:08 PM, Joshua Johnson
- KC5JMJ wrote:
dmr keeps timing out and cannot figure out why its doing it
|
|
|
|
DMR Time out
Joshua Johnson - KC5JMJ
dmr keeps timing out and cannot figure out why its doing it
E: 2021-11-16 16:55:41.382 DMR, Connection to the master has timed out, retrying connection M: 2021-11-16 16:55:41.382 DMR, Closing DMR Network M: 2021-11-16 16:55:41.382 DMR, Opening DMR Network M: 2021-11-16 16:55:51.537 DMR, Logged into the master successfully: 74.91.118.251:62031
|
|
|
|
Re: Unable to access DMR via DVSwitch ( #dvs #brandmeister )
#dvs
#brandmeister
That is why I do not use brandmeister 4 DM are I use TGIF. Network for my DM are and I don't have a problem using DV switch on it
On Tue, Nov 2, 2021, 3:35 AM Stefsan <dl1esz@...> wrote: Hi,
|
|
|
|
Re: Unable to access DMR via DVSwitch ( #dvs #brandmeister )
#dvs
#brandmeister
Stefsan
Hi,
i got a info from DK5RAS , the server from DE 2621, 2622 and 2001 will not support DVSwicht devices for big talkgroups (like91) anymore. The reason for that are some obscure problems with software implementations between DVSwich and BM, also perhaps some personal reasons with some users. to This info reaches me via telegram from DK5RAS. Interesting hereby is, this is a german problem (once again), all or most other BM master servers did not restrict users from beeing us of DVSwitch at this time. The workaround to change Master Server to another country as described before is still fine. Id like to share this info with you unfortunally there is no other information from BM according to this intentionally based problem. Maybe it could be a good intention both sides DEV DVS and DEV BM should go into deep discussions to rework problems, it is not a good idea (as happens) here deliberately handle problems at the users back. BR Stefan DL1ESZ
|
|
|
|
Re: install dvswitch
Yes you can. I have it on my repeater. If you want help to set it up e mail me at my email address on QRZ.COM Brad N8PC
On Mon, Nov 1, 2021, 11:34 AM Johnnie Smith <ne5l39437@...> wrote:
|
|
|
|
install dvswitch
Johnnie Smith
Hello, can you install DVSwitch on to the Hamvoip??? And if you can is there a link for help??? ne5l
|
|
|
|
Re: P25 North America reflector
Ok so I’m still a bit lost in all the replies and files... Has a patch/workaround been found for the audio issues? I am still getting garbled transmissions and my log is showing “Overflow in the P25 RF queue” errors. Is there a file that I can upload into my hotspot or some lines of code I need to edit somewhere to fix this issue in my end? Thanks!
|
|
|
|
dvswitch dashboard local activity
pa1gm738@...
after I have updated the dvswitch server the local activity no longer works on the dashboard anyone any idea what the problem could be . everything else works fine also making connections etc . thanks in advance
|
|
|
|
P25 North America Net (?)
Hello all. For those that don’t know me my name is David Coviello, AK4FD. I’ve been working in Public Safety for almost 25 years and am an avid P25 user and fan (I feel the audio quality is superb and second to none)! That being said, to bring more attention to the WONDERFUL digital mode that P25 is, I decided to start a Facebook Page and Group dedicated to the 10200 talkgroup! The fan Page can be found here: P25 TG 10200 (https://www.Facebook.com/TG10200) and the discussion Group can be found here: P25 TG 10200 Group (https://www.Facebook.com/groups/TG10200). The reason for this message is two-fold. A) to let you all know about the pages in case you’d like a place to chat and put faces to the names we chat with, and B) because I would like to start our first P25 North America Net that I would do weekly on Sunday evenings and would like your input and/or support. However I want to clear it with Steve N4IRS first so he doesn’t think I’m hijacking his talkgroup and server. Any comments/questions/suggestions are welcome! You can also private message me on here or using QRZ. 73,
|
|
|
|
Re: Looking for a suggestion bridging BM TG to XLXD (DMR)
Komkit Listisard
it was an existing TG they have for a while.
hblink.log seems okay, nothing jump out at me. Even though it showing I am connected and accepted but when I go to BM dashboard I do not the ID in question show up. There is also no traffic to and from BM to XLXD. INFO 2021-10-26 18:29:17,188 (TGIF) Sending login request to master 74.91.115.118:62031
INFO 2021-10-26 18:29:17,190 (BMUSA) Sending login request to master 162.248.88.117:62031
INFO 2021-10-26 18:29:17,193 (XLX) Sending login request to master 192.168.80.100:62030
INFO 2021-10-26 18:29:17,206 (XLX) Repeater Login ACK Received with 32bit ID: 2881966353
INFO 2021-10-26 18:29:17,210 (TGIF) Repeater Login ACK Received with 32bit ID: 3366612602
INFO 2021-10-26 18:29:17,212 (BMUSA) Repeater Login ACK Received with 32bit ID: 1570304732
INFO 2021-10-26 18:29:17,218 (XLX) Repeater Authentication Accepted
INFO 2021-10-26 18:29:17,219 (XLX) Repeater Configuration Sent
INFO 2021-10-26 18:29:17,230 (XLX) Repeater Configuration Accepted
INFO 2021-10-26 18:29:17,231 (XLX) Connection to Master Completed
INFO 2021-10-26 18:29:17,233 (XLX) Sending XLX Module request
INFO 2021-10-26 18:29:17,234 (TGIF) Repeater Authentication Accepted
INFO 2021-10-26 18:29:17,236 (TGIF) Repeater Configuration Sent
INFO 2021-10-26 18:29:17,238 (BMUSA) Repeater Authentication Accepted
INFO 2021-10-26 18:29:17,239 (BMUSA) Repeater Configuration Sent
INFO 2021-10-26 18:29:17,261 (BMUSA) MSTCL Recieved
INFO 2021-10-26 18:29:17,262 (TGIF) Repeater Configuration Accepted
INFO 2021-10-26 18:29:17,263 (TGIF) Connection to Master Completed
INFO 2021-10-26 18:29:22,194 (BMUSA) Sending login request to master 162.248.88.117:62031
INFO 2021-10-26 18:29:22,216 (BMUSA) Repeater Login ACK Received with 32bit ID: 1570304732
INFO 2021-10-26 18:29:22,240 (BMUSA) Repeater Authentication Accepted I have never looked in the OBP, I may have to look into it. Otherwise MMDVM_Bridge x2 seem to be the answer. Thank you kindly, Kit
|
|
|
|
Re: Looking for a suggestion bridging BM TG to XLXD (DMR)
So,
toggle quoted messageShow quoted text
why does it have to be a 6 digit TG? What HBMonitor shows does not mean much, what does HB log say? What about a OBP connection? If you have to do it with MMDVM_Bridge, do it with 2 instances of MMDVM_Bridge cross connected. Steve N4IRS
On 10/26/21 6:56 PM, Komkit Listisard
via groups.io wrote:
Steve,
|
|
|
|
Re: Looking for a suggestion bridging BM TG to XLXD (DMR)
Komkit Listisard
Steve,
BM would not do that with 6 digits TG to an XLX, we do not have a master server or BM team in our country. DMR repeater is out of the question due to local laws and regulations. So we do not have many options. At any rate, did have HBlink bridged TGIF TG to XLXD no issue at all but try to do the same with BM, my HBmon is showing red/orange in the peer systems displays while TGIF network is green. This should be it or I am missing something: MASTER_IP: BM IP address
MASTER_PORT: 62031
PASSPHRASE: 1234567 (yes, I entered my real passcode in the config)
CALLSIGN: HS0XXX
RADIO_ID: XXXXXXX01
Otherwise I will have to go the longer way by creating a YSF reflector and bridge BM TG using MMDVM_Bridge then again another MMDVM_Bridge from YSF reflector to XLXD 4005. Much longer way but it is what it is. Not sure if that would even work. Thank you kindly, Kit
|
|
|