Requested by HonorHealth
Ticket: https://akkadianlabssupport.zendesk.com/agent/tickets/74949
Summary
Request for the ability to prioritize data sources used for contact resolution within Akkadian Contact Manager (aCM) and integrated Cisco Jabber environments.
Cisco Jabber relies on data provided by Akkadian Contact Manager for contact lookups.
When multiple data sources are configured in aCM (e.g., CSV uploads, SQL databases, LDAP/Active Directory), aCM aggregates and serves the combined directory to Jabber.
Currently, there is no way to control the order in which aCM prioritizes sources during number or contact lookups. If a phone number exists in both AD and a local aCM source, Jabber may display the AD record rather than the desired local contact.
This can cause confusion when local contacts in aCM are intended to take precedence.
AD contains ~80 users with the main number 623-580-5800 in their telephone field.
aCM contains a local contact labeled “CNC” with the same number (623-580-5800).
Add a configuration option in Akkadian Contact Manager that allows administrators to define source priority for contact resolution such as Contact/profile or by data source.
Example configuration:
Local data source (CSV / SQL)
CUCM / UDS
LDAP / Active Directory
When resolving a contact:
aCM should check the highest-priority source/profile first.
If a match is found, it should stop searching lower-priority sources and return that result to Jabber.
Shane Stamper
