About this release
What's new
What's new in 2.9 LTSR
Improved user audio experience during conversation pauses:
When speakers pause during calls, the call participants hear comfort noise instead of silence. This enhancement avoids call participants wondering if the call is still connected.
Quality of Experience statistics:
Added more video parameters in the Quality of Experience statistics reports.
TraceRoute information for Quality of Experience reports:
The HDX RealTime Optimization Pack now collects routing information from calls. This information is useful when troubleshooting call performance issues. TraceRoute is not supported on Android. For more information about the Microsoft TraceRoute table, see TraceRoute table.
Fixed issues
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
-
If macOS 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.
-
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 into a conference call.
-
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.
-
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.
-
When a call is started on a Chrome OS device using a webcam microphone and a Polycom CX100 speaker or a built-in speakerphone/microphone, echo cancellation might not work. The remote participant in the call might hear their own voice at a low volume. Background sounds from the originator can also be heard.
-
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.
HDX RealTime Media Engine known issues
-
In Seamless mode, the following issues exist for the Full Screen video:
-
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 issue is a known issue for Microsoft installers and applies to Citrix Receiver as well.
Third party issues
-
Workaround: Upgrade to iOS 9.3.2
-
Because of changes to the privacy policies in Microsoft Windows, audio and video calls might fail in fallback mode on VDAs. For more information, see Windows 10 camera, microphone, and privacy.Workaround: Enable access to the microphone.
-
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 the 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).Section "InputClass"Identifier "Jabra"MatchVendor "Jabra"Option "Ignore" "True"EndSectionSection "InputClass"Identifier "Plantronics"MatchVendor "Plantronics"Option "Ignore" "true"EndSectionSection "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.
-
There might be a 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.
-
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.root>Audio>Value name: RecordScaleValue data: 400 (Default is 100)Value name: RecordScaleAuto -Value data: 0 (Default is 1- sets to 100)1 Sets the RecordScale value based on the hardware type.2 Does not set the RecordScale value based on the hardware type.For playback, these controls work the same way as the input volume controls.root>Value name: OutputScaleValue data: 400 (Default is 100)Value name: OutputScaleAutoValue data: 0 (Default is 1)