Forum Discussion
Teams call automatically gets disconnected frequently
- Sep 18, 2020
Elari160 But to permanently fix this challenge, I re-installed Windows OS & fixed this.
May be you can also give a try
I encounter similar issues; lots of disconnect and call drop on Webex. When I reboot the Jabra headset, then the call is good.
- AquayaMar 05, 2021Copper Contributor
faithlibraWhat do you mean with "reboot the headset"? Unplug and replug its USB cord ? (FYI I have this issue with a wired Jabra headset).
By the way, in my case the disconnect is always somewhere between 2min55s and 3min01s after setting up the connection - according to my Teams Call History.
The issue started to happen right after my company enabled dialing external phone numbers on Teams.
- AquayaMar 16, 2021Copper ContributorSolved in my case by exiting Skype which was still running in background next to MS Teams.
Having two applications open that both try to control the Jabra headset seems the cause of the issue.- markscheibleApr 08, 2021Copper Contributor
Aquaya - I agree with your suggestion. I switch between Webex and Teams and my Jabra headset (BT) starts connecting and disconnecting like it's jumping between applications. I've made sure Teams is shut down when using Webex and that seems to work. However, i've also had the issue with ONLY Teams open. Seems like joining a scheduled Teams meeting, and having Teams open (for chat, etc.) may also cause the two competing connections (both from Teams). Shutting Teams down and then joining the Teams meeting invite seems to work.
- JMbuzzFeb 26, 2021Copper Contributor
faithlibra Elari160 Ranjith1988
Elari160 (Sept 11 2020). 'The only solution that works for me is that I quite MS Teams before every meeting and restart.' That technically is not a solution, but it does I think point to the issue with the sync process between the app, and all of the underlying connections. If this were a bug, I suspect it'd be a bug in the OS and not the hardware, or Teams application. Perhaps the hardware driver that manages the Jambra calls to make the transfer.Ranjith1988 (Sept 11 2020) is also interesting and it too points to the fragility of the setup. His solution, re-install the OS, which to me again points to the driver and possibility some recent security updates in the OS (not specific to Jambra). The hardware headset is just the most common variable, in my opinion, to the underlying cause. It may happen with any blue tooth connected device, I suspect.