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.
I've got a reply from Shokz support, too. They explain the reason for the problem like you, but due to the feedback from several users they now reported the problem to their development department. Hopefully there will be a firmware update soon.
I too am having the same problem since just a few days ago. I am also using the Sennheiser HD 450BT
For some reason I was not hearing beeping sound again when I muted mine today. I pressed both volume up and down simultaneously though. I was under the impression that I needed to press it each time I unmute and mute it again. Will check again tomorrow...
Has this issue been resolved?
Same here from last week! Driving me crazy...