This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
When using my Aftershokz OpenComm during a call, I hear a loud beeping noise when I mute myself during the call. This beeping only goes away when I unmute. I've contacted Aftershokz, and they've assured me this is due to a recent MS Teams update causing connectivity issues.
I've also read other non-Microsoft forums and realize this is apparently an issue since 2021 with MS Teams and multiple brands of headphones/headsets. However, it only recently started for me today, April 18, 2022.
Is Microsoft doing anything to solve this issue? Is there a solution to this?
It seems to be making many users upset and frustrated. I'm surprised Microsoft hasn't addressed this yet.
Managing sound and video settings during Teams meetings and calls for optimal communication
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Same problem, same Opencomm headset. I updated Bluetooth drivers to the latest Intel drivers this morning, no improvement.
This is really a kick in the teeth, as the Opencomms have been just about perfect since I got them more than 6 months ago.
So... I've heard back from Shokz.
First thing is to understand what's going on.
When you "mute" your audio, there are two ways that an application can do this. The first way is to turn the gain on the microphone input down to zero. That means you don't get any input from the microphone. The second way is to tell the microphone to mute. Although the effect on the audio is equivalent, the two ways are very different. The first way just stops any audio from the mic. The second way explicitly sets the mute, which can do additional action such as turning on a red LED on the microphone, etc.
Why is this important?
If you explicitly tell the Shokz headset to "Mute", then it tells you this - "Mute on", then beeps whilst on mute, then "Mute off" when you cancel the mute again. The Shokz headset isn't alone in doing this, apparently some other headsets do this too (but I don't have any so can't confirm this behaviour).
If you just turn the microphone gain down to zero, the Shokz headset hasn't actually been muted, so you get no notification.
When you "mute" on Zoom, it just turns the microphone gain to zero. It doesn't actually mute the input.
In earlier versions of MS Teams, when you "mute", it also turned the microphone gain to zero. It didn't actually mute the input.
In the recent update to MS Teams, when you "mute", then it does actually tell the microphone to "mute". This means the microphone would know to turn on its red LED, etc. Unfortunately, for the Shokz headset, this means you get the irritating notifications, beeps, etc.
Now, all these notifications, beeps, etc. are all generated within the Shokz headset. They don't come from Windows. It's the Shokz headset firmware making all these noises. The correct fix is for Shokz to have an option on their headset to disable the mute notifications. Unfortunately, they don't.
There are some solutions:
The WebApp version of Teams, when you "mute", simply turns the mic gain down to zero. It doesn't tell the headset to mute. So, the WebApp doesn't make the headset beep, etc. I've switched over from the Desktop version to the WebApp version of Teams, and it's all OK again. Microsoft - please, please, please don't change the WebApp to mute the audio sources properly!!!!
I really, really hate this option. I hate that Shokz have even done this. What they have done is take a generic BT dongle that's worth perhaps £10 at best, then put a different software driver on it that blocks the mute command from getting to the headset. Now when the app tells the headset to "mute", the driver blocks the mute command and instead turns the microphone gain to zero. Magic. No beeping.
What the dongle gets wrong is when you turn off the headset, it doesn't remove the audio source, so your audio configuration doesn't switch over to your other speakers (if you have them).
I hate that Shokz have basically left this issue with the firmware in their headset, then tried you to pay 5x for a generic BT dongle with some hacked drivers that work around the firmware issues in their headset.
Bottom line, this isn't a Microsoft problem, this is a Shokz problem with some very unfriendly firmware in their headset, and they refuse to fix it. Instead, they want you to spend _another_ £50 to buy their custom BT dongle and driver, which 5x overpriced.
I love the Shokz headset... I really hate the way that the Shokz company is behaving.
I can confirm that the beeping when muted only when using the Teams desktop application. When I use the web Teams browser the beeping goes away.
Same issue here with a Sennheiser HD 458BT
I become mad with theses beeps
I agree as well on using AfterShokz OpenComm. I use Team call from Phone for now until this issue is resolved.
The pressing-button-a-little-longer trick did not work for me. I will try the web team next.
Updated: I use the Team on Web and there is NO issue with beeping when on Mute!