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.
This document describes an issue encountered when you integrate Cisco Unity Connection with Active Directory to be able to import users from Lightweight Directory Access Protocol (LDAP) and offers a solution to the problem.
When you attempt to import a user via LDAP in Unity Connection, the user does not show as available for import. The user does not show as an existing user when you run a user search in the GUI. In this case, there is a stale entry in a table about this user that prevents it from being imported.
This document provides examples of searches for User: cisco test and for Userid: ciscotest.
Steps to Troubleshoot
Verify that the user is not available when you try to import from LDAP.
Verify that the user is on the LDAP server.
Navigate to the users page on Unity Connection and search for the user in order to verify that users are not already present on Unity Connection.
Check if the user is available in EndUser table with this Structured Query Language (SQL) query:
admin:run sql SELECT pkid, firstname, lastname, userid, telephonenumber FROM EndUser u WHERE userid='ciscotest'