[asterisk-bugs] [JIRA] (ASTERISK-20987) non-admin users, who join muted conference are not being muted

[hristo (JIRA)]

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

hristo commented on ASTERISK-20987:
-----------------------------------

On a second thought, it now seems more reasonable to simply have the muted state exposed to the dialplan (like for example the 'locked' state via CONFERENCE_INFO) and if connecting to a muted conference to set the user profile accordingly. This will keep the current confbridge logic as is and at the same time will provide users with a choice whether to mute newly connecting users or not.

The only downside that I see to this approach is a race condition that will be introduced in case a conference is unmuted between the time the check is made and the time the user is actually connected to it. This can easily be several seconds until all announcement are played and and then the user will end up muted in a conference that is already unmuted, but I still think that this will be much better, than the current behavior.

I am not a programmer, but I had a quick look at the code in app_confbridge.c and it sure seems like a simple copy/paste of the part that reports the "locked" status and then simply changing "locked" to "muted" should do the trick.
                
> non-admin users, who join muted conference are not being muted
> --------------------------------------------------------------
>
>                 Key: ASTERISK-20987
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20987
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_confbridge
>    Affects Versions: 11.2.0
>         Environment: debian squeeze 64-bit
>            Reporter: hristo
>            Severity: Minor
>
> If an admin user sets global conference mute via 'admin_toggle_mute_participants' it only affects users, who are currently in the conference. Any new (or reconnecting) non-admin users, who join the conference after that are not being muted.
> I would certainly expect that once a conference is muted for all non-admin users, then it must remain muted, even when for example a user drops out of the conference and reconnects or new (late) users connect after it has started.
> This would have been trivial to resolve in the dialplan if the conference muted/unmuted state was somehow exposed via a variable or function (like CONFERENCE_INFO or similar), but without this I would consider it a bug.

--
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