Dial Plan Model Overview¶
The Dial Plan Model was formalized to facilitate a common basis for all the translation patterns, partitions, and calling search spaces, and provide consistent naming conventions. The model included G1 (Flat Dial Plan), G2 (Generic Dial Plan) and G3 (Shared Architecture Dial Plan) inter- and intra-site calling patterns. The model evolved to provide structure and consistency across deployments but was cumbersome to manage.
The Dial Plan Model in VOSS Automate 10.x/11.5(x) leverages templates and workflows in VOSS Automate 10.x/11.5(x) using json files to implement the model. The new model is more flexible and is designed to simplify dial plan management wherever possible.
The Dial Plan Model in VOSS Automate 10.x/11.5(x) consists of four basic, predefined call types:
Directory Number = Site Location Code (SLC) + Extension, no Inter Site Prefix (ISP) in SLC
Directory Number = SLC + Extension with ISP as part of SLC
Directory Number = SLC + Extension and without ISP, can be with or without Extension Dialing Prefix (EDP)
Directory Number = Flat Dial Plan (no SLC)
These four dial model types encompass all the functionality that was available on the previous Dial Plan Model, but in order to offer flexibility for service providers, the four types can be extended with custom schemas. Customization is managed through discrete, selectable elements in VOSS Automate 10.x/11.5(x).
The Dial Plan Model provides flexible features such as:
Dynamic Class of Service
Country Dial Plans
Blocked / Non-blocked numbers
Call Manager groups
Flexible routing
PSTN prefix per country per customer. The first site of the country of the customer sets the PSTN prefix for all other sites of the country for that customer.
In VOSS Automate 10.x/11.5(x), the administrator is asked at either the customer or site level to fill in a template which determines the Dial Plan Model that is delivered to the Cisco Unified Communications Manager and sites.
At the customer level, the Dial Plan Model is based on the following configuration elements:
Is SLC-based dial plan required?
Does the customer require inter-site prefix (ISP)?
Is inter-site prefix required as part of SLC?
Is the ISP part of the Directory Number?
Is the ISP included in the Voice Mail ID?
At the site level, the Dial Plan Model is based on the following configuration elements:
Site Name
External breakout number
SLC
Extension length
Extension Prefix required
Extension Prefix
Published number
Emergency number
High level work flows manage the following in VOSS Automate 10.x/11.5(x):
Locations, Region and Device Pools per site
Call Manager Groups at the Provider/Reseller/Customer level
Local Route Groups Names at the cluster level
Default and custom Customer and Site level dial plan schemas
Voice Mail
Routing
Emergency Calling Line Identification
Inventory Management
Gateway Management