Recent update to Teams causes beeping in headset when on mute

Did not work for my model HD 458 BT.

This one did not work for my model but I was able to update it using the Sennheiser Smart Control Android App.

Install it from the app store and connect your headset to your phone and then you can install the update.

I know I'm late to the party, but I just recently started directly connecting my OpenComm to my laptop and had the same issue, but found an easy work around if anyone still needs it.

I believe the issue comes down to how the headset is recognized--both as headphones AND a headset--and how Teams reconciles that since Skype does not have the same problem. Though to be fair, I just figured this out and haven't been able to test more thoroughly.

The following steps have to be completed during every call, but are pretty quick. That may change depending on disabling the "headphones" in your BT devices, but again I haven't been able to play around with it:

1. Open Settings, click "Devices" (alternately you can right click "Bluetooth Devices" in the system tray and "open settings" there
2. Scroll down to the "Related Settings" section and select "Sound settings"
3. Scroll down to the "Input" section and select the link that says "Device properties and test microphone"
4. Under "Related Settings" select "additional device properties" which will open a new small window with four tabs: General, Listen, Levels, and Advanced. Click the "levels" tab.
5. If yours is like mine, there's a box that says headset with a sliding volume scale, and next to that is a text box where you can enter a number from one to 100 to set the volume percentage. To the right of that text box is a button with a speaker and the slashed red circle, indicating the headset speaker is off. CLICK THAT BUTTON.

The speaker will look like it's been unmuted, you'll hear "unmuted" in your headset, and the "hold beep" is gone. This will not unmute you in your Teams call.

Dave, Danial - Count me in. I am absolutely disgusted with Microsoft for not fixing this glitch resulting from their software update. Darn software engineers talk endlessly about how great their products are and live the good life from charging crazy-high prices, justified by how great their products are: And then when their products don't work, "it's a compatibility issue with another device of yours"; and then when THAT'S proven false by MILLIONS of others reporting the SAME problem having started at the SAME time, you get their answer #2 : "You need to buy our newer product"! Disgusting! I work in a medium-sized professional firm; we all started coming back to work after the pandemic highpoint (fall 2021), despite the fact that we work in an open office, by buying headsets (Aftershokz Model AS660), After a handful of blissful months, I now have to reserve one of our meeting rooms and move my laptop their to join a meeting; originally so that I can join the meeting without muting my mic. without disturbing the meeting (the irony there is that, once in the private conf. room, I don't need the headphones that I paid $150 for! SHAME ON YOU, MicroSoft! If NOTHING else, you ought to offer the millions of us who suffer from this problem, an update that undoes whatever that previous update did that caused this problem. Or you ought to buy every single one of the affected headsets from those of us that shelled out $150 for product that, following MS's update, no longer does what ti was bought for!

Hi,

dont know for you, but since today itself, no more beeps on my OpenRun Pro!!

And volume button are also now operationnals.

I didn't tried anything to get this, just... it happened. A patch or similar I guess.

Just hoping it's permanent !