As part of the Wrangler WxC-DI Migration Dial plan Type Template - an option exist to select SDP (Simplified Dial Plan). This will enable the push of a Simplified country dial plan to the target WxC-DI server. The Source CUCM Dial Plan objects are then mapped to the pre provisioned dial plan and device objects transformed and migrated
The dial plan is created in wrangler using templates and libphone library. A dialplan instance will be automatically created / country and sites and pushed by Wrangler to the target as part of migration
The SDP templates may be freely modified to suit as required.
Migration with SDP Dial Plan
To initiate a migration with SDP process is same as to initiate any migration with Wrangler with selections as per below screenshot, the follow normal migration process here https://yarnlab.atlassian.net/wiki/spaces/YSP/pages/2728493069/Wrangler+UCMC+Migration+User+Guide#Template-Dialplan-Migration-(Push-Dialplan-From-Templates)
Dial Plan Functionality
The SDP creates Dialplan in target that uses a single loop prior to routing calls. All National Prefixes for supported call types are crated by Wrangler SDP as Translation Patterns.
For every external call, numbers dialed match a TP (Translation Pattern) entry depending on COS. The TP strips the prefix and add routing prefix using calling parties CSS, pointing to a Route pattern that in turn selects appropriate RL to route the call
Call Flow Sample below
DN 35100 dials 912343555555
Line has CSS C01S02USA-NationalCLIP-CSS that contains RP USA-Natl-PT
This matches a TP 91.23[149][2-9]XXXXXX which strips predot (91) and prefixes **021 Creating new number **0212343555555 using original DN 35100’s CSS
This new number matches Route Pattern **02.! in USA-NatlCLIPRtg-PT (This RP part of DN35100 CSS) This Route pattern strips predot (**02) and prefixes with + creating number +12343555555 routing it to RL USA-Natl-RL allowing CLIP
Translation Patterns
Dial Plan Objects Created
As mentioned above using libphone library, call types and templates, The SDP will create a basic dial plan including dial out prefixes, country dial plan translation patterns allowing for COS, blocking, CLIP/CLIR and routing in the target supporting a number of call types with the following objects
CSS’s
Route Partitions
Translation Patterns
Route Lists
Route Groups (Trunk/ GW’s need to be added to RG’s as required)
Route Patterns
Note that any Emergency dialing is not supported and needs to be created manually
CSS’s
Calling search spaces are created for COS and routing.
There are COS for Internal Only, National, International and Premium calling with CLIR or CLIP created/ site
Route Partitions
Route partitions are created to support COS including Blocking partitions, routing partitions, partitions for all call types with CLIP and CLIR
Translation Patterns
The TP’s are the core of the SDP. The Wrangler schema templates using libphonenumber library, creates a set of TP Dial Plan prefix entries for each call type for the nation selected in the target CUCM.
The Sample template below will generate a set of TP entries for national US prefixes
Route Lists
The Route List SDP templates will create a RL / country for Route Patter. The SDP will crate a set of Route Lists for Each type National, International and Services Routes for each country supported by cluster
Below template will create a RL for CBO
Route Groups
Same as Route Lists above, SDP will create a Set of Route Groups for National, International and Services for each country supported. Any trunks/ GW\s for the RG’s will need to entered manually as required.
Route Patterns
A set of Route Patterns are created by SDP to support Each of National, International and Services trunk routing for each of CLIP and CLIR and individual country
Modifying the Dialplan Templates
The existing Dial Plan templates may be modified or new ones created as required. They may be modified ‘globally’ or they may be modified on a per migration basis.
Global Template Creation and modification
To modify templates globally requires that existing Default Schema is Cloned and downloaded. To do this, select Schemas, then Default Schema from menu
Next create Clone by selecting +Clone Schema, name the clone and +Clone
The newly created clone can now be modified as required. To narrow down the view, select Filter All Groups → simplifiedDialplan, which will show all the SDP templates
From here, any of the existing SDP templates may be selected and modified as required by selecting the individual template in the Name column.
If we for example wanted to view/ modify template that creates TP’s with country national prefixes, we select SDP - TransPattern - Country CallType Pattens National Fixed Line voip which brings up below display
To the left of the screen we have template attributes which determines how the template will be used and to the right the template fields with macros
When any changes have been completed, select Save Changes
To use the new modified schema in a migration - when initiating a new migration, select the new schema rather than Default Schema
Changing Template per migration
Templates may also be modified/ per migration. To do this, within migration, select Schema → Templates
Then from All Groups filter select simplifiedDialplan
from here select the Template that should be viewed/ modified. In below screenshot we have selected
SDP - TransPattern - Country CallType Patterns National Fixed Line voip
To Modify any field in the template as required, you select Overview Template, modify as required, then Save Changes. Here now also have a preview option that shows the output from modification for testing before deploying
To use the preview function, select Preview Template then select required options and Generate Report
This will show the template and the output of the template for verification
