What's New in Cisco Jabber for Windows 11.8.0

Document created by Cisco Documentation Team on Nov 28, 2016Last modified by Raj Kiran on Dec 5, 2016
Version 2Show Document
  • View in full screen mode

Cisco Directory Integration (CDI)

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 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 update 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

  • Message Bubbles—Chats now include the option to display conversations using message bubbles. The default style is left/right aligned message bubbles, but you can also select left-aligned bubbles and minimal style in the Options > Instant Message Styles menu. You can apply whichever style you prefer to different chats.

  • Persistent IM Notifications—IM notifications of new messages do not fade and stay on the screen until you dismiss them. Up to six notifications are stacked above each other at the side of the screen, where newer notifications replace the oldest. If you enable it, then users have the option to turn it off in the Options > Notifications menu of their client.

    In the jabber-config.xml file, configure the PersistIMNotifications parameter with a value of true or false (default). To enable the feature when installing Jabber, set the PERSIST_IM_NOTIFICATIONS installation argument to true.

    For more information on configuring this feature, see the Parameters Reference Guide for Cisco Jabber.

  • Inline Images—You 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 downloadeding them 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.

  • Import Contacts—In the Settings menu, under File > Import Contacts, you can import contact details from Gmail, Outlook, and IBM Notes. Contact details can be imported in .vcf, .csv,or .xml format. The limit to the file size of imported contacts is 80 KB (about 500 contacts).

  • Taskbar IM Notifications—A notification is displayed on top of your Jabber icon on the task bar indicating the number of unread messages you have waiting.

  • Align Group Chat Invitations—Group chat invitations have been improved to provide consistent notifications across all Jabber clients.

  • Custom Status Management—You can now fully manage your Jabber presence from the hub window or your system tray. With one click, you can create a custom status, choose from your existing presence status, or delete custom status messages that you already created.


  • Voice Message Forwarding—You can now right-click on a voice message in the Voice Messages tab and choose to forward the voice message to one or more of your contacts. You can also record your own message to send along with the forwarded voicemail. You can listen to your recorded message and rerecord your message if you want. Recipients receive the forwarded voice message into their Voice Messages tab and it appears as a regular new voice message with the name of the contact who sent it and the “FW:” identifier. When they play the message, your recording is played first if you sent one, 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 off the feature, in the Jabber-config.xml file, configure the ForwardVoicemail parameter with true or false. This parameter is true by default. To disable the feature when installing Jabber, set the FORWARD_VOICEMAIL installation argument to false. For more information about this parameter, see the Parameters Reference Guide.

  • Disable Phone Services—You can turn off your phone in the device selection menu from the Hub window by choosing Disable Phone Services. To turn your phone back on, select the option to use your computer or desk phone for calls. You can’t turn off your phone when you run Jabber in a virtual environment.

  • Hunt Group in Recents—If you make a call to a hunt group, then the hunt group name is displayed as part of the call records on your Recents tab.

  • Display User Details—Users’ phone numbers and display names are shown when you search for users to forward voice messages to. Seeing this information helps you differentiate between users who have the same name.


  • Time Stamp Removal—Users can add or remove individual time stamps from messages. Users can select Ctrl+Shift+B to toggle on and off whether JAWS calls out time stamp information on IMs.

  • Accessibility Improvements—We've improved Jabber for speech response, icon recognition, navigation, and error message detection.

  • Screen Reader Experience—We've improved the screen reader experience for notifications during a call, whether a call or chat is in focus, and elements of the status tab.

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.

  • Improved @mentions—When you hover over mentioned users, their contact details are displayed.

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


  • 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.
  • Contact Resolution Improvements —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. To view the Contact Resolution data, in the hub window, select Ctrl+ Shift+C.

    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 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, resync 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.

  • Enhanced 911 Prompt—Display a customizable disclaimer message or notification to users each time they sign in to Jabber, which they must acknowledge before they can proceed.

    In the Jabber-config.xml file, configure the E911NotificationURL parameter with a value that's a valid HTML page. 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 mode deployments.

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

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

  • Citrix—Jabber for Windows now supports Citrix XenDesktop 7.9 and 7.8, and Citrix XenApp 7.9, 7.8, and 7.6 published apps and desktop.

  • Cisco Meeting Server (CMS)—Jabber now supports Cisco Meeting Server 2.0 and later.

  • Microsoft SharePoint—Jabber for Windows supports Microsoft SharePoint 365 2016. Presence integration is not supported unless users switch to the classic mode in SharePoint. For more details on this limitation, see the Limitations and Restrictions for All Deployments section of the Release Notes.


  • LDAP credentials—You can prompt users to enter their LDAP credentials on the Accounts tab of the Options menu in Jabber.

    This option is not available when:

    • SSO directory access is available

    • You have already defined users' credentials in the Service Profile or in the jabber-config.xml file.

  • Authenticate Passphrase Changes—Users must now authenticate passphrase changes in order to prevent an unlocked machine from being used to change a passphrase and gain control over it.