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.
Your very lucky to be able to use the headphone Sennheiser HB450T, and I to also have other headsets that, but this reply perhaps does not understand
for some that have hearing difficulties that the Aftershokz bone conducting is an option which improves the ability for some to hear correctly. Using the Aftershokz was a huge improvement for me. However, unlike standard headphones, and for me and perhaps others the beeping being in the higher frequency level is not only annoying but slightly painful. The bottom line is I don't care who sorts this out, but I suspect that since Microsoft introduced it then they have a responsibility to work with Aftershokz to find a solution that helps the deaf community.
Not willing to defend Microsoft but their only mistake has been to enable the support of bluetooth hands-free profile which was theoretically the right thing to do. The beep comes from the firmware of the headsets. Sennheiser removed it. All headset manufacturers could do the same or at least make it less noisy... Microsoft not using the hands-free profile would be a workaround for something they are not responsible for, that's probably the reason why they don't address this issue.
Just adding another data point to this thread. Been using Aftershokz OpenMove on Teams on my Microsoft Surface Book for almost a year with no issues... until this morning. 3 hour call with beeps every 5 seconds except for the 45 seconds I was speaking made for a LOUSY experience.
Microsoft should not lean on the headphone manufacturers to push firmware updates to solve their problem. The beeping seems to be baked into the native OS headset controls Teams now uses to run the bluetooth profile, so Microsoft can fix it in one update.
I don't see who would want the beep, but if someone with authority at MS is saying the feature needs to remain, then I'll spitball ideas:
-Maybe make the beep pop up if you start talking when you're still muted?
-Just add a checkbox to enable/disable the feature that defaults to enable until you change the profile for your headset?
-Add a voice echo if you're speaking on mute so it sounds like you're talking to a wall?
Don't beep at me when I'm listening in silence!
Similarly for my Sennheiser HD-450BT: after firmware upgrade (now 5.5.1), beeps are gone. Sennheiser removed the beep feature entirely. Problem solved...