Aftershokz headset alerting me that my Teams call is muted

Anonymous

I have the same question posed in this previous thread, but the solution hasn't worked for me. https://answers.microsoft.com/en-us/msteams/forum/all/double-beep-when-muted-on-teams-aftershokz/d67018d1-7081-4acf-b688-bf947a524058?page=1

In short, no matter how I try to mute my mic, the headset tells me mute is on and double-beeps every few seconds. It happens if I mute the call, mute in call settings, or even if I simply mute in my laptop's sound settings.

Teams does NOT alert me that I'm muted if I use a different headset or no headset -- only using the Aftershokz headset. This is an Aftershokz problem, not a Teams problem, but Aftershokz tech support has been unhelpful. I'm hoping someone here has a workaround.

This problem cropped up last fall, went away, and now is back.

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.

0 comments

68 answers

Anonymous

2022-10-31T08:37:03+00:00

Agree with @christian_314 Microsoft should change the way ms teams interact with headset. Don't blame it to the device manufacturer.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments
Anonymous

2022-10-28T15:22:17+00:00

I have the OpenComm headset and found a reddit thread with the fix for me.

Join the call, Mute in Teams, and then hold the Volume + and - button at the same time for 2 seconds.

This causes Teams to mute, but unmutes the headset itself.

The "mute chime" is by far the stupidest feature of these headset.

Makes 0 sense in a modern age of mute discipline on calls.
Was this answer helpful?

8 people found this answer helpful.

0 comments No comments
Anonymous

2022-09-30T13:48:38+00:00
Is anyone from MicroSoft going to take a look at this. It's only been made worse due to recent update and it IS NOT a problem with the headset. It is a problem with the way MicroSoft is choosing to interact with the headset.

OLD ACTION THAT WORKED
- Push the mute button in teams
- Teams muted the app and only the app
- Could still use the microphone in other apps WHILE teams was running.
- The headset itself was not muting but the system (OS/Software) was muting the sound into the App.
Teams was not trying to control the system. It was only muting its own input.

CURRENT ACTION THAT DOES NOT WORK
- Push the mute button in teams.
- Teams mutes the microphone at the OS level.
- The OS sends communication to headset to tell the headset to mute as well
- The headset mic is COMPLETELY muted and can not be used anywhere else
This process makes NO SENSE. If the user mutes in teams than they are only intending for Teams to be muted. Why would the assumptions by the developers be that the user want's to mute system wide? Further why is it necessary for the OS to tell the headset to mute? The OS can mute and has no reason to tell the hardware to mute. If the user wants the hardware to mute than they can push the button the headset to do so.
Was this answer helpful?

20+ people found this answer helpful.

0 comments No comments
Anonymous

2022-09-29T15:12:17+00:00

"Unfortunately this workaround does not work anymore since 1.5.00.21668. Now Teams is subscribed to changes within the button described in the 3rd bullet point. Every time I unmute in the settings, unmute also goes in Teams.

Why cannot it be configurable in Teams? Anyone from Teams' dev team here?"

Same here. Again and again this is disappointing by Microsoft Teams.
Was this answer helpful?

2 people found this answer helpful.

0 comments No comments
Anonymous

2022-09-29T14:25:34+00:00

Yes I just noticed this myself. Incredibly infuriating.
Was this answer helpful?

0 comments No comments