I've tried both applying this globally and within my node configuration but all identification of echolink connections are long numeric IDs. I've tried from my phone and desktop (both through a relay and proxy) and no-good.
I'm not finding anything in any documentation that says relays (are... these different from proxies?) and proxies mask callsigns.
I've tried changing eannmode to zero, which gets me zero announcement, so that seems to be working. Is there a way to check if my node is having trouble decoding echolink node numbers? AllstarMon3 shows the description with the callsign in it.
Do you have this turned on as well? IF NO then remove the ; to use telemetry feedback on echolink connections
echolinkdefault = 2 ; 0 = Telemetry output off
; 1 = Telemetry output on
; 2 = Timed telemetry output on command execution and for a short time thereafter
; 3 = Follow local telemetry mode
William, be careful how you judge this.
There are many issues within EL that are on the EL or Relay agent side of this.
Test a bit more broadly.
With asl3, I think there were updates to EL as some of the issues were in format.
So, make sure you have the latest update before you chase your tail on it.
One of my asl 1.01 nodes that has not changed config in over 7 years rarely gets callsign from a relay agent, and many times other info and gets disconnected near immediately..
Tough to determine the cause, but I don't try. I just advise users not to use them.
I only have it there for convenience. Not convenient for me.
eannmode=2 ;0=no announcements, 1=node number(Allstar-xlated), 2=callsign, 3=both
echolinkdefault=1 ;0=off, 1=on, 2=on after command & shortly after, 3=follow local telemetry
echolinkdynamic=1 ;0=disallow user change setting via COP command, 1=Allow users to change