Overview
--------

As of HCS 10.6, inter-cluster call routing for HCS is officially supported as
a static configuration (see `Manual Configuration for InterSite Cross Cluster Support <http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/hcs/10_6_1/HCS_Solution/Dial_Plan/CHCS_BK_DD3FD85C_00_dial-plan-for-cucdm-106x/CHCS_BK_DD3FD85C_00_dial-plan-for-cucdm-1061_chapter_010.html>`_).
Inter-site routing will require ICT Route Patterns.  This includes supporting customer-level INIs,
such as when using customer-wide Hunt Pilots, multi-cluster VM pilots, etc.

Holistic multi-cluster dial plan support needs to cater for Enterprise and E.164 dialing behaviors.
At present, HCS dial plan schemas support these dialing habits in the following manner for intra-cluster call flows.

* E.164 Dialling - Implemented at Customer Level as a Dial Plan Feature in CustomerFONet-Feature-VX-SCH
* Enterprise Dialling - Implemented at Customer Level using the HcsDefaultAddCustomerSchema Core Schema

Customer dial plans can extend these Dial Plan Schemas to support inter-cluster call routing.
End-to-end dial plan template and workflow support for multicluster call routing is on the
product backlog and is planned for an upcoming VOSS Automate release.