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)
Been using Teams since the start of lockdown with a headset. As of today I am getting a double-beep at about five second intervals (like a hold beep) in the headset when I am muted. This has not happened before and been using same headset for months.
Also note that when I mute / unmute in Teams, the headset now announces "mute on" and "mute off" to me.
This feels like a Teams update has created this "feature" - please turn it off!
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.
OMG!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! It Works! I can't believe it! The Setting is in Teams.
After trying SOOO many headsets and finally discovering Aeropex, only to be crushed by a Teams update...sigh.
My workaround is to use an alternate microphone, while keeping Aeropex for the speaker setting. I'm getting voice quality complaints again, but at least I can hear :-/
I tried using the ASUS USB-BT500 dongle but the beeps persisted.
Well, on the plus side, they implemented this feature that allows you to save 20 keystrokes in a day with an auto response you can pick. Never mind the fact that you can't think straight about what to choose with beeping noises blaring in your ear.
So my Aftershokz OpenCom just started doing this as well, out of nowhere. Seems to be a whole slew of new posts within the past two weeks. Do not know what you did MS, but please fix it!
What I can't understand is if it's a function of the device that Teams triggers inadvertently, or something built into Teams for certain use cases? Seems most but not all the posts are on the OpenComms from Shokz. I haven't tried to use the OpenComms in another application to test if I can get this to happen somehow outside of Teams. That might help figure out what Teams just started doing to trigger it.