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

111 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-02-06T21:04:45+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.

    Was this answer helpful?

    20+ people found this answer helpful.
    0 comments
  2. Anonymous
    2023-02-01T15:55:14+00:00

    I also experience this issue (Jabra Evolve 75). This impacts more than just the visible status of the busy light, because I also cannot use my headset from my iPhone until the busy light is cleared. This implies that Teams truly hasn't released the headset.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  3. Anonymous
    2023-02-13T15:23:37+00:00

    Microsoft Premier Support provided me with an update on Friday:

    The issue was caused by the most recent monthly production rollout, which has already completed. However, we are currently working on a hotfix - original timeline for the fix for this issue was 2/27 but it is likely they'll be pushing a fix sometime next week.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  4. Anonymous
    2023-01-30T11:30:50+00:00

    Glad its not just me then. Its definitely something in Teams holding the headset connection open. I just quit out of teams and the headset disconnected straight away. 1 to 1 meetings are find, just in group meetings holding it open. Wasn't any issue up until recently so guessing it's maybe a Teams update?

    Sorry should have said, I'm using a Bluetooth headset and not a wired one.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  5. Anonymous
    2023-01-31T23:34:50+00:00

    Half the users in the office here are also having the issue. I hope MS fix it soon.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments