cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
429
Views
0
Helpful
1
Replies

Delay with CUPS - LDAP directory search

Hello All,

This is new CUPS deployment(Primary and secondary CUPS server). We have integrated CUPS with LDAP(primary AD and secondaru AD).

The callmanager is integrated with the same LDAP servers. Same search criteria and LDAP settings are used in the CUCM and in the CUPS.

CUPC is configured for desk phone mode and when we do a directory search on the ip phone the contacts are displayed within 2 seconds. But when we

do a contact search on the CUPC client it CUPS takes atleast 15 seconds to pull the contacts and display on the CUPC. Just wondering how this delay can be minimised. The latency between the CUCM to LDAP and CUPS to LDAP are the same.

Below are the configuration,

recursive search is checked in

search context :     dc=xyzdomain,dc=com

Any help would be greatly appreciated.

1 Reply 1

htluo
Level 9
Level 9

Assuming you didn't change the default settings in "CUCM > System > Enterprise Parameters > URL Directory", here's the work flow:

  • Search contacts from IP phone (Directory)

IP Phone will search CUCM internal database, regardless if CUCM is LDAP integrated or not.

  • Search contacts from CUPC

CUPC will search LDAP (CUPC cannot search CUCM).  To troubleshoot the delay, you may do a packet capture on CUPC computer.  Based on the design, CUPC sends industrial-standard LDAP query to LDAP server.  CUPC has no control of the LDAP server at all.  If LDAP server was taking too long to respond, you may narrow the search base.  Or troubleshoot LDAP performance (you need to contact your LDAP vendor for this).

Hope this helps!

Michael

http://htluo.blogspot.com

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: