Known issues

Important

Editing the registry incorrectly can cause serious problems that might 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.

General known issues

  • When starting an audio point-to-point call and starting video at the same time, a Cannot start video message appears.

    Workaround: Do not start an audio point-to-point call and video at the same time. [LOP-2356]

  • In point-to-point calls using a UVC camera, or in a Meet Now, before a user starts transmitting video, the aspect ratio of the picture-in-picture video window might not display in the correct aspect ratio. On point-to-point calls, the video you’re sending might be wider and include more content than what is visible in the picture-in-picture window. In Meet Now, after each participant becomes an active speaker, the aspect ratio changes to 16:9. [LOP-2462]

  • We do not support two or more active network interfaces. For example, user1 has wired Ethernet and Wi-Fi enabled. User2 calls user 1 and connection problems occur causing the call to fail. [LOP-1822]

  • The Optimization Pack is not compatible with the Polycom RealPresence Trio 8800. If you use the Skype for Business UI to accept a call, but use the Polycom RealPresence Trio 88 to hang up the call, the call doesn’t end. [LOP-1983]

  • After the called party using an IP phone accepts a video call as audio-only, the caller cannot add a third participant to turn the call in to a conference call. Workaround: The called party can add the third participant, after which all conferencing capabilities are available. [LOP-1504]

  • If Mac OS X user changes the dock UI setting while Skype for Business is running, current and future calls don’t display local or remote video.

    Workaround: Restart Skype for Business. [LOP-1062]

  • If a caller plugs in another human interface device (HID) during an active call, the call might drop. [LOP-1377]

  • Skype for Business might crash at startup after RealTime Connector is installed.

    Workaround: Restart Skype for Business.[608171]

  • Some headset devices (for example, Polycom and Plantronics) are mistaken for speaker phone or handset devices.

    Workaround: Restart Skype for Business [605349]

  • If Citrix Receiver for Mac 12.0 is on the endpoint device and a Human Interface Device (HID) is removed after Skype for Business and RealTime Optimization Pack are running, the RealTime Media Engine might crash.

    Workaround: Upgrade your version of Citrix Receiver for Mac to a more recent version. [612448]

  • Skype for Business might crash when exiting a video conference call or when exiting from the notification area. [612444, 612115, 610894]

  • Optimization Pack, does not appear in the Citrix Receiver for Windows Support Info generated from the Advanced Preferences menu. [608200, LOP-650]

  • When a public switched telephone network (PSTN) gateway is configured to generate custom ringback tones, the Skype for Business built-in ringback tone might be heard for a short period before the gateway ringback is heard. [LOP-1243]

  • When fallback mode is set to audio only, and the users in fallback mode participate in a video conference, they might see their own states in the participant list incorrectly displayed as On Hold. Other users are not affected. [LOP-1175]

