.. _p-dialplan-overview:
Introduction to Cisco HCS dial plan
--------------------------------------
:bdg-primary:`Cisco`
:bdg-secondary:`provider-only`
.. _18.1-Patch-Bundle-3|EKB-673:
.. tip::
:ref:`use-action-search-to-navigate-automate`
Overview
.........
Automate Provider solution supports Cisco HCS dial plan tools.
Custom (non-HCS) Cisco dial plans are also supported for Enterprise deployments.
For details, see *Appendix: Optional Features* in this guide.
The Cisco custom dial plan is independent of the hierarchy schema approach of the Cisco HCS
dialplan. However, it can also be used in conjunction with schema-based dial plan management.
.. note::
For Microsoft dial plan, see *Microsoft Teams Dial Plan Management* in this guide.
.. rubric:: Related topics
*
.. raw:: latex
Dial Plan Schemas in the Provider HCS Dial Plan Management Guide
.. raw:: html
Dial Plan Schemas
*
.. raw:: latex
Dial Plan Schema Groups in the Provider HCS Dial Plan Management Guide
.. raw:: html
Dial Plan Schema Groups
*
.. raw:: latex
Associate Custom Dial Plan Schema Group in the Provider HCS Dial Plan Management Guide
.. raw:: html
Associate Custom Dial Plan Schema Group
*
.. raw:: latex
Emergency and CLI Settings in the Provider HCS Dial Plan Management Guide
.. raw:: html
Emergency and CLI Settings
Example workflow for Cisco HCS dial plan
.........................................
This section provides a high level example workflow for a Cisco HCS dial plan.
.. note::
See also the Provider HCS Dial Plan Management Support Guide for additional details
around using Cisco HCS dial plans in Automate.
1. Mandatory. Deploy country dials plans (for countries other than United States or United Kingdom).
.. note::
This task is mandatory when using country dial plans other than US or UK. For details,
see the "Provider HCS Dial Plan Management Support Guide".
2. Apply customer dial plan at customer.
3. Apply site dial plan at site.
4. Optional. Configure Class of Service (CoS) at site.
5. Add Directory Number Inventory at customer or site.
6. Optional. Configure E.164 Inventory at customer or site.
7. Optional. Configure E.164 Number to Directory Number associations at customer or site.
8. If not using Site Location Codes (that is, you have deployed a Type 4 Dial Plan),
configure Directory Number Routing at site to enable intra- and inter-site calls.
9. Optional. Configure Short Codes at site.
10. Edit Site Defaults as follows:
a. On the **Device Defaults** tab, set the default Automate device CSS to
an appropriate device Class of Service.
b. On the **Line Defaults** tab, set the Default UCM Line CSS to an
appropriate line Class of Service.
11. For offnet PSTN call configuration, see the "Provider HCS Dial Plan Management Support Guide".
12. For Local Breakout (LBO) configuration, see "IOS Device Management".
13. For user, phone, and line configuration, see "User Management".
Cisco shell schema groups
.............................
To deploy your own existing dial plan rather than one of Cisco's
out-of-the-box dial plans, use the shell schema group to enable core
functionality without deploying a pre-configured Automate schema
group.
The shell schema group provides a starting point for you to build
your own dial plan. The shell schema group has no preset site default
values other than Default Device Pool and Default UCM Group. The shell
schema group does not contain any default core schemas, features schemas,
or country schemas. You can clone the shell schema group instance and
tailor all other settings to your own specifications.
On the **Custom Workflows** tab, the shell schema group provides default
workflows for the following registry events used to create customer
inventories and associations:
.. tabularcolumns:: |p{5cm}|p{10cm}|
+--------------------------------+----------------------------------------------------------------------------+
| Registry event | Description |
+================================+============================================================================+
| addDnInventory | Allows you to create DN inventory without enforcing any rules or |
| | constraints on the DN numbers |
+--------------------------------+----------------------------------------------------------------------------+
| addE164Inventory | Allows you to create E164 inventory without enforcing any rules or |
| | constraints on the E164 number other than enforcing the country code |
| | prefix for a given site |
+--------------------------------+----------------------------------------------------------------------------+
| associateE164ToDn | Allows E164 to DN number association (N to N) on Automate without |
| | configuring anything on Cisco Unified CM |
+--------------------------------+----------------------------------------------------------------------------+
| unassociateE164ToDn | Removes E164 to DN number association (N to N) from Automate without |
| | removing anything on Cisco Unified CM |
+--------------------------------+----------------------------------------------------------------------------+
| associateE164ToSingleDn | Allows E164 to DN number association (N to 1) on Automate without |
| | configuring anything on Cisco Unified CM |
+--------------------------------+----------------------------------------------------------------------------+
| unassociateE164ToSingleDn | Removes E164 to DN number association (N to 1) on Automate without |
| | removing anything on Cisco Unified CM |
+--------------------------------+----------------------------------------------------------------------------+
.. note::
For more information on configuring schema groups and associating them with customers,
see the *Provider HCS Dial Plan Management Support Guide*.