1

We have been trying to get multiple headsets to work with Cisco Jabber on VDI. We test them on windows and they work with the button on the headset when answering a phone call. But on a VM when a call comes in the headset will not pick the call up with the button. We have tried Jabra, Plantronics, Yealink and a couple others.

1 Spice up
2

How is the headset being used?
Is it being passed to the remote VM? or is it a local audio device only?

What form of VM? e.g. VDI what OS, what environment (horizon, citrix, MS, other)? or a terminal server (MS, xenapp) or just generic VM
What client - windows full fat, thinos, rdp, citrix etc

3

The VM is VMware Horizon and Dell Thin OS, On the thin client we have only been running the jabber client and not the JVDI Agent on the gold image of the VM. Once installing the agent the headset doesn’t get detected in Jabber. On the horizon client side the button only works with USB redirection enabled if so though there’s a delay in audio.

4

That makes sense.
If you redirect USB then the VDI OS knows abou the full functionality of the headset. But then you get the redirection delay issues.

If you are running the jabber client on Thin OS and it doesn’t work log issue with Dell and Cisco.
Does the Dell Thin OS recognize the mute button? i.e. does pressing it mute the audio on the thin os device? IF so I would expect the answer button to work. The most likely issue is that Thin Os recognizes it as a generic audio device not the specific device with additional functionality. Is the headset you are using supported on Thin OS?

5

Yes the headset works on the thin OS and does work with Jabber occasionally, well it always works with Jabber but the button doesn’t work all the time. I do have a ticket with Jabber and we haven’t fixed it yet. They said to install the Jabber Agent on the gold image after doing so it does not even detect our headsets in jabber but does detect them on the thin OS. Seems like Jabber works better without JVDI agent on the thin client.