Configuring Zoom VDI to support WebRTC redirection for the Zoom Web App
WebRTC (Web Real-Time Communication) redirection optimizes performance for real-time communication applications within Virtual Desktop Infrastructure (VDI) environments by offloading processing from the virtual desktop to the client endpoint. This feature improves the user experience for Zoom Phone and Zoom Contact Center in the web, as well as the Zoom Contact Center CTI Connector in VDI environments by reducing CPU usage, optimizing network traffic, and providing smoother audio with reduced latency.
Note: VDI WebRTC redirection is currently only available for voice channels.
Requirements for configuring VDI to support WebRTC redirection for the Zoom Web App
General requirements
- WebRTC redirection feature enabled for your Zoom account
Citrix Requirements
- Citrix Virtual Apps and Desktops with Virtual Delivery Agent (VDA) 2407 or later
- Minimum supported Citrix Workspace app version:
- For Windows: 2409 or later
- For Linux: 2411 or later
- For macOS: 2411 or later
- For ChromeOS/HTML 2503 or the latest release
- Supported Browsers: Defined by the ProcessWhitelist registry key
Omnissa Horizon Requirements
-
- Horizon Agent 2503 or later
- Horizon Client:
- For Windows: 2503 or later
- For Linux: 2503 or later
- Chrome or Microsoft Edge browser installed on the virtual desktop
- Browser extension installed on the virtual desktop
How to configure Citrix Virtual Apps and Desktops
Enabling WebRTC redirection in a Citrix environment involves configuring policies and ensuring the correct components are installed.
Configure the virtual desktop environment
- On the virtual machine, open the Windows Registry Editor.
- Navigate to HKLM\SOFTWARE\Software\WOW6432Node\Citrix\WebSocketService.
- Create or modify the following registry entry:
- Value: ProcessWhitelist
- Type: REG_MULTI_SZ
- Data: "chrome.exe","msedge.exe"
- Reboot the virtual machine for the changes to take effect.
For more information, see Citrix's setup documentation.
How to configure Omnissa Horizon
Follow Omnissa’s support article for
full setup instructions.
Configuring the thin client
On the endpoint device, install Horizon Client for Windows 2503 or later. While the Horizon WebRTC Redirection option is installed and enabled by default, users can configure this from the server connection Settings menu.
Configuring the virtual desktop
Ensure the virtual desktop has Horizon Agent 2503 or later installed.
Configuring Group Policy settings
- Download the GPO Bundle from Omnissa following their setup instructions.
- Configure the following policies:
- Set Enable Media Optimization for web applications policy to Enabled
- Set the policies for the Edge and/or Chrome browsers:
- To support Chrome, set Enable Chrome Browser for Horizon WebRTC Redirection SDK Web App Support policy to Enabled
- To support Edge, set Enable Chromium Edge Browser for Horizon WebRTC Redirection SDK Web App Support policy to Enabled
- Set Enable URL list for Horizon WebRTC Redirection SDK Web App Support policy and add the URL:
https://*.zoom.us/*
- Sign out from the agent and sign back in for the policy changes to take effect.
Install the browser extension on the Virtual Machine
Users will need to install the Chrome extension in their Virtual desktop to support WebRTC redirection on the virtual desktop, or force install the extension using the Policy for Google Chrome, or Microsoft Edge on the virtual machine side using the policy ExtensionInstallForcelist, or follow these instructions for setting policy through GPO Editor - Chrome's policy key is below.
Key: *\Software\Policies\Google\Chrome\ExtensionInstallForcelist
Type: REG_SZ
Value: 1 = "emildoafpcgihdmhphelfhghioccllfi"
How to test and troubleshoot
After configuring WebRTC redirection, test the functionality to ensure it's working correctly.
- Connect to your virtual desktop from the VDI client.
- Open a web browser and access Zoom Contact Center either directly through the web or through Salesforce integration.
- Join a call to test the audio functionality.
- Open another browser tab and visit chrome://webrtc-internals.
- Confirm that no RTCPeerConnection has been created or connected.
This indicates that WebRTC redirection is working properly and the processing has been offloaded to the client endpoint.
Note: If you see RTCPeerConnection entries in the WebRTC internals page, WebRTC redirection may not be configured correctly. Review your configuration settings and ensure all requirements are met.