Date   

Re: YSFReflector, HBlink or HB_confbridge, and mmdvm_bridge be on same linux box

Steve N4IRS
 

Steve,
Do you see a login attempt on hblink?
 Are you sure hblink is listening on 62031?

netstat -unap will show you what program is listening on what UDP port
But, be aware that the program listening to the port is python NOT hblink.py

Here is an example:

root@openbridge:/home/szingman# netstat -unap
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name   
udp        0      0 0.0.0.0:62031           0.0.0.0:*                           7356/python        
udp        0      0 0.0.0.0:62035           0.0.0.0:*                           7356/python        
udp        0      0 0.0.0.0:54001           0.0.0.0:*                           7356/python        
udp        0      0 0.0.0.0:54002           0.0.0.0:*                           7356/python        

Python is listening to UDP port 62031. OK, but which python program?
I have bolded the UDP port number and the PID.
Now let's see what is running:

root@openbridge:/home/szingman# ps ax | grep python
 7356 ?        Ss    34:17 /usr/bin/python /opt/OpenBridge/hb_confbridge.py
 8976 ?        Ss     7:41 /usr/bin/python /opt/hbmonitor/web_tables.py
31311 pts/0    S+     0:00 grep python
root@openbridge:/home/szingman#

OK, PID 7356 in my case is running  hb_confbridge.py so hb_confbridge.py is listening on UDP port 62031

Hope this helps,
Steve N4IRS


On 12/23/18 7:43 AM, dstrobbe@... wrote:
ysf reflector , hblink  and mmdvm  on same linux VM
same ip   10.1.0.117
YSFreflector   registered SMS in registry


