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.
Yup. Randomly started a few days ago with my Aeropex and it's extremely annoying. I'm not holding out much hope for a fix since I haven't even seen them acknowledge it as an issue. I wish I could use something other than Teams but it's for work so there's not an option.
This is by far one of the worst features I've ever seen in an application. I don't even know what the real world scenario is where anyone would ever want this to happen. Started happening again for me in a recent update.
Yeah, agree. That's what makes it so mystifying. There no reason I can think of that anyone would want the stupid thing thing to beep in your ears every minute that you're on mute.
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.