We have found that when we supply alias names that contain spaces and numbers, that, for some reason the MailBoxDN does not get built properly, and the DisplayName gets modified.
For example, If I supply these two DisplayName of
Denver_Univ_Xabc_1st FCS Branch
Denver_Univ_Xabc_1st CSM Branch
The DirectorySync process will create the AD account for the first one. Then, when it tries to create the second one, it seems to only make a comparision up to the first "1" or possibly the first 20 characters and finds the mailbox for the first AD account created. It then sets that accound to the MailBoxDN field of the second Subscriber we are creating and then alters the DisplayName to be the same.
On our system, this happens 100% of the time we attempt to add subscribers.
I'm going to guess that there is a defect lurking in either the AD Sync code or the Subscriber Synch portion of the process.
Further testing we have found that if the alias is greater than 20 characters and the first 20 characters are the same between aliases, then the AD will not be assigned the proper mailbox for subsequent subscribers and the subscribers DisplayName will be corrupted.
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...