[asterisk-bugs] [Asterisk 0014117]: Incorrect processing of "maxuser" parameter in real-time meetme
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Jan 14 08:59:49 CST 2009
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: feedback
Asterisk Version: SVN
Regression: No
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 163991
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-12-19 13:48 CST
Last Modified: 2009-01-14 08:59 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?
======================================================================
----------------------------------------------------------------------
(0097719) seanbright (manager) - 2009-01-14 08:59
http://bugs.digium.com/view.php?id=14117#c97719
----------------------------------------------------------------------
Actually, I see what the problem is now. The previous two patches won't
fix it completely. I'll whip up another one in an hour or so.
Issue History
Date Modified Username Field Change
======================================================================
2009-01-14 08:59 seanbright Note Added: 0097719
======================================================================
More information about the asterisk-bugs
mailing list