Caveats and Limitations

• Unity Connection with Bottom Up is unlikely to be effective with MIFs, due to a lack of LDAP fields available to construct an effective MIF.
• Unity Connection Bottom-Up may have unexpected results for user duplication due to duplicates during the ImportUsers transaction. This may lead to unexpected failures during Quick Add Subscriber (QAS) transactions where voicemail is provisioned. This known issue is tracked in CSCvd58565. The workaround is to ensure that userid duplicates are filtered in the Unity Connection LDAP bind agreement(s) using multiple binds or LDAP filtering.
• When LDAP Search, that is UDS Proxy, is used, CUCM Local Users will not be listed in the UDS directory
• More complex MIFs could be required for non-geo clusters, where a separate macro may need to be defined, for example filtering on US Area Codes in telephoneNumber attribute. In this case, it could lead to many statements for large clusters with many sites. Some care will need to be taken to find the most effective macros for the deployment. MIFs containing a large number of attr_filters have the potential for data sync performance degradation. In such cases, consult your VOSS-4-UC Account Team before employing this approach to assess the performance impact.
• At this time, custom LDAP attributes are not yet supported with MIFs due to limitations in the CUCM AXL API.