[arm-allstar] Tracking Echolink connects

[Tom Whiteside]

We had a problem recently with computer sounds be broadcast over several
nets that we believe was coming from an Echolink connected user - this
assertion is based on the sounds being quite clear and on top of other users
and not sounding like an FM double.   Turns out this was the case and the
user contacted us and "confessed" after discovering his inadvertent error.
In the process of trying to track this down, I have tried to generally
instrument connects so we can be better prepared if this happens again.

Our first attempt was using the Echolink node number shown on the Allstar
connect bubble chart to look up the user (after discarding the leading "3")
on the Echolink current login page here:

http://echolink.org/logins.jsp

This works fine if someone is connecting from the Echolink software on a
Windows computer but not for most phone users going through a proxy server.
For these cases, you get the callsign of the proxy server...

Watching connects with Asterisk -rvvv shows connect happening but not who is
connecting.   Found nothing useful grubbing around in the logs but perhaps
was not looking in the right place.   My next attempt was to setup the
Echolink node to announce connects figuring the real callsign would be
passed through.   Our Echolink setup is on its own node but I figured I
could listen on Zoiper or Echolink to hear these connects.  I added the
following line to the RPT.conf file based on an example I found online:

Eannmode=2 

This is supposed to announce the call only on a connect.   Nothing gets
announced however - not even sure this even works on this implementation.

I've run out of ideas!   Is there some log of Echolink connects and perhaps
key ups?   Is this announce command supported or is there another
encantation?

Tom N5TW