Release and General Information

These release notes describe new features, requirements, restrictions, and caveats for Cisco Jabber Softphone for VDI for Unicon eLux Release 12.0. These release notes are updated for every maintenance release but not for patches or hot fixes.

Before you install Cisco Jabber Softphone for VDI, we recommend that you review these release notes for information about issues that may affect your system.


Note

Cisco Jabber Softphone for VDI was formerly called Cisco Virtualization Media Edition.


Introduction to Cisco Jabber Softphone for VDI

In this release notes document, the term thin client refers to any supported device (including reused PCs) used to access the hosted virtual desktops (HVD).

Cisco Jabber Softphone for VDI extends the Cisco collaboration experience to virtual deployments. With supported versions of Cisco Jabber for Windows or Cisco UC Integration™ for Microsoft Lync, users can send and receive phone calls on their hosted virtual desktops (HVD). The software routes all audio and video streams directly from one endpoint to another, without going through the HVD.

The Cisco Jabber for Windows version must match your Cisco Jabber Softphone for VDI version. The Cisco JVDI Agent and Cisco JVDI Client versions must be the same.

For more information about Cisco Jabber, see the Release Notes for Cisco Jabber for Windows for your release:

https://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/products-release-notes-list.html

For more information about Cisco UC Integration™ for Microsoft Lync, see the Release Notes for Cisco UC Integration for Microsoft Lync for your release:

https://www.cisco.com/c/en/us/support/unified-communications/uc-integration-tm-microsoft-lync/products-release-notes-list.html

Languages

The Cisco JVDI Agent and Cisco JVDI Client installation programs, and Device Selector are localized in the following languages:

  • Arabic

  • Bulgarian

  • Catalan

  • Chinese Simplified

  • Chinese Traditional

  • Croatian

  • Czech

  • Danish

  • Dutch

  • English(US)

  • Finnish

  • French

  • German

  • Greek

  • Hebrew

  • Hungarian

  • Italian

  • Japanese

  • Korean

  • Norwegian

  • Polish

  • Portuguese Brazil

  • Portuguese Portugal

  • Romanian

  • Russian

  • Serbian

  • Slovak

  • Slovenian

  • Spanish

  • Swedish

  • Thai

  • Turkish

Cisco Jabber Softphone for VDI Copyright

Copyright © 2018–2019 Cisco or its affiliated entities. All Rights Reserved.

New in This Release for Cisco Jabber Softphone for VDI

Cisco Jabber Softphone for VDI for Unicon eLux Release 12.0 adds support for the following programs and features:

Cisco Jabber Support

This release supports Cisco Jabber for Windows Release 12.0.

Cisco Jabber Softphone for VDI supports all Cisco Jabber for Windows and Cisco UC Integration™ for Microsoft Lync features, except the following:

  • Accessory Call Control (adjust call volume, answer or end phone calls, and mute audio) for the following accessories:

    • Logitech

    • Plantronics

    • Sennheiser

  • Audio device selection from the Hub Menu

  • Binary Floor Control Protocol (BFCP) Desktop Share

  • Cisco Unified Survivable Remote Site Telephony (SRST)

  • Collaboration Edge

  • Device Selection menu on the Call Conversation window

  • Direct Pickup and Group Pickup

  • Far End Camera Control (FECC)

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

  • Jabber to Jabber Call

  • 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)

  • Multiline

    Only the first line of a multiline account is available. If a second call comes in, while the first line is in use, the second line rings, but no incoming call notification appears.

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

System Requirements


Important

Each of the components listed in the following table must meet the requirements. Use of unsupported components can result in a nonfunctional deployment.

Only the components and requirements listed in the table are supported.


Component

Requirements

Unicon eLux thin clients—Hardware

The minimum hardware requirements for thin clients are:

  • 1.6-GHz dual-core processor

  • 2-GB RAM

