PSTN Call Processing and Routing in Cisco Unified CDM

Introduction to PSTN Call Processing and Routing

PSTN call processing and routing leverages two Cisco Unified Communications Domain Manager features:

  • Calling Search Space (CSS) hierarchy
  • Name Local Route Group

Call processing includes the following stages:

  1. Dial plan determination (internal and PSTN dial plan)
  2. Country dial Plan post-dialing delay (PDD) elimination, normalization, and call type classification (applies to PSTN calling only)
  3. Feature processing - Forced On-Net, Origination Call Screening, Time of Day, Calling Line Identification Restriction (CLIR), Calling Line Identification Presentation (CLIP), Forced Authorization Code and CMC (applies to PSTN calling only)
  4. Line or device based routing
Figure 1. Call Processing Stages

One change from Unified Communications Domain Manager 8.1(x) is that features and routing are based on call type rather than dialed number. The biggest advantage of using call type classification is that most features are independent of the country dial plan. Adding a country dial plan defines the dialing behavior patterns, classifying them into different call types, and defining routing.

There are two caveats on using feature chaining and call type classification:

  • In order to bypass a feature within a feature, a ‘nil’ feature is implemented.
  • For some features (for example FONet), call type classification must be de-classified and reclassified to handle the feature.
Figure 2. Call Processing Implementation

Dial Plan Determination

This chapter covers PSTN call processing and routing. The first stage of call processing is the determination of which dial plan is applied against the incoming call.

It is assumed that there is a PSTN breakout code and the PSTN breakout code is used as a steering digit to direct the PSTN call processing. The PSTN breakout code is a single digit that is country specific and customer specific.

Dial Plans for Cisco Unified Communications Domain Manager 10.x and later are available at CUCDM NextGen Country Dial Plans.

Country Dial Plan Deployment

Each country dial plan deployed consists of a single partition containing all the patterns that handle the dialing behavior for that country. The partition is configured with the 'All Day' Time Schedule. The objective of each pattern in this partition is to eliminate Post Dialing Delay (PDD), normalize the Called Number, prefix the first feature code of the feature chain and set the Call Type to the normalized called number.

If there is Local Dialing behavior, then it is necessary to define a per-site local call handling partition. The patterns in this partition are built based on the following data collected from the user:
  • Local Area Code if present and is or is not required for local dialing

  • The number of digits for the Local (Subscriber) number.

The pattern objective is to eliminate PDD for local dialing, normalize the called number and prefix the first feature code. The local call traverses the feature chain like any other PSTN Call Type.

Besides defining the dialing behavior, it is also necessary to define per-country routing. In general, the routing is similar for every country except for the route list used. Hence it is a matter of copying an existing country routing defined and changing the route pattern route list name.

Predefined Country Dial Plans

The following predefined country dial plans are shipped with Cisco Unified Communications Domain Manager. However, more country dial plans or updated versions of country dial plans may be made available between releases.

Dial Plans for Cisco Unified Communications Domain Manager 10.x and later are available at CUCDM NextGen Country Dial Plans.

Country ISO Three-Letter Country Code

Algeria

DZA

American Samoa

ASM

Angola

AGO

Anguilla

AIA

Antigua and Barbuda

ATG

Argentina

ARG

Aruba

ABW

Australia

AUS

Austria

AUT

Azerbaijan

AZE

Bahamas

BHS

Bahrain

BHR

Barbados

BRB

Belarus

BLR

Belgium

BEL

Belize

BLZ

Bermuda

BMU

Bolivia

BOL

Botswana

BWA

Brazil

BRA

British Virgin Islands

BVI

Bulgaria

BGR

Cameroon

CMR

Canada

CAN

Cayman Islands

CYM

Chile

CHL

China

CHN

Colombia

COL

Commonwealth of Dominica

DMA

Costa Rica

CRI

Croatia

HRV

Cuba

CUB

Curaçao

CUW

Cyprus

CYP

Czech Republic

CZE

Denmark

DNK

Dominican Republic

DOM

Ecuador

ECU

Egypt

EGY

El Salvador

SLV

Estonia

EST

Ethiopia

ETH

Finland

FIN

France

FRA

Georgia

GEO

Germany

DEU

Ghana

GHA

Greece

GRC

Grenada

GRD

Guadeloupe

GLP

Guatemala

GTM

Guinea

GIN

Guyana

GUY

Haiti

HTI

Honduras

HND

Hong Kong

HKG

Hungary

HUN

Iceland

ISL

India

IND

Indonesia

IDN

Iraq

IRQ

Ireland

IRL

Israel

ISR

Italy

ITA

Ivory Coast

CIV

Jamaica

JAM

Japan

JPN

Jordan

JOR

Kazakhstan

KAZ

Kenya

KEN

Kuwait

KWT

Latvia

LVA

Lebanon

LBN

Lithuania

LTU

Luxembourg

LUX

Macau

MAC

Macedonia

MKD

Madagascar

MDG

Malaysia

MYS

Martinique

MTQ

Mauritius

MUS

Mexico

MEX

Mongolia

MNG

Montserrat

MSR

Morocco

MAR

Mozambique

MOZ

Myanmar

MMR

Netherlands

NLD

New Zealand

NZL

Nicaragua

NIC

Nigeria

NGA

Norway

NOR

Oman

OMN

Pakistan

PAK

Panama

PAN

Papua New Guinea

PNG

Paraguay

PRY

Peru

PER

Philippines

PHL

Poland

POL

Portugal

PRT

Puerto Rico

PRI

Qatar

QAT

Republic of Korea

KOR

Reunion

REU

Romania

ROU

Russia

RUS

Saint Kitts and Nevis

KNA

Saint Lucia

LCA

Saint Vincent and the Grenadines

VCT

Saudi Arabia

SAU

Serbia

SRB

Seychelles

SYC

Singapore

SGP

Sint Maarten

SXM

Slovakia

SVK

Slovenia

SVN

South Africa

ZAF

Spain

ESP

Sri Lanka

LKA

Swaziland

SWZ

Sweden

SWE

Switzerland

CHE

Taiwan

TWN

Tanzania

TZA

Thailand

THA

Trinidad and Tobago

TTO

Tunisia

TUN

Turkey

TUR

Turks and Caicos Islands

TCA

Uganda

UGA

Ukraine

UKR

United Arab Emirates

ARE

United Kingdom

GBR

United States of America

USA

Uruguay

URY

US Virgin Islands

VIR

Venezuela

VEN

Vietnam

VNM

Zambia

ZMB

Zimbabwe

ZWE


Note

If you require a new country dial plan to be created, contact your Cisco representative.


Install Country Dial Plan (.template file)

Use this procedure to install a new Country Dial Plan using a .template file.

Procedure


Step 1

Extract the country dial plan .template file from the country dial plan package you downloaded from cisco.com.

Step 2

Use sftp to transfer the country dial plan .template file to the platform user's media directory server.

Step 3

Install the template with the app template media/<template_file> command.

Step 4

Review the output from the app template command and confirm that the message Script /opt/platform/admin/home/template_<random_number>/install_script completed successfully appears.


What to do next

If installation succeeds, add the new Country Dial Plan to your customer dial plan.

Install Country Dial Plan (.json file)

Use this procedure to install a new Country Dial Plan using a .json file.

Procedure


Step 1

Log in as hcsadmin administrator.

Step 2

Select Administration Tools > Import.

Step 3

Browse to the .json file and select Import.

Step 4

To monitor the status of the import, select Administration Tools > Transaction.


What to do next

If the import succeeds, add the new Country Dial Plan to your customer dial plan.

Add a Country Dial Plan to a Dial Plan Before Deploying to a Customer

By default, the USA and GBR country dial plans are associated with Type 1 through Type 4 dial plan schema groups. Use this procedure to associate another country dial plan with a dial plan schema group before deploying the dial plan to the customer.

Procedure


Step 1

Log in as the hcsadmin or provider administrator.

Step 2

Select Dial Plan Management > Advanced Configuration > Dial Plan Schema Group.

Step 3

Choose an existing dial plan schema group to clone, or create a new dial plan schema group.

If you choose an existing dial plan schema group, select Action > Clone. Update the Dial Plan Schema group Name on the General tab. For example, clone Cisco Type 4 Schema Group and give it the name "Cisco Type 4 Schema Group with France."

Step 4

Click the Country Schemas tab.

Step 5

Add the two schemas associated with the country dial plan to the dial plan schema group.

  • HcsGenericCustomer<Country>DP-V<version>-SCH: The schema template used to deploy the customer-level country dial plan elements for the target country.

  • HcsGenericSite<Country>DP-V<version>-SCH: The schema template used to deploy the site-level country dial plan elements for the target country.

Provide the following mandatory information for the two schemas:
Field Description
Dial Plan Schema Usage Select Add Site for both schemas.
Country Name Select the target country.
Dial Plan Schema Scope Select Customer for the customer schema. Select Site for the site schema.
Dial Plan Schema Name Select HcsGenericCustomer<Country>DP-V<version>-SCH for the customer schema.

Select HcsGenericSite<Country>DP-V<version>-SCH for the site schema.

Note 
Add more country dial plan schemas as needed by the customer.
Step 6

Click Save.

Step 7

Deploy the customized schema group to the customer.

  1. Select Dial Plan Management > Advanced Configuration > Associate Custom Dial Plan Schema Group.

  2. Set the hierarchy path to the customer hierarchy node.

  3. Click Add.

  4. From the Dial Plan Schema Group pull down, select the customized dial plan schema group with your added country or countries.

  5. Click Save.


What to do next

Deploy your customer and site dial plans. When a site is created that targets the country you added to the customized dial plan schema group, the appropriate country dial plan schemas are deployed.

Add a Country Dial Plan to a Deployed Customer Dial Plan

Use this procedure to enable another country dial plan for a customer that already has a dial plan deployed.

Procedure


Step 1

Log in as a provider administrator.

Step 2

Select Dial Plan Management > Advanced Configuration > Associate Custom Dial Plan Schema Group.

Make a note of which Dial Plan Schema Group is currently associated with the customer.

Step 3

Set the hierarchy path to the customer hierarchy node for which you want to add country dial plan schemas.

Step 4

Select Dial Plan Management > Advanced Configuration > Dial Plan Schema Group.

Step 5

Select the schema group currently associated with the customer.

Step 6

Select Action > Clone.

Step 7

Click the Country Schemas tab.

Step 8

Add the two schemas associated with the country dial plan to the dial plan schema group.

  • HcsGenericCustomer<Country>DP-V<version>-SCH: The schema template used to deploy the customer-level country dial plan elements for the target country.

  • HcsGenericSite<Country>DP-V<version>-SCH: The schema template used to deploy the site-level country dial plan elements for the target country.

Provide the following mandatory information for the two schemas:
Field Description
Dial Plan Schema Usage Select Add Site for both schemas.
Country Name Select the target country.
Dial Plan Schema Scope Select Customer for the customer schema. Select Site for the site schema.
Dial Plan Schema Name Select HcsGenericCustomer<Country>DP-V<version>-SCH for the customer schema.

Select HcsGenericSite<Country>DP-V<version>-SCH for the site schema.

Note 
Add more country dial plan schemas as needed by the customer.
Step 9

Click Save.

An instance of the schema group with the additional country dial plan schemas is created at the customer level. It has the same name as the schema group from which it was cloned. However, the schema group at the customer level is used rather than the instance at a higher hierarchy node.

What to do next

Deploy the dial plan on the site that uses the new country dial plans.

Called Party Number As Dialed Feature

By default Cisco Type 1-4 dial plans route outbound PSTN calls with called party numbers in a +E.164 format. However, you can implement the As Dialed feature to instead route outbound calls using an 'as-dialed' format using a country's national trunk prefix.

For example, for Great Britain, if the dialed number is 0 20 8824 9286, then called-party number in E.164 format is +44 20 8824 9286. If the 'as-dialed' format is enabled, then the called-party number is 0 20 8824 9286.


Note

  • Enabling sending called-party numbers 'as dialed' is done on a per-country and per-call type basis.
  • This procedure applies to Cisco Type 1-4 dial plan schema groups.

The procedures to implement the Called-Party Number As Dialed feature vary depending on:
  • The version of Cisco Unified CDM

  • Whether country-specific dial plans have been deployed to the customer

Pre-Cisco Unified CDM 10.6(2)

Cisco Unified CDM 10.6(2) or later

