As David mentioned, as long as the existing users have the same accounts in CUCM (LDAP) with the same e-mail address, their accounts will stay active and all the meetings scheduled will stay intact. However, if their local CWMS password is different from the CUCM/LDAP password for their account, once you enable Directory Integration, those users will have to use their CUCM/LDAP password.
If the local users used an e-mail address as their ID that is different from e-mail address in CUCM/LDAP, then these users will be marked as INACTIVE and won't be able to authenticate to the system. Their meetings will still remain on the system, but if Join before host is not enabled, these meetings won't be possible to start/attend.
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...