[arm-allstar] Persistent connection

[David McGough]

Hi Tom,

Do you have your destination node connection info in the 
/etc/asterisk/rpt.conf file, [nodes] stanza?  If not, that is probably the 
problem.

Note that for all connections operations, normal or permanent, to proceed,
there must be directory entry for the destination node at initial
connection time...And, in the case of a freshly booted system, the macros
including the permanent connection command will run before rpt_extnodes
file is downloaded, causing the command to fail.

If you don't know what the destination node IP address or port info is at
boot time, meaning that adding an entry in the rpt.conf [nodes] stanza is
impractical, you can also drop a temporary file in /tmp/rpt_extnodes, 
which contains "spoofed" entries as place-holders. This will allow the 
connection command to correctly execute and then the connection would 
proceed once a real rpt_extnodes file is downloaded.

73, David KB4FXC






On Mon, 31 Jul 2017, "Tom Hayward via arm-allstar" wrote:

> I have a node that is configured to create a persistent connection to a hub
> on startup. However, when it boots it doesn't connect. If I log into ssh
> and restart asterisk, the startup macro works fine and it connects to the
> hub. Something is different at boot time. This is a problem because the
> link does not automatically reestablish after a power loss. How can I
> correct this?
> 
> Tom KD7LXL
> _______________________________________________
> 
> 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
>