[asterisk-bugs] [JIRA] (ASTERISK-20606) Wrong confbridge behavior when participants enter simultaneously

[Jonathan Rose (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-20606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=198911#comment-198911 ] 

Jonathan Rose edited comment on ASTERISK-20606 at 10/25/12 2:47 PM:
--------------------------------------------------------------------

Did you actually test this in 11.0.0-beta2?

I ask this because 11.0.0-beta2 contains a commit r374657 which was aimed specifically at these sorts of problems that 10.9.0 does not.  This same fix is also in more recent versions (unreleased) of 10 as well.
                
      was (Author: jrose):
    Did you actually test this in 11.0.0-beta2?

I ask this because 11.0.0-beta2 contains a commit r374652 which was aimed specifically at these sorts of problems that 10.9.0 does not.  This same fix is also in more recent versions (unreleased) of 10 as well.
                  
> Wrong confbridge behavior when participants enter simultaneously
> ----------------------------------------------------------------
>
>                 Key: ASTERISK-20606
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20606
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 10.9.0, 11.0.0-beta1, 11.0.0-beta2
>            Reporter: Eugenia Belova
>            Severity: Critical
>
> We test confbridge and detected next situations
> The first one is when participants enter simultaneously into not existent conference. Moh plays in one of the channels. We detected this behavior in 11.0.0-rc1/2 versions.
> The second one is when there is a participant in the conference (he is listening to the moh) and two other participants enter the same conference simultaneously. The first participant continues to listen to the moh. We detected this behavior in 10.9.0 version.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira