[App_rpt-users] Echolink Unauthorized
Eric Tichansky
no3m at no3m.net
Sun Sep 20 20:01:50 UTC 2009
The problem that keeps coming up is that while the updates are
attempted, it often fails throwing complaints about zlib, et.al.
Between what seems to be a long delay in acquiring the node list and
frequent failures, I've found there are times when it may be more than
30-45 minutes before the current IP becomes part of the locally cached
listing. This isn't so good when trying to connect to the system using
an echolink client on a laptop while mobile, where mobile broadband
connectivity may be in and out periodically.
Is anyone else seeing these same frequent echolink node list update
failures? We are running asterisk/app_rpt/chan_echolink/zaptel from the
1.4.23-pre svn trunk over Gentoo Linux vs. ACID or limey linux.
73 - eric no3m
>
> Bingo.
>
> When run the echolink app on your pc, chan_echolink will not accept
> connections until it downloads an update to the authorized nodes list
> with your PC's node number in the update.
>
> The thing to remember is that you must wait 5-10 minutes before trying
> to connect so that a node update includes your PC's node number.
>
> Steve
> WA6ZFT
>
More information about the App_rpt-users
mailing list