[arm-allstar] Echolink troubles

[David McGough]

Most likely you've got 2 identical echolink instances setup, each on a 
different nodes.  KC0FTV-R  is showing registered on on-line right now, 
based on info from the echolink servers. If you entirely shut down 
asterisk on the node in question, my guess is KC0FTV-R will still show up 
as on-line, positively demonstrating this is the problem.


73, David KB4FXC


On Mon, 22 Feb 2021, "John Simmons via ARM-allstar" wrote:

> My node isn't connecting to the Echolink servers but it used to. I THINK 
> everything is configured correctly.
> 
> I verified the router forwarding by loading Echolink on a Windoz box and 
> setting the IP address on the router... all was good, so I reset the IP 
> address back to my node.
> 
> Monitoring Asterisk on my node I see:
> "Received OK from Echolink server server1.echolink.org"
> "Received OK from Echolink server server3.echolink.org"
> then
> "Error in parsing header on server server1.echolink.org"
> "Error in parsing header on server server3.echolink.org"
> 
> In the Asterisk CLI entering
> 'module load chan_echolink.so'results in:
> "Module 'chan_echolink.so' already exists"
> 
> 'echolink dbdump' does not give any result
> 'echolink dbget callsign KC0FTV-R' reports
> "Entry for KC0FTV-R not found" yet with my cell app that callsign is online.
> 
> So obviously there is a connectivity problem. Any suggestions on how to 
> proceed?
> 
> 
> 
>