Extended AD information missing

If you are using some of the more extended AD attributes such as Assistant or Secretary fields, the may not be gathered during a full LDAP build if you are pointing at an AD entry point other than the default at TCP/389.
Some installations require contacting various AD replicas such as a Global Catalog server (GC at TCP/3268) or a Lightweight Directory Service (LDS).  These are not always complete replicas and will not provide the more obscure attributes.  However, it may be possible that they can be added to replicas.  Work with your Active Directory support team as needed.

CTI issues with Park DNs

CallManager allows you to create Park positions in a couple of ways.

The most common is an all numeric numbering plan.
Example:

5000

500[0-9]

500X

However, it is possible to create Park positions with non-numeric characters.

While these can still function as park positions, CallManager will not provide proper CTI information on those positions.  Furthermore, it has been noted that if there are a very large number of these, the Cisco TSP from CallManager 10.5.2 will crash providing no CTI for any DNs.

Examples:

*5000

#5000

*500[0-9]

*500X

Bridge Communication Operator Console only supports all numeric globally unique park DN's.