Steve Edwards wrote: > On Wed, 28 Apr 2010, Gareth Blades wrote: > >> The script does not issue any commands. The same script is called at all >> 3 stages but with different parameters on the command line to indicate >> the call status. Works fine before the call is answered but during and >> at the end of the call it quits before asterisk has finished sending the >> information about the current call via STDIN. > > As others have said -- you are violating the protocol. > > Asterisk sends the "AGI environment" to the AGI via STDIN. If you don't > read it, you are violating the protocol. > > For a AGI that is called repeatedly, maybe you should consider > implementing it in a compiled language. > > You can execute XXX AGIs written in C in the time it takes to load the > Perl interpreter and parse your script. >
We are reading in the STDIN (assume its part of the asterisk perl module). If I add a 3 second pause to the end of the perl code then it works fine. But if this is the case then for a system with a high call volume this significantly increases the number of running AGI programs which is not good for system load. -- _____________________________________________________________________ -- 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