My Jabra evolve 75 get stuck in call mode after Teams call is ended.

Anonymous
2023-01-31T11:59:26+00:00

It seems Teams cannot end the call on my Jabra Evolve 75 headset appropriately. The Teams call is ended but the headset is left as if still in a call in mono mode.

Microsoft Teams | Microsoft Teams for business | Meetings and calls | Audio and video

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
Answer accepted by question author
Alvaro A- 1,670 Reputation points Independent Advisor
2023-01-31T12:35:23+00:00

Hi Flemming,

I'm sorry to hear that you're have issues with your Jabra whenever you end calls. First, let's make sure that the user's Teams app cache files are not corrupted. Please follow the steps below according to your operating system.

Clear Teams cache in Windows

If Teams is still running, right-click the Teams icon in the taskbar, and then select Quit.

Open the Run dialog box by pressing the Windows logo key +R.

In the Run dialog box, enter %appdata%\Microsoft\Teams, and then select OK.

Delete all files and folders in the %appdata%\Microsoft\Teams directory.

Restart Teams.

Clear Teams cache in macOS

If Teams is still running, right-click the Teams icon in the dock, and then select Quit, or press Command (⌘)-Q.

In the Finder, open the /Applications/Utilities folder, and then double-click Terminal.

Enter the following command, and then press Return:

rm -r ~/Library/Application\ Support/Microsoft/Teams

Restart Teams.

This usually fixes these types of issues but if not, you'll have to make sure that the proper drivers for your Jabra 75 are installed in your PC. You may download it from here.

https://www.apac.jabra.com/supportpages/jabra-e...

Was this answer helpful?

0 comments

69 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2023-10-02T12:14:41+00:00

    Hi Jakob

    We have Jabra Evolve2 65 and are experiencing this exact issue again. Started last week.

    We also experienced the issue back in February 2023, but it was solved some weeks later.

    Added: temporary fix is to initiate the Teams test call in Teams settings > Devices. When you then hang up, it "solves" the issue. This then has to be done after each call/meeting.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2023-09-29T11:56:38+00:00

    This problem is not solely related to Jabra!

    I do have Poly devices in my hands and got stuck in a call as well.

    Jabra Direct is not related into fixing the issues. Call control is mainly happening embedded through being a certified device for Teams. Therefore Teams has and takes control over the device.

    The headset software in this context act only for device settings. Plugins for call control are served for other UC applications where there is no embedded call control implemented. Zoom and Webex for example are one of those.

    You can as well uninstall those apps and you will still face the issues.

    In short: Teams has the same issue like back in February. If its the same, remains to be clarified. Its obvious though that after completing a call the command on the USB HID is not executed to terminate the communication on the USB device.

    Above written represents my personal view/opinion and does not rely on examined protocols or logs.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2023-09-29T09:13:23+00:00

    Hi Jakob,

    for me the problem went away after both MS Teams (1.6.00.24078) and the Jabra software (6.10.25001) installed an update.

    unfortunately the issue appeared again. need to report as not solved.

    BR

    Thomas

    Was this answer helpful?

    0 comments
  4. Anonymous
    2023-09-29T08:33:50+00:00

    Hello Jakob,

    yes. Unfortunately it seems the failure occours again and reaches more users as backend or client updates happen in waves. If its due the same bug, which was around in February, is uncertain but its the same outcome right now.

    Back in February the fix was implemented in the backend and no update on the client itself was necessary. So your version of the client might not be even relevant to check for.

    George

    Was this answer helpful?

    0 comments