Recently headset busylight not clearing after Teams meetings, but behaving correctly for 1:1 calls

Anonymous
2023-01-30T07:37:30+00:00

I've long used call controls and presence with my Jabra headset & Teams, however recently I to started having the problem of either MS Teams or Jabra Direct not clearing the busylight status following the ending of Teams meetings. I've isolated this down to be Teams meetings specifically, if I call a colleague directly the busy status will clear correctly, but if I dial a meeting it will not clear.

Likewise if I do the Settings/Devices/Make a test call, it reliably turns on the busy light then turns it off when the call finishes.

I use a Jabra Evolve 75 headset, the latest version of Jabra Direct and MS Teams 1.6.00.1381 (64-bit), on Windows 10 Pro.

When its in its busy status, call controls continue to function reliably, if I make a new call. And if close Teams and Jabra Direct, the busy light status clears, until I make another call where it goes busylight again as it should. So strangely all is functioning, except for clearing busy status after hanging up a Teams meeting.

Following reading other reports on forums, I've tried; Rebooting. Disabling microphone permissions from Windows 10 Catana search. Manually disabling & re-enabling busylight. Upgrading "Intel Smart Sound Technology for USB Audio" divers. Then later disabling Intel's USB Audio, and rebooting. With no change, the busylight still doesnt get cleared from Team's meeting.

Any ideas for further troubleshooting or whether this is a known bug? (it didnt used to be)

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Other

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 No comments

111 answers

Sort by: Most helpful
  1. Anonymous
    2023-02-22T13:24:04+00:00

    Hello

    for those that are using a Jabra headset, did you try to install this application "Jabra Direct"

    and did it solved your problem ?

    For us, it seem to correct the problem but I'm a bit off to install an application when it's not needed for using Teams

    Was this answer helpful?

    0 comments No comments
  2. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  3. Anonymous
    2023-02-21T20:23:47+00:00

    I opened a ticket with Microsoft after posting here and seeing how many other users from different companies and headsets are having similar issues with no resolution. After doing analysis gathering with Microsoft support, I received this response today. "Our product group has identified the root cause of the issue and a fix has then been rolled out. The fix will hit the general ring end of this month or early next month. The fix is for all headsets."

    This is all the details they provided but at least the good news is that the fix is few weeks away.

    Thanks Jeff. Have you had any updated timeframe for the fix. Going by your post it still a week or 2 away :(

    Cheers

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-02-21T16:35:15+00:00

    The fix has not yet rolled out to me and the issue still occurs. I *did* install the most recent "patch Tuesday" patches. My Teams version still shows "You have Microsoft Teams Version 1.6.00.1381 (64-bit). It was last updated on 2/6/2023.". When I manually checked for updates just now, the response was "You've got the latest updates. Enjoy!". So I'll continue to wait for the fix to roll my way.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-02-21T16:23:02+00:00

    Curious how you got that version. I'm in the Developer and Public preview rings and I'm only up to v1.6.00.2588

    Was this answer helpful?

    0 comments No comments