Not sure if this applies here, but I've seen issues with employeeNumber when a component tries to look up a user based on this on a global catalog server.
By default it isn't included in the set of attributes that are on the Global Catalog - so for example, if you use employeeNumber as userID on CCM for AD sync, and then switch from 389 to 3268, it stops working.
The fix in that case is to go into AD Schema Admin, and put a tick in a box to replicate it to the GC. After it's synched, all is well.
Please remember to rate helpful posts to identify useful responses, and mark 'Answered' if appropriate!
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...