Date   

talker alias

Patrick Perdue
 

Hello:

I would like to pass talker alias from DVSwitch through hblink to connected peers on the bridge. Mike, N4IRR, tells me that MMDVM_Bridge from DVSwitch should be doing this already. My version of hblink3 is pretty old (late 2019 or so, I think). Do current versions support passthrough of talker alias? Which fork should I use? There seem to be quite a few.

Thanks and 73

N2DYI


Re: Connecting to two XLX reflectors #hblink

GB7NR Support
 

Hi, it works well! One thing HBLink works well in is peers and XLX links! Proper homebrew MMDVM outbound connections! We have many connected without flaw or issue and transcoding does not matter if connecting via a DMR connection anyway :) Plus you have full control of the connection!

Example it works..

HBLink under a docker container running Bullseye (OBP Master)

Shane 
M0VUB

On 23 Aug 2022, at 02:07, W8DSB <w8dsb@...> wrote:

Thanks, changing the 54004 to 54005 was my issue. I have two XLX connected now.


Re: Connecting to two XLX reflectors #hblink

W8DSB
 

Thanks, changing the 54004 to 54005 was my issue. I have two XLX connected now.


Re: Connecting to two XLX reflectors #hblink

Patrick Perdue
 

You're probably best actually using XLX Interlink, not HBlink for that, though I think you'd still need AMBE encoders connected to all modules on both reflectors you want to have transcoding.

I don't really mess with DMR/YSF/DSTAR anymore in favor of Allstar, so I could be wrong about that. I've never done an interlink with transcoding hardware only on one of the two reflectors.



On 8/22/2022 6:18 PM, W8DSB wrote:
The issue with using interlink it seems to link the two DSTAR's together and the DMR is only one way because only one end has the AMBE chips....none of the YSF go back and forth. Unless I am doing something wrong that's what I get using that system.

My hope is I can link the two XLX together using HBLINK which is DMR which in turn should link all modes on DSTAR, DMR, YSF < == > DMR and YSF (Then disable DSTAR on this end in the cloud).


Re: Connecting to two XLX reflectors #hblink

GB7NR Support
 

Hi, yes, you do. Make sure that this “local” port is unique to any other port on the local HBLink instance.

Ascend you ports like 54001 54002

Make peer ports +100 away from your master local ports like this 

Master ports 54000-54099
Peer ports 54100-54199
XLX ports 54200-54299
OBP ports 62035-62135

Etc etc…

You can connect many XLX reflectors with HBLink as long as you make sure your ports are organised :) 

Shane 
M0VUB

On 22 Aug 2022, at 23:10, W8DSB <w8dsb@...> wrote:

Can one connect to two different XLX reflectors?

This first one I have been connected to for many years but when I added a second one the system would not start up:

[XLX982b]
MODE: XLXPEER
ENABLED: True
LOOSE: True
EXPORT_AMBE: False
IP: 
PORT: 54004
MASTER_IP: x.x.x.x
MASTER_PORT: 62030
PASSPHRASE: xxxxx
CALLSIGN: W8LRK
RADIO_ID: 3159806
RX_FREQ: 434300000
TX_FREQ: 434300000
TX_POWER: 1
COLORCODE: 1
SLOTS: 2
LATITUDE: 42.592782
LONGITUDE: -083.86818
HEIGHT: 330
LOCATION: Howell, USA
DESCRIPTION: LARK
URL: www.w8lrk.org
SOFTWARE_ID: 20170620
PACKAGE_ID: MMDVM_HBlink
GROUP_HANGTIME: 1
XLXMODULE: 4002
USE_ACL: True
SUB_ACL: DENY:1
TGID_TS1_ACL: DENY:ALL
TGID_TS2_ACL: PERMIT:9,311887

When I added the second one I changed the name and Master IPaddress. I am not sure where the 54004 came from and I am not sure if I need to change it like I did in the MASTER INSTANCES.


Re: Connecting to two XLX reflectors #hblink

W8DSB
 

The issue with using interlink it seems to link the two DSTAR's together and the DMR is only one way because only one end has the AMBE chips....none of the YSF go back and forth. Unless I am doing something wrong that's what I get using that system.

