[arm-allstar] Echolink Timeout

[Doug Crompton]

Adam,

 There are no timeouts in Echolink. Like you said in your last paragraph
the best way to handle this is through Supermon and Echolink restrictions
(deny or allow in echolink.conf) to stations that continually abuse. Have
net controls use Supermon to disconnect nodes causing problems.


*73 Doug*

*WA3DSP*

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


On Wed, Feb 5, 2020 at 4:00 PM "Pawlowski, Adam via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Good afternoon all,
>
> Is there a way I can configure a timeout specifically for Echolink TX ?
>
> I know we'd established there's not really any logging of these events,
> but, more than once now we've had someone connect via Echolink, then
> somehow the app crashes, they leave coverage, etc, and leave it in
> transmit. As this happens during a net, people panic and restart Asterisk
> or the whole Pi. Half the time restarting Asterisk results in it failing to
> be able to open the USB devices, so they will then restart the Pi, and I
> lose logging.
>
> Since the net should be able to continue duplexed until the transmitter
> itself times out or some other tx timeout is hit, I'm not too concerned
> about it, but, without logging I can't see who's doing what. If they time
> out and get kicked off of keying then I'd be happy with that.
>
> Going to get supermon access setup for a group of people to hopefully see
> better what is happening to quell the panic.
>
> Any tips appreciated.
>
> Adam
> KC2YQF
> _______________________________________________
>
> 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/4 web page - http://hamvoip.org
>