[arm-allstar] Echolink Won't Stay Linked

[Dan Ozment]

Thanks, Doug.   

I added backup.echolink.org when I took server5 out.  I can put server5 back
in if that makes sense.  We haven't done long term Echolink connections
before now. Normally, our Echolink node connects to the repeate via RF.  So,
I cannot say when this began.  

I am currently getting the info for our Echolink node.

allstar43287*CLI> echolink dbget nodename 3026
3026|WB4QOJ-R|174.49.65.11

I'm trying to catch it when it drops the connection to see if it is there
then.   I'm forwarding inbound UDP/5198 and UDP/5199 to the Pi.  TCP/5200
outbound isn't blocked.

Internet doesn't seem to be a problem.  I've been logged into the Pi
remotely all day today.  However, it is a dynamic IP address at the site.

The WB4QOJ-R echolink node is running on a remote PC.  It has been running
there for years, and is very stable.   We simply turned the radio on it off
and connected it to the Allstar node.  

I can probably link it to another Echolink node for a day or so to see if it
is more stable there.

Thanks for the tips.  Any other ideas are welcome.

Dan




-----Original Message-----
From: arm-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
"Doug Crompton via arm-allstar"
Sent: Monday, June 5, 2017 10:29 PM
To: ARM Allstar <arm-allstar at hamvoip.org>
Cc: Doug Crompton <wa3dsp at gmail.com>
Subject: Re: [arm-allstar] Echolink Won't Stay Linked

Dan,

 Echolink has gone through several bug fixes in the hamvoip code over the
last 5 months to make it more stable. As far as we know at this point it is
tremendously more stable then it had been before these changes. I run it
here on a busy hub with daily connections for months and others do also
without problems. Exactly why you would be having the problem you are is
hard to diagnose because it could be so many things.

The server5 error is because there is no active server5 BUT the code
requires at least 3 servers be defined or echolink will not load so if you
take server5 out you would need to put another in. server5 being in there
and logging those errors would have nothing to do with your apparent
problems though. I am assuming you are getting node downloads correctly -
echolink dbdump  - in the client and you have the proper port forwarding
setup for echolink to your server.

Unless you can be more specific it would be hard to diagnose. Has this just
started happening? Does it only happen with certain connections? Echolink is
not as forgiving as a permanent Allstar connection would be. Is your
Internet OK? Are you running Echolink on a separate node connected to a main
node?


*73 Doug*

*WA3DSP*

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