VoIP Mailing List Archives

[jesset at gmail.com]

We've built an alert system at our company so that if our monitoring software notices anything very bad happening, and we don't react to a text message after a few minutes, then it will begin to call our telephones directly. This seems to help a lot with staff who are asleep, or who might not be near enough to the phone to hear text message notifications.

We do this by having a folder full of .call files, and programatically moving a copy of the appropriate call file into /var/spool/asterisk/outgoing/ when an outbound shout is required.


This has worked well for a couple of years, but recently we are experiencing a problem where sometimes Asterisk will simply ignore this folder. When we notice the logjam of ignored call files in /var/spool/asterisk/outgoing/, then we restart the asterisk daemon and things run smoothly again. 


When "wedged", the Asterisk daemon will function normally in every other way that we use it. The PBX still functions, outbound manual calls still function, inbound calls, voicemail, nothing else appears to be negatively impacted. However new files introduced into /var/spool/asterisk/outgoing/ folder get ignored. No messages spring up on asterisk -rvv console, nothing shows up in the logs, the .call files just get snubbed. We're at a loss to determine what other debugging avenues may be available, and we have googled for every applicable keyword we can think of including "asterisk auto dial" and "pbx_spool" to no avail.


We are running:
Asterisk 1.8.13.1~dfsg1-3+deb7u3 built by pbuilder @ pungenday on a x86_64 running Linux on 2014-01-04 01:03:48 UTC

on Debian Linux stable (wheezy). It is possible that this symptom began a few months ago after a system update (apt-get update; apt-get upgrade).


Any advise to further track down what is going on would be appreciated, thank you!


- - Jesse Thompson
Webformix, Bend OR
www.webformix.com

[asterisk-03 at jeremyk...]

On 4/30/2014 7:24 PM, Jesse Thompson wrote:

[jesset at gmail.com]