Share via

Jabra Evolve 65 TE / Evolve2 65 disconnect when answering a Teams or phone call via MS Teams

Schmidlin, Pascal 20 Reputation points
2026-04-29T14:20:01.28+00:00

Hi

A few days ago, we've encountered the issue that our Jabra Evolve 65 TE linked with a Jabra Link 390 disconnect, as soon as you pick up a call or want to make one via MS Teams. Happens with both - Teams or phone calls.
Firmware of Jabara Evolve 65 TE & Jabra Link is the latest as of today. Teams version is 26093.415.4620.1935 (2026/04/29).

We encounter the same issue with Jabra Evolve2 65 headsets.

I've already deactivated power saving for all USB Hubs of my device (HP Elitebook G8 840 running Windows 11 H25H2) and deleting all Jabra Link 390 entries in the device manager (even the inactive ones). Unfortunately, this won't solve the issue.

As we have not updated the Jabra Direct software as well as the Jabra FW it seems like a Teams issue.

Has anyone else encountered this issue and found a work around or solution?

Kind regards,
Pascal

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

Answer accepted by question author

  1. Emily T 485 Reputation points Microsoft External Staff Moderator
    2026-04-29T18:39:20.5166667+00:00

    Hi @Schmidlin, Pascal,

    Based on the symptoms you see (the device briefly appearing as "2‑Jabra‑Link‑390" and audio being routed to the Realtek speakers), this usually indicates that Windows is momentarily detecting the dongle as a new audio device. When that happens, Microsoft Teams may quickly switch between available audio endpoints, which explains the short audio drop or device hopping during call setup.

    Below are a few suggestions you may want to try, in sequence:

    1/ Double‑check the certified headset and dongle combination:

    Microsoft’s Teams Device Certification program ensures that only tested and approved combinations are labeled Certified for Microsoft Teams.

    Since Jabra Evolve / Evolve2 headsets with the Link 390 (MS variant) are certified, it’s worth confirming that:

    • You are using the Microsoft‑certified Link 390, not a UC variant
    • Audio is actually routed through the dongle, not via native Bluetooth

    You may find the following pages useful for reference:

    2/ Explicitly select the Jabra device in Teams:

    In Teams > Settings > Devices, manually set:

    • Speaker: Jabra Link 390
    • Microphone: Jabra Link 390

    Avoid using "Default", as Teams may temporarily attach itself to whichever device Windows presents during the re‑enumeration window.

    3/ Set the headset as both default devices in Windows:

    In the Windows Sound Control Panel, make sure the Jabra headset is set as:

    • Default Device
    • Default Communication Device

    This often improves the handoff between Windows and Teams and prevents unexpected routing changes.

    4/ Clear or reset the (New) Teams client cache:

    Microsoft recommends clearing the Teams client cache, or resetting the New Teams app, when unusual device detection or routing behavior appears after an update.

    This can often resolve audio states that become “stuck.”

    You can follow the steps here: Clear the Teams client cache.

    5/ Verify Jabra Direct softphone integration settings:

    If multiple softphones are installed, open Jabra Direct and confirm:

    • Settings > Softphone Integration
    • Preferred softphone is set to Microsoft Teams

    This helps ensure consistent call control and audio routing.

     User's image

    6/ Reset and re‑pair the Link 390 (firmware up to date):

    If the dongle continues to re‑enumerate, performing a full reset and re‑pair of the Link 390 can often eliminate duplicate audio endpoints such as "2‑Jabra‑Link‑390".

    7/ Contact Microsoft Support:

    If the problem continues after trying the steps above, the most effective next step is to engage Microsoft Support. They can review your tenant from the backend using tools that aren’t available client‑side.

    Please have your Microsoft 365 Global Administrator submit a support request through the Admin Center (Help & Support section). 

    For detailed instructions on how to get support, please refer to Get support - Microsoft 365 admin.     

    If you’re not a Global Admin, you’ll need to coordinate with the appropriate person in your organization to proceed.

    Note: If you’re an end-user, please coordinate with your Office 365 Global Administrator to handle these steps. If you are unsure who your Global Admin is, you may refer to this guide: How do I find my Microsoft 365 admin?

    I hope the information helps. Please don't hesitate to reach out again if you have any update or need further assistance.

    Wishing you all the best.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

     

    1 person found this answer helpful.

2 additional 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. Q&A Assist
    2026-04-29T14:20:37.4666667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    The described behavior is consistent with issues that can occur when using non‑certified or partially compatible audio devices with Microsoft Teams.

    Teams guidance highlights that:

    • Calls or meetings can drop or disconnect when using non‑certified devices, including when clicking a call notification or resuming a call from hold.
    • For the best experience and to avoid dropped or failed calls, officially Teams‑certified devices should be used.
    • Older or non‑certified variants of devices, even from well‑known vendors, may not work as expected with Teams.
    • Vendor companion software (such as Jabra Direct) can sometimes interfere with device button functionality and call handling in Teams; closing such third‑party software is recommended as a first troubleshooting step.

    Given the steps already taken (USB power‑saving disabled, device entries removed and re‑added, firmware current), the next practical options are:

    1. Verify that the exact headset and dongle models in use are the Teams‑certified variants (not similarly named non‑certified models). If they are not, test with a Teams‑certified model.
    2. Temporarily close or uninstall Jabra Direct or other vendor/third‑party calling software and test again, as these can interfere with Teams’ HID control.
    3. Test with another Teams‑certified audio device (for example, a different certified headset or speakerphone) to confirm that the issue is limited to the current devices.
    4. Ensure Teams is fully up to date and restart the Teams client after any changes.

    If the problem persists only with these Jabra models and not with other Teams‑certified devices, escalation to the device vendor and/or Microsoft support is appropriate, as this would indicate a compatibility or regression issue rather than a general Teams configuration problem.


    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.