Country Dial Plan not deployed for customer

  1. Edit Country Dial Plan Schema (pre-10.6(2)) for Called-Party As Dialed Feature

  2. Deploy Country Dial Plan

  1. Edit Country Dial Plan Schema (10.6(2) or later) for Called-Party As Dialed Feature

  2. Deploy Country Dial Plan

Country Dial Plan deployed for customer

  1. Edit Route Patterns for Called-Party As Dialed Feature

  2. Edit Route Lists for Called-Party As Dialed Feature

  1. Edit Route Lists for Called-Party As Dialed Feature

Edit Country Dial Plan Schema (pre-10.6(2)) for Called-Party As Dialed Feature

Modify the Route Patterns and Route Lists in the dial plan schema for each country dial plan to be deployed to the customer.


Important

Edit all route patterns with the following exceptions:
  • Any route pattern that has the digits 04 (emergency), 05 (service), or 11 (operator) immediately before the dot.

  • Any route pattern that has the digits 01 (international) immediately before the dot, unless the country code is specified immediately after the dot.

  • Any route pattern that has an X (mask digit) immediately after the dot.

Edit all route lists with the following exceptions:
  • Emergency

  • International

  • Operator

  • Service


Before you begin

To complete this procedure, you need to know the country code and country-specific trunk prefix.

Procedure

Step 1

Log in as provider administrator.

Step 2

Select Dial Plan Management > Advanced Configuration > Dial Plan Schema.

Step 3

Click the country dial plan schema you want to modify.

Select the country dial plan schema located closest to the customer hierarchy node.

Example:
For Great Britain, select HcsGenericCustomerGBRDP-V5-SCH.
Step 4

Select the Route Patterns tab.

Step 5

For each route pattern, except for the ones noted previously:

  1. In the Route Pattern field:

    • If the route pattern contains the country code after the dot, move it to immediately before the dot.
    • If the route pattern does not contain the country code, add it immediately before the dot.
    Example:
    For Great Britain:
    • Change **001.44! to **00144.!
    • Change **002.! to **00244.!
  2. In the Called Party Prefix Digits (Outgoing Calls) field, change the + to +<cc>, where <cc> is the appropriate country code.

    Example:
    For Great Britain, change + to +44
Step 6

Select the Route Lists tab.

Step 7

For each route list, except for the ones noted previously, under Members, click More...

  1. If necessary, click + to expand the Members field.

  2. For Called Party Discard Digits, select PreDot.

  3. For Called Party Prefix Digits (Outgoing Calls), enter the appropriate trunk prefix for the country.

Step 8

Click Save.


Edit Country Dial Plan Schema (10.6(2) or later) for Called-Party As Dialed Feature

Modify the dial plan schema for each country dial plan to be deployed to the customer.


Important

Edit all route lists with the following exceptions:
  • Emergency

  • International

  • Operator

  • Service


Before you begin

To complete this procedure, you need to know the country code and country-specific trunk prefix.

Procedure

Step 1

Log in as provider administrator.

Step 2

Select Dial Plan Management > Advanced Configuration > Dial Plan Schema .

Step 3

Click the country dial plan schema you want to modify.

Step 4

On the tabs bar, select Route Lists.

Step 5

For the route list you want to update, under Members, click More...

Step 6

If necessary, click + to expand the Members field.

Step 7

For Called Party Discard Digits, select PreDot.

Step 8

For Called Party Prefix Digits (Outgoing Calls), enter the appropriate trunk prefix for the country.

Step 9

Click Save.


Edit Route Patterns for Called-Party As Dialed Feature

If pre-10.6(2) Country Dial Plans have been deployed, edit certain route patterns to place the country code before the dot in the patterns.


Important

Edit all route patterns for all country dial plans deployed for the customer with the following exceptions:
  • Any route pattern that has the digits 04 (emergency), 05 (service), or 11 (operator) immediately before the dot.

  • Any route pattern that has the digits 01 (international) immediately before the dot, unless the country code is specified immediately after the dot.

  • Any route pattern that has an X (mask digit) immediately after the dot.


Before you begin

To complete this procedure, you need to know the country code for each country dial plan deployed for the customer.

Procedure

Step 1

Log in as provider administrator.

Step 2

Set the hierarchy path to the customer for which you are implementing the As Dialed feature.

Step 3

Select Device Management > CUCM > Route Patterns.

Step 4

Click the route pattern.

Step 5

On the Pattern Definitions tab, edit the Route Pattern field.

  • If the route pattern contains the country code after the dot, move it to immediately before the dot.
  • If the route pattern does not contain the country code, add it immediately before the dot.
Example:
For Great Britain:
  • Change **001.44! to **00144.!
  • Change **002.! to **00244.!
Step 6

On the Called Party Transformations tab, change the Prefix Digits (Outgoing Calls) field from + to +<cc> where <cc> is the appropriate country code.

Example:
For Great Britain, change + to +44
Step 7

Click Save.


Edit Route Lists for Called-Party As Dialed Feature

If country dial plans have been deployed, use this procedure to implement the Called-Party As Dialed feature.


Important

Edit all country-specific route lists for the customer with the following exceptions:
  • Emergency

  • International

  • Operator

  • Service


Before you begin

To complete this procedure you need to know the country-specific trunk prefix.

Procedure

Step 1

Log in as provider administrator.

Step 2

Set the hierarchy path to the customer for which you want to implement the Called-Party As Dialed feature.

Step 3

Select Device Management > CUCM > Route Lists.

Step 4

Click the route list to edit.

Step 5

Click the + to expand the Route Group Items section.

Step 6

For Called Party Discard Digits, select PreDot.

Step 7

For Called Party Prefix Digits, enter the appropriate trunk prefix for the country.

Step 8

Click Save.


Country Dial Plan - Automatically Provisioned Route Patterns

The following route patterns are automatically created by each country dial plan deployed on Unified CM.

Table 1. Automatically Created Route Patterns for Line and Device Based Routing

Call Type

Automatically Created Route Pattern

For Line Based Routing

For Device Based Routing

International

**001.!

**001.!

International with FAC

**101.!

**001.!

International with CMC

**201.!

**201.!

International with FAC&CMC

**301.!

**301.!

National

**0021.!

**0021.!

National with FAC

**1021.!

**1021.!

National with CMC

**2021.!

**2021.!

National with FAC&CMC

**3021.!

**3021.!

Mobile

**0031.!

**0031.!

Mobile with FAC

**1031.!

**1031.!

Mobile with CMC

**2031.!

**2031.!

Mobile with FAC&CMC

**3031.!

**3031.!

Service

**005.!

**005.!

Service with FAC

**105.!

**105.!

Service with CMC

**205.!

**205.!

Service with FAC&CMC

**305.!

**305.!

Local

**0061.!

**0061.!

Local with FAC

**1061.!

**1061.!

Local with CMC

**2061.!

**2061.!

Local with FAC&CMC

**3061.!

**3061.!

Premium

**0071.!

**0071.!

Premium with FAC

**1071.!

**1071.!

Premium with CMC

**2071.!

**2071.!

Premium with FAC&CMC

**3071.!

**3071.!

FreePhone

**0081.!

**0081.!

FreePhone with FAC

**1081.!

**1081.!

FreePhone with CMC

**2081.!

**2081.!

FreePhone with FAC&CMC

**30081.!

**30081.!

Personal Com. Service

**0091.!

**0091.!

Personal Com. Service with FAC

**1091.!

**1091.!

Personal Com. Service with CMC

**2091.!

**2091.!

Personal Com. Service with FAC&CMC

**3091.!

**3091.!

Special Rate Service

**0101.!

**0101.!

Special Rate Service with FAC

**1101.!

**1101.!

Special Rate Service with CMC

**2101.!

**2101.!

Special Rate Service with FAC&CMC

**3101.!

**3101.!

Operator

**011.!

**011.!

Operator with FAC

**111.!

**111.!

Operator with CMC

**211.!

**211.!

Operator with FAC&CMC

**311.!

**311.!

Country Dial Plan - Manually Provision Route Patterns

The following tables provide country-specific route patterns that must be provisioned manually if the dial plan uses an International Restricted call type.

American-Samoa (ASM)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

British Virgin Islands (BVI)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted with no FAC and no CMC

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Canada (CAN)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Cayman Islands (CYM)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted with no FAC and no CMC

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Curacao (CUW)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Italy (ITA)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Kazakhstan (KAZ)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Kenya (KEN)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Macau (MAC)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Malaysia (MYS)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Mexico (MEX)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Netherlands (NLD)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Norway (NOR)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

Reunion (REU)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Russian Federation (RUS)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Tanzania (TZA)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Turks and Caicos Islands (TCA)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted with no FAC and no CMC

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Uganda (UGA)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

**212.!

International Restricted with FAC&CMC

**312.!

**312.!

Uruguay (URY)

Call Type

Manually Created Route Pattern

For Line Based Routing

For Device Based Routing

International Restricted

**012.!

**012.!

International Restricted with FAC

**112.!

**112.!

International Restricted with CMC

**212.!

International Restricted with FAC&CMC

**312.!

Country Dial Plan - Manually Provision Route Patterns for “as dialed” Patterns

Route patterns for the following countries must be manually configured for “as dialed” patterns.

Australia (AUS)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

International as dialed

**0010161.!

**0010161.!

International as dialed with FAC

**1010161.!

**1010161.!

International as dialed with CMC

**2010161.!

**2010161.!

International as dialed with FAC&CMC

**3010161.!

**3010161.!

Bolivia (BOL)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

International as dialed

**00101591.!

**00101591.!

International as dialed with FAC

**10101591

**10101591

International as dialed with CMC

**20101591.!

**20101591.!

International as dialed with FAC&CMC

**30101591.!

**30101591.!

National as dialed

**00201591.!

**00201591.!

National as dialed with FAC

**10201591.!

**10201591.!

National as dialed with CMC

**20201591.!

**20201591.!

National as dialed with FAC&CMC

**30201591.!

**30201591.!

Mobile as dialed

**00301591.!

**00301591.!

Mobile as dialed with FAC

**10301591.!

**10301591.!

Mobile as dialed with CMC

**20301591.!

**20301591.!

Mobile as dialed with FAC&CMC

**30301591.!

**30301591.!

Botswana (BWA)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

International restricted as dialed

**01201267.!

**01201267.!

International restricted as dialed with FAC

**11201267.!

**11201267.!

International restricted as dialed with CMC

**21201267.!

**21201267.!

International restricted as dialed with FAC&CMC

**31201267.!

**31201267.!

Germany (DEU)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

National as dialed

**0020149.!

**0020149.!

National as dialed with FAC

**1020149.!

**1020149.!

National as dialed with CMC

**2020149.!

**2020149.!

National as dialed with FAC&CMC

**3020149.!

**3020149.!

Ecuador (ECU)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

FreePhone

**00801593.!

**00801593.!

FreePhone with FAC

**10801593.!

**10801593.!

FreePhone with CMC

**20801593.!

**20801593.!

FreePhone with FAC&CMC

**30801593.!

**30801593.!

Spain (ESP)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

Service

**0050134.!

**0050134.!

Service with FAC

**1050134.!

**1050134.!

Service with CMC

**2050134.!

**2050134.!

Service with FAC&CMC

**3050134.!

**3050134.!

France (FRA)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

Premium as dialed

**0070133.!

**0070133.!

Premium as dialed with FAC

**1070133.!

**1070133.!

Premium as dialed with CMC

**2070133.!

**2070133.!

Premium as dialed with FAC&CMC

**3070133.!

**3070133.!

Georgia (GEO)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

International as dialed

**00101995.!

**00101995.!

International as dialed with FAC

**10101995.!

**10101995.!

International as dialed with CMC

**20101995.!

**20101995.!

International as dialed with FAC&CMC

**30101995.!

**30101995.!

Hong Kong (HKG)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

Premium as dialed

**00701852.!

**00701852.!

Premium as dialed with FAC

**10701852.!

**10701852.!

Premium as dialed with CMC

**20701852.!

**20701852.!

Premium as dialed with FAC&CMC

**30701852.!

**30701852.!

Indonesia (IDN)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

International as dialed

**0010162.!

**0010162.!

International as dialed with FAC

**1010162.!

**1010162.!

International as dialed with CMC

**2010162.!

**2010162.!

International as dialed with FAC&CMC

**3010162.!

**3010162.!

National as dialed

**0020162.!

**0020162.!

National as dialed with FAC

**1020162.!

**1020162.!

National as dialed with CMC

**2020162.!

**2020162.!

National as dialed with FAC&CMC

**3020162.!

**3020162.!

FreePhone

**0080162.!

**0080162.!

FreePhone with FAC

**1080162.!

**1080162.!

FreePhone with CMC

**2080162.!

**2080162.!

FreePhone with FAC&CMC

**3080162.!

**3080162.!

India (IND)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

Local Mobile as dialed

**0060191.!

**0060191.!

Local Mobile as dialed with FAC

**1060191.!

**1060191.!

Local Mobile as dialed with CMC

**2060191.!

**2060191.!

Local Mobile as dialed with FAC&CMC

**3060191.!

**3060191.!

FreePhone

**0080191.!

**0080191.!

FreePhone with FAC

**1080191.!

**1080191.!

FreePhone with CMC

**2080191.!

**2080191.!

FreePhone with FAC&CMC

**3080191.!

**3080191.!

Korea (KOR)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

National as dialed

**0020182.!

**0020182.!

National as dialed with FAC

**1020182.!

**1020182.!

National as dialed with CMC

**2020182.!

**2020182.!

National as dialed with FAC&CMC

**3020182.!

**3020182.!

Latvia (LVA)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

Premium as dialed

**00701371.!

**00701371.!

Premium as dialed with FAC

**10701371.!

**10701371.!

Premium as dialed with CMC

**20701371.!

**20701371.!

Premium as dialed with FAC&CMC

**30701371.!

**30701371.!

Mexico (MEX)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

Mobile as dialed

**0030152045.!

**0030152045.!

Mobile (local) as dialed

**0030152044.!

**0030152044.!

Mobile as dialed with FAC

**1030152045.!

**1030152045.!

Mobile (local) as dialed

**1030152044.!

**1030152044.!

Mobile as dialed with CMC

**2030152045.!

**2030152045.!

Mobile (local) as dialed

**2030152044.!

**2030152044.!

Mobile as dialed with FAC&CMC

**3030152045.!

**3030152045.!

Mobile (local) as dialed

**3030152044.!

**3030152044.!

Premium as dialed

**0070152.!

**0070152.!

Premium as dialed with FAC

**1070152.!

**1070152.!

Premium as dialed with CMC

**2070152.!

**2070152.!

Premium as dialed with FAC&CMC

**3070152.!

**3070152.!

Macedonia (MKD)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

International as dialed

**00101389.!

**00101389.!

International as dialed with FAC

**10101389.!

**10101389.!

International as dialed with CMC

**20101389.!

**20101389.!

International as dialed with FAC&CMC

**30101389.!

**30101389.!

National as dialed

**00201389.!

**00201389.!

National as dialed with FAC

**10201389.!

**10201389.!

National as dialed with CMC

**20201389.!

**20201389.!

National as dialed with FAC&CMC

**30201389.!

**30201389.!

Peru (PER)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

International as dialed

**0010151.!

**0010151.!

International as dialed with FAC

**1010151.!

**1010151.!

International as dialed with CMC

**2010151.!

**2010151.!

International as dialed with FAC&CMC

**3010151.!

**3010151.!

Philippines (PHL)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

FreePhone

**0080163.!

**0080163.!

FreePhone with FAC

**1080163.!

**1080163.!

FreePhone with CMC

**2080163.!

**2080163.!

FreePhone with FAC&CMC

**3080163.!

**3080163.!

Papua New Guinea (PNG)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

National as dialed

**00201675.!

**00201675.!

National as dialed with FAC

**10201675.!

**10201675.!

National as dialed with CMC

**20201675.!

**20201675.!

National as dialed with FAC&CMC

**30201675.!

**30201675.!

Singapore (SGP)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

International as dialed

**0010165.!

**0010165.!

International as dialed with FAC

**1010165.!

**1010165.!

International as dialed with CMC

**2010165.!

**2010165.!

International as dialed with FAC&CMC

**3010165.!

**3010165.!

Swaziland (SWZ)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

International as dialed

**00101268.!

**00101268.!

International as dialed with FAC

**10101268.!

**10101268.!

International as dialed with CMC

**20101268.!

**20101268.!

International as dialed with FAC&CMC

**30101268.!

**30101268.!

Taiwan (TWN)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

FreePhone

**00801886.!

**00801886.!

FreePhone with FAC

**1080886.!

**1080886.!

FreePhone with CMC

**20801886.!

**20801886.!

FreePhone with FAC&CMC

**30801886.!

**30801886.!

Uruguay (URY)

Call Type

Route Pattern

For Line Based Routing

For Device Based Routing

International as dialed

**00101598.!

**00101598.!

International as dialed with FAC

**10101598.!

**10101598.!

International as dialed with CMC

**20101598.!

**20101598.!

International as dialed with FAC&CMC

**30101598.!

**30101598.!

International Operator as dialed

**01101598.!

**01101598.!

International Operator as dialed with FAC

**11101598.!

**11101598.!

International Operator as dialed withCMC

**21101598.!

**21101598.!

International Operator as dialed with FAC&CMC

**31101598.!

**31101598.!

International restricted as dialed

**01201598!

**01201598!

International restricted as dialed with FAC

**11201598!

**11201598!

International restricted as dialed with CMC

**21201598!

**21201598!

International restricted as dialed with FAC&CMC

**31201598!

**31201598!

Plus Number Dialing Customization

You can make the following customizations to improve + number dialing:

  • Suppress the outside dial tone, which is unnecessary for + number dialing.

  • Support Digit by Digit Dialing

The procedures to implement the customizations depend on whether you have deployed country-specific dial plans or not.

Country-Specific Dial Plans Not Deployed

Country-Specific Dial Plans Deployed

Suppress Outside Dial Tone
  1. Edit Country Dial Plan Schema to Suppress Outside Dial Tone

  2. Deploy Country Dial Plan

  1. Edit Cisco Unified CM Translation Patterns to Suppress Outside Dial Tone

Support Digit by Digit Dialing
  1. Edit Country Dial Plan Schema to Enable Digit by Digit Dialing

  2. Deploy Country Dial Plan

  1. Edit Cisco Unified CM Translation Patterns to Enable Digit by Digit Dialing

Edit Country Dial Plan Schema to Suppress Outside Dial Tone

