Updating Site Dial Plans (provider deployment)¶
Modify a Site Dial Plan¶
This procedure updates a dial plan for a site.
Note
Relevant for a Provider deployment only.
Log in as the provider, reseller, or customer administrator.
Set the hierarchy path to the site where you want to update the dial plan.
Go to (default menus) Dial Plan Management > Site > Dial Plan.
In the list view, click on the site dial plan where you want to make changes.
On the Dial Plan page, you can update the following:
Field
Description
Area Code
You can modify or delete existing area codes, or add new area codes.
Local Number Length
The length of a locally dialed number for the specified area code.
Area Code Used for Local Dialing
Defines whether the area code is included in locally dialed calls.
Published Number
The site published number is the default E.164 mask when a line is associated to a phone at a particular site.
Emergency Call Back Number
The site emergency call-back number is the calling number when initiating an outgoing emergency call.
Click Save.
Area Code Changes¶
When updating a site dial plan and you have the Cisco Type 1-4 dial plans, area code changes result in the affected local dialing translation patterns getting reapplied for the site.
When adding new area codes, new translation patterns are deployed to the site, based on the country dial plan schema associated with the site.
When deleting area codes, related translation patterns are undeployed from CUCM, based on the country dial plan schema associated with the site.
When modifying area codes, related translation patterns are undeployed from CUCM, and new translation patterns are deployed, based on the updated area codes.
For the Cisco Type 1-4 dial plan schema groups, area code changes generate LBO IOS area code events. If you change the area code for a site associated with one or more Local SIP Gateways, area code IOS commands are generated. If an area code is:
Added - The area code add IOS command is generated.
Deleted - The area code delete IOS command is generated if no other sites associated with the same SIP Local Gateway are using the deleted area code. If another site still references the same gateway’s area code, the delete area code IOS command is not generated. This prevents invalidating the other site’s local dialing behavior.
Updated - The area code delete and add IOS commands are generated as necessary based on the added and deleted logic.
Published Number Changes¶
When updating a site dial plan and you change the Published Number, the following site defaults are updated if they used the previous Published Number:
Default CUCM Phone Line E164 Mask
Default CUCM Device Profile Line E164 Mask
Line E164 Mask
If you changed the Published Number, then Phone Line Masks, Device Profiles, and Remote Destination Profiles that use the previous Published Number are updated. Any Phone Line Masks, Device Profiles, and Remote Destination Profiles that use a number other than the previous Published Number are not updated.
If you changed the Published Number, previously generated E164 IOS commands for a SIP Local Gateway associated with the site are automatically regenerated.
Emergency Call Back Number Changes¶
When updating a site dial plan and you have a Type 1 - 4 dial plan configured, two calling party transformations are created automatically with the Emergency Call Back Number.
Changing the Emergency Call Back Number updates the calling party mask in these calling party transformation patterns if it used the previous Emergency Call Back Number:
"{{ macro.HcsDpSiteId}}!"
"{{ macro.HcsDpSiteId}}\+!"
If the calling party mask has been manually changed, the fields are untouched.
These calling party transformation patterns insert the Emergency Call Back Number as the caller ID for any emergency calls placed from phones within the site.
Next Steps
Apply any generated or regenerated IOS commands to your IOS gateway.