Summary: | ASTERISK-21003: MOH keeps playing for the fist participant, if two participants connect at the same time to an empty conference | ||||
Reporter: | hristo (hristo) | Labels: | |||
Date Opened: | 2013-01-28 07:31:36.000-0600 | Date Closed: | 2013-01-28 11:09:43.000-0600 | ||
Priority: | Minor | Regression? | |||
Status: | Closed/Complete | Components: | Applications/app_confbridge | ||
Versions: | 11.2.0 | Frequency of Occurrence | Constant | ||
Related Issues: |
| ||||
Environment: | debian squeeze 64-bit | Attachments: | ( 0) moh-keeps-playing.log | ||
Description: | I have made the following test:
Two users connect to a ConfBridge conference at about the same time. The are the first two users to connect to the conference and both have the same profile: admin=yes marked=yes announce_user_count=yes announce_join_leave=yes music_on_hold_when_empty=yes Note: I don't think "admin" and "marked" are relevant for this bug, because I see the same problem when I test with non-admin users too, but I include them here, because that's how I generated the attached debug log. The interesting part starts after the announcements with the users' names are recorded and I press the '#' at the same time for both users to end the recording (lines 679 and 684 in attached debug). One of the users is bridged first and hears all single user related announcements, the other it bridged a fraction of a second later and hears a different set of announcements. Up until now everything is ok and expected, however, as soon as all announcements finish playing the user that was bridged first starts listening to the music on hold (line 3333 in debug) instead of being able to talk to the other participant that joined just a few milliseconds later. What is worse, the first user doesn't even realize that everything he says is being transmitted into the conference while he's listening to the MOH. The MOH keeps playing until the user disconnects from the conference (line 5513). | ||||
Comments: | By: hristo (hristo) 2013-01-28 07:34:05.212-0600 console output with debug enabled By: Richard Mudgett (rmudgett) 2013-01-28 11:09:26.160-0600 This is a duplicate of ASTERISK-20606. The fix is not in Asterisk 11.2. It will be in the next release. |