Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Unity Connection 9 Slow to Import Users (LDAP)

A new Unity Connection ( install has been pointed at LDAP (MS Server 2012) to Import Users.  Pulling up the Import User page takes about 2-3min. Searching for users takes a few more min. So it takes a good 6-7min of waiting to select a single user to import, but it works.

- Everything else in CUC runs fast and the resources are not stressed

- We can ping the Domain Controller by IP and the LDAP setup points to the Domain Conroller by IP (So no DNS issue)

- Services and servers have been rebooted

Any ideas why this would be so slow?

Everyone's tags (3)
Cisco Employee

Unity Connection 9 Slow to Import Users (LDAP)

Probably because it's not supported and tested

Requirements for an LDAP Directory Integration

No way to tell you what might be wrong as the BU never tested such scenario.

Use a supported LDAP and it should work as expected.



if this helps, please rate



if this helps, please rate
New Member

Unity Connection 9 Slow to Import Users (LDAP)


Our intention was to sync CUC Users with LDAP, we had the correct settings under (System Settings > LDAP) but the Import User pagers were painfully slow to navigate.  It turns out another coworker had jumped in there and tried to configure the CUCM AXL integration.  Once I cleared out the unnecessary AXL configurations the LDAP Import User works as expected.

The unwanted AXL settings were found here:

(Telephony Integrations > Phone System > ‘YourPhoneSystem’ > Edit > Cisco Unified Communications Manager AXL Services)

CUCM and CUC 9.1.1 both seem to sync LDAP with Windows Server 2012 just fine.



New Member

thanks natethat was my

thanks nate

that was my problem too!


New Member

i fixed mine issue on CUC 9.1

i fixed mine issue on CUC 9.1.2 by removed the invalid AXL servers. Also check to see if system is using the correct CUCM AXL port 8443 

New Member

Had same problem too.  Thank

Had same problem too.  Thank you.



CreatePlease login to create content