From 6916252ce11142db84a10efe5b04abb70e560705 Mon Sep 17 00:00:00 2001
From: Leonard Kim <leonard.h.kim@gmail.com>
Date: Wed, 28 Mar 2018 10:44:02 -0700
Subject: [PATCH] fix(toolbar): exercise conference audio toggling

The redux flows do not account for as many scenarios, such
as config.startWithAudioMuted being true.
---
 .../components/buttons/AudioMuteButton.web.js      | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/react/features/toolbox/components/buttons/AudioMuteButton.web.js b/react/features/toolbox/components/buttons/AudioMuteButton.web.js
index 27f8b6634..072352c76 100644
--- a/react/features/toolbox/components/buttons/AudioMuteButton.web.js
+++ b/react/features/toolbox/components/buttons/AudioMuteButton.web.js
@@ -4,6 +4,7 @@ import PropTypes from 'prop-types';
 import React from 'react';
 import { connect } from 'react-redux';
 
+import UIEvents from '../../../../../service/UI/UIEvents';
 import {
     ACTION_SHORTCUT_TRIGGERED,
     AUDIO_MUTE,
@@ -122,6 +123,19 @@ export class AudioMuteButton extends AbstractAudioMuteButton {
 
     _doToggleAudio: () => void;
 
+    /**
+     * Emits an event to signal audio mute should be toggled.
+     *
+     * @private
+     * @returns {void}
+     */
+    _doToggleAudio() {
+        // The old conference logic must be used for now as the redux flows do
+        // not handle all cases, such as unmuting when the config
+        // startWithAudioMuted is true.
+        APP.UI.emitEvent(UIEvents.AUDIO_MUTED, !this.props._audioMuted, true);
+    }
+
     _onShortcutToggleAudio: () => void;
 
     /**