What's New in Cisco Jabber for Windows 11.7

Document created by Cisco Documentation Team on Aug 3, 2016Last modified by Shona O'Flaherty on Oct 28, 2016
Version 2Show Document
  • View in full screen mode

Chat and Presence

  • Display Names for Contacts—Cisco Unified Communications Manager Release 11.5 now supports the displayName attribute for UDS contact searches. Cisco Jabber tries to match against the first name, last name, and display name for contact searches. Users are identified in Jabber contact lists and searches by their display name if one is configured for them in the End User Configuration window in Cisco Unified CM Administration. If no display name is set up for a Jabber user, then the first name and last name are used in contact lists and searches.

  • Contact Search Update—On-premises deployments only. Users can now 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 the first letters of first and last names. For example, searching for McKen, A finds contacts who have last names that start with McKen, and first names that start with A.

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


    Note


    When users enter a comma (,) in their searches, then any values configured for the PredictiveSearchFilter, BDIPredictiveSearchFilter, and BDIUseANR parameters are ignored.


  • Change Presence from System Tray—You can now change your Jabber presence from the Windows system tray.

  • Multiple Device Messaging (On-Premises Deployments)—Requires Cisco Unified Communications Manager IM and Presence 11.5. With this release, multiple device messaging is supported for on-premises deployments. In release 11.5, multiple device messaging was made available for cloud deployments.

    Users who are signed into multiple devices can 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 devices where you are signed in. 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.

    • If AES encryption is required, then you can't enable Multiple device messaging.

  • Chats Tab—A new Chats tab has been added to the Hub window under the Contacts tab. This tab shows all recent and unread one-to-one conversations. Chat records are listed by most recent conversation, and are not saved between sessions. From the record, you can see your contact's availablity and can right-click to interact with them. You can select multiple chat records then right-click to intereact with the group. Jabber displays up to 30 chat records. Chat records for group chats are currently not supported.

    The Chats tab is available by default. You can hide the Chats tab by setting the Recent_Chats_Enabled parameter to False.

  • Alert When Available on Chats and Recents Tabs—Now you can also right-click on a contact in the Chats or Recents tabs to have Jabber notify you when your contact is available by selecting Alert when available.

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

  • Group Chat Improvements:

    • Automatically accept and join—In the Options menu, the option to display alerts for group chat invites has moved from the Sounds and Alerts tab to the Chats tab. It is now called Automatically accept and join group chats, and is on by default. Deselect this option to receive notifications before joining a group chat.

    • Start a group chat—When you hover over a group name on the Contacts tab, a Chat icon is displayed that starts a group chat. Select this button to start a group chat with all of the available participants in the group. You can also use the group chat button when you select multiple contacts at once and hover over their names.

    • Recent Contacts List—On the Contacts or Chats tabs, when you select multiple contacts and select the group chat icon, in the Start Group Chat window that opens, your recent contacts are listed for you to choose from. A maximum of 20 recent contacts is displayed. The recent contacts list is cleared whenever you sign out of Jabber.

    • Add Participants—Now when you drag and drop a contact name from the hub window into a group chat or participants list, the Add Participants window opens. In previous releases, this action created a mention for that contact. You can also drag and drop a contact name into a one-to-one chat to open the Start Group Chat window. Drag and drop only works from the Contacts tab in the hub window.

    • Group chat for Enterprise Groups—You can start a group chat with all of the available people in an enterprise group by hovering over the group name on the Contacts tab.

Telephony

  • URI Dialing with DTMF—Users can now start calls by entering a SIP URI followed by DTMF codes. For example, to join a meeting with an access code of 1234, users can enter mymeeting@cisco.com,1234#.

  • Jabber Calls from IMs—Cloud deployments only. Users can now click phone numbers in a chat window and start a Jabber call. Phone numbers are identified as being four or more digits long. If the phone number is prefixed by +, it must have at least 11 digits to be recognized as a phone number and converted to a clickable link. When users click the phone number, a window opens that asks them to confirm calling the number.

  • Audio Device Selection from the Hub Window—In the Phone Controls drop-down menu on the Hub window, the option to Use my computer for calls now lists the audio device that is currently in use. 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 Options to select alternate speaker and microphone devices. This feature is available for IM‐only and Full UC deployments.

  • Conference Call Improvements:

    • 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, a call button is displayed. You can click this 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.

    • 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 Eenterprise Group.

  • Call Management Records to Cisco Unified Communications Manager—Cisco Jabber sends end-of-call performance and quality information to Cisco Unified Communications Manager, similar to Cisco IP desk phones. Cisco Unified Communications Manager uses these metrics to populate the Cisco Unified Communications Manager Call Management Record (CMR). With this release, Jabber sends the following information for both audio and video calls:

    • Number of packets send and received

    • Number of octets sent and received

    • Number of packets lost

    • Average jitter

    The metrics appear in the Cisco Unified Communications Manager CMR record in plain text format. This data can be read directly or used 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.

  • Desk Phone Video Configuration—The Cisco Media Services Interface has been replaced with the Jabber Desk Phone Video Services Interface. The user experience and application behavior has not changed. The Jabber Desk Phone Video Services Interface can be downloaded from Cisco.com. During installation, users are prompted to allow installation of a driver with a Cisco certificate. Users must allow the installation of this driver in order to install the Jabber Desk Phone Video Services Interface. For more information about configuring desk phone video, see the Deployment Guide.

  • Audio Ducking—Cisco Jabber for Windows now supports audio ducking, which automatically reduces or mutes the volume of background audio streams when you make or receive a call. You can set your preference in your compuater's Control Panel, in the Sound settings, under the Communications tab.

Accessibility

  • Audio Sliders—You can change the settings on your audio volume silders more quickly with new keystrokes. From the Audio tab of the Options menu, you can tab to the volume settings, and use the Pageup and PageDown keys to increase and decrease volume by 10%, or use the Home and End keys to move silder to 0% and 100%.

    Visually impaired users get notifications of all changes to the audio sliders through JAWS screen reader.

  • Keypad Accessibility during Calls—When you are in a call, you can now access the keypad as follows:
    • When the keypad button is in focus, press the Space key to open the keypad.

    • Use the arrow keys to navigate around the keypad.

    • Press the Space or Enter keys to make a selection.

    • Press the Esc key to close the keypad.

Visual Refresh

  • UI Improvements—The appearance of Jabber has been improved. You'll see some changes in the sign in and sign out windows, the hub window, and other UI elements like the call and chat icons.

Administrator

  • DPI Awareness Per Monitor—For users who have Windows 8.1 or Windows 10 and have more than one monitor, Jabber can differentiate between different DPI settings per monitor and adjust its DPI settings accordingly.

  • Persistent Chat High Availability —There is now high availability support for the persistent chat feature if the primary server becomes unavailable or unreachable. If failover occurs, users may get a message that they can't send messages. When the node has failed over, users automatically rejoin the chat room and can send messages again.

  • Voicemail High Availability—There is now high availablity support for voicemail if the primary server becomes unavilable or unreachable. Configure voicemail failover using the VoicemailBackup1Server and VoicemailBackup2Server parameters. For more information about these parameters, see the Parameters Reference Guide.

  • Self Care Portal—You can now show or hide the Self Care Portal tab in the Options menu by using a new parameter called ShowSelfCarePortal. This tab is displayed by default. For more information about this parameter, see the Parameters Reference Guide.

  • Support for Jabber on Citrix XenApp Published Application —You can use Cisco Jabber for Windows 11.7 when it is hosted on a Citrix server and presented to the user as a published application. Virtualization Experience Media Edition is not supported, which means softphone telephony is not available in this feature. Instant messaging, presence and deskphone control are all available to users, with the following exceptions:

    • Sending screen captures

    • Sending and receiving files

    • RDP screen sharing

    • Starting a conversation from Outlook if Outlook is not on the same publishing server as the client and browser.

    • Saving a PRT file

  • Jabber Updates Over Expressway for Mobile and Remote Access —You can configure Jabber to allow automatic updates while connected to the corporate network over the Expressway for Mobile and Remote Access. Add the AllowUpdatesViaExpressway value to the XML file that you use for automatic updates.

    For more information on this feature, see Configure Automatic Updates for Windows in the On-Premises Deployment for Cisco Jabber.

Security

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

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

  • Next Generation Encryption—Release 11.7 offers the following support for 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. This change allows Cisco Jabber to comply with US Federal requirements for endpoint registration on a FedRAMP-compliant cloud.

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

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




Attachments

    Outcomes