This message was deleted.

Hmm, good question. I dont think I've tried answering from my headset. I'll see if I can test that today and let you know.

Hi Daniel, if your Citrix deployment is 2203 or later, you should be able to use the composite device functionality to get the hid keys on your headset to be redirected inside a session. I've personally tested receiving a teams call, increasing/decreasing volume, mute and they all seemed to work.

The customer isn't that coordinated in using the same headset, all around 🙂 so I'd rather not gather all PIDs and so on.

Ah okay. Unfortunately, without setting the appropriate device rule, I don't think it would work with the USB redirection.

To be sure this is going to work, I would use/recommend only Citrix Ready hardware. Else, implementations and fixes for this functionality differs to much.

On the pid vid, try doing a larger class of head sets this way it will pass any head set through. Not sure if this is a possibility. https://www.usb.org/defined-class-codes Ultimately I agree with @Tommy Tee . But I do know I passed all kinds of headset by doing that. Now never tested it in teams to be honest around answering from a headset myself. My headset has a teams button. If someone calls me, I hit the button and teams picks it up. But it’s a Citrix ready device

@Daniel Madsen Have you submitted Generic USB redirection for Teams headset? Could you please share your solution?

@Dima I haven't found a solution. Other than find every PID and VID code for each headset, the customer have. Which is not something I wanna do 🙂

We have installed MS Teams on the Citrix image for a customer and configured the MS Teams optimizations. MS Teams now works well, but the customer uses a FA headset (Jabra Link 380 (dongle) and Jabra Evolve2 65). The call accept and hang up buttons on the headset do not work. Environment: DaaS Terminal Server 2019 Office 2016 VDA 2309 Server-based profiles Folder redirections Desktop, Documents Endpoint Windows 10 Workspace App 2309.1 for Windows I have now created a Citrix ticket and received a workaround that has been tested and works on one client: 1. On the Citrix DaaS policies: Create a new policy and only apply client USB device redirection and allow it 2. Configure the USB Device Rules as follows: CONNECT: vid=0B0E pid=111E split=01 intf=02 # HID Keys; DENY: vid=0B0E pid=111E split=01 intf=01 # Jabra Audio We are assuming the interface numbers (intf=02 is for HID and 01 for Audio) based on an in-house device. You can use the USBView tool to check the interface number to validate. Could you please estimate how high the risk is to implement the workaround in production and why?

If you had Citrix support to deliver a workaround, then go ahead a configure it. I can't estimate the impact.