Manual Configuration for Intersite Cross-Cluster Support¶
In order to support intersite calls for customers that have sites that span multiple clusters, the following manual procedure is required.
Create a full-mesh network between clusters for customers. Create trunk, route group, and route list with VOSS Automate 10.x/11.5(x) for a given cluster to every other cluster owned by the customer. For a shared Cisco Unified Communications Manager, a SIP security profile is needed for each trunk. For procedures, see Configure SIP Trunks and Configure Route Groups Configure Route Lists.
For each site added to a cluster, a route pattern must be added to all the other clusters in the mesh network owned by the customer. The route pattern is added to the InterSiteRouting partition, the partition name in Cisco Unified Communications Manager is Cu<CustomerID>-ISR-PT, where <CustomerID> is the customer ID.
The pattern in the route pattern depends on the internal dial plan type:
Type 1 and type 3 are the site location code (SLC) plus the extension mask of the site.
Type 2 is the ISP plus the SLC plus the extension mask of the site.
Type 4 is the DN range of the site.
The route list in the route pattern is the route list associated to the site cluster.