Welcome to DVSwitch
Purpose
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
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: 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
|
|
Re: Analog audio streaming
Hello Chris ... after all this time, have you managed to make an analog web streammer work? ... could you give me a light in that direction?
Thanks!
73's!
|
|
Re: Audio settings and other associated handsfree opitions
Richard W4JXA
I should clarify, I am only using the Android version of the application.
toggle quoted messageShow quoted text
73 W4JXA Richard
|
|
Audio settings and other associated handsfree opitions
Richard W4JXA
A few years ago, when the application was in Beta tester mode, I listened to a presentation about what DVswitch would do. Most of those declared goals have been achieved. However, trying to use this application handsfree is almost impossible. Everything under "AUDIO SOURCE" still says "Not Implemented Yet"
Along with that, the TX screen button is way too small! Peanut, and Zello both have nice large buttons and both have the option to set up a non screen PTT. Great application for certain but please return to the Audio Source opitions and implement them. Otherwise I will only be able to use it for listening, and it's far too great an application to only use for RX 73 W4JXA Richard
|
|
Re: Location of the P25Gateway
Jay
OK, I will change the port number. Daemon=0
[Id Lookup] Name=DMRIds.dat Time=24
[Log] # Logging levels, 0=No logging DisplayLevel=1 FileLevel=1 FilePath=/var/log/P25Reflector/ FileRoot=P25Reflector
[Network] Port=41000 Debug=0
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name udp 0 0 127.0.0.1:323 0.0.0.0:* 460/chronyd udp 0 0 0.0.0.0:42000 0.0.0.0:* 10078/YSFReflector udp 0 0 0.0.0.0:41000 0.0.0.0:* 21879/./P25Reflecto udp 0 0 0.0.0.0:68 0.0.0.0:* 270/dhclient udp6 0 0 ::1:323 :::* 460/chronyd udp6 0 0 fe80::439:2ff:feb2::546 :::* 366/dhclient jb N4NQY
|
|
Re: Location of the P25Gateway
Can I assume you tested it with your hotspot running Pi-Star. Are
you sure you disabled the firewall. I suggest for testing you use
the same port number are 10200 that way you know Pi-Star will allow
the port.
toggle quoted messageShow quoted text
Please post your P25Reflector.ini Please post the output of netstat -unap Steve n4IRS
On 1/6/21 5:20 PM, Jay wrote:
|
|
Re: Location of the P25Gateway
Jay
My Hotspot acts like the Gateway. It shows "Connected to 99539" and in about 3 minutes times out (I guess).
|
|