Hello dear friends, I installed the latest HBLink3 everything is working, Private Calls, Open Bridge too but I'm receiving a kind of loop authentication, this is part of the log: INFO 2020-10-25 12:09

#support #closed

Hi Charly, I'm going to presume that, based on your subject line, you're trying to connect your HBLink instance to BrandMeister. Please check the following FAQ for information about that. In short: to

#support #closed

That is not an openbridge connection. Openbridge is a stateless connection and does not login like a peer. The connection has to be setup on each side and talkgroups must be sent to you, you do not re

#support #closed

Thanks, I´ll do it that way, thanks for the answer. Charly XE2SSN

#support #closed

Thanks for the answer dear Corey, I will open a ticket requesting the Openbridge connection data to BM, thanks. Charly XE2SSN

#support #closed

I can however, answer the original question. It appears deliberate. BM Masters don't appear to allow login from anything that identifies as HBLink. There are two solutions, only one of which is "corre

#support #closed

Well, it's not like BM hasn't been saying this for a long, long time. I think everyone is better off when you follow the prescribed solution rather than go rogue and connect any which way, just becaus

#support #closed

Thanks dear Randy, I´m asking because I want to make the things the right way, and of course still in a learning process and never my intentions are to use the great tool HBlink in the bad way and wan

#support #closed

No problem Charly, Thanks for checking on this and getting set up on OpenBridge. Let us know how it goes. --R

#support #closed

I can assure you we have NOTHING in the System that looks for “hblink” and denies the connection. This is totally false. Regardless, we have ask numerous times not to do it!!! Corey

#support #closed

Corey, Thanks for your feedback. I wouldn't fault the BM Admin team if they did, but I understand the whack-a-mole approach something like that represents. We're trying our best on this end to get peo

#support #closed

Hello, I have sucessfully configured a HBlink3 private server ( http://vps29637.publiccloud.com.br) with PARROT just for learning purposes. I use just 2 TGs: 13 for Local and 9999 for ECHO - parrot. T

#parrot #closed #hblink #echo #dudestar

What do you logs show you?

#parrot #closed #hblink #echo #dudestar

from parrot.log # TX (1) - from radio (ID:1000007) INFO 2021-03-17 13:02:43,529 (PARROT) *START RECORDING* STREAM ID: 2539034976 SUB: 1000007 (1000007) REPEATER: 9999 (9999) TGID 9999 (9999), TS 2 INF

#parrot #closed #hblink #echo #dudestar

At the " Call log window" ## TX (1) - from radio (ID:1000007) 13:02:43 VOICE START SYS: MASTER-1 SRC: 724216401; 724216401 TS: 2 TGID: 9999 Papagaio SUB: 1000007 ; Heitor, heitor h3 13:02:48 VOICE END

#parrot #closed #hblink #echo #dudestar

I thought BM Parrot was 9990, not 9999 --R

#parrot #closed #hblink #echo #dudestar

Yes it is, but its not the point. The point is that the DudeStar crashes the ECHO service in HBlink3.

#parrot #closed #hblink #echo #dudestar

I'm not entirely convinced it's HBLink that is at issue here, since BM eventually delivers the audio. It's not like HBLink is storing it somewhere until a DMR subscriber radio actually tries the talk

#parrot #closed #hblink #echo #dudestar

DudeStar and DroidStar like all currently released mobile / PC software use the MMDVM protocol to connect to a DMR Master. BM is requiring this type of software to use the Open DMR Terminal Protocol.

#parrot #closed #hblink #echo #dudestar

That's quite a mouthful there, isn't it. --R

#parrot #closed #hblink #echo #dudestar