Introduction to the Dial Plan Model in VOSS Automate#

Overview#

The dial plan model was formalized to facilitate a common basis for all translation patterns, partitions, and calling search spaces (CSS). It was also intended to provide consistent naming conventions, and included the following calling patterns:

  • G1 (Flat Dial Plan) calling patterns

  • G2 (Generic Dial Plan) calling patterns

  • G3 (Shared Architecture Dial Plan) inter- and intra-site calling patterns

The dial plan model evolved to provide structure and consistency across deployments, but was inconvenient and clumsy to manage.

The dial plan model in VOSS Automate leverages templates and workflows, and JSON files are used to implement it. These features make this dial plan model more flexible and easier to manage.

Dial plan model types in VOSS Automate#

The VOSS Automate dial plan model comprises these four, basic, predefined call types (dial plan model 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)

Note

These four dial plan model types comprise all previously available functionality, but gives service providers additional flexibility because they can be extended with custom schemas (additional, standalone elements you can choose in VOSS Automate to add to the schema).

Dial plan model features#

The dial plan model provides several flexible features, including:

  • 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 customer’s country sets the PSTN prefix for all other sites of the country for that customer.

Using the dial plan model in VOSS Automate#

An admin user in VOSS Automate fills out a template (at either customer or site level), which defines the dial plan model that is delivered to the CUCM and sites.

The dial plan model is based on various configuration elements, depending on the hierarchy level:

Hierarchy

Configuration elements

Customer level

  • 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 voicemail ID?

Site level

  • Site name

  • External breakout number

  • SLC

  • Extension length

  • Extension prefix required

  • Extension prefix

  • Published number

  • Emergency number

High level dial plan workflows manage the following in VOSS Automate:

  • Locations, region, and device pools per site

  • CUCM 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

  • voicemail

  • Routing

  • Emergency calling line identification (CLI)

  • Inventory management

  • Gateway management