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.
Contents
Known defects, or bugs, have a severity level that indicates the priority of the defect. Development managers usually define bug severity. Severity helps the product team focus on bug fixes for future releases and prioritize fixes.
Severity level | Description | |
---|---|---|
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. |
Identifier | Severity | Headline |
---|---|---|
CSCuo82526 | 2 | MRA Jabber does not send cookie x-auth token with login request |
CSCuo85779 | 3 | Jabber for Windows shows returned xml in the SSO login window |
CSCun65353 | 3 | No Outlook resolution on calls if contact is not in cache |
CSCuo32278 | 3 | In-call history missed calls show VM pilot number as a caller |
CSCuo70664 | 3 | Jabber for Windows 9.7 Cannot Join Instant Meeting from Toast |
CSCuo73369 | 3 | Call history in Jabber Windows does not record calls with * dialing |
CSCuo76001 | 3 | Click-To-X doesn't work after log-out/login in Cloud SSO |
CSCul53699 | 3 | Double ring back tone on client |
CSCul63819 | 3 | Jabber for Windows unable to connect to WebEx Instant Meeting |
CSCuo06010 | 3 | Softphone does not register in secure mode when logged into PC-2 |
CSCuo26763 | 3 | Jabber for Windows 9.7.0 - Call control lockup on change of network |
CSCuo34049 | 3 | Jabber for Windows getting unregistered intermittently on Win 7 |
CSCun68421 | 3 | Cannot reconnect after hibernate/resume in high availability mode |
CSCul02324 | 3 | Takes 1 minute to go offline after sign out/exit |
Identifier | Severity | Headline |
---|---|---|
CSCun55968 | 2 | Intermittent SSO Login Failure - XML displayed in login window |
CSCuo58290 | 2 | Jabber for Windows 9.7 crashes intermittently |
CSCuo00110 | 2 | Intermittently seeing Jabber unexpectedly exit when processing hyperlink |
CSCug96646 | 3 | Jabber for Windows Photo Retrieval fails if PC username is non-english |
CSCun84091 | 3 | Search clearing is inconsistent |
CSCuo06884 | 3 | In certain instances, no contact image in JFW |
CSCuo21868 | 3 | MSI 4.1.0 silent install does not work on Windows 7 32-bit |
CSCuo28307 | 3 | Calling party transformation CSS is not taking effect in softphone mode |
CSCuo60610 | 3 | Cisco Jabber for Windows does not honor Jabber-config file. |
CSCuo62929 | 3 | Failing to update in-memory dialing rules |
CSCuo65043 | 3 | Allow Programmatic clipboard Access disabled in IE-Cut/paste not working |
CSCun28090 | 3 | Duplicate person records due to case sensitive comparison of Email & JID |