Introduction

Build Number

What's New in Release 11.6(4)

What's New in Release 11.6(3)

What's New in Release 11.6(2)

What's New in Release 11.6(1)

What's New in Release 11.6

Requirements

Software Requirements

Hardware Requirements

Network Requirements

Ports and Protocols

Third-Party Requirements

Limitations and Restrictions

Limitations and Restrictions for All Deployments

Limitations and Restrictions for On-Premises Deployments

Limitations and Restrictions for Cloud Deployments

Performance and Behavior Notes

Caveats

Bug Severity Levels

Search for Bugs

Open Caveats in Release 11.6(3)

Resolved Caveats in Release 11.6(3)

Open Caveats in Release 11.6(2)

Resolved Caveats in Release 11.6(2)

Open Caveats in Release 11.6(1)

Resolved Caveats in Release 11.6(1)

Open Caveats in Release 11.6

Resolved Caveats in Release 11.6

Release Notes for Cisco Jabber for Windows 11.6.x

First Published: April 20, 2016

Last Updated: July 10, 2017

Introduction

These release notes describe new features, requirements, restrictions, and caveats for all versions of Cisco Jabber for Windows Release 11.6. These release notes are updated for every maintenance release but not for patches or hot fixes. Each maintenance release includes the features, requirements, restrictions, and bug fixes of the previous releases unless mentioned otherwise. Before you install Cisco Jabber for Windows, we recommend that you review this document for information about issues that may affect your system.

Build Number

Release

Build Number

Release 11.6(4)

11.6.4.53396

Release 11.6(3)

11.6.3.44957

Release 11.6(2)

11.6.2.40282

Release 11.6(1)

11.6.1.38147

Release 11.6

11.6.0.35037

What's New in Release 11.6(4)

Security Enhancement

This release provides a Security update for WebEx Desktop Share.

What's New in Release 11.6(3)

Updated JCF Library

The Cisco Jabber Client Framework (JCF) Components includes a version of the 'LibTiff' library that is affected by the vulnerabilities identified by the following Common Vulnerability and Exposures (CVE) IDs:

CVE-2013-1961,CVE-2013-1960,CVE-2013-4244,CVE-2013-4243,CVE-2012-4447,CVE-2012-3401, CVE-2015-1547,CVE-2014-9655,CVE-2013-4231

The LibTiff library has been removed from the JCF component. This vulnerability has been resolved with caveat CSCva89914.

Resolved Caveats

This release provides fixes for a number of known issues. See the Resolved Caveats in Release 11.6(3) section for a list of caveats fixed in this release.

What's New in Release 11.6(2)

Resolved Caveats

This release provides fixes for a number of known issues. See the Resolved Caveats in Release 11.6(2) section for a list of caveats fixed in this release.

What's New in Release 11.6(1)

Resolved Caveats

This release provides fixes for a number of known issues. See the Resolved Caveats in Release 11.6(1) section for a list of caveats fixed in this release.

What's New in Release 11.6

IPv6

Cisco Jabber 11.6 is fully IPv6 ready, it works as normal in pure IPv6 and hybrid networks, subject to a number of limitations (for more information see the Planning Guide for Cisco Jabber 11.6. Cisco Collaboration solutions does not currently fully support IPv6. For example, Cisco VCS Expressway for Mobile and Remote Access has limitations in pure IPv6 networks that require NAT64/DNS64 to be deployed in mobile carrier networks. Cisco Unified Communications Manager and Cisco Unified Communications Manager IM and Presence Service don't currently support HTTPS in pure IPv6 networks.

IPv6 is configured using the IP_Mode parameter to set the protocol to IPv4, IPv6, or dual stack. Dual stack is the default setting. The IP_Mode parameter can be included in the jabber-config.xml file, the bootstrap for Windows, and the URL configuration for Mac and Mobile clients.

The network IP protocol used by Jabber when connecting to services is determined by the following factors:

- The jabber-config.xml IP_Mode parameter.

- The client operating system IP capabilities.

- The server operating system IP capabilities.

- The availability of a DNS record for IPv4 and IPv6.

- Cisco Unified Communications Manager SIP setting for softphone devices configuration for IPv4, IPv6, or both. The SIP connection setting for softphone devices must match the Jabber IP_Mode parameter setting to make a successful connection.

- Underlying network IP capabilities.

On Cisco Unified Communications Manager, the IP capability is determined by generic server settings and device-specific settings.

When you use Jabber in IPv6_only mode, NAT64/DNS64 is required to connect to an IPv4 infrastructure. For example, when connecting to Cisco WebEx Messenger service, Cisco VCS Expressway for Mobile and Remote Access, and Cisco Spark.

For more information about the IP_Mode parameter, see the Parameters Reference Guide for Cisco Jabber 11.6. For more information about IPv6 support, see the Planning Guide for Cisco Jabber 11.6.

Cisco Jabber Diagnostics Tool

The Cisco Jabber Diagnostics Tool provides configuration and diagnostics information for the following functionality:

- Service Discovery

- WebEx

- Cisco Unified Communications Manager Summary

- Cisco Unified Communications Manager Configuration

- Voicemail

- Certificate Validation

- Active Directory

- DNS Records

To access the Cisco Jabber Diagnostics Tool window, users must bring the hub window into focus and enter Ctrl + Shift + D. Users can update the data by clicking the Reload button. Users can also save the information to an HTML file by clicking the Save button.

The Cisco Jabber Diagnostics Tool is available by default. To disable this tool, set the DIAGNOSTICS_TOOL_ENABLED installation parameter to FALSE. For more information about this installation parameter, see On-Premise Deployment for Cisco Jabber 11.6, or Cloud and Hybrid Deployments for Cisco Jabber 11.6, depending on your setup.

New Configuration for Meeting Notifications

The DisableNonAcceptMeetingReminder parameter determines whether the Cisco Jabber popup meeting notification is displayed for nonaccepted WebEx Meetings. The default value is false, which means that the Jabber popup meeting notification displays for nonaccepted WebEx Meetings.

For more information about this parameter, see the Parameters Reference Guide for Cisco Jabber 11.6.

User Interface Updates

Presence pills and avatars have been redesigned and now have a round shape. Accessibility icons have also been redesigned. For more information about accessibility icons, see the Cisco Jabber for Windows 11.6 User Guide.

Documentation Updates

The document Features and Options for Cisco Jabber has been renamed to Feature Configuration for Cisco Jabber. This document has been restructured so that features are grouped in functional sections and listed alphabetically.

Requirements

Software Requirements

Server

Software

Operating systems

- Microsoft Windows 10, 32 bit and 64 bit (Desktop OS x86)

- Microsoft Windows 8.x, 32 and 64 bit

- Microsoft Windows 7 SP1 or later, 32 and 64 bit

On-premises servers

- Cisco Unified Communications Manager version 9.x or later

- IM and Presence Service version 9.x or later

- Cisco Unity Connection version 8.6(2) or later

- Cisco WebEx Meetings Server version 2.6 MR1 or later

- Cisco Expressway Series for Cisco Unified Communications Manager 8.6.2 or later

- Cisco TelePresence Video Communication Server 8.1.1 or later

Virtual servers

- Citrix XenDesktop 7.6, 7.5, 7.1

- Citrix XenApp 7.6 published desktop, 7.5 published desktop, 6.5 published desktop

- VMWare Horizon View 6.1, 6.0, 5.3

Cloud-based servers

- Cisco WebEx Messenger service

- Cisco WebEx Meeting Center, version WBS28 or later

- Cisco WebEx Meetings Server 1.5 and later

Directory servers

- Active Directory Domain Services for Windows Server 2012 R2

- Active Directory Domain Services for Windows Server 2008 R2

- Any server that supports LDAPv3 protocol

- Active Directory Lightweight Directory Service (AD LDS) or Active Directory Application Mode (ADAM)

User Data Service

- Cisco Unified Communications Manager version 9.1(2) with the following COP file:
cmterm-cucm-uds-912-5.cop.sgn.

- Cisco Unified Communications Manager version 10.0(1). No COP file is required.

Hardware Requirements

Hardware

Requirement

Installed RAM

2 GB RAM

Free Physical Memory

128 MB

Free Disk Space

256 MB

CPU Speed and Type

- Mobile AMD Sempron Processor 3600+ 2 GHz

- Intel Core2 CPU T7400 at 2. 16 GHz

- Intel Atom

GPU

DirectX11 on Microsoft Windows 7

I/O Ports

USB 2.0 for USB camera and audio devices.

Network Requirements

Ports and Protocols

The client uses the ports and protocols listed in the following table. If you plan to deploy a firewall between the client and a server, configure the firewall to allow these ports and protocols.

Port

Application Layer Protocol

Transport Layer Protocol

Description

Configuration

6970

HTTP

TCP

Connect to the TFTP server to download client configuration files.

6972

HTTPS

TCP

Connects to the TFTP server to download client configuration files securely for Cisco Unified Communications Manager release 11.0 and later.

53

DNS

UDP

Hostname resolution.

3804

CAPF

TCP

Issues Locally Significant Certificates (LSC) to IP phones. This port is the listening port for Cisco Unified Communications Manager Certificate Authority Proxy Function (CAPF) enrollment.

8443

HTTPS

Traffic to Cisco Unified Communications Manager and Cisco Unified Communications Manager IM and Presence Service.

8191

SOAP

TCP

Connects to local port to provide Simple Object Access Protocol (SOAP) web services.

Directory Integration—For LDAP contact resolution one of the following ports are used based on LDAP configuration.

389

LDAP

TCP

LDAP TCP (UDP) Connects to an LDAP directory service.

3268

LDAP

TCP

Connects to a Global Catalog server for contact searches.

636

LDAPS

TCP

LDAPS TCP Connects securely to an LDAP directory service.

3269

LDAPS

TCP

LDAPS TCP Connects securely to the Global Catalog server.

Instant Messaging and Presence

443

XMPP

TCP

XMPP traffic to the WebEx Messenger service. The client sends XMPP through this port in cloud-based deployments only. If port 443 is blocked, the client falls back to port 5222.

5222

XMPP

TCP

Connects to Cisco Unified Communications Manager IM and Presence Service for instant messaging and presence.

37200

SOCKS5 Bytestream

TCP

Peer to Peer file transfer, In on-premises deployments, the client also uses this port to send screen captures.

7336

HTTPS

TCP

MFT File transfer (On-Premises only).

Communication Manager Signaling

2748

CTI

TCP

Computer Telephony Interface (CTI) used for desk phone control.

5060

SIP

TCP

Provides Session Initiation Protocol (SIP) call signaling.

5061

SIP over TLS

TCP

SIP over TCP Provides secure SIP call signaling. (Used if Secure SIP is enabled for device.)

30000 to 39999

FECC

UDP

Far end camera control (FECC).

5070 to 6070

BFCP

UDP

Binary Floor Control Protocol (BFCP) for video screen sharing capabilities.

Voice or Video Media Exchange

16384 to 32766

RTP/SRTP

UDP

Cisco Unified Communications Manager media port range used for audio, video, and BFCP video desktop share.

33434 to 33598

RTP/SRTP

UDP

Cisco Hybrid Services (Jabber to Jabber calling) media port range used for audio and video.

49152 to 65535

RDP

TCP

IM-only desktop share. Applies to Cisco Jabber for Windows only.

8000

RTP/SRTP

TCP

Used by Jabber Desk Phone Video Interface, allows users to receive video transmitted to their desk phone devices on their computers through the client.

Unity Connection

7080

HTTP

TCP

Used for Cisco Unity Connection to receive notifications of voice messages (new message, message update, and message deleted).

7443

HTTPS

TCP

Used for Cisco Unity Connection to securely receive notifications of voice messages (new message, message update, and message deleted).

443

HTTPS

TCP

Connects to Cisco Unity Connection for voicemail.

Cisco WebEx Meetings

80

HTTP

TCP

Connects to Cisco WebEx Meeting Center for meetings.

443

HTTPS

TCP

Connects to Cisco WebEx Meeting Center for meetings.

8443

HTTPS

TCP

Web access to Cisco Unified Communications Manager and includes connections for the following:

- Cisco Unified Communications Manager IP Phone (CCMCIP) server for assigned devices.

- User Data Service (UDS) for contact resolution.

Accessories Manager

8001

TCP

In Cisco Jabber for Windows and Mac, Sennheiser plugin uses this port for Localhost traffic for call controls.

Ports for Other Services and Protocols

In addition to the ports listed in this section, review the required ports for all protocols and services in your deployment. You can find the port and protocol requirements for different servers in the following documents:

- For Cisco Unified Communications Manager, Cisco Unified Communications Manager IM and Presence Service, see the TCP and UDP Port Usage Guide.

- For Cisco Unity Connection, see the System Administration Guide.

- For Cisco WebEx Meetings Server, see the Administration Guide.

- For Cisco WebEx services, see the Administrator's Guide.

- For Expressway for Mobile and Remote Access, refer to Cisco Expressway IP Port Usage for Firewall Traversal.

- For file transfer port usage, see the Configuration and Administration of IM and Presence Service on Cisco Unified Communications Manager.

Third-Party Requirements

Third-Party Software

Requirement

Microsoft Internet Explorer

Microsoft Internet Explorer 9 or later

Note:
Browser Click to Call is not supported on Microsoft Edge.

Microsoft Office

- Microsoft Office 2016 Desktop OS Version, 32 and 64 bit

- Microsoft Office 2013, 32 and 64 bit

- Microsoft Office 2010, 32 and 64 bit

Microsoft Exchange integrates directly with Cisco Unified Communications Manager. For more information, see the Configuration Guides for the appropriate version of Cisco Unified Communications Manager.

Microsoft SharePoint

- Microsoft SharePoint 2013

- Microsoft SharePoint 2010

Microsoft 365

Cisco Jabber for Windows supports client-side integration with Microsoft Office 365 with the following applications using an on-premises Active Directory (AD) deployment:

- Microsoft Office 2016 Desktop OS Version, 32 and 64 bit

- Microsoft Office 2013

- Microsoft Office 2010

Third-party calendars

- Microsoft Outlook 2016, 32 and 64 bit

- Microsoft Outlook 2013, 32 and 64 bit

- Microsoft Outlook 2010, 32 and 64 bit

- IBM Lotus Notes 9 32 bit

- IBM Lotus Notes 8.5.3 32 bit

- IBM Lotus Notes 8.5.2 32 bit

- IBM Lotus Notes 8.5.1 32 bit

- Google Calendar

Antivirus Exclusions

If you deploy antivirus software, include the following folder locations in the antivirus exclusion list:

- C:\Users\<User>\AppData\Local\Cisco\Unified Communications\Jabber

- C:\Users\<User>\AppData\Roaming\Cisco\Unified Communications\Jabber

- C:\ProgramData\Cisco Systems\Cisco Jabber

Limitations and Restrictions

Limitations and Restrictions for All Deployments

IBM Notes Contact Search

Jabber doesn't support searching for IBM Notes contacts using " or \ as the first character in the search string.

Microsoft Outlook OST File

Intermittently Cisco Jabber for Windows is unable to access the Microsoft Outlook OST file. To resolve this issue, restart Jabber and restart Outlook.

Automatic Detection of Proxy Settings (WPAD)

The Cisco Jabber for Windows Meetings Service no longer supports automatic detection of proxy settings. Web Proxy Auto-Discovery (WPAD) protocol lookup is supported only for iOS devices. For information about how to configure proxy settings for Cisco Jabber, see Configure Proxy Settings in the On-Premises Deployment for Cisco Jabber guide.

Call Transfers

When you are transferring a call to a third party, the third party must respond to the call before you can complete the transfer. You cannot currently dial the third party and connect the first party while waiting for the call to connect (also known as a blind transfer).

Chat Reply and No Voicemail Profile

The chat reply feature does not work if the user has no voicemail profile configured. If the user selects Chat reply in an incoming call, the call continues to ring and the Chat reply and Answer options are greyed out. This limitation is documented in CSCux75667.

Check Point VPN

Cisco Jabber for Windows does not currently support Check Point VPN. This limitation is documented in CSCuy34099.

Cisco AnyConnect Secure Mobility Client

Cisco Jabber for Windows supports Cisco AnyConnect Secure Mobility Client version 4.0 and later. This limitation is documented in CSCuy14721.

Cisco Unity Connection Dispatch Messages

In Cisco Unity Connection, a dispatch message is sent to a distribution list with the message configured in such a way that only one user responds to that message. A user can accept, decline, or postpone the dispatch message. Cisco Jabber for Windows does not support Cisco Unity Connection dispatch messages. This limitation is documented in CSCuw31908.

Emails to a Group of Contacts

There is a limit of 2083 characters in the To field when sending an email to a group of contacts. Depending on the length of the email addresses and the number of contacts, not all contacts may be added to the email. For more information about the 2083 character limitation, see Click Here . This limitation is documented in CSCuz80198.

Location Feature and Multiple Domain Support

Consider the following deployment scenario:

When you deployed your Cisco Unified Communications Manager IM and Presence Service node, all users were imported with single domain support. You later changed the address scheme to Directory URI (multiple domain support).

The location feature will now not work for newly added domain users. Users in the initial domain are unaffected. This limitation is documented in CSCuu76519.

Microsoft Outlook Local Contacts and Presence

Users' presence is unknown when the contact is manually added to contacts in Microsoft Outlook 2010 and 2013, when the contact is added to local (custom) contacts with an email address type of SMTP. To resolve this issue, delete the contact and add it again manually, ensuring the email address type is Exchange (EX). This item is documented in CSCuo57172.

Phone Mode Deployments with Microsoft Lync

Click-to-x functionality must be disabled if you want to deploy Cisco Jabber for Windows in phone mode on the same computer as Microsoft Lync. See the Common Installation Arguments section of the Deployment Guide for more information about the CLICK2X installer switch.

Plantronics Accessories and Software

If you use Plantronics accessories for Cisco Jabber call management, and if you have Plantronics Hub installed, ensure that at least version 3.5 is installed. Download Plantronics Hub 3.5 from the Plantronics website.

Remote Desktop Control over Mobile and Remote Access

Remote desktop control over Mobile and Remote Access is not supported. This limitation is documented in CSCuz19139.

SAML Single Sign-On Limitations

When configuring SAML SSO on Cisco Unified Communications Manager and Cisco Unity Connection servers, use a fully qualified domain name (FQDN) instead of an IP Address to define the server name. If you use an IP Address, the client displays a warning message that the certificate is not valid. The requirement to use an FQDN is because the embedded Internet Explorer browser is not able to validate IP addresses in the Subject Alternate Name (SAN) certificate.

Space Characters in Credentials

The following rules apply to space characters and credentials:

- Usernames can contain spaces in on-premises deployments.

- Usernames cannot contain spaces in cloud-based deployments.

- Passwords cannot contain spaces in any deployment scenario.

- The first and last characters of usernames in on-premises deployments must not be spaces. This rule is also true for usernames synchronized from a directory source.

Standard CTI Secure Connection User Group

Cisco Jabber for Windows does not currently support CTI connections over transport layer security (TLS). As a result, Cisco Jabber for Windows users cannot switch from using a CSF device to using a desk phone device if they belong to the Standard CTI Secure Connection user group. This limitation is documented in CSCux83786.

Using Click-To-X Feature with Contacts in Microsoft Outlook

If you use UDS as a directory source, users can only use Click-To-X capabilities, such as Click-To-Call and Click-To-IM, to contact Microsoft Outlook users if they are already in the cache file. A cache file is created for someone if they are in the users' Cisco Jabber contacts list, or have a Cisco Jabber history created by the user previously searching, IMing, or calling them, or by leaving a voice message.

Windows 10 Taskbar

On Windows 10 Build 10240, the Cisco Jabber presence and sign out taskbar actions don't work.

Supported Characters in a Cisco Jabber User ID/E-mail Address

The following characters are supported in a Cisco Jabber user ID/E-mail Address:

- Uppercase characters (A to Z)

- Lowercase characters (a to z)

- Numbers (0-9)

- Period (.)

- Hyphen (-)

- Underscore (_)

- Tilde (~)

Limitations and Restrictions for On-Premises Deployments

Adding Federated Contacts

When adding federated contacts, Cisco recommends that users add the federated contacts as company contacts (File > New > Contact), rather than as custom contacts. Adding federated contacts as custom contacts can cause intermittent presence issues. This issue is documented in CSCuz59060.

Creating and Configuring Devices for Users in Cisco Unified Communications Manager 11.0

If you are creating devices for users in Cisco Unified Communications Manager 11.0, you can now specify a key order as RSA Only, EC Only or EC Preferred, RSA Backup. However, the EC Only option is not currently supported by Cisco Jabber, and if you select it, the client will fail to connect to the server.

Multiple Resource Login

When a user signs in to multiple instances of the client at the same time, the chat feature behaves as follows in on-premises deployments (more on multiple resource login in Common Deployment Scenarios):

- Signing in on one client changes custom availability states to 'Available' on other clients.

- If you set the availability state from 'On a call' to another state while on a call, the availability state does not automatically change to 'On a call' for subsequent calls.

SIP Trunk for Phone Presence

From Release 11.5(3), you must configure a SIP trunk between Cisco Unified Communications Manager and IM and Presence Service if you want Cisco Jabber users to see phone presence. In previous releases, a SIP trunk was not required for phone presence. This limitation is documented in CSCuz85578.

Limitations and Restrictions for Cloud Deployments

Blocking Users in Enterprise Groups

Blocking users does not prevent a blocked user's status from being displayed if the blocked users are in a contact list as part of an enterprise group. For example, User A blocks User B. However, User A is in User B's contact list as part of an enterprise group. As a result, User B can view User A's availability status.

Invitees to Instant WebEx Meetings

Invitees to instant WebEx meetings must be provisioned with WebEx accounts before they can join an instant WebEx meeting. For example, User A has a WebEx account and starts an instant WebEx meeting from Cisco Jabber. Use A then invites User B, who does not have a WebEx account, to the meeting. When User B clicks on the meeting link in Cisco Jabber, an error message is displayed and the user can't join the meeting. User B must be provisioned with a WebEx account before attempting to join any instant WebEx meetings. This limitation is documented in CSCux52068.

Jabber to Jabber Calls

We recommend running Internet Explorer 10 or greater while using the Jabber to Jabber calling feature. Using this feature with previous versions of Internet Explorer or with Internet Explorer in Compatibility Mode can cause issues with Cisco Jabber client login (non-SSO setup) or Jabber to Jabber calling capability (SSO setup).

Users in Common Identity

There is a known issue with signing into Cisco Jabber for some users who have migrated to Common Identity. If users receive an Incorrect user name or password error message when entering their username and password, see the following knowledge base article Click Here

Performance and Behavior Notes

Jabber to Jabber Calls and Symantec Host IDS (HIDS)

Jabber to Jabber calls can trigger errors in Symantec HIDS.

Symantec HIDS has a rule that disables connections from internet-based servers if it receives 5 connection requests from the same internet-based server within 200 seconds. For example, 3 Jabber to Jabber calls within 200 seconds will trigger Symantec HIDS. When this happens, ongoing Jabber to Jabber calls are dropped and Jabber to Jabber calls are disabled for 600 seconds.

To avoid this scenario, you must add Cisco Jabber to the Symantec exception list. This behavior is documented in CSCuw32007.

Meeting Reminders

Cisco Jabber displays pop-up reminders for Cisco WebEx meetings only. Reminders for non-Cisco WebEx meetings are not displayed.

If the URL for a WebEx meeting is changed (for example, by URL filter software), attempts to join the meeting from the meeting reminder or from the Meetings tab fail. This behavior is documented in CSCux03658.

Removing Participants During Conference Calls

Users can only remove participants from a conference call when using the softphone(CSF) device for calls. Users can't remove participants from conference calls in desk phone control mode or using extend and connect.

Video Calls

The Start My Video button doesn't work immediately after a call connects. Users must wait approximately 6 seconds after the call starts before clicking the Start My Video button. This behavior is documented in CSCuz06415.

Caveats

Caveats describe unexpected behavior. The following sections describe how to obtain the latest information.

Bug Severity Levels

Known defects, or bugs, have a severity level that indicates the priority of the defect. These release notes include the following bug types:

- All severity level 1 or 2 bugs

- Significant severity level 3 bugs

- All customer-found bugs except severity level 6 enhancement requests

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

To search for bugs not listed here, use the Bug Search Tool.

Procedure

Step 1

To access the Bug Search Tool, go to Click Here .

Step 2

Sign in with your Cisco.com user ID and password.

Step 3

To look for information about a specific problem, enter the bug ID number in the Search for field, then press Enter. Alternatively, you can search by product and release.

Open Caveats in Release 11.6(3)

Identifier

Severity

Headline

CSCva46320

2

Jabber presence not re-connecting correctly.

CSCva54928

3

Deadlock in SIPCC when shutting down telephony.

CSCva62247

3

Jabber for Windows 11.6 does a server health check for meetings although no UC service.

CSCva67752

3

Group chat title changed to IDR_MAINVIEW_RIGHT_GROUP 2.

Resolved Caveats in Release 11.6(3)

Identifier

Severity

Headline

CSCva85148

2

CUCM calls drop after refresh of SSO token.

CSCux87284

2

Jabber does not give proper options to add federated contact from chat.

CSCva89914

2

Address LibTiff vulnerabilities in Cisco Jabber.

Open Caveats in Release 11.6(2)

Identifier

Severity

Headline

CSCuz94526

3

Jabber Windows contact import via xml file display name does not persist

CSCva02298

3

Custom Tab via MRA - J4W not sending authorization header due to cache

CSCva09037

3

AD Group users not seeing Location information of other AD Group users

CSCva22088

3

Jabber 11.6 - View >Show contact pictures does not work on group chats

CSCva32701

3

J4W-Windows 10 after close runs as a background process

Resolved Caveats in Release 11.6(2)

Identifier

Severity

Headline

CSCuz72507

2

Jabber Loses Audio After Remote IP Address Change

CSCuz78072

3

Temp presence does not work, from second search

CSCuz84097

3

Jabber crashes when placing or receiving call

CSCuz99714

3

If more than one db for address book Jabber IBM Notes integration fails

CSCuz98093

3

New location incorrectly popped when there is a delay from server

CSCva00186

3

Disable start my video while video not available

CSCuz91224

3

Jabber Windows 11.6 crashes when alt+F4 is pressed in docked window

CSCuz98410

3

J4Win Reconnecting with New IP Address Fails to Invoke TftpHelper.cpp

CSCuy41249

3

Jabber displays black contact window after P2P screen share

CSCva09318

3

Jabber showing black Meet me button after screen share

CSCva18525

3

J4W-Email address entry is not pulled for CUPC custom contacts

CSCva20093

3

Jabber InitialPhoneSelection parameter not working

CSCuz78863

3

Cyrillic letter issue when sent from Pidgin to Jabber in chat room

Open Caveats in Release 11.6(1)

Identifier

Severity

Headline

CSCuz72507

2

Jabber Loses Audio After Remote IP Address Change

CSCux71702

3

Hang JabberUtils!jabberutils:SystemUtils::isNetworkConnectionAvailable

CSCuy41249

3

Jabber displays black contact window after P2P screen share

CSCuy84721

3

Jabber to select reachable UDS server

CSCuz63521

3

Jabber cannot create custom contacts when logged into multiple devices

CSCuz78072

3

Temp presence does not work , from second search

CSCuz78863

3

Cyrillic letter issue when sent from Pidgin to Jabber in chat room

CSCuz84097

3

Jabber crashes when placing or receiving call

Resolved Caveats in Release 11.6(1)

Identifier

Severity

Headline

CSCuz60448

2

J4W: Unable to Get softPhone control

CSCuz83928

2

[J4Win] libxml2 Vulnerabilities addressed by 2.9.4

CSCuy62564

2

Evaluation of J4W for OpenSSL March 2016

CSCuz85499

3

Unnecessary resignaling of bandwidth when no bandwidth history

CSCuz70500

3

Jabber Windows freezes after switching from MRA

CSCuz52263

3

Movi to Jabber call screen share not working (J4W)

CSCuz38726

3

sending email via jabber limit

CSCuz71592

3

Jabber for window character garble under "recents"

CSCux76460

3

J4W contact card call button drop down not working

CSCuz74121

3

Jabber/Win Screen sharing do not show mouse cursor

CSCuz70550

3

Persistent Chat Show More Update Does not Render Scroll Bar to Bottom

CSCuy53831

4

Jabber drag and drop of image in same IM window causing image resend

CSCuu88928

6

J4W properties are missing from mst file

Open Caveats in Release 11.6

Identifier

Severity

Headline

CSCuz16302

2

Empty Location Data added to PEP node

CSCuw23422

3

J4W :Jabber crash in uiautomationcore

CSCux76460

3

J4W contact card call button drop down not working

CSCuy41249

3

Jabber displays black contact window after P2P screen share

CSCux71702

Hang JabberUtils!jabberutils:SystemUtils::isNetworkConnectionAvailable

CSCuy77272

3

Calendar meetings are not showing in the jabber client

CSCuy91041

3

Jabber Windows is unresponsive in VPN connection mode

CSCuz01132

3

Jabber-to-CUVA Video Freeze intermittently

CSCuz06643

3

Jabber calling fails when user moves off customers network

CSCuz06662

3

Jabber does not close ldap connections when connected to openldap

CSCuz20865

3

Cannot Send Messages When Loading Spark In Jabber Custom Tab

CSCuz21552

3

unable to hear jabber chat notification sounds in J4W 11.5.2

CSCuz24887

3

Directory group member photo download not triggered automatically

Resolved Caveats in Release 11.6

Identifier

Severity

Headline

CSCux69005

3

Crash in wcl_dll in function LoadFile

CSCux74738

3

Crash in wcl_dll UnregisterServer

CSCux80499

3

Evaluate CVE-2015-6360 for libsrtp Denial of Service (DoS)

CSCux88497

3

User unable to copy/paste from IM pane using mouse

CSCuy04669

3

J4W does not search Lotus for incoming calls

CSCuy29056

3

Jabber does not use new BFCP configs after Multiway escalation

CSCuy51657

3

Jabber Directory Lookup Inconsistent with UDS

CSCuy69674

3

Jabber Intermittent one-way audio to conference bridge

CSCuy75563

3

J4W 11.5.1 crash when call is received from SIP trunk

CSCuy88506

3

J4W intermittently does not select the primary line when calling out

CSCuy92648

3

Large entry in cache file cause client crash on start

CSCuy77069

3

Presence changed to on a call when no Call/Call ended on Jabber client

CSCuy18230

6

Cisco Jabber - Poor Video Quality Surface pro4