What's New in Cisco Jabber for Mac 11.8

Document created by Cisco Documentation Team on Nov 30, 2016Last modified by Raj Kiran on Apr 10, 2017
Version 3Show Document
  • View in full screen mode

Cisco Directory Integration

This release includes changes to the way LDAP is configured. Cisco Directory Integration (CDI) replaced Basic and Enhanced Directory Integration (BDI and EDI). Jabber uses service discovery to automatically detect the directory server and also how to connect to it. You’ll have some optional configuration available if you want to prioritize authentication methods, or define the primary server.

If you want to customize your LDAP configuration, there is now one set of CDI parameters that apply to all clients. The CDI parameters are the same as EDI parameters, and do not require any further action. The BDI parameters are no longer supported, so if you're upgrading from a BDI-only deployment, you must make some changes to your LDAP configuration.

For more details on how CDI works, including a detailed description of how to upgrade to 11.8 from a BDI contact source and a complete list of parameters affected by moving from BDI and EDI to CDI, read LDAP Option: Cisco Directory Integration (CDI) in the Planning Guide for Cisco Jabber 11.8.

Chat and Presence

  • Inline Images—Users can add .jpg, .jpeg, .png, and .gif images by using drag and drop or file transfer to an IM. You can configure the images to be automatically accepted by users to download. You can also configure the images to be displayed in the client without needing to be downloaded first. Any .gif images that are sent automatically play and loop for the sender and receiver.

    In the Jabber-config.xml file, configure the AutoAcceptImages parameter with true (default) or false values to have image files automatically accepted for download. Configure the EnableInlineImages parameter with true (default) or false values to have images displayed in the client automatically without being downloaded first.

  • File Transfer Improvements—You can set up the client to automatically accept file transfers without the recipient needing to agree to download the file first. File transfers do not include image files, which you can configure using AutoAcceptImages parameter. In the Jabber-config.xml file, configure the AutoAcceptFileTransfers parameter with true or false (default) values.

  • Custom Status Management—Users can manage their custom statuses from the Mac status menu or in the Jabber hub window. A new window opens where users enter their status description and select the status type from Available, Away, or Do Not Disturb. Users can delete individual custom status messages in the hub window.

  • Save Chat History to Outlook folder—Users can save their chat history automatically in the Cisco Jabber Chats folder in Microsoft Outlook.

    This feature is configured using the following:

    1. Set the SaveChatHistoryToExchangeOperationMode parameter to one of the following:

      • DisabledByPolicy (default)—Users cannot save chat history to Microsoft Outlook. The option is not visible in the client.

      • EnabledByPolicy—Chats are saved to Microsoft Outlook. The option Save chat sessions to "Cisco Jabber Chats" Folder in Microsoft Outlook is visible on the client, but users cannot access it.

        With this option, you must set up authentication for the client to authenticate with the Exchange server by synching credentials.

      • DisabledByDefault—Users can save chats to Microsoft Outlook. The option Save chat sessions to "Cisco Jabber Chats" Folder in Microsoft Outlook is unchecked in the client, but users can change it.

      • EnabledByDefault—Users can save chats to Microsoft Outlook. The option Save chat sessions to "Cisco Jabber Chats" Folder in Microsoft Outlook is checked on the Outlook tab of the Options menu, but users can change it.

    2. Choose a method to authenticate users to the Exchange Server.

      1. Specify a value for the Exchange_UseCredentialsFrom parameter in the jabber-config.xml file.

        Example: <Exchange_UseCredentialsFrom>CUCM</Exchange_UseCredentialsFrom>. In this example, Cisco Unified Communications Manager is defined as the service which provides the Exchange server with credentials for authentication.

      2. Users enter their credentials in the client.

    3. Choose a method for determining which server to use.

      1. Define internal and external servers in the jabber-config.xml file, using the following parameters:

        • InternalExchangeServer
        • ExternalExchangeServer
      2. Users enter the server information in the client.

  • New Emoticons—This release includes a number of new emoticons.

  • Large Emoticons—Any emoticons that are sent in chat without text are displayed three times larger than normal in the chat.


  • Audio and Video Device Selection—There are separate Audio and Video tabs in the Audio/Video Preferences window. When a new device is plugged in, Jabber automatically uses this device. Jabber remembers a list of devices that you have attached and when you unplug a device, it switches to the next selected device that is available. The options to select system devices for Audio and Video in Jabber has been removed

  • Voice Message Forwarding—Users can right-click on a voice message in the Voice Messages tab and forward the voice message to contacts. Users can also record their own message to send with the forwarded voicemail. Users can listen to their recorded message and rerecord the message. Recipients receive the forwarded voice message in their Voice Messages tab and it appears as a new voice message with the name of the contact who sent it and the “FW:” identifier. When they play the message, the users recording is played first if one was sent, followed by the original voicemail. Private voicemails can’t be forwarded. Only one voicemail can be forwarded at a time. The recipients list is based on searches in the directory.

    To turn the feature off, in the jabber-config.xml file, configure the ForwardVoicemail parameter with true (default) or false. For more information about this parameter, see the Parameters Reference Guide for Cisco Jabber 11.8.


