[arm-allstar] Echolink

Wed May 22 16:45:03 EDT 2019

Perhaps he already has an established base of EL users.  Perhaps he's wanting to establish another means of access to his repeater.  Both of these things were true in my case and EL runs better on my HamVoIP node than it did standalone.

No need for you to be so judgemental - EL serves a useful purpose in some instances.  You don't have to like it, but don't attack others for making use of a feature of HamVoIP.

Mike.
WM4B
On May 22, 2019 4:13 PM, jay via ARM-allstar <arm-allstar at hamvoip.org> wrote:
>
> Why are you farting with echolink? Why doesnt this member just build a portable node and get a node number and just connect in at will?Sent from my droid phone. 
> -------- Original message --------From: David McGough via ARM-allstar <arm-allstar at hamvoip.org> Date: 5/22/19  13:59  (GMT-06:00) To: ARM-allstar at hamvoip.org Cc: David McGough <kb4fxc at inttek.net> Subject: [arm-allstar] Echolink Forwarded message, below...Original was filtered due to html only content.-----------------------------------------------------------------------------Date: Wed, 22 May 2019 17:58:14 +0200From: Paul Kindell <pkindell at mail.com>To: ARM-allstar at hamvoip.orgSubject: EcholinkOur 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 t 
> he asterisk cli, I keep seeing Recieved OK from Echolink server server1.echolink.orgThen 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. Ican 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 itdoes 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_______________________________________ 
> ________ARM-allstar mailing listARM-allstar at hamvoip.orghttp://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstarVisit the BBB and RPi2/3 web page - http://hamvoip.org 
> _______________________________________________ 
>
> 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 