Okay, the next time it gets in this state I’ll gather that information.
[mailto:asterisk-users-bounces@xxxxxxxxxxxxxxxx] On Behalf Of Warren Selby
On Fri, May 18, 2012 at 12:00 PM, Justin Killen <jkillen@xxxxxxxxxxxxxxxxxxxxxx> wrote:
I have and automated call-in dispatch system where hundreds of people call in daily for 2-3 minutes each. The extension is set up to get their information, then text-to-speech the dispatch information (via odbc). It then loops 5 times then ends the call. These calls are being handled by an 8 port analog digium card.
Sometimes though, I see calls via ‘core show channel dahdi/1-1’ that have a time of > 16 hours. I’m not sure if this is a result of dahdi missing the hangup, ODBC timing out, or TTS failing for some reason. When a channel gets in this state, the call doesn’t seem to progress through the dialplan, they always display the TTS line. Doing a ‘dahdi destroy channel 1-1’ doesn’t seem to be effective – the only way I’ve been able to clear the calls is to do a ‘dahdi restart’ and/or restart the asterisk service.
For TTS I’m using cepstral with the Swift wrapper.
Here is a snippet of my dialplan:
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Gnu Gatekeeper] [IETF Sipping] [Info Cyrus] [ALSA User] [Fedora Linux Users] [DCCP] [Gimp] [100% Free Online Dating] [Yosemite News] [Arts & Crafts] [Yosemite Photos] [Deep Creek Hot Springs] [Yosemite Campsites] [ISDN Cause Codes]