Caveats for Cisco Jabber for Windows 9.7(7)

Document created by Cisco Documentation Team on Mar 9, 2016Last modified by on Mar 9, 2016
Version 2Show Document
  • View in full screen mode

Bug Severity Levels

Known defects, or bugs, have a severity level that indicates the priority of the defect. These release notes include the following bug types:

  • All severity level 1 or 2 bugs

  • Significant severity level 3 bugs

  • All customer-found bugs except severity level 6 enhancement requests


Severity Level


1 Catastrophic

Reasonably common circumstances cause the entire system to fail, or a major subsystem to stop working, or other devices on the network to be disrupted. No workarounds exist.

2 Severe

Important functions are unusable and workarounds do not exist. Other functions and the rest of the network is operating normally.

3 Moderate

Failures occur in unusual circumstances, or minor features do not work at all, or other failures occur but low-impact workarounds exist.

This is the highest level for documentation bugs.

4 Minor

Failures occur under very unusual circumstances, but operation essentially recovers without intervention. Users do not need to install any workarounds and performance impact is tolerable.

5 Cosmetic

Defects do not cause any detrimental effect on system functionality.

6 Enhancement

Requests for new functionality or feature improvements.

Search for Bugs

To search for bugs not listed here, use the Bug Search Tool.

Step 1   To access the Bug Search Tool, go to
Step 2   Sign in with your user ID and password.
Step 3   To look for information about a specific problem, enter the bug ID number in the Search for field, then press Enter. Alternatively, you can search by product and release.

Open in this Release


There are no new open caveats in this release. 


Fixed in this Release










Jabber client does not allow to enforce STARTTLS as required.



Jabber sends Authorization Header over unencrypted connection.