HCS Dial Plans GDPR Support#

  • Canned HCS Dial Plans have not been formally extended to support all multi-cluster requirements. Several Dial Plan recommendations can be made after analysis of the HCS Customer and Feature Dial Plan Schemas, but are subject to further call flow testing. This does not serve as best practice for inter-cluster call routing when using HCS dial plans.

  • To align with current best practices for dial plan design, it is recommended to employ GDPR/ILS to leverage the many benefits of dynamic call routing schemes. A detailed setup guide via VOSS Automate is beyond the scope of this document but contact your VOSS account team or technical contact for the latest guides and configurations to load.

Reusing Existing HCS Dial Plan Partitioning#

Using GDPR with HCS will enable the seamless support of multi-cluster call routing for multiple call flow scenarios. GDPR can easily be implemented on top of the existing HCS Looping Dial Plan by reusing existing Customer Dial Plan partitions:

  • Forced Onnet Routing

    • {{pwf.HcsDpUniqueCustomerPrefixMCR}}-E164LookUp-PT

  • Enterprise Dialling

    • {{ macro.DP_CUST_PRE_INTER_SITE_ROUTING_PT }}

In order to implement ILS/GDPR, the following high-level procedure is recommended:

  1. Perform static configuration directly on CUCM to:

    1. Configure ILS Configuration for each respective Leaf Cluster/SME. Take note of the advertised route string.

    2. Define the GDPR Learned Patterns Partition for E.164 and Enterprise Dialling using the macro partition specification listed above.

      1. {{pwf.HcsDpUniqueCustomerPrefixMCR}}-E164LookUp-PT

      2. {{ macro.DP_CUST_PRE_INTER_SITE_ROUTING_PT }}

  2. Provision SIP Trunk Security Profiles, SIP Profiles, SIP Trunks, Device Pools, Leaf Cluster Ingress CSS’s etc. on each respective Leaf Cluster/SME.

  3. Provision SIP Route Patterns to match the advertised route string scheme, applying default route (e.g. *.route) in the event that SME is provisioned.

  4. Provision GDPR advertised patterns for E.164 and Enterprise dialling.

The addendum of this document includes several relevant CFTs which may assist in streamlining a bulk-loaded configuration. Workflow adaptations are currently in progress to extend existing functionality to support GDPR as part of E164 associations and Number Management. In the interim, the VOSS Automate team has prepared a set of reference Bulk Loaders. Please contact your VOSS Automate Account Manager for more information.

Segregated GDPR Partitioning#

Customers may wish to selectively partition GDPR patterns for greatly flexibility and dial plan control. This method requires additional configuration, and schema extensions to support new dial plan elements. Additionally, migrating existing dial plans to support multicluster may require a large number of Line CSS updates. For most environments, the proposal for re-using existing schema partitions will meet all business requirements, is simpler to maintain, and is the preferred multicluster system design. If you wish to implement a segregated dial plan partitioning for GDPR, please contact your VOSS Automate Account Team.