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 |
Headlline |
---|---|---|
CSCuq70170 |
2 |
BIB INVITE may send incorrect codec leading to dropped calls. |
CSCur85643 |
2 |
Jabber unexpectedly exits after issue in TelephonyControl. |
CSCus18018 |
2 |
Jabber Windows DTMF Fails - Incoming/Contact Header port different. |
CSCuq91678 |
3 |
Jabber for Windows does not show calling name if no calling number is sent. |
CSCur13395 |
3 |
Jabber for Windows does not show contact photo after login using MRA. |
CSCuq40557 |
3 |
Waiting to Join shows up one after another for video conference call. |
CSCuq76278 |
3 |
Click2X: 'Work' not shown when URI Dialing is Enabled. |
CSCur54626 |
3 |
IM user activity report does not show up the number of telephony calls. |
CSCur59634 |
3 |
Jabber EM Profile shows up the first time the Deskphone devices queried. |
CSCus14633 |
3 |
J4W IM only share does not work well with browsers. |
CSCus18564 |
3 |
J4W: Unable to type certain Polish characters. |
CSCus20007 |
3 |
Jabber uses JID to send reminder instead of email. |
Identifier |
Severity |
Headline |
---|---|---|
CSCur23302 |
2 |
Jabber presence is inconsistent. |
CSCur71623 |
2 |
Crash due to deadlock when trying to retrieve or update MRA settings. |
CSCus12075 |
2 |
Jabber automatically joins DX80 calls. |
CSCur25922 |
3 |
Upgrading Jabber for Windows does not save WebEx account settings. |
CSCur58932 |
3 |
Lost the docked window position after upgrade. |
CSCus12594 |
3 |
After network disconnection and call ended, presence always return to Available. |
CSCur78845 |
3 |
Jabber debugging should show milliseconds for reconnect instead of seconds. |
CSCur78915 |
3 |
Jabber for Windows not able to search users with two or more last names using UDS. |
CSCur16381 |
3 |
Jabber Windows intermittently freezes with Visual Voicemail. |
CSCur77577 |
3 |
Jabber for Windows 10.5.2 chat time stamps after midnight GMT. |
CSCur38105 |
3 |
Jabber reports IM failed to deliver when it was delivered. |
CSCur35541 |
3 |
DS allowed with external users despite the policy set to not share. |
CSCur89604 |
3 |
Jabber for Windows not using UDS Batch API. |
CSCur19793 |
3 |
Jabber for Windows softphone video mode does not trigger on softphone calls. |
CSCur87636 |
3 |
Jabber for Windows 10.5 unexpectedly closes when connecting using VPN. |
CSCur31152 |
3 |
Handle leak in Jabber's interaction with Outlook. |
CSCuq78958 |
3 |
Screen capture fails with image showing red X. |
CSCur95286 |
3 |
Jabber should not create multiple persons for the same person record. |
CSCup50047 |
3 |
Jabber 9.7 configured "Display (Caller ID)" not shown for Dif locale. |
CSCur11512 |
3 |
Visual VoiceMail is disconnected and connected again when new voicemail is received. |
CSCur15925 |
3 |
Client does not detect Plantronics Blackwire C720 headset after sleep. |
CSCur90702 |
3 |
Call History is not working in certain scenarios for Jabber 10.5.2. |