[asterisk-bugs] [JIRA] (ASTERISK-19726) [patch][bug] ConfBridge - Users listening to MoH, and who should be muted, are often unmuted and recorded

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-19726?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-19726:
-----------------------------------

    Target Release Version/s: 10.10.0
    
> [patch][bug] ConfBridge - Users listening to MoH, and who should be muted, are often unmuted and recorded
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-19726
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-19726
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Applications/app_confbridge
>    Affects Versions: SVN, 10.0.1, 10.1.0, 10.1.1, 10.1.2, 10.1.3, 10.2.0, 10.2.1, 10.3.0, 10.4.0, 10.5.0
>            Reporter: Neil Tallim
>            Assignee: Neil Tallim
>            Severity: Critical
>      Target Release: 10.10.0
>
>         Attachments: allow_forced_mute.diff, bugASTERISK-19562_ASTERISK-19726_ASTERISK-20181.patch, moh_crash_fix_-_apply_afterwards.patch, moh_mute.patch, moh_prompt_fix_-_apply_after_crash_fix.patch, muting.patch
>
>
> app_confbridge has something of a mind of its own when it comes to deciding when to mute users and when to put them on hold. It also has a tendency to not mute users while they're on hold.
> While working on some other patches to correct this inconsistent behaviour (without negatively altering the user experience), my team discovered something shocking: we were being recorded while on-hold, before a conference started. Further testing showed that this happened while on-hold in a number of cases, and even when we thought we were muted. We did not observe this behaviour without recording because we had no users without WAITMARKED set in our testing scenarios.
> Further exploration showed that this issue affects unpatched versions of ConfBridge, thus justifying why it has been submitted as a critical issue.
> This patch works by introducing a "forced mute" flag on participants, which prevents app_confbridge's whimsical unmuting of participants who were explicitly muted via AMI/CLI and ensuring that all MoH is accompanied by appropriate muting logic.
> IMPORTANT: This patch builds upon other patches, which must be applied first, for it to be effective. These patches introduce corrective behavioural changes, but should have no unintended side-effects and have been in production in my environment for weeks with no observed problems:
> ASTERISK-19562
> ASTERISK-19724

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