On Apr 28, 2010, at 1:00 PM, Gareth Blades wrote: > Steve Edwards wrote: >>> Steve Edwards wrote: >>>> How do you reconcile your assumption that the Perl module is reading >>>> STDIN and your statement that your AGI "quits before asterisk has >>>> finished sending the information about the current call via STDIN." >> >> On Wed, 28 Apr 2010, Gareth Blades wrote: >> >>> Only that if I put a 3 second pause in the script at the end then I get >>> no errors. If I put in a 1 second pause I get errors about half way >>> through asterisk sending the input. >> >> The fact that you have to introduce a pause means that you are doing >> something wrong. It may just mean that Asterisk has finished writing the >> cruft to the created process's STDIN instead of being interrupted in the >> middle, but whatever you are doing is still wrong. >> >> There is an outside chance that you have discovered a bug in Asterisk, but >> considering nobody else has experienced this behavior implies the bug is >> in your code. >> >> Why are you so resistant to this? What evidence do you have that your code >> is correct? >> > > I am not resistant to it. I didnt write the code and I an not that > familiar with perl. > > It just seemed strange that the debug output from the mode-start script > run appeared instantly on the screen but for the other AGI code > executions I could see the debug output scroll up slowly.
Did I miss where the code was posted? ---fred http://qxork.com -- _____________________________________________________________________ -- 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