[arm-allstar] Echolink dropping out
wa3dsp at gmail.com
Tue Mar 14 16:15:51 EST 2017
Echolink has a lot of timeouts that can be initiated at the Windows end
and possibly at other remote clients. It is possible a timeout was your
issue. I have not seen a problem with echolink and in fact the 1.5 version
has several improvements to the code that previously in certain situations
caused system crashes.
I assume you are aware of the ports that need to be forwarded for echolink
and that you cannot be running another instance of Echolink on the same
public IP unless through a proxy.
Also make sure you have the latest updates for that node from hamvoip.
If it persists it would be helpful to run the client and look for any error
messages that may have appeared when this was happening. You can also do a
dump of nodes or look for a specific node with the echolink commands in the
On Mon, Mar 13, 2017 at 8:42 PM, "Barry Buelow via arm-allstar" <
arm-allstar at hamvoip.org> wrote:
> I have a node running V1.5 which temporarily has Echolink enabled. There
> is a limited access list. Everything runs fine for days, then the Echolink
> function looses registration with the mother ship. Today I had an instance
> where the Echo node fell off the list while connected and we were still
> talking just fine. After many minutes, it dropped the connection. Likely
> the remote node rechecked and my node was not listed, hence a disconnect.
> While this loss of Echo is occurring, I can still SSH into the node just
> fine. I commanded astres.sh and believe it executed. I was on my phone
> doing SSH. It did not solve the problem. I suppose I should have done a
> Has anyone seen this before? Suggestions?
> Barry w0iy
> arm-allstar mailing list
> arm-allstar at hamvoip.org
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
More information about the arm-allstar