Summary:	ASTERISK-29164: ast_write: Failed to write data to channel monitor write stream
Reporter:	Rosa Atienza (atienzar)	Labels:
Date Opened:	2020-11-13 08:20:32.000-0600	Date Closed:	2020-11-13 08:20:33.000-0600
Priority:	Minor	Regression?
Status:	Closed/Complete	Components:	Applications/app_mixmonitor
Versions:	13.33.0	Frequency of Occurrence
Related Issues:
Environment:	A VM with Debian 9.2 and Asterisk 13.33.0	Attachments:
Description:	We have a tons of this message :    -- Called SIP/136    -- SIP/136-00025c9d is ringing       > 0x7f708803c310 -- Strict RTP learning after remote address set to: 10.20.1.70:8000    -- SIP/136-00025c9d answered SIP/lcr-00025c99    -- Stopped music on hold on SIP/lcr-00025c99    -- Channel SIP/136-00025c9d joined 'simple_bridge' basic-bridge <9bf4f29d-c8ca-425b-94ec-5e21e187db52>    -- Channel SIP/lcr-00025c99 joined 'simple_bridge' basic-bridge <9bf4f29d-c8ca-425b-94ec-5e21e187db52>       > 0x7f708803c310 -- Strict RTP switching to RTP target address 10.20.1.70:8000 as source [Nov 13 14:26:47] WARNING[28566][C-00015f3e]: file.c:259 ast_writestream: Translated frame write failed [Nov 13 14:26:47] WARNING[28566][C-00015f3e]: channel.c:5577 ast_write: Failed to write data to channel monitor write stream [Nov 13 14:26:47] WARNING[28613][C-00015f3f]: file.c:259 ast_writestream: Translated frame write failed [Nov 13 14:26:47] WARNING[28613][C-00015f3f]: channel.c:5577 ast_write: Failed to write data to channel monitor write stream [Nov 13 14:26:47] WARNING[28613][C-00015f3f]: file.c:259 ast_writestream: Translated frame write failed [Nov 13 14:26:47] WARNING[28613][C-00015f3f]: channel.c:5577 ast_write: Failed to write data to channel monitor write stream [Nov 13 14:26:47] WARNING[28613][C-00015f3f]: file.c:259 ast_writestream: Translated frame write failed [Nov 13 14:26:47] WARNING[28613][C-00015f3f]: channel.c:5577 ast_write: Failed to write data to channel monitor write stream [Nov 13 14:26:47] WARNING[28613][C-00015f3f]: file.c:259 ast_writestream: Translated frame write failed [Nov 13 14:26:47] WARNING[28613][C-00015f3f]: channel.c:5577 ast_write: Failed to write data to channel monitor write stream ...... [Nov 13 14:26:51] WARNING[28613][C-00015f3f]: channel.c:5577 ast_write: Failed to write data to channel monitor write stream    -- Channel SIP/250-00025c9b left 'simple_bridge' basic-bridge <85fbf056-ce80-4240-930f-686ce2285f5a>    -- Channel SIP/lcr-00025c9c left 'simple_bridge' basic-bridge <85fbf056-ce80-4240-930f-686ce2285f5a>  == Spawn extension (macro-troncal, s, 13) exited non-zero on 'SIP/250-00025c9b' in macro 'troncal'  == Spawn extension (from-user, 988111222, 2) exited non-zero on 'SIP/250-00025c9b'    -- Executing [h@from-user:1] Set("SIP/250-00025c9b", "CDR(stats)=ssrc=999111222;themssrc=719880945;lp=0;rxjitter=0.000000;rxcount=1027;txjitter=0.015241;txcount=738;rlp=0;rtt=0.056869") in new stack    -- Executing [h@from-user:2] System("SIP/250-00025c
Comments:	By: Asterisk Team (asteriskteam) 2020-11-13 08:20:33.198-0600 We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. If this issue is actually a bug please use the Bug issue type instead. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Asterisk Team (asteriskteam) 2020-11-13 08:20:33.733-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. Please note that log messages and other files should not be sent to the Sangoma Asterisk Team unless explicitly asked for. All files should be placed on this issue in a sanitized fashion as needed. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. Please note that by submitting data, code, or documentation to Sangoma through JIRA, you accept the Terms of Use present at [https://www.asterisk.org/terms-of-use/|https://www.asterisk.org/terms-of-use/].