Thank you Randy, 73 from PU2XTL.

#parrot #closed #hblink #echo #dudestar

The latest from nostar (maintainer of DudeStar): So Heitor, I would suggest you take a look at the latest code drop for DudeStar and try your setup again. In the meantime, we will take up the task of

#parrot #closed #hblink #echo #dudestar

I don't think line 128 factors into this. The playback.py script is pretty stripped down, so it's easy to see what's going on. Sets up the Twisted reactor object based on configuration The only thing

#parrot #closed #hblink #echo #dudestar

Perhaps the addition of a timeout condition in line 128 could work? I'll play with this idea a little later.

#parrot #closed #hblink #echo #dudestar

I wish it were that simple. The problem stems from the following: the app, as written, only does processing when it receives network traffic. That's what the dmrd_received() function is all about. So

#parrot #closed #hblink #echo #dudestar

That is the ugly solution that i think for playback.py #line 112 def dmrd_received(self, _peer_id, _rf_src, _dst_id, _seq, _slot, _call_type, _frame_type, _dtype_vseq, _stream_id, _data): ... #line 14

#parrot #closed #hblink #echo #dudestar

Yes, i am using playback.py for PARROT. I read the source code of playback.py, but i am have not enough skills in Python for test any modifications. About my server configs i get instructions from htt

#parrot #closed #hblink #echo #dudestar

Yeah, it's like the lightbulb went on here. Playback.py is dead simple as far as a parrot application goes. It's also not particularly well-designed or executed (no slight on Cort or Steve for writing

#parrot #closed #hblink #echo #dudestar

Wait a second. The parrot you're using here, is it playback.py from this repository? I need to see your config file for HBLink. Please copy/paste it in a reply or attach it, redacted if necessary. --R

#parrot #closed #hblink #echo #dudestar

Clever acronyms aside, I get your meaning. I'll see if I can contact him and figure out what's going on between DroidStar/DudeStar and HBLink --R

#parrot #closed #hblink #echo #dudestar

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

#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

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

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 thought BM Parrot was 9990, not 9999 --R

#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

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

What do you logs show you?

#parrot #closed #hblink #echo #dudestar

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

That would do it! Glad to hear it's working. --R

#hblink #support #closed