On Sun, 3 Jun 2012, Tom Browning wrote:
AGI script has exit handler that connects and updates an external
database upon BYE from either side.
I know that if exit handler hangs around too long, Bad Things (tm) will
happen.
One of the systems I coded uses an AGI at call completion to update the
database, convert the accumulated WAV files to WMA, and upload the WMA to
a web server running on an over-subscribed Godaddy host*.
This AGI (which should only take about 20 seconds) occasionally takes a
minute or 3 to complete, but it does complete. What kinds of problems are
you seeing when your AGI takes too long?
*) If I get a chance to re-code it, I'd just write a database record and
then cobble up a daemon or cron job to do the heavy (and time consuming)
lifting.
--
Thanks in advance,
-------------------------------------------------------------------------
Steve Edwards [email protected] Voice: +1-760-468-3867 PST
Newline Fax: +1-760-731-3000
--
_____________________________________________________________________
-- 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
