Managing sound and video settings during Teams meetings and calls for optimal communication
OMG!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! It Works! I can't believe it! The Setting is in Teams.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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.
My aftershokz started this really annoying problem this morning. I removed the headset from the bluetooth audio options in my Windows 10 HP laptop, performed a factory reset on the headset, and re-paired to the laptop. the beeping and mute notifications are now gone. Please give this a try everyone.
I also have the Aftershokz OpenComm and started getting this behavior after MS Teams updated.
MS Teams isn't causing the beeping, it is the headset. You can prove this by muting the headset microphone in the Windows Sound settings. Same thing happens. I think what Teams changed is that instead of just ignoring the mic, it now synchronizes with the system sound. This would be a good thing, except for the OpenComm trying to deafen me with the beeping noises.
Thanks to ToddAtnip and DavidLopezA for the tip of using a Jabra dongle. I have a "Jabra Link 370") and disabling the Call Control/Softphone Integration in Jabra Direct worked to avoid Teams muting the headset and causing the beep.
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.
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.