This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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)
Additional meeting and call-related features and issues within Microsoft Teams for business
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.
Confirmed the MS bug number is # 2876578. This issue affects multiple manufacturers. My org works with MS on alliance projects.
Until the patch is rolled out, here is a more practical workaround...go to the three dots to the left of your picture, click on them, then select settings, then devices, then select make a test call. As soon as it starts "ringing", click leave. The headset disconnects from the call (at least for me) at that point. Probably a little quicker than quitting Teams altogether.
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.
Microsoft Premier Support confirmed: The fix for the issue is scheduled to go by end of February.
I am also having the same issue and it started in the last couple of weeks. I have tried all the same suggestions with no luck. I am using a Poly Voyager Focus 2 (Teams Certified) for my headset. I did notice that if I wait for the meeting to end and then end call on the headset before putting it back in the cradle it won't show busy. I think it has to with Teams since quitting Teams or making a Teams Call and Ending it will also reset the headset busy indicator.
Will be interested to hear if someone finds a solution or Microsoft acknowledges it as an issue.