We have a test system where I am testing the AD import and sync of end users.
At present all our users are local users and have local passwords.
I have linked the Test CUCM to AD and used a Custom Filter to ensure only two users are synced.
One user did not exist in CUCM as a local user and one did.
The user that did exist already then suddenly has their account constantly locking in AD, the event logs show the CUCM test server as the source of the lock. The only way to stop it locking is to remove the AD sync.
Weirdly enough the AD user which did not exist as a local CUCM user during the sync has had no issues.
The sync itself does not lock any account just because, you'd need to find out exactly what is the cause for the account locking, most likely it will be due to authentication failure, but CUCM just sends the simple BIND it received from an app like Jabber.
I'd probably look at LDAP logs or even a sniffer to confirm you're sending authentication requests that are causing this.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...