Contents

• Introduction
• Build Number
• What's New in Release 11.5.2
• What's New in Release 11.5.1
• What's New in Release 11.5
• Requirements
• Software Requirements
• Hardware Requirements
• Network Requirements
• Limitations and Restrictions
• Caveats
• Bug Severity Levels
• Search for Bugs
• Open Caveats in Release 11.5.2
• Resolved Caveats in Release 11.5.2
• Closed Caveats in Release 11.5.2
• Open Caveats 11.5.1
• Resolved Caveats in Release 11.5.1
• Closed Caveats 11.5.1
• Open Caveats in Release 11.5
• Resolved Caveats in Release 11.5

First Published: December 22, 2015

Last Updated: April 27, 2016

Introduction

---

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

Build Number

Release 11.5.2

The build number for this release is:

11.5.2.235632

The DownloadURL file element in the XML file for automatic updates is:

Cisco-Jabber-Mac-11.5.2.235632-65013293-MC0CFQCNdOQQYr8YiptMPPJ2QV5uZRJiWgIUA6YDfyzrPH2nSuK+AzCgeliKBog!.zip

The DownloadURL file element refers to the Cisco Jabber for Mac installation file. The installation file on the update server must be renamed to match this DownloadURL file element name.

Release 11.5.1

The build number for this release is:

11.5.1.229678

The DownloadURL file element in the XML file for automatic updates is:

Cisco-Jabber-Mac-11.5.1.229678-65470028-MCwCFGr+mkB2Ip+wRp+x7AiWqNAqHyv_AhQPSs5BLBdNkI92R6MqEk1HroGCoA!!.zip

The DownloadURL file element refers to the Cisco Jabber for Mac installation file. The installation file on the update server must be renamed to match this DownloadURL file element name.

Release 11.5

The build number for this release is:

11.5.0.226858

The DownloadURL file element in the XML file for automatic updates is:

Cisco-Jabber-Mac-11.5.0.226858-69060552-MC0CFCGHZHQbG02opg8Jz7EMVr92YxNJAhUAhrgr6ODHhTkOo8y6WYkoM_rUxWo!.zip

The DownloadURL file element refers to the Cisco Jabber for Mac installation file. The installation file on the update server must be renamed to match this DownloadURL file element name.

Note	To ensure the DSA signature succeeds, configure Web servers to escape special characters. For example, on Microsoft IIS the option is: Allow double spacing.

What's New in Release 11.5.2

For information on the caveats in this release, see the Resolved Caveats in Release 11.5.2.

What's New in Release 11.5.1

Resolved Caveats

This release includes a number of resolved caveats. For more information, see the Resolved Caveats in Release 11.5.1

What's New in Release 11.5

Calling Features

• Hunt Group—Hunt Groups enable incoming calls to be directed to a group of users. The call route is based on several factors, including first available, longest Idle, broadcast hunting and circular hunting. You can use Cisco Jabber and deskphones to answer hunt group calls.

  A hunt group works with route filters and hunt lists to direct calls to specific devices. If a phone or device is ringing and not being answered, then another available number is searched for until the call is answered.

  A hunt list contains a set of line groups in a specific order. A single line group can appear in multiple hunt lists. A line group comprises a group of directory numbers in a specific order. The order controls the progress of the search for available directory numbers for incoming calls.

  Configured using the EnableHuntGroup and the PreventDeclineOnHuntCall parameter. For more information about these parameters, see the Parameters Reference Guide for Cisco Jabber 11.5.

• Call Pickup—Call Pickup allows users to pick up incoming calls from their own group. Group Call Pickup and Directed Call Pickup allow users to pick up incoming calls to another group or individual, respectively. You can use Cisco Jabber and deskphones to answer call pickup calls.

  Directory numbers are assigned to call pickup groups and Cisco Unified Communications Manager automatically dials the appropriate call pickup group number. Users select Pickup to answer the call.

  There are four kinds of call pickup that allow users to ensure that incoming phone calls are not missed.

  • Call pickup: Allows users to pick up incoming calls from their own group. Configured using the EnableCallPickup parameter.

  • Group call pickup: Allows users to pick up incoming calls from another group. Configured using EnableGroupCallPickup parameter.

  • Other group pickup: Allows users to pick up incoming calls from a group that is associated with their group. You cannot use this option with the hunt group feature. Configured using the EnableOtherGroupPickup parameter.

  • Directed call pickup: Allows users to pick up an incoming call on a directory number. You cannot use this option with the hunt group feature.

  For more information about the parameters, see the Parameters Reference Guide for Cisco Jabber 11.5.

