[arm-allstar] echolink causing the repeater to TX silence?

[Doug Crompton]

Richard,

   Unfortunately Echolink in Allstar lacks the timers that would disconnect
a errant Echolink node that someone left in TX or left in TX and then
disconnected. In your case it sounds like the user lost connection in the
keyed state. Echolink is not Allstar in that regard. Unfortunately we have
to live with some of these idiosyncrasies of Echolink if we choose to use
it. Looking at possible Echolink timers is on our list of things to look at
but not the highest priority right now.

If this is happening all the time when anyone connects to Echolink then
there might be some other issue but if it seldom happens or happens only
with a specific Echolink user then it is probably a fault on the other end.
Lets us know what you are experiencing over time. We have not seen this
issue in general being a problem.


*73 Doug*

*WA3DSP*

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



On Fri, Feb 16, 2018 at 9:40 PM, "Richard Bateman via arm-allstar" <
arm-allstar at hamvoip.org> wrote:

> Hi,
>
> I've been experiencing a weird issue where someone trying to use echolink
> on my repeater causes the repeater to stop responding properly; it leaves
> the PTT closed and stops retransmitting audio until I restart asterisk. The
> only thing I see in the logs is a bunch of "ERROR[519] chan_echolink.c:
> Cannot find DB entry for IP addr x.x.x.x. Trying to update database!"
> messages during the time period when the issue occurs.
>
> Anyone have any ideas? I might just have to disable echolink, but some club
> members like to use it to participate in nets and I'd prefer to allow them
> that option.
>
> Richard
> KD7BBC
> _______________________________________________
>
> 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
>