Technical overview

This article contains this information:

  • Key features
  • Limitations
  • Considerations and recommendations
  • Bandwidth guidelines for virtualized Skype for Business
  • Citrix Customer Experience Improvement Program (CEIP)

The RealTime Optimization Pack offers clear, crisp high-definition audio/video calls with Microsoft Skype for Business in an optimized architecture. Users can seamlessly participate in audio-video or audio-only calls to and from other:

  • Skype for Business users
  • Microsoft Lync users
  • Standards-based video desktop and conference room multipoint control unit (MCU) systems
  • Standalone IP phones compatible with Skype for Business

All audio/video processing is offloaded from the Server to the end-user device or terminal, optimizing the quality of the call with minimal impact on server scalability.

Video icon

Key features

The Optimization Pack provides XenApp and XenDesktop customers the following key features:

  • Optimizes Skype for Business audio and video calling on Windows, Mac, and Linux devices by redirecting media processing to the user device. Our partner, Dell, supports Wyse ThinOS.
  • Co-developed with Microsoft, who developed and maintains the native Skype for Business client user interface. The advantage is that there is no UI hooking by the Citrix software. Users see the familiar native Skype for Business interface.
  • Simulcast video transmission (multiple concurrent video streams) to optimize video quality on conference calls and Skype Meetings.
  • Compatible with Skype for Business Server 2015, Lync Server 2013, and Skype for Business Online (Office 365).
  • Enables call initiation from the Skype for Business dialpad, dial-in bar, contacts list, Conversation window, and Outlook or other Office application.
  • Supports all Skype for Business calling and conferencing scenarios. That includes audio and video calling, hold, transfer, call forking and redirection, active speaker conferencing, and simulcast video.
  • Compatible with Skype for Business protocols for networking, media encryption (SRTP/AES), firewall traversal (STUN/TURN/ICE), and bandwidth management.
  • Forwards device location information to the Skype for Business client, to support Emergency Services (for example, E911) and Location Based Routing (LBR).
  • Supports these audio codecs: SILK, G.771, G.722, G.722.1, G.722c, and RT-Audio. We don’t support the G.722 Stereo and the Siren low bandwidth codec. This support enables voice communications over a wide range of network environments, including the public internet and mobile networks.
  • Field-proven compatibility with a broad range of audio devices, conferencing bridges, gateways, and server and network-based recording solutions. For recommended products, see Citrix Ready Marketplace.
  • Supports RT-Video, H.264 UC, H.264 Scalable Video Coding (SVC), and H.264 Advanced Video Coding (AVC). Video call rates range from 128 kb/s to 2048 kb/s. All video is encoded at up to 30 fps (depending on the webcam used) and transmitted over RTP/UDP (preferred) or TCP.
  • Uses hardware H.264 encoding on Windows devices that support AMD VCE or Intel Quick Sync, subject to compatibility. We recommend using the latest driver versions.
  • Supports most webcams, including built-in webcams on Windows devices and built-in webcams (Facetime cameras) on Mac devices.
  • Uses the hardware acceleration capabilities of UVC 1.1/1.5 H.264 hardware-encoding webcams with Windows and Linux devices (not including the Citrix Ready workspace hub).
  • Supports a wide range of video resolutions, from 320x180 to 1920x1080, at up to 30 frames per second.
  • Supports Quality of Service (QoS) by observing the audio and video port ranges configured on the Skype for Business server (see and
  • Supports Differentiated Services Code Point (DSCP) marking for media packets. For Windows, distribute the QoS policies to the endpoints. For Linux and Mac OS X, there are Optimization Pack registry settings that must be applied in the user profile on the server. For more information, see
  • Optimizes Quality-of-Experience (QoE) through adaptive jitter buffer, packet loss concealment, call rate adaptation, and other techniques.
  • If there is no RealTime Media Engine present on the user device, provides fallback to server-side media processing (Generic RealTime).
  • Improves audio and video quality over lossy connections by enabling forward error correction (FEC).
  • Call Admission Control on the Skype for Business server improves media quality in enterprise networks. It does so by tracking media bandwidth usage and denying calls that would overload the network by using too much bandwidth.
  • When enabled by administrators, all audio and video calls made with the Optimization Pack inform the Skype for Business server infrastructure about bandwidth usage. The calls follow all bandwidth policy constraints, including:
    • Limits audio and video bandwidth as required by the policies.
    • Downgrades video calls to audio only if bandwidth for video is not available. A generic message displays.
    • Reroutes the call through the internet when bandwidth on the corporate network is not available. A generic message displays.
    • Reroutes the call to voicemail when bandwidth is not available anywhere. A generic message displays.
    • Reports Call Admission Control bandwidth constraints to the Quality-of-Experience monitoring database.
  • Call Admission Control works in all network configurations supported by Microsoft. That is, multiple regions, sites, links, routes, policies, and so forth. It works for both on-premises and remote endpoints. On remote endpoints, just as with native Skype for Business clients running remotely, only internal portions of the media path are subject to Call Admission Control bandwidth policies.
  • RealTime Media Engine uses the Citrix Receiver for Windows auto-update capability and policy controls.
  • Single download, single install bundle of Citrix Receiver for Windows and RealTime Media Engine. The single install bundle is ideal for first-time users on unmanaged devices.


When you deliver the Skype for Business client in a virtualized environment, there are a few feature differences. For more information, see


Editing the registry incorrectly can cause serious problems that may require you to reinstall your operating system. Citrix cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk. Be sure to back up the registry before you edit it.

  • The dual-monitor Citrix Ready workspace hub configuration doesn’t support video overlays. Therefore it is not compatible with the HDX RealTime Media Engine for Skype for Business.
  • The Citrix Ready workspace hub doesn’t support the webcam H.264 hardware encoding feature. All video encoding is done on the Citrix Ready workspace hub, which provides up to 640x360 video resolution.
  • When using an HP T730 thin client with Windows 10 and a Logitech C925e web cam to make a video call, and then resizing the window to high definition resolution, a 30 fps video stream is sent as a 24 fps video stream.
  • If Skype for Business is running locally on your device, right-click the Skype for Business icon in the system tray and Exit the application. Interaction issues are likely when running Skype for Business locally while it is also running in the data center as a hosted application.
  • Microsoft does not support the Lync and Skype for Business basic client with the Optimization Pack. Workaround: Use the full version of Skype for Business.
  • The Optimization Pack does not support direct media connections to and from public switched telephone network (PSTN) gateways. There is an optional feature of Skype for Business, known as media bypass. For more information, see and If Skype for Business server administrators enable media bypass, PSTN calls involving Optimization Pack users automatically and transparently route media connections through the Mediation Server. This feature limitation doesn’t cause user impact. Take this limitation in to account when planning network capacity.
  • When the Skype for Business client is delivered as a published application rather than as part of a full Windows desktop, desktop sharing is not supported. If you use desktop sharing, the server desktop is shared rather that the local desktop. Application sharing can be used to share other hosted applications during a Skype for Business call. The virtualized Skype for Business client cannot share applications running locally on the user device.
  • Client-side recording is not supported. Citrix recommends evaluating third-party server/network-based recording solutions.
  • Gallery view is not supported in multiparty calls. Active speaker view is used in Skype for Business multiparty calls using the Optimization Pack.
  • Panoramic webcams that deliver a 360-degree view of the meeting room are not supported.
  • Optimized delivery (redirection of media processing to the user device) in a double-hop XenApp/XenDesktop-Receiver scenario is not supported.
  • Web proxy limitations:
    • HTTP proxy authentication is not supported. Configure proxies using white lists to allow unauthenticated access to target Skype for Business servers (for example, Office 365 servers for cloud-based deployments).
    • Web Proxy Auto-Discovery Protocol (WPAD) and dynamic proxy detection are supported by using Windows endpoints only. Configure Linux and Mac endpoints using a static HTTP proxy address.
  • On Linux terminals, the RealTime Media Engine installer disables multimedia redirection in Linux Receiver. Thus, avoiding the Optimization Pack and Linux/Unix Receiver getting into a conflict when accessing video devices. However, other unified communications applications cannot support Generic USB redirection when accessed on a Linux terminal that has RealTime Media Engine installed.
  • The date and time strings on USB telephone devices that have display capabilities are not properly localized.
  • The Plantronics Clarity P340 audio device is not supported.
  • The Optimization Pack disables the use of hardware acceleration for the Logitech C920 camera on Windows. Support is provided for the C920 as a nonencoding camera. To enable hardware compression for the Logitech C920 on Windows, do the following:
  1. Replace the Logitech driver with the stock Microsoft driver.

  2. Create a registry setting that enables hardware acceleration with the C920.

On 32-bit and 64-bit Windows:

HKEY_CURRENT_USER\Software\Citrix\HDXRTConnector\MediaEngine Name: EnableC920Compression Type: DWORD Data: 1 (enables the hardware acceleration) 0 or missing (disables hardware acceleration)

Note: Logitech does not recommend the C920 for business use cases. We recommend the more modern Logitech cameras (C930E, C925E), which are compatible with standard Microsoft drivers.

Considerations and recommendations

  • The inclusion of hardware acceleration for video increases the amount of data being sent if you deploy devices that support hardware acceleration for video. Ensure that you have sufficient bandwidth available among all endpoints or update your Skype for Business server media bandwidth policies accordingly.

  • In Fallback mode, video quality might degrade to the point of failure on virtual desktops that have a single virtual CPU. Fallback mode is when RealTime Media Engine is not available on the endpoint and audio/video processing occurs on the server.

We recommend that you change the VDA configuration to have a minimum of two CPUs for users who might need Fallback mode. For more information, see and

  • Users might hear an echo or other artifacts when using any built-in microphone and speakers on endpoints.

We recommend that you use a headset on an endpoint or a speakerphone that has hardware-based echo cancellation.

  • When attempting to make high-definition video calls from a home office, consider your user network bandwidth and ISP routing policies. If you observe pixelation of the video or problems with lip sync, adjust the Maximum Packet Size (MTU) on the NIC properties. Specify a lower value such as 900 to avoid situations where ISPs perform traffic shaping based on packet size.

  • Various scenarios (for example, combining content sharing and audio/video conferencing) might not work properly when some conversation participants run 1.x versions of the Optimization Pack.

We recommend participants using older versions of the Optimization Pack upgrade to this version of the Optimization Pack.

  • Users might see an error when making a call or joining a session when they have multiple sessions running.

We recommend running only one session.

  • Old versions of graphics card drivers might impact the stability of the Optimization Pack. H.264 hardware encoding and decoding on Intel and AMD chipsets works most reliably when using the latest versions of graphics drivers. The drivers are available from the endpoint or chipset vendors. If an unsupported driver version is detected, Optimization Pack might automatically disable these features.

Bandwidth guidelines for virtualized Skype for Business

In general, bandwidth consumption when using the HDX RealTime Optimization Pack is consistent with non-virtualized Skype for Business. The HDX RealTime Media Engine supports the audio and video codecs that Skype for Business commonly uses, and obeys the bandwidth restrictions configured on the Skype for Business server. If the network has been provisioned for Skype for Business traffic, the Optimization Pack might not require more traffic engineering. For new or growing deployments, network bandwidth, and Quality of Service provisioning, follow the Microsoft guidelines for voice and video. These guidelines apply when client endpoints are the sources and destinations of real-time media traffic.

Audio and video traffic in Optimized mode flows out-of-band from ICA. The only extra traffic generated by the Optimization Pack is from the:

  • Low bandwidth ICA virtual channel control interactions between the RealTime Connector on the VDA server and the RealTime Media Engine on the client endpoint.
  • Compressed logging data sent from the RealTime Media Engine to the RealTime Connector. This additional traffic amounts to under 25 Kbps of upstream ICA bandwidth and about 5 Kbps of ICA downstream bandwidth.

This table summarizes different types, sources, and destinations of network traffic with HDX RealTime Optimization Pack:

Network traffic type Optimized mode Fallback mode
Real-time audio and video streams sources and destinations Client endpoints VDA servers
Real-time A/V bandwidth usage Follows Microsoft policies and usage requirements Follows Microsoft policies and usage requirements
HDX audio and webcam bandwidth usage Not used in optimized mode Used in fallback mode;HDX audio and webcam bandwidth guidelines apply
Extra ICA usage by the Optimization Pack 5 kbps downstream, 25 kbps upstream None
Content sharing sources, destinations, and bandwidth usage Content sharing network streams always originate and end on VDA servers Content sharing network streams always originate and end on VDA servers

For the Microsoft bandwidth guidelines for Skype for Business, see

H.264 is the main video codec used by Skype for Business and RealTime Optimization Pack. H.264 supports a wide range of video resolution and target bandwidth values. Skype for Business bandwidth usage policies always constrain bandwidth usage for video. In specific call scenarios, actual bandwidth usage might be even lower depending on current bandwidth availability and client endpoint capabilities. For HD video resolution in peer-to-peer calls, we suggest 1 Mbps or more and for VGA resolution, 400 Kbps or more. Conference calls might require more bandwidth to support HD video (we recommend 2 Mbps).

The Optimization Pack also supports the legacy RT Video codec for interoperability scenarios with legacy versions of Microsoft unified communication software. Bandwidth usage with RT Video is similar to H.264, but video resolutions using RT Video are limited to VGA or less.

Audio codec usage depends on the call scenario. Because the Microsoft Skype for Business Audio-Video Conferencing Server doesn’t support SILK or RtAudio, these codecs are used only on point-to-point calls. Conference calls use G.722. SILK offers comparable audio quality to G.722 while consuming less bandwidth.

In addition to the codecs used by the native Skype for Business client, the HDX RealTime Media Engine offers a super-wideband codec, G.722.1C. This codec offers superior audio quality when both parties on a point-to-point call are using the Optimization Pack. This codec consumes 48 Kbps of network bandwidth. The Optimization Pack 2.4 doesn’t support the ultra-low bandwidth Siren codec, which is the predecessor to G.722.1. The Optimization Pack does support G.722.1 for interoperability with third-party systems, although Skype for Business does not support G.722.1.

The Optimization Pack automatically selects the best audio codec that all participants on the call support and fits within the available bandwidth. Typically:

  • A call between two Optimization Pack users uses the super-wideband G.722.1C codec at 48 Kbps and has good audio fidelity.
  • A conference call uses the wideband G.722 codec at 64 Kbps. That is, 159.6 Kbps with IP header, UDP, RTP, SRTP, and Forward Error Correction.
  • A call between an Optimization Pack user and a native Skype for Business client user uses the wideband SILK codec at 36 Kbps. That is, 100 Kbps with IP header, UDP, RTP, SRTP, and Forward Error Correction.
  • When an Optimization Pack user makes or receives a public switched telephone network (PSTN) call, one of the narrowband codecs is used: G.711 at 64 Kbps or narrowband RtAudio at 11.8 Kbps.

Citrix Customer Experience Improvement Program (CEIP)

The Citrix CEIP usage and analytics program is a voluntary data collection program designed to improve your product experience. After installing this version of the Optimization Pack, you can participate in the programs anonymously.

You can change your participation in the program at any time. For more information, see

CEIP is voluntary. When you opt-in, the CEIP services running in Citrix products gather anonymous configuration and usage data from your deployment, and automatically sends the data to Citrix. CEIP collects these classes of data:

  • Configuration data
  • All system and account identifiers are anonymized before being uploaded.

How your privacy is protected:

  • Citrix does not collect any personally identifiable data.
  • Random identifier is created at install time, which tracks data transfers over time.
  • Citrix does not record information such as IP addresses, server names, or domain names.
  • All data is sent using HTTPS directly to Citrix servers - no third-party data hosting services.
  • All data is secured on Citrix servers and is accessible only by authorized individuals.

CEIP Opt-out policies and the user interface (UI)

The RealTime Connector defines the following registry entries controlling CEIP metrics:

HKEY_LOCAL_MACHINE\Software\Citrix\HDXRTConnector\ DWORD DisableCEIPMetrics

If absent or set to 0, the user controls the CEIP metrics collection. If present and set to nonzero, metrics collection is disabled and the opt-out UI is hidden.

On 64-bit Windows, the RealTime Connector checks both HKEY_LOCAL_MACHINE\Software\Citrix and HKEY_LOCAL_MACHINE\Software\Wow6432Node\Citrix for this value.

HKEY_CURRENT_USER\Software\Citrix\\ DWORD OptOutOfCEIPMetrics

If absent or set to 0, the user did not opt out of CEIP metrics collection. If present and set to nonzero, the user opted out of CEIP metrics collection.

In the Settings dialog screen, the RealTime Connector adds a check box.

Send anonymous usage metrics to Citrix

The check box is hidden if the administrator disables CEIP metrics collection by setting DisableCEIPMetrics. Otherwise, it appears. The check box is checked if the OptOutOfCEIPMetrics registry value is absent or set to zero. The check box is clear if OptOutOfCEIPMetrics is present and set to nonzero. When the user changes the state of the check box, the RealTime Connector updates the registry setting and enables or disables CEIP metrics submission accordingly.