RF repeater users PTT so quick, echolink users hear nothing

Hello,

I am using ASL 2.0 and a private node for echolink. And using DRA-50 connecting FTM-100 for RF side.

This is the RF bridged to a local repeater.

Everything seem to be working fine except 1 minor issue.

That is, when the echolink user unkeyed. Folks on the RF repeater, normally there will be a repeater courtesy tone and a about a sec later, the repeater will drop the carrier.

The issue is if the RF repeater user key up so soon, the echolink side users will not hear what was said (unless they have their radio listening on the repeater frequency).

My node radio would hear the repeater fine but perhaps it was not enough time to passing the audio to DRA-50 and on to echolink server.

However, if the RF repeater waited for courtesy tone then carrier dropped and wait for about 1-2 sec then key up, the echolink user will hear everything just fine.

Is there any setting in the rpt.conf or echolink.conf that can minimize the issue?

Kind of hard to explain to the analog users about leaving the pause between key up.

73, Kit

Unfortunately, you’re describing latency issues with Echolink and not ASL/app_rpt. You may want to try ASL3 as the Echolink stuff has been greatly improved by Danny. It may help.

Komkit,
Unfortunately, echolink wanted all telemetry removed and got just what the wanted.
So , users on the echolink side do not hear CT’s or other telemetry… They have to watch whatever display they are using to indicate active/non-active channel.
Bridging between the two is more complex than you might think, but admit-ably, should be a simple thing.

The asl system can set the delay between the loss of carrier to CT time to help limit the issue.
I ‘think’ this is the correct timer…?
hangtime = 0
Not sure if it is in seconds or milliseconds. Not in my notes. I assume milliseconds.
Perhaps try this in testing with increasing values etc

You can’t force folks to not quick key, it happens.
I am ‘not certain’ asl3 would relieve the issue for you, but there are suppose to be other elink fixes. But nobody has stated them for the record that I have seen.
Outside of talking over has been eliminated. User gets text message, but that does not help in the revere direction on a asl node unless it is ready to rx said text and act on it in some way. Perhaps it does, but no data on it.

Please come back and state the fix if you find one.
It’s all the guidance I can give on the matter.