[arm-allstar] Echolink
Doug Crompton
wa3dsp at gmail.com
Thu May 23 10:35:35 EDT 2019
We talk or should I say worry way to much about Echolink! Like I said there
is no worry that all servers work nor is it a problem if one does not work.
You need three entries in the config file. One could be xxx.com, it doesn't
care. Many of the servers are redundant pointing to the same Ip address.
The bottom line is that you are getting the data and you can check that as
I pointed out before. Below is the list of known servers and their IP
addresses. They all resolve and as you can see many have the same IP
addresses. They do not ping so there is really no easy way to tell if they
are alive. If you look in your client you will get the following about
every five minutes when things are working. The server is one of the three
you selected. Little is known or published about the servers.
-- Received OK from Echolink server server3.echolink.org
-- Directory pgm done downloading(partial,compressed), 269 records
another example -
-- Received OK from Echolink server server1.echolink.org
-- Received OK from Echolink server server3.echolink.org
-- Directory pgm done downloading(partial,compressed), 150 records
Servers -
server1.echolink.org (174.129.36.165) Network AMAZON-AES - Amazon.com, Inc.
(US) Routing 174.129.0.0/16 via AS11164 , AS16509 , AS14618
server2.echolink.org (174.129.209.125) Network AMAZON-AES - Amazon.com,
Inc. (US) Routing 174.129.0.0/16 via AS11164 , AS16509 , AS14618
server3.echolink.org (174.129.209.125) Same as server2
server4.echolink.org (50.18.55.39) Network AMAZON-02 — Amazon.com, Inc., US
(US) Routing 50.18.0.0/18 via AS16509
server5.echolink.org (68.178.144.151) Network AS-26496-GO-DADDY-COM-LLC —
GoDaddy.com, LLC, US (US) Routing 68.178.144.0/22 via AS26496
server6.echolink.org (54.161.182.37) OS Fedora Network AMAZON-AES -
Amazon.com, Inc. (US) Routing 54.160.0.0/14 via AS16509 , AS14618
server7.echolink.org (54.93.96.123) Network AMAZON-02 - Amazon.com, Inc.
(US) Routing 54.93.64.0/18 via AS7018 , AS1299 , AS16509
servers.echolink.org (174.129.36.165) Same as server1
naeast.echolink.org (174.129.209.125) Same as server2
nasouth.echolink.org (174.129.209.125) Same as server2
backup.echolink.org (54.161.182.37) Same as server6
*73 Doug*
*WA3DSP*
*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
On Thu, May 23, 2019 at 9:31 AM "Paul Kindell via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:
> Doug,
> The file echolink.xxx has as the following
>
> server1=server1.echolink.org
> server5=server2.echolink.org
> server3=server3.echolink.org
> ;naeast.echolink.org
> ;nasouth.echolink.org
> ;servers.echolink.org
> ;backup.scholink.org
>
> What worked for me is
>
> ;server1=server1.echolink.org
> ;server5=server2.echolink.org
> ;server3=server3.echolink.org
> server1=naeast.echolink.org
> server2=nasouth.echolink.org
> server3=servers.echolink.org
> server4=backup.scholink.org
>
>
> If you could push that update to the echolink.xxx file, that would save
> the next guy a bunch of grief.
> What made it difficult for me is I could get the node to dump the node
> list using echolink dbdump. It just would not register enough to be listed
> as an active node to connect to it.
>
> The help sheet on Ham Voip was very good and is what I used as a guide but
> with the settings old in the template file and no where could I find that
> it needed to be changed slowed me down.
>
> Thanks for all you do!
>
> 73, Paul
>
>
> > Sent: Wednesday, May 22, 2019 at 11:49 PM
> > From: "Doug Crompton via ARM-allstar" <arm-allstar at hamvoip.org>
> > To: "ARM Allstar" <arm-allstar at hamvoip.org>
> > Cc: "Doug Crompton" <wa3dsp at gmail.com>
> > Subject: Re: [arm-allstar] Echolink
> >
> > The various Echolink servers have been up and down for awhile. At the
> > moment I can't seem to ping any of them but since I have not tried that
> in
> > awhile it is possible they do not allow pings any more. The
> echolink.conf
> > file requires that three servers are defined. The way the servers seem to
> > change availability precludes any fixed values although I have had no
> > trouble here with the image suggestions. This is also a geographical
> > problem as not all servers may be available at a particular location.
> >
> > Unfortunately Echolink is like Allstar was before hamvoip introduced the
> > DNS lookup method. Echolink nodes are download periodically, the initial
> > list at start and then changes following. There was a change awhile back
> to
> > force a download if another Echolink node was trying to connect and they
> > were not in the list.
> >
> > You can pretty much troubleshoot Echolink in the client with the dbdump
> > and dbget commands.
> >
> > Example -
> >
> > 27225-HUB*CLI> echolink dbget c WA3DSP-L
> > 147090|WA3DSP-L|67.165.29.63
> >
> > 27225-HUB*CLI> echolink dbget n 147090
> > 147090|WA3DSP-L|67.165.29.63
> >
> > dbdump gives the entire downloaded list and can be saved to a file in
> this
> > way for review. This is done at the Linux prompt.
> >
> > asterisk -rx "echolink dbdump" > /tmp/echolink.txt
> >
> > Then review the downloaded file - less /tmp/echolink.txt
> >
> > If you are getting a list then your password registration with Echolink
> and
> > at least one server is working. If you are getting the list error
> messages
> > about not being able to reach a server can be ignored. They will happen
> > periodically or even perhaps regularly.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> > On Wed, May 22, 2019 at 10:42 PM "Paul Kindell via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > Charles,
> > > Thank you so much for the help! Following your file was the key. I
> didn't
> > > know the servers had to be changed. The example file needs to be
> updated
> > > in the image!
> > >
> > > I can see it now on the status page, now to try and connect!
> > >
> > > Again, Thank You!
> > > 73, Paul
> > >
> > > > Sent: Wednesday, May 22, 2019 at 5:35 PM
> > > > From: "Charles Powell via ARM-allstar" <arm-allstar at hamvoip.org>
> > > > To: "ARM Allstar" <arm-allstar at hamvoip.org>
> > > > Cc: "Charles Powell" <5h3dx.zinga at gmail.com>
> > > > Subject: Re: [arm-allstar] Echolink
> > > >
> > > > Here is my echolink.conf file. The How-To on hamvoip.org <
> > > http://hamvoip.org/> is quite comprehensive.
> > > >
> > > > 73,
> > > >
> > > > Charles - NK8O
> > > >
> > > > [el0]
> > > > confmode=no
> > > > call=NK8O-L ; Change this! You must be
> registered
> > > as XXXXXX-L or XXXXXX-R and this is different from your individual
> login
> > > > pwd=XXXXXXXX ; Change this!
> > > > name=Charles ; Change this to your real name!
> > > > qth=Louisburg KS ; Change this to your actual QTH!
> > > > email=XXXX at XXXX.net ; Change this!
> > > > maxstns=10 ; set the maximum number of users
> here
> > > > rtcptimeout=10
> > > > node=963349 ; Echolink node number - Change this
> > > and use your own!
> > > > recfile=/tmp/recorded.gsm
> > > > astnode=47337 ; Change this to your active Allstar
> > > node number!
> > > > context=radio-secure
> > > > ;server1=server1.echolink.org
> > > > ;server2=server3.echolink.org
> > > > ;server3=server5.echolink.org
> > > > server1=naeast.echolink.org <http://naeast.echolink.org/> ;
> > > echolink servers have changed
> > > > server2=nasouth.echolink.org <http://nasouth.echolink.org/> ; note
> > > changes
> > > > server3=servers.echolink.org <http://servers.echolink.org/> ;
> > > > server4=backup.echolink.org <http://backup.echolink.org/> ;
> > > > ; Outgoing message
> > > > message=This node is an AllStar bridge.\rPlease be aware you could be
> > > connected to hundreds of nodes worldwide\r\rGive your station ID if you
> > > transmit.
> > > > ; Change following setting to your parameters
> > > > freq=
> > > > tone=
> > > > lat=38.631981
> > > > lon=-94.677393
> > > > power=
> > > > height=
> > > > gain=
> > > > dir=0
> > > > ;deny=
> > > > ;permit=
> > > >
> > > >
> > > > > On May 22, 2019, at 3:40 PM, Boban Jovanovic YT1JB via ARM-allstar
> <
> > > arm-allstar at hamvoip.org> wrote:
> > > > >
> > > > > On 22.05.2019. 22:29, "Charles Powell via ARM-allstar" wrote:
> > > > >> Echolink works extremely well on the HamVOIP distribution
> > > > >
> > > > > It's nice news! Thank you!
> > > > >
> > > > >> Remember the the port forwarding is UDP for 5198 and 5199, plus
> 5200
> > > which is TCP.
> > > > >
> > > > > 5200/TCP is outgoing but 5198/UDP and 5199/UDP is incoming. For
> > > registering EchoLink node does not need incoming ports. It must be
> seen in
> > > list of active EchoLink nodes, but I could not achive that.
> > > > >
> > > > > Some config file would be nice to see here, please...
> > > > >
> > > > > 73, Boban YT1JB
> > > > > _______________________________________________
> > > > >
> > > > > 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
> > > >
> > > _______________________________________________
> > >
> > > 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
> >
> _______________________________________________
>
> 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
>
More information about the ARM-allstar
mailing list