[arm-allstar] Link Activity Timer Not Always Working

[Larry Aycock]

Hi David,

Just a quick follow up.  I looked up what dual registration is, and the answer is no, I am not dual registered with the HamVOIP servers.  Perhaps that is something I should do, but I'm not sure how to go about getting a registration string for HamVoip.  If you could send me instructions, I would appreciate it.  I'm still researching this in the meantime.  Does the node have to be running on HamVOIP to use dual registration, or can a node running on ASL also use it? E.g., my hub node now in the cloud, which is running on ASL.

BTW, if there is a way to install and run HamVOIP on a virtual server (I'm using Vultr.com), I would love to know how to do that.  I am more comfortable with HamVoip and would prefer to use it instead of ASL, but it is my understanding that HamVoip won't run on a VPS.


73,
Larry Aycock
N6LKA

-----Original Message-----
From: David McGough <kb4fxc at inttek.net> 
Sent: Thursday, October 22, 2020 3:44 PM
To: Larry Aycock via ARM-allstar <arm-allstar at hamvoip.org>
Cc: Larry Aycock <N6LKA at outlook.com>
Subject: Re: [arm-allstar] Link Activity Timer Not Always Working


Larry,

Did this problem start after changing to using a VPS-based hub node?

Are you using HamVoIP dual-registration?


73, David KB4FXC



On Thu, 22 Oct 2020, "Larry Aycock via ARM-allstar" wrote:

> Hello,
> 
> For a while now, I have been using the link activity timers on a few
nodes/repeaters, and they have been working for the most part.  I have a hub node, which I just moved to a cloud server.  I have my repeater node, a friend's repeater node, and my dad's simplex node connecting to my hub node.  On my repeater, my friend's repeater, and my dad's node, we use the link activity timer to disconnect all nodes and reconnect back to my hub node.  As I mentioned, this has been working for the most part.  
However, on my friend's repeater and my dad's node, it will occasionally disconnect from the hub, and won't reconnect.  Hours will pass and it will not reconnect back to the hub.  Eventually, one of us will notice the link is down, and send the command to run the script, and it reconnects back to the hub.  Nothing has changed on either of the nodes, and it seems like this problem is occurring much more frequently within the past week.
> 
> Note that my repeater has not had this problem with disconnecting and
remaining disconnected.  However, the hub node was, prior to this morning, hosted on the same RPi as my repeater node.  I moved the hub node to a cloud server for several reasons, but was also trying to troubleshoot this problem.  Unfortunately, even once I moved the hub to the cloud, I found the problem with the two nodes remaining disconnected is still happening.  I am baffled by this problem because it doesn't always happen.  I have not been able to consistently recreate the problem, so I have not been able to identify the cause.
> 
> Below is a copy of the part from my rpt.conf file used on my repeater.  
Remember that I am not having this problem with my repeater, but the same lines are used in my dad's and my friend's rpt.conf files.
> 

<snip>

> 
> 
> 73, Larry, N6LKA
> 
>