[arm-allstar] Echolink

[David McGough]

Forwarded message, below...Original was filtered due to html only content.

-----------------------------------------------------------------------------
Date: Wed, 22 May 2019 17:58:14 +0200
From: Paul Kindell <pkindell at mail.com>
To: ARM-allstar at hamvoip.org
Subject: Echolink

Our club is interested in linking on Echolink from our Allstar Node to 
reconnect with a member that moved away. I started the process a couple of 
days ago and need a push to get it working. Here is what I have done so 
far.

I validated a -R callsign for the repeater.

I renamed and updated the file /ect/asterisk/echolink.xxx to echolink.conf.

Port forwarded 5198 and 5199 to the pi in the router.

I rebooted the pi.

There are no other Echolink devices out at this tower site.

When I log back on and go to the asterisk cli, I keep seeing Recieved OK 
from Echolink server server1.echolink.org
Then error parsing header on server1.echolink.org. I see this for server 
1, 2, and 3.

I have actually done this now on 2 nodes trying to get it to work. The 
first one on its own, started downloading the data base after a day of 
parsing errors. I
can now do a "echolink dbdump" and see the list. I still don't see the 
Echolink node on the Echolink status page and can't connect to it on the 
android app as it
does not appear in the repeater list.

The second node, now only a few minites old is just giving the error 
message on parsing like the first one did.

The first node seems very close as I can dump the data base but not 
showing up in the repeater lists makes me think I have something else 
missing.

I have not tried any outbound connections because, I just haven't read up 
on how to connect on the air to echolink yet!

Any ideas on what to try next?

Thanks a bunch!

Paul WB8ZVL