To suppress an unnecessary outside dial tone for + number dialing, edit the pre-11.5(1) country dial plan schema prior to deploying the country dial plan.

Procedure

Step 1

Login as the provider administrator.

Step 2

Select Dial Plan Management > Advanced Configuration > Dial Plan Schema

Step 3

Click the country dial plan schema you want to modify.

Important 

Select the country dial plan schema located closest to the customer hierarchy node.

Step 4

Click the Translation Patterns tab.

Step 5

For each translation pattern that begins with '\+' and that does not contain another '\+', uncheck the Provide Outside Dial tone check box.

Step 6

Click Save.


Edit Country Dial Plan Schema to Enable Digit by Digit Dialing

To enable digit by digit dialing for + number calling, edit the country dial plan schema prior to deploying the country dial plan.


Important

Enabling digit by digit dialing also introduces Post Dial Delay.


Procedure

Step 1

Login as the provider administrator.

Step 2

Select Dial Plan Management > Advanced Configuration > Dial Plan Schema

Step 3

Click the country dial plan schema you want to modify.

Important 

Select the country dial plan schema located closest to the customer hierarchy node.

Step 4

Click the Translation Patterns tab.

Step 5

For each translation pattern that begins with '\+' and that does not contain another '\+', uncheck the Urgent Priority check box.

Step 6

Click Save.


Edit Cisco Unified CM Translation Patterns to Suppress Outside Dial Tone

If pre-11.5.1 country dial plans have been deployed, edit the Cisco Unified CM translation patterns to suppress an unnecessary outside dial tone for + number dialing.
Procedure

Step 1

Log in as the provider administrator.

Step 2

Set the hierarchy path to the customer for which you are suppressing the outside dial tone.

Step 3

Select Device Management > CUCM > Translation Patterns.

Step 4

Filter the translation patterns to see only + numbers for a country dial plan.

  1. Click the funnel-shaped filter icon on the Translation Pattern column heading.

  2. Select Starts With as the Filter Type.

  3. Enter \+ in the Value field.

  4. Click + to add another filter.

  5. Select Partition as the Column.

  6. Select Contains as the Filter Type.

  7. Enter <ISO-CC>DP in the Value field, where <ISO-CC> is the three letter ISO country code for a country dial plan deployed for the customer. For example, for a US customer enter USADP.

  8. Click Apply.

Step 5

Click each translation pattern except for ones that contain more than one '\+'.

Step 6

Uncheck the Provide Outside Dial Tone check box.

Step 7

Click Save.


Edit Cisco Unified CM Translation Patterns to Enable Digit by Digit Dialing

If country dial plans have been deployed, edit the Cisco Unified CM translation patterns to enable digit by digit dialing.


Important

Enabling digit by digit dialing also introduces Post Dial Delay.


Procedure

Step 1

Log in as the provider administrator.

Step 2

Set the hierarchy path to the customer for which you are enabling digit by digit dialing.

Step 3

Select Device Management > CUCM > Translation Patterns.

Step 4

Filter the translation patterns to see only + numbers for a country dial plan.

  1. Click the funnel-shaped filter icon on the Translation Pattern column heading.

  2. Select Starts With as the Filter Type.

  3. Enter \+ in the Value field.

  4. Click + to add another filter.

  5. Select Partition as the Column.

  6. Select Contains as the Filter Type.

  7. Enter <ISO-CC>DP in the Value field, where <ISO-CC> is the three letter ISO country code for the country dial plan deployed for the customer. For example, for a US customer enter USADP.

  8. Click Apply.

Step 5

Click each translation pattern except for ones that contain more than one '\+'.

Step 6

Uncheck the Urgent Priority check box.

Step 7

Click Save.


Correct Device Based Routing Class of Service to Enable Single Number Reach

Prior to Cisco Unified CDM 11.5, country dial plans were configured with the PreDBRteSel-PT route partition in the site DBRDevice Calling Seach Space (CSS). This configuration causes problems with Single Number Reach (SNR). The correction is to remove the PreDBRteSel-PT route partition from the site DBRDevice calling search space, and add it to each Device Based Routing Class of Service CSS for the site.

If you have deployed country dial plans, correct the deployed CSS using Correction for SNR If Dial Plan Deployed.

If you have not deployed country dial plans, and have not done a new install of Cisco Unified CDM 11.5, correct the country dial plans schemas using Correction for SNR If Dial Plan Not Deployed.

Correction for SNR If Dial Plan Deployed

Use this procedure to correct site level Class of Service CSS to enable Single Number Reach.

Do this procedure for each site that you have deployed a site dial plan to.

Procedure

Step 1

Sign in as a provider administrator.

Step 2

Set the hierarchy path to the site.

Step 3

Select Device Management > CUCM > Calling Search Spaces.

Step 4

Click the Cu<CustomerId>-<ISOCountryCode>DP-DBRDevice-CSS calling search space.

Step 5

Click - to remove the Cu<CustomerId>-<ISOCoutnryCode>DP-PreDBRteSet-PT route partition.

Step 6

Click Save.

Step 7

Select Dial Plan Management > Site > Class of Service.

Step 8

Click a device base routing (DBR) Class of Service CSS.

Step 9

Add the Cu<CustomreId>-<ISOCoutnryCode>DP-PreDBRteSet-PT route partition.

  1. Scroll down to the last route partition.

  2. Click + to add a route partition.

  3. Set the Index to one more than the last index value.

  4. Select Cu<CustomerId>-<ISOCoutnryCode>DP-PreDBRteSet-PT for the route partition.

Step 10

Click Save.

Step 11

Repeat steps 8 through 10 for each DBR Class of Service CSS.


Correction for SNR If Dial Plan Not Deployed

Use this procedure to update site country dial plan schemas to correct the device based routing Class of Service CSS. This correction enables Single Number Reach when the country dial plan is deployed to the customer site. Do this procedure for each affected country dial plan schema.
Procedure

Step 1

Sign in as a provider administrator.

Step 2

Select Dial Plan Management > Advanced Configuration > Dial Plan Schema.

Step 3

Click the country site schema HcsGenericSite<ISOCoutnryCode>DP-V<Version>-SCH. Edit the instance at the provider hierarchy node.

Step 4

Click the Calling Search Spaces tab.

Step 5

Click the {{pwf.HcsDpUniqueSitePrefixMCR}}-<ISOCountryCode>DP-DBRDevice-CSS

Step 6

Click More under the Partitions column.

Step 7

Click - to remove the {{pwf.HcsDpUniqueCustomerPrefixMCR}}-<ISOCountryCode>DP-PreDBRteSel-PT partition (index 2).

Step 8

Click a device base routing Class of Service CSS.

Step 9

Click More under the Partitions column.

Step 10

Click + next to the last route partition.

Step 11

For Route Partition Name, enter {{pwf.HcsDpUniqueCustomerPrefixMCR}}-<ISOCountryCode>DP-PreDBRteSel-PT, where the <ISOCountryCode> is the three character country ISO code for this schema file (for example. USA).

Step 12

For Index, enter a value that is one greater than the current highest route partition index.

Step 13

Repeat steps 8 through 12 for each device based routing Class of Service CSS in the site country dial plan schema.

Step 14

Click Save.


Dial Plans for Caribbean Countries

Country, ISO, and Area Codes for Caribbean countries

The following Caribbean countries follow North American Numbering Plan (NANP) and most of these countries have one area code, except Puerto Rico with two and The Dominican Republic with three area codes. The Caribbean countries are:

Country

ISO

Area Code

Anguilla

AIA

264

Antigua and Barbuda

ATG

268

The Bahamas

BHS

242

Barbados

BRB

246

Bermuda

BMU

441

The British Virgin Islands

BVI

284

The Cayman Islands

CYM

345

The Commonwealth of Dominica

DMA

767

The Dominican Republic

DOM

809, 829, 849

Grenada

GRD

473

Jamaica

JAM

876

Montserrat

MSR

664

Puerto Rico

PRI

787, 939

Saint Kitts and Nevis

KNA

869

Saint Lucia

LCA

758

Saint Vincent and the Grenadines

VCT

784

Saint Maarten

SXM

721

Trinidad and Tobago

TTO

868

The Turks and Caicos Islands

TCA

649

The US Virgin Islands

VIR

340

Calls to neighboring Caribbean countries will be treated similar to calls to USA or Canada. They will be treated as Call Type 03.

Since all of these countries are in the NANP dial plan, and instead of repeating the common Translation Patterns for each country, the dial plans for Caribbean Countries have been split into NANP Schema, and each Country specific Schema.

Call Type Options for Caribbean Countries

Calls to neighboring Caribbean countries can be treated similar to calls to the USA or Canada. In this case they will be treated as Call Type 03 (Normally mobile call type, but has been reused as Calls to NANP countries including USA, Canada and other Caribbean Countries).

Since all of these countries are in the NANP dial plan, and instead of repeating the common Translation Patterns for each country, the dial plans for Caribbean Countries have been split into NANP Schema, and each Country specific Schema.

Alternatively, calls to the Caribbean countries can be treated differently than calls to USA or Canada with the use of the CariCC schema. With this schema the area codes belonging to the Caribbean countries will be call typed as Call Type 12 (International Restricted).

Use the following table as a guide when implementing dial plans for Caribbean countries.

Table 2. Use of Call Type 03 or Call Type 12 for Caribbean Countries

Call Type (3)

Call Type (12)

Configure NANP schema. (The first time any Caribbean country is to be deployed, the NanpDP schema has to be specified. Subsequent Caribbean countries do not require this step.)

Configure NANP Schema. (The first time any Caribbean country schema is to be deployed, the Customer specific NanpDP schema and CariCCDP Schema is to be included along with the Country specific Schema. The subsequent Caribbean countries only need the Country specific Schema.)

Configure Site Schema

Configure CariCC schema

Configure Customer Schema

Configure Country Specific schema

Configure Calling Search spaces

Configure Feature schema

Configure Site schema

Configure Calling Search Spaces

Configure Route List

Configure Route Patterns

North American Numbering Plan Schema

The NANP schema is at a customer level and consists of the common Translation Patterns across all the NANP countries. The following call types are covered in this schema:
  • Call Type (01) – International calls outside of NANP dialed as 011+.

  • Call Type (03) – Normally mobile call type, but has been reused as Calls to NANP countries including USA, Canada and other Caribbean Countries (1+NPA+NXX XXXX).

  • Call Type (05) – Service calls (N11).

  • Call Type (07) – Premium Rate Service (e.g. 900).

  • Call Type (08) – Toll Free or Free phone Service (e.g.800, 888).

  • Call Type (09) – PCS (Personal Communication Service)(e.g. 500).

  • Call Type (10) – Special Rate Service (SRS) calls to Directory Assistance (411, 1+NPA 555 1212).

  • Call Type (11) – Operator Services (0-, 0+).

The Translation Patterns related to Nanp schema are assigned to the CuX-NanpDP-Defn-PT partition, where X is the customer ID.

Caribbean Countries Schema (Optional)

The Caribbean Countries schema is also at a customer level and consists of all the area codes assigned to the Caribbean Countries. This is an optional schema to be used only if calls to the Caribbean countries are to be treated differently than calls to USA or Canada. If this schema is not loaded, or the corresponding partition has not been assigned to the Calling Search Space, calls to other Caribbean countries will be call typed as (03). If this schema is activated, the area codes belonging to the Caribbean countries will be call typed as:
  • Call Type (12) – International Restricted.

The Translation Patterns related to Caribbean Countries Area codes are assigned to the CuX-CariCCDP-Defn-PT partition, where X is the customer ID.

Country Specific Schema

Each Caribbean country mentioned above will have its own country specific schema:

  • The Customer Schema will consist of the following call types:
    • Call Type (02) – The National call type is used if the Caribbean country has multiple area codes (DOM and PRI).

    • Call Type (05) – Service Calls if different from NANP patterns (N11) (Trinidad and Tobago).

  • The Site Schema will consist of the following call types:
    • Call Type (04) – Emergency Patterns.

    • Call Type (06) – Local Call (most of these countries follow 7 digit dialing). The mobile calls are treated as local calls. If they need to be separated out, then please assign them to Call Type (02) National Calls.

Installing the Dial Plan

Specify Call Type 12 Feature Schema

The current Feature Schema does not support Call Type 12. To access the correct schema use the json file CallScreening-Feature-V3.

Procedure

Step 1

Import the file: CallScreening-Feature-V3.json.

