[arm-allstar] perm link on startup

[Greg Stahlman]

I have several nodes set up for auto perm connect on startup.  The problem I
have seen is sometimes after they have been off network for a while, they
are not registered and will not connect to anything on startup.  You have to
let them register, then they will connect.  Unfortunately, with the perm
connection, I have found that they will not try to reconnect if the node is
not registered.  Best to let it come up, stay on for a while to register,
then either do a restart or manually to a perm connect to get them back up.
I have TWO portable radioless nodes that act this way.

 

73  KJ6KO

 

From: arm-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
"LaRoy McCann via arm-allstar"
Sent: Thursday, February 23, 2017 2:58 PM
To: ARM Allstar
Cc: LaRoy McCann
Subject: [arm-allstar] perm link on startup

 

I have nodes configured to permanently link to a hub on startup.  These
nodes
all are on a wide area network that I control.  They will reconnect
automatically if there is a network outage.

I added two other nodes on two other outside networks.  They are setup to
use
a vpn router back to my network.  This all works fine.

The problem is if there is a network outage the new nodes will not
reconnect.
I have the same startup macro configured on all nodes.
startup_macro = *7341741
I can restart Asterisk and it reconnects.

One of the new nodes is V1.5 and the other is V1.02 Beta.

Any ideas on what to look for?

LaRoy McCann K5TW




_______________________________________________

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



__________ Information from ESET NOD32 Antivirus, version of virus signature
database 14991 (20170224) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com



__________ Information from ESET NOD32 Antivirus, version of virus signature
database 14991 (20170224) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com