Run asterisk in the foreground with some verbosity ( asterisk -r -vvv) from putty or console and watch the screen for live events to see what is being called. ...mike/kb8jnm On 11/9/2018 2:22 PM, Steve Thompson wrote:
I’ve recently created a new Allstar node, and I’m working my way through some issues. One issue is that every hour, on the hour, the node transmits a dead carrier for 3 minutes, then there’s a CW message telling me it’s a timeout. Then the node unkeys.
Very early on in the process of bringing my new node alive, the node was transmitting the time (in voice) at the top of the hour. So I have to believe this was the same process which is now working incorrectly. And perhaps I did something at some point to cause it to error out.
I’ve searched through all the conf files in /etc/asterisk and the only reference to any sort of schedule is in rpt.conf. In the [schedule...] section, the only two lines (which reference a macro to be run on the hour) are both commented out with semi-colons. I did not comment them out. I would think since they are commented out, they’d not be running .. unless there’s something somewhere else triggering this behavior.
Where else can I see what is going on with a schedule? Any thoughts on how to (1) in the short term, disable this scheduled event, and (2) in the long term, fix it so that it works properly?
I have an extensive IT background but not much familiarity with Linux OS, so go easy on me.
Steve N7TX _______________________________________________ App_rpt-users mailing list App_rpt-users@lists.allstarlink.org http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
To unsubscribe from this list please visit http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button" You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.