Hi there, I'm using the Jabra Evolve 75 headset which supports dual Bluetooth®-Connectivity with 2 devices (PC/Smartphone) for parallel (either/or) use of softphone (Jabber) and audio (Spotify). The headset works fine with Jabber/Webex via its own USB/Bluetooth dongle (Jabra Link 370). Also the headset connects directly via Bluetooth to the Smartphone, but only as long as the Cisco apps on the PC are not "using" the Jabra Link 370).
Scenario: PC via Jabra Link 370 and Smartphone in parallel connected to my Jabra Evolve 75 => message from the headphone: "2 devices connected". Jabra Link 370 dongle displays "blue light" (= bluetooth connection on). No Cisco apps running on PC. I am listening to Spotify on the Smartphone but as soon as I start Cisco Jabber, I get the message in my headphone "muted" and the red LED on Jabra Link 370 goes on.
When I unplug the Jabra Link 370 dongle from the PC, I get the obvious "PC disconnected" message in my Jabra Evolve 75 headset and the music from Spotify on the Smartphone continues to be heard in the headphone.
Why does the Cisco Apps set the Jabra Headset/Jabra Link 370 dongle to mute, although no rnning coversation is ongoing with them? And even more important: how to solve this problem.
When I had the Headset new, I could use the duel bluetooth connectivity (Jabber on PC / Sportify on Smartphone) perfectly. About 8 weeks ago, there might have been an update to the Cisco Apps and from that moment on, I always have to unpulg/plug the Jabra Link dongle to listen to Spotify on the Smartphone or use Jabber/Webex.
Thanks in advance for any hint on how to go back to original functionality.
I had contacted Jabra support already and they replied: " ... it seems that the Jabber client keeps your headset/dongle busy, even when no activity/call is in place, so it seems to be a problem of the Jabber client and not the headset. Normally the Cisco Softwares shall free the connection when not in use. Cisco Webex had such known problems in mid 2020, but in combination with Jabber, we are not aware of them. Version 40.8 (I am using 40.11.6.15) shall have fixed that problem at least partially, when only Webex is used. When Webex and Jabber are both used, it might still occur." => as it does in my scenario.
Greetings and happy x-mas and stay healthy.
Eric
