Summary:	ASTERISK-06202: CPU load increasing when a SIP client using iLBC is left alone in a MeetMe conference
Reporter:	Antonio (asvaranda)	Labels:
Date Opened:	2006-01-26 10:10:29.000-0600	Date Closed:	2011-06-07 14:02:38
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Applications/app_meetme
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	The CPU load of the box running Asterisk increases when a SIP client using iLBC is left alone in a MeetMe conference after other clients left. This happens only when the clients are using iLBC codec! The scenario is as follows: 1) A sip client joins a meetme conference 2) Other client(s) join in 3) Some client(s) leave the meetme conference 4) When there is only one client left in the meetme conference, the CPU goes up about 6/7% per each meetme conference in which this situation takes place! The server only recovers from this state when this last client leaves the conference. If this happens in 10 conferences at the same time, asterisk will easily eat almost 100% of CPU. I managed to get an asterisk with only 12 clients in this scenerio using more than 90% CPU of the machine. In a normal situation this box would hold up to 60 participants using iLBC. ****** ADDITIONAL INFORMATION ****** The current workaround to this, was to use the old implementation of iLBC codec module from version 1.0.9. Using this one, the normal flow of execution takes place.
Comments:	By: Olle Johansson (oej) 2006-02-02 01:11:16.000-0600 Any updates? Anyone that can repeat this? /Housekeeping By: Patrick Himebrook (thuper) 2006-03-21 16:59:54.000-0600 Does this happen using exclusively ilbc? By: Serge Vecher (serge-v) 2006-05-01 16:12:07 No response from reporter. If anyone is able to reproduce this issue, please contact a bug marshall on the #asterisk channel to reopen.