What port are you using to LDAP into AD? 389 or are using a GC with the 3268? Trying changing the LDAP profile on CUPS to point to the GC on port 3268, close, exit CUPC and then relaunch. See if it changes the behavior.
Ok, this is weird, just tested my laptop on our production network and the same CUPC 7.0.2 client can login to the production CUPS and search LDAP successfully so I must have something unique in the lab although can't think of what it would be.
In any case, I'll give a look at this in more detail next week as time permits.
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...