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.
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 |
---|---|---|
CSCup78097 |
2 |
Jabber search on a user is returning multiple Outlook contacts for users. |
CSCuo90291 |
3 |
Jabber screen sharing quality varies due to cached low bandwidth level. |
CSCup14715 |
3 |
Restricted number is not stored in call history of Jabber for Windows. |
CSCup29889 |
3 |
Phone, company, and photo intermittently missing on Windows 8. |
CSCup82773 |
3 |
Call drops after a temporary network loss. |
CSCup70296 |
3 |
Jabber incorrectly modifying Nickname field. |
CSCup38516 |
3 |
Jabber login issue with _cisco-uds if the password is in Umlaut format. |
CSCup50047 |
3 |
Jabber 9.7 configured "Display (Caller ID)" not shown for Dif locale. |
CSCul53699 |
3 |
Double ring-back tone on client. |
CSCup39611 |
3 |
Jabber requires Voicemail server config on IMP |
Identifier |
Severity |
Headline |
---|---|---|
CSCuq70170 |
2 |
BIB INVITE may send incorrect codec leading to dropped calls. |
CSCuq02404 |
3 |
Token not requested in resume-on-cloud SSO mode. |
CSCuq18032 |
3 |
AppVerifier: Crash when uploading photo. |
CSCuo53987 |
3 |
Jabber crashes while running inspect.exe. |
CSCuq23747 |
3 |
Unable to add more than 7 custom contact in one login. |
CSCuq26881 |
3 |
The word "Subject" is prepended to any IM sent to Apple messages.app |
CSCup30905 |
3 |
UDS service discovery fails with hardware phone. |
CSCup30350 |
3 |
MS Voice Recognition causes Jabber to behave unexpectedly. |
CSCur10579 |
3 |
Pizza guy contact name converts to DN after making a call. |