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: 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:
|
|
Re: bluetooth speaker mic inrico B01
Richard W4JXA
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 experimenting getting a viable hands-free mobile device to work without any success. I have managed to get the received audio thru the Bluetooth, but not TX. Since the vehicles I operate are quite noisy the automatic DSP on a Bluetooth device is really necessary to transmit when moving. Still doesn't help with the PTT problem. I could use the on screen button if it was wasn't so small. PA7LIM David has a nice large PTT on his Peanut application. Put the device in a holder and it's actually possible to use it ever when the trucks are shaking about. W4JXA Richard 73
|
|
Re: bluetooth speaker mic inrico B01
Kenneth Grimard
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 will find the settings for Bluetooth under the application configuration section, but none of it works.
|
|
Re: bluetooth speaker mic inrico B01
Richard W4JXA
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 will find the settings for Bluetooth under the application configuration section, but none of it works.
toggle quoted messageShow quoted text
73 W4JXA Richard
|
|
Re: bluetooth speaker mic inrico B01
g4aqv@...
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 button. I hope this is done at some stage as this is the only thing stopping me taking DV mobile in the car.. Karl G4AQV
|
|
bluetooth speaker mic inrico B01
btp@...
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 Madrid-Spain.
Tony EA4GVR
|
|
Re: DVSwitch Mobile not showing properly on AllStarLink stat page
I got a VERY quick response from AllStarLink. The status page has
been resolved and the bubble chart is being fixed.
toggle quoted messageShow quoted text
A big thanks to the AllStarLink team! Steve N4IRS
On 1/8/2021 2:33 PM, Steve N4IRS via
groups.io wrote:
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 status page and in the bubble chart. I can tell everyone that we did not change anything. From the look of the status pages, something at AllStarLink was changed. I will be reaching out to who I think manages that server to see if I can find out what is going on. Stay tuned.
|
|
DVSwitch Mobile not showing properly on AllStarLink stat page
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 status page and in the bubble chart. I can tell everyone that we did not change anything. From the look of the status pages, something at AllStarLink was changed. I will be reaching out to who I think manages that server to see if I can find out what is going on. Stay tuned.
Steve N4IRS
|
|
Re: Analog audio streaming
fabiobassa
Following this topic 73' s
|
|