Date   

Re: Current status DMRlink, HBlink DVSwitch

Steve N4IRS
 

Matthew,
Thank you for the captures and comments. That's consistent with what we think are the inconstancy of HB Protocol. The published document, The source code without comments and multiple servers do it "their way" Maybe a effort to create a true protocol document would be worthwhile. Something that actually documents what is happening. We could use it to convince the different parties to come to some agreement.  

Thanks, Steve

--
The nice thing about standards is that there are so many to choose from!


On 10/2/2017 7:12 PM, Matthew 2E0SIP wrote:

Hi Steve,

Heres the login details for XLX950-

Address=xlx950.epf.lu
Port=62030
Password=passw0rd

I performed some packet captures direct from MMDVMHost and it looks as though XLX950 is not returning the Repeater ID after the RPTACK. I've checked the source and it doesn't look like MMDVMHost or DMRGateway are validating the repeater ID but HBLink is, causing it to fail. Interestingly enough, DMRGateway does include the Repeater ID when it ACK's the MMDVMHost login. 


I've attached the packet captures-

mmdvm_bm.pcap (successful BM login, showing RPTACK with Repeater ID)

mmdvm_xlx.pcap (succesfull XLX login, showing RPTACK without Repeater ID)

 

I guess to be inline with MMDVMHost and DMRGateway, HBlink shouldn't validate the repeater ID when it receives an RTPACK from a master, but should include the ID when it sends a RPTACK to a master.

I hope that helps,

Matthew

2E0SIP



Re: Current status DMRlink, HBlink DVSwitch

david bencini ik5xmk
 

Hi Steve and all, 

i've a dedicated MMDVM DMR RPT to connect our XLX reflector,

this is MMDVM.ini configuration for DMR section to use DMRGateway software:


[DMR Network]
Enable=1
Address=127.0.0.1
Port=62031
Jitter=300
Local=62032
Password=passw0rd
Options=
Slot1=1
Slot2=1
Debug=0

This is DMRGateway.ini configuration, to connect XLX039 for trascoding module B (Italy (TG 4002 to link and TG 222 to speak)) on SLOT 1 and XLX077 (Module R (4018 and TG 22251 to speak), Tuscany Region) on SLOT 2 


[General]
Timeout=10
RptAddress=127.0.0.1
RptPort=62032
LocalAddress=127.0.0.1
LocalPort=62031
RuleTrace=0
Daemon=0
Debug=0

[XLX Network 1]
#*************************************
# CONNESSIONE SLOT 1 A NAZIONALE DSTAR
#*************************************
Enabled=1
Name=XLX039
Port=62030
Slot=1
TG=222
Base=4000
Startup=4002
Relink=10
Password=passw0rd
Debug=0

[XLX Network 2]
#***************************************
# CONNESSIONE SLOT 2 A REGIONALE R DSTAR
#***************************************
Enabled=1
Name=XLX077
Port=62030
Slot=2
TG=22251
Startup=4018
Relink=10
Password=passw0rd
Debug=0

All is working very well, with a good audio (using 2 ThumbDV USB to transcode).

Our RPT dashboard: http://185.109.24.70:8080/


Our DMR MASTER (where i do tests) dashboard: http://dmrmaster.grupporadiofirenze.net/

Thank you

David IK5XMK



2017-10-02 23:55 GMT+02:00 Steve N4IRS <szingman@...>:

David,
That was as I expected. We are looking at this. I will say that the HBlink client instance has no trouble connecting to BM, DMR Master, DMRGateway and HBlink server instance. We are still going to see if we can isolate the issue. I do have a request, to make our lives easier can someone supply us with the login info needed to connect to a existing XLX DMR?

Thanks, Steve N4IRS

On 10/02/2017 06:24 AM, david bencini ik5xmk wrote:
Hi Steve,

i'm making some tests, to dmr master server no problem to connect to, 
but on xlx side i've this error:

DEBUG 2017-10-02 06:13:39,719 Logging system started, anything from here on gets logged
INFO 2017-10-02 06:13:39,720 HBlink 'HBlink.py' (c) 2016 N0MJS & the K0USY Group - SYSTEM STARTING...
DEBUG 2017-10-02 06:13:39,721 (REPEATER-1) Client maintenance loop started
INFO 2017-10-02 06:13:39,722 (REPEATER-1) Sending login request to master 185.203.118.66:55555
DEBUG 2017-10-02 06:13:39,722 CLIENT instance created: REPEATER-1, <__main__.HBSYSTEM instance at 0x7fbf0433aab8>
DEBUG 2017-10-02 06:13:39,723 (REPEATER-2) Client maintenance loop started
INFO 2017-10-02 06:13:39,723 (REPEATER-2) Sending login request to master 5.249.151.111:62030
DEBUG 2017-10-02 06:13:39,723 CLIENT instance created: REPEATER-2, <__main__.HBSYSTEM instance at 0x7fbf040fb878>
INFO 2017-10-02 06:13:39,724 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 2225069
INFO 2017-10-02 06:13:39,725 (REPEATER-1) Repeater Authentication Accepted
INFO 2017-10-02 06:13:39,725 (REPEATER-1) Repeater Configuration Sent
DEBUG 2017-10-02 06:13:39,726 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 1
INFO 2017-10-02 06:13:39,727 (REPEATER-1) Repeater Configuration Accepted
INFO 2017-10-02 06:13:39,727 (REPEATER-1) Connection to Master Completed
INFO 2017-10-02 06:13:39,768 (REPEATER-2) Repeater Login ACK Received with 32bit ID: 1228258867
ERROR 2017-10-02 06:13:39,813 (REPEATER-2) Master ACK Contained wrong ID - Connection Reset




