These release notes describe new features, requirements, restrictions, and caveats for all versions of Cisco Jabber for Mac Release 11.9.x. 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 caveats 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.9.3
Release 11.9.2
Release 11.9.1
Release 11.9.0

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



Release 11.9.3


Release 11.9.2

Release 11.9.1
Release 11.9


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.

You can also download the manual installation file, if your users install the client manually.


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.9


  • Fast Sign-in for Jabber—This feature enables you to now sign in to all services at the same time instead of the sequential sign-in process used earlier. Each service independently connects to its respective server and authenticates you based on cached data. This makes the sign-in process quick and dynamic. You can configure the Fast Sign in feature by using the STARTUP_AUTHENTICATION_REQUIRED parameter for all clients. For more information, see Parameter Reference Guide for Cisco Jabber 11.9.

  • O-Auth Support for SSO Jabber Users—Cisco Jabber can use OAuth to authorize the user access permission. If the user signs in with an OAuth enabled environment, then there is no need to enter the credentials every time the user signs in. For more information, see Planning Guide for Cisco Jabber 11.9.


    OAuth must be enabled for all the servers at the same time, if some of the servers are not OAuth enabled, Jabber may not function appropriately.

UI Enhancements

  • Automatic sign-in—With the introduction of fast sign-in feature in 11.9 release, the Automatic sign-in option is removed from the Jabber Sign-in screen. The user password is cached if you enable the fast sign-in feature.

  • Edit Password for Instant Messaging Account—In the earlier releases, non-SSO users didn't have the option to edit the Instant Messaging account password in Jabber. From this release onwards, non-SSO users can edit the Instant Messaging account password from Preference > Accounts, and they do not have to sign out and sign in to Jabber after editing and applying the password. They can just continue to use Jabber after applying the password.

  • Disable Self-View During an Audio Call—From this release onwards, during an audio call, the self-view window is disabled by default. You can also enable the self-view window by using the Video Toggle button available at the top-right corner.

  • Cisco Jabber and Spark Interop—Applies to Cisco Spark Interop enabled WebEx Messenger users.

    If you have Spark interop enabled, you can send and receive 1:1 messages from your contacts on Spark. The presence status of interop enabled contacts will be displayed as On Cisco Spark within Cisco Jabber.

  • Animated Emoticons—Jabber now has 18 animated emoticons. To send and receive animated emoticons, both the users must have Jabber 11.9 version installed. If either of them doesn’t have 11.9 version, then animated emoticons appear as strings in their chat window.

    You cannot send an animated emoticon along with the text. When you send an animated emoticon, it appears three times bigger than the regular size. You can also use text code to send animated emoticons. For example, to send animated laugh out loud emoticon, type (laughoutloud).

    To send an animated emoticon:
    1. In the Chat window, click emoticon icon.

    2. Click animated emoticon tab, which is next to static emoticon tab.

    3. Select your desired emoticon and click to send it to the user.

  • Additional Static Emoticons—Cisco Jabber has updated and expanded the existing set of static emoticons available for messaging.

  • Add, Chat, and Call options in Search Results—Earlier Jabber releases did not show any options when you hovered the mouse cursor over the searched contact. From this release onwards, you can view add, chat, and call options when you hover the mouse cursor over the searched contact. If the searched contact is already an added contact in your list, then you can view only call and chat options.

  • Outlook Integration—From 11.9 release onwards, you can integrate Jabber with Outlook for Mac client. Integration of Jabber with Outlook for Mac enables you to use the features, such as Click-to-Call, Click-to-Chat, and view the presence status in the Outlook for Mac client.


    • Outlook version 15.33 or later

    • User's email address and Jabber ID must be aligned


    Specifying a proxy address is not supported on the Office client for Mac.

    Jabber integration with Outlook is supported on Microsoft Exchange and Office 365 accounts. Apart from Outlook for Mac client, Jabber 11.9 release is also exposed to Session Initiation Protocol (SIP) and Instant Messaging (IM) protocols handlers in the Outlook Web Access (OWA) platform running in an Office 365 environment. Jabber integration with OWA supports only Click-to-Call and Click-to-Chat features, but not the presence status.

Operating System

Jabber is no longer supported for Apple OS X Yosemite 10.10.

What's New in Release 11.9.1

UI Enhancement

  • Alert Notification to Validate Credentials for Non-SSO Account Services—After connecting to Jabber, if the connection to any service (Instant Messaging, Phone, and Voicemail) fails, you will receive a pop-up notification to validate your credentials. The pop-up notification enables you to click Update or Cancel option. If you click Update, Jabber will open the Accounts Settings page to validate your credentials. If you click Cancel, the pop-up notification closes and you will not be able to use the service until you validate your credentials. The pop-up notification will not be shown again, but the service connection failed error message will be shown in the status bar. You can also validate your credentials by clicking the error message in the status bar.

OS Support

Jabber is now supported on the Apple OS version 10.13.

What's New in Release 11.9.2


  • New Parameter to Hide the Screen Capture Button—There is a new parameter ShowScreenCaptureButton that allows you to hide the Screen Capture button.

    For more information, see the Parameter Reference Guide for Cisco Jabber.

  • Contact Feature Behavior Change—Contact is not displayed in the Cisco Jabber contact list, if your contact isn't subscribed to the presence service. This might also occur if your contact has declined your buddy request.

Stability Improvements

This release provides fixes for several known issues. See the Resolved Caveats in Release 11.9.2 section for a list of caveats fixed in this release.

What's New in Release 11.9.3

Stability Improvements

This release provides fixes for several known issues. See the Resolved Caveats in Release 11.9.3 section for a list of caveats fixed in this release.

Software Requirements



Operating systems

  • Apple OS X Sierra 10.12 (or later)

  • Apple OS X El Capitan 10.11 (or later)

  • Apple OS X High Sierra 10.13 (or later)

On-premises servers

  • Cisco Unified Communications Manager version 9.1 (2) or later

  • Cisco Unified Communications Manager IM & Presence version 9.1 (1) or later

  • Cisco Unity Connection version 9.1 (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 8.1.1 or later

  • Cisco Meeting Server (CMS) 2.0 or later

Cloud-based servers

  • Cisco WebEx Messenger service

  • Cisco WebEx Meeting Center, minimum supported version WBS31 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



Installed RAM


Free Physical Memory


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.


Application Layer Protocol

Transport Layer Protocol






Connect to the TFTP server to download client configuration files.




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




Hostname resolution.




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.



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




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.




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




Connects to a Global Catalog server for contact searches.




LDAPS TCP Connects securely to an LDAP directory service.




LDAPS TCP Connects securely to the Global Catalog server.

Instant Messaging and Presence




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.




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


SOCKS5 Bytestream


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




MFT File transfer (On-Premises only).

Communication Manager Signaling




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




Provides Session Initiation Protocol (SIP) call signaling.


SIP over TLS


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

30000 to 39999



Far end camera control (FECC).

5070 to 6070



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

Voice or Video Media Exchange

16384 to 32766



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

33434 to 33598



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

49152 to 65535



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




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




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




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




Connects to Cisco Unity Connection for voicemail.

Cisco Webex Meetings




Connects to Cisco Webex Meetings Center for meetings.




Connects to Cisco Webex Meetings Center for meetings.




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



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.

Limitations and Restrictions


Jabber for Mac only supports SIMPLE BIND LDAP mechanism.

Save Chats to Outlook

When you use Outlook 2016, all images sent in chats are not saved in Outlook, however any emoji sent in chats are saved in Outlook.

Audio Device Setting After Upgrade

When users upgrade the client, intermittently this results in a reset of their selected audio devices. To resolve this issue, set the audio devices in the Audio/Video Preferences window. This limitation is documented in CSCva48136.


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.

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 user name or password error message when entering their username and password, see the following knowledge base article

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 supported by Cisco Jabber, and if you select it, the client fails to connect to the server.

Certificate Validation for CTI Connections

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, the Cisco Jabber client expects a response time of less than 5 seconds. Connections will fail if the response time is greater than the expected 5 seconds.

Network Disconnection When 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 for Mac does not currently support CTI connections over transport layer security (TLS). As a result, Cisco Jabber for Mac 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.

Contact Resolution for Enterprise Groups

Jabber resolves contacts in enterprise groups individually rather than all at once. As a result, when you add an enterprise group to your users' contact lists—or if they clear their local cache—they'll only see the username and domain for each person until they hover over or interact with them.

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


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.


Step 1

To access the Bug Search Tool, go to

Step 2

Sign in with your 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.9.1

There are no open caveats in this release.

Open Caveats in Release 11.9






Presence unmatched when as a temp buddy and as a normal buddy



Presence on location subscription has incorrect stanza

Resolved Caveats in Release 11.9




CSCvc17892 3 certificate not valid
CSCvc36197 3 Jabber for MAC fails to load WebEx SSO page until Jabber cache is cleared
CSCvc73807 3 Jabber for MAC causing high CPU on machine
CSCvc80320 3 Missed call badge in Jabber MAC not showing
CSCvd57064 3 Hiding offline contacts also hide unknown contacts



Localization issue after Jabber MAC IOS is upgraded to Sierra



Jabber for MAC application dial rules not working after hibernation



Jabber for MAC will not reconnect meeting after error code 20



Jabber for MAC 11.8.1 becomes unresponsive after viewing and exiting Recents tab w/ large call history



Jabber crashes when receiving a screenshot



Only a single ring tone is heard when calling to an extension with SNR from Jabber Soft Phone

Resolved Caveats in Release 11.9.1




CSCvf74181 1 Jabber for Mac unbind to OpenLDAP but search queries are not cleaned.
CSCvf71824 2 Jabber MRA not able to register phone services.
CSCvf80097 3 Jabber for Mac does not show complete timestamp in the call history.
CSCvf74906 3 Jabber unexpectedly exits when meeting site window is closed manually.

Resolved Caveats in Release 11.9.2




CSCvg39932 2 Jabber for MAC unable to add offline contacts to conference, contacts are added but immediately removed.
CSCvg83957 2 Jabber for MAC Softphone Service will not failover when Primary Node is down.
CSCvg58640 3 Jabber crashed in WinHttpGetIEProxyConfigForCurrentUser.
CSCvg84372 3 Jabber Mac 11.9 Meet Now not sending correct Attendee Name.
CSCvg30629 3 Jabber calls via MRA drops after 30 seconds.
CSCvg19215 3 Jabber MAC 11.9 SSO not working.
CSCvg48250 3 Phone service cannot connect (cprBind failed: errno = 46).
CSCvg30963 3 Jabber for MAC not connecting to Phone services over VPN when MAC is resumed after sleep operation.
CSCvg30949 3 Jabber for MAC not connecting to Phone services when moving from Corporate Wi-Fi to VPN.
CSCvg01731 3 Jabber for MAC does not display the Call option when hovering over a searched contact.
CSCvg21042 3 Jabber for MAC 11.9 does not show the presence bubble when IM service shows unavailable.
CSCvg40289 3 Jabber MAC 11.9.1 loads Custom Tabs (pre-load Yes for Popup) multiple times on subsequent logins.
CSCvg65457 3 Jaber MAC 11.9 not saving to Outlook.

Resolved Caveats in Release 11.9.3






Cisco Jabber incorrectly handles PAC Script on macOS High Sierra 10.13.



Cisco Jabber for Mac 11.9 does not send media over MRA after VPN connection is established.

What's New



Open Caveats

Resolved Caveats