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.
No it doesn’t, it Unmutes and stops the beep, pressing and holding the volume up/power button turns the headset off. Pressing both up and down unmutes.
This still isn't fixed? I can't be in a meeting on mute cause all I hear is the double beep.
Yeah that works cause it turns the headphones off.
I figured it out in the end, somehow Shokz thinks your muted.
hold both VOLUME buttons (volume "+" and "-" at the same time) for about 3 seconds. You will hear MUTE OFF. then prob should be solved.
Hi I have the same issue with Teams and Shokz. My organization uses both Teams and Zoom. The issue is not occurring in Zoom, so it is Teams, not Windows that is creating the problem. I am moving meetings from Teams to Zoom wherever possible as a work-around until this is fixed because the Shokz headsets are becoming more common in my organization.