This release includes bug fixes and minor enhancements. For more information, see Resolved Caveats for Release 12.8(1).

Cisco Jabber Support

This release supports the following new Cisco Jabber for Windows Release 12.8 features:

• Audio Device Priority

• Call Park

• Cisco Headset Support

• Global Shortcut Key for Conversation Window

• Microsoft Office 2019 Support

• Multiline Per Line Ringtones

Attention

With N-1 or N-2 support, the lower version determines the available feature set.

Deprecated Parameter

We added the HeadsetPreference parameter to specify how Cisco Jabber handles new audio devices.

Note	The new parameter replaces the now deprecated HeadsetPreferenceOnVDI parameter.

By default, when you connect a new audio device, Cisco Jabber adds it to the top of the priority list. The default behavior is a problem in some hot-desking environments. When a user moves their thin client and headset, the embedded microphone becomes the preferred device.

Modern meeting rooms are often equipped with a large wall mounted monitor with HDMI, which handles both audio and video. When a Cisco Jabber user connects to a monitor using HDMI, by default the monitor becomes the preferred device.

You can set this parameter to ensure that the user's headset remains the preferred device. Users can override this setting in their Audio preferences. For more information about the new parameter, see Parameters Reference Guide for Cisco Jabber Release 12.8.

Mute Notification Sounds During Calls or Meetings

Users in VDI deployments can now choose to mute notification sounds during their calls or meetings.

Version Support Strategy

The Cisco Jabber for Windows and Cisco JVDI Agent versions must always match. However, the JVDI Client version can be the same, or up to two releases earlier (N-2 support). For example, the following version combinations are supported:

• Cisco Jabber for Windows Release 12.8, Cisco JVDI Agent Release 12.8, and Cisco JVDI Client Release 12.8

• Cisco Jabber for Windows Release 12.8, Cisco JVDI Agent Release 12.8, and Cisco JVDI Client Release 12.7

• Cisco Jabber for Windows Release 12.8, Cisco JVDI Agent Release 12.8, and Cisco JVDI Client Release 12.6

VDI Fallback Mode

Sometimes the Cisco JVDI Agent and the Cisco JVDI Client can't communicate. This issue occurs because of a network problem with the virtual channel, or because of a problem with the Cisco Jabber Softphone for VDI installation. If the JVDI Agent and the JVDI Client can't communicate, Cisco Jabber can't operate in VDI-optimized mode. For more information about troubleshooting, see Deployment and Installation Guide for Cisco Jabber Softphone for VDI Release 12.8.

This release introduces VDI Fallback mode, and a new parameter to enable this mode. Cisco Jabber Softphone for VDI checks the virtual channel every 10 seconds, to ensure that the JVDI Agent and the JVDI Client can communicate. If communication is down, for two consecutive checks, Cisco Jabber Softphone for VDI switches Cisco Jabber to VDI Fallback mode. For more information about the new EnableVDIFallback parameter, see Parameters Reference Guide for Cisco Jabber Release 12.8.

In VDI Fallback mode, users can make and receive calls, with audio traveling over the ICA channel. The connection status for Cisco Jabber changes from Softphone with VDI, to Softphone. Users can receive video; the ability to send video depends on the capabilities of your Citrix or VMware version. Audio and video quality depend on network conditions, and the capabilities of your Citrix or VMware version. When Cisco Jabber operates in VDI Fallback mode, users see a notification message at the start of each call.

When Cisco Jabber Softphone for VDI detects communication between the JVDI Agent and the JVDI Client, it automatically switches Cisco Jabber back to VDI-optimized mode.

Note	Cisco Jabber Softphone for VDI switches modes only between calls.

General requirements apply to all Cisco Jabber Softphone for VDI platforms.

Important

Only the components, versions, and minimum hardware requirements listed in this guide are supported. Use of unsupported components can result in a nonfunctional deployment.

Accessories

For a complete listing of recommended audio and video accessories, see Unified Communications Endpoint and Client Accessories, at http://www.cisco.com/c/en/us/products/unified-communications/uc_endpoints_accessories.html.

Ensure that all Jabra devices are running the latest firmware. You can use Jabra Direct to update the firmware.

Cisco Jabber for Windows

Cisco Jabber for Windows 12.8 running on the hosted virtual desktop (HVD).

For complete information about virtual environment compatibility, see the Cisco Jabber documentation for your release.

Cisco Unified Communications Manager

Recommended: CUCM Release 11.5(1)SU3 or later

Minimum: CUCM Release 10.5

Cisco Expressway for Mobile and Remote Access (MRA)

Recommended: Expressway X12.5

Minimum: Expressway X8.11.4

Connection Broker—Installed on the Hosted Virtual Desktops

• Citrix Virtual Apps and Desktops (formerly XenApp and XenDesktop) versions 7.x and later (latest LTSR 1912), and 7.15 CU5 LTSR

  Shared Desktop is supported only in full-screen mode. Published Application is supported in full-screen mode for Cisco Jabber Softphone for VDI—Windows.

• VMware Horizon versions 6.x to 7.11.

A connection broker is software that creates connections to hosted virtual desktops. A connection broker performs a number of tasks including the following:

• Validating the username and providing a connection for the user.

• Allowing the user to connect to a specific virtual desktop.

Operating Systems—Installed on the Hosted Virtual Desktops

• Microsoft Windows 8 32–bit

• Microsoft Windows 8 64–bit

• Microsoft Windows 8.1 32–bit

• Microsoft Windows 8.1 64 64–bit

• Microsoft Windows 10 32–bit

• Microsoft Windows 10 64–bit

Server Operating Systems—Installed on the Hosted Virtual Desktops

• Microsoft Windows Server 2012 R2

• Microsoft Windows Server 2016

Port Requirements

Cisco Jabber Softphone for VDI requires the same ports as Cisco Jabber does, and the following additional port range:

Supported Codecs

Audio Codecs:

• G.722

• G.722.1 (24 and 32k)

  G.722.1 is supported on Cisco Unified Communications Manager 8.6.1 or later.

• G.711 A-law

• G.711 u-law

• G.729a

• Opus

  Opus is supported on Cisco Unified Communications Manager 11.0 or later.

Video Codec: H.264/AVC

Citrix Workspace app or VMware Horizon Client—Installed on the Thin Clients

The HP Thin Pro image includes the required Citrix and VMware versions.

The Citrix Workspace app or VMware Horizon Client provides a user interface for the corresponding connection broker.

Published application mode and the scale to fit option are not supported.

HP Thin Pro Thin Clients—Hardware

We recommend the following client hardware, which was tested with HP Thin Pro 6.2:

• HP t520

• HP t530

• HP t620

• HP t630

• HP t730

• HP mt21

We recommend the following client hardware, which was tested with HP Thin Pro 7.1 SP3.3:

• HP t430

• HP t520

• HP t530

• HP t630

• HP t730

• HP mt21

HP ThinPro Platform Image

32–bit: HP ThinPro 6.2

64–bit: HP ThinPro 7.1 SP3.3 and 7.x versions

Ubuntu Desktop Image

• Ubuntu 14.04 32b LTS (i386)

• Ubuntu 16.04 64b LTS (AMD64)

• Ubuntu 18.04 64b LTS (AMD64)

• Ubuntu 20.04 64b LTS (AMD64)

Note	The supported versions do not include Ubuntu Minimal.

Ubuntu Thin Clients—Hardware

The minimum hardware requirements for thin clients are as follows:

• Installed RAM 2 GB

• Free Physical Memory 1 GB

• Free Disk Space 256 MB

• CPU: AMD G-T56N 1.65Ghz, or Intel Core2Duo T7500 2.2 GHz

• USB 2.0 for USB camera and audio devices

Citrix Workspace app or VMware Horizon Client—Installed on the Thin Clients

• Citrix Receiver 13.0 and later

• Citrix Workspace app 1808 and later

• VMware Horizon View Client versions 4.x, 5.x, and 8.x

The Citrix Workspace app or VMware Horizon Client provides a user interface for the corresponding connection broker.

Published application mode and the scale to fit option are not supported.