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. 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

  2. Anonymous
    2023-02-07T16:48:32+00:00

    Same issue with Teams Certified Jabra Product. Software - Jabra Direct 6.5.31801
    Jabra Link - Firmware Version - 1.87.0Jabra Evolve 65 Firmware Version - 2.97.0Microsoft Teams Version 1.6.00.1381 (64-bit). It was last updated on 02-02-2023.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-02-07T14:47:04+00:00

    Same issues here with multiple Jabra headsets and numerous co-workers. Issue appears only after scheduled meetings, not one on one calls.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-02-07T14:23:00+00:00

    I've also been suffering from this issue. Extremely frustrating. Killing the Teams process and restarting does reset the headset status, but it's pretty poor that this issue was ever allowed to appear in the first place...

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-02-07T12:53:25+00:00

    Hi xmannersx,

    Another option that you may try are the following:

    1. Manually switch the busylights on and off, press the volume up and volume down button simultaneously for 5 seconds.
    2. To deactivate the busylight function entirely, hold volume up and volume down simultaneously for 5 seconds. ( This will prevent the function to use the busylights)
    3. To reactivate the busylight function, hold the volume up and volume down simultaneously for 5 seconds.

    Please let me know if this doesn't work or if you need further assistance.

    Thank you.

    Hi leeshengfung, for some reason I had the same issue as the originator of the post (busy light on like I'm in a call that already ended). Tried touching the Answer/Hang-up button on my Plantronics Voyager Focus headset and IT WORKED! Now the Dongle and headset are in the standby mode again, I could use music from my mobile again like it was before. Thanks for this suggestion!

    Was this answer helpful?

    0 comments No comments