Re: Current status DMRlink, HBlink DVSwitch

Matthew 2E0SIP
 

Hi Steve,

Heres the login details for XLX950-

Address=xlx950.epf.lu
Port=62030
Password=passw0rd

I performed some packet captures direct from MMDVMHost and it looks as though XLX950 is not returning the Repeater ID after the RPTACK. I've checked the source and it doesn't look like MMDVMHost or DMRGateway are validating the repeater ID but HBLink is, causing it to fail. Interestingly enough, DMRGateway does include the Repeater ID when it ACK's the MMDVMHost login. 


I've attached the packet captures-

mmdvm_bm.pcap (successful BM login, showing RPTACK with Repeater ID)

mmdvm_xlx.pcap (succesfull XLX login, showing RPTACK without Repeater ID)

 

I guess to be inline with MMDVMHost and DMRGateway, HBlink shouldn't validate the repeater ID when it receives an RTPACK from a master, but should include the ID when it sends a RPTACK to a master.

I hope that helps,

Matthew

2E0SIP


Re: Current status DMRlink, HBlink DVSwitch

Steve N4IRS
 

David,
That was as I expected. We are looking at this. I will say that the HBlink client instance has no trouble connecting to BM, DMR Master, DMRGateway and HBlink server instance. We are still going to see if we can isolate the issue. I do have a request, to make our lives easier can someone supply us with the login info needed to connect to a existing XLX DMR?

Thanks, Steve N4IRS

On 10/02/2017 06:24 AM, david bencini ik5xmk wrote:
Hi Steve,

i'm making some tests, to dmr master server no problem to connect to, 
but on xlx side i've this error:

DEBUG 2017-10-02 06:13:39,719 Logging system started, anything from here on gets logged
INFO 2017-10-02 06:13:39,720 HBlink 'HBlink.py' (c) 2016 N0MJS & the K0USY Group - SYSTEM STARTING...
DEBUG 2017-10-02 06:13:39,721 (REPEATER-1) Client maintenance loop started
INFO 2017-10-02 06:13:39,722 (REPEATER-1) Sending login request to master 185.203.118.66:55555
DEBUG 2017-10-02 06:13:39,722 CLIENT instance created: REPEATER-1, <__main__.HBSYSTEM instance at 0x7fbf0433aab8>
DEBUG 2017-10-02 06:13:39,723 (REPEATER-2) Client maintenance loop started
INFO 2017-10-02 06:13:39,723 (REPEATER-2) Sending login request to master 5.249.151.111:62030
DEBUG 2017-10-02 06:13:39,723 CLIENT instance created: REPEATER-2, <__main__.HBSYSTEM instance at 0x7fbf040fb878>
INFO 2017-10-02 06:13:39,724 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 2225069
INFO 2017-10-02 06:13:39,725 (REPEATER-1) Repeater Authentication Accepted
INFO 2017-10-02 06:13:39,725 (REPEATER-1) Repeater Configuration Sent
DEBUG 2017-10-02 06:13:39,726 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 1
INFO 2017-10-02 06:13:39,727 (REPEATER-1) Repeater Configuration Accepted
INFO 2017-10-02 06:13:39,727 (REPEATER-1) Connection to Master Completed
INFO 2017-10-02 06:13:39,768 (REPEATER-2) Repeater Login ACK Received with 32bit ID: 1228258867
ERROR 2017-10-02 06:13:39,813 (REPEATER-2) Master ACK Contained wrong ID - Connection Reset



Re: Current status DMRlink, HBlink DVSwitch

david bencini ik5xmk
 

Hi Steve,

i'm making some tests, to dmr master server no problem to connect to, 
but on xlx side i've this error:

DEBUG 2017-10-02 06:13:39,719 Logging system started, anything from here on gets logged
INFO 2017-10-02 06:13:39,720 HBlink 'HBlink.py' (c) 2016 N0MJS & the K0USY Group - SYSTEM STARTING...
DEBUG 2017-10-02 06:13:39,721 (REPEATER-1) Client maintenance loop started
INFO 2017-10-02 06:13:39,722 (REPEATER-1) Sending login request to master 185.203.118.66:55555
DEBUG 2017-10-02 06:13:39,722 CLIENT instance created: REPEATER-1, <__main__.HBSYSTEM instance at 0x7fbf0433aab8>
DEBUG 2017-10-02 06:13:39,723 (REPEATER-2) Client maintenance loop started
INFO 2017-10-02 06:13:39,723 (REPEATER-2) Sending login request to master 5.249.151.111:62030
DEBUG 2017-10-02 06:13:39,723 CLIENT instance created: REPEATER-2, <__main__.HBSYSTEM instance at 0x7fbf040fb878>
INFO 2017-10-02 06:13:39,724 (REPEATER-1) Repeater Login ACK Received with 32bit ID: 2225069
INFO 2017-10-02 06:13:39,725 (REPEATER-1) Repeater Authentication Accepted
INFO 2017-10-02 06:13:39,725 (REPEATER-1) Repeater Configuration Sent
DEBUG 2017-10-02 06:13:39,726 (REPEATER-1) MSTPONG Received. Pongs Since Connected: 1
INFO 2017-10-02 06:13:39,727 (REPEATER-1) Repeater Configuration Accepted
INFO 2017-10-02 06:13:39,727 (REPEATER-1) Connection to Master Completed
INFO 2017-10-02 06:13:39,768 (REPEATER-2) Repeater Login ACK Received with 32bit ID: 1228258867
ERROR 2017-10-02 06:13:39,813 (REPEATER-2) Master ACK Contained wrong ID - Connection Reset
DEBUG 2017-10-02 06:13:44,725 (REPEATER-1) Client maintenance loop started
DEBUG 2017-10-02 06:13:44,726 (REPEATER-1) RPTPING Sent to Master. Pings Since Connected: 1
DEBUG 2017-10-02 06:13:44,726 (REPEATER-2) Client maintenance loop started
INFO 2017-10-02 06:13:44,726 (REPEATER-2) Sending login request to master 5.249.151.111:62030
INFO 2017-10-02 06:13:44,771 (REPEATER-2) Repeater Login ACK Received with 32bit ID: 1228258867
ERROR 2017-10-02 06:13:44,816 (REPEATER-2) Master ACK Contained wrong ID - Connection Reset
^CINFO 2017-10-02 06:13:45,300 SHUTDOWN: HBLINK IS TERMINATING WITH SIGNAL 2
INFO 2017-10-02 06:13:45,300 SHUTDOWN: DE-REGISTER SYSTEM: REPEATER-1
INFO 2017-10-02 06:13:45,301 (REPEATER-1) De-Registeration sent to Master: 185.203.118.66:55555
INFO 2017-10-02 06:13:45,301 SHUTDOWN: DE-REGISTER SYSTEM: REPEATER-2
INFO 2017-10-02 06:13:45,302 (REPEATER-2) De-Registeration sent to Master: 5.249.151.111:62030
INFO 2017-10-02 06:13:45,302 SHUTDOWN: ALL SYSTEM HANDLERS EXECUTED - STOPPING REACTOR

form xlx log:

root@superciuk:~# tail -f /var/log/messages
Oct  2 12:19:55 superciuk xlxd: DMRmmdvm connect packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:19:55 superciuk xlxd: DMRmmdvm authentication packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:00 superciuk xlxd: DMRmmdvm connect packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:00 superciuk xlxd: DMRmmdvm authentication packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:05 superciuk xlxd: DMRmmdvm connect packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:05 superciuk xlxd: DMRmmdvm authentication packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:10 superciuk xlxd: DMRmmdvm connect packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:10 superciuk xlxd: DMRmmdvm authentication packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:15 superciuk xlxd: DMRmmdvm connect packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:15 superciuk xlxd: DMRmmdvm authentication packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:20 superciuk xlxd: DMRmmdvm connect packet from IZ5ILG  B at 185.177.59.72
Oct  2 12:20:20 superciuk xlxd: DMRmmdvm authentication packet from IZ5ILG  B at 185.177.59.72

I tried with some callsigns and ids, but i think there is a problem in the code linking to xlx...
can you help me ?

thank you

David






2017-09-29 11:39 GMT+02:00 Steve N4IRS <szingman@...>:

David,
Your next step is to make sure HBlink can login to the 2 servers.
I suggest you test each connection separately by disabling one of the clients.
Rename or copy hblink-SAMPLE.cfg to hblink.cfg.
Run hblink.py in the foreground and watch the console to verify valid login.
You can then reduce the log level by changing LOG_LEVEL: DEBUG to LOG_LEVEL: INFO

Once that works, enable both clients, run hblink.py  and watch the console for errors.
If everything looks good you can run hb_bridge_all.py and test for traffic passing between the 2 servers.

73, Steve N4IRS

 

On 09/29/2017 04:54 AM, david bencini ik5xmk wrote:
Hi Steve, i'm looking for hblink-SAMPLE.cfg to work with this software.

