Forum Discussion
Teams call controls on jabra headset not working
I found a solution for my Jabra Speak 510 where the controls and LEDs did not work for teams on USB - Bluetooth worked.
Change the Driver to "Jabra SPEAK 510 (Sound Research)" to "Jabra SPEAK 510 USB (Sound Research)" by selecting available drivers.
No everything is fine again. Seems to be that Windows selected the wrong driver after updating to 20H2...
Jabra support is saying that the call control buttons (answer, hangup, etc) will only work if you have teams enabled as a full PBX (to allow out bound calling to external numbers, etc) Is anyone running teams just for meetings and teams-teams calls and able to get the call control buttons to work? Would be nice to be able to hit the "hang up" button to be able to end meetings without having to go to the teams app on the pc.
That's a cop out.. they told me same thing. To the extent of call control, it doesn't matter for teams to answer an incoming call or hang up an active one. In one environment, it worked without PSTN.
However, one of my clients does have full PSTN service (phone system) and it's not working there either..
This is what Jabra support reported to me
"The omission of dialpad implies HID command string coding, which dictates remote call control; ringtone to headset with answer/end from headset equipment is not in part or fully accessible in the Teams client. What signal the Jabra is being presented that is causing it's awareness would require ID by MS. "
We're on teams 1.3.00.19173
Windows 10 1909 (18363.900)
Jabra Direct 4.0.8560
Ok, but it worked a few weeks ago is the thing.
I tested today again. I uninstalled teams, wiped out all app data folders, etc., (including machine wide teams installer) then reinstalled just teams client which was 1.3.00.15561. I tested Jabra 9470 and logitech BCC950 from test account using test call from my clients tenant that was PSTN enabled, controls seemed to work (teams native mode). I tried from my tenant with my user account, NO PSTN, teams native mode... controls seemed to work. I tried from another tenant in island mode, controls DIDN'T work. I upgraded teams client to 1.3.00.19173 by forcing update in teams client, didn't impact any above results.
I have client testing again now. Current hypothesis is island mode isn't supported at all now (which, I still say there is a problem, as they did work with that tenant at least a few mos back). And, in native teams tenant, uninstalling teams client and teams-wide installer, cleaning up all traces of data directories, and reinstalling, may fix it.
I think MS just has lost all insights into how the code works so they just point fingers wherever they can. Look at Windows QC as a reference point...
I'm all for 'move fast and break things' not 'move fast, break things, gaslight customers by claiming they never worked, blame customer, ignore issue'...
My Jabra 510 worked beautifully for a good 5 months and then it went no controls. What is happening with Teams?
