Webex App VDI Solution and Phone Services to Expressway

[shockocisco]

I'm looking at evaluating Webex App VDI with Citrix Virtual Apps and desktops 2203 LTSR CU2 and Citrix Workspace App 2203 LTSR. I have setup the optimization (Webex plugin for VDI at client and Webex App in Citrix session host) so that audio/video is optimized to the client endpoint. This works great for Web calls and meetings but we also require phone services to our Expressway at our edge for phone number calling. Is this supported with the VDI solution i.e. can it be optimised to send the audio from the endpoint via the Citrix workspace App Webex VDI plugin?

[asmvar@1234 · Accepted solution]

Hi there, 

It is possible to implement it but it is little bit complexed. Cisco has proper guidelines about preparation and implementation. 

https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/vdi/wbx-vdi-deployment-guide/wbx-teams-vdi-deployment_chapter_01.html

Check the part for Mobile and Remote Access (MRA) requirements

 

[thomas-buchholz]

Hi asmvar@1234 

i went through the full guide, and from my point of view we configured anything from that document.

But we are facing a strange issue:

User logs in from home PC to a Citrix session, Webex VDI plugin is installed on his PC.

When he opens Webex App, health checker shows Virtual VDI channel is ok.

CSF Device in CUCM shows registered, and i can do calls, but without Audio.

Network Traces show that CUCM negotiate Media directly between private IP of Home PC and the endpoint , which is of course not possible, because private IP is external.

in CUCM,  CSF Real Time Device Status shows:

IPv4 Address:  private IP from Home PC

Hosted Virtual Desktop Address: IP from Citrix HVD 

Usual MRA registration and Calls work fine, means Webex App on Home PC outside of Citrix Session registers through Expressway-E.

It looks like the Home PC doesnt send the Media via expressway. Also Citrix HVD  doesn't seems to send the HTTPS and SIP 5061 to Port 8443 on Expressway-E  external interface, but to CUCM.

Wireshark traces home Home PC  are showing request to DNS for _collab-edge.tls.domain, but no DNS Lookup or connection for the Expressway-E FQDN from this SRV.

Any idea what can be wrong? 

Thanks,

Thomas

----------------

From the guide:

Step 5- After receiving and caching the Expressway-E FQDN, the Webex App (HVD) then performs a DNS A record lookup for the Expressway-E FQDN. For a single NIC deployment, this step retrieves the Expressway-E's IP address (internal IP with split DNS or external IP without split DNS), which is used for Edge configuration and SSO authentication over port 8443.

Step 6- After the Edge details are retrieved, the Webex App (HVD) establishes HTTPS connections to the Expressway-E IP for UDS and TFTP requests. Through this process, the Webex App (HVD) authenticates and retrieves configuration details, such as Soft-phone Device Config, Application Dial Rules, and Directory Lookup Dial Rules.

Step 7- The Webex VDI plugin resolves the Expressway-E external IP and then sends to the Webex App (HVD). Through the device information that is retrieved in the previous step, Webex App begins the CSF device (Windows desktop) registration through the Expressway-E external interface.