HDX RealTime Media Engine known issues

  • The RealTime Media Engine v2.0.5 causes a slideshow effect in conference video calls when interoperating with 2.1.X and above.

    Workaround: Disable H264UC codec: Add DWORD DisableH264UC in the registry:[HKEY_CURRENT_USER\Software\Citrix\HDXRTConnector\MediaEngine\CodecSettings] “DisableH264UC=dword:000000001 The codec is enabled if the value is absent or set to 0, and is disabled if the value is present and set to 1. [LC6665]

  • When a user (user2) on a Mac tries to use the RealTime Media Engine that another user (user1) installed, user2 might not receive an optimized experience.

    Workaround: On a Mac, install the RealTime Media Engine by using the actual user’s logon. [LOP-2203]

  • For Citrix Receiver for Windows versions 4.2 and earlier - Uninstalling the Citrix Receiver, uninstalls HDX Real Time Media Engine. You must reinstall HDX Real Time Media Engine after installing Receiver. For more information, see https://support.citrix.com/article/CTX200340. [484913]

  • Sometimes, when attempting to install HDX RealTime Media Engine on Windows, a message indicates that there is no available disk space. However, limited space does exist on the Z:/ drive of the terminal. This is a known issue for Microsoft installers and applies to Citrix Receiver as well.

  • During installation or un-installation, it is possible to encounter certain error conditions where the error message string is not localized. [14530, #93]

  • In Seamless mode, the following issues exist for Full Screen video:

    • Full Screen video appears in letterbox format with the Linux version of the RealTime Media Engine in Seamless mode. [13564]

    • The Full Screen Control hides behind other apps in a Seamless session in XenApp Seamless mode. [10731]

Citrix Ready workspace hub (formerly known as HDX Ready Pi) issues

  • When you use the RealTime Media Engine on the Citrix Ready workspace hub, the buttons on audio devices that have Human Interface Design (HID) functions do not work. You can use these devices as plain audio devices. [LOP-1634]

  • Video capture issues sometimes occur when using a Logitech 310 or Logitech 9000 camera and the Citrix Ready workspace hub. The Preview option might not work, call initialization might be slow, calls placed on hold might not resume, or the camera fails during a call. Workaround: If the preview tries to display but fails, select Start my video. [LOP-2268, LOP-2339]

  • Connecting a USB audio device to the Citrix Ready workspace hub while Skype for Business is running might cause a loss of the wired Ethernet connection. For optimal performance, we recommend that you connect your USB video camera and audio device to the Citrix Ready workspace hub as part of your setup procedure. If you lose the wired Ethernet connection because of disconnecting or reconnecting a USB device, restart the Citrix Ready workspace hub. [LOP-2523]

  • USB devices on the Citrix Ready workspace hub might lock up when Skype for Business starts or during a MeetNow call. Workaround: Restart the Citrix Ready workspace hub. [LOP-2527]

  • Acoustic echo cancellation might not work. Using the Citrix Ready workspace hub with a microphone and speakers can generate echo that is heard by the other parties to the call. [LOP-2538]

  • A user on the Citrix Ready workspace hub and Stratodesk who makes an outgoing audio call might not hear any audio. That includes a ring back tone and voice. Workaround: Open the Stratodesk system configuration Audio tab and set Standard audio device to Analog. [LOP-2579]

  • On the Citrix Ready workspace hub and a Stratodesk image using XenDesktop 7.6, the Picture in Picture and incoming video windows might appear as blue screens. Workaround: Disable HDX 3D Pro H.264 acceleration. [LOP-2588]

  • Sending or receiving high resolution video on the Citrix Ready workspace hub might cause audio distortion. Workaround: During video calls with Citrix Ready workspace hub devices, do not enlarge the video window.[LOP-2613]

Third party issues

  • Using a Logitech C930e camera that has a pre-8.0.875 firmware version might cause the picture-in-picture to freeze on either side of the call. Workaround: Upgrade your firmware to a minimum of 8.0.875. For more information, see https://support.logitech.com/en_us/product/webcam-c930e-business. [LOP-2571]

  • The Windows 10 Anniversary Update (August 2016) has issues with web cameras and H.264. These issues might cause unnecessary bitrate adaption problems in RealTime Optimization Pack to RealTime Optimization Pack video calls. The problem is constant video resolution changes on your Windows 10 endpoints. Workaround: Add this registry key to the Windows 10 endpoint. [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows Media Foundation\Platform] “EnableFrameServerMode”=dword:00000000 [LOP-1985]

  • If Microsoft .NET Framework 4.6 is installed using the default configuration, RealTime Connector on 64-bit Windows might crash or become unstable. For possible workarounds, see RyuJIT settings cause managed applications to crash after you install Microsoft .NET Framework 4.6. [LOP-1278]

  • There might be problem dialing dual tone multi frequency (DTMF) digits using a Jabra Pro 9465 device on a Linux client. Workaround: Use the RealTime Optimization Pack interface to dial the DTMF digits. [547234]

  • Citrix RealTime Optimization Pack does not support the Plantronics Clarity P340 audio device but does support the P340-M (Skype for Business qualified device). [597048, 603639, 608218]

  • On Mac OS X, Citrix RealTime Optimization Pack does not support Hewlett-Packard 4310, Hewlett-Packard 2300, and Microsoft LifeCam Studio webcams for point to point calls. [LOP-2371]

  • Linux might mistake some audio devices containing buttons for a Human Interface Device (mouse) instead of an audio device. When a user presses a button, Linux interprets it as a mouse button press and prevents the regular mouse from working correctly until the call ends. Workaround: Configure the Linux X11 graphics subsystem to ignore the devices as sources of user input. Create or change a .conf file in the /usr/share/X11/xorg.conf.d directory with the following sections (for example, Jabra, Plantronics, or Sennheiser). [21088]

Section “InputClass”

Identifier “Jabra”

MatchVendor “Jabra”

Option “Ignore” “True”

EndSection

Section “InputClass”

Identifier “Plantronics”

MatchVendor “Plantronics”

Option “Ignore” “true”

EndSection

Section “InputClass”

Identifier “Sennheiser”

MatchVendor “Sennheiser|1395”

Option “Ignore” “true”

EndSection

  • The microphone volume level of some Linux clients is low.

Workaround: Increase the microphone level using the Linux system volume control.

  • The microphone volume level of the Polycom CX100 speakerphone is low even at its full level when used with the HP Thin Pro client. Workaround: Change the registry key that comes with the HP Thin Pro by using the regeditor program on the client. You can run the program as root or from the Registry Editor component of the Profile editor.

These settings limit the range of available settings on the input volume slider. The RecordScale default value of 100 limits it to 25% of its maximum value for the microphone jack. Setting RecordScale to the maximum value of 400 allows the slider access to the entire scale. [604219]

root>Audio>

Value name: RecordScale Value data: 400 (Default is 100)

Value name: RecordScaleAuto - Value data: 0 (Default is 1- sets to 100)

1 Sets RecordScale value based on hardware type.

2 Does not set RecordScale value based on hardware type.

For playback, these controls work the same way as the input volume controls.

root>

Value name: OutputScale Value data: 400 (Default is 100)

Value name: OutputScaleAuto Value data: 0 (Default is 1)

  • You might encounter errors with Skype (not Skype for Business) on iOS 9.2. Workaround: Upgrade to iOS 9.3.2 [LOP-1313]

  • If you have more than one camera connected to an endpoint and you want to use the second camera for videos or video previews, open Tools > Video Device Settings and select the camera and click OK. [LOP-1397]

  • If Skype (not Skype for Business) fails to connect video from the RealTime Optimization Pack in a video call, you might see a black screen or a still video from the RealTime Optimization Pack user. [LOP-1295]