What's New in Cisco Jabber for Mac 11.7

Document created by Cisco Documentation Team on Jul 28, 2016Last modified by Sheelagh O Leary on Nov 10, 2016
Version 3Show Document
  • View in full screen mode

Chat and Presence

  • Sort Contacts by Status—You can order your contacts by presence status or contact name. Select View > Sort Contacts by and choose Name or Status.

  • Search Results Menu Option—When you search for a contact in the hub window, the search results show a menu where you can easily select an action to interact with that contact.

  • Contact Search Update—Applies to On-Premises deployments only. You can search for contacts using all or some letters in a first name, for example, McKenzie,A matches all contacts with the last name McKenzie and all first names that begin with A. This search works for BDI, EDI, or UDS contact sources.

    For the UDS contact source, you can also search for incomplete first and last names. For example, searching for McKen,A finds contacts who have a last name that start with McKen and first names that start with A.

    Locales that switch the first name and last name are also supported.

    When the search criteria includes a comma (,) any values added for the PredictiveSearchFilter, BDIPredictiveSearchFilter and BDIUseANR parameters are ignored.

  • Contact Card on Hover—Users' contact card is displayed when you hover over the contact in your Contact list. This feature is enabled by default and configured by the ContactCardonHover parameter.

  • Multiple Device Messaging (On-Premises Deployments)—Users who are signed into multiple devices can see all sent and received IMs on each device. 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. This feature is supported on Cisco Unified Communications Manager IM and Presence service 11.5 and later.

    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

  • Group Chat Improvements—A number of improvements have been made to the group chat experience:

    • Group Chat for Enterprise Groups—When you hover over a group name for an enterprise group on the Contacts tab, they can start a group chat with all of the available participants in the enterprise group.

    • Alert When Available for Groups—You can right-click on any group header and select Alert When Available. They are notified as each member of the group becomes available.

    • Automatically Join a Group Chat—You can set to automatically join group chats without accepting an invitation. This option is set in the Chat Preferences window.

    • Start a Group Chat—When you hover over a group name on the Contacts tab, a group chat button is displayed. Select the button to start a group chat with all of the available participants in the group. You can select multiple contacts from the Contacts or Chats tabs and the group chat button is displayed.

    • Protocol Handler—You can use the ciscoimgroup protocol handler to create group chats in the client.

    • Start a New Chat in Chats Tab—Select the new chats button in the Chats tab. You can add participants and a subject line.

  • New Emoticons—There are ten new emoticons in this release.


  • Call Controls in Menu Bar—This release includes call controls for calls. During an active call, you can choose Mute Audio or End Call.

  • Call Management Records to Cisco Unified Communications Manager—When a call ends Cisco Jabber sends performance and quality information to Cisco Unified Communications Manager similar to Cisco IP desk phones.

    The following information is sent for both audio and video calls:

    • Number of packets sent and received.

    • Number of octets sent and received.

    • Number of packets lost.

    • Average jitter.

    The client also sends the following video-specific information:

    • Codec

    • Resolution

    • Framerate

    The metrics appear in the Cisco Unified Communications Manager CMR record output in plain text format. This data can be read directly or consumed by a telemetry or analytics application.

    For more information about configuring Cisco Unified Communications Manager CMR records, see the Call Management Records chapter of the Call Detail Records Administration Guide for your release of Cisco Unified Communications Manager.

  • Ring on All Devices—For incoming calls and alerts, configure the sound to play on all devices. This option is set in the Audio/Video Preferences window.

  • Accessories Manager—Accessories Manager is a component that provides Unified Communication control APIs to accessory device vendors. Third-party vendors write plugins that are loaded by the application. Third-party devices can use these APIs to perform tasks such as mute audio, answer calls, and end calls from the device. Standard headsets can be connected with speaker and microphone support. Only specific devices interact with Accessories Manager for call control. Please contact your devices vendor for more information. Desk phones are not supported.

    Supported third party vendors:

    • Logitech

    • Sennheiser

    • Jabra

    Accessories manager functionality is enabled by default and configured using the EnableAccessoriesManager parameter. You can disable specific Accessories Manager plugins from third party vendors using the BlockAccessoriesManager parameter.

  • Audio Device Selection from the Hub Window—In the Phone control drop-down menu on the hub window, the Use my Computer for Calls option lists the audio devices that are currently in use. Different icons are used to distinguish between speaker devices, microphone devices, and headsets. If two audio devices are being used (one for speaker and one for microphone), then both are listed. Select Audio/Video Preferences to open the Audio/Video Preferences window, where you can select alternate speaker and microphone devices.

  • Control Incoming Call Notifications—You can specify if notifications are shown for all incoming calls. Using the ShowCallAlerts parameter you can set the default for your users. This feature is enabled by default and a notification is shown for all incoming calls. When this parameter is set to false, you can answer calls on your desk phone or another connected device.

  • Do Not Disturb—You can choose whether you want to see incoming call alerts and hear ringtones when your presence is in Do Not Disturb or a custom Do Not Disturb presence. You select these options in the Preferences window.

  • Conference Call Improvements—A number of improvements have been made to the conference call experience:

    • Start a Conference Call From the Contacts Group Header or From Multiple Contact Selection—When you hover over a group name on the Contacts tab and you have selected Use my conference service in the Meetings Preferences window, a call button is displayed. Select the call button to start a conference call with all of the available participants in the group. Similarly, if you select multiple contacts from the Contacts or Recents tabs, the call button is displayed when you hover over any of the selected contacts.

    • Suggested Participant List for Conference Calls—When you are selecting participants to join in a conference call, a list of recent contacts is displayed.

    • Conference Calls for Enterprise Groups—When you hover over a group name for an enterprise group on the Contacts tab, a call button is displayed. You can click this button to start a conference call with all of the available participants in the enterprise group.

Visual Refresh

There has been a visual refresh in the following areas:

  • Contact card

  • Group chats for Enterprise Groups

  • Conferencing icons

  • The number of participants in a group chat is displayed in the invite.

  • Chat themes and messaging styles have been redesigned.

  • Notifications Preferences refresh—The choices for notifications and sounds have been redesigned to align with the Cisco Jabber for Windows client. You can choose to receive notifications for chats, incoming calls, or when your presence is set as Do Not Disturb.

  • Hub window

  • Conversation window and toolbar

  • Call control strip

  • Call, chat and add contact buttons

  • Sign-in screens


Improved Tabbing for Input Fields—You can tab to input fields and use the tab to move between fields. To use this feature select System Preferences > Keyboard > Shortcuts and in the Full Keyboard Access area select All controls.


  • UDS Directory Authentication—Cisco Jabber supports authenticated directory queries when searching for contacts. The authentication is configured on Cisco Unified Communications Manager release 11.5 or later.

  • Installer for Cisco Jabber for Mac—This release includes an installer for the Cisco Jabber for Mac client. The installer adds the new version of the client into the Applications folder on your Mac, overwriting any existing version. For further information, see the Installer for Cisco Jabber for Mac section of the Deployment guides.


    You need an administrator password to install Cisco Jabber for Mac using the installer.

  • Secure LDAP Password—With this release, a more secure way to configure common account LDAP credentials is to reuse the existing credentials that Jabber uses when connecting to other services, such as Cisco Unified Communications Manager. Jabber no longer supports common account LDAP credentials that are configured in the device profile. Instead, LDAP credentials can be configured in the Cisco Unified Communications Manager service profile or in the jabber-config.xml file using the directory integration parameters.

    For more information about configuring LDAP authentication, see the section on Authentication Options in the On-Premises Deployment for Cisco Jabber.

    We recommend that you use the Service Profile to configure LDAP authentication. Otherwise, you can use the jabber-config.xml using the LDAP_UseCredentialsFrom and LDAPUserDomain parameters, or configure anonymous binding with the UseAnonymousBinding parameter.

    For information about the new LDAP_UseCredentialsFrom, LdapUserDomain, and UseAnonymousBinding parameters, see the Parameters Reference Guide.

    Configuring LDAP authentication in both the Service Profile and the jabber-config.xml is not supported. If you do configure using both, then they must use the same credentials.

  • Next Generation Encryption—This release supports the following next generation encryption:

    • TLS 1.2 and Next Generation Encryption RSA Ciphers can be enforced on all Cisco Jabber interfaces. This change allows Cisco Jabber to comply with US Federal requirements.

    • SHA-2 hashing for digital signatures is now supported.

    • In addition to SHA-1, SHA-2 hashing in CAPF responses to Cisco Unified Communications Manager is now supported.

    • Cisco Jabber supports 3072 and 4096-bit RSA key lengths.

    For more information on Next Generation Encryption, see see http://www.cisco.com/c/en/us/about/security-center/next-generation-cryptography.html

  • Persistent Chat HA Support—High availability is supported for the persistent chat feature. During the failover window, users may be prompted that they can't send messages. When the node has failed over, users automatically rejoin the chat room and can send messages again.

  • Self-care Portal Show or Hide Configuration—You can configure if the Self-Care portal tab is available. This is configured using the ShowSelfCarePortal parameter and the tab is available by default.

  • Supported Operating Systems—Cisco Jabber for Mac is only supported on the following operating systems:

    • Apple OS X El Capitan 10.11 (or later)

    • Apple OS X Yosemite 10.10 (or later)

  • Voicemail Failover—When the primary server becomes unavailable or unreachable, if a secondary voicemail server is configured, then the clients automatically failover to the secondary voicemail server.