Summary:ASTERISK-19491: MeetMe fails to remove participant from conference when user leaves during playback of 'conf-onlyperson.ulaw'
Reporter:Andrew (edge87)Labels:
Date Opened:2012-03-06 15:46:22.000-0600Date Closed:2012-11-07 11:19:34.000-0600
Versions: Frequency of
is duplicated byASTERISK-20486 MeetMe Unable to write frame to channel after SIP channel hangs up.
Environment:Ubuntu Linux latest kernel 3.0.0-12-server #20-Ubuntu SMP x86_64 x86_64 x86_64 GNU/LinuxAttachments:( 0) Asterisk_debug_log
Description:When calling the Meetme() application if you hangup on the initial prompt it floods the CLI with these messages endlessly:

Unable to write frame to channel SIP/7081053DA9E1-00000000
Unable to write frame to channel SIP/7081053DA9E1-00000000

If I call it back again, I get a tone as though I'm the second person in the conference call. When I hang up again it then destroys the conference and then stops the messages.

I'm able to reproduce this every time. I had this issue on 1.8.7 and then upgraded to 1.8.10 to see if the issue was resolved before reporting it.
Comments:By: Matt Jordan (mjordan) 2012-03-13 09:33:39.379-0500

We require a complete debug log to help triage the issue. This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

By: Andrew (edge87) 2012-03-13 11:15:47.377-0500

I followed the logging to a T, and the messages are inside the log, but were not present in the console after turning on debugging. I called the Meetme() application 3 times and all three times it did this.

By: Andrew (edge87) 2012-03-13 13:09:29.829-0500

I have attached the debugging log and commented.

By: Johan Wilfer (johan) 2012-08-29 02:09:59.831-0500

This is similar to ASTERISK-19949, you could try the patch there.

By: Julian Yap (jyap) 2012-08-29 04:23:00.454-0500

I can reproduce this on: certified-asterisk-1.8.11-cert4

By: Jonathan Rose (jrose) 2012-11-07 11:19:34.863-0600

Please follow this issue through ASTERISK-20486