The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
These release notes describe new features, requirements, restrictions, and caveats for all versions of Cisco Jabber for Windows Release 10.6.x. These release notes are updated for every maintenance release but not for patches or hot fixes. Note that each maintenance release includes the features, requirements, restrictions, 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.
The build number for this release is 10.5.2.45439.
The following documents are available for Cisco Jabber for Windows.
Provide administrators with a summary of information about the release, which include feature enhancements, requirements, limitations and restrictions of the software, and caveats overview.
This Licensing Information document provides information on the open source libraries used by the application.
Instructions to help navigate end users around Cisco Jabber for Windows for the first time and use a few key features.
Provides an overview of task-based information about end user operation of the client.
Provides information on navigating the client, including shortcut keys, keyboard navigation, and other accessibility features.
This release provides fixes for a number of known issues. See the Fixed in this Release section for a list of resolved caveats.
You can now enable the client to require users to upgrade their client. To set mandatory upgrades for on-premises deployments, you set the Mandatory parameter in the upgrade .xml file to true.
If you do not define mandatory upgrades, or you set it to false, then when logging into the client, users can choose to install the update or remind me later. If you define mandatory upgrades as true, then users can only select to install the update or exit the client.
To set mandatory upgrades in cloud deployments, from the Cisco WebEx Connect Administration Tool, select
For more information on upgrading the client, see the Configure Automatic Updates topic in the Deployment and Installation Guide.
Two new configuration keys are available that you can use to control whether the client can be used as XMPP and SIP protocol handlers. These parameters can be added to the jabber-config.xml file in the Policies node.
Specifies if the client registers as the protocol handler for the IM: URI and XMPP: URI.
Specifies if the client registers as the protocol handler for the SIP: URI.
<Policies> <EnableImProtocolHandler>True</EnableImProtocolHandler> <EnableSipProtocolHandler>True</EnableSipProtocolHandler> </Policies>The default value is true. When set to false, the client will not handle the XMPP or SIP protocol invocations.
Specifies the start of the port range.
Specifies the size of the range.