• Personal Ringtone—Users can select a ringtone for incoming calls from a menu of distinctive ringtones for their client in the Preferences window.

• Call with Edit—A Call with Edit menu option is available from the main window by right-clicking over a contact's name. When users select a number from this menu option, the call number is copied into the Search or Call field. Users can edit the number before making the call.

  No configuration is required to enable this feature.

• Extend and Connect—Users can use the client to do the following:

  • Make and receive calls on a non-Cisco IP Phone in the office.

  • Control a non-Cisco IP Phone in the office, such as hold or resume

  • Control a home or hotel phone when connecting with Expressway for Mobile and Remote Access

Chat and Presence Features

• Restore Chats on Sign In—When users sign into the client, the chat sessions that were open when the user signed out of the client are restored. This feature applies to 1:1 chats only and is configured using the RestoreChatOnLogin parameter. For more information about this parameter, see the Parameters Reference Guide for Cisco Jabber 11.5.

• Multiple Device Messaging (Cloud)—Users who are signed into multiple devices can now see all sent and received IMs on each device regardless of which device is active. Notifications are synchronized; if an IM is read on one device, it shows as read on other signed-in devices. This feature is enabled by default, but can be disabled with the Disable_MultiDevice_Message parameter. The following limitations apply:

  • Clients must be signed-in. Signed-out clients do not display sent or received IMs or notifications.

  • File transfer between multiple devices is not supported—Files are available only on the active devices that sent or received the file.

  • Group chat is not supported.

  • Multiple device messaging cannot be enabled if AES encryption is required.

  • Applies to cloud deployments only.

  For more information about the Disable_MultiDevice_Message parameter, see the Parameters Reference Guide for Cisco Jabber 11.5.

• Broadcast Messages with Rich Text and Emoticons—Broadcast messages allow users to send a single message to multiple contacts. Users can select multiple contacts or a group of contacts from their contact list and send a broadcast message to all of them at once. Recipients receive broadcast messages in the same way as normal 1:1 chats. In cloud and hybrid deployments, offline contacts do not receive broadcast messages.

  No configuration is required to enable this feature.

• Alert when Available—Users can set the client to notify them when a contact becomes available. Right-click over the user's name to select the Alert When Available option. A message notification is displayed the first time the user becomes available.

  No configuration is required to enable this feature.

• Locations—Create, define, and display locations in the client for your contacts to see. Configure the Locations feature using the Location_Enabled, Location_Mode, and LOCATION_MATCHING_MODE parameters. For more information about these parameters, see the Parameters Reference Guide for Cisco Jabber 11.5. Users can define their settings in the Preferences window.

• Persistent Chat Rooms

  Persistent Chat Rooms are applicable to on-premises deployments only.

  • Administration and Management—Administrators can now create and delete rooms, manage membership, and moderate rooms. Define room moderators who can create or remove rooms, add or remove members, and define room types and descriptions.

  • Room discovery and Enrolment—View joined rooms, browse through a list of available rooms, join open rooms, and request membership of members-only rooms.

• Logout Inactivity Timer—This timer allows you to automatically log users out of the client after a specified amount of time of inactivity.

  Inactivity on the desktop clients includes:

  • No keyboard or mouse activity.

  • No user interaction on connected accessories for making and answering calls.

  Configure this feature using the ForceLogoutTimerDesktop parameter. If the parameter is not set, the client will not automatically log out. For more information about this parameter, see the Parameters Reference Guide for Cisco Jabber 11.5.

Configuration

• Jabber Configuration XML File in Cisco WebEx Messenger Administration Tool—In the Cisco WebEx Messenger Administration tool you can import a jabber-config.xml file. You can apply separate configuration files for groups in the Cisco WebEx Messenger Administration Tool. The client downloads this file when it successfully connects to Cisco WebEx Messenger and the client applies these configurations.

  The client will use the following order for configuration settings:

  1. Settings in Cisco WebEx Messenger Administration Tool.

  2. Settings in jabber-config.xml file from Cisco WebEx Messenger Administration Tool.

     Note	Group configuration file settings take priority over the configuration file in Cisco WebEx Messenger Administration Tool.

  3. Settings in jabber-config.xml file from the TFTP server.

  This feature applies to cloud deployments only.

• Custom Embedded Tabs—Custom tabs can be created in the client. The feature is configured using the AllowUserCustomTabs parameter. For more information on creating custom tabs, see the Custom Embedded Tabs section of the Features and Options Guide.

Requirements

Software Requirements

Server	Software
Operating systems	Apple OS X El Capitan 10.11 (or later) Apple OS X Yosemite 10.10 (or later) Apple OS X Mavericks 10.9 (or later)
On-premises servers	Cisco Unified Communications Manager version 9.x or later Cisco Unified Communications Manager IM & Presence version 9.x or later Cisco Unity Connection version 8.6(2) or later Cisco WebEx Meetings Server version 2.0 or later Cisco Expressway Series for Cisco Unified Communications Manager Cisco Expressway-E Version 8.1.1 or later Cisco Expressway-C Version 8.1.1 or later Cisco TelePresence Video Communication Server Cisco VCS Expressway Version 8.1.1 or later Cisco VCS Control Version 8.1.1 or later
Cloud-based servers	Cisco WebEx Messenger service Cisco WebEx Meeting Center, minimum supported versions T28 or later
Directory servers	Active Directory Domain Services for Windows Server 2012 R2 Active Directory Domain Services for Windows Server 2008 R2 Cisco Unified Communications Manager User Data Service (UDS) Cisco Jabber supports UDS with Cisco Unified Communications Manager version 9.1(2) with the COP file cmterm-cucm-uds-912-3.cop.sgn. OpenLDAP 2.4 and later

Hardware Requirements

Hardware	Requirement
Installed RAM	2 GB RAM
Free Physical Memory	1GB
Free Disk Space	300 MB
CPU Speed and Type	Intel Core 2 Duo or later processors in any of the following Apple hardware: Mac Pro MacBook Pro (including Retina Display model) MacBook MacBook Air iMac Mac Mini
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	TCP	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	UDP	Sends RTP media streams for audio or video.
	49152 to 65535	RDP	TCP	IM-only screen share. Applies to Cisco Jabber for Windows only.
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.

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.

Limitations and Restrictions

Antivirus

When the client connects to Cisco Unity Connection on a device that has antivirus software, users can have issues with voicemail connections. To resolve this issue, add the Cisco Unity Connection server information to the exceptions list for the antivirus software.

Split View

Split View on Apple OS X El Capitan is only supported on the chat window in the client.

Users in Common Identity

There is a known issue signing into Cisco Jabber for some users who have migrated to Common Identity. If users receive an Incorrect username or password error message when entering their username and password, see the following knowledge base article https:/​/​cisco-support.webex.com/​guest/​articles/​en_US/​Troubleshooting/​WBX000019555/​myr=false.

Upgrades

The following features and support are not available in this release:

• Voicemail transcripts

• Call Park

• Send to Mobile

• Forced Authorization Code or Client Matter Code

• Observer Contact List

• Group Chat History

• Compound search base

• Change Password—This is applicable to on-premise (Cisco Unified Communications Manager IM and Presence Service server IM/Availability) deployments only.

• Cisco Medianet support

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

When you create devices for users in Cisco Unified Communications Manager 11.0, you can specify a key order. The EC Only option is not supported, and if you select it, the client fails to connect to the server.

Certificate Validation for CTI Connections

In this release, Cisco Jabber uses certificate validation for CTI connections. We recommend using either Public CA or Private CA to sign certificates.

Connecting to Cisco Unified Communications Manager using a self-signed certificate, results in a certificate validation failure, to resolve this issue do one of the following:

• The user accepts the invalid Cisco Unified Communications Manager self-signed certificate on first certificate validation failure and Cisco Jabber saves this certificate to the trust store.

• Deploy the certificates using a certificate deployment management application.

Expressway for Mobile and Remote Access Deployment

For an Expressway for Mobile and Remote Access deployment, when using an online certificate status protocol (OCSP) or online certificate revocation lists (CRL) to obtain the revocation status of the certificates, Jabber expects a response time of less than 5seconds. Connections fail when the response time is greater than the expected 5 seconds.

File Transfer

Cisco Jabber 10.6 clients and Cisco Unified Communications Manager IM and Presence Service 10.5(2) server introduce file transfer compliance and policy options for file transfer and screen capture. When users interact with earlier versions of Jabber or earlier versions of the Cisco Unified Communications Manager IM and Presence service, some file transfers don't complete or revert from a managed file transfer to a peer to peer file transfer.

Network Disconnection Using Cisco Jabber on Audio or Video Call

There is a known issue in the Mac OS where network interfaces drop intermittently when DSCP is enabled.

If you encounter this issue, do the following:

1. Select Preferences > Calls > Advanced.
2. Uncheck Enable Differentiated Service for Calls.

Standard CTI Secure Connection User Group

Cisco Jabber doesn't support CTI connections over transport layer security (TLS). As a result, Cisco Jabber 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.

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 https:/​/​tools.cisco.com/​bugsearch/​search.
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.5.2

Identifier	Severity	Headline
CSCuw99634	3	Remote side see presentation continuously refresh and or go blank.
CSCux38739	3	Jabber getting hang after sleep and resume
CSCux87795	3	J4M- antivirus blocking voicemail connectivity after upgrade to 11.5

Resolved Caveats in Release 11.5.2

Identifier	Severity	Headline
CSCuy08286	1	Jabber can't start after certain crash type
CSCux41458	2	Evaluation of jabber-mac for OpenSSL December 2015 vulnerabilities
CSCux74900	2	Jabber client does not allow to enforce STARTTLS as required
CSCux44307	2	libxml2 December 2015 parsing vulnerabilities
CSCuv87845	3	J4M | both local and remote ringback heard if SIP 180 is followed by 183.
CSCux49839	4	Call window pops when is deskphone mode and show window set to never
CSCux55833	4	SSO HTTP Basic Login Dialog Doesn't Allow Copy/Paste
CSCux55722	3	CPVE crashed trying to release an object
CSCux55738	3	Offline user cannot receive invitation email

Closed Caveats in Release 11.5.2

Identifier	Severity	Headline
CSCuw88260	3	Jabber consuming high memory (two occasions)

Open Caveats 11.5.1

Identifier	Severity	Headline
CSCuw99634	3	Remote side see presentation continuously refresh and or go blank.
CSCux38739	3	Jabber getting hang after sleep and resume
CSCux87795	3	J4M- antivirus blocking voicemail connectivity after upgrade to 11.5

Resolved Caveats in Release 11.5.1

Identifier	Severity	Headline
CSCuy08286	1	Jabber can't start after certain crash type
CSCux41458	2	Evaluation of jabber-mac for OpenSSL December 2015 vulnerabilities
CSCux74900	2	Jabber client does not allow to enforce STARTTLS as required
CSCux44307	2	libxml2 December 2015 parsing vulnerabilities
CSCuv87845	3	J4M | both local and remote ringback heard if SIP 180 is followed by 183.
CSCux49839	4	Call window pops when is deskphone mode and show window set to never
CSCux55833	4	SSO HTTP Basic Login Dialog Doesn't Allow Copy/Paste
CSCux55722	3	CPVE crashed trying to release an object
CSCux55738	3	Offline user cannot receive invitation email

Closed Caveats 11.5.1

Identifier	Severity	Headline
CSCuw88260	3	Jabber consuming high memory (two occasions)

Open Caveats in Release 11.5

Identifier	Severity	Headline
CSCuv87845	3	J4M | both local and remote ringback heard if SIP 180 is followed by 183.
CSCux55722	3	CPVE crashed trying to release an object
CSCuw88260	3	Jabber consuming high memory (two occasions)
CSCuw99634	3	Remote side see presentation continuously refresh and or go blank.
CSCux38739	3	Jabber getting hang after sleep and resume
CSCux55738	3	Offline user cannot receive invitation email

Resolved Caveats in Release 11.5

Identifier	Severity	Headline
CSCuv95758	3	Change service profile shows error
CSCuw07681	2	Jabber for MAC sends incorrect C-Type in SOAP when logging into IMP

Copyright © 2016, Cisco Systems, Inc. All rights reserved.