The following client hardware was tested with eLux RP 5.2.0, RP 5.3.0, RP 5.5.0, RP 5.5.1, and RP 5.7.0:

  • HP T620 Dual Core / Quad Core

  • HP T630 Dual Core / Quad Core

  • Cisco VXC 6215

  • Dell Wyse Z50D

Hosted virtual desktop OS (server-side)

  • Microsoft Windows 7 32 bit

  • Microsoft Windows 7 64 bit

  • Microsoft Windows 8 32 bit

  • Microsoft Windows 8 64 bit

  • Microsoft Windows 8.1 32 bit

  • Microsoft Windows 8.1 64 bit

  • Microsoft Windows 10 32 bit

  • Microsoft Windows 10 64 bit

Connection broker for the hosted virtual desktop

1
  • Citrix XenDesktop 6.5, 7.5, and later 7.x versions

  • Citrix XenApp 6.5, 7.5, and later 7.x versions—Published desktops only

  • VMware Horizon 6.0 (with View)—Published desktops only

  • VMware Horizon 6 version 6.1.0, 6.2.0, 7.0 and later 7.x versions—Published desktops only

Citrix XenApp Published Application is not supported with Cisco Jabber Softphone for VDI for Unicon eLux.

Citrix Receiver or

VMware Horizon Client

2

(Installed on the thin client)

Unicon eLux contains the required Citrix Receiver and VMware Horizon Client.

For Unicon eLux 5.2.0

  • ICA Client V13.3.0.1-9 and later 13.3 versions

  • VMware Horizon View Client V5.7.1.1-3 and later 5.7 versions

For Unicon eLux 5.3.0, 5.5.0, 5.5.1, and 5.7.0

  • ICA Client V13.3.9.1-13 and later versions

  • VMware Horizon View Client V6.0.0.3-1 and later 6.0 versions

Cisco Unified Communications client on the hosted virtual desktop:

Cisco Jabber for Windows or Cisco UC Integration™ for Microsoft Lync.

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

Cisco Jabber Softphone for VDI is compatible with all future 12.0(x) Cisco Jabber for Windows versions.

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 AnyConnect (Optional)

vpnsystem V4.5-1

Accessories

For a complete listing of supported 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.

Important 

Ensure that all Jabra devices are running the latest firmware. You can use Jabra Direct to update the firmware. For more information visit: http://www.jabra.com.

1

A connection broker is software that creates connections to hosted virtual desktops. A connection broker performs a number of tasks that include

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

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

2

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

Installation and Upgrade Notes

There is no supported upgrade path from Cisco Virtualization Experience Media Engine for Unicon eLux. To install Cisco Jabber Softphone for VDI, first uninstall Cisco Virtualization Experience Media Engine (VXME Client and VXME Agent).

Important Notes

Cisco Audio Session Tunnel

Cisco Audio Session Tunnel (CAST) connection to the HVD is not supported.

Cisco Media Services Interface and Dual VLAN

Cisco Media Services Interface (MSI) and Dual VLAN are not supported for this release.

Cisco Expressway

Cisco Jabber Softphone for VDI does not support the use of Mobile Remote Access and Cisco Expressway.

Cisco Unified Communications Manager Failover

When a failover from one Cisco Unified Communications Manager to another occurs, Cisco Jabber for Windows retains phone functionality. However, with Cisco Jabber Softphone for VDI, phone functionality is lost. This issue occurs because CTI failover is not supported in the virtual environment.

Echo Cancellation

Echo cancellation is enabled only for audio calls.

SIP Profiles

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.


Important

If you choose Secure Phone Profile, do not specify the Certificate Authority Proxy Function (CAPF) authentication mode By Null string. This setting is not supported for use with Cisco Jabber Softphone for VDI, because it causes Jabber registration with Cisco Unified Communications Manager to fail.


USB Camera Redirection Not Supported with VMware View

USB camera redirection is not supported with VMware View.

HDX RealTime Webcam with Citrix

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

Silent Monitoring and Call Recording

