PDF(4.8 KB) View with Adobe Reader on a variety of devices
ePub(79.6 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(64.1 KB) View on Kindle device or Kindle app on multiple devices
Updated:April 13, 2022
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.
The search takes place in a top-down fashion. As soon as a number is resolved to a name, it displays that contact information.
Unfortunately, once there is incorrect information in the local cache, the cache must be deleted. It is most often found that Jabber picks up an Outlook Contact that has incorrect information. However, when this information is used once by Jabber, it is cached and then further lookups are never done for this number again.
Once the problem is identified, the only solution is to find the Jabber cache of the Jabber client that is displayed incorrectly, and delete the cache.
The cache is stored in a folder called “Jabber” which can be found at this location: