Preview Tool

Cisco Bug: CSCur93273 - Need to build unique ID for contact whose primary attribute is empty

Last Modified

Feb 07, 2017

Products (1)

  • Cisco Jabber for Windows

Known Affected Releases


Description (partial)

In some use cases when in the config file the attribute UserAccountName is set to  <employeeNumber> for example in ldap not all users will have the employe number field defined. This will causes issues during EDI search.

we build a unique ID for the contact using a configured attribute which is empty. The net result is that a contact is created without a unique ID, and this contact will match most (if not all) searches. 
This use case is not currently supported, and would be an enhancement to how we currently create contacts in Jabber

All jabber versions
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.