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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2023-01-30T08:29:10+00:00

    Hello xmannersx,

    My name is Joanna, I’ll be happy to help you out today.

    Have you try the following:

    1. Unistall and install the Teams app
    2. Clear Cache
    3. Disconnect and connect the headset then try to do a test call

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

    Thank you.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-01-30T09:02:46+00:00

    Thanks Joanna,
    Yes, had tried reinstall of Teams app. And following your suggestion, cleared the %appdata\Microsoft\Teams\ cache. Disconnect/reconnected the headset and restarted Teams. However the condition is the same, 1:1 Calls clear the busylight status, however Meetings it does not.

    Was this answer helpful?

    10+ people found this answer helpful.
    0 comments
  3. Anonymous
    2023-01-30T09:24:20+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.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  4. Anonymous
    2023-01-30T09:53:25+00:00

    Thanks Joanna,

    Tried manually disabling busy light function and then later re-enabling it on the headset. The busy status restores when re-enabled, despite not being in a meeting/call. To clear, I then Make a test call via settings, and again reliably Teams clears the busylight status that way, but does not when hanging up from a meeting.

    Was this answer helpful?

    8 people found this answer helpful.
    0 comments
  5. Anonymous
    2023-01-30T09:54:47+00:00

    Hi xmannersx,

    It seems to be a bug.

    This issue needs to be further investigated by Microsoft product group. Unfortunately, as a community advisor (not Microsoft staff), I don't have access to the user's account, so it's difficult to further investigate this issue.

    I would suggest submitting a feedback to the support engineer team of Microsoft so that they can include this in future releases.

    https://feedbackportal.microsoft.com/feedback

    Thank you.

    Was this answer helpful?

    6 people found this answer helpful.
    0 comments