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.
This is really frustrating. Today beeps are back ;.(. No clue how and why. Will test further.
Hi Jim, I can't disagree with you on this, Microsoft should definitely have reverted this change if it caused only frustration. All I'm saying is that maybe they had a good reason to enable it and maybe this reason is still valid despite the frustrations. Their answer about using certified headset is 100% tactless and unacceptable though.
But on the other hand I can't figure out why a Smart company like Shokz would put such a loud unusable beep in their firmware, didn't they test this feature ? And I'm upset that they didn't provide the possibility for end users to update the firmware. It's a $160 device for god sake...
I've been doing this a long time and as I think through it from all sides I suppose I can find some sympathy for MS...
But their response "get a certified device" amounts to "authoritarianism" (which is nothing new...) They can do that because they ARE the 800 pound gorilla.
Stepping back a bit it's also easy to see that Aftershokz is not the only hardware affected... many unique devices have been reported in this forum (and elsewhere). Some of them have issued firmware updates, etc... in support of their products.
But Teams is a MS product and as a peripheral company, I think its a mistake for Aftershokz to profiteer on this customer issue... A response of "we're sending you a dongle that will circumvent the issue" would be more appropriate.
In any case, I also don't like being put in the position of spending my money and time fighting that "gorilla" for Aftershokz, but I've been here many times...
And by the way, using my laptop's mic works well for me, I spend 99% my "Teams" time in close proximity, so for now I'm not feeling the pain.
In my case this just disconnects me totally. no beep but also no audio, no mic...