My hope is I can link the two XLX together using HBLINK which is DMR which in turn should link all modes on DSTAR, DMR, YSF < == > DMR and YSF (Then disable DSTAR on this end in the cloud).


Re: Connecting to two XLX reflectors #hblink

Patrick Perdue
 

I've never attempted to link up to more than one XLX reflector with HBlink, but I'd think a better way to do that would be to use XLX Interlink between the two reflectors, unless you don't want to create a permanent link between two modules, E.G. an on-demand situation triggered by a talkgroup.

Regarding 54004, that's a local UDP port, and yes, you'd need to change that for other peers.


On 8/22/2022 6:10 PM, W8DSB wrote:
Can one connect to two different XLX reflectors?

This first one I have been connected to for many years but when I added a second one the system would not start up:

[XLX982b]
MODE: XLXPEER
ENABLED: True
LOOSE: True
EXPORT_AMBE: False
IP: 
PORT: 54004
MASTER_IP: x.x.x.x
MASTER_PORT: 62030
PASSPHRASE: xxxxx
CALLSIGN: W8LRK
RADIO_ID: 3159806
RX_FREQ: 434300000
TX_FREQ: 434300000
TX_POWER: 1
COLORCODE: 1
SLOTS: 2
LATITUDE: 42.592782
LONGITUDE: -083.86818
HEIGHT: 330
LOCATION: Howell, USA
DESCRIPTION: LARK
SOFTWARE_ID: 20170620
PACKAGE_ID: MMDVM_HBlink
GROUP_HANGTIME: 1
XLXMODULE: 4002
USE_ACL: True
SUB_ACL: DENY:1
TGID_TS1_ACL: DENY:ALL
TGID_TS2_ACL: PERMIT:9,311887

When I added the second one I changed the name and Master IPaddress. I am not sure where the 54004 came from and I am not sure if I need to change it like I did in the MASTER INSTANCES.


Connecting to two XLX reflectors #hblink

W8DSB
 

Can one connect to two different XLX reflectors?

This first one I have been connected to for many years but when I added a second one the system would not start up:

[XLX982b]
MODE: XLXPEER
ENABLED: True
LOOSE: True
EXPORT_AMBE: False
IP: 
PORT: 54004
MASTER_IP: x.x.x.x
MASTER_PORT: 62030
PASSPHRASE: xxxxx
CALLSIGN: W8LRK
RADIO_ID: 3159806
RX_FREQ: 434300000
TX_FREQ: 434300000
TX_POWER: 1
COLORCODE: 1
SLOTS: 2
LATITUDE: 42.592782
LONGITUDE: -083.86818
HEIGHT: 330
LOCATION: Howell, USA
DESCRIPTION: LARK
URL: www.w8lrk.org
SOFTWARE_ID: 20170620
PACKAGE_ID: MMDVM_HBlink
GROUP_HANGTIME: 1
XLXMODULE: 4002
USE_ACL: True
SUB_ACL: DENY:1
TGID_TS1_ACL: DENY:ALL
TGID_TS2_ACL: PERMIT:9,311887

When I added the second one I changed the name and Master IPaddress. I am not sure where the 54004 came from and I am not sure if I need to change it like I did in the MASTER INSTANCES.


HBNET no OBP connect

Paul on6dp
 

Hi,
I have installed the HBNET and configured the OBP
I would like create an OBP between HBLink and HBnet server
On HBNet server I have a problem with OBP
 In place of connection i have this
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)
('161.97.169.233', 62996)


And no connection to OBP
Where is my mistake

73 Paul


Re: Hblink3 rules.py

Bob kc2cwt
 

You would think that there would be some type of wild card that would allow you to pass everything through.

Bob KC2CWT
Carmel NY 10512
(914) 497-5502

On June 3, 2022 11:13:42 AM Bob kc2cwt <kc2cwt@...> wrote:

I'm trying to avoid adding a line for everything or actually two lines cuz I may be passing more than 12 talk groups through this

Bob KC2CWT
Carmel NY 10512
(914) 497-5502

On June 3, 2022 10:58:52 AM "Michael Karp" <kn4kcw@...> wrote:

[Edited Message Follows]

As far as I know, it is not possible.

you have to create individual stanzas for each TG.

however, if all repeaters/hotspots are joining the same master, it should pass the traffic to all members that are joined to the same master



Re: Hblink3 rules.py

Bob kc2cwt
 

I'm trying to avoid adding a line for everything or actually two lines cuz I may be passing more than 12 talk groups through this

Bob KC2CWT
Carmel NY 10512
(914) 497-5502

On June 3, 2022 10:58:52 AM "Michael Karp" <kn4kcw@...> wrote:

[Edited Message Follows]

As far as I know, it is not possible.

you have to create individual stanzas for each TG.

however, if all repeaters/hotspots are joining the same master, it should pass the traffic to all members that are joined to the same master


Re: Hblink3 rules.py

Michael Karp
 
Edited

As far as I know, it is not possible.

you have to create individual stanzas for each TG.

however, if all repeaters/hotspots are joining the same master, it should pass the traffic to all members that are joined to the same master


Hblink3 rules.py

Bob kc2cwt
 

Good morning all,
is thair a way in the rules.py to pass All TG 
I tryed this below with the ALL and * and its did work 
thank you 

 'DMRSE1': [
{'SYSTEM': 'MASTER-DMRSE-1', 'TS': 1, 'TGID':ALL, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [98,], 'OFF': [99,], 'RESET': []},
{'SYSTEM': 'FIRST-COAST', 'TS': 1, 'TGID':ALL, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [98,], 'OFF': [99,], 'RESET': []},
],
'DMRSE2': [
{'SYSTEM': 'MASTER-DMRSE-1', 'TS': 2, 'TGID':ALL, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [98,], 'OFF': [99,], 'RESET': []},
{'SYSTEM': 'FIRST-COAST', 'TS': 2, 'TGID':ALL, 'ACTIVE': True, 'TIMEOUT': 2, 'TO_TYPE': 'NONE', 'ON': [98,], 'OFF': [99,], 'RESET': []},
], 
Bob KC2CWT
Carmel NY 10512
(914) 497-5502


Re: HBLINK service won't come up after server went down #hblink

Alejandro Pereida
 

It worked! thanks for the advice

73 de N2IX Alex

On 5/19/22 07:46, Eric-K6KWB wrote:
Looks like you're missing the value, check your your  subscriber.json file and other with .json file download a new one if necessary.

May 18 22:13:46 servidor.xe2dnn.org python3[2610]: raise JSONDecodeError("Expecting value", s, err.value) from None
May 18 22:13:46 servidor.xe2dnn.org python3[2610]: json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

best,
Eric


Re: HBLINK service won't come up after server went down #hblink

Eric-K6KWB
 

Looks like you're missing the value, check your your  subscriber.json file and other with .json file download a new one if necessary.

May 18 22:13:46 servidor.xe2dnn.org python3[2610]: raise JSONDecodeError("Expecting value", s, err.value) from None
May 18 22:13:46 servidor.xe2dnn.org python3[2610]: json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

best,
Eric


HBLINK service won't come up after server went down #hblink

Alejandro Pereida
 

I went to vacation, came back to my shack after a week to find my Centos server off, UPS was also off, so I turned all on again, server came up but hblink.service didn't: the error while trying
to start the service is:

[root@servidor log]# systemctl status hblink.service
● hblink.service - HBlink DMR server
   Loaded: loaded (/usr/lib/systemd/system/hblink.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2022-05-18 22:13:46 PDT; 9s ago
  Process: 2610 ExecStart=/usr/bin/python3 /data0/hblink3-master/bridge.py (code=exited, status=1/FAILURE)
 Main PID: 2610 (code=exited, status=1/FAILURE)
 
May 18 22:13:46 servidor.xe2dnn.org python3[2610]: File "/usr/lib64/python3.6/json/__init__.py", line 354, in loads
May 18 22:13:46 servidor.xe2dnn.org python3[2610]: return _default_decoder.decode(s)
May 18 22:13:46 servidor.xe2dnn.org python3[2610]: File "/usr/lib64/python3.6/json/decoder.py", line 339, in decode
May 18 22:13:46 servidor.xe2dnn.org python3[2610]: obj, end = self.raw_decode(s, idx=_w(s, 0).end())
May 18 22:13:46 servidor.xe2dnn.org python3[2610]: File "/usr/lib64/python3.6/json/decoder.py", line 357, in raw_decode
May 18 22:13:46 servidor.xe2dnn.org python3[2610]: raise JSONDecodeError("Expecting value", s, err.value) from None
May 18 22:13:46 servidor.xe2dnn.org python3[2610]: json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
May 18 22:13:46 servidor.xe2dnn.org systemd[1]: hblink.service: main process exited, code=exited, status=1/FAILURE
May 18 22:13:46 servidor.xe2dnn.org systemd[1]: Unit hblink.service entered failed state.
May 18 22:13:46 servidor.xe2dnn.org systemd[1]: hblink.service failed

Any ideas what went wrong and how to correct it?
Thanks in advance

Alex N2IX


Re: force talker alias from HBlink

Vincenzo
 

hi,
okay thanks to you

73 IU7HAL

Il giorno mer 27 apr 2022 alle ore 21:28 Patrick Perdue <borrisinabox@...> ha scritto:
Hi:

Just wondering if it's possible to force talker alias to callsign using
the master DMR ID database if no talker alias is present. Specifically,
I'm thinking of a situation wherein Allstar via
DVSwitch/Analog_Reflector is connected to TGIF through HBlink.
Analog_Reflector is passing a callsign from Asterisk ami, to
MMDVM_Bridge, then to HBlink. I want the callsign to display on radios
instead of the DMR ID if that ID is not in the local radio database.

Thanks and 73

N2DYI







force talker alias from HBlink

Patrick Perdue
 

Hi:

Just wondering if it's possible to force talker alias to callsign using the master DMR ID database if no talker alias is present. Specifically, I'm thinking of a situation wherein Allstar via DVSwitch/Analog_Reflector is connected to TGIF through HBlink. Analog_Reflector is passing a callsign from Asterisk ami, to MMDVM_Bridge, then to HBlink. I want the callsign to display on radios instead of the DMR ID if that ID is not in the local radio database.

Thanks and 73

N2DYI


Re: Hblink Stopped working...

GB7NR Support
 

Hi, happy days :) 

Shane 
M0VUB 

On 16 Apr 2022, at 01:17, Steve Siesel [K4KSA] <steve@...> wrote:


Thanks! That was it....Removed the file and all is good now.

Steve

On Fri, Apr 15, 2022 at 5:58 PM GB7NR Support <support@...> wrote:
Hi, 

looks like a corrupt JSON file upon auto download. Let’s see the output from your log file on that time stamp, just the snippet from the start of the error to the end will do.

 You will need to probably delete the JSON files that are automatically downloaded. These are “peer_ids.json”, “subscriber_ids.json”,” etc etc. Normally these are pulled from radioID when TRY_DOWNLOAD: True is enabled in hblink.cfg. Obviously by the looks of it one of these has failed or part downloaded and corrupted one of them. HBLink has failed to read this and thrown a decode error.. also make sure your “talkgroup_ids.json” has been edited with the correct syntax for JSON format. 

Try deleting “peer_ids.json” & “subscriber_ids.json” and restarting the service!

Shane 
M0VUB 

On 15 Apr 2022, at 21:42, Steve Siesel [K4KSA] <steve@...> wrote:



 

All,

 

I am getting the following after trying to start HBlink3

 

I don’t think I messed with anything….any thoughts?

 

● hblink.service - Start HBLink

   Loaded: loaded (/lib/systemd/system/hblink.service; enabled; vendor preset: enabled)

   Active: failed (Result: exit-code) since Fri 2022-04-15 16:29:10 EDT; 45s ago

  Process: 472 ExecStart=/usr/bin/python3 /opt/HBlink3/bridge.py (code=exited, status=1/FAILURE)

Main PID: 472 (code=exited, status=1/FAILURE)

 

Apr 15 16:29:10 fldmr python3[472]:   File "/usr/lib/python3.5/json/__init__.py", line 319, in loads

Apr 15 16:29:10 fldmr python3[472]:     return _default_decoder.decode(s)

Apr 15 16:29:10 fldmr python3[472]:   File "/usr/lib/python3.5/json/decoder.py", line 339, in decode

Apr 15 16:29:10 fldmr python3[472]:     obj, end = self.raw_decode(s, idx=_w(s, 0).end())

Apr 15 16:29:10 fldmr python3[472]:   File "/usr/lib/python3.5/json/decoder.py", line 357, in raw_decode

Apr 15 16:29:10 fldmr python3[472]:     raise JSONDecodeError("Expecting value", s, err.value) from None

Apr 15 16:29:10 fldmr python3[472]: json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Apr 15 16:29:10 fldmr systemd[1]: hblink.service: Main process exited, code=exited, status=1/FAILURE

Apr 15 16:29:10 fldmr systemd[1]: hblink.service: Unit entered failed state.

Apr 15 16:29:10 fldmr systemd[1]: hblink.service: Failed with result 'exit-code'.

root@fldmr:/home/k4ksa#

 

 

Steve

 


Re: Hblink Stopped working...

Steve Siesel [K4KSA]
 

Thanks! That was it....Removed the file and all is good now.

Steve


On Fri, Apr 15, 2022 at 5:58 PM GB7NR Support <support@...> wrote:
Hi, 

looks like a corrupt JSON file upon auto download. Let’s see the output from your log file on that time stamp, just the snippet from the start of the error to the end will do.

 You will need to probably delete the JSON files that are automatically downloaded. These are “peer_ids.json”, “subscriber_ids.json”,” etc etc. Normally these are pulled from radioID when TRY_DOWNLOAD: True is enabled in hblink.cfg. Obviously by the looks of it one of these has failed or part downloaded and corrupted one of them. HBLink has failed to read this and thrown a decode error.. also make sure your “talkgroup_ids.json” has been edited with the correct syntax for JSON format. 

Try deleting “peer_ids.json” & “subscriber_ids.json” and restarting the service!

Shane 
M0VUB 

On 15 Apr 2022, at 21:42, Steve Siesel [K4KSA] <steve@...> wrote:



 

All,

 

I am getting the following after trying to start HBlink3

 

I don’t think I messed with anything….any thoughts?

 

● hblink.service - Start HBLink

   Loaded: loaded (/lib/systemd/system/hblink.service; enabled; vendor preset: enabled)

   Active: failed (Result: exit-code) since Fri 2022-04-15 16:29:10 EDT; 45s ago

  Process: 472 ExecStart=/usr/bin/python3 /opt/HBlink3/bridge.py (code=exited, status=1/FAILURE)

Main PID: 472 (code=exited, status=1/FAILURE)

 

Apr 15 16:29:10 fldmr python3[472]:   File "/usr/lib/python3.5/json/__init__.py", line 319, in loads

Apr 15 16:29:10 fldmr python3[472]:     return _default_decoder.decode(s)

Apr 15 16:29:10 fldmr python3[472]:   File "/usr/lib/python3.5/json/decoder.py", line 339, in decode

Apr 15 16:29:10 fldmr python3[472]:     obj, end = self.raw_decode(s, idx=_w(s, 0).end())

Apr 15 16:29:10 fldmr python3[472]:   File "/usr/lib/python3.5/json/decoder.py", line 357, in raw_decode

Apr 15 16:29:10 fldmr python3[472]:     raise JSONDecodeError("Expecting value", s, err.value) from None

Apr 15 16:29:10 fldmr python3[472]: json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Apr 15 16:29:10 fldmr systemd[1]: hblink.service: Main process exited, code=exited, status=1/FAILURE

Apr 15 16:29:10 fldmr systemd[1]: hblink.service: Unit entered failed state.

Apr 15 16:29:10 fldmr systemd[1]: hblink.service: Failed with result 'exit-code'.

root@fldmr:/home/k4ksa#

 

 

Steve

 

21 - 40 of 2790