I want to know about a true conversion. As you do when you go from a local CUC subscriber to an LDAP Synced subscriber.
I have tried using the store procedure: csp_subscribermodify, supplying the following params: pobjectid = the object id, palias = my AD user ID, pldapccmuserid = my AD user ID, pldaptype = 3, pccmid = null, and pccmidtype = 0.
While the stored procedure looks like it worked, the web page for the subscriber looks a bit odd. The alias changed, and the ldap sync status changes, but the normally greyed out fields, like alias, are still editible. Also, none of the other LDAP attributes sync. So, I'm convinced it didn't actually work.
What am I missing to make this work? Thanks.
PS Jeff, if you see this, I enjoy your training videos. "Easy Peasy!"
Please use the star ratings to help drive great content to the top of searches.
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...