Teams will not fully "hang up" and release my Bluetooth Headset

Anonymous
2023-02-04T03:38:27+00:00

With issue for a few years, I have been using a Jabra 65 Evolve headset with Microsoft Teams on the same Windows 10 Laptop. In the last few weeks, I have had problems where after exiting a Teams meeting, the Teams software is not fully hanging up. Upon exiting via the the "Leave" button in the Teams Window or Hanging up with a long-press of the Jabra Headset button, the meeting and the meeting window will close and appear to have fully ended, but my headset is still "connected" appearing to be part of a meeting. While in this connected state, the headset will not connect to another Bluetooth device (like my mobile phone). It will stay in this state indefinitely and will only respond/connect if I enter another Teams meeting.

The only fix I have found is when I fully exit Teams. Once I do that, the headset is fully released/hung up and connects back to my Mobile phone. Only after exiting Teams and then reloading Teams does the headset work properly and pair back up with the headset while also being paired with my mobile phone.

I believe this is a Teams problem only because anything I try with the Jabra headset or software does not change the state of the headset. The headset still appears connected even if I unplug the Jabra Link 370 dongle and then plug it back in. Again, only after I fully exit/shutdown Teams and then restart Teams is the headset for use like it had been for the years before. My ticket to Jabra states this is a Microsoft Teams problem (of course).

Laptop LENOVO ThinkPad T15 Gen 1

Windows Version 10.0.19044 Build 19044

Microsoft Teams Version 1.6.00.1381 (64-bit)

Jabra Evolve Headset Firmware 2.97.0

Jabra Link 370 Firmware 1.87.0

Jabra Direct Software 6.5.31801

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

48 answers

Sort by: Most helpful
  1. Anonymous
    2023-04-20T15:54:18+00:00

    I assume for many that this problem is now resolved. I had a fix with a new version install a few weeks ago. I see now that I am running 1.6.00.6754 (64-bit) which was last updated on 3/24/23 and the problem is gone with this version.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-04-20T13:58:13+00:00

    I'm having the same issue here with Apple AirPods Pro 2. Another quick way around this issue is to go into Windows Bluetooth settings and disconnect then reconnect the headphones. At least this way, I don't have to terminate and reload teams. But the problem still persists as of today, 4/20/2023.

    I'm on Teams version 1.6.00.6754 (64-bit) updated on 3/30/2023.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-02-23T02:06:25+00:00

    Thanks, but been there and done that. FYI... this is a confirmed Microsoft problem that Jabra and Microsoft agree on. I know my software updates as needed and it's up to date. I wish it would have been the Jabra software, that is much easier to get support for and update.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-02-23T00:38:23+00:00

    Try downloading Jabra Direct and update the firmware. https://www.jabra.com/software-and-services/jabra-direct

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2023-02-22T20:33:58+00:00

    Crazy thing is that my Teams system has been hanging up just fine today even though I am still using the same version of Teams (1.6.00.1381 64bit) and Jabra. The only thing that changed is now I am on Windows 11 instead of 10 (now on Windows Version 10.0.22000 Build 22000). But I have been on Windows 11 for just over a week now. So not sure what happened to make things start working today. I restarted Teams just to make sure I didn't get an update/new version and Teams tells me I am on the latest version.

    Either way, I am happy as can be that this problem has gone away. I just hope it stays away.

    Was this answer helpful?

    0 comments No comments