Preview Tool

Cisco Bug: CSCvh82666 - Add option to disable merging contacts based on phone number

Last Modified

Jun 25, 2019

Products (1)

  • Cisco Jabber for Windows

Known Affected Releases


Description (partial)

++ Current behavior:
"If duplicate contact records are found, then Jabber compares the contact record fields in the following order:
1. Jabber ID (JID)—If the records have a JID, the records are matched based on the JIDs and no further comparison is done on the mail or phone number fields.
2. Mail—If the records have a mail field, the records are matched based on the mail field and no further comparison is done for phone numbers.
3. Phone Number—If the records have a phone number, the records are matched based on the phone number.
As the records are compared and a match is found, the contact information is merged to create one contact record."
As a result, non-presence contacts are merged with LDAP contacts whenever phone number field matches even though the names are different. This causes the issue with displaying correct name.

++ Expected behavior:
Customer would like to have an option to disable merge based on the phone number.

Non-presence contact and LDAP contact having the same phone number. For instance:
[13] <Person: 0B074B5C>
  <PersonRecord: 1F2520A8> John Doe (CUPEditable-fb03d14c-904d-fe60-123a-422c1111a259) Numbers:[123456]
  <PersonRecord: 6C900C93> Peter Parker (LDAP:PP123@movie.lab) Emails:[Peter.Parker@movie.lab] JIDS:[Peter.Parker@movie.lab] Numbers:[123456, +19125551234, (Peter.Parker@movie.lab)]
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.