[arm-allstar] Echolink

[Doug Crompton]

Port 5200 TCP is an outbound port and since most routers allow all outbound
traffic it is generally not needed. I have never set it up here. Port range
fowarding has always worked for me but your milage may vary.


*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Wed, May 22, 2019 at 11:17 PM "Gervais Fillion via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Jay
>
> 5198 and 5199 should be open UDP in your router and individualy not like
> each must have his setup line
> 5198 to 5199 UDP,,some router wont work corectly and i experience that
> here.
> you also forgot 5200 TCP
>
> good luck
> gervais ve2ckn
>
>
> ________________________________
> De : ARM-allstar <arm-allstar-bounces at hamvoip.org> de la part de "jay via
> ARM-allstar" <arm-allstar at hamvoip.org>
> Envoyé : 22 mai 2019 16:13
> À : ARM Allstar
> Cc : jay
> Objet : Re: [arm-allstar] Echolink
>
> 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
> _______________________________________________
>
> 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
>