[Index]
PROVIDER ONLY
CISCO
Overview
A Cisco HCS site dial plan is not automatically created for a site when the site is created.
Once the first site for a specified customer is deployed, the customer-level dial plan elements are provisioned on Cisco Unified Communications Manager (CUCM), followed by the site-specific dial plan elements.
Each subsequent site only has site-specific dial plan elements to provision, so it takes less time to create.
For customers with two or more sites, the site dial plan must be applied to each site.
A site can be associated with only one dial plan.
Add a Cisco HCS Site Dial Plan
This procedure creates a Cisco HCS site dial plan and associates the dial plan with a site.
Pre-requisites:
Create the customer dial plan.
You can't create a site dial plan until the customer dial plan exists because there are attributes defined in the customer dial plan that are required when the site dial plan is created.
To add a site dial plan:
Log in to the VOSS Automate Admin portal as a Provider administrator or Customer administrator.
Note
For details around tasks that can be performed for each admin level, see Cisco Hosted Collaboration Solution Roles and Privileges.
Go to (default menus) Cisco Dial Plan Management > Site > Dial Plan, and view existing site dial plans in the list view.
Click the Plus icon (+) to add a new site dial plan; then, select the site.
On the Dial Plan / New Record page, configure the dial plan:
At External Breakout Number, fill out the one digit external breakout number associated with the country associated with the site.
Note
The external breakout number is the PSTN prefix that is used when deploying a country dial plan. The default is 9.
For Cisco HCS Type 1 to 4 dial plan schemas, country dial plans are deployed at the customer level. The country dial plan is pushed to CUCM once the first site associated with a given country is deployed. For example, if a site is associated with the United States, and it is the first site dial plan being created for the USA, the US country dial plan is deployed as part of creating the site's dial plan.
VOSS Automate supports only one external breakout number for each country. For example, all sites within the USA have the same external breakout as the first site within USA.
At Site Location Code, fill out the site location code (SLC). The maximum number of digits is 8. The SLC must be unique across sites for a customer.
Note
This field displays only when the customer dial plan uses site location codes.
At Extension Length, define the number of digits for the extension (between 1 and 30 digits).
At Use extension prefix, for sites without without Inter-Site Prefixes (ISPs), define whether this dial plan uses the extension prefix from the customer dial plan.
Note
This field displays only if your customer dial plan does not use ISPs, for example, HCS Type 3 dial plans (SLC, no ISP, DN=SLC+EXT).
When enabled, this setting is applied only if there is an extension prefix defined in the customer dial plan.
At Area Codes, click the Plus icon (+) to valid, local area codes for the site, if required.
For each area code you add:
Note
The area code is used to generate the PSTN local route patterns for the site. For example, in the USA, if area codes are added for Dallas, Texas, the area codes could be specified for local dialing as 214, 469, and 972 with a subscriber length of 7.
Local Number Length is the length for the subscriber section of the entire E.164 number.
At Area Code used for Local Dialing, define whether the area code is required for for local dialing from this site.
Note
In the USA, this setting determines whether you use 7-digit or 10-digit local dialing.
At Published number, choose from the available E.164 inventory numbers, or fill out a custom number.
Note
Site published number is the default E.164 mask when a line is associated to a phone at a particular site.
At Emergency Call Back Number, choose from the available E.164 inventory numbers, or fill out a custom number.
Note
Site emergency call-back number is the calling number when initiating an outgoing emergency call. It can be used when you use Extension Mobility and make an emergency call from a site other than your own. It can be used when the emergency call goes out to the PSTN network, when the system includes the site emergency number so that the origin of the call is known.
The system adds this calling party transformation to the DN2DDI4Emer-PT partition.
The emergency call back number is not the number to dial for an emergency. Instead, it is the number used to identify the calling party for emergency calls originating from a particular site.
At Use DDI for emergency calls, enable this setting, or leave the checkbox clear.
Note
The read-only Site ID field displays a unique, auto generated number for each customer site, which is prefixed to elements as an identifier (for example, Cu4Si2 indicates Customer 4, Site 2).
Click Save.
The new site dial plan is added. The system takes a few minutes to provision the site dial plan, especially for the first site.
The site information is loaded on CUCM, and is identifiable by its Customer ID, Site ID prefix.
Modify a Cisco HCS Site Dial Plan
PROVIDER ONLY
CISCO
This procedure modifies a Cisco HCS site dial plan.
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) Cisco 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 in Cisco HCS Site Dial Plans
For 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 un-deployed from CUCM, based on the country dial plan schema associated with the site. |
| When modifying area codes | Related translation patterns are un-deployed 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:
| When adding an area code | The area code add IOS command is generated. |
| When deleting an area code | 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. |
| When updating an area code | The area code delete and add IOS commands are generated as necessary, based on the added and deleted logic. |
Published Number Changes in Cisco HCS Site Dial Plans
When changing an existing published number in a Cisco HCS site dial plan:
Emergency Call Back Number Changes in Cisco HCS Site Dial Plans
When updating a Cisco HCS 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:
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.
To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com
This procedure creates a site dial plan and associates the dial plan with a site.
Note
Before you start:
Create the customer dial plan.
You can't create a site dial plan until the customer dial plan exists because there are attributes defined in the customer dial plan that are required when the site dial plan is created.
To add a site dial plan:
Log in to the VOSS Automate Admin portal as a Provider administrator or Customer administrator.
Note
For details around tasks that can be performed for each admin level, see Cisco Hosted Collaboration Solution Roles and Privileges.
Go to (default menus) Dial Plan Management > Site > Dial Plan. The Dial Plan list view displays existing dial site plans.
Click the Plus icon (+) to add a new site dial plan; then, select the site.
On the Dial Plan / New Record page, configure the dial plan:
At External Breakout Number, fill out the one digit external breakout number associated with the country associated with the site.
Note
The external breakout number is the PSTN prefix that is used when deploying a country dial plan. The default is 9.
For Cisco HCS Type 1 to 4 dial plan schemas, country dial plans are deployed at the customer level. The country dial plan is pushed to CUCM once the first site associated with a given country is deployed. For example, if a site is associated with the United States, and it is the first site dial plan being created for the USA, the US country dial plan is deployed as part of creating the site's dial plan.
VOSS Automate supports only one external breakout number for each country. For example, all sites within the USA have the same external breakout as the first site within USA.
At Site Location Code, fill out the site location code (SLC). The maximum number of digits is 8. The SLC must be unique across sites for a customer.
Note
This field displays only when the customer dial plan uses site location codes.
At Extension Length, define the number of digits for the extension (between 1 and 30 digits).
At Use extension prefix, for sites without without Inter-Site Prefixes (ISPs), define whether this dial plan uses the extension prefix from the customer dial plan.
Note
This field displays only if your customer dial plan does not use ISPs, for example, HCS Type 3 dial plans (SLC, no ISP, DN=SLC+EXT).
When enabled, this setting is applied only if there is an extension prefix defined in the customer dial plan.
At Area Codes, click the Plus icon (+) to valid, local area codes for the site, if required.
For each area code you add:
Note
The area code is used to generate the PSTN local route patterns for the site. For example, in the USA, if area codes are added for Dallas, Texas, the area codes could be specified for local dialing as 214, 469, and 972 with a subscriber length of 7.
Local Number Length is the length for the subscriber section of the entire E.164 number.
At Area Code used for Local Dialing, define whether the area code is required for for local dialing from this site.
Note
In the USA, this setting determines whether you use 7-digit or 10-digit local dialing.
At Published number, choose from the available E.164 inventory numbers, or fill out a custom number.
Note
Site published number is the default E.164 mask when a line is associated to a phone at a particular site.
At Emergency Call Back Number, choose from the available E.164 inventory numbers, or fill out a custom number.
Note
Site emergency call-back number is the calling number when initiating an outgoing emergency call. It can be used when you use Extension Mobility and make an emergency call from a site other than your own. It can be used when the emergency call goes out to the PSTN network, when the system includes the site emergency number so that the origin of the call is known.
The system adds this calling party transformation to the DN2DDI4Emer-PT partition.
The emergency call back number is not the number to dial for an emergency. Instead, it is the number used to identify the calling party for emergency calls originating from a particular site.
At Use DDI for emergency calls, enable this setting, or leave the checkbox clear.
Note
The read-only Site ID field displays a unique, auto generated number for each customer site, which is prefixed to elements as an identifier (for example, Cu4Si2 indicates Customer 4, Site 2).
Click Save.
The new site dial plan is added. The system takes a few minutes to provision the site dial plan, especially for the first site.
The site information is loaded on CUCM, and is identifiable by its Customer ID, Site ID prefix.
Update a Site Dial Plan
This procedure updates a Cisco HCS 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.
Making Area Code Changes in Site Dial Plans
For 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 un-deployed from CUCM, based on the country dial plan schema associated with the site. |
| When modifying area codes | Related translation patterns are un-deployed 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:
| When adding an area code | The area code add IOS command is generated. |
| When deleting an area code | 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. |
| When updating an area code | The area code delete and add IOS commands are generated as necessary, based on the added and deleted logic. |
Making Published Number Changes in Site Dial Plans
When changing an existing published number in a site dial plan:
Making Emergency Call Back Number Changes in Site Dial Plans
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:
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.
| Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Site name * | Default: {{ macro.HcsDpSiteName }} |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Customer | Specify the customer that owns this site Default: {{ macro.HcsDpCustomerName }} |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| External breakout number | The external breakout number for the country associated with this site. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Site location code | Site location code can have a maximum of 8 digits. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension length * | Extensions can be from 1 to 30 digits in length. Default: 4 |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Extension prefix required? | Indicates that this site will use the extension prefix as specified in the customer dial plan. If the extension prefix is not specified in the customer dial plan, this setting has no effect. Default: false |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Area Codes | Specify one or more area codes for this site. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Area Code * | An area code associated with this site. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Local Number Length * | Length of the local numbers associated with this area code. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Area Code Used for Local Dialing | Indicates whether area code is needed for local dialing. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Published number | The site published number is the default E164 mask when a line is associated to a phone, device profile, or remote destination profile at a particular site. The default CUCM phone line E164 mask, default CUCM device profile line E164 mask, and the default CUCM remote destination profile line E164 mask in the site default doc are updated with this number, unless those default values in the site defaults doc have been manually updated to some other number. Furthermore, if any existing subscribers are using the site published number in their phone line E164 mask, device profile line E164 mask, or remote destination profile line E164 mask, that value is updated as well. |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Emergency number | The site emergency callback number is the calling number when initiating an outgoing emergency call. If you change the emergency callback number, the following calling party transformation patterns are updated to use the new value: *{{ macro.HcsDpSiteId}}*! and *{{ macro.HcsDpSiteId}}*\+! |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Site ID * | Unique ID for this site Default: {{ macro.HcsDpSiteId }} |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Site Active | Enable to activate the site. Default: false |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Site-Location Code (SLC) Based Dial Plan * | Indicates whether or not Site Location Code is required for this customer. This value for this field taken from Customer Dial Plan model. Default: {{ data.DpCustomer.slcBased }} |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Debug Info | Used to store store debug info and on-screen help information. Default: Default debug info |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Use DDI for emergency calls | Use DDI for emergency calls when user is at home location |
|
|||||||||||||||||||||||||||||||||||||||||||||||
| Shadow |
|
||||||||||||||||||||||||||||||||||||||||||||||||
| Name * |
|
||||||||||||||||||||||||||||||||||||||||||||||||