[arm-allstar] Echolink troubles

John Simmons jasimmons at pinewooddata.com
Mon Feb 22 09:18:19 EST 2021


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?



-- 
73,
-de John NI0K in rural Debs, MN USA



More information about the ARM-allstar mailing list