I am having problems with MMDVM_bridge setting up dmr to ysf .
mmdvm_bridge out put.
2018-12-23 11:31:30.044 General Parameters
I: 2018-12-23 11:31:30.044     Callsign: KJ4FPA
I: 2018-12-23 11:31:30.044     Id: 1112822
I: 2018-12-23 11:31:30.044     Duplex: no
I: 2018-12-23 11:31:30.044     Timeout: 180s
I: 2018-12-23 11:31:30.044     D-Star: disabled
I: 2018-12-23 11:31:30.044     DMR: enabled
I: 2018-12-23 11:31:30.044     YSF: enabled
I: 2018-12-23 11:31:30.044     P25: disabled
I: 2018-12-23 11:31:30.044     NXDN: disabled
I: 2018-12-23 11:31:30.044 Modem Parameters
I: 2018-12-23 11:31:30.044     Port: /dev/null
I: 2018-12-23 11:31:30.044     RX Invert: no
I: 2018-12-23 11:31:30.044     TX Invert: no
I: 2018-12-23 11:31:30.044     PTT Invert: no
I: 2018-12-23 11:31:30.044     TX Delay: 100ms
I: 2018-12-23 11:31:30.045     RX Offset: 0Hz
I: 2018-12-23 11:31:30.045     TX Offset: 0Hz
I: 2018-12-23 11:31:30.045     RX DC Offset: 0
I: 2018-12-23 11:31:30.045     TX DC Offset: 0
I: 2018-12-23 11:31:30.045     RF Level: 100.0%
I: 2018-12-23 11:31:30.045     DMR Delay: 0 (0.0ms)
I: 2018-12-23 11:31:30.045     RX Level: 50.0%
I: 2018-12-23 11:31:30.045     CW Id TX Level: 50.0%
I: 2018-12-23 11:31:30.045     D-Star TX Level: 50.0%
I: 2018-12-23 11:31:30.045     DMR TX Level: 50.0%
I: 2018-12-23 11:31:30.045     YSF TX Level: 50.0%
I: 2018-12-23 11:31:30.045     P25 TX Level: 50.0%
I: 2018-12-23 11:31:30.045     NXDN TX Level: 50.0%
I: 2018-12-23 11:31:30.045     RX Frequency: 222340000Hz (222340000Hz)
I: 2018-12-23 11:31:30.045     TX Frequency: 224940000Hz (224940000Hz)
M: 2018-12-23 11:31:30.045 Opening the MMDVM
I: 2018-12-23 11:31:30.045 Display Parameters
I: 2018-12-23 11:31:30.045     Type: 
I: 2018-12-23 11:31:30.045 DMR Network Parameters
I: 2018-12-23 11:31:30.046     Address: 10.0.117
I: 2018-12-23 11:31:30.046     Port: 62031
I: 2018-12-23 11:31:30.046     Local: 62032
I: 2018-12-23 11:31:30.046     Jitter: 360ms
I: 2018-12-23 11:31:30.046     Slot 1: enabled
I: 2018-12-23 11:31:30.046     Slot 2: enabled
I: 2018-12-23 11:31:30.046     Mode Hang: 3s
I: 2018-12-23 11:31:30.046 Info Parameters
I: 2018-12-23 11:31:30.046     Callsign: KJ4FPA
I: 2018-12-23 11:31:30.046     RX Frequency: 222340000Hz
I: 2018-12-23 11:31:30.046     TX Frequency: 224940000Hz
I: 2018-12-23 11:31:30.046     Power: 1W
I: 2018-12-23 11:31:30.046     Latitude: 41.733299deg N
I: 2018-12-23 11:31:30.046     Longitude: -50.399899deg E
I: 2018-12-23 11:31:30.046     Height: 0m
I: 2018-12-23 11:31:30.046     Location: "Iceberg, North Atlantic"
I: 2018-12-23 11:31:30.046     Description: "MMDVM_Bridge"
I: 2018-12-23 11:31:30.046     URL: "https://groups.io/g/DVSwitch"
M: 2018-12-23 11:31:30.046 DMR, Opening DMR Network
I: 2018-12-23 11:31:30.046 System Fusion Network Parameters
I: 2018-12-23 11:31:30.047     Local Address: 0
I: 2018-12-23 11:31:30.047     Local Port: 3200
I: 2018-12-23 11:31:30.047     Gateway Address: 47.206.21.33
I: 2018-12-23 11:31:30.047     Gateway Port: 42000
I: 2018-12-23 11:31:30.047     Mode Hang: 3s
M: 2018-12-23 11:31:30.047 Opening YSF network connection
I: 2018-12-23 11:31:30.047 RSSI
I: 2018-12-23 11:31:30.047     Mapping File: RSSI.dat
W: 2018-12-23 11:31:30.047 Cannot open the RSSI data file - RSSI.dat
I: 2018-12-23 11:31:30.047 DMR Id Lookups
I: 2018-12-23 11:31:30.047     File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-23 11:31:30.047     Reload: 24 hours
I: 2018-12-23 11:31:30.165 Loaded 119347 Ids to the DMR callsign lookup table
I: 2018-12-23 11:31:30.165 DMR RF Parameters
I: 2018-12-23 11:31:30.165     Id: 1112822
I: 2018-12-23 11:31:30.165     Color Code: 1
I: 2018-12-23 11:31:30.165     Self Only: no
I: 2018-12-23 11:31:30.165     Embedded LC Only: yes
I: 2018-12-23 11:31:30.165     Dump Talker Alias Data: no
I: 2018-12-23 11:31:30.165     Prefixes: 0
I: 2018-12-23 11:31:30.165     Call Hang: 3s
I: 2018-12-23 11:31:30.165     TX Hang: 3s
I: 2018-12-23 11:31:30.165     Mode Hang: 10s
M: 2018-12-23 11:31:30.165 DMR, Opening INI file: DVSwitch.ini
M: 2018-12-23 11:31:30.165 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2018-12-23 11:31:30.165 DMR, Setting [DMR] TXPort -> 31100
M: 2018-12-23 11:31:30.166 DMR, Setting [DMR] RXPort -> 31103
M: 2018-12-23 11:31:30.166 DMR, Setting [DMR] Slot -> 2
M: 2018-12-23 11:31:30.166 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
I: 2018-12-23 11:31:30.166 YSF RF Parameters
I: 2018-12-23 11:31:30.166     Low Deviation: no
I: 2018-12-23 11:31:30.166     Remote Gateway: no
I: 2018-12-23 11:31:30.166     Self Only: no
I: 2018-12-23 11:31:30.166     DSQ: no
I: 2018-12-23 11:31:30.166     Mode Hang: 10s
M: 2018-12-23 11:31:30.166 YSF, Opening INI file: DVSwitch.ini
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] TXPort -> 31103
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] RXPort -> 31100
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] FallbackID -> 1234567
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] ExportTG -> 1234
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] Slot -> 2
M: 2018-12-23 11:31:30.166 YSF, Transmitting on 127.0.0.1:31103 and listening on port 31100.  Result = 1
M: 2018-12-23 11:31:30.167 MMDVM_Bridge-20180423 is running
I: 2018-12-23 11:31:30.167 Started the DMR Id lookup reload thread
E: 2018-12-23 11:32:40.171 DMR, Connection to the master has timed out, retrying connection
M: 2018-12-23 11:32:40.171 DMR, Closing DMR Network
M: 2018-12-23 11:32:40.171 DMR, Opening DMR Network
^CM: 2018-12-23 11:33:46.737 Closing the MMDVM
The DMR network keeps connecting and timing out   
do not see YSF connection. 


Thanks

Steven Strobbe D.O.
KJ4FPA


YSFReflector, HBlink or HB_confbridge, and mmdvm_bridge be on same linux box

dstrobbe@...
 

ysf reflector , hblink  and mmdvm  on same linux VM
same ip   10.1.0.117
YSFreflector   registered SMS in registry


I am having problems with MMDVM_bridge setting up dmr to ysf .
mmdvm_bridge out put.
2018-12-23 11:31:30.044 General Parameters
I: 2018-12-23 11:31:30.044     Callsign: KJ4FPA
I: 2018-12-23 11:31:30.044     Id: 1112822
I: 2018-12-23 11:31:30.044     Duplex: no
I: 2018-12-23 11:31:30.044     Timeout: 180s
I: 2018-12-23 11:31:30.044     D-Star: disabled
I: 2018-12-23 11:31:30.044     DMR: enabled
I: 2018-12-23 11:31:30.044     YSF: enabled
I: 2018-12-23 11:31:30.044     P25: disabled
I: 2018-12-23 11:31:30.044     NXDN: disabled
I: 2018-12-23 11:31:30.044 Modem Parameters
I: 2018-12-23 11:31:30.044     Port: /dev/null
I: 2018-12-23 11:31:30.044     RX Invert: no
I: 2018-12-23 11:31:30.044     TX Invert: no
I: 2018-12-23 11:31:30.044     PTT Invert: no
I: 2018-12-23 11:31:30.044     TX Delay: 100ms
I: 2018-12-23 11:31:30.045     RX Offset: 0Hz
I: 2018-12-23 11:31:30.045     TX Offset: 0Hz
I: 2018-12-23 11:31:30.045     RX DC Offset: 0
I: 2018-12-23 11:31:30.045     TX DC Offset: 0
I: 2018-12-23 11:31:30.045     RF Level: 100.0%
I: 2018-12-23 11:31:30.045     DMR Delay: 0 (0.0ms)
I: 2018-12-23 11:31:30.045     RX Level: 50.0%
I: 2018-12-23 11:31:30.045     CW Id TX Level: 50.0%
I: 2018-12-23 11:31:30.045     D-Star TX Level: 50.0%
I: 2018-12-23 11:31:30.045     DMR TX Level: 50.0%
I: 2018-12-23 11:31:30.045     YSF TX Level: 50.0%
I: 2018-12-23 11:31:30.045     P25 TX Level: 50.0%
I: 2018-12-23 11:31:30.045     NXDN TX Level: 50.0%
I: 2018-12-23 11:31:30.045     RX Frequency: 222340000Hz (222340000Hz)
I: 2018-12-23 11:31:30.045     TX Frequency: 224940000Hz (224940000Hz)
M: 2018-12-23 11:31:30.045 Opening the MMDVM
I: 2018-12-23 11:31:30.045 Display Parameters
I: 2018-12-23 11:31:30.045     Type: 
I: 2018-12-23 11:31:30.045 DMR Network Parameters
I: 2018-12-23 11:31:30.046     Address: 10.0.117
I: 2018-12-23 11:31:30.046     Port: 62031
I: 2018-12-23 11:31:30.046     Local: 62032
I: 2018-12-23 11:31:30.046     Jitter: 360ms
I: 2018-12-23 11:31:30.046     Slot 1: enabled
I: 2018-12-23 11:31:30.046     Slot 2: enabled
I: 2018-12-23 11:31:30.046     Mode Hang: 3s
I: 2018-12-23 11:31:30.046 Info Parameters
I: 2018-12-23 11:31:30.046     Callsign: KJ4FPA
I: 2018-12-23 11:31:30.046     RX Frequency: 222340000Hz
I: 2018-12-23 11:31:30.046     TX Frequency: 224940000Hz
I: 2018-12-23 11:31:30.046     Power: 1W
I: 2018-12-23 11:31:30.046     Latitude: 41.733299deg N
I: 2018-12-23 11:31:30.046     Longitude: -50.399899deg E
I: 2018-12-23 11:31:30.046     Height: 0m
I: 2018-12-23 11:31:30.046     Location: "Iceberg, North Atlantic"
I: 2018-12-23 11:31:30.046     Description: "MMDVM_Bridge"
I: 2018-12-23 11:31:30.046     URL: "https://groups.io/g/DVSwitch"
M: 2018-12-23 11:31:30.046 DMR, Opening DMR Network
I: 2018-12-23 11:31:30.046 System Fusion Network Parameters
I: 2018-12-23 11:31:30.047     Local Address: 0
I: 2018-12-23 11:31:30.047     Local Port: 3200
I: 2018-12-23 11:31:30.047     Gateway Address: 47.206.21.33
I: 2018-12-23 11:31:30.047     Gateway Port: 42000
I: 2018-12-23 11:31:30.047     Mode Hang: 3s
M: 2018-12-23 11:31:30.047 Opening YSF network connection
I: 2018-12-23 11:31:30.047 RSSI
I: 2018-12-23 11:31:30.047     Mapping File: RSSI.dat
W: 2018-12-23 11:31:30.047 Cannot open the RSSI data file - RSSI.dat
I: 2018-12-23 11:31:30.047 DMR Id Lookups
I: 2018-12-23 11:31:30.047     File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-23 11:31:30.047     Reload: 24 hours
I: 2018-12-23 11:31:30.165 Loaded 119347 Ids to the DMR callsign lookup table
I: 2018-12-23 11:31:30.165 DMR RF Parameters
I: 2018-12-23 11:31:30.165     Id: 1112822
I: 2018-12-23 11:31:30.165     Color Code: 1
I: 2018-12-23 11:31:30.165     Self Only: no
I: 2018-12-23 11:31:30.165     Embedded LC Only: yes
I: 2018-12-23 11:31:30.165     Dump Talker Alias Data: no
I: 2018-12-23 11:31:30.165     Prefixes: 0
I: 2018-12-23 11:31:30.165     Call Hang: 3s
I: 2018-12-23 11:31:30.165     TX Hang: 3s
I: 2018-12-23 11:31:30.165     Mode Hang: 10s
M: 2018-12-23 11:31:30.165 DMR, Opening INI file: DVSwitch.ini
M: 2018-12-23 11:31:30.165 DMR, Setting [DMR] Address -> 127.0.0.1
M: 2018-12-23 11:31:30.165 DMR, Setting [DMR] TXPort -> 31100
M: 2018-12-23 11:31:30.166 DMR, Setting [DMR] RXPort -> 31103
M: 2018-12-23 11:31:30.166 DMR, Setting [DMR] Slot -> 2
M: 2018-12-23 11:31:30.166 DMR, Transmitting on 127.0.0.1:31100 and listening on port 31103.  Result = 1
I: 2018-12-23 11:31:30.166 YSF RF Parameters
I: 2018-12-23 11:31:30.166     Low Deviation: no
I: 2018-12-23 11:31:30.166     Remote Gateway: no
I: 2018-12-23 11:31:30.166     Self Only: no
I: 2018-12-23 11:31:30.166     DSQ: no
I: 2018-12-23 11:31:30.166     Mode Hang: 10s
M: 2018-12-23 11:31:30.166 YSF, Opening INI file: DVSwitch.ini
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] Address -> 127.0.0.1
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] TXPort -> 31103
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] RXPort -> 31100
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] FallbackID -> 1234567
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] ExportTG -> 1234
M: 2018-12-23 11:31:30.166 YSF, Setting [YSF] Slot -> 2
M: 2018-12-23 11:31:30.166 YSF, Transmitting on 127.0.0.1:31103 and listening on port 31100.  Result = 1
M: 2018-12-23 11:31:30.167 MMDVM_Bridge-20180423 is running
I: 2018-12-23 11:31:30.167 Started the DMR Id lookup reload thread
E: 2018-12-23 11:32:40.171 DMR, Connection to the master has timed out, retrying connection
M: 2018-12-23 11:32:40.171 DMR, Closing DMR Network
M: 2018-12-23 11:32:40.171 DMR, Opening DMR Network
^CM: 2018-12-23 11:33:46.737 Closing the MMDVM
The DMR network keeps connecting and timing out   
do not see YSF connection. 


Thanks

Steven Strobbe D.O.
KJ4FPA


Re: Hbmonitor problem

Valentino
 

El 2018-12-20 20:21, Heiko DL1BZ escribió:

you need to forward the port 9000 (websocket python) too in addition for your webserver-port  80XX for communication outside/NAT with the hbmonitor.

73 Heiko, DL1BZ

Many thanks, Heiko, just leave a new post in this thread. Many thanks a lot and my best regard.

Merry Christmas for you and your family

EA1HNC - Valentino
--
vP


Conforme a la LOPD 15/1999 la posible información que pudiera
contener este comunicado, relacionada con datos de carácter personal,
no será utilizada para fines que no sean los estrictamente necesarios
para la realización de su cometido, añadiendo además la absoluta
confidencialidad y exclusividad, quedando prohibida a cualquier
persona su revelación, copia, distribución o el ejercicio de
cualquiera acción relativa a su contenido.

 Si recibe este e-mail erróneamente, ruego lo elimine de todos sus
archivos. Conforme a la Ley 34/2002 de Servicios de la Sociedad de la
Información y Comercio Electrónico


Re: New Set Up MMDVM to IPSC

Steve N4IRS
 

You can point the second MMDVM repeater at the HB_Bridge instance.


Re: New Set Up MMDVM to IPSC

