Cisco Jabber Softphone for VDI supports the following new Cisco Jabber for Windows Release 12.7 features:

• BOT Support

• Display Directory Number or Label for Single Lines

• Call Progress Indicator for Extend & Connect

• Chat Rooms Maintains Participant List Visibility

• Configure Clients Through Cisco Webex Control Hub

• Device Selection from the Conversation Window

• Enhancement to Security Labels

• Enterprise Content Management (ECM) Support

• People Insights

• Improved Office 365 Migration Authentication Notification

• Improved Voicemail

• Modern Design

• OAuth Handling of Refresh Tokens

• OAuth Sign-Out Behavior

• On-Demand Recording

• Presence Based on Non-Jabber Activity

• Proxy Authentication Support

• Quote Message

• Themes

For more information about the new Cisco Jabber features, see Release Notes for Cisco Jabber for Windows: https://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/products-release-notes-list.html.

For a list of Cisco Jabber features that are not supported with Cisco Jabber Softphone for VDI, see Cisco Jabber Features.

We've added support for CTI failover. When a failover occurs, from one Cisco Unified Communications Manager to another, Cisco Jabber for Windows retains phone functionality.

This release includes a new parameter for controlling headset selection. By default, when you connect a new headset Cisco Jabber adds it to the top of the priority list. This is a problem in some hot-desking environments. When a user moves their thin client and headset, the embedded microphone becomes the preferred device. You can set this parameter to ensure that the user's headset remains the preferred device.

The parameter applies only to Cisco Jabber Softphone for VDI (all platforms)

You can use the parameter to specify whether Cisco Jabber adds a new device to the top, or to the bottom of the device priority list in the Advanced settings.

• PreferNewDevice (default)—Cisco Jabber adds the new headset to the top of the list, and makes it the preferred device.

• PreferOldDevice—Cisco Jabber adds a new headset to the bottom of the list with no change to the configured preferred device

Example:

<HeadsetPreferenceOnVDI>PreferOldDevice</HeadsetPreferenceOnVDI>

This release introduces a 64-bit installation package for Unicon eLux 6.5 LTS

We have added support for the Cisco Jabber Multiline feature. Multiline provides mid-call features such as hold, transfer, and call forward, for users with more than one configured line. Multiline even works for video calls. You can configure up to eight lines in softphone mode. Only the primary line is supported when users access Cisco Jabber using Mobile and Remote Access (MRA).

Cisco Jabber for Windows supports Cisco Hosted Collaboration Solution (HCS), Cisco Packaged Contact Center Enterprise (PCCE), Cisco Contact Center Enterprise (CCE), and Cisco Unified Contact Center Express (CCX) 11.6 (up to four lines). For more information, see the Features Configuration Guide for Cisco Jabber.

In a virtual environment, users do not always access the same virtual desktop. To guarantee a consistent user experience, their profiles must be accessible every time they start Cisco Jabber. We have added support for roaming profiles. Cisco Jabber with Cisco Jabber Softphone for VDI stores data in the following locations:

%currentuser%\AppData\ Local \Cisco

• Contacts—Contact cache files

• History—Call and chat history

• Photo cache—Caches the directory photos locally

%currentuser%\AppData\Roaming\Cisco

• Config—Maintains user configuration files and stores configuration store cache

• Credentials—Stores encrypted username and password file

Because file encryption and decryption are linked to the Windows user profile, ensure that the following folders are accessible:

• C:\Users\username\AppData\Roaming\Microsoft\Crypto

• C:\Users\username\AppData\Roaming\Microsoft\Credentials

• C:\Users\username\AppData\Local\Microsoft\Crypto

• C:\Users\username\AppData\local\Microsoft\Credentials

For more information, see the Planning Guide for Cisco Jabber.

Citrix Virtual Apps and Desktops was formerly known as Citrix XenApp and Citrix XenDesktop.

Cisco Jabber Softphone for VDI Release 12.7 supports Citrix-based published desktops, shared desktops, and shared applications (full-screen and windows modes).

The Cisco Jabber for Windows and Cisco JVDI Agent versions must always match. However, the JVDI Client version can be the same, or the prior release (N-1 support). The following version combinations are supported:

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

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

Accessory call control (adjust call volume, answer or end phone calls, and mute audio) is supported for compatible headsets. Some other headsets provide basic functionality, but the accessory call control features do not work with Cisco Jabber Softphone for VDI. For a complete list of compatible headsets and other accessories, see https://www.cisco.com/c/en/us/products/unified-communications/uc_endpoints_accessories.html.

Cisco Jabber Softphone for VDI does not support Call Preservation, also known as "survivability". If a network interruption occurs and Cisoc Jabber goes into Call Preservation mode, the calls drop for VDI users.

Cisco Jabber Softphone for VDI Release 12.7 supports all Cisco Jabber for Windows Release 12.7 features, except the following:

• Application Sharing

• Audio device selection from the Hub Menu

• Cisco Unified Survivable Remote Site Telephony (SRST)

• Migrate Custom Contacts

• Far End Camera Control (FECC)

• Federal Information Processing Standard, Publication 140-2 (FIPS 140-2) and Information Assurance (IA) Compliance

• Improved Video Resolution

• Cisco Jabber to Jabber Call

• Cisco Jabber desk phone video (display of video on the desktop when the thin client is connected to the user's desk phone)

• Kerberos and Common Access Card (CAC) with Single Sign On (SSO)

  Cisco Jabber Softphone for VDI does not support CAC, and supports Kerberos only with SSO.

• PreferP2PDesktopShare (configuration parameter to prioritize person to person screen sharing over video sharing in the Cisco Jabber configuration file)

• Wireless Screen Sharing

Cisco Jabber Softphone for VDI does not support HDX Plug-n-Play for cameras. Citrix recommends using HDX Webcam for camera interactions.

Cisco Jabber Softphone for VDI supports only PC-over-IP (PCoIP) for VMware and ICA for Citrix.

When you create a Cisco Unified Client Services Framework (CSF) device, you specify a SIP Profile for the device. SIP profiles provide specific SIP information for the phone, such as registration and keepalive timers, media ports, and Do Not Disturb control.

You can use Certificate Authority Proxy Function (CAPF) to manage the phone certificates for the hosted desktop versions of Jabber for Windows. When you change the CAPF Certificate Operation from No Pending Operation to Install/Upgrade, the users must reset Jabber for Windows and sign in to complete the certificate installation.

Important

Do not choose Authentication Mode By Null string when using the Certificate Authority Proxy Function (CAPF). This setting breaks Cisco Jabber Softphone for VDI registration to Cisco Unified Communications Manager.

Cisco Jabber Softphone for VDI does not support Display Scaling mode. Users should check their VMware Options menu and ensure that Allow Display Scaling is not checked.

Cisco Jabber Softphone for VDI supports full-screen display only; windows mode is not supported.

Cisco Jabber Softphone for VDI establishes video quality at the start of a call. If you start a call with one of the supported HD cameras, and then switch to a standard-definition camera, video quality is affected. We recommend that you switch cameras between calls.

Software decoding relies heavily on the CPU. Estimated CPU usage for the Cisco JVDI Client with lower-end CPUs is as follows:

• 1.5Ghz, Dual core CPU—65% (55 to 75%)

• 1.5Ghz, Quad core CPU—35% (25 to 45%)

Use of a camera with a built-in hardware decoder reduces the load on the CPU.