Servers (Hosted Virtual Desktop (HVD), where the Webex app is Make sure your VDI environment meets the requirements for the supported Hosted virtual desktop and thin client requirements Step, Webex App begins the CSF device (Windows desktop) registration through the Through the device information that is retrieved in the previous The Webex VDI plugin resolves the Expressway-E external IP and then sends to Soft-phone Device Config, Application Dial Rules, and Directory Lookup Dial Through this process, the Webex App (HVD) authenticates and retrieves configuration details, such as Opposite of what's configured for the external interface.Īfter the Edge details are retrieved, the Webex App (HVD) establishes HTTPS connections to the Expressway-E IP for UDS and In this case, the internal interface is the If Expressway-E is set up in a dual NIC deployment, both interfaces can (internal IP with split DNS or external IP without split DNS), which is usedįor Edge configuration and SSO authentication over port 8443. ForĪ single NIC deployment, this step retrieves the Expressway-E's IP address Once service discovery is complete, Webex App VDI plugin sends the Expressway-E FQDN to the Webex App client.Īfter receiving and caching the Expressway-E FQDN, the Webex App (HVD) then performs a DNS A record lookup for the Expressway-E FQDN. Plugin machine is connecting from an external network, therefore needing toĬonnect over MRA. In this scenario, the Webex App VDI plugin resolves the _collab-edge DNS SRV record because the VDI That was sent to it from the Webex App client. The Webex App VDI plugin does this by referencing the voice service domain information Next, the Webex App VDI plugin performs service discovery. Webex App client sends the voice service domain information to the Webex App VDI plugin. The Webex App client and Webex App VDI plugin then go set up all the control streams that are used toĮxchange data over the virtual channel. (The internal service discovery includes the UDSĭNS SRV lookup, Unified CM authentication, home cluster lookup, and If Unified CM is enabled, the Webex App starts the teamshvdagent.exe process and begins HVD (virtual machine) hosted on the Hypervisor.Īfter a user launches the Webex App on the HVD, Webex determines if it is in a virtual environment and if Once selected, a virtualĬhannel is set up between the user's thin client (physical machine) and the Workspace App or VMware Horizon Client),connect to the connection broker,Īnd then select an HVD or virtual application. To start a session, users first launch their virtual broker-client (Citrix Unlike VDI over MRA, on-premises deployments don't route traffic through the DMZ Protocol sessions for Webex VDI with Unified CM over MRAĪlthough the diagram depicts Webex App VDI over MRA, the flow is the same as an on-premises VDI deployment. This diagram shows the expected protocol sessions that are set up during normal Webex App use when deployed with Unified CM calling over Mobile and Remote Access (MRA).įigure 1. The Webex App plugin and agent use this virtual channel to communicate. When a user launches a virtual broker-client (Citrix Workspace app or VMWare HorizonĬlient), the vendor's software initiates a virtual channel. On a thin client while the app is installed on the HVD. The Webex App VDI architecture consists of two primary components: the Webex App for VDI and the Webex VDI plugin for the thin client. Mobile and Remote Access (MRA) requirements.Supported realtime media workflows for calling and meetings.Hosted virtual desktop and thin client requirements.Prepare your environment for Webex App for VDI
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |