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).
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) WHEREAS47 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.
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.
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.
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
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
John,
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
John,
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
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
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
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
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
Thank you for your help Ken. I am a commercial driver have been trying to get a Bluetooth headset and Bluetooth PTT button to work for a long time. A friend of mine in Sydney has also been
Thank you for your help Ken. I am a commercial driver have been trying to get a Bluetooth headset and Bluetooth PTT button to work for a long time. A friend of mine in Sydney has also been
Check the voice call button under the options and it will work with a Bluetooth headset. But not with the inrico mic. I have tried that too. The mic only works with zello
Ken n1dot
Check the voice call button under the options and it will work with a Bluetooth headset. But not with the inrico mic. I have tried that too. The mic only works with zello
Ken n1dot
I have been waiting for the audio opitions to be implemented for a few years now Tony. I only use the Mobile DVSWITCH application. Virginia just started enforcement of handsfree law 01/01/2021. You
I have been waiting for the audio opitions to be implemented for a few years now Tony. I only use the Mobile DVSWITCH application. Virginia just started enforcement of handsfree law 01/01/2021. You
Tony
I have tried this with the mobile DV app but with no avail, I was able to get the RX audio come through the Microphone but no PTT and no audio through the bluetooth mic when i used the Phone PTT
Tony
I have tried this with the mobile DV app but with no avail, I was able to get the RX audio come through the Microphone but no PTT and no audio through the bluetooth mic when i used the Phone PTT
Much appreciated if anyone could guide me to mazke the ptt button work. audio is great but kind of desperate with the ptt function. Maybe it wont work yet? any experiences. Thanks from
Much appreciated if anyone could guide me to mazke the ptt button work. audio is great but kind of desperate with the ptt function. Maybe it wont work yet? any experiences. Thanks from
I got a VERY quick response from AllStarLink. The status page has been resolved and the bubble chart is being fixed.
A big thanks to the AllStarLink team!
Steve N4IRS
I got a VERY quick response from AllStarLink. The status page has been resolved and the bubble chart is being fixed.
A big thanks to the AllStarLink team!
Steve N4IRS
I have received a few direct e-mails asking why we changed the way a DVSM client that was connected to a AllStarLink node. It used to be that the callsign of the connected client was displayed on the
I have received a few direct e-mails asking why we changed the way a DVSM client that was connected to a AllStarLink node. It used to be that the callsign of the connected client was displayed on the