[arm-allstar] Watchdog if asterisk crashes.
Doug Crompton
doug at crompton.com
Wed Jul 13 17:22:31 EST 2016
You can connect a node in two ways for transceive. Either use *73<node> in DTMF from your radio or on the command line in the client.
asterisk -rvvv
rpt fun <yournode> *73<node>
You can also use lsnodes, iaxrpt, or allmon to connect to a node permanently.
*71<node disconnects a permanent connection.
Permanent means that if node A connected to node B and node B went down (rebooted or restarted) and came back up the connection would re-establish. This includes a disruption anywhere along the Internet path.
If node A reboots or restarts the permanent connection will not restart unless node A has a startup macro to restart the connection.
A startup macro command is located in the node section of rpt.conf. It is on a per node basis. Here is an example of a starup macro -
In the node section -
startup_macro = *A900
Then in the function section -
A900=cmd,/etc/asterisk/local/startup_commands
The function definition (A900 here) can be whatever you want.
This then calls a script that has the commands you want to execute at startup like in this example -
#! /bin/bash
# Echolink
/usr/bin/asterisk -rx "rpt fun <yournode> *73<node>"
sleep 1
# 223.76 Repeater
/usr/bin/asterisk -rx "rpt fun <yournode> *73<node>"
sleep 1
etc.... any commands you want to execute at startup.
#End of script
I hope I did not confuse you and this was what you were asking!
73 Doug
WA3DSP
http://www.crompton.com/hamradio
Date: Wed, 13 Jul 2016 14:59:24 -0700
To: arm-allstar at hamvoip.org
Subject: Re: [arm-allstar] Watchdog if asterisk crashes.
From: arm-allstar at hamvoip.org
CC: k6ecm1 at gmail.com
Doug, could you say more about "started with a permanent connection - *73<node>," like, where is this command inserted (e.g. *.conf, stanza, etc)?
Thanks,k6ecm73Sent from my iPhone
On Jul 13, 2016, at 2:53 PM, Doug Crompton via arm-allstar <arm-allstar at hamvoip.org> wrote:
Roselito,
Not sure what you mean by "crash" ?? This is NOT a common occurrence so I am not sure why it would be happening to you. The hamvoip code has a watchdog that can be implemented in /usr/local/etc/allstar.env. This is for the system not Allstar. Allstar is started with safe_asterisk which will restart if Asterisk itself crashes.
If you always want Asterisk to start connected to a certain node or nodes you can use a startup macro. Nodes that you want to stay connected should always be strarted with a permanent connection - *73<node>
What image are you using? What conditions cause this? Having multiple nodes connected should NOT cause a crash. Some hub have 30 or more nodes connected without problems.
73 Doug
WA3DSP
http://www.crompton.com/hamradio
To: arm-allstar at hamvoip.org
Date: Wed, 13 Jul 2016 14:18:05 -0700
Subject: [arm-allstar] Watchdog if asterisk crashes.
From: arm-allstar at hamvoip.org
CC: tolitski at hotmail.com
I have a hub that crashes for some reason. I think it happens when a lot of nodes connect to it?? It usually happens at night.After looking at different watchdog implementations, this is something I came up with after reading Justin Campbells original code. I am submitting this just in case Hamvoip does not have one yet.
https://gist.github.com/tolitski/5e302d31f4f56b35bf68615a65366bf9
73,
Lito KK6OOS
_______________________________________________
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
_______________________________________________
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/20160713/82288cf5/attachment-0001.html>
More information about the arm-allstar
mailing list