Release Notes for Cisco Jabber for Windows 11

Release Notes for Cisco Jabber for Windows 11.8.x

Download Options

View with Adobe Reader on a diversity of devices

View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone

View on Kindle device or Kindle app on numerous devices

Very first Published: December 05, 2016

Last Updated: July 27, 2017

Introduction

These release notes describe fresh features, requirements, limitations, and caveats for all versions of Cisco Jabber for Windows Release 11.8.x. These release notes are updated for every maintenance release but not for patches or hot fixes. Each maintenance release includes the features, requirements, limitations, and bug fixes of the previous releases unless mentioned otherwise. Before you install Cisco Jabber for Windows, we recommend that you review this document for information about issues that may affect your system.

Build Number

What’s Fresh in Release 11.8.Five

Stability Improvements

This release provides fixes for a number of known issues. See the Resolved Caveats in Release 11.8.Five section for a list of caveats motionless in this release.

What’s Fresh in Release 11.8.Four

Administrator

Fresh Configuration Key —A fresh configuration key BulkQuerySize has been added in this release. This specifies the maximum query size whenever Jabber runs a bulk query. The default query size is 50. You can decrease this value if the LDAP server does not react with the configured size.

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

Fresh LDAP Parameter—There is a fresh parameter EnableEmployeeNumber that specifies if the Employee number can be obtained from the server through a search. The default value is set to false.You can switch this to true in the configuration file if you want the Employee number to be displayed when a search is performed.

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

Resolved Caveats

This release provides fixes for a number of known issues. See the Resolved Caveats in Release 11.8.Four section for a list of caveats motionless in this release.

What’s Fresh in Release 11.8.Three

Resolved Caveats

This release provides fixes for a number of known issues. See the Resolved Caveats in Release 11.8.Trio section for a list of caveats immovable in this release.

What’s Fresh in Release 11.8.Two

Stability Improvements

The objective of this release is to resolve the caveat CSCvc89294.

What’s Fresh in Release 11.8.1

Administrator

Fresh Directory Integration Parameter—There is a fresh parameter UseLdapReferral that specifies if the client uses LDAP referrals when attempting to resolve contacts. For more information, see the Parameter Reference Guide for Cisco Jabber .

Stability Improvements

This release provides fixes for a number of known issues. See the Resolved Caveats in Release 11.8.1 section for a list of caveats immobile in this release.

What’s Fresh in Release 11.8

Cisco Directory Integration (CDI)

This release includes switches to the way LDAP is configured. Cisco Directory Integration (CDI) substituted 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 act. 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 accomplish 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 .

Talk 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 choose to different talks.

Persistent IM Notifications—IM notifications of fresh 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 substitute 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 Pictures—You can add .jpg, .jpeg, .png, and .gif pics by using haul and drop or file transfer to an IM. You can configure the pictures to be automatically accepted by users to download. You can also configure the pics to be displayed in the client without downloadeding them very first. Any .gif pictures 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 picture files automatically accepted for download. Configure the EnableInlineImages parameter with true (default) or false values to have pictures displayed in the client automatically without being downloaded very 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 very first. File transfers do not include picture files, which you can configure using AutoAcceptImages parameter.

In the Jabber-config.xml file, configure the AutoAcceptFileTransfers parameter with true or false (default) values.

The contacts phone number is not imported into Jabber, only the IM address is imported.

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 Talk Invitations—Group talk invitations have been improved to provide consistent notifications across all Jabber clients.

Custom-built 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-built status, choose from your existing presence status, or delete custom-made status messages that you already created.

Telephony

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 shows up as a regular fresh voice message with the name of the contact who sent it and the “FW:” identifier. When they play the message, your recording is played very 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. Witnessing this information helps you differentiate inbetween users who have the same name.

Accessibility

Time Stamp Removal—Users can add or eliminate 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 Practice—We’ve improved the screen reader practice for notifications during a call, whether a call or talk is in concentrate, and elements of the status tab.

Visual Refresh

Camera Self-View—When you are in a movie call but not sending movie, 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 talk without text are displayed three times larger than normal in the talk.

Administrator

Average Round Journey Time (RTT) for movie flows

Concealed Seconds for audio rivulets

Severely Concealed Seconds for audio flows


The metrics show up 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 switches 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 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.

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.

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 improvised limit bandwidth on rivulets, resync movie, avoid unnecessary congestion-based burst losses, protect packet loss, and protect low-frame and low-bit rate rivulets.

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 Ten.x or later. For audio and movie, on Cisco Unified Communications Manager 11.Five or later. For Expressway for Mobile and Remote Access deployments, Cisco Media Assure requires Cisco Expressway Release 8.8.1 or later.

Enhanced nine hundred eleven 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 nine hundred eleven is supported on Cisco Expressway for Mobile and Remote Access.

This feature is available in Utter 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 Two.0 and later.

Microsoft SharePoint—Jabber for Windows supports Microsoft SharePoint three hundred sixty five 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 Confinements for All Deployments section of the Release Notes.

Security

LDAP credentials—You can prompt users to come in 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 Switches—Users must now authenticate passphrase switches in order to prevent an unlocked machine from being used to switch a passphrase and build up control over it.

Release Notes for Cisco Jabber for Windows eleven

Release Notes for Cisco Jabber for Windows 11.8.x

Download Options

View with Adobe Reader on a multitude of devices

View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone

View on Kindle device or Kindle app on numerous devices

Very first Published: December 05, 2016

Last Updated: July 27, 2017

Introduction

These release notes describe fresh features, requirements, confinements, and caveats for all versions of Cisco Jabber for Windows Release 11.8.x. These release notes are updated for every maintenance release but not for patches or hot fixes. Each maintenance release includes the features, requirements, limitations, and bug fixes of the previous releases unless mentioned otherwise. Before you install Cisco Jabber for Windows, we recommend that you review this document for information about issues that may affect your system.

Build Number

What’s Fresh in Release 11.8.Five

Stability Improvements

This release provides fixes for a number of known issues. See the Resolved Caveats in Release 11.8.Five section for a list of caveats immovable in this release.

What’s Fresh in Release 11.8.Four

Administrator

Fresh Configuration Key —A fresh configuration key BulkQuerySize has been added in this release. This specifies the maximum query size whenever Jabber runs a bulk query. The default query size is 50. You can decrease this value if the LDAP server does not react with the configured size.

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

Fresh LDAP Parameter—There is a fresh parameter EnableEmployeeNumber that specifies if the Employee number can be obtained from the server through a search. The default value is set to false.You can switch this to true in the configuration file if you want the Employee number to be displayed when a search is performed.

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

Resolved Caveats

This release provides fixes for a number of known issues. See the Resolved Caveats in Release 11.8.Four section for a list of caveats motionless in this release.

What’s Fresh in Release 11.8.Three

Resolved Caveats

This release provides fixes for a number of known issues. See the Resolved Caveats in Release 11.8.Three section for a list of caveats immobilized in this release.

What’s Fresh in Release 11.8.Two

Stability Improvements

The objective of this release is to resolve the caveat CSCvc89294.

What’s Fresh in Release 11.8.1

Administrator

Fresh Directory Integration Parameter—There is a fresh parameter UseLdapReferral that specifies if the client uses LDAP referrals when attempting to resolve contacts. For more information, see the Parameter Reference Guide for Cisco Jabber .

Stability Improvements

This release provides fixes for a number of known issues. See the Resolved Caveats in Release 11.8.1 section for a list of caveats motionless in this release.

What’s Fresh in Release 11.8

Cisco Directory Integration (CDI)

This release includes switches to the way LDAP is configured. Cisco Directory Integration (CDI) substituted 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 act. 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 finish 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 .

Talk 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 choose to different talks.

Persistent IM Notifications—IM notifications of fresh 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 substitute 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 Photos—You can add .jpg, .jpeg, .png, and .gif photos by using haul and drop or file transfer to an IM. You can configure the pics to be automatically accepted by users to download. You can also configure the pictures to be displayed in the client without downloadeding them very first. Any .gif photos 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 picture files automatically accepted for download. Configure the EnableInlineImages parameter with true (default) or false values to have pictures displayed in the client automatically without being downloaded very 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 very first. File transfers do not include photo files, which you can configure using AutoAcceptImages parameter.

In the Jabber-config.xml file, configure the AutoAcceptFileTransfers parameter with true or false (default) values.

The contacts phone number is not imported into Jabber, only the IM address is imported.

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 Talk Invitations—Group talk invitations have been improved to provide consistent notifications across all Jabber clients.

Custom-made 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-made status, choose from your existing presence status, or delete custom-built status messages that you already created.

Telephony

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 emerges as a regular fresh voice message with the name of the contact who sent it and the “FW:” identifier. When they play the message, your recording is played very 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. Witnessing this information helps you differentiate inbetween users who have the same name.

Accessibility

Time Stamp Removal—Users can add or liquidate 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 Practice—We’ve improved the screen reader practice for notifications during a call, whether a call or talk is in concentrate, and elements of the status tab.

Visual Refresh

Camera Self-View—When you are in a movie call but not sending movie, 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 talk without text are displayed three times larger than normal in the talk.

Administrator

Average Round Tour Time (RTT) for movie flows

Concealed Seconds for audio rivulets

Severely Concealed Seconds for audio flows

The metrics emerge 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 switches 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 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.

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.

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 improvised limit bandwidth on rivulets, resync movie, avoid unnecessary congestion-based burst losses, protect packet loss, and protect low-frame and low-bit rate flows.

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 Ten.x or later. For audio and movie, on Cisco Unified Communications Manager 11.Five or later. For Expressway for Mobile and Remote Access deployments, Cisco Media Assure requires Cisco Expressway Release 8.8.1 or later.

Enhanced nine hundred eleven 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 nine hundred eleven is supported on Cisco Expressway for Mobile and Remote Access.

This feature is available in Utter 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 Two.0 and later.

Microsoft SharePoint—Jabber for Windows supports Microsoft SharePoint three hundred sixty five 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 Limitations for All Deployments section of the Release Notes.

Security

LDAP credentials—You can prompt users to come in 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 Switches—Users must now authenticate passphrase switches in order to prevent an unlocked machine from being used to switch a passphrase and build up control over it.

Related video:

Leave a Reply