LDAP Credentials—Users are prompted to enter their LDAP credentials in the client in cases where the SSO directory access is not available, you have not defined another service from which to use the same credentials, or credentials have not been received from the Service Profile or jabber-config.xml file.

Accepted formats for username:

Visual Refresh

  • Camera Self-View—When you are in a video call but not sending video, your avatar is displayed instead of the self-view camera.

  • There have been visual refreshes in the following areas:

    • Connection Status window.

    • Meetings tab.

    • About window.

    • Contact card.


  • Call Management Records—When a call ends Cisco Jabber sends performance and quality information to Cisco Unified Communications Manager. Cisco Unified Communications Manager uses these metrics to populate the Cisco Unified Communications Manager Call Management Record (CMR). In this release Cisco Jabber includes the following information:

    • Average Round Trip Time (RTT) for video streams

    • Concealed Seconds for audio streams

    • Severely Concealed Seconds for audio streams

    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.

  • Enhanced 911 Prompt—Display a customizable disclaimer message or notification to users each time they log in to Jabber, which they must accept before their telephony capabilities are enabled. This prompt allows users to acknowledge the disclaimer or notification.

    In the Jabber-config.xml file, configure the E911NotificationURL parameter with a value that's a valid HTML page. Jabber navigates to that location so that the server can respond with a page containing the disclaimer message. Enhanced 911 is supported on Cisco Expressway for Mobile and Remote Access.

    This feature is available in Full UC mode or Phone Only mode. It is not available to IM Only deployments.

    Prerequisites: You must have the telephony_enabled parameter set to true.

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

  • Diagnostics Tool—The Cisco Jabber Diagnostics tool provides configuration information that Jabber uses for service discovery. To access the Cisco Jabber Diagnostics tool window, in the hub window select Ctrl + Shift + D.

  • Cisco Media Assure Support—Ensure quality of real-time media on all network types so that your meetings aren’t interrupted because of poor media quality. For minor to severe network conditions, Media Assure can temporary limit bandwidth on streams, re-sync video, avoid unnecessary congestion-based burst losses, protect packet loss, and protect low-frame and low-bit rate streams.

    Enable the Pass all unknown SDP attributes value for the SDP Transparency Profile in the device’s SIP profile in Cisco Unified Communications Manager.

    Prerequisites: Cisco Unified Communications Manager Release 10.x or later. For audio and video, on Cisco Unified Communications Manager 11.5 or later. For Expressway for Mobile and Remote Access deployments, Cisco Media Assure requires Cisco Expressway Release 8.8.1 or later.

  • Accessories Manager—The Plantronics plugin for accessories manager is included in this release. Users are able to use their devices 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 device vendor for more information.

  • Automatic Update Improvements—The client checks for updates two minutes after resuming from sleep. Users are prompted that there is an update available without having to sign out of the client.

  • Resolving Duplicate Contacts—Contacts in Jabber can come from different sources. This release includes some changes in the way Jabber compares these contacts and resolves the information to merge the contact records.

    Jabber compares the contact record fields in the following order:

    1. Jabber ID (JID)—If the records have a JID, the records are matched based on the JIDs and no further comparison is done on the mail or phone number fields.

    2. Mail—If the records have a mail field, then the records are matched based on the mail field and no further comparison is done for phone numbers.

    3. Phone Number—If the records have a phone number, the records are matched based on the phone number.

    As the records are compared and a match is found, the contact information is merged to create one contact record.

  • Cisco Unity Connection—Jabber now supports Cisco Unity Connection 9.x and later.

  • Cisco Meeting Server—Jabber supports Cisco Meeting Server 2.0 or later.