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: MMDVM_Bridge to Brandmeister Not working
Jay
Yep, did some checking and Verizon has a big East Coast outage. Maybe that was the issue?? Who knows. Now I can move on.
-- -- jb N4NQY
|
|
Re: MMDVM_Bridge to Brandmeister Not working
I would say that 46% is not good.
toggle quoted messageShow quoted text
On 1/26/2021 3:16 PM, Jay wrote:
|
|
Re: MMDVM_Bridge to Brandmeister Not working
Jay
It started to work. Maybe a network think I am geting 46% packet lass between my cloud server and BM. -- jb N4NQY
|
|
Re: MMDVM_Bridge to Brandmeister Not working
Jay
-- jb N4NQY
|
|
Re: MMDVM_Bridge to Brandmeister Not working
You are sure you have a static TG setup for 315112201? Post
screenshot.
toggle quoted messageShow quoted text
On 1/26/2021 3:06 PM, Jay wrote:
|
|
Re: MMDVM_Bridge to Brandmeister Not working
Jay
I: 2021-01-26 20:04:05.832 MMDVM_Bridge:
I: 2021-01-26 20:04:05.832 Portions Copyright (C) 2018 DVSwitch, INAD.
I: 2021-01-26 20:04:05.832 Hacks by Mike N4IRR and Steve N4IRS
I: 2021-01-26 20:04:05.832 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2021-01-26 20:04:05.832 This software is for use on amateur radio networks only,
I: 2021-01-26 20:04:05.832 it is to be used for educational purposes only. Its use on
I: 2021-01-26 20:04:05.833 commercial networks is strictly prohibited.
I: 2021-01-26 20:04:05.833 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2021-01-26 20:04:05.833 MMDVM_Bridge-20191105_V1.4.1 is starting
M: 2021-01-26 20:04:05.833 Built 14:38:14 Nov 11 2019 (GitID #9dae1ac)
I: 2021-01-26 20:04:05.833 General Parameters
I: 2021-01-26 20:04:05.833 Callsign: N4NQY
I: 2021-01-26 20:04:05.833 Id: 315112201
I: 2021-01-26 20:04:05.833 Duplex: yes
I: 2021-01-26 20:04:05.833 Timeout: 180s
I: 2021-01-26 20:04:05.834 D-Star: disabled
I: 2021-01-26 20:04:05.834 DMR: enabled
I: 2021-01-26 20:04:05.834 YSF: disabled
I: 2021-01-26 20:04:05.834 P25: disabled
I: 2021-01-26 20:04:05.834 NXDN: disabled
I: 2021-01-26 20:04:05.834 Modem Parameters
I: 2021-01-26 20:04:05.834 Port: /dev/null
I: 2021-01-26 20:04:05.834 RX Invert: no
I: 2021-01-26 20:04:05.834 TX Invert: no
I: 2021-01-26 20:04:05.834 PTT Invert: no
I: 2021-01-26 20:04:05.835 TX Delay: 100ms
I: 2021-01-26 20:04:05.835 RX Offset: 0Hz
I: 2021-01-26 20:04:05.835 TX Offset: 0Hz
I: 2021-01-26 20:04:05.835 RX DC Offset: 0
I: 2021-01-26 20:04:05.835 TX DC Offset: 0
I: 2021-01-26 20:04:05.835 RF Level: 100.0%
I: 2021-01-26 20:04:05.835 DMR Delay: 0 (0.0ms)
I: 2021-01-26 20:04:05.835 RX Level: 50.0%
I: 2021-01-26 20:04:05.835 CW Id TX Level: 50.0%
I: 2021-01-26 20:04:05.835 D-Star TX Level: 50.0%
I: 2021-01-26 20:04:05.835 DMR TX Level: 50.0%
I: 2021-01-26 20:04:05.836 YSF TX Level: 50.0%
I: 2021-01-26 20:04:05.836 P25 TX Level: 50.0%
I: 2021-01-26 20:04:05.836 NXDN TX Level: 50.0%
I: 2021-01-26 20:04:05.836 RX Frequency: 443900000Hz (443900000Hz)
I: 2021-01-26 20:04:05.836 TX Frequency: 448900000Hz (448900000Hz)
M: 2021-01-26 20:04:05.836 Opening the MMDVM
I: 2021-01-26 20:04:05.836 Display Parameters
I: 2021-01-26 20:04:05.836 Type:
I: 2021-01-26 20:04:05.836 DMR Network Parameters
I: 2021-01-26 20:04:05.836 Address: 3102.repeater.net
I: 2021-01-26 20:04:05.837 Port: 62031
I: 2021-01-26 20:04:05.837 Local: 62032
I: 2021-01-26 20:04:05.837 Jitter: 500ms
I: 2021-01-26 20:04:05.837 Slot 1: disabled
I: 2021-01-26 20:04:05.837 Slot 2: enabled
I: 2021-01-26 20:04:05.837 Mode Hang: 3s
I: 2021-01-26 20:04:05.873 Info Parameters
I: 2021-01-26 20:04:05.873 Callsign: N4NQY
I: 2021-01-26 20:04:05.873 RX Frequency: 443900000Hz
I: 2021-01-26 20:04:05.873 TX Frequency: 448900000Hz
I: 2021-01-26 20:04:05.874 Power: 1W
I: 2021-01-26 20:04:05.874 Latitude: 37.630001deg N
I: 2021-01-26 20:04:05.874 Longitude: -77.300003deg E
I: 2021-01-26 20:04:05.874 Height: 0m
I: 2021-01-26 20:04:05.874 Location: "Hanover, VA"
I: 2021-01-26 20:04:05.874 Description: "MMDVM_DMRF"
I: 2021-01-26 20:04:05.874 URL: "https://groups.io/g/DVSwitch"
M: 2021-01-26 20:04:05.874 DMR, Opening DMR Network
I: 2021-01-26 20:04:05.875 RSSI
I: 2021-01-26 20:04:05.875 Mapping File: RSSI.dat
W: 2021-01-26 20:04:05.875 Cannot open the RSSI data file - RSSI.dat
I: 2021-01-26 20:04:05.875 DMR Id Lookups
I: 2021-01-26 20:04:05.875 File: /var/lib/mmdvm/DMRIds.dat
I: 2021-01-26 20:04:05.875 Reload: 24 hours
I: 2021-01-26 20:04:06.150 Loaded 182247 Ids to the DMR callsign lookup table
I: 2021-01-26 20:04:06.151 DMR RF Parameters
I: 2021-01-26 20:04:06.151 Id: 315112201
I: 2021-01-26 20:04:06.151 Color Code: 1
I: 2021-01-26 20:04:06.151 Self Only: no
I: 2021-01-26 20:04:06.151 Embedded LC Only: yes
I: 2021-01-26 20:04:06.152 Dump Talker Alias Data: no
I: 2021-01-26 20:04:06.152 Prefixes: 0
I: 2021-01-26 20:04:06.152 Call Hang: 3s
I: 2021-01-26 20:04:06.152 TX Hang: 3s
I: 2021-01-26 20:04:06.152 Mode Hang: 10s
M: 2021-01-26 20:04:06.152 DMR, Opening INI file: DVSwitch.ini
M: 2021-01-26 20:04:06.153 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2021-01-26 20:04:06.153 DMR, Setting [DMR] TXPort -> 31100
M: 2021-01-26 20:04:06.153 DMR, Setting [DMR] RXPort -> 31103
M: 2021-01-26 20:04:06.153 DMR, Setting [DMR] Slot -> 2
M: 2021-01-26 20:04:06.153 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103. Result = 1
M: 2021-01-26 20:04:06.153 MMDVM_Bridge-20191105_V1.4.1 is running
I: 2021-01-26 20:04:06.154 Started the DMR Id lookup reload thread
D: 2021-01-26 20:04:16.192 DMR, Sending authorisation
D: 2021-01-26 20:04:16.228 DMR, Sending configuration
M: 2021-01-26 20:04:16.264 DMR, Logged into the master successfully
-- jb N4NQY
|
|
Re: MMDVM_Bridge to Brandmeister Not working
Show me the complete startup of MB when you run it from the
commandline.
toggle quoted messageShow quoted text
On 1/26/2021 2:58 PM, Jay wrote:
oh yes, several times and the traffic is heard on the BM Last Heard. The TG I am keying is a Group Call to my ID, which is a Static TG on the ID(+suffix) used for the MB. I double checked the INI file to be sure of the "Hotspot" ID. The MB is running on a cloud server with the Firewall Temporarily disabled.
|
|
Re: MMDVM_Bridge to Brandmeister Not working
Jay
oh yes, several times and the traffic is heard on the BM Last Heard. The TG I am keying is a Group Call to my ID, which is a Static TG on the ID(+suffix) used for the MB. I double checked the INI file to be sure of the "Hotspot" ID. The MB is running on a cloud server with the Firewall Temporarily disabled.
-- jb N4NQY
|
|
Re: MMDVM_Bridge to Brandmeister Not working
When you say, nothing past that, did you try to send traffic from
DMR to the static TG?
toggle quoted messageShow quoted text
On 1/26/2021 2:50 PM, Jay wrote:
Yep, last entry was "DMR, Logged into the master successfully" nothing pass that except the exit, when I stopped it (I was running it from the command line)
|
|
Re: MMDVM_Bridge to Brandmeister Not working
Jay
Yep, last entry was "DMR, Logged into the master successfully" nothing pass that except the exit, when I stopped it (I was running it from the command line)
No errors show during the startup. -- jb N4NQY
|
|
Re: MMDVM_Bridge to Brandmeister Not working
Check the MB log?
toggle quoted messageShow quoted text
On 1/26/2021 2:28 PM, Jay wrote:
I have an MB that connects/Logs In to BM. I hear nothing. To test the problem I made my ID a static TG on the HOTSPOT ID being used for the MB.
|
|
MMDVM_Bridge to Brandmeister Not working
Jay
I have an MB that connects/Logs In to BM. I hear nothing. To test the problem I made my ID a static TG on the HOTSPOT ID being used for the MB.
If I transmit a Group Call to the BM, it appears on Last Heard, but the MB sees nothing. No keyup, no audio. I search Groups.io but nothing struck me as matching,. Any ideas?? -- -- jb N4NQY
|
|
Re: Problems with 4G connections
Michael KD5DFB
Thanks Steve!
|
|
Re: Setup of a Bridge YSF to DMR - Anyone out there who can solve this mystery ?
#mmdvm_bridge
KC1JFN
Hi, I have the same set up with Uli, both RPI running on raspbian stretch lite on the same network. I did what Steve told Uli to do by pointing MMDVM_Bridge at the 2 systems you want to bridge. But it does not work. I am a newbie with regards to this things.
Is it only on MMDVm_Bridge.ini that I have to change? What does it mean by GatewayAddress=ysfreflector.dvswitch.org <-------- point this at the YSF reflector? The ip address to the YSF Reflector is, My public ip? I downloaded this from YSF Reflector registry 07854;US-ICARE-Iloilo;ICARE Iloilo;32.214.141.124;42002;001;http://ic6008.com/Dashboard This is what I put in GatewayAddress=32.214.141.124 GatewayPort=42002 Please help, Thank you
|
|
Can't connect to TG 3149
Roger Davies
Hi All,
For some reason, I can't connect to my state talk group 3149 (Utah) with DVSwitch Mobile. or pyUC. The connection has worked in the past. I see the DVS dashboard light up telling me that I talking on 3149, but can't hear the repeater keyup while listening on a radio (I'm in range of the repeater). When there is traffic on 3149 on the repeater, I don't hear it with DVSwitch. I can hear and talk on other talk groups, with DVS, with no problems. When I connect to 3149 with a pi-star hotspot, it works fine, meaning the repeater keys up but not hearing anything on DVS. Things I've tried: Updated DVSwitch Mobile to the latest version. Updated DVSwitch using the menu option. I've tried all I can think to fix this issue. I'm not sure where the talk group database is on DVS. Could there be an error in that database file? Any help would be greatly appreciated. 73, Roger - N6DVZ
|
|
Re: Problems with 4G connections
Mike,
toggle quoted messageShow quoted text
I misspoke, correction below. Thank you for a good answer. There is a option in DVSM to reduce the bandwidth used. In the account there is an option to select a lower bandwidth codec. The option is codec types. The best quality is slin (default) I suggest you try ADPCM first (worst quality) if that works, go up to uLaw (mid quality) and see if that works. Hope this helps, Steve N4IRS
On 1/24/21 1:43 PM, Michael KD5DFB
wrote:
I had a similar issue with my Inrico T320. I was using a service provider that was a reseller for T-mobile. I downloaded a speed test app and did some testing and found my download speed was .1 mbps and upload was .5 mbps. After going back and forth with them over support emails, I found out that the plan I was using was being throttled to basically 64 kbps up and down. Obviously that is not enough to reliably run the app.
|
|
Re: Problems with 4G connections
Mike,
toggle quoted messageShow quoted text
Thank you for a good answer. There is a option in DVSM to reduce the bandwidth used. In the account there is an option to select a lower bandwidth codec. The option is codec types. The best quality is ulaw (default) I suggest you try slin first (worst quality) if that works, go up to ADPCM (mid quality) and see if that works. Hope this helps, Steve N4IRS
On 1/24/21 1:43 PM, Michael KD5DFB
wrote:
I had a similar issue with my Inrico T320. I was using a service provider that was a reseller for T-mobile. I downloaded a speed test app and did some testing and found my download speed was .1 mbps and upload was .5 mbps. After going back and forth with them over support emails, I found out that the plan I was using was being throttled to basically 64 kbps up and down. Obviously that is not enough to reliably run the app.
|
|
Re: Problems with 4G connections
Michael KD5DFB
I had a similar issue with my Inrico T320. I was using a service provider that was a reseller for T-mobile. I downloaded a speed test app and did some testing and found my download speed was .1 mbps and upload was .5 mbps. After going back and forth with them over support emails, I found out that the plan I was using was being throttled to basically 64 kbps up and down. Obviously that is not enough to reliably run the app.
I ended up going directly to T-mobile to get the service thru their pre-paid plans. That fixed the issue. Getting 10+- mbps up and down now. Hope this might help. Michael KD5DFB
|
|
I need some Help!!!
Steve Siesel [K4KSA]
Steve and the group…
I inadvertently I believe updated my asterisk....below is what is on the screen when I log into astersisk…. Is there a good way to get back to a good version of ASL? I posted here because I use Analog Bridge and MMDVM Bridge as well. I know it’s a new version because the “rpt” command is not there…
== Parsing '/etc/asterisk/asterisk.conf': Found Connected to Asterisk GIT Version adaec47 currently running on dmrlink (pid = 551) Verbosity is at least 10 dmrlink*CLI>
and my directory structure seems to be in place as well
4 drwxr-xr-x 4 root root 4096 Dec 30 11:19 . 4 drwxr-xr-x 92 root root 4096 Nov 20 10:31 .. 4 drwxr-xr-x 2 root root 4096 Jul 14 2018 2018-07-14 4 -rw-r--r-- 1 root root 345 Jul 14 2018 allmon.ini.php 4 -rw-r--r-- 1 root root 767 Feb 26 2018 amd.conf 4 -rw-r--r-- 1 root root 1989 Feb 26 2018 asterisk.conf 4 -rw-r--r-- 1 root root 520 Feb 26 2018 beagle.conf 24 -rw-r--r-- 1 root root 24035 Feb 26 2018 chan_dahdi.conf 4 drwxr-xr-x 2 root root 4096 Mar 18 2018 custom 4 -rw-r--r-- 1 root root 205 Feb 26 2018 dnsmgr.conf 4 -rw-r--r-- 1 root root 107 Feb 26 2018 dundi.conf 4 -rw-r--r-- 1 root root 1978 Jul 22 2018 echolink.conf 8 -rw-r--r-- 1 root root 5542 Dec 30 11:19 extensions.conf 8 -rw-r--r-- 1 root root 4741 Jul 14 2018 extensions.conf.old 4 -rw-r--r-- 1 root root 376 Feb 26 2018 features.conf 4 -rw-r--r-- 1 root root 1505 Feb 26 2018 gps.conf 8 -rw-r--r-- 1 root root 4538 Dec 30 11:17 iax.conf 8 -rw-r--r-- 1 root root 4503 Feb 26 2018 indications.conf 4 -rw-r--r-- 1 root root 341 Feb 26 2018 logger.conf 4 -rw-r--r-- 1 root root 3762 Jul 14 2018 manager.conf 16 -rw-r--r-- 1 root root 13779 Jul 14 2018 modules.conf 4 -rw-r--r-- 1 root root 2958 Feb 26 2018 pi.conf 8 -rw-r--r-- 1 root root 7090 Feb 26 2018 pi-dsp.conf 4 -rw-r--r-- 1 root root 2981 Feb 26 2018 pi-nodsp.conf 0 -rw-r--r-- 1 root root 0 Feb 26 2018 pi_tune_1.conf 0 -rw-r--r-- 1 root root 0 Feb 26 2018 pi_tune_2.conf 4 -rw-r----- 1 root root 244 Feb 26 2018 res_snmp.conf 8 -rw-r--r-- 1 root root 6916 Dec 30 11:16 rpt.conf 28 -rw-r--r-- 1 root root 27782 Jul 14 2018 rpt.conf.old 4 -rw-r--r-- 1 root root 80 Jul 14 2018 savenode.conf 4 -rw-r--r-- 1 root root 2584 Jul 14 2018 simpleusb.conf 0 -rw-r--r-- 1 root root 0 Feb 26 2018 simpleusb_tune_usb_1999.conf 0 -rw-r--r-- 1 root root 0 Jul 14 2018 simpleusb_tune_usb_46031.conf 4 -rw-r--r-- 1 root root 601 Feb 26 2018 sip.conf 4 -rw-r--r-- 1 root root 556 Feb 26 2018 tlb.conf 8 -rw-r--r-- 1 root root 5021 Jul 14 2018 usbradio.conf 0 -rw-r--r-- 1 root root 0 Feb 26 2018 usbradio_tune_usb_1999.conf 0 -rw-r--r-- 1 root root 0 Jul 14 2018 usbradio_tune_usb_46031.conf 4 -rw-r--r-- 1 root root 2285 Jul 14 2018 voter.conf
Steve K4KSA
|
|
Problems with 4G connections
I notice that my connections on 4G drop out very often, while the GSM masts are visible from a distance. Receiving is not a problem, but broadcasts often drop out or crumbling sound. Is there anything to do about this? I have no problems with this with Zello. I have an Inrico T320 with android 7.0
|
|