Cisco Jabber Softphone for VDI supports silent monitoring and call recording. To enable these audio path functions for a device, you configure Cisco Unified Communications Manager. For step-by-step instructions, the Cisco Unified Communications Manager Features and Services Guide for your release.

  • Cisco Jabber does not provide any interface to start silent monitoring or call recording. Use the appropriate software to silently monitor or record calls.

  • Cisco Jabber does not currently support monitoring notification tone or recording notification tone.

  • You can use silent monitoring and call recording functionality only. Cisco Jabber does not support other functionality such as barging or whisper coaching.

  • You might need to download and apply a device package to enable monitoring and recording capabilities on the device, depending on your version of Cisco Unified Communications Manager.

Determine Device Package Requirements

Use Cisco Unified Communications Manager Administration to determine whether a device requires a device package to enable silent monitoring and recording.
Procedure

Step 1

Navigate to and open the Phone Configuration window for the device, for which you want to enable monitoring and recording.

Step 2

Locate the Built-in-Bridge field.

If the Built-in-Bridge field is not available, download and install a device package for the device.


Accessories

Jabra Firmware

Ensure that all Jabra devices are running the latest firmware. You can use Jabra Direct to update the firmware. For more information visit: http://www.jabra.com.

Adjust Settings for Jabra Bluetooth Devices

Most Jabra Bluetooth devices introduce a short delay in bringing up the audio path (about 1 to 3 seconds). For supported Jabra Bluetooth devices, you can eliminate the delay by changing the device settings in Jabra Direct. For more information, visit http://www.jabra.com.

Before you begin

Jabra Direct must be installed.

Procedure

Step 1

Open Jabra Direct.

Step 2

Click the Jabra device for which you want to modify the settings.

Step 3

Click Settings.

Step 4

Click to expand Softphone (PC).

Step 5

From the Preferred softphone list, select Cisco Jabber or Cisco UC Integration for Microsoft Lync.

Step 6

Set Open phone line to On.

Step 7

Set PC audio to Off.

Step 8

Click Apply.


Camera Hot Swap

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.

Caveats

Search for Bugs

Bug Classification

Known defects, or bugs, have a severity level that indicates the priority of the defect. Development managers usually define bug severity. Severity helps the product team focus on bug fixes for future releases and prioritize fixes.

The following table describes bug severity levels:
Severity level Description
1 Catastrophic Reasonably common circumstances cause the entire system to fail, or a major subsystem to stop working, or other devices on the network to be disrupted. No workarounds exist.
2 Severe Important functions are unusable and workarounds do not exist. Other functions and the rest of the network is operating normally.
3 Moderate Failures occur in unusual circumstances, or minor features do not work at all, or other failures occur but low-impact workarounds exist.

This is the highest level for documentation bugs.

4 Minor Failures occur under very unusual circumstances, but operation essentially recovers without intervention. Users do not need to install any workarounds and performance impact is tolerable.
5 Cosmetic Defects do not cause any detrimental effect on system functionality.
6 Enhancement Requests for new functionality or feature improvements.

Search for Bugs

Use the Bug Search page to obtain more information about a bug.
  1. Go to https://tools.cisco.com/bugsearch.
  2. Sign in with your Cisco.com user ID and password.
  3. Enter a bug ID or specify search parameters.
For more information, select Help at the top right of the Bug Search page.

Open Caveats in Release 12.0

There are no open caveats (bugs) for this release.

Closed Caveats in Release 12.0

There are no closed caveats (bugs) for this release.

Resolved Caveats in Release 12.0

The following table lists the caveats (bugs) that are fixed in this release.

Caveat ID Number

Severity

Description

CSCvg52148

3

VXME 11.9.0 - New installation of VXME for Unicon eLux fails.

CSCvh80408

3

VXME 11.9 Signalling does not work with Jabra headsets

CSCvi14892

4

VXME 11.9 registers on the CUCM wrong display active load id for CSF as version 12.0