Cisco Jabber for Windows 10.5(5) Release Notes

Bias-Free Language

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.

Book Contents

Find Matches in This Book

Results

Updated:: February 19, 2015

Caveats

Search for Bugs

Bug Classification

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.

The following table describes bug severity levels:

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.

Search for Bugs

Use the Bug Search page to obtain more information about a bug.

Go to https://tools.cisco.com/bugsearch.
Sign in with your Cisco.com user ID and password.
Enter a bug ID or specify search parameters.

For more information, select Help at the top right of the Bug Search page.

Open in This Release

Identifier	Severity	Headline
CSCuq91678	3	Jabber for Windows does not show calling name if no calling number is sent.
CSCuq40557	3	Waiting to Join shows up one after another for video conference call.
CSCus18564	3	Unable to type certain Polish characters.
CSCus20007	3	Jabber uses JID to send reminder instead of email.

Fixed in This Release

ID	Severity	Headline
CSCur19362	3	Crash after exiting call when call window is popped out.
CSCus91027	3	Jabber Windows not showing Away status when user is Offline and in Out Of Office meeting.
CSCus58947	3	Jabber Windows login results in card reader software pop-up.

Was this Document Helpful?

Feedback

Contact Cisco

Open a Support Case
(Requires a Cisco Service Contract)