Dutch Drahtlos
 

Thank for the info...

so is it like this:?

MMDVM + Raspberry   --------------------      XPR8300
(HB_Bridge)                    Ethernet Link
(IPSC_Bridge)

to connect 2 MMDVM repeater, also same like this too?


Re: Hbmonitor problem

Valentino
 

Hello _Mr. Heiko, many thanks a lot!!!!!!! Just missed this!!!!! Yesterday an a friend here EA4GAX ask me if  to have oper this port and i tell without thinking "NO" !!! then i open this port 9000 and runninig immediately.!! Many thanks a lot also for you. Have a nice evening and Merry Christmas and Happy  New Year for you and family
Sincerely

Valentino - EA1HNC


Re: Hbmonitor problem

Heiko DL1BZ
 

you need to forward the port 9000 (websocket python) too in addition for your webserver-port  80XX for communication outside/NAT with the hbmonitor.

73 Heiko, DL1BZ


Re: A newbei Question about NXDN <--> DMR

Serdar ULUKONAKCI
 

Hi Steve,
Thank you very much.
Best Regards,
Serdar

On 20.12.2018 02:18, Steve N4IRS wrote:
Serdar,
You used all the right words and you have the concepts correct. The problem is the Kenwood networking protocol. It is a closed system and I see no way to gain access. The only way would be to reverse engineer the protocol and that would take time and equipment.

Steve

On 12/19/18 6:11 PM, Serdar ULUKONAKCI wrote:
Hi Steve,
Thank you very much for your reply and guidance. Maybe, "BRIDGE" is the wrong terminology, I don't know. I read  about "REFLECTORS". Running a reflector for NXDN can be a solution?
Sorry as I wrote before, this is my first steps into the interconnection world so I may have use  some keywords incorrectly.
Best Regards,
Serdar
On 20.12.2018 02:03, Steve N4IRS wrote:
Serdar,
Unfortunately you will not be able to bridge to the NXR710. The networking of the Kenwood repeater is not open and to be honest, there is not enough demand to warrant the expense and work to reverse engineer the protocol they use.

73, Steve N4IRS

On 12/19/18 5:01 PM, Serdar ULUKONAKCI wrote:
Hi All,
This is my first post and first steps in the world of interconnection between digital networks so my question may be silly but your help will be appreciated.
Our amateur radio club is running two NXDN (Kenwood NXR710) and one DMR (Hytera RD985) repeaters. BTW, Hytera RD985 repeater is connected to BM network. All of these repeaters are are in same IP network and same subnet. We want to create a bridge (sorry I don't know exact terminology) between DMR and NXDN world. Our members want to use their NXDN handhelds for communicate with DMR network and vice versa.
I hope that, I can explain current situation.
What software should we use?
What is the required hardware?
Your help will be appreciated.
73!
TA3AS
Serdar



Re: A newbei Question about NXDN <--> DMR

Steve N4IRS
 

Serdar,
You used all the right words and you have the concepts correct. The problem is the Kenwood networking protocol. It is a closed system and I see no way to gain access. The only way would be to reverse engineer the protocol and that would take time and equipment.

Steve

On 12/19/18 6:11 PM, Serdar ULUKONAKCI wrote:
Hi Steve,
Thank you very much for your reply and guidance. Maybe, "BRIDGE" is the wrong terminology, I don't know. I read  about "REFLECTORS". Running a reflector for NXDN can be a solution?
Sorry as I wrote before, this is my first steps into the interconnection world so I may have use  some keywords incorrectly.
Best Regards,
Serdar
On 20.12.2018 02:03, Steve N4IRS wrote:
Serdar,
Unfortunately you will not be able to bridge to the NXR710. The networking of the Kenwood repeater is not open and to be honest, there is not enough demand to warrant the expense and work to reverse engineer the protocol they use.

73, Steve N4IRS

On 12/19/18 5:01 PM, Serdar ULUKONAKCI wrote:
Hi All,
This is my first post and first steps in the world of interconnection between digital networks so my question may be silly but your help will be appreciated.
Our amateur radio club is running two NXDN (Kenwood NXR710) and one DMR (Hytera RD985) repeaters. BTW, Hytera RD985 repeater is connected to BM network. All of these repeaters are are in same IP network and same subnet. We want to create a bridge (sorry I don't know exact terminology) between DMR and NXDN world. Our members want to use their NXDN handhelds for communicate with DMR network and vice versa.
I hope that, I can explain current situation.
What software should we use?
What is the required hardware?
Your help will be appreciated.
73!
TA3AS
Serdar



Re: A newbei Question about NXDN <--> DMR

Serdar ULUKONAKCI
 

Hi Steve,
Thank you very much for your reply and guidance. Maybe, "BRIDGE" is the wrong terminology, I don't know. I read  about "REFLECTORS". Running a reflector for NXDN can be a solution?
Sorry as I wrote before, this is my first steps into the interconnection world so I may have use  some keywords incorrectly.
Best Regards,
Serdar

On 20.12.2018 02:03, Steve N4IRS wrote:
Serdar,
Unfortunately you will not be able to bridge to the NXR710. The networking of the Kenwood repeater is not open and to be honest, there is not enough demand to warrant the expense and work to reverse engineer the protocol they use.

73, Steve N4IRS

On 12/19/18 5:01 PM, Serdar ULUKONAKCI wrote:
Hi All,
This is my first post and first steps in the world of interconnection between digital networks so my question may be silly but your help will be appreciated.
Our amateur radio club is running two NXDN (Kenwood NXR710) and one DMR (Hytera RD985) repeaters. BTW, Hytera RD985 repeater is connected to BM network. All of these repeaters are are in same IP network and same subnet. We want to create a bridge (sorry I don't know exact terminology) between DMR and NXDN world. Our members want to use their NXDN handhelds for communicate with DMR network and vice versa.
I hope that, I can explain current situation.
What software should we use?
What is the required hardware?
Your help will be appreciated.
73!
TA3AS
Serdar


Re: A newbei Question about NXDN <--> DMR

Steve N4IRS
 

Serdar,
Unfortunately you will not be able to bridge to the NXR710. The networking of the Kenwood repeater is not open and to be honest, there is not enough demand to warrant the expense and work to reverse engineer the protocol they use.

73, Steve N4IRS

On 12/19/18 5:01 PM, Serdar ULUKONAKCI wrote:
Hi All,
This is my first post and first steps in the world of interconnection between digital networks so my question may be silly but your help will be appreciated.
Our amateur radio club is running two NXDN (Kenwood NXR710) and one DMR (Hytera RD985) repeaters. BTW, Hytera RD985 repeater is connected to BM network. All of these repeaters are are in same IP network and same subnet. We want to create a bridge (sorry I don't know exact terminology) between DMR and NXDN world. Our members want to use their NXDN handhelds for communicate with DMR network and vice versa.
I hope that, I can explain current situation.
What software should we use?
What is the required hardware?
Your help will be appreciated.
73!
TA3AS
Serdar


A newbei Question about NXDN <--> DMR

Serdar ULUKONAKCI
 

Hi All,
This is my first post and first steps in the world of interconnection between digital networks so my question may be silly but your help will be appreciated.
Our amateur radio club is running two NXDN (Kenwood NXR710) and one DMR (Hytera RD985) repeaters. BTW, Hytera RD985 repeater is connected to BM network. All of these repeaters are are in same IP network and same subnet. We want to create a bridge (sorry I don't know exact terminology) between DMR and NXDN world. Our members want to use their NXDN handhelds for communicate with DMR network and vice versa.
I hope that, I can explain current situation.
What software should we use?
What is the required hardware?
Your help will be appreciated.
73!
TA3AS
Serdar


Re: Milestone

G7RPG - Peter Kendall
 

I'll second that. Big thanks to Mike, Steve, Cort and anyone else involved.

73
Peter
G7RPG

On 18/12/2018 19:42, EA5GVK Joaquin wrote:
Congratulations. For All work. Magnific software for all hamradio.
Many thx. Work Perfect new HBLINK and HBmonitor.
73 EA5GVK.


Re: Milestone

EA5GVK Joaquin
 

Congratulations. For All work. Magnific software for all hamradio.
Many thx. Work Perfect new HBLINK and HBmonitor.
73 EA5GVK.


Milestone

Steve N4IRS
 

We have crossed a milestone here at DVSwitch. We now have over 500 members on groups.io. I know that there are other larger groups but I am surprised. Not bad for a group dedicated to building Digital Voice tools that allow people to "build it their way" All of the software has evolved over time. Cort has made major changes and additions to HBlink including support for OpenBridge and significant upgrades to the confbridge software. Pretty damn good for a guy that claims he is not a programmer and started by wanting to "scratch a itch"
I can see some other things in the future as the HB protocol becomes the place for innovation.

Analog_Bridge has added support for Most of the digital voice formats and does a pretty good job of transcoding those formats or connecting to analog services like AllStarLink. MMDVM_Bridge is working (with a couple of bugs) and is scheduled for a refresh in 2019. Every comment, bug report and success is  being watch, logged and considered. No time frame yet. We introduced Quantar_Bridge to add the ability to connect a purpose built P25 repeaters to the MMDVM P25 Network. That is not to say there are not other great P25 repeaters and of course there is MMDVM_Host and the MMDVM modem (redundant). I see some changes coming to the reflector system next year. Again, we are listening.

There is at least one other major refresh in the works today. I hope to announce that "real soon".

What we do need is some help. We are lacking in tutorials, demos and howto. Please consider submitting some of the work you have done as a editable document so that we can work with you to create something that will help people accomplish what they are trying to do.

For DVSwitch,
73, Steve N4IRS


Hbmonitor problem

Valentino
 

Hello guys, just finish to instal HBlink with HBmonitor and really runing well in my local ip, is fantastic and i do also some qso. But  i have a problem...

Out, at this link http://hblink.dynu.net:8081 is possible see a home page and not more, when you are connections here i read a messagge: Connection closed (wasclean = false, code = 1006, reason = '')

but in my local machine i read and see all.


 Pic nº 2


Well  but out  is not possible see all data, always error Connection closed (wasclean = false, code = 1006, reason = '')

If some friend know a problem  i need your help. Many thanks a lot and my best 73 - EA1HNC - Valentino


Re: New Set Up MMDVM to IPSC

Steve N4IRS
 

It can run on the same host as MMDVM_Host.


Re: New Set Up MMDVM to IPSC

Dutch Drahtlos
 

HB_Bridge and IPSC_Bridge is in same raspberry with mmdvm or different hardware?


Re: NXDNReflector with DVSwitch

JJ Cummings
 

I think that it works well, I need to adjust levels to get the audio a bit cleaner <-> ASL, of course I suspect there is only so much that can be done when emulating, but for emulation it’s decent.   I’d love to help out with dev when I have time but I’m swamped now with ASL work and real life pay the bills work.  

Sent from the iRoad

On Dec 14, 2018, at 17:47, Steve N4IRS <szingman@...> wrote:

Who da thunk it.
Yes, NXDN, D-Star and P25 REQUIRE a gateway.
DMR does not need one.
YSF can use one and it does bring features to the table.

Mike and I have discussed removing the need for P25 and maybe NXDN. We have not decided yet.

Glad I was able to help you get it going.

Steve N4IRS

On 12/14/18 5:20 PM, JJ Cummings wrote:
You are correct sir... I had to undo all of the things that I had monkeyed with to try and make it work before and now it works perfectly!

On Fri, Dec 14, 2018 at 7:50 AM Steve N4IRS <szingman@...> wrote:
If I remember, the defaults in MMDVM_Bridge.ini and the defaults in NXDN_Gateway match up fine.

On 12/14/2018 9:36 AM, JJ Cummings wrote:
So how do I tie NXDNGateway into DVSwitch, I don't even see packets sourcing from DVSwitch toward anything... I'll try it with NXDNGateway in between such as follows and see what happens:

NXDNReflector <-> NXDNGateway <-> DVSwitch etc....

On Fri, Dec 14, 2018 at 7:28 AM Steve N4IRS <szingman@...> wrote:
OK,
Yes it works with YSF. No it does not work with NXDN. You need NXDNGateway.

On 12/14/2018 9:09 AM, JJ Cummings wrote:
I am not, I’m doing what I have with YSFReflector that works.. so 

NXDNReflector <-> DVSwitch <-> Analog_Bridge

Where DVSwitch of course makes the outbound connections to either side etc..

Sent from the iRoad

On Dec 13, 2018, at 23:47, Steve N4IRS <szingman@...> wrote:

Are you running NXDNGateway?




Re: YSF to P25 always return fallbackID

Steve N4IRS
 

Yes,
I plan to consolidate the scripts. Good to hear things are working.

Steve

On 12/14/18 10:08 PM, lazy walker wrote:
I was using the script from
https://github.com/DVSwitch/DVSwitch-System-Builder/blob/master/Directories/usr/local/sbin/DMRIDUpdateBM.sh,
it pulled IDs from radioed.net

$/etc/cron.daily# vi DMRIDUpdateBM
# Generate new file
curl 'https://www.radioid.net/static/users.csv' 2>/dev/null | sed -e
's/[[:space:]]\+/ /g' > ${DMRIDFILE}

the format of this Id file is
$ head /var/lib/mmdvm/DMRIds.dat
Radio ID,Callsign,Name,City,State,Country,Remarks
1023001,VE3THW,Wayne Edward,Toronto,Ontario,Canada,DMR
1023002,VA3ECM,Mathieu Goulet,Ottawa-Hull,Quebec,Canada,CCS7


while the one from http://registry.dstar.su/dmr/DMRIds.php is
# Call ID Call Alias
2 LW1EOI Luis Mario
24001 SM6TKT Claes

there are different.

so i pull off the second one and give it a try, and it works!
may be you should update the script of DVSwitch-System-Builder?

because all service(p25gateway, p25reflector, etc..) are sharing the
same DMRIds, I wonder which format of DMDIds.dat will serve them all.

Tnx


On Sat, Dec 15, 2018 at 9:12 AM Steve N4IRS <szingman@msgstor.com> wrote:
Check the script and make sure it is pulling from here:
<http://registry.dstar.su/dmr/DMRIds.php>

On 12/14/18 8:03 PM, lazy walker wrote:
Yep but i think it’s fresh because the cron job just download it 2 hours ago :)

$ /var/lib/mmdvm# ls -l
total 12704
-rw-r--r-- 1 root root 6348707 Dec 15 06:26 DMRIds.dat
-rw-r--r-- 1 root root 6343785 Dec 15 06:25 DMRIds.dat.151218

On Dec 15, 2018, at 08:57, Steve N4IRS <szingman@msgstor.com> wrote:

Looks right. I will do some local testing this week. You might try to removed the datafile and download a fresh copy.

Steve

On 12/14/18 7:52 PM, lazy walker wrote:
Here is mine >
I: 2018-12-14 16:28:19.781 DMR Id Lookups
I: 2018-12-14 16:28:19.781 File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-14 16:28:19.781 Reload: 24 hours
I: 2018-12-14 16:28:19.874 Loaded 116072 Ids to the DMR callsign lookup table
I: 2018-12-14 16:28:19.874 YSF RF Parameters

On Sat, Dec 15, 2018 at 8:43 AM Steve N4IRS <szingman@msgstor.com> wrote:
Check when MMDVM_Bridge starts up. You should see this in the log:
I: 2018-12-02 11:33:12.161 DMR Id Lookups
I: 2018-12-02 11:33:12.161 File: /var/lib/mmdvm/DMRIds.dat
I: 2018-12-02 11:33:12.161 Reload: 24 hours
I: 2018-12-02 11:33:12.690 Loaded 117442 Ids to the DMR callsign lookup table
I: 2018-12-02 11:33:12.690 P25 RF Parameters
I: 2018-12-02 11:33:12.690 Started the DMR Id lookup reload thread

I bolded the 2 important entries. Check yours.

Steve N4IRS


On 12/14/18 7:33 PM, lazy walker wrote:

Hi Steve,
Yes i'm pretty sure we have the DmrId.dat file right :

grep BD7MQB /var/lib/mmdvm/DMRIds.dat
4607133,BD7MQB,Michael Changzhi Cai,Shenzhen/Guangdong,Hu Nan Guang
Dong Guang Xi,China,DMR


On Sat, Dec 15, 2018 at 12:18 AM Steve N4IRS <szingman@msgstor.com> wrote:

Please check MMDVM_Bridge.ini for:
[DMR Id Lookup]
File=/var/lib/mmdvm/DMRIds.dat

Make sure that points to a valid ID file
Then make sure it contains a ID:
grep BD7MQB /var/lib/mmdvm/DMRIds.dat

Steve N4IRS

On 12/14/2018 10:37 AM, lazy walker wrote:

I: 2018-12-14 15:27:35.370 YSF, Lookup call BD7MQB returned id 0 -> 1234567







7001 - 7020 of 9595