Step 2

Within this json file is the schema: Customer-CallScreening-Feature-V3-SCH. Replace the existing feature schema with Customer-CallScreening-Feature-V3-SCH.


Example
Replace the existing Feature Schema with the Customer-CallScreening-Feature-V3-SCH schema. The screen shot is for Type 4 Schema Group. It can also be applied to other Schema Group Types.
Figure 3. Adding Customer-CallScreening-V3-SCH Schema

Specify Site Schema

The first time you deploy a Caribbean country, the NanpDP (North American Numbering Plan Dial Plan) schema must be specified. Deploying subsequent Caribbean countries does not require this process.

If you are using Call Type 12 the first time any Caribbean country schema is to be deployed, the Customer specific NanpDP schema and CariCCDP Schema must be included along with the Country specific Schema. The subsequent Caribbean countries only need the Country specific schema.

Example
The example shown is for Grenada but this can be applied to any Caribbean country from the list of Carribbean countries shown.
Figure 4. Defining the Customer Specific NanpDP Schema and CariCCDP Schema

Define Calling Search Spaces

Update the Calling Search spaces to include the NANP route partition as well as (if used) the CariCC route partition. The following is an example of a typical CSS.

Procedure

Step 1

Log in as the Customer Administrator or the Provider Administrator. For a list of the roles and tasks that can be done at each level, see Cisco Hosted Collaboration Solution Roles and Privileges.

Step 2

In Device Management -> CUCM -> Calling Search Spaces, insert NANPDP Route Partitions after the country specific Defn PT.


Example
Figure 5. Calling Search Spaces Including NanDP and CariCCDP

Route List Required

A new Route List is required if calls to neighboring countries are to be routed over a different trunk group. The create a new Route List see Configure Route Lists.

Create Route Patterns

Procedure
  • Following Route Patterns are to be created for Call Type 12. The following example shows RP **012 for IntlRst Call Type – no FAC no CMC. If FAC and or CMC is required, other Route Patterns can be created as required.

Example
Figure 6. Route Pattern: RP **012 for IntlRst Call Type – no FAC no CMC

Local Breakout (LBO)

In addition to centralized breakout using the aggregation layer, customers can also connect to PSTN through a local gateway. Using a local gateway is also referred to as Local Breakout (LBO). For LBO, each site or location requiring LBO is equipped with a local gateway. When a local gateway is added to a location, the administrator defines the call types that can be routed through the local gateway. For example, you can select national calls to be routed through the local gateway. By default, all call types are routed by LBO.

Enable Local Break Out Custom Workflows

If you have done a fresh install of Cisco Unified CDM 10.6(2) or later, your Type 1-4 Cisco Dial Plan Schema Group will already have the following Local Break Out (LBO) custom workflows specified:
  • associateLboGateway

  • unassociateLboGateway

However, if you have upgraded from a pre-10.6(2) version, you must update your Dial Plan Schema Group to enable these custom workflows, if you want to use Local Break Out.

Procedure


Step 1

Log in as the provider administrator.

Step 2

Select Dial Plan Management > Advanced Configuration > Dial Plan Schema Group.

Step 3

Select the appropriate schema group that is in use by your customer.

Step 4

Click the Custom Workflows tab.

Step 5

Add the following Dial Plan Event to Workflow bindings:

  • associateLboGateway > HcsDefaultAddLBOGatewayPWF

  • unassociateLboGateway > HcsDefaultDelLBOGatewayPWF

Step 6

Click Save.


associateLboGateway Custom Workflow

The associateLboGateway custom workflow is optional. If it is not specified in the customer's Dial Plan Schema Group, when a SIP Local Gateway is associated with a site only the IOS Command Builders are triggered.

The HcsDefaultAddLBOGatewayPWF is triggered every time a SIP Local Gateway is associated with a site and executes the following logic:

  • If the site-specific Cu<cid>Si<sid>-LBO-RG route group doesn’t exist, it is created with the SIP Trunk associated with the SIP Local Gateway as a member device.

  • If the site-specific Cu<cid>Si<sid>-LBO-RG route group exists, it is updated to include the SIP Trunk associated with the SIP Local Gateway as a member device.
  • For line-based routing (LBR), the HcsDefaultLboSchema is deployed.
    Figure 7. HcsDefaultLboSchema


  • For device-based routing (DBR), if this is the first SIP Local Gateway associated to the site, the site default device pool Cu<cid>Si<sid>-DevicePool is updated, such that all the default Local Route Groups are set to the new Cu<cid>Si<sid>-LBO-RG.

  • Once a SIP Local Gateway is associated with a site and the HcsDefaultLboSchema dial plan schema has been deployed, the Cu<cid>Si<sid>-LBOLBRtg-PT route partition can be used when constructing a site line-based routing (LBR) Class of Service (CoS) that uses local break-out.

    Note

    The LBR CoS must be defined such that the LBOLBRtg-PT (used for LBO) is higher priority than the LBRtg-PT (used for Central Break-out (CBO)).


  • By default, when more SIP Local Gateways are associated to the same site, the Cu<cid>Si<sid>-LBO-RG route group is updated to include the additional SIP Trunk associated with the additional gateway. The trunks in this route group use the Top Down distribution algorithm.

unassociateLboGateway Custom Workflow

The unassociateLboGateway custom workflow is required only if associateLboGateway is enabled. If it is not specified in the customer's Dial Plan Schema Group, when a SIP Local Gateway is disassociated from a site only the IOS Command Builders are triggered.

The HcsDefaultDelLBOGatewayPWF is triggered every time a SIP Local Gateway is disassociated from a site and executes the following logic:

  • Update the site-specific Cu<cid>Si<sid>-LBO-RG route group to remove the SIP Trunk associated with the SIP Local Gateway as a member device.

  • For line-based routing (LBR), if this is the last SIP Local Gateway associated with the site, the Translation Patterns are removed from the Cu<cid>Si<sid>-LBOLBRtg-PT route partition. Removing the Translation Patterns forces the class of service CSS's that use LBO to fall back to central break-out (CBO).
  • For device-based routing (DBR), if this is the last SIP Local Gateway associated with the site, the site default device pool, Cu<cid>Si<sid>-DevicePool, is updated such that all the default Local Route Groups are no longer associated with Cu<cid>Si<sid>-LBO-RG.