[asterisk-bugs] [Asterisk 0015354]: MixMonitor - utils.c: write() returned error: Broken pipe

[Asterisk Bug Tracker]

The following issue has been CLOSED 
====================================================================== 
https://issues.asterisk.org/view.php?id=15354 
====================================================================== 
Reported By:                astvikas
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15354
Category:                   Applications/app_mixmonitor
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           1.6.0.10 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-06-18 08:06 CDT
Last Modified:              2009-09-17 14:51 CDT
====================================================================== 
Summary:                    MixMonitor - utils.c: write() returned error: Broken
pipe
Description: 
Whenever i use mixmonitor or call AGI in dialplan following error comes on
asterisk CLI and i think because of this my D-Channel goes down and calls
are getting disocnnected.
====================================================================== 

---------------------------------------------------------------------- 
 (0110888) lmadsen (administrator) - 2009-09-17 14:51
 https://issues.asterisk.org/view.php?id=15354#c110888 
---------------------------------------------------------------------- 
I am closing this issue for now because the ERROR messages I'm seeing was
fixed in a version somewhere just prior to 1.4.26, or just after 1.4.26 was
released.

If you still experience this error after testing the latest 1.4 release
candidate (1.4.27-rc1 currently), then please open a new issue with the
appropriate information in order to reproduce the issue.

Thanks! 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-17 14:51 lmadsen        Note Added: 0110888                          
2009-09-17 14:51 lmadsen        Status                   new => closed       
======================================================================