I've found that I get this error when I don't properly listen for
asterisk responses to my commands in my agi scripts. Anytime you send
a command to asterisk from an agi script, asterisk sends a response to
the script with the result of the command (i.e a 200 ok response if
asterisk was able to properly execute the command). If your script
doesn't properly handle these responses, you get the error mentioned
below.
It's never caused any of my calls to drop, though. Try turning on AGI
debug to see if this is the case for you.
Thanks,
--Warren Selby
On Jan 26, 2010, at 5:11 AM, "Lee Archer" <lee.arc...@thebigword.com>
wrote:
Hi, does anyone have an info into what could cause
[Nov 28 14:24:48] ERROR[11964] utils.c: write() returned error:
Broken pipe
[Nov 28 14:25:08] ERROR[12540] utils.c: write() returned error:
Broken pipe
[Nov 28 14:25:08] ERROR[12540] utils.c: write() returned error:
Broken pipe
[Nov 28 14:26:23] ERROR[13098] utils.c: write() returned error:
Broken pipe
Is it a write process or a problem with one of the scripts I am
running? I am seeing this over and over again and experience call
drops on a percentage of calls.
Thanks
Lee
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
