[asterisk-bugs] [Asterisk 0014117]: Incorrect processing of "maxuser" parameter in real-time meetme

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=14117 
====================================================================== 
Reported By:                sergedevorop
Assigned To:                seanbright
====================================================================== 
Project:                    Asterisk
Issue ID:                   14117
Category:                   Applications/app_meetme
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 163991 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-12-19 13:48 CST
Last Modified:              2009-01-15 09:34 CST
====================================================================== 
Summary:                    Incorrect processing of "maxuser" parameter in
real-time meetme
Description: 
I compile app_meetme with enable realtime. 
   rt_schedule = 1;
   fuzzystart = 1;
   earlyalert = 1;
   endalert = 1;
   extendby = 1;

Also I create a table which include `maxusers` field. Conference work fine
but with some bug. Imaging that I book conference with maxusers==2.
- 1st participant call to the asterisk, connect to the room and listen MOH
(music on hold)
- 2nd one call to the asterisk, connect to the room and listen MOH
- 3d one call to the Asterisk, enter the room_number, enter pin and get
play sound that "conference is full".
- 4th one call to the Asterisk, enter the room_number, enter pin and no
any sounds. Asterisk log show that las message was play "get pin number".
- If then conference will be not full, for example include only 1
participant any other calls to the conference will be processed like 4th.

What does it may be?

====================================================================== 

---------------------------------------------------------------------- 
 (0097912) svnbot (reporter) - 2009-01-15 09:34
 http://bugs.digium.com/view.php?id=14117#c97912 
---------------------------------------------------------------------- 
Repository: asterisk
Revision: 168706

_U  branches/1.6.0/
U   branches/1.6.0/apps/app_meetme.c

------------------------------------------------------------------------
r168706 | seanbright | 2009-01-15 09:34:35 -0600 (Thu, 15 Jan 2009) | 18
lines

Merged revisions 168705 via svnmerge from 
https://origsvn.digium.com/svn/asterisk/trunk

........
  r168705 | seanbright | 2009-01-15 10:33:18 -0500 (Thu, 15 Jan 2009) | 11
lines
  
  Add a missing unlock and properly handle the 'maxusers' setting on
MeetMe
  conferences.  We were using the 'user number' field to compare against
the
  maximum allowed users, which works assuming users with lower user
numbers
  didn't leave the conference.
  
  (closes issue http://bugs.digium.com/view.php?id=14117)
  Reported by: sergedevorop
  Patches:
        20090114__bug14117-2.diff.txt uploaded by seanbright (license 71)
  Tested by: sergedevorop
........

------------------------------------------------------------------------

http://svn.digium.com/view/asterisk?view=rev&revision=168706 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-01-15 09:34 svnbot         Checkin                                      
2009-01-15 09:34 svnbot         Note Added: 0097912                          
======================================================================