[arm-allstar] Tracking Echolink connects

[Doug Crompton]

Tom,

  Echolink on Allstar is a minimalist implementation. It works but could
stand some improvements. There are some updates to Echolink in our next
release but mostly only to correct bugs. Echolink is not top priority as
most would rather see it go away. But it is there and I guess we need to
put up with it unless we can convert some of these guys to Allstar. Overall
it tends to drag down the good quality of Allstar.

Isolating Echolink on an Allstar node by itself allows for a quick
disconnect from mainstream Allstar and is a recommend way to go. A quick
disconnect of that node and Echolink is gone.


You can also permit or deny Echolink users in the config file. If you don't
want drive bys build the permit list. If you want to just limit certain
people then use deny.

Often the problem you run into in a widely connected hub is more than one
user has Echolink activated. You either need to coordinate that or block
the offending Allstar node if they don't cooperate.






*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Mon, Nov 21, 2016 at 1:16 PM, Tom Whiteside via arm-allstar <
arm-allstar at hamvoip.org> wrote:

> 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
>
> _______________________________________________
>
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>
>