Date   

Re: MMDVM_Bridge not sending to NXDNGateway

Steve N4IRS
 

Do you have an entry for 31360 in /var/lib/mmdvm/private_NXDNHosts.txt

On 1/27/20 8:23 PM, Bill N2WNS wrote:
I tried to add them as TXT attachments and they wouldn't post. Here they are:

*********MMDVM_Bridge*********

[General]
Callsign=KC2CWT
Id=3136187
Timeout=180
Duplex=0

[Info]
RXFrequency=222340000
TXFrequency=224940000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Tristate2NXDN Bridge
Description=MMDVM_Bridge
URL=https://groups.io/g/DVSwitch

[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=2
FilePath=/opt/TriState_NXDN/MMDVM_Bridge/log
FileRoot=MMDVM_Bridge

[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24

[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24

[Modem]
Port=/dev/null
RSSIMappingFile=RSSI.dat
Trace=0
Debug=0

[D-Star]
Enable=0
Module=C

[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=0
DumpTAData=0

[System Fusion]
Enable=0

[P25]
Enable=0
NAC=293

[NXDN]
Enable=1
RAN=1
Id=34001

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0

[DMR Network]
Enable=1
Address=REMOVED
Port=REMOVED
Jitter=360
Local=61085
Password=REMOVED
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=0
Slot2=1
Debug=0

[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=ysfreflector.dvswitch.org
GatewayPort=42166
Debug=0

[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0

[NXDN Network]
Enable=1
#LocalAddress=127.0.0.1
Debug=1
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020


*************NXDNGateway***********

[General]
Callsign=N2WNS
Suffix=NXDN
RptAddress=127.0.0.1
RptPort=14021
LocalPort=14020
Debug=0
Daemon=0

[Info]
RXFrequency=430475000
TXFrequency=439475000
Power=1
Latitude=0.0
Longitude=0.0
Height=0
Name=Nowhere
Description=Multi-Mode Repeater

[Voice]
Enabled=0
Language=en_US
Directory=./Audio

[aprs.fi]
Enable=0
# Server=noam.aprs2.net
Server=euro.aprs2.net
Port=14580
Password=9999
Description=APRS Description
Suffix=N

[Id Lookup]
Name=/var/lib/mmdvm/NXDN.csv
Time=24

[Log]
FilePath=/opt/TriState_NXDN/NXDNGateway/log
FileRoot=NXDNGateway

[Network]
Port=14050
HostsFile1=/opt/TriState_NXDN/NXDNGateway/NXDNHosts.txt
HostsFile2=/var/lib/mmdvm/private_NXDNHosts.txt
ReloadTime=60
ParrotAddress=127.0.0.1
ParrotPort=42021
NXDN2DMRAddress=127.0.0.1
NXDN2DMRPort=42022
Startup=31360
InactivityTimeout=0
Debug=0

[Mobile GPS]
Enable=0
Address=127.0.0.1
Port=7834



Re: MMDVM_Bridge not sending to NXDNGateway

Bill N2WNS
 

I tried to add them as TXT attachments and they wouldn't post. Here they are:

*********MMDVM_Bridge*********

[General]
Callsign=KC2CWT
Id=3136187
Timeout=180
Duplex=0

[Info]
RXFrequency=222340000
TXFrequency=224940000
Power=1
Latitude=41.7333
Longitude=-50.3999
Height=0
Location=Tristate2NXDN Bridge
Description=MMDVM_Bridge
URL=https://groups.io/g/DVSwitch

[Log]
# Logging levels, 0=No logging, 1=Debug, 2=Message, 3=Info, 4=Warning, 5=Error, 6=Fatal
DisplayLevel=1
FileLevel=2
FilePath=/opt/TriState_NXDN/MMDVM_Bridge/log
FileRoot=MMDVM_Bridge

[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat
Time=24

[NXDN Id Lookup]
File=/var/lib/mmdvm/NXDN.csv
Time=24

[Modem]
Port=/dev/null
RSSIMappingFile=RSSI.dat
Trace=0
Debug=0

[D-Star]
Enable=0
Module=C

[DMR]
Enable=1
ColorCode=1
EmbeddedLCOnly=0
DumpTAData=0

[System Fusion]
Enable=0

[P25]
Enable=0
NAC=293

[NXDN]
Enable=1
RAN=1
Id=34001

[D-Star Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=20010
LocalPort=20011
Debug=0

[DMR Network]
Enable=1
Address=REMOVED
Port=REMOVED
Jitter=360
Local=61085
Password=REMOVED
# for DMR+ see https://github.com/DVSwitch/MMDVM_Bridge/blob/master/DOC/DMRplus_startup_options.md
# for XLX the syntax is: Options=XLX:4009
# Options=
Slot1=0
Slot2=1
Debug=0

[System Fusion Network]
Enable=0
LocalAddress=0
LocalPort=3200
GatewayAddress=ysfreflector.dvswitch.org
GatewayPort=42166
Debug=0

[P25 Network]
Enable=0
GatewayAddress=127.0.0.1
GatewayPort=42020
LocalPort=32010
Debug=0

[NXDN Network]
Enable=1
#LocalAddress=127.0.0.1
Debug=1
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020


*************NXDNGateway***********

[General]
Callsign=N2WNS
Suffix=NXDN
RptAddress=127.0.0.1
RptPort=14021
LocalPort=14020
Debug=0
Daemon=0

[Info]
RXFrequency=430475000
TXFrequency=439475000
Power=1
Latitude=0.0
Longitude=0.0
Height=0
Name=Nowhere
Description=Multi-Mode Repeater

[Voice]
Enabled=0
Language=en_US
Directory=./Audio

[aprs.fi]
Enable=0
# Server=noam.aprs2.net
Server=euro.aprs2.net
Port=14580
Password=9999
Description=APRS Description
Suffix=N

[Id Lookup]
Name=/var/lib/mmdvm/NXDN.csv
Time=24

[Log]
FilePath=/opt/TriState_NXDN/NXDNGateway/log
FileRoot=NXDNGateway

[Network]
Port=14050
HostsFile1=/opt/TriState_NXDN/NXDNGateway/NXDNHosts.txt
HostsFile2=/var/lib/mmdvm/private_NXDNHosts.txt
ReloadTime=60
ParrotAddress=127.0.0.1
ParrotPort=42021
NXDN2DMRAddress=127.0.0.1
NXDN2DMRPort=42022
Startup=31360
InactivityTimeout=0
Debug=0

[Mobile GPS]
Enable=0
Address=127.0.0.1
Port=7834


Re: MMDVM_Bridge not sending to NXDNGateway

Steve N4IRS
 

Bill,
I forgot to ask for your MMDVM_Bridge.ini and the NXDNGateway.ini

Steve

On 1/27/20 5:55 PM, Bill N2WNS wrote:
M: 2020-01-27 22:50:59.890 Opening Icom connection
I: 2020-01-27 22:50:59.890 Opening NXDN network connection
I: 2020-01-27 22:51:00.924 Loaded 49 NXDN reflectors
I: 2020-01-27 22:51:00.925 Loaded NXDN parrot (TG10)
I: 2020-01-27 22:51:00.925 Loaded NXDN2DMR reflector (TG20)
I: 2020-01-27 22:51:00.926 Loaded 2345 Ids to the NXDN callsign lookup table
M: 2020-01-27 22:51:00.926 Starting NXDNGateway-20180524
M: 2020-01-27 22:51:00.926 Linked at startup to reflector 31360
I: 2020-01-27 22:51:00.926 Started the NXDN Id lookup reload thread


I: 2020-01-27 22:51:04.988 MMDVM_Bridge:
I: 2020-01-27 22:51:04.988 Portions Copyright (C) 2018 DVSwitch, INAD.
I: 2020-01-27 22:51:04.988 Hacks by Mike N4IRR and Steve N4IRS
I: 2020-01-27 22:51:04.988 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2020-01-27 22:51:04.988 This software is for use on amateur radio networks only,
I: 2020-01-27 22:51:04.988 it is to be used for educational purposes only. Its use on
I: 2020-01-27 22:51:04.988 commercial networks is strictly prohibited.
I: 2020-01-27 22:51:04.988 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-01-27 22:51:04.988 MMDVM_Bridge-20191105_V1.4.1 is starting
M: 2020-01-27 22:51:04.988 Built 14:38:14 Nov 11 2019 (GitID #9dae1ac)
I: 2020-01-27 22:51:04.988 General Parameters
I: 2020-01-27 22:51:04.988     Callsign: KC2CWT
I: 2020-01-27 22:51:04.988     Id: 3136187
I: 2020-01-27 22:51:04.988     Duplex: no
I: 2020-01-27 22:51:04.988     Timeout: 180s
I: 2020-01-27 22:51:04.988     D-Star: disabled
I: 2020-01-27 22:51:04.988     DMR: enabled
I: 2020-01-27 22:51:04.988     YSF: disabled
I: 2020-01-27 22:51:04.988     P25: disabled
I: 2020-01-27 22:51:04.988     NXDN: enabled
I: 2020-01-27 22:51:04.988 Modem Parameters
I: 2020-01-27 22:51:04.988     Port: /dev/null
I: 2020-01-27 22:51:04.988     RX Invert: no
I: 2020-01-27 22:51:04.988     TX Invert: no
I: 2020-01-27 22:51:04.988     PTT Invert: no
I: 2020-01-27 22:51:04.988     TX Delay: 100ms
I: 2020-01-27 22:51:04.988     RX Offset: 0Hz
I: 2020-01-27 22:51:04.988     TX Offset: 0Hz
I: 2020-01-27 22:51:04.988     RX DC Offset: 0
I: 2020-01-27 22:51:04.988     TX DC Offset: 0
I: 2020-01-27 22:51:04.988     RF Level: 100.0%
I: 2020-01-27 22:51:04.988     DMR Delay: 0 (0.0ms)
I: 2020-01-27 22:51:04.988     RX Level: 50.0%
I: 2020-01-27 22:51:04.988     CW Id TX Level: 50.0%
I: 2020-01-27 22:51:04.988     D-Star TX Level: 50.0%
I: 2020-01-27 22:51:04.988     DMR TX Level: 50.0%
I: 2020-01-27 22:51:04.988     YSF TX Level: 50.0%
I: 2020-01-27 22:51:04.988     P25 TX Level: 50.0%
I: 2020-01-27 22:51:04.988     NXDN TX Level: 50.0%
I: 2020-01-27 22:51:04.988     RX Frequency: 222340000Hz (222340000Hz)
I: 2020-01-27 22:51:04.988     TX Frequency: 224940000Hz (224940000Hz)
M: 2020-01-27 22:51:04.988 Opening the MMDVM
I: 2020-01-27 22:51:04.988 Display Parameters
I: 2020-01-27 22:51:04.988     Type:
I: 2020-01-27 22:51:04.988 DMR Network Parameters
I: 2020-01-27 22:51:04.988     Address: hotspot.dmrnet.net
I: 2020-01-27 22:51:04.988     Port: 62065
I: 2020-01-27 22:51:04.988     Local: 61085
I: 2020-01-27 22:51:04.988     Jitter: 360ms
I: 2020-01-27 22:51:04.988     Slot 1: disabled
I: 2020-01-27 22:51:04.988     Slot 2: enabled
I: 2020-01-27 22:51:04.988     Mode Hang: 3s
I: 2020-01-27 22:51:04.995 Info Parameters
I: 2020-01-27 22:51:04.995     Callsign: KC2CWT
I: 2020-01-27 22:51:04.995     RX Frequency: 222340000Hz
I: 2020-01-27 22:51:04.995     TX Frequency: 224940000Hz
I: 2020-01-27 22:51:04.995     Power: 1W
I: 2020-01-27 22:51:04.995     Latitude: 41.733299deg N
I: 2020-01-27 22:51:04.995     Longitude: -50.399899deg E
I: 2020-01-27 22:51:04.995     Height: 0m
I: 2020-01-27 22:51:04.995     Location: "Tristate2NXDN Bridge"
I: 2020-01-27 22:51:04.995     Description: "MMDVM_Bridge"
I: 2020-01-27 22:51:04.995     URL: "https://groups.io/g/DVSwitch"
M: 2020-01-27 22:51:04.995 DMR, Opening DMR Network
I: 2020-01-27 22:51:04.995 NXDN Network Parameters
I: 2020-01-27 22:51:04.995     Gateway Address: 127.0.0.1
I: 2020-01-27 22:51:04.995     Gateway Port: 14020
I: 2020-01-27 22:51:04.995     Local Address:
I: 2020-01-27 22:51:04.995     Local Port: 14021
I: 2020-01-27 22:51:04.995     Mode Hang: 3s
M: 2020-01-27 22:51:04.996 Opening NXDN network connection
I: 2020-01-27 22:51:04.996 RSSI
I: 2020-01-27 22:51:04.996     Mapping File: RSSI.dat
W: 2020-01-27 22:51:04.996 Cannot open the RSSI data file - RSSI.dat
I: 2020-01-27 22:51:04.996 DMR Id Lookups
I: 2020-01-27 22:51:04.996     File: /var/lib/mmdvm/DMRIds.dat
I: 2020-01-27 22:51:04.996     Reload: 24 hours
I: 2020-01-27 22:51:05.121 Loaded 154617 Ids to the DMR callsign lookup table
I: 2020-01-27 22:51:05.121 DMR RF Parameters
I: 2020-01-27 22:51:05.121     Id: 3136187
I: 2020-01-27 22:51:05.121     Color Code: 1
I: 2020-01-27 22:51:05.121     Self Only: no
I: 2020-01-27 22:51:05.121     Embedded LC Only: no
I: 2020-01-27 22:51:05.121 Started the DMR Id lookup reload thread
I: 2020-01-27 22:51:05.121     Dump Talker Alias Data: no
I: 2020-01-27 22:51:05.121     Prefixes: 0
I: 2020-01-27 22:51:05.121     Call Hang: 3s
I: 2020-01-27 22:51:05.121     TX Hang: 3s
I: 2020-01-27 22:51:05.121     Mode Hang: 10s
M: 2020-01-27 22:51:05.121 DMR, Opening INI file: DVSwitch.ini
M: 2020-01-27 22:51:05.121 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2020-01-27 22:51:05.121 DMR, Setting [DMR] TXPort -> 31015
M: 2020-01-27 22:51:05.121 DMR, Setting [DMR] RXPort -> 31014
M: 2020-01-27 22:51:05.121 DMR, Setting [DMR] Slot -> 2
M: 2020-01-27 22:51:05.121 DMR, Transmitting on 127.0.0.1:31015 and listening on port 31014.  Result = 1
I: 2020-01-27 22:51:05.121 NXDN Id Lookups
I: 2020-01-27 22:51:05.121     File: /var/lib/mmdvm/NXDN.csv
I: 2020-01-27 22:51:05.121     Reload: 24 hours
I: 2020-01-27 22:51:05.123 Loaded 2345 Ids to the NXDN callsign lookup table
I: 2020-01-27 22:51:05.123 NXDN RF Parameters
I: 2020-01-27 22:51:05.123     Id: 34001
I: 2020-01-27 22:51:05.123     RAN: 1
I: 2020-01-27 22:51:05.123     Self Only: no
I: 2020-01-27 22:51:05.123     Remote Gateway: no
I: 2020-01-27 22:51:05.123     Mode Hang: 10s
M: 2020-01-27 22:51:05.123 NXDN, Opening INI file: DVSwitch.ini
I: 2020-01-27 22:51:05.123 Started the NXDN Id lookup reload thread
M: 2020-01-27 22:51:05.123 NXDN, Setting [NXDN] Address -> 127.0.0.1
M: 2020-01-27 22:51:05.123 NXDN, Setting [NXDN] TXPort -> 31017
M: 2020-01-27 22:51:05.123 NXDN, Setting [NXDN] RXPort -> 31016
M: 2020-01-27 22:51:05.123 NXDN, Setting [NXDN] FallbackID -> 34000
M: 2020-01-27 22:51:05.123 NXDN, Setting [NXDN] NXDNFallbackID -> 34000
M: 2020-01-27 22:51:05.123 NXDN, Setting [NXDN] Translate -> 31360=31360
M: 2020-01-27 22:51:05.123 NXDN, Setting [NXDN] Slot -> 2
M: 2020-01-27 22:51:05.123 NXDN, NXDN TG 31360 <--> TLV TG 31360
M: 2020-01-27 22:51:05.123 NXDN, Transmitting on 127.0.0.1:31017 and listening on port 31016.  Result = 1
M: 2020-01-27 22:51:05.123 MMDVM_Bridge-20191105_V1.4.1 is running
M: 2020-01-27 22:51:15.137 DMR, Logged into the master successfully
M: 2020-01-27 22:51:31.364 DMR Slot 2, received network voice header from N2WNS to TG 31360
M: 2020-01-27 22:51:31.868 NXDN, TX state = ON
I: 2020-01-27 22:51:31.868 NXDN, dmrToNxdn by call: N2WNS
I: 2020-01-27 22:51:31.868 NXDN, Begin TX: src=3134293 rpt=310998 dst=31660 slot=2 cc=1 metadata=N2WNS
I: 2020-01-27 22:51:31.868 NXDN, (3134293, 31660) -> (34002, 31660)
M: 2020-01-27 22:51:31.868 NXDN, received RF header from N2WNS to TG 31660
M: 2020-01-27 22:51:33.703 DMR Slot 2, received network end of voice transmission, 2.3 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-27 22:51:33.708 NXDN, TX state = OFF
M: 2020-01-27 22:51:33.708 NXDN, received RF end of transmission, 2.2 seconds, BER: 0.0%
M: 2020-01-27 22:51:46.016 Closing the MMDVM
I: 2020-01-27 22:51:46.125 Stopped the DMR Id lookup reload thread
I: 2020-01-27 22:51:46.126 Stopped the NXDN Id lookup reload thread
M: 2020-01-27 22:51:46.126 DMR, Closing DMR Network
M: 2020-01-27 22:51:46.126 Closing NXDN network connection
I: 2020-01-27 22:51:46.126 MMDVM_Bridge-20191105_V1.4.1 exited on receipt of SIGTERM

Now full disclosure, I did not use the NXDNGateway package that came with NXDNClients. I used the one off the DVSwitch Git site.

Thanks,

-Bill


Re: MMDVM_Bridge not sending to NXDNGateway

Bill N2WNS
 

M: 2020-01-27 22:50:59.890 Opening Icom connection
I: 2020-01-27 22:50:59.890 Opening NXDN network connection
I: 2020-01-27 22:51:00.924 Loaded 49 NXDN reflectors
I: 2020-01-27 22:51:00.925 Loaded NXDN parrot (TG10)
I: 2020-01-27 22:51:00.925 Loaded NXDN2DMR reflector (TG20)
I: 2020-01-27 22:51:00.926 Loaded 2345 Ids to the NXDN callsign lookup table
M: 2020-01-27 22:51:00.926 Starting NXDNGateway-20180524
M: 2020-01-27 22:51:00.926 Linked at startup to reflector 31360
I: 2020-01-27 22:51:00.926 Started the NXDN Id lookup reload thread


I: 2020-01-27 22:51:04.988 MMDVM_Bridge:
I: 2020-01-27 22:51:04.988 Portions Copyright (C) 2018 DVSwitch, INAD.
I: 2020-01-27 22:51:04.988 Hacks by Mike N4IRR and Steve N4IRS
I: 2020-01-27 22:51:04.988 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I: 2020-01-27 22:51:04.988 This software is for use on amateur radio networks only,
I: 2020-01-27 22:51:04.988 it is to be used for educational purposes only. Its use on
I: 2020-01-27 22:51:04.988 commercial networks is strictly prohibited.
I: 2020-01-27 22:51:04.988 Copyright(C) 2015-2018 by Jonathan Naylor, G4KLX and others
M: 2020-01-27 22:51:04.988 MMDVM_Bridge-20191105_V1.4.1 is starting
M: 2020-01-27 22:51:04.988 Built 14:38:14 Nov 11 2019 (GitID #9dae1ac)
I: 2020-01-27 22:51:04.988 General Parameters
I: 2020-01-27 22:51:04.988     Callsign: KC2CWT
I: 2020-01-27 22:51:04.988     Id: 3136187
I: 2020-01-27 22:51:04.988     Duplex: no
I: 2020-01-27 22:51:04.988     Timeout: 180s
I: 2020-01-27 22:51:04.988     D-Star: disabled
I: 2020-01-27 22:51:04.988     DMR: enabled
I: 2020-01-27 22:51:04.988     YSF: disabled
I: 2020-01-27 22:51:04.988     P25: disabled
I: 2020-01-27 22:51:04.988     NXDN: enabled
I: 2020-01-27 22:51:04.988 Modem Parameters
I: 2020-01-27 22:51:04.988     Port: /dev/null
I: 2020-01-27 22:51:04.988     RX Invert: no
I: 2020-01-27 22:51:04.988     TX Invert: no
I: 2020-01-27 22:51:04.988     PTT Invert: no
I: 2020-01-27 22:51:04.988     TX Delay: 100ms
I: 2020-01-27 22:51:04.988     RX Offset: 0Hz
I: 2020-01-27 22:51:04.988     TX Offset: 0Hz
I: 2020-01-27 22:51:04.988     RX DC Offset: 0
I: 2020-01-27 22:51:04.988     TX DC Offset: 0
I: 2020-01-27 22:51:04.988     RF Level: 100.0%
I: 2020-01-27 22:51:04.988     DMR Delay: 0 (0.0ms)
I: 2020-01-27 22:51:04.988     RX Level: 50.0%
I: 2020-01-27 22:51:04.988     CW Id TX Level: 50.0%
I: 2020-01-27 22:51:04.988     D-Star TX Level: 50.0%
I: 2020-01-27 22:51:04.988     DMR TX Level: 50.0%
I: 2020-01-27 22:51:04.988     YSF TX Level: 50.0%
I: 2020-01-27 22:51:04.988     P25 TX Level: 50.0%
I: 2020-01-27 22:51:04.988     NXDN TX Level: 50.0%
I: 2020-01-27 22:51:04.988     RX Frequency: 222340000Hz (222340000Hz)
I: 2020-01-27 22:51:04.988     TX Frequency: 224940000Hz (224940000Hz)
M: 2020-01-27 22:51:04.988 Opening the MMDVM
I: 2020-01-27 22:51:04.988 Display Parameters
I: 2020-01-27 22:51:04.988     Type:
I: 2020-01-27 22:51:04.988 DMR Network Parameters
I: 2020-01-27 22:51:04.988     Address: hotspot.dmrnet.net
I: 2020-01-27 22:51:04.988     Port: 62065
I: 2020-01-27 22:51:04.988     Local: 61085
I: 2020-01-27 22:51:04.988     Jitter: 360ms
I: 2020-01-27 22:51:04.988     Slot 1: disabled
I: 2020-01-27 22:51:04.988     Slot 2: enabled
I: 2020-01-27 22:51:04.988     Mode Hang: 3s
I: 2020-01-27 22:51:04.995 Info Parameters
I: 2020-01-27 22:51:04.995     Callsign: KC2CWT
I: 2020-01-27 22:51:04.995     RX Frequency: 222340000Hz
I: 2020-01-27 22:51:04.995     TX Frequency: 224940000Hz
I: 2020-01-27 22:51:04.995     Power: 1W
I: 2020-01-27 22:51:04.995     Latitude: 41.733299deg N
I: 2020-01-27 22:51:04.995     Longitude: -50.399899deg E
I: 2020-01-27 22:51:04.995     Height: 0m
I: 2020-01-27 22:51:04.995     Location: "Tristate2NXDN Bridge"
I: 2020-01-27 22:51:04.995     Description: "MMDVM_Bridge"
I: 2020-01-27 22:51:04.995     URL: "https://groups.io/g/DVSwitch"
M: 2020-01-27 22:51:04.995 DMR, Opening DMR Network
I: 2020-01-27 22:51:04.995 NXDN Network Parameters
I: 2020-01-27 22:51:04.995     Gateway Address: 127.0.0.1
I: 2020-01-27 22:51:04.995     Gateway Port: 14020
I: 2020-01-27 22:51:04.995     Local Address:
I: 2020-01-27 22:51:04.995     Local Port: 14021
I: 2020-01-27 22:51:04.995     Mode Hang: 3s
M: 2020-01-27 22:51:04.996 Opening NXDN network connection
I: 2020-01-27 22:51:04.996 RSSI
I: 2020-01-27 22:51:04.996     Mapping File: RSSI.dat
W: 2020-01-27 22:51:04.996 Cannot open the RSSI data file - RSSI.dat
I: 2020-01-27 22:51:04.996 DMR Id Lookups
I: 2020-01-27 22:51:04.996     File: /var/lib/mmdvm/DMRIds.dat
I: 2020-01-27 22:51:04.996     Reload: 24 hours
I: 2020-01-27 22:51:05.121 Loaded 154617 Ids to the DMR callsign lookup table
I: 2020-01-27 22:51:05.121 DMR RF Parameters
I: 2020-01-27 22:51:05.121     Id: 3136187
I: 2020-01-27 22:51:05.121     Color Code: 1
I: 2020-01-27 22:51:05.121     Self Only: no
I: 2020-01-27 22:51:05.121     Embedded LC Only: no
I: 2020-01-27 22:51:05.121 Started the DMR Id lookup reload thread
I: 2020-01-27 22:51:05.121     Dump Talker Alias Data: no
I: 2020-01-27 22:51:05.121     Prefixes: 0
I: 2020-01-27 22:51:05.121     Call Hang: 3s
I: 2020-01-27 22:51:05.121     TX Hang: 3s
I: 2020-01-27 22:51:05.121     Mode Hang: 10s
M: 2020-01-27 22:51:05.121 DMR, Opening INI file: DVSwitch.ini
M: 2020-01-27 22:51:05.121 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2020-01-27 22:51:05.121 DMR, Setting [DMR] TXPort -> 31015
M: 2020-01-27 22:51:05.121 DMR, Setting [DMR] RXPort -> 31014
M: 2020-01-27 22:51:05.121 DMR, Setting [DMR] Slot -> 2
M: 2020-01-27 22:51:05.121 DMR, Transmitting on 127.0.0.1:31015 and listening on port 31014.  Result = 1
I: 2020-01-27 22:51:05.121 NXDN Id Lookups
I: 2020-01-27 22:51:05.121     File: /var/lib/mmdvm/NXDN.csv
I: 2020-01-27 22:51:05.121     Reload: 24 hours
I: 2020-01-27 22:51:05.123 Loaded 2345 Ids to the NXDN callsign lookup table
I: 2020-01-27 22:51:05.123 NXDN RF Parameters
I: 2020-01-27 22:51:05.123     Id: 34001
I: 2020-01-27 22:51:05.123     RAN: 1
I: 2020-01-27 22:51:05.123     Self Only: no
I: 2020-01-27 22:51:05.123     Remote Gateway: no
I: 2020-01-27 22:51:05.123     Mode Hang: 10s
M: 2020-01-27 22:51:05.123 NXDN, Opening INI file: DVSwitch.ini
I: 2020-01-27 22:51:05.123 Started the NXDN Id lookup reload thread
M: 2020-01-27 22:51:05.123 NXDN, Setting [NXDN] Address -> 127.0.0.1
M: 2020-01-27 22:51:05.123 NXDN, Setting [NXDN] TXPort -> 31017
M: 2020-01-27 22:51:05.123 NXDN, Setting [NXDN] RXPort -> 31016
M: 2020-01-27 22:51:05.123 NXDN, Setting [NXDN] FallbackID -> 34000
M: 2020-01-27 22:51:05.123 NXDN, Setting [NXDN] NXDNFallbackID -> 34000
M: 2020-01-27 22:51:05.123 NXDN, Setting [NXDN] Translate -> 31360=31360
M: 2020-01-27 22:51:05.123 NXDN, Setting [NXDN] Slot -> 2
M: 2020-01-27 22:51:05.123 NXDN, NXDN TG 31360 <--> TLV TG 31360
M: 2020-01-27 22:51:05.123 NXDN, Transmitting on 127.0.0.1:31017 and listening on port 31016.  Result = 1
M: 2020-01-27 22:51:05.123 MMDVM_Bridge-20191105_V1.4.1 is running
M: 2020-01-27 22:51:15.137 DMR, Logged into the master successfully
M: 2020-01-27 22:51:31.364 DMR Slot 2, received network voice header from N2WNS to TG 31360
M: 2020-01-27 22:51:31.868 NXDN, TX state = ON
I: 2020-01-27 22:51:31.868 NXDN, dmrToNxdn by call: N2WNS
I: 2020-01-27 22:51:31.868 NXDN, Begin TX: src=3134293 rpt=310998 dst=31660 slot=2 cc=1 metadata=N2WNS
I: 2020-01-27 22:51:31.868 NXDN, (3134293, 31660) -> (34002, 31660)
M: 2020-01-27 22:51:31.868 NXDN, received RF header from N2WNS to TG 31660
M: 2020-01-27 22:51:33.703 DMR Slot 2, received network end of voice transmission, 2.3 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-27 22:51:33.708 NXDN, TX state = OFF
M: 2020-01-27 22:51:33.708 NXDN, received RF end of transmission, 2.2 seconds, BER: 0.0%
M: 2020-01-27 22:51:46.016 Closing the MMDVM
I: 2020-01-27 22:51:46.125 Stopped the DMR Id lookup reload thread
I: 2020-01-27 22:51:46.126 Stopped the NXDN Id lookup reload thread
M: 2020-01-27 22:51:46.126 DMR, Closing DMR Network
M: 2020-01-27 22:51:46.126 Closing NXDN network connection
I: 2020-01-27 22:51:46.126 MMDVM_Bridge-20191105_V1.4.1 exited on receipt of SIGTERM

Now full disclosure, I did not use the NXDNGateway package that came with NXDNClients. I used the one off the DVSwitch Git site.

Thanks,

-Bill


Re: MMDVM_Bridge not sending to NXDNGateway

Steve N4IRS
 

Bill,
Here is what I want you to do:
stop MMDVM_Bridge
Stop NXDNGateway
delete the MMDVM_Bridge log in /var/log/mmdvm
delete the NXDNGateway log in /var/log/mmdvm

Start NXDN_Gateway
Start MMVM_Bridge

Send ONE transmission through the bridge.
stop MMDVM_Bridge
Stop NXDNGateway

get the MMDVM_Bridge and the NXDNGateway logs and post them.

Steve N4IRS


On 1/27/20 3:40 PM, Bill N2WNS wrote:
Yes sir it is:

[NXDN Network]
Enable=1
#LocalAddress=127.0.0.1
Debug=1
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020


 I enabled Debug to see if I could see anything else.

Everything lives on the same host.

-Bill


Re: MMDVM_Bridge not sending to NXDNGateway

Bill N2WNS
 

Yes sir it is:

[NXDN Network]
Enable=1
#LocalAddress=127.0.0.1
Debug=1
LocalPort=14021
GatewayAddress=127.0.0.1
GatewayPort=14020


 I enabled Debug to see if I could see anything else.

Everything lives on the same host.

-Bill


Re: MMDVM_Bridge not sending to NXDNGateway

Steve N4IRS
 

Take a look at [NXDN Network] stanza in MMDVM_Bridge.ini and make sure NXDNGateway is running. 

On 1/26/20 4:40 PM, Bill N2WNS wrote:
I'm bridging DMR to NXDN and I don't see the traffic hitting NXDNGateway:

M: 2020-01-26 21:29:39.654 NXDN, Setting [NXDN] Address -> 127.0.0.1
M: 2020-01-26 21:29:39.654 NXDN, Setting [NXDN] TXPort -> 31017
M: 2020-01-26 21:29:39.654 NXDN, Setting [NXDN] RXPort -> 31016
M: 2020-01-26 21:29:39.654 NXDN, Setting [NXDN] FallbackID -> 34000
M: 2020-01-26 21:29:39.654 NXDN, Setting [NXDN] NXDNFallbackID -> 34000
M: 2020-01-26 21:29:39.654 NXDN, Setting [NXDN] Translate -> 31360=31360
M: 2020-01-26 21:29:39.655 NXDN, Setting [NXDN] Slot -> 2
M: 2020-01-26 21:29:39.655 NXDN, NXDN TG 31360 <--> TLV TG 31360
M: 2020-01-26 21:29:39.655 NXDN, Transmitting on 127.0.0.1:31017 and listening on port 31016.  Result = 1
M: 2020-01-26 21:29:39.655 MMDVM_Bridge-20191105_V1.4.1 is running
M: 2020-01-26 21:29:49.676 DMR, Logged into the master successfully
M: 2020-01-26 21:30:25.305 DMR Slot 2, received network voice header from N2WNS to TG 31360
M: 2020-01-26 21:30:25.822 NXDN, TX state = ON
I: 2020-01-26 21:30:25.823 NXDN, dmrToNxdn by call: N2WNSCheck the NXDN
I: 2020-01-26 21:30:25.823 NXDN, Begin TX: src=3134293 rpt=310998 dst=31660 slot=2 cc=1 metadata=N2WNS
I: 2020-01-26 21:30:25.823 NXDN, (3134293, 31660) -> (34002, 31660)
M: 2020-01-26 21:30:25.823 NXDN, received RF header from N2WNS to TG 31660
M: 2020-01-26 21:30:29.444 DMR Slot 2, received network end of voice transmission, 4.1 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-26 21:30:29.449 NXDN, TX state = OFF
M: 2020-01-26 21:30:29.449 NXDN, received RF end of transmission, 4.0 seconds, BER: 0.0%

Where should I be looking?

73,

-Bill
 N2WNS


Re: Which base image to use with DV Switch: Allstar or HamVoIP

JJ Cummings
 

I’d suggest submitting patches to the actual ASL project, much more likely to be added in and you’ll also get credit for your contributions.

Sent from the iRoad

On Jan 26, 2020, at 18:04, David Ranch <dvswitch-groupsio@...> wrote:


Hello Mike,

Yes, I got it working. 

I went with the HamVoIP v1.5 image ( which is a fork of Allstar's Raspberry Pi image) which uses the Arch Linux distribution.  The HamVoIP release evidently has several fixes in it regarding audio delays, etc. that the the official Allstar images do NOT have.  The challenge I found with the HamVoIP image is not well integrated with modern SystemD-based Linux OSes and the binaries for the DV-Switch stuff seems to lag from what N4IRS publishes at https://github.com/DVSwitch.  I submitted several changes to the HamVoIP developers to improve that SystemD integration but regardless saying they would add them in, I don't think they ever did.  I will admit it was some time ago and I need to look again.  I'm happy to send these patches to others who might be interested in them.

There is also a user-created DV-Switch image which i uses Raspbian (better support on Raspberry Pi, is more SystemD integrated, etc:

   http://ea5gvk-dmr.zigor.es/2019/12/17/v-5-imagen-dvswitch-y-hblink-blasmakers-bautizada-dvlink-llega-para-quedarse/

That web site is Spanish centric, a bit hard to find the details, etc. but it might work for you.


Anyway,  what I ultimately did was follow this doc and started with the software AMBE support:

    https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg/edit

I later switched over to a hardware AMBE device made by NW-Digitial and that worked fine as well.

--David
KI6ZHD


On 01/26/2020 11:22 AM, Mike WG5EEK wrote:
David, did you get this running?  I want to add a DMR bridge to my HamVoIP install but ran into obviously issues with dependencies.

Mike


Re: Which base image to use with DV Switch: Allstar or HamVoIP

David Ranch
 


Hello Mike,

Yes, I got it working. 

I went with the HamVoIP v1.5 image ( which is a fork of Allstar's Raspberry Pi image) which uses the Arch Linux distribution.  The HamVoIP release evidently has several fixes in it regarding audio delays, etc. that the the official Allstar images do NOT have.  The challenge I found with the HamVoIP image is not well integrated with modern SystemD-based Linux OSes and the binaries for the DV-Switch stuff seems to lag from what N4IRS publishes at https://github.com/DVSwitch.  I submitted several changes to the HamVoIP developers to improve that SystemD integration but regardless saying they would add them in, I don't think they ever did.  I will admit it was some time ago and I need to look again.  I'm happy to send these patches to others who might be interested in them.

There is also a user-created DV-Switch image which i uses Raspbian (better support on Raspberry Pi, is more SystemD integrated, etc:

   http://ea5gvk-dmr.zigor.es/2019/12/17/v-5-imagen-dvswitch-y-hblink-blasmakers-bautizada-dvlink-llega-para-quedarse/

That web site is Spanish centric, a bit hard to find the details, etc. but it might work for you.


Anyway,  what I ultimately did was follow this doc and started with the software AMBE support:

    https://docs.google.com/document/d/1eN50Csr29eAprBu7eKA0Bfa2XUcsXw5iktY1Ey-Qjkg/edit

I later switched over to a hardware AMBE device made by NW-Digitial and that worked fine as well.

--David
KI6ZHD


On 01/26/2020 11:22 AM, Mike WG5EEK wrote:
David, did you get this running?  I want to add a DMR bridge to my HamVoIP install but ran into obviously issues with dependencies.

Mike


MMDVM_Bridge not sending to NXDNGateway

Bill N2WNS
 

I'm bridging DMR to NXDN and I don't see the traffic hitting NXDNGateway:

M: 2020-01-26 21:29:39.654 NXDN, Setting [NXDN] Address -> 127.0.0.1
M: 2020-01-26 21:29:39.654 NXDN, Setting [NXDN] TXPort -> 31017
M: 2020-01-26 21:29:39.654 NXDN, Setting [NXDN] RXPort -> 31016
M: 2020-01-26 21:29:39.654 NXDN, Setting [NXDN] FallbackID -> 34000
M: 2020-01-26 21:29:39.654 NXDN, Setting [NXDN] NXDNFallbackID -> 34000
M: 2020-01-26 21:29:39.654 NXDN, Setting [NXDN] Translate -> 31360=31360
M: 2020-01-26 21:29:39.655 NXDN, Setting [NXDN] Slot -> 2
M: 2020-01-26 21:29:39.655 NXDN, NXDN TG 31360 <--> TLV TG 31360
M: 2020-01-26 21:29:39.655 NXDN, Transmitting on 127.0.0.1:31017 and listening on port 31016.  Result = 1
M: 2020-01-26 21:29:39.655 MMDVM_Bridge-20191105_V1.4.1 is running
M: 2020-01-26 21:29:49.676 DMR, Logged into the master successfully
M: 2020-01-26 21:30:25.305 DMR Slot 2, received network voice header from N2WNS to TG 31360
M: 2020-01-26 21:30:25.822 NXDN, TX state = ON
I: 2020-01-26 21:30:25.823 NXDN, dmrToNxdn by call: N2WNS
I: 2020-01-26 21:30:25.823 NXDN, Begin TX: src=3134293 rpt=310998 dst=31660 slot=2 cc=1 metadata=N2WNS
I: 2020-01-26 21:30:25.823 NXDN, (3134293, 31660) -> (34002, 31660)
M: 2020-01-26 21:30:25.823 NXDN, received RF header from N2WNS to TG 31660
M: 2020-01-26 21:30:29.444 DMR Slot 2, received network end of voice transmission, 4.1 seconds, 0% packet loss, BER: 0.0%
M: 2020-01-26 21:30:29.449 NXDN, TX state = OFF
M: 2020-01-26 21:30:29.449 NXDN, received RF end of transmission, 4.0 seconds, BER: 0.0%

Where should I be looking?

73,

-Bill
 N2WNS


Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

EA5GVK Joaquin
 

Here have v5 update OTA until V8

http://ea5gvk-dmr.zigor.es/2019/12/17/v-5-imagen-dvswitch-y-hblink-blasmakers-bautizada-dvlink-llega-para-quedarse/

And also versión virtualbox V8 DVLINK. With server DVSwitch multiuser and server Hblink.

http://ea5gvk-dmr.zigor.es/2020/01/19/ya-disponemos-imagen-dvlink-para-virtualbox-virtualdvlink-por-ea7jcl/

73 EA5GVK & EA7JCL @GROUP BLASMAKERS


Re: Which base image to use with DV Switch: Allstar or HamVoIP

Patrick Perdue
 

I'm not as familiar with the conventions of Arch Linux as I am with Debian. Did you install from a package (I think there is one in the HamVoIP repository,) or did you put everything in place and manually implement the init scripts?

I don't have an immediate need to run DVSwitch on my HamVoIP nodes, but I've gotten questions about it recently from some who do.


On 1/26/2020 2:51 PM, Brad N8PC wrote:
yes it works. I have DMR bridge on hamvoip image. check out 314651 dmr tg allstar 45743or echolink 275408

Brad N8PC

On 1/26/2020 2:22 PM, Mike WG5EEK wrote:
David, did you get this running?  I want to add a DMR bridge to my HamVoIP install but ran into obviously issues with dependencies.

Mike


Re: Which base image to use with DV Switch: Allstar or HamVoIP

Brad N8PC
 

yes it works. I have DMR bridge on hamvoip image. check out 314651 dmr tg allstar 45743or echolink 275408

Brad N8PC

On 1/26/2020 2:22 PM, Mike WG5EEK wrote:
David, did you get this running?  I want to add a DMR bridge to my HamVoIP install but ran into obviously issues with dependencies.

Mike


Re: Which base image to use with DV Switch: Allstar or HamVoIP

Mike WG5EEK
 

David, did you get this running?  I want to add a DMR bridge to my HamVoIP install but ran into obviously issues with dependencies.

Mike


Re: Image for Raspberry pi3 with Debian 10 Buster with DVSWICTH SERVER, HBLINK3 AND HBMONITOR.

kj4gmu@...
 

Hello All,

I have installed Jaoquin’s v2 DVSwitch Server image on a R Pi 3+ and have followed the setup instructions. The YSF mode works flawlessly, however I can’t seem to have any luck receiving or transmitting any audio on DMR+ or DMR BM. I have updated the server IP on both and have also updated binaries and scripts. Any ideas as to what I have missed or done incorrectly?

Thanks a lot,
Jay KJ4GMU


Re: DVSwitch Server instructions refresh

 

On Wed, Jan 22, 2020 at 9:05 PM Ken, K6EFJ <ken@...> wrote:
Any idea when the updated pdf for
 (https://dvswitch.groups.io/g/Mobile/files/Mobile%20DVSwitch%200725.pdf) with dvswitch.sh will be available?
Thanks,
Ken Smith K6EFJ 


Re: change USRP and TLV gain with dvswitch.sh

Patrick Perdue
 

Thanks Steve. This works as expected.

On 1/24/2020 5:55 AM, Steve N4IRS wrote:
Patrick,
dvswitch.sh will do what you want.

Example:
dvswitch.sh tlvAudio AUDIO_USE_GAIN 1.1
dvswitch.sh usrpAudio AUDIO_USE_GAIN .93

You will see the change reflected in the AB log and in the AB json file in /tmp
Assuming you are using port 12345, you will find a file in /tmp named:
ABInfo_12345.json
This contains all current setting in use by AB.

Steve N4IRS

On 1/23/20 11:43 PM, Patrick Perdue wrote:
Is there a way to change the USRP and TLV gain on the fly with dvswitch.sh?

I normally have my USRP gain set to 0.34, and TLV gain set to 3.00, which works fine most of the time, but there is one net controller using a very hot DMR radio (GD77S) which clips out at that gain even when he backs off. I like having higher than unity gain, because it makes it easier for those using Allstar to hear the wider dynamic range of DMR users. If I change the gain to unity or 1.80, it's fine with this hot radio (1.80 is actually a little on the edge as well, but not as bad as 3.00,) but the only way I know of for doing this is changing it in the INI file and restarting A_B. I have never gotten satisfactory results with AGC.

Thanks and 73

KE4DYI





Re: change USRP and TLV gain with dvswitch.sh

Steve N4IRS
 

Patrick,
dvswitch.sh will do what you want.

Example:
dvswitch.sh tlvAudio AUDIO_USE_GAIN 1.1
dvswitch.sh usrpAudio AUDIO_USE_GAIN .93

You will see the change reflected in the AB log and in the AB json file in /tmp
Assuming you are using port 12345, you will find a file in /tmp named:
ABInfo_12345.json
This contains all current setting in use by AB.

Steve N4IRS

On 1/23/20 11:43 PM, Patrick Perdue wrote:
Is there a way to change the USRP and TLV gain on the fly with dvswitch.sh?

I normally have my USRP gain set to 0.34, and TLV gain set to 3.00, which works fine most of the time, but there is one net controller using a very hot DMR radio (GD77S) which clips out at that gain even when he backs off. I like having higher than unity gain, because it makes it easier for those using Allstar to hear the wider dynamic range of DMR users. If I change the gain to unity or 1.80, it's fine with this hot radio (1.80 is actually a little on the edge as well, but not as bad as 3.00,) but the only way I know of for doing this is changing it in the INI file and restarting A_B. I have never gotten satisfactory results with AGC.

Thanks and 73

KE4DYI



change USRP and TLV gain with dvswitch.sh

Patrick Perdue
 

Is there a way to change the USRP and TLV gain on the fly with dvswitch.sh?

I normally have my USRP gain set to 0.34, and TLV gain set to 3.00, which works fine most of the time, but there is one net controller using a very hot DMR radio (GD77S) which clips out at that gain even when he backs off. I like having higher than unity gain, because it makes it easier for those using Allstar to hear the wider dynamic range of DMR users. If I change the gain to unity or 1.80, it's fine with this hot radio (1.80 is actually a little on the edge as well, but not as bad as 3.00,) but the only way I know of for doing this is changing it in the INI file and restarting A_B. I have never gotten satisfactory results with AGC.

Thanks and 73

KE4DYI


Re: DMR to YSF Weird Issue

Eric-K6KWB
 
Edited

Steve N4IRS
Just FYI - this suggestion works, thank you much.

chmod +x MMDVM_Bridge.amd64

best, Eric

3741 - 3760 of 9532