CCM5.1, what happen the users if rebuild the LDAP server?
Users pulled from previous LDAP server and also updated to associate IP phone and UDP. If I rebuild the LDAP server with same informaiton as previous one, is the users in CCM still keep same information such as device association or reset all by re-sync the fresh from new LDAP?
I want to apply this methodology if it works to staging the CCM before integration to the production LDAP server.
Re: CCM5.1, what happen the users if rebuild the LDAP server?
As per doc, the sync agreement lookup the existing CCM account and mark to active for the matched.
Here is my scenario,
1. in the LAB, build same IP@, domain information as the production, and same users with userID, sn(last name) and telephonenumber. the production has more but I want to set only three attributes.
2. BAT update for the users to associate devices.
3. move the CCM to production environment and I guess automatically re-establish to the LDAP server since all same (IP@ and domain)
4. sync agreement will compare the account between CCM and LDAP, and will mark the CCM user active since the acconts are match, and will pulling all other attributes which configured in production LDAP into CCM.
If this work, I can save lots of time in customer site. minimize any activity in cutstomer site is best approach as you know.
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...