Additional meeting and call-related features and issues within Microsoft Teams for business
I am having the same issue with the same Jabra headset.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hi,
Would like Microsoft to respond.
When ending a scheduled teams call, the Jabra headset does not disconnect. Have to issue a test call every time to release it. This does not happen on Zoom call. Happening with many others. see other string.
Teams 1.6.00.376.
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.
I am having the same issue with the same Jabra headset.
I would love to help you. However, further testing is needed to isolate this issue. Please let me know how it goes once you had the time to test. Thank you.
Hello,
myself and my colleagues experience the same issue. We are having Jabra Evolve2 65.
Jabra Evolve2 65 firmware version: 2.7.7
Jabra link 380 firmware version: 1.16.0
Jabra Direct 6.5.31801
MS TEAMS:
You have Microsoft Teams Version 1.6.00.1381 (64-bit). It was last updated on 03.02.2023.
/testcall helps to reset the presence or application restart. I think the issue is being observed for around 1-2 weeks so one of the last updates had to "install" this "feature"...
BR
Aleksander
Jabra recommended to open a ticket with Microsoft. Thier response was:
"The problem seems to correlate with an MS Teams challenge we've been having recently. An update seems to have caused Teams to stop sending call ending signals to our headsets, resulting in "phantom calls" staying open which stop functionality to other devices.
As a temporary workaround while Microsoft works on a Teams Update, please try the following:
If this resolves the issue, use this as a short term fix while awaiting Microsoft's update. We also strongly suggest opening a ticket with Microsoft."
I fully agree - this started happening a few weeks ago to me as well. Same exact setup.