When CUCM is using LDAP for authentication several subsystems including CTI manager utilize this mechanism for device authentication. One for example is the CTI manager the invokes an LDAP authentication process with LDAP when a CUPC user enabled deskphone control.
Generally most LDAP querys (aka searchRequests) have a sizeLimit and timeLimit variable that can control to overall response in addition to the filter.
When an Tomcat authentication request takes place these size and time Limit Values are sent to the LDAP server with 0's for each.
When a CTI authentication request takes place the SizeLimit value is 0, however the timeLimit value is 1996501041 . This variable seems to cause issues with Sun One LDAP systems where the LDAP server returns a timeLimitExceeded... I can execute the exact same searchRequest with a stand alone browser with a timeLimit of 0 and get the appropriate response every time.
Does anyone know why this timeLimit value gets populated on CTI requests from CUCM or what this value actually represents?
Thanks for the reply. I do know now that the timestamp is a unix epoch timestamp for sometime in 2033.. but this is the only delta in between a successfull result and a failure.. I am requesting logs from the LDAP side of the house to see what type of errors are being collected on that side. Do you know by chance since CTI is C/C++ of this value is compiled into the subsystem or is a variable somewhere that could be changed with the appropriate system access?
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.