[arm-allstar] Echolink Time Out ?

Doug Crompton doug at crompton.com
Tue Jun 28 00:45:21 EST 2016


Echolink has no permanent connect method like Allstar does so you would expect any downstream interruption to drop the link. It also has no timeouts at our end. I have no idea about the other end. 

The echolink/Allstar bridge was never intended to be a permanent connection but rather a method for echolink users to casually connect and converse within the Allstar network.

For Allstar connects I always stress permanent Allstar links (*73) for connections you don't want to fail.  
I occasionally get complaints "my link is dropping" and when I ask they used (*3) to connect. There are always dropouts on the Internet especially overnight when providers often service networks.

73 Doug
WA3DSP
http://www.crompton.com/hamradio


> Date: Tue, 28 Jun 2016 00:19:36 -0400
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Echolink Time Out ?
> From: arm-allstar at hamvoip.org
> CC: w2ymm1 at gmail.com
> 
> It is through a Netgear router. Pi has a static local IP address. It doesn't always happen but has happened on the past two nets we were connected to. 
> Not sure what conference software they use. Conference is *AB2M*. 
> 
> It seems like a glitch in our network that doesn't recover. 
> 
> After reconnecting tonight,it was fine for the rest of the net, about 1 1/2 hours. 
> 
> Weird. Just curious if there might be a workaround. 
> I'll keep monitoring. 
> 
> I did notice a lot of errors in the log for being unable to connect to Echolink server 5.  Not sure if that could be part of the problem. 
> 
> Thanks 
> 
> Bob W2YMM
> 
> 
> 
> Sent from my iPhone
> Bob Prybyzerski
> 631-960-1051
> W2YMM
> 
> > On Jun 27, 2016, at 11:50 PM, David McGough via arm-allstar <arm-allstar at hamvoip.org> wrote:
> > 
> > 
> > Hi Bob,
> > 
> > Are you running your RPi2 through a NAT router, or does it have a "live" 
> > IP address??
> > 
> > I've not personally seen the behavior you're describing, but, If you're
> > behind a "stateful" NAT firewall, that might be the problem.
> > 
> > Do you know what conference software is being used?
> > 
> > 73, David KB4FXC
> > 
> > 
> >> On Mon, 27 Jun 2016, W2YMM via arm-allstar wrote:
> >> 
> >> I was curious if anyone else who uses Echolink on their Allstar node ever
> >> experienced a problem like this...
> >> The Echolink node is connected to a Conference server then about 30-40
> >> minutes into a net Audio Stops being passed to the repeater from the
> >> Echolink stations, but the Allstar node still shows that it is connected.
> >> Issuing a disconnect then reconnecting brings the audio back.
> >> 
> >> I am using a Raspberry Pi2 with V1.01 code.
> >> Is there any kind of timer settings ?
> >> 
> >> The Allstar node is at a remote location with a link radio, So I can't see
> >> it physically when the problem occurs.
> >> We leave pauses and wait for the link radio to reset quite often.
> >> 
> >> Thanks
> >> Bob W2YMM
> > 
> > _______________________________________________
> > 
> > arm-allstar mailing list
> > arm-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > 
> > Visit the BBB and RPi2 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 web page - http://hamvoip.org
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.hamvoip.org/pipermail/arm-allstar/attachments/20160628/bdbab711/attachment-0001.html>


More information about the arm-allstar mailing list