- This topic has 2 replies, 2 voices, and was last updated 2 years, 5 months ago by
.
-
Posts
-
Jabber Client version 14.0.3
Jabber Package 14.0.2.306216.3
VMware Horizon 2111.8.4.0.18957622_3
ThinOS 9.1.5
Issue 1: Our call center users are using Jabber softphone (with the jabber agent installed on the Windows 10 image) on VDI. We are continually running into an intermittent issue where the “Use my computer for calls” disconnects from CUCM. After looking into Jabber logs, it seems the Jabber ThinOS package gets “Disconnected”… ? Like the Agent (on the Windows side) isn’t seeing the corresponding Client (ThinOS JVDI package).
Issue 2: Occasionally, when using the “Device Selector”, they cannot select their headset. When they click their headset in the list, nothing changes. Again, this is kind of pointing me to the JVDI package as the culprit (because that component adds the “Device Selector” option)
Anyone experiencing this also? Any tips or things i should be looking at to dig deeper? This issue has been lingering and with the call center being so busy (we’re a health care facility), i’d love to get this one resolved.
Thanks all!
Have not had this experience but also not using Jabber to the extent you are with a call center. Are these users external going through a Netscaler gateway or internal to their VM’s with a direct brokered connection?
Have you validated with Cisco the network port requirements for Jabber if the thin clients need to connect directly out the firewall to Cisco cloud infrastructure?
I’ve engineered our Zoom and WebEx for VDI environment, all these things have network port requirements to cloud data centers of some sort and our thin clients aren’t leveraging a proxy so you may have to punch some holes in the firewall for that.
I know Jabber has similar requirements, we’re still transitioning from 12.8 to 14 on the client side but the 14.0.2 JVDI plugin for the thin client side still works for us with the 12.8 client and agent on the VM side.
If all of what I said makes sense I would also work with your network team if they can do any on-site captures and analyze the traffic to see if anything is getting dropped or blocked our out of order.
Other thoughts:
Is your Citrix environment setup to use UDP, TCP or EDT?
What version of Citrix VDA is on the VM’s; LTSR or CR?
Are these standardized peripherals for your headsets and/or webcams?
Assuming your policy is NOT allowing USB redirect for audio and video devices, that’s required for the plugins to offload audio/video to the local thin client?
Well, just realized you’re using Horizon. My questions may still apply to a degree regarding port requirements, disregard the Citrix specific questions but may be worth checking the Horizon versions as well.
sorry I’m not a VMWare guy I know Citrix better.
- You must be logged in to reply to this topic.