Le 06/04/2016 23:45, mike@midnighteng.com a écrit :
When you hear some other callsign, it will announce the proxy station and not the proxy user for non direct connects. Some proxy's don't have proper handling and that can screw things up.
I'm quite disappointed with the Echolink module. Despite my tries, I didn't manage to have it work as expected. I'm using the Android Echolink client. I do not have any control about what proxy is used. Sometimes, I hear an unknown callsign. But most of the time, I hear no callsign at all. I never heard *my* callsign ! Am I the only one having this behaviour ? Moreover, my radio node is connected to a hub. When my Echolink node is also connected to the hub, on the radio, I can hear four quick acute bips before the "normal" bip (remotetx or linkunkeyct). I tried all the CTs, but I didn't find where those are located, and I didn't manage to remove them. When the Echolink node is disconnected from the hub, I do not hear those 4 bips. From where are they coming ? And how to remove / change them ? Thank you in advance...