Notes

In conclusion, VOSS Automate Day 2 Provisioning is expected to cater for multi-cluster customer requirements adequately.

Several critical deployment decisions are required before implementation to ensure successful User Integrations. Some care must be taken to select a model that affords adequate user filtering, considering the functionality available when using VOSS-integrated LDAP, UC App-integrated LDAP, CUCM LDAP Search and Model Instance Filters. Several deployment options are presented, with current best practice strongly recommending using LDAP Search for Directory Integration in conjunction with both Bottom-Up and Top-Down Data Syncs.

Despite the fact that fully-tested multi-cluster dial plan extensions for canned HCS Dial Plans not yet being available, the suggestions contained herein should facilitate basic intercluster routing in most call flows. Several extensions may still be required, with the primary caveats listed in this documents. ILS/GDPR is the recommended method for intercluster trunking and route propagation but is a static configuration at this time. INIs are not yet partition-aware and must be unique across all clusters.