[arm-allstar] Tracking Echolink connects

[Doug Crompton]

Tom,

  One thing I was thinking if these checkins are using echolink in Windows
then they could just as easily use iaxrpt. I was thinking how to do that
and keep it secure. You would have to setup another server just for that,
use a different IAX port, limit the functions or turn them off. A user
would log in (automatic with account setup) and be connected to whatever
that node was connected to. Again if there was a problem you could
disconnect that node. Everyone with a need would be given the login
credentials. You would obviously need to be running a dynDNS or have a
static public IP to do this. Just a thought.

You still would have the problem of one person hanging up the whole works.
Probably the best way would be to use the permit/deny in Echolink. Either
have people register with you for access and add them to the permit list or
build a deny based on abusers.



*73 Doug*

*WA3DSP*

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

On Tue, Nov 22, 2016 at 3:47 PM, Tom Whiteside via arm-allstar <
arm-allstar at hamvoip.org> wrote:

> Thanks Doug.   We do have it on a separate node so can disconnect it if
> need
> be.   Our biggest use is on ARES nets where some members from neighboring
> counties with marginal RF connections are encouraged to check in with
> Echolink so it is inconvenient to disconnect the lot of them but we
> certainly will if need be.   I've put a few of them on Zoiper experimenting
> with that as an alternative - it certainly has better audio and less delay
> but with an interface that is a bit more challenging for them and volume
> issues with iphones.
>
>
>
> 73 Tom N5TW
>
>
>
> Message: 2
>
> Date: Mon, 21 Nov 2016 14:17:04 -0500
>
> From: Doug Crompton <wa3dsp at gmail.com <mailto:wa3dsp at gmail.com> >
>
> To: ARM Allstar <arm-allstar at hamvoip.org <mailto:arm-allstar at hamvoip.org>
> >
>
> Subject: Re: [arm-allstar] Tracking Echolink connects
>
> Message-ID:
>
>
> <CAMp6vsuoKfz9BEwcM9j2c0wyZf9h+jOKjs5Ttp11_d26s_xgzw at mail.gmail.com
> <mailto:CAMp6vsuoKfz9BEwcM9j2c0wyZf9h+jOKjs5Ttp11_d26s_xgzw at mail.gmail.com
> >
> >
>
> Content-Type: text/plain; charset=UTF-8
>
>
>
> 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*
>
>
>
>
>
> _______________________________________________
>
> 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
>
>