[asterisk-bugs] [Asterisk 0013173]: Asterisk blocked when 2 or more users leave a meetme when announce user is on

[Asterisk Bug Tracker]

The following issue is now READY FOR TESTING. 
====================================================================== 
http://bugs.digium.com/view.php?id=13173 
====================================================================== 
Reported By:                pep
Assigned To:                jpeeler
====================================================================== 
Project:                    Asterisk
Issue ID:                   13173
Category:                   Applications/app_meetme
Reproducibility:            always
Severity:                   block
Priority:                   normal
Status:                     ready for testing
Asterisk Version:           1.4.21.1 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-07-27 05:46 CDT
Last Modified:              2008-10-20 17:45 CDT
====================================================================== 
Summary:                    Asterisk blocked when 2 or more users leave a meetme
when announce user is on
Description: 
If option I is used with meetme and 2 or more participants leave a
conference simultaneously, Asterisk stops working properly.  As the number
of simultaneous users leaving increases, the affect on Asterisk is
increased.

When the users hangup, zap channels stop accepting calls until the "user
has left the conference" message has played.  When several users leave
simultaneously the dialplan stops executing.
console commands such as meetme and core show channels will stop working. 
Sometimes the response is delayed by a few seconds and sometimes nothing is
returned at all.

When a larger number of users disconnect at the same time, Asterisk
becomes completely unusable without a restart
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-10-20 17:45 jpeeler        Status                   assigned => ready for
testing
======================================================================