Can you help me to understand how to handle this link?

In practice hblink should be able to connect as mmdvm client to the XLX dstar reflector, so act in configuration in this way?

[REPEATER-1]
MODE: CLIENT
ENABLED: True
EXPORT_AMBE: False
IP:
PORT: 62030
MASTER_PORT: 62030
PASSPHRASE: homebrew
CALLSIGN: IK5XMK
RADIO_ID: 2225013
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 2
...

and then, on the other side, to DMR MASTER server as mmdvm client repeater:


[REPEATER-2]
MODE: CLIENT
ENABLED: True
EXPORT_AMBE: False
IP:
PORT: 55555
MASTER_PORT: 55555
PASSPHRASE: passw0rd
CALLSIGN: IK5XMK
RADIO_ID: 2225013
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 2
...

on [MASTER-1]
ENABLED: False

What else do you need to hblink to work?
Is this a way to think about a collector between the two networks? This is for the first step to try the link...

Thank you,
David

... must i to open a new topic for this?

2017-09-28 21:26 GMT+02:00 Steve N4IRS <szingman@...>:
David,
Since both "endpoints" speak HBR protocol (MMDVM) it might be as simple as using HBlink:
dmrmaster <---> HBlink <---> XLX.
The problem that you might run into that HBlink does omore checking of the source ID. That is where DMRGateway came in.
Cort or Mike may chime in will a more detailed answer. Since it's only software (did I really say that?) It's worth a try. Take it one side at a time and build into the middle.

Steve

On 9/28/2017 3:15 PM, david bencini ik5xmk wrote:
Thank you Steve. It can be a way to try. Good!

At the end (only me ?) i need a software that side A it connects an xlx module (like standard mmdvm repeater) and
side B it connects a dmrmaster server (like standard mmdvm repeater), so when i hit  a TG i can hear me on dstar and viceversa.
Transcoding is fully working on my xlx.
I think (wrong tinking?) that it is not difficult to bring a data flow from a system to other, with same homebrew protocol.

by the way, thank you and best 73 to you and to all guys on group

David IK5XMK

2017-09-28 20:59 GMT+02:00 Steve N4IRS <szingman@...>:
David,
I do not know of a way to connect DMR+, IPSC2 or DMRMaster to XLX. If, and it's a BIG if, IPSC2 can connect to IPSC_Bridge (DMRlink) it might go something like this:
IPSC2 <---> IPSC_Bridge <---> HB_Bridge <---> DMRGateway <---> XLX. I think I remember someone posting that he needed DMRGateway from G4KLX to connect HB_Bridge to XLX.
Sorry I could not be of more help.

73, Steve N4IRS

On 9/28/2017 2:50 PM, david bencini ik5xmk wrote:
Hi Steve, great work !! Thank you.

Please, where can i find informations/which software/configuration about linking my dmr server (dmrmaster.webandcloud.net or ipsc2.webandcloud.net
to my xlx dstar server (http://vpngrf.webandcloud.net/db/dashboard/index.php) that it has an hardware transcoder server (2 USB ThumbDV)  into? I need a dmr flow to put into my
dstar system so i can join my dstar/dmr repeaters in my region. Now i can link my mmdvm repeater directly to xlx via dmrmmdvm protocol, and it works
very well with good audio, but a lot of friends are on dmr servers and i need a "connector" from dmr world to dstar one :)

Thank you for any infos
73, David IK5XMK






Re: DV3000

Bob N1XBM <N1XBM@...>
 

Ya I'm running the older version and ambe_audio.

N1XBM
Apparare Scientor
Paratus Communicare
Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657
www.radioguysrepeaternetwork.com

On Sep 29, 2017 6:48 PM, "Steve N4IRS" <szingman@...> wrote:
Am I correct you are running the older DMRGateway and ambe_audio? Not saying that's it, just making sure what we are looking at.

Steve

On 09/29/2017 06:45 PM, Bob N1XBM wrote:
I noticed when talking from Allstar to BM, when I look at my zum spot running the pi-star image that my loss numbers are quite high. It seems to sound fine. I understand this is not the pi-star group or zum spot, but I've only noticed the problem when talking from analog to dmr.

Anyone eles notice this?

N1XBM
Apparare Scientor
Paratus Communicare
Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657
www.radioguysrepeaternetwork.com


Re: DV3000

Steve N4IRS
 

Am I correct you are running the older DMRGateway and ambe_audio? Not saying that's it, just making sure what we are looking at.

Steve

On 09/29/2017 06:45 PM, Bob N1XBM wrote:
I noticed when talking from Allstar to BM, when I look at my zum spot running the pi-star image that my loss numbers are quite high. It seems to sound fine. I understand this is not the pi-star group or zum spot, but I've only noticed the problem when talking from analog to dmr.

Anyone eles notice this?

N1XBM
Apparare Scientor
Paratus Communicare
Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657
www.radioguysrepeaternetwork.com


DV3000

Bob N1XBM <N1XBM@...>
 

I noticed when talking from Allstar to BM, when I look at my zum spot running the pi-star image that my loss numbers are quite high. It seems to sound fine. I understand this is not the pi-star group or zum spot, but I've only noticed the problem when talking from analog to dmr.

Anyone eles notice this?

N1XBM
Apparare Scientor
Paratus Communicare
Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657
www.radioguysrepeaternetwork.com


Re: Current status DMRlink, HBlink DVSwitch

Steve N4IRS
 

I could not say it any better then Cort. For me it's about open source tools that allow people to control their own destiny. I'n not out to build a giant network and have to admin it. Oh, and "sticking it to the man" ain't so bad either.

DVSwitch is the next logical step in how Partners connect to each other and how that that traffic flows. Nothing giant, just versatile

Steve.  

On 09/29/2017 05:42 PM, Cort N0MJS wrote:
I should be clear.... you CAN build a “network” with our tools. Being lord and master of yet another DMR fiefdom is not part of our plan.

0x49 DE N0MJS

Sent from my iPhone

On Sep 29, 2017, at 4:00 PM, Cort N0MJS <n0mjs@...> wrote:

I am strongly opposed to single-entity control of networking as it has always been with DMR... because we end up with disparate “networks” fighting over who’s better than the other.

I started DMRlink almost 4.5 years ago with the goal of building tools and knowledge for networking, but not to “build a network”.

0x49 DE N0MJS

Sent from my iPhone

On Sep 29, 2017, at 2:55 PM, Matthew 2E0SIP <groups.io@...> wrote:

Welcome back guys, thanks for your continued efforts.

Out of curiosity, what's the end goal for DVSwitch? Is it intended as a small scale tool for bridging modes and networks, or is the end goal for it to function as a standalone network itself, with 'nodes' distributed globally? 

Thanks

Matthew
2E0SIP

 

 



Re: Current status DMRlink, HBlink DVSwitch

Matthew 2E0SIP
 

Hi Cort,

Thanks for the reply. I'm with you on that, 100%. That said I think there's room for an agnostic, open source and decentralised 'network', perhaps one that merely routes traffic between other entities that can choose themselves what traffic they carry, how the network is accessed etc. Easier said than done I guess.

Unfortunately I think there will always be a need for an impartial 'regulator' to allocate talk groups, DMR IDs and the like.

Cheers
Matthew
2E0SIP


Re: Current status DMRlink, HBlink DVSwitch

Cort N0MJS <n0mjs@...>
 

I should be clear.... you CAN build a “network” with our tools. Being lord and master of yet another DMR fiefdom is not part of our plan.

0x49 DE N0MJS

Sent from my iPhone

On Sep 29, 2017, at 4:00 PM, Cort N0MJS <n0mjs@...> wrote:

I am strongly opposed to single-entity control of networking as it has always been with DMR... because we end up with disparate “networks” fighting over who’s better than the other.

I started DMRlink almost 4.5 years ago with the goal of building tools and knowledge for networking, but not to “build a network”.

0x49 DE N0MJS

Sent from my iPhone

On Sep 29, 2017, at 2:55 PM, Matthew 2E0SIP <groups.io@...> wrote:

Welcome back guys, thanks for your continued efforts.

Out of curiosity, what's the end goal for DVSwitch? Is it intended as a small scale tool for bridging modes and networks, or is the end goal for it to function as a standalone network itself, with 'nodes' distributed globally? 

Thanks

Matthew
2E0SIP

 

 


Re: Current status DMRlink, HBlink DVSwitch

Cort N0MJS <n0mjs@...>
 

I am strongly opposed to single-entity control of networking as it has always been with DMR... because we end up with disparate “networks” fighting over who’s better than the other.

I started DMRlink almost 4.5 years ago with the goal of building tools and knowledge for networking, but not to “build a network”.

0x49 DE N0MJS

Sent from my iPhone

On Sep 29, 2017, at 2:55 PM, Matthew 2E0SIP <groups.io@...> wrote:

Welcome back guys, thanks for your continued efforts.

Out of curiosity, what's the end goal for DVSwitch? Is it intended as a small scale tool for bridging modes and networks, or is the end goal for it to function as a standalone network itself, with 'nodes' distributed globally? 

Thanks

Matthew
2E0SIP

 

 


Re: Current status DMRlink, HBlink DVSwitch

Matthew 2E0SIP
 

Welcome back guys, thanks for your continued efforts.

Out of curiosity, what's the end goal for DVSwitch? Is it intended as a small scale tool for bridging modes and networks, or is the end goal for it to function as a standalone network itself, with 'nodes' distributed globally? 

Thanks

Matthew
2E0SIP

 

 


Re: Current status DMRlink, HBlink DVSwitch

Steve N4IRS
 

David,
Your next step is to make sure HBlink can login to the 2 servers.
I suggest you test each connection separately by disabling one of the clients.
Rename or copy hblink-SAMPLE.cfg to hblink.cfg.
Run hblink.py in the foreground and watch the console to verify valid login.
You can then reduce the log level by changing LOG_LEVEL: DEBUG to LOG_LEVEL: INFO

Once that works, enable both clients, run hblink.py  and watch the console for errors.
If everything looks good you can run hb_bridge_all.py and test for traffic passing between the 2 servers.

73, Steve N4IRS

 

On 09/29/2017 04:54 AM, david bencini ik5xmk wrote:
Hi Steve, i'm looking for hblink-SAMPLE.cfg to work with this software.

Can you help me to understand how to handle this link?

In practice hblink should be able to connect as mmdvm client to the XLX dstar reflector, so act in configuration in this way?

[REPEATER-1]
MODE: CLIENT
ENABLED: True
EXPORT_AMBE: False
IP:
PORT: 62030
MASTER_PORT: 62030
PASSPHRASE: homebrew
CALLSIGN: IK5XMK
RADIO_ID: 2225013
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 2
...

and then, on the other side, to DMR MASTER server as mmdvm client repeater:


[REPEATER-2]
MODE: CLIENT
ENABLED: True
EXPORT_AMBE: False
IP:
PORT: 55555
MASTER_PORT: 55555
PASSPHRASE: passw0rd
CALLSIGN: IK5XMK
RADIO_ID: 2225013
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 2
...

on [MASTER-1]
ENABLED: False

What else do you need to hblink to work?
Is this a way to think about a collector between the two networks? This is for the first step to try the link...

Thank you,
David

... must i to open a new topic for this?

2017-09-28 21:26 GMT+02:00 Steve N4IRS <szingman@...>:
David,
Since both "endpoints" speak HBR protocol (MMDVM) it might be as simple as using HBlink:
dmrmaster <---> HBlink <---> XLX.
The problem that you might run into that HBlink does omore checking of the source ID. That is where DMRGateway came in.
Cort or Mike may chime in will a more detailed answer. Since it's only software (did I really say that?) It's worth a try. Take it one side at a time and build into the middle.

Steve

On 9/28/2017 3:15 PM, david bencini ik5xmk wrote:
Thank you Steve. It can be a way to try. Good!

At the end (only me ?) i need a software that side A it connects an xlx module (like standard mmdvm repeater) and
side B it connects a dmrmaster server (like standard mmdvm repeater), so when i hit  a TG i can hear me on dstar and viceversa.
Transcoding is fully working on my xlx.
I think (wrong tinking?) that it is not difficult to bring a data flow from a system to other, with same homebrew protocol.

by the way, thank you and best 73 to you and to all guys on group

David IK5XMK

2017-09-28 20:59 GMT+02:00 Steve N4IRS <szingman@...>:
David,
I do not know of a way to connect DMR+, IPSC2 or DMRMaster to XLX. If, and it's a BIG if, IPSC2 can connect to IPSC_Bridge (DMRlink) it might go something like this:
IPSC2 <---> IPSC_Bridge <---> HB_Bridge <---> DMRGateway <---> XLX. I think I remember someone posting that he needed DMRGateway from G4KLX to connect HB_Bridge to XLX.
Sorry I could not be of more help.

73, Steve N4IRS

On 9/28/2017 2:50 PM, david bencini ik5xmk wrote:
Hi Steve, great work !! Thank you.

Please, where can i find informations/which software/configuration about linking my dmr server (dmrmaster.webandcloud.net or ipsc2.webandcloud.net
to my xlx dstar server (http://vpngrf.webandcloud.net/db/dashboard/index.php) that it has an hardware transcoder server (2 USB ThumbDV)  into? I need a dmr flow to put into my
dstar system so i can join my dstar/dmr repeaters in my region. Now i can link my mmdvm repeater directly to xlx via dmrmmdvm protocol, and it works
very well with good audio, but a lot of friends are on dmr servers and i need a "connector" from dmr world to dstar one :)

Thank you for any infos
73, David IK5XMK





Re: Current status DMRlink, HBlink DVSwitch

david bencini ik5xmk
 

Hi Steve, i'm looking for hblink-SAMPLE.cfg to work with this software.

Can you help me to understand how to handle this link?

In practice hblink should be able to connect as mmdvm client to the XLX dstar reflector, so act in configuration in this way?

[REPEATER-1]
MODE: CLIENT
ENABLED: True
EXPORT_AMBE: False
IP:
PORT: 62030
MASTER_PORT: 62030
PASSPHRASE: homebrew
CALLSIGN: IK5XMK
RADIO_ID: 2225013
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 2
...

and then, on the other side, to DMR MASTER server as mmdvm client repeater:


[REPEATER-2]
MODE: CLIENT
ENABLED: True
EXPORT_AMBE: False
IP:
PORT: 55555
MASTER_PORT: 55555
PASSPHRASE: passw0rd
CALLSIGN: IK5XMK
RADIO_ID: 2225013
RX_FREQ: 449000000
TX_FREQ: 444000000
TX_POWER: 25
COLORCODE: 1
SLOTS: 2
...

on [MASTER-1]
ENABLED: False

What else do you need to hblink to work?
Is this a way to think about a collector between the two networks? This is for the first step to try the link...

Thank you,
David

... must i to open a new topic for this?

2017-09-28 21:26 GMT+02:00 Steve N4IRS <szingman@...>:

David,
Since both "endpoints" speak HBR protocol (MMDVM) it might be as simple as using HBlink:
dmrmaster <---> HBlink <---> XLX.
The problem that you might run into that HBlink does omore checking of the source ID. That is where DMRGateway came in.
Cort or Mike may chime in will a more detailed answer. Since it's only software (did I really say that?) It's worth a try. Take it one side at a time and build into the middle.

Steve

On 9/28/2017 3:15 PM, david bencini ik5xmk wrote:
Thank you Steve. It can be a way to try. Good!

At the end (only me ?) i need a software that side A it connects an xlx module (like standard mmdvm repeater) and
side B it connects a dmrmaster server (like standard mmdvm repeater), so when i hit  a TG i can hear me on dstar and viceversa.
Transcoding is fully working on my xlx.
I think (wrong tinking?) that it is not difficult to bring a data flow from a system to other, with same homebrew protocol.

by the way, thank you and best 73 to you and to all guys on group

David IK5XMK

2017-09-28 20:59 GMT+02:00 Steve N4IRS <szingman@...>:
David,
I do not know of a way to connect DMR+, IPSC2 or DMRMaster to XLX. If, and it's a BIG if, IPSC2 can connect to IPSC_Bridge (DMRlink) it might go something like this:
IPSC2 <---> IPSC_Bridge <---> HB_Bridge <---> DMRGateway <---> XLX. I think I remember someone posting that he needed DMRGateway from G4KLX to connect HB_Bridge to XLX.
Sorry I could not be of more help.

73, Steve N4IRS

On 9/28/2017 2:50 PM, david bencini ik5xmk wrote:
Hi Steve, great work !! Thank you.

Please, where can i find informations/which software/configuration about linking my dmr server (dmrmaster.webandcloud.net or ipsc2.webandcloud.net
to my xlx dstar server (http://vpngrf.webandcloud.net/db/dashboard/index.php) that it has an hardware transcoder server (2 USB ThumbDV)  into? I need a dmr flow to put into my
dstar system so i can join my dstar/dmr repeaters in my region. Now i can link my mmdvm repeater directly to xlx via dmrmmdvm protocol, and it works
very well with good audio, but a lot of friends are on dmr servers and i need a "connector" from dmr world to dstar one :)

Thank you for any infos
73, David IK5XMK




Re: Current status DMRlink, HBlink DVSwitch

Steve N4IRS
 

David,
Since both "endpoints" speak HBR protocol (MMDVM) it might be as simple as using HBlink:
dmrmaster <---> HBlink <---> XLX.
The problem that you might run into that HBlink does omore checking of the source ID. That is where DMRGateway came in.
Cort or Mike may chime in will a more detailed answer. Since it's only software (did I really say that?) It's worth a try. Take it one side at a time and build into the middle.

Steve

On 9/28/2017 3:15 PM, david bencini ik5xmk wrote:
Thank you Steve. It can be a way to try. Good!

At the end (only me ?) i need a software that side A it connects an xlx module (like standard mmdvm repeater) and
side B it connects a dmrmaster server (like standard mmdvm repeater), so when i hit  a TG i can hear me on dstar and viceversa.
Transcoding is fully working on my xlx.
I think (wrong tinking?) that it is not difficult to bring a data flow from a system to other, with same homebrew protocol.

by the way, thank you and best 73 to you and to all guys on group

David IK5XMK

2017-09-28 20:59 GMT+02:00 Steve N4IRS <szingman@...>:
David,
I do not know of a way to connect DMR+, IPSC2 or DMRMaster to XLX. If, and it's a BIG if, IPSC2 can connect to IPSC_Bridge (DMRlink) it might go something like this:
IPSC2 <---> IPSC_Bridge <---> HB_Bridge <---> DMRGateway <---> XLX. I think I remember someone posting that he needed DMRGateway from G4KLX to connect HB_Bridge to XLX.
Sorry I could not be of more help.

73, Steve N4IRS

On 9/28/2017 2:50 PM, david bencini ik5xmk wrote:
Hi Steve, great work !! Thank you.

Please, where can i find informations/which software/configuration about linking my dmr server (dmrmaster.webandcloud.net or ipsc2.webandcloud.net
to my xlx dstar server (http://vpngrf.webandcloud.net/db/dashboard/index.php) that it has an hardware transcoder server (2 USB ThumbDV)  into? I need a dmr flow to put into my
dstar system so i can join my dstar/dmr repeaters in my region. Now i can link my mmdvm repeater directly to xlx via dmrmmdvm protocol, and it works
very well with good audio, but a lot of friends are on dmr servers and i need a "connector" from dmr world to dstar one :)

Thank you for any infos
73, David IK5XMK



Re: Current status DMRlink, HBlink DVSwitch

david bencini ik5xmk
 

Thank you Steve. It can be a way to try. Good!

At the end (only me ?) i need a software that side A it connects an xlx module (like standard mmdvm repeater) and
side B it connects a dmrmaster server (like standard mmdvm repeater), so when i hit  a TG i can hear me on dstar and viceversa.
Transcoding is fully working on my xlx.
I think (wrong tinking?) that it is not difficult to bring a data flow from a system to other, with same homebrew protocol.

by the way, thank you and best 73 to you and to all guys on group

David IK5XMK

2017-09-28 20:59 GMT+02:00 Steve N4IRS <szingman@...>:

David,
I do not know of a way to connect DMR+, IPSC2 or DMRMaster to XLX. If, and it's a BIG if, IPSC2 can connect to IPSC_Bridge (DMRlink) it might go something like this:
IPSC2 <---> IPSC_Bridge <---> HB_Bridge <---> DMRGateway <---> XLX. I think I remember someone posting that he needed DMRGateway from G4KLX to connect HB_Bridge to XLX.
Sorry I could not be of more help.

73, Steve N4IRS

On 9/28/2017 2:50 PM, david bencini ik5xmk wrote:
Hi Steve, great work !! Thank you.

Please, where can i find informations/which software/configuration about linking my dmr server (dmrmaster.webandcloud.net or ipsc2.webandcloud.net
to my xlx dstar server (http://vpngrf.webandcloud.net/db/dashboard/index.php) that it has an hardware transcoder server (2 USB ThumbDV)  into? I need a dmr flow to put into my
dstar system so i can join my dstar/dmr repeaters in my region. Now i can link my mmdvm repeater directly to xlx via dmrmmdvm protocol, and it works
very well with good audio, but a lot of friends are on dmr servers and i need a "connector" from dmr world to dstar one :)

Thank you for any infos
73, David IK5XMK



Re: Current status DMRlink, HBlink DVSwitch

Steve N4IRS
 

David,
I do not know of a way to connect DMR+, IPSC2 or DMRMaster to XLX. If, and it's a BIG if, IPSC2 can connect to IPSC_Bridge (DMRlink) it might go something like this:
IPSC2 <---> IPSC_Bridge <---> HB_Bridge <---> DMRGateway <---> XLX. I think I remember someone posting that he needed DMRGateway from G4KLX to connect HB_Bridge to XLX.
Sorry I could not be of more help.

73, Steve N4IRS

On 9/28/2017 2:50 PM, david bencini ik5xmk wrote:
Hi Steve, great work !! Thank you.

Please, where can i find informations/which software/configuration about linking my dmr server (dmrmaster.webandcloud.net or ipsc2.webandcloud.net) 
to my xlx dstar server (http://vpngrf.webandcloud.net/db/dashboard/index.php) that it has an hardware transcoder server (2 USB ThumbDV)  into? I need a dmr flow to put into my
dstar system so i can join my dstar/dmr repeaters in my region. Now i can link my mmdvm repeater directly to xlx via dmrmmdvm protocol, and it works
very well with good audio, but a lot of friends are on dmr servers and i need a "connector" from dmr world to dstar one :)

Thank you for any infos
73, David IK5XMK
_._,_._,_


Re: Current status DMRlink, HBlink DVSwitch

david bencini ik5xmk
 

Hi Steve, great work !! Thank you.

Please, where can i find informations/which software/configuration about linking my dmr server (dmrmaster.webandcloud.net or ipsc2.webandcloud.net) 
to my xlx dstar server (http://vpngrf.webandcloud.net/db/dashboard/index.php) that it has an hardware transcoder server (2 USB ThumbDV)  into? I need a dmr flow to put into my
dstar system so i can join my dstar/dmr repeaters in my region. Now i can link my mmdvm repeater directly to xlx via dmrmmdvm protocol, and it works
very well with good audio, but a lot of friends are on dmr servers and i need a "connector" from dmr world to dstar one :)

Thank you for any infos
73, David IK5XMK


Re: Current status DMRlink, HBlink DVSwitch

David KE6UPI
 

Thanks for the update and great work you all have done.


--
Thanks, David
KE6UPI

"Laws that forbid the carrying of arms...disarm only those who are neither inclined nor determined to commit crimes. Such laws make things worse for the assaulted and better for the assailants; they serve rather to encourage than prevent homicides, for an unarmed man may be attacked with greater confidence than an armed one."
Thomas Jefferson

10301 - 10320 of 10738