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: DStar Message
Mike,
toggle quoted messageShow quoted text
It is not configurable. Steve N4IRS
On 1/17/21 4:45 PM, Mike, AA9VI via
groups.io wrote:
How do you change the outgoing Dstar message from CALLSIGN /DVSW to something else? (like "Gateway")
|
|
|
|
DStar Message
Mike, AA9VI
How do you change the outgoing Dstar message from CALLSIGN /DVSW to something else? (like "Gateway")
Mike, AA9VI
|
|
|
|
weird audio from P25 to Allstar
Patrick Perdue
Hi:
I just connected my P25 reflector to ASL. Though it is part of a multi-mode system, the P25 instance of Analog_Bridge is connected directly to ASL on it's own private node to avoid transcoding layers. Audio from ASL to P25 is fine, but audio from P25 to ASL has a weird, resonant quality, almost like there are two versions of the PCM stream coming into the node with a very slight delay, less than 10MS, between them. I've never quite encountered anything like this before, so I'm not sure what to look for. There are no duplicates of the USRP RX or TX ports in my rpt.conf. I can't tell if this audio issue is coming into or going out of A_B from M_B. As I said, the audio going in the ASL > P25 direction is perfectly fine. I'm using Analog_Bridge Version 1.6.0 Tue Jan 5 10:11:29 EST. Any help is appreciated.
|
|
|
|
DWSwitch-Server, remote ircddbgateway, ThumbDV
Ryan Collier
Greetings,
I would not get dummyrepeater and ASL to work right. It quit sending traffic to ASL. But ASL can send traffic to DSTAR. So I changed my path. I wanted more capabilities. So, I have DVswitch -server installed. I have ASL TX and RX from dvswitch. I am not running a local ircddbgateway. I all ready have ircddbgateway running my repeater. So I just created a 2nd repeater in ircddbgateway. the port is on gateway address for that port is on 20025. Here is the config I have for that section. [D-Star Network] Enable=1 GatewayAddress=10.0.2.169 GatewayPort=20025 LocalPort=20010 Debug=1 I can not get ircddbgateway to see the connection. So if I run MMDVM_Bridge at the CLI. Here is what I get. What is wrong? I an very confused. I want to get DMR Local 9 linked to DSTAR and use ASL as the connect. But I have to get DSTAR working first. I: 2021-01-15 02:08:39.414 MMDVM_Bridge: I: 2021-01-15 02:08:39.414 Portions Copyright (C) 2018, 2019, 2020 DVSwitch, INAD. I: 2021-01-15 02:08:39.414 Hacks by Mike N4IRR and Steve N4IRS I: 2021-01-15 02:08:39.414 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- I: 2021-01-15 02:08:39.414 This software is for use on amateur radio networks only, I: 2021-01-15 02:08:39.414 it is to be used for educational purposes only. Its use on I: 2021-01-15 02:08:39.415 commercial networks is strictly prohibited. I: 2021-01-15 02:08:39.415 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others M: 2021-01-15 02:08:39.415 MMDVM_Bridge-20201129_V1.6.2 is starting M: 2021-01-15 02:08:39.415 Built 08:55:21 Dec 1 2020 (GitID #89f8998) I: 2021-01-15 02:08:39.415 General Parameters I: 2021-01-15 02:08:39.415 Callsign: KD8TUZ I: 2021-01-15 02:08:39.415 Id: 113969811 I: 2021-01-15 02:08:39.415 Duplex: no I: 2021-01-15 02:08:39.415 Timeout: 180s I: 2021-01-15 02:08:39.415 D-Star: enabled I: 2021-01-15 02:08:39.415 DMR: disabled I: 2021-01-15 02:08:39.415 YSF: disabled I: 2021-01-15 02:08:39.415 P25: disabled I: 2021-01-15 02:08:39.415 NXDN: disabled I: 2021-01-15 02:08:39.415 Modem Parameters I: 2021-01-15 02:08:39.415 Port: /dev/null I: 2021-01-15 02:08:39.415 RX Invert: no I: 2021-01-15 02:08:39.415 TX Invert: no I: 2021-01-15 02:08:39.415 PTT Invert: no I: 2021-01-15 02:08:39.415 TX Delay: 100ms I: 2021-01-15 02:08:39.415 RX Offset: 0Hz I: 2021-01-15 02:08:39.415 TX Offset: 0Hz I: 2021-01-15 02:08:39.415 RX DC Offset: 0 I: 2021-01-15 02:08:39.415 TX DC Offset: 0 I: 2021-01-15 02:08:39.415 RF Level: 100.0% I: 2021-01-15 02:08:39.415 DMR Delay: 0 (0.0ms) I: 2021-01-15 02:08:39.415 RX Level: 50.0% I: 2021-01-15 02:08:39.415 CW Id TX Level: 50.0% I: 2021-01-15 02:08:39.415 D-Star TX Level: 50.0% I: 2021-01-15 02:08:39.415 DMR TX Level: 50.0% I: 2021-01-15 02:08:39.415 YSF TX Level: 50.0% I: 2021-01-15 02:08:39.415 P25 TX Level: 50.0% I: 2021-01-15 02:08:39.415 NXDN TX Level: 50.0% I: 2021-01-15 02:08:39.415 RX Frequency: 442650000Hz (442650000Hz) I: 2021-01-15 02:08:39.415 TX Frequency: 447650000Hz (447650000Hz) M: 2021-01-15 02:08:39.415 Opening the MMDVM I: 2021-01-15 02:08:39.415 Display Parameters I: 2021-01-15 02:08:39.415 Type: I: 2021-01-15 02:08:39.415 D-Star Network Parameters I: 2021-01-15 02:08:39.415 Gateway Address: 10.0.2.169 I: 2021-01-15 02:08:39.415 Gateway Port: 20025 I: 2021-01-15 02:08:39.415 Local Port: 20010 I: 2021-01-15 02:08:39.415 Mode Hang: 3s M: 2021-01-15 02:08:39.415 Opening D-Star network connection I: 2021-01-15 02:08:39.415 RSSI I: 2021-01-15 02:08:39.415 Mapping File: /dev/null I: 2021-01-15 02:08:39.415 Loaded 0 RSSI data mapping points from /dev/null I: 2021-01-15 02:08:39.415 DMR Id Lookups I: 2021-01-15 02:08:39.415 File: /var/lib/mmdvm/DMRIds.dat I: 2021-01-15 02:08:39.415 Reload: 24 hours I: 2021-01-15 02:08:39.606 Loaded 183688 Ids to the DMR callsign lookup table I: 2021-01-15 02:08:39.606 D-Star RF Parameters I: 2021-01-15 02:08:39.606 Module: D I: 2021-01-15 02:08:39.606 Self Only: no I: 2021-01-15 02:08:39.606 Ack Reply: yes I: 2021-01-15 02:08:39.606 Ack Time: 750ms I: 2021-01-15 02:08:39.606 Error Reply: yes I: 2021-01-15 02:08:39.606 Remote Gateway: no I: 2021-01-15 02:08:39.606 Mode Hang: 10s M: 2021-01-15 02:08:39.606 D-Star, Opening INI file: DVSwitch.ini M: 2021-01-15 02:08:39.606 D-Star, Setting [DSTAR] address -> 127.0.0.1 M: 2021-01-15 02:08:39.606 D-Star, Setting [DSTAR] txPort -> 32100 M: 2021-01-15 02:08:39.606 D-Star, Setting [DSTAR] rxPort -> 32103 M: 2021-01-15 02:08:39.606 D-Star, Setting [DSTAR] fallbackID -> 113968 M: 2021-01-15 02:08:39.606 D-Star, Setting [DSTAR] exportTG -> 1977 M: 2021-01-15 02:08:39.606 D-Star, Setting [DSTAR] slot -> 2 M: 2021-01-15 02:08:39.606 D-Star, Setting [DSTAR] RemotePort -> 20010 M: 2021-01-15 02:08:39.606 D-Star, Setting [DSTAR] message -> %location %description M: 2021-01-15 02:08:39.607 D-Star, Transmitting on 127.0.0.1:32100, and listening on port 32103. Result = 1 M: 2021-01-15 02:08:39.607 MMDVM_Bridge-20201129_V1.6.2 is running I: 2021-01-15 02:08:39.607 Started the DMR Id lookup reload thread M: 2021-01-15 02:08:55.265 D-Star, TX state = ON I: 2021-01-15 02:08:55.265 D-Star, Begin TX: src=1139698 rpt=113969811 dst=2 slot=2 cc=1 metadata=KD8TUZ M: 2021-01-15 02:08:56.425 D-Star, TX state = OFF The DSTAR Begin section to me is not right. It looks like it is in DMR format. Everything I find online is DMR not DSTAR. The other thing that is weird. The target is TG not a dstar layout. I want to use one of my starnets. but I can not get that either. Thanks
|
|
|
|
Re: Interface Icom D-Star repeater to DVSwitch?
Ryan Collier
Do you still need help with this issue? I have 2 ICOM repeater stacks running full stack. I have ICOM software installed and running along with ircddbgateway. I do run starnet at STN093_C (Chat). I can help with the process.
|
|
|
|
Re: Hytera DMR Gateway
D B
Ok if I start from scratch? What do you suggest I use to get a system up and running?
the goal is to have several Hyteras linked together. Then I wish to connect a cell phone app to that network AND have the little mmdvm radios connected to it all? I believe some of you have the HYT and the bridge built to the mmdvm and the rest of the world like BM and others? My goal is to start semi small and connect HYT to (????) to mmdvm radios to a tablet or pc or cell phone? So I'm hoping to find some one that has built the wheel and is willing to explain to us all in the simplest terms what we have to do to get it to work? With the more current HYTERA gear or if you have it (ALL) working on older HYT gear what firmware are you using? I can contact HYT and ask engineering for a way to downgrade the firmware back? But would prefer to use current gear. PI computer running IOS (???) Then you need to install (???) this package so you can connect XXX And so on (PLEASE) Thanks
|
|
|
|
Re: Hytera DMR Gateway
Peter M0NWI
1st – this is a volunteer project, no one needs shouting at.
2nd – As I understand it when I last did this some years ago (not had access to a Hytera for a long time!), the DMRGateway binary only converts the Hytera protocol to MMDVM protocol, and so you’ll need to connect that to a bridge, be that DVSwitch Server, HBLink or BM direct. CBridge doesn’t talk MMDVM, so you’d need to convert MMDVM to IPSC using DVSwitch.
From: main@DVSwitch.groups.io <main@DVSwitch.groups.io>
On Behalf Of D B
Sent: 14 January 2021 08:24 To: main@DVSwitch.groups.io Subject: Re: [DVSwitch] Hytera DMR Gateway
Ok gentle men. I watched the video above. I build the jessie light PI as he described. I added the two Hytera gateway folders as he described?
|
|
|
|
Re: Hytera DMR Gateway
The things in video are old. This old gw_hytera_mmdvm was build for FW 8.xx of HYTERA repeater and had some issues with the newer FW 9.xx.
|
|
|
|
Re: Hytera DMR Gateway
D B
If you watched the beginning of the video by Chris? he clearly states using a specific flavor of Jessie_lite because of the other versions having library issues.
|
|
|
|
Re: Hytera DMR Gateway
D B
Ok gentle men. I watched the video above. I build the jessie light PI as he described. I added the two Hytera gateway folders as he described?
(BUT) at the end of his video he quickly mentions a blurb about he connected it to his HP or HB server? My question to all that have a (WORKING) gateway to their Hytera only repeater? but not through any other stuff like BM or cbridge. would you help us all by? Telling us how you personally did it. 1 what flavor of linux. 2 did you use the Hytera GW files from the video ? if not what did you use? 3 is your PI linked either by LAN or WAN to the Hytera directly with out other servers and devices in slave mode? 4 are you using dvswitch / hblink or some other software package? 5 what version of firmware AND what model Hytera are you using? 6 what software are you using on your PC or phone to connect to the mmdvm network? To talk to the network? Please only respond if YOU have a WORKING system! We don't need anyone speculating their thoughts that (MAY OR MAY NOT) work. Thanks I think we all want to tweak the wheel not re invent it from scratch.
|
|
|
|
Re: Hytera DMR Gateway
D B
Whats your JITTER TIME in the repeater? sounds like you need like (8) or more?
|
|
|
|
Re: Location of the P25Gateway
Jay
Just to update, Changing the port does not help. Tested with no firewall.
-- jb N4NQY
|
|
|
|
Re: DVSwitch Mobile App. Hardware
John,
toggle quoted messageShow quoted text
Yes, you can use a Pi Zero. It's on the very low end of functionality. I would really suggest a Pi 3. If you have a Zero now, by all means, try it out. Steve N4IRS
On 1/11/21 6:27 PM, John C wrote:
|
|
|
|
DVSwitch Mobile App. Hardware
John C
All that I’ve seems to point to a need for a PI. In which I’m asking, what would be the minimum PI be, could I use a PI Zero?
Sent from Mail for Windows 10
|
|
|
|
Re: bluetooth speaker mic inrico B01
Richard W4JXA
I have been using 3 different Android devices and 1 PTT dedicated button. Samsung J7 Galaxy Android 7, Samsung J7 Star Android 9, and a Ulefone X5 running Android 10. The PTT button is a Pryme product which someone said would work on DVSwitch. After contacting the technical department at Pryme and having a phone call with them, they had no solution. I have since returned the PTT button. Also have tried 3 different Blueparrott headsets which all have programmable PTT buttons and 3 other necklace types, the most expensive of which is the LG which also has a programmable PTT button. W4JXA Richard 73
|
|
|
|
Re: bluetooth speaker mic inrico B01
Kenneth Grimard
Samsung s20+ Ken
On Sun, Jan 10, 2021, 16:42 Steve N4IRS <szingman@...> wrote:
|
|
|
|
Re: bluetooth speaker mic inrico B01
What Android device?
toggle quoted messageShow quoted text
On 1/10/21 4:36 PM, Kenneth Grimard
wrote:
|
|
|
|
Re: bluetooth speaker mic inrico B01
Kenneth Grimard
We are both trying to get the inrico B01 Bluetooth speaker mic to work with dvswitch android app. It works fine for me with zello Ken
On Sun, Jan 10, 2021, 12:30 Steve N4IRS <szingman@...> wrote:
|
|
|
|
Re: bluetooth speaker mic inrico B01
What PTT button are you trying to use?
toggle quoted messageShow quoted text
On 1/10/21 11:50 AM, Richard W4JXA via
groups.io wrote:
|
|
|
|
Re: bluetooth speaker mic inrico B01
Richard,
toggle quoted messageShow quoted text
What Mobile device are you using?
On 1/10/21 11:50 AM, Richard W4JXA via
groups.io wrote:
|
|
|