Discovery 18: Implement Globalized Call Routing

Introduction
When you deploy Cisco Unified Communications Manager in a multisite environment with centralized call
processing, the digit manipulation requirements can become extremely complex, especially when a single Cisco
Unified Communications Manager cluster covers multiple countries with different PSTN dialing habits.

When features such as Extension Mobility, Device Mobility, Automated Alternate Routing (AAR), or Tail End Hop
Off (TEHO) are deployed across country boundaries, there are just too many possible dialed number (call ingress)
formats that could be combined with different outbound dialed (call egress) formats.

Globalized call routing allows you to decouple the ingress format from the egress format by introducing a
normalized format for called- and calling-party numbers. Instead of mapping all possible ingress formats to all
possible egress formats, you convert all possible ingress formats to the normalized format and the normalized
format can be converted to all possible egress formats. The normalized format is +E.164, which is based on the
ITU standard of representing global telephone numbers.

In this lab, you will have one Cisco Unified Communications Manager cluster that serves two sites: one in the
United States (San Jose) and one in the United Kingdom (London). One phone (US-CIPC-1) is located in San Jose
(SJC) and one phone (UK-CIPC-1) is located in London (LON).

Each site has a local PSTN gateway. The PSTN-CIPC phone represents the PSTN and is configured with eight
lines. Depending on the number you dial (a local, national, international, or emergency number) and on the
originating site (San Jose or London), your call is delivered to a different line on the PSTN phone.

The PSTN gateways and the PSTN itself are simulated by a Cisco Unified Communications Manager
cluster. The PSTN gateways that you configure in the Cisco Unified Communications Manager cluster (an
H.323 gateway at the SJC site and a SIP gateway at the LON site) refer directly to the PSTN Cisco Unified
Communications Manager cluster and not to actual Cisco IOS gateways. Therefore, you will not configure
any Cisco IOS gateways.

You will implement inbound and outbound PSTN calls for the SJC and LON sites using globalized call routing. You
will allow localized call ingress at the phones and you will configure the necessary translation patterns to globalize
the localized call ingress to +E.164 format. At the egress gateways, you will localize called- and calling-party
numbers as required by the corresponding gateway. Inbound PSTN calls are globalized at call ingress and then
localized when the calls are routed to the internal phones.

When implementing globalized call routing, you have to perform many repetitive steps with similar
configuration. To give you enough time to perform these tasks and avoid too many repetitive steps, some
components are preconfigured. The instructions refer to preconfigured items so that you know which
components already exist but are required.

This lab will take approximately 2 hours to complete.

Topology
Job Aid
Device Information

Device Description IP Address Credentials

PC-1 PC running Cisco IP Communicator US-CIPC-1 10.1.5.200 Student, C0ll@B

PC-3 PC running Cisco IP Communicator UK-CIPC-1 10.1.99.101 Student, C0ll@B

PC-4 PC running Cisco IP Communicator PSTN-CIPC 10.1.35.101 Student, C0ll@B

HQ-CUCM Cisco Unified Communications Manager serving the US and the UK sites 10.1.5.5 Administrator, C0ll@B

PSTN-CUCM Cisco Unified Communications Manager providing the simulated PSTN 10.1.99.5

HQ-WIN-SERVER-1 Microsoft Windows Server providing NTP and DNS services 10.1.5.100

PSTN Numbers and Dial Rules

The following tables describe the PSTN numbers and dial rules.

The spaces that are used in the shown numbers are not displayed in calling-party numbers and cannot be
entered when you dial a destination. They are only used to make the numbers easier to read.

PSTN Numbers, DID Ranges, and Internal Directory Numbers

PSTN Number or DID (+E.164 Directory Country Area Number of Subscriber

Country City
Format) Numbers Code Code Digits

United States
San Jose (SJC) +1 408 5551XXX 11XXX 1 408 7
(US)

United Kingdom
London (LON) +44 20 7940XXX 21XXX 44 20 8
(UK)

United States
Tampa (TPA) +1 813 5550000 PSTN only 1 813 7
(US)

United Kingdom Manchester

+44 161 4960000 PSTN only 44 161 7
(UK) (MAN)
 PSTN Number or DID (+E.164 Directory Country Area Number of Subscriber
Country City
Format) Numbers Code Code Digits

Australia (AU) Sydney (SYD) +61 2 70100000 PSTN only 61 2 8

PSTN Dial Rules

City PSTN Access Code (Outside Line) International Access Code National Access Code Local Emergency

SJC 9 011 1 10 digits 911

TPA 9 011 1 10 digits 911

LON 9 00 0 8 digits 999

MAN 9 00 0 7 digits 999

SYD 0 0011 0 8 digits 000

In this particular lab environment, you must use 10 digits for local calls within the United States, even if the
area codes of the source and the destination are identical.

Use of the PSTN Phone

To place calls from the PSTN phone, you have to select the line from which you want to place the call before you
enter the destination number. Simply click the phone button of the corresponding line to select the line. If you do
not select a line, the first line is used.

You can place the following calls from the PSTN phone:

Line Number and Calling-Party Location of the Simulated Numbers You Can Dial from Gateway to Which the Call
Label Number PSTN Phone the Line Is Routed

1, SJC-local +1 408 5550000 SJC 408 5551XXX SJC Gateway

2, SJC-ntl +1 813 5550000 TPA 1 408 5551XXX SJC Gateway

3, SJC-intl +61270100000 SYD 0011 1 408 5551XXX SJC Gateway

4, SJC-emergency SJC

5, LON-local +44 20 79460000 LON 79460XXX LON Gateway

6, LON-ntl +44 161 4960000 MAN 0 20 79460XXX LON Gateway

7, LON-intl +61270100000 SYD 0011 44 20 79460XXX LON Gateway

8, LON-emergency LON

The PSTN phone simulates residential subscribers. Therefore, you must not prefix the PSTN access code
when you dial from the PSTN phone.

Placing Calls to the PSTN

You can place calls to the PSTN from Cisco Unified Communications Manager through the SJC gateway and
through the LON gateway.

Use the speed dials on the SJC phone (US-CIPC-1) and on the LON phone (UK-CIPC-1). There is a speed dial for
each possible destination (local, national, international, and emergency).

The call is delivered to the appropriate line of the PSTN phone (lines 1 to 4 if sent through the SJC gateway, lines 5
to 8 if sent through the LON gateway).

Formats Supported Between the PSTN Gateways and the PSTN

Direction of the Call Calling-Party Number Called-Party Number

To local: 10 digits, no TON

(408 5550000)
To national: 1, followed by 10 digits,
no TON
Call from Cisco Unified Communications Manager to the PSTN, 10 digits, no TON
(1 813 5550000)
through the SJC gateway (408 5551001)
To international: 011, followed by
E.164, no TON
(011 61 2 70100000)
To emergency: 911, no TON

To local: E.164, no TON

(44 20 79460000)
To national: E.164, no TON
Call from Cisco Unified Communications Manager to the PSTN, 10 digits, no TON
(44 161 4960000)
through the LON gateway (20 79460001)
To international: E164, no TON
(61 2 70100000)
To emergency: 999, no TON

From local: 10 digits, TON

subscriber
(408 5550000)
From national: 10 digits, TON
Call from the PSTN to Cisco Unified Communications Manager, 10 digits, no TON
national
through the SJC gateway (408 5551001)
(813 5550000)
From international: E.164, TON
international
(61 2 70100000)

From local:E.164, no TON

(44 20 79460000)
From national: E.164, no TON
Call from the PSTN to Cisco Unified Communications Manager, 10 digits, no TON
(44 161 4960000)
through the LON gateway (20 79460001)
From international: E.164, no
TON
(61 2 70100000)

In the previous table, you can see that no TONs are used at any numbers that are exchanged between the
LON gateway and the PSTN. The LON gateway is a SIP gateway and SIP does not support TON.
Therefore, TONs cannot be used. In addition, you cannot send the plus (+) sign through a SIP trunk.

When you send a call to the PSTN and your calling-party number does not comply with the rules explained
previously, a calling-party number of 99999999 will be displayed on the PSTN phone.

What about wrong called numbers? Do I still route them to emergency or does the call fail?

Task 1: Register Endpoints

Activity
The initial configuration includes a simple dial plan, including preconfigured endpoints.

You will register the endpoints.

Register the Endpoints

Now you will register these endpoints:

Cisco IP Communicator Device Cisco Unified Communications Directory

PC PSTN Number Location
Name Manager Number

PC-1 US-CIPC-1 10.1.5.5 11001 +1 408 5551001 US, San Jose (SJC)

+44 20
PC-4 UK-CIPC-1 10.1.5.5 21001 UK, London (LON)
79460001
 Cisco IP Communicator Device Cisco Unified Communications Directory
PC PSTN Number Location
Name Manager Number

US, San Jose (SJC)

+1 408 5550000
US, Tampa (TPA)
+1 813 5550000
Australia, Sydney
+61 2 70100000
(SYD)
911
US, Emergency
+44 20
PC-3 PSTN-CIPC 10.1.99.5 UK, London (LON)
79460000
UK, Manchester
+44 161
(MAN)
4960000
Australia, Sydney
+61 2 70100000
(SYD)
999
UK, Emergency

Step 1
On PC-1, open Google Chrome and navigate to Cisco Unified Communications Manager Administration
(https://10.1.5.5/ccmadmin). Log in using Administrator for the username and C0ll@B for the password.

Step 2
Select Device > Phone, click Find and observe if Cisco IP Communicator phones are displayed. If phones are
not displayed wait a while for the automation system to finish configuring Cisco Unified Communicacitons
Manager and then click Find again. Continue only when phones are displayed.
Step 3
On PC-1, start Cisco IP Communicator and configure it with the following settings:
Device Name: US-CIPC-1
TFTP Servers: 10.1.5.5

Step 4
On PC-4, start Cisco IP Communicator and configure it with the following settings:

Device Name: UK-CIPC-1

TFTP Servers: 10.1.5.5
Step 5
On PC-3, start Cisco IP Communicator and configure it with the following settings:

Device Name: PSTN-CIPC

TFTP Servers: 10.1.99.5
Task 2: Review the Existing Configuration
Activity
The initial configuration includes a simple dial plan with preconfigured endpoints.

You will explore the relevant preconfigured items and perform simple test calls between the two internal phones
(US-CIPC-1 running on PC-1 and UK-CIPC-1 running on PC-4).

Existing Partitions and CSSs

Globalized call routing requires lots of partitions and CSSs. The initial configuration already includes the required
partitions as shown in the table.

Partition Name Description

DN This partition includes the directory numbers of the phones.

This partition includes the translation patterns for globalizing numbers that are used in PSTN calls that have been
USToE164 dialed using US PSTN dial rules (with PSTN access code 9, national access code 1, and international access code
011).

This partition includes the translation patterns for globalizing numbers that are used in PSTN calls that have been
UKToE164 dialed using UK PSTN dial rules (with PSTN access code 9, national access code 0, and international access code
00).

PSTNInternational This partition includes the \+.! route pattern that is used to route calls to the PSTN in globalized format.

USEmergency This partition includes the emergency route patterns that are used in the US sites.

UKEmergency This partition includes the emergency route patterns that are used in the UK sites.

SJCGWLocalizeCd This partition includes called-party transformation patterns for egress at the SJC gateway.

SJCGWLocalizeCn This partition includes calling-party transformation patterns for egress at the SJC gateway.
Partition Name Description

LONGWLocalizeCd This partition includes called-party transformation patterns for egress at the LON gateway.

LONGWLocalizeCn This partition includes calling-party transformation patterns for egress at the LON gateway.

This partition includes the calling-party transformation patterns that modify the calling-party number of inbound PSTN
USPhLocalize
calls that are sent to a US phone.

This partition includes the calling-party transformation patterns that modify the calling-party number of inbound PSTN
UKPhLocalize
calls that are sent to a UK phone.

You will focus on basic globalized call routing in a single-cluster deployment with just two sites, which are
located in different countries. In a larger deployment that uses additional, dial plan-related features such
as Cisco Unified Device Mobility or Cisco Extension Mobility, TEHO, and AAR, the implementation is more
complex. Refer to the “Call Control” section of the Preferred Architecture for Cisco Collaboration 12.x
Enterprise On-Premises Deployments, CVD document (https://www.cisco.com/c/en/us/td/docs/solutions
/CVD/Collaboration/enterprise/12x/120/collbcvd/control.pdf) for more detailed information.

Basic globalized call routing does not include or require all the components that are described in the
preferred architecture. Therefore, you will use only a subset of the partitions and CSSs that are listed in
the preferred architecture. For your convenience, the naming conventions are the same as you would see
in the preferred architecture.

The initial configuration includes the CSSs shown in the table.

Contains Assigned to
CSS Name Description
Partitions Devices

Gateways
DN This CSS allows gateways to route calls to internal directory numbers. DN (SJC and
LON)

This CSS applies the called-party transformation patterns to outbound PSTN calls SJC
SJCGWLocalizeCd SJCGWLocalizeCd
that use the SJC gateway. Gateway

This CSS applies the calling-party transformation patterns to outbound PSTN calls SJC
SJCGWLocalizeCn SJCGWLocalizeCn
that use the SJC gateway. Gateway

This CSS applies the called-party transformation patterns to outbound PSTN calls LON
LONGWLocalizeCd LONGWLocalizeCd
that use the LON gateway. Gateway

This CSS applies the calling-party transformation patterns to outbound PSTN calls LON
LONGWLocalizeCn LONGWLocalizeCn
that use the LON gateway. Gateway

DN
This CSS allows SJC phones to access internal directory numbers and PSTN USToE164 SJC Phone
SJCInternational
patterns (including emergency). This CSS is applied as a line CSS to the phones. USEmergency Lines
PSTNInternational

DN
This CSS allows LON phones to access internal directory numbers and PSTN UKToE164 LON Phone
LONInternational
patterns (including emergency). This CSS is applied as a line CSS to the phones. UKEmergency Lines
PSTNInternational

This CSS applies the calling-party transformation patterns to inbound PSTN calls
when they are sent to a US phone. These transformation patterns control how a
USPhLocalize calling-party number is shown on the phone display. This CSS is applied as the USPhLocalize SJC Phone
Calling Party Transformation CSS in the Number Presentation Transformation
part of the phone device-level configuration.

This CSS applies the calling-party transformation patterns to inbound PSTN calls
when they are sent to a US phone. These transformation patterns control how a
UKPhLocalize calling-party number is shown on the phone display. This CSS is applied as the UKPhLocalize LON Phone
Calling Party Transformation CSS in the Number Presentation Transformation
part of the phone device-level configuration.

Step 1
 On PC-1, open Chrome or Firefox and navigate to https://10.1.5.5/ccmadmin (Cisco Unified CM
Administration). Log in using Administrator for the username and C0ll@B for the password.

Step 2
Select Call Routing > Class of Control > Calling Search Space. Then click Find to view a list of all Calling
Search Spaces that have been preconfigured as already discussed.

Step 3
Select Call Routing > Class of Control > Partition. Then click Find to view a list of all Partitions that have been
preconfigured as already discussed.

The partitions Directory URI, Global Learned E164 Numbers, Global Learned E164 Patterns, Global
Learned Enterprise Numbers, and Global Learned Enterprise Patterns exist by default and you will not
use them.
Existing Device Pools
The initial configuration of this lab already includes device pools: one for the SJC site and one for the LON site.
Each device pool is preconfigured with a site-specific location, region, and date and time group.

Step 4
Explore the existing device pools by browsing the two entries under System > Device Pool.

Existing Gateways
The initial configuration includes the PSTN gateways. The gateways (an H.323 gateway for the SJC site and a SIP
gateway for the LON site) are configured with the destination addresses (the PSTN Cisco Unified Communications
Manager that simulates the PSTN) and the DN CSS is applied to both gateways.

Step 5
Explore the existing H.323 gateway under Device > Gateway > 10.1.99.5.

Step 6
Explore the existing SIP gateway under Device > Trunk > LON-GW.
Existing Route Groups and Route Lists
The initial configuration of this lab includes two route groups—one for each site. The SJC-H323_RG includes the
H.323 PSTN gateway that is located at the San Jose site and the LON-SIP_RG includes the SIP PSTN gateway
that is located at the London site.

The initial configuration also includes a route list, called RL_PSTN. This route list has the Standard Local Route
Group as its only member.

Step 7
Explore the existing route list under Call Routing > Route/Hunt > Route List.

Step 8
Explore the existing Route Groups under Call Routing > Route/Hunt > Route Group.
Existing Phones
The initial configuration of this lab already includes the phones: one for the SJC site and one for the LON site. You
registered these phones earlier.

Each phone is configured with one directory number. The SJC phone (US-CIPC-1) is configured with directory
number 11001 in partition DN and its line CSS is set to SJCInternational. The LON phone (UK-CIPC-1) is
configured with directory number 21001 in partition DN and its line CSS is set to LONInternational. Both phones
are configured with external phone number masks, which if applied, show the phone number in +E.164 format.
Each phone has four speed dials: one to reach a local PSTN number, one to reach a national PSTN number, one
to reach an international PSTN destination, and one for emergency calls. The speed dial destination numbers are
configured in the format that is typically used for PSTN calls in the appropriate countries based on the applicable
PSTN dial rules.

Step 9
Explore the existing phones and their associated lines and speed dials by browsing to the phones under Device
> Phone.

Step 10
Establish a test call from US-CIPC-1 to UK-CIPC-1 by dialing 21001. Keep the call open for a few seconds, then
drop the call.

Step 11
Establish a test call from UK-CIPC-1 to US-CIPC-1 by dialing 11001. Keep the call open for a few seconds, then
drop the call.

Task 3: Configure Inbound PSTN Calls to the SJC Site

Activity
You can test calls from the PSTN to both of your sites (SJC and LON) using the PSTN phone. Refer to the PSTN
Numbers and Dial Rules job aid for details about the PSTN DID ranges, dial rules, and use of the PSTN phone.

You will configure the required dial plan elements to allow inbound PSTN calls to the SJC site. Specifically, you will
have to manipulate the received called number so that it matches the internal directory number. Your DID range is
+1 408 5551XXX and the associated internal directory number range is 11XXX. The PSTN delivers the called-party
number to the SJC gateway using 10 digits and no TON.

You will first place a test call to see that the call does not work. The call does not work because the delivered
called-party number does not match the internally used directory number. Then you will change the received 10
digits by first stripping the leading 7 digits and then prefixing 11. You will apply this digit manipulation at the ingress
gateway (SJC gateway).

Step 1
From the PC-3, use the first line of the PSTN phone (labeled SJC-local) and dial 4085551001. The call fails.
Step 2
On PC-1 open the Cisco Unified CM Administration, select Device > Gateway; then click the H.323 gateway
name to open the configuration page.

Step 3
Scroll to the Incoming Called Party Settings section and enter the below information into the Unknown Number
fields:

Prefix: 11
Strip Digits: 7

Make sure that you make the changes under the Incoming Called Party Settings, and not the Incoming
Calling Party Settings.
Step 4
Repeat the test call from the SJC local line of the PSTN phone to US-CIPC-1 (dial 4085551001). This time the
call works. The calling-party number is shown as a 10-digit number (4085550000).

If the call still fails, click Apply Config on the Gateway, then Reset.

Configure Globalization of the Calling-Party Number

When implementing globalized call routing, the calling number of an inbound PSTN call must be changed to
+E.164 format at call ingress.

You will configure the SJC gateway to add the required prefixes so that all inbound calling-party numbers are
globalized to +E.164 format. The PSTN delivers local calling-party numbers in 10-digit format with the TON
subscriber, national calling-party numbers in 10-digit format with the TON national, and international calling-party
numbers in E.164 format with the TON international.

Step 5
On the configuration page of the SJC H.323 PSTN gateway, implement digit manipulation of incoming calling-
party numbers as follows:

Number Type > National Number > Prefix: +1

Number Type > International Number > Prefix: +
Number Type > Subscriber Number > Prefix: +1
Step 6
Place the following test calls from the PSTN phone and make sure that the calling-party number is always shown
in +E.164 format:

From PSTN phone line 1 (labeled SJC-local): 4085551001

From PSTN phone line 2 (labeled SJC-ntl): 14085551001
From PSTN phone line 3 (labeled SJC-intl): 001114085551001

The calling-party number for the first call is +14085550000.

The calling-party number for the second call is +18135550000.

The calling-party number for the third call is +61270100000.

Configure Localization of the Calling-Party Number

You successfully configured globalization of the calling-party number at call ingress. Now you can control how the
calling-party number should be displayed on the receiving phone; you can configure localization at call egress.

You want to show local and national callers with a 10-digit calling-party number on phones that are located at the
SJC site. International callers should be shown in +E.164 format.

Based on these requirements, you will have to configure a calling-party transformation pattern that changes the
calling-party number from +1408XXXXXXX to 408XXXXXXX. Then you have to apply the calling-party
transformation to the SJC phone (US-CIPC-1).

The partitions and CSS for the calling-party transformation already exist. You have to assign the partition
to the pattern and apply the corresponding CSS to the phone.

Step 7
Choose Call Routing > Transformation > Transformation Pattern > Calling Party Transformation Pattern
and add the following pattern:

Pattern: \+1.XXXXXXXXXX
Partition: USPhLocalize
Description: display inbound US PSTN calls on US phones
Discard Digits: PreDot
Step 8
Go to the configuration page of the SJC phone (US-CIPC-1) and apply the USPhLocalize CSS as the Calling
Party Transformation CSS for the remote number.

You must uncheck the check box Use Device Pool Calling Party Transformation CSS (Device
Mobility Related Information) before you can set the Calling Party Transformation CSS.

Step 9
Place the following test calls from the PSTN phone and make sure that the calling-party number is now shown in
localized format:

From PSTN phone line 1: 4085551001

From PSTN phone line 2: 14085551001
From PSTN phone line 3: 001114085551001

The calling-party number for the first call is 4085550000.

 The calling-party number for the second call is 8135550000.

The calling-party number for the third call is +61270100000.

Step 10
On the US-CIPC-1 phone, click the directories button and look at the received calls.

If you did not answer any of the test calls, look at the missed calls directory instead of the received calls.

Conclusion
You configured globalization of calling-party numbers for inbound PSTN calls at call ingress at the SJC gateway.
You customized how the calling-party numbers are shown at the target phone by localizing from +E.164 format.

Although the local and national inbound PSTN callers were shown as 10-digit numbers on the phone display, they
are stored in the (pretransformed) +E.164 format. This approach is extremely useful if, for example, you use a
different gateway for callback. The number is stored in a universal format that can be routed to any egress
gateway. At the egress gateway, you can then modify the number as needed by the chosen egress gateway.

Task 4: Configure Inbound PSTN Calls to the LON Site

Activity
You can test calls from the PSTN to both of your sites (SJC and LON) using the PSTN phone. Refer to the PSTN
Numbers and Dial Rules job aid for details about the PSTN DID ranges, dial rules, and the usage of the PSTN
phone.

In this task, you will configure the required dial plan elements to allow inbound PSTN calls to the LON site.
Specifically, you will have to manipulate the received called number so that it matches the internal directory
number. Your DID range is +44 20 79460XXX and the associated internal directory number range is 21XXX. The
PSTN delivers the called-party number to the LON gateway using 10 digits. There cannot be a TON because the
gateway uses the SIP protocol, which does not support TON.

You will first place a test call to see that the call does not work. The call does not work because the delivered
called-party number and the internally used directory number do not match. You will then change the received 10
digits by first stripping the leading 7 digits and then prefixing 21. You will apply this digit manipulation at the ingress
gateway (LON gateway).

Step 1
From PC-3, try to place a local call to UK-CIPC-1. Use the fifth line of the PSTN phone (labeled LON-local) and
dial 79460001 on the keypad of the PSTN phone. The call fails.
Step 2
From Cisco Unified CM Administration, select Device > Trunk and click the LON-GW trunk.

Step 3
Configure digit manipulation of the Incoming Called Party Settings as follows:

Prefix: 21
Strip Digits: 7

Step 4
Repeat the test call from the LON local line of the PSTN phone to UK-CIPC-1 (dial 79460001). This time the call
works. The calling-party number is shown as an E.164 number (442079460000).
Configure Globalization of the Calling-Party Number
When implementing globalized call routing, the calling number of an inbound PSTN call must be changed to
+E.164 format at call ingress.

You will configure the LON gateway to add the required prefixes so that all inbound calling-party numbers are
globalized to +E.164 format. The PSTN delivers all calling-party numbers in E.164 format.

Step 5
On the configuration page of the LON-GW trunk, implement digit manipulation for the Incoming Calling Party
Settings as follows:

Prefix: +
Strip Digits: 0

Step 6
Place the following test calls from the PSTN phone and make sure that the calling-party number is always shown
in +E.164 format:

From PSTN phone line 5: 79460001

From PSTN phone line 6: 02079460001
From PSTN phone line 7: 0011442079460001

The calling-party number for the first call is +442079460000.

The calling-party number for the second call is +441614960000.

The calling-party number for the third call is +61270100000.

Configure Localization of the Calling-Party Number
You successfully configured globalization of the calling-party number at call ingress. Now you are able to control
how the calling-party number should be displayed on the receiving phone; you should now configure localization at
call egress.

Local callers should be displayed as an 8-digit calling-party number on phones that are located at the LON site.
National callers should be shown with a 10-digit calling-party number, and international callers should be shown in
+E.164 format.

Based on these requirements, you need two calling-party transformation patterns: one pattern that changes
+4420XXXXXXXX to XXXXXXXX and another pattern that changes +44XXXXXXXXXX to XXXXXXXXXX. For your
convenience, the second pattern is already preconfigured, so you will only configure the first transformation pattern.
Then you will apply the calling-party transformation to the LON phone (UK-CIPC-1). This time, you will apply the
transformation CSS via the device pool.

The partitions and CSS for the calling-party transformation already exist. You have to assign the partition
to the pattern and apply the corresponding CSS to the phones (via the device pool). Once you apply the
CSS to the device pool, the preconfigured second pattern will also take effect.

Step 7
Select Call Routing > Transformation > Transformation Pattern > Calling Party Transformation Pattern and
add the following pattern:

Pattern: \+4420.XXXXXXXX
Partition: UKPhLocalize
Description: display inbound local PSTN calls on LON phones
Discard Digits: PreDot
Step 8
Select System > Device Pool, click Find, and then click the LON device pool.

Step 9
In the Device Mobility Related Information section, select the UKPhLocalize CSS as the Calling Party
Transformation CSS. Click Save, and then click Reset.

You have to reset the device pool to have the changes take effect.

Step 10
Place the following test calls from the PSTN phone and make sure that the calling-party number is now shown in
localized format:

From PSTN phone line 5 (labeled LON-local): 79460001

From PSTN phone line 6 (labeled LON-ntl): 02079460001
From PSTN phone line 7 (labeled LON-intl): 0011442079460001

The calling-party number for the first call is 79460000.

The calling-party number for the second call is 1614960000.

The calling-party number for the third call is +61270100000.

Step 11
On the UK-CIPC-1 phone, click the directories button and look at the received calls.

If you did not answer any of the test calls, look at the missed calls directory instead of the received calls.
Conclusion
You configured globalization of calling-party numbers for inbound PSTN calls at call ingress at the LON gateway.
You customized how the calling-party numbers are shown at the target phone by localizing from +E.164 format.

Although the local and national inbound PSTN callers were shown as 8- and 10-digit numbers on the phone
display, they are stored in the (pretransformed) +E.164 format. This approach is extremely useful if, for example,
you use a different gateway for callback. The number is stored in a universal format that can be routed to any
egress gateway. At the egress gateway, you can then modify the number as needed by the chosen egress
gateway.

Task 5: Configure Outbound PSTN Calls at the SJC Site

Activity
In this task, you will configure the required dial plan elements to allow outbound PSTN calls from the SJC site to
the PSTN. Specifically, you will have to configure a \+! route pattern that points to a route list. The route list will
refer to the standard Local Route Group. This standard Local Route Group is then replaced with an actual route
group, which is determined based on the device pool of the calling device. Therefore, you will have to set the Local
Route Group in the device pools.

Once the route pattern, route list, and the Local Route Groups are in place, you can route calls to the PSTN if the
called-party number is in +E.164 format.

End users typically want to be able to dial in the same way they always dial. They want to be able to use PSTN
access codes, national and international access codes, and so on, and they do not want to be forced to manually
dial in +E.164 format. Therefore, you will have to configure translation patterns that globalize such localized call
ingress to +E.164 format.

After the translation, the call is then routed to the local gateway based on the \+! route pattern, the route list that
refers to the standard Local Route Group, and the Local Route Group that is configured at the device pool of the
calling device.

After this process, you will configure localization at call egress according to the PSTN requirements at the chosen
egress gateway. This localization is done by called-party transformation patterns, which you will apply to the egress
gateway.

The requirements for the calling-party number are similar. First you have to globalize the internally used directory
numbers to +E.164 format. This globalization of the calling-party number is done in the translation patterns that
globalize the called number. You will apply the external phone number mask to the calling-party number in all your
translation patterns. After the egress gateway has been chosen, the calling-party number can be localized per the
requirements of the egress gateway. The location of the calling-party numbers is also performed by transformation
patterns, this time calling-party transformation patterns, which are applied to the egress gateway.
In summary, you will perform the following procedure:
Configure a \+! route pattern that refers to a route list that is configured with the standard Local Route Group.
Set the Local Route Group in device pools.
Configure translation patterns to globalize localized call ingress. These translation patterns globalize both the
called- and the calling-party number.
Configure called- and calling-party transformation patterns for localized call egress and apply them to the
egress gateway.

Configure Call Routing for Globalized Patterns

You will configure the \+! route pattern and complete the configuration of the Local Route Group feature.

Step 1
Select Call Routing > Route/Hunt > Route Pattern, click Add New, and configure the new route pattern as
follows:

Route Pattern: \+!

Route Partition: PSTNInternational
Description: globalized PSTN patterns
Gateway/Route List: RL_PSTN

The route list RL_PSTN already exists and is configured to use the Standard Local Route Group.

Step 2
Select System > Device Pool, and then click SJC.
Step 3
Under the Local Route Group Settings section, select the SJC-H323_RG from the drop-down list for Standard
Local Route Group.

The LON device pool is already preconfigured with route group LON-SIP_RG.

Configure Globalization of Localized Ingress

You will configure the translation patterns that are needed to allow users to continue dialing per the PSTN dial
rules. You will create the translation pattern for local calls. This pattern will translate the called pattern
9408XXXXXXX to +1408XXXXXXX and it will apply the external phone number mask that is configured on the US
phone lines (+1408555XXXX) to the calling-party number.

Translation patterns for globalization of national and international calls are already preconfigured. The
translation pattern for national calls translates from 91XXXXXXXXXX to +1XXXXXXXXXX. The translation
pattern for international calls translates the prefix 9011 to a plus (+) sign.

Step 4
Select Call Routing > Translation Pattern, click Add New, and use the following settings to configure the new
Translation Pattern:
Translation Pattern: 9.408XXXXXXX
Partition: USToE164
Description: globalize US local calls
Use Originator’s Calling Search Space: Check this check box
Do Not Wait For Interdigit Timeout On Subsequent Hops: Check this check box.
Calling Party Transformations > Use Calling Party’s External Phone Number Mask: Check this check
box.
Called Party Transformations > Discard Digits: PreDot
Called Party Transformations > Prefix Digits (Outgoing Calls): +1
Configure Localized Call Egress
At this stage, you have configured everything that is needed to route the call to the egress gateway. However, this
PSTN has very specific requirements on how you have to deliver the called- and calling-party numbers.

The called-party number must be delivered as a 10-digit number if it is a local call.

The called-party number must be delivered with a national access code 1, followed by a 10-digit number if it is a
national call.
The called-party number must be delivered with an international access code 011, followed by the E.164
number if it is an international call.
For all three types of calls, you must not set the TON for the called-party number.
The calling-party number must be delivered as a 10-digit number.
You must not set the TON for the calling-party number.

You will configure the called- and calling-party transformations that change the called- and calling-party numbers
from +E.164 format per the requirements previously listed. Then you will apply the transformation patterns to the
egress gateway.

You will only have to configure the called-party transformation pattern for local PSTN calls. The called-
party transformation patterns for national and international calls are preconfigured.

Step 5
Select Call Routing > Transformation > Transformation Pattern > Called Party Transformation Pattern.
Click Add New and use the following settings to configure the new transformation pattern:

Pattern: \+1.408XXXXXXX
Partition: SJCGWLocalizeCd
Description: localize local calls at SJC egress
 Discard Digits: PreDot
Called Party Number Type: Unknown
Called Party Numbering Plan: Unknown

Step 6
Select Device > Gateway, and click 10.1.99.5 (SJC PSTN GW H323). Then set the Called Party Transformation
CSS of outbound calls to SJCGWLocalizeCd.

You must uncheck the Use Device Pool Called Party Transformation CSS check box. If this check
box is checked and a called-party transformation CSS is configured at the gateway, the called-party
transformation CSS setting of the device pool is applied and the locally configured called-party
transformation CSS is ignored.
Step 7
Place the following test calls from the SJC phone (US-CIPC-1) to the PSTN and make sure that the call is
delivered to the correct line on the PSTN phone. Also check the calling-party number that is shown on the PSTN
phone.

Call a local destination (dial 94085550000 or use the speed dial labeled SJC-PSTN).
Call a national destination (dial 918135550000 or use the speed dial labeled TPA-PSTN).
Call a local destination (dial 901161270100000 or use the speed dial labeled SYD-PSTN).

The first call is delivered to the first line (labeled SJC-local).

The first call is delivered to the first line (labeled SJC-ntl).

The first call is delivered to the first line (labeled SJC-intl).

The calling-party number of all three calls is 99999999, which indicates that the calling-party number was not
delivered as expected by the PSTN.

Step 8
Select Call Routing > Transformation > Transformation Pattern > Calling Party Transformation Pattern.
Click Add New and use the following settings to configure the new transformation pattern:

Pattern: \+1.4085551XXX
Partition: SJCGWLocalizeCn
Description: localize calling number at SJC egress
Discard Digits: PreDot
Calling Party Number Type: Unknown
Calling Party Numbering Plan: Unknown
Step 9
Select Device > Gateway, click 10.1.99.5 (SJC PSTN GW H323), and then set the Calling Party Transformation
CSS of outbound calls to SJCGWLocalizeCn.

You must uncheck the Use Device Pool Calling Party Transformation CSS check box. If this check
box is checked and a calling-party transformation CSS is configured at the gateway, the calling-party
transformation CSS setting of the device pool is applied and the locally configured calling-party
transformation CSS is ignored.
Step 10
Repeat the following test calls from the SJC phone (US-CIPC-1) to the PSTN and make sure that the calling-
party number that is shown on the PSTN phone is now delivered as a 10-digit number.

Call a local destination (dial 94085550000 or use the speed dial labeled SJC-PSTN).
Call a national destination (dial 918135550000 or use the speed dial labeled TPA-PSTN).
Call a local destination (dial 90114085550000 or use the speed dial labeled SYD-PSTN).

In real life, the PSTN would have to inflate the calling-party number to E.164 format when delivering the
call to another country as is the case with the third test call. Here, it is sufficient if all three calls deliver
the calling-party number as a 10-digit number.

The calling-party number of all three calls is 4085551001, which indicates that the calling-party number was
delivered to the PSTN as expected (as a 10-digit number).

Configure Emergency Dialing

At this stage, you have configured local, national, and international outbound PSTN calls for the SJC site.

Now you will implement emergency calls.

Specifically, you will configure an emergency route pattern 9.911 and try to apply the external phone number mask
to the calling-party number. The assumption is that the calling-party transformation pattern that you just applied
successfully in the previous steps will also work for emergency calls.

However, you will see that there is a problem with the calling-party number modification. The issue is that the
calling-party number transformation patterns are checked against the so-called pretransformed number, which is
the number before a route pattern or route list modified it.
The previous calls were going through a translation pattern and the logic there is a bit different. A translation
causes a new lookup request to the call-routing table after the modification. This new lookup request (after the
translation of called- and calling-party numbers) is treated as if it is a new (initial) call. Therefore, the result of the
translation pattern digit manipulation is considered to be the pretransformed number according to the called- and
calling-party transformation CSS logic that is applied to an egress device. This situation explains why your calling-
party transformation pattern \+1.408XXXXXXX found a match in your local, national, and international outbound
PSTN calls. The original calling-party number of 11001 was changed to +140855511001 by the translation patterns
and, therefore, the “new” call request for the translated called-party number had a pretransformed calling-party
number of +140855511001 and not 11001.

When you inflate the directory number to +E.164 format at a translation pattern, the pretransformed number is
11001. Therefore, you will have to configure an extra calling-party transformation pattern that changes 11001 to a
10-digit number (as required by the PSTN).

You will perform the following procedure:

1. Configure an emergency route pattern (9.999) where you apply the external phone number mask to the calling-
party number.
2. Place a test call to the emergency number. The call will be correctly routed to the destination.
3. Identify that the calling-party number is not correct.
4. Fix the problem by adding another calling-party transformation pattern that matches the internal directory
number.

Step 11
Select Call Routing > Route/Hunt > Route Pattern, click Add New, then configure the new route pattern for
emergency calls as follows:

Route Pattern: 9.911

Route Partition: USEmergency
Description: US emergency pattern
Gateway/Route List: RL_PSTN
Urgent Priority: Check this check box
Calling Party Transformations > Use Calling Party’s External Phone Number Mask: Check this check
box.
Called Party Transformations > Discard Digits: PreDot
Step 12
 Place a call from the SJC phone (US-CIPC-1) to the PSTN emergency number by dialing 9911 or by using the
speed dial labeled Emergency. Make sure that the call is received on line 4 (labeled SJC-emergency) at the
PSTN phone. The calling-party number should be displayed as a 10-digit number, but is shown as 99999999,
which indicates that it was not sent to the PSTN in the expected 10-digit format.

A second emergency pattern 911 is already preconfigured. You can dial 9911 or 911; the result is the
same: the call is routed correctly, but the calling-party number is incorrectly sent to the PSTN gateway.

Step 13
Select Call Routing > Transformation > Transformation Pattern > Calling Party Transformation Pattern,
click Add New, and then configure the transformation pattern as follows:

Pattern: 1.1XXX
Partition: SJCGWLocalizeCn
Description: set calling number at SJC egress if not translated
Discard Digits: PreDot
Prefix Digits: 408555
Calling Party Number Type: Unknown
Calling Party Numbering Plan: Unknown

Step 14
Place a call from the SJC phone (US-CIPC-1) to the PSTN emergency number by dialing 911 or 9911 or by using
the speed dial labeled Emergency. Make sure that the call is received on line 4 (labeled SJC-emergency) at the
PSTN phone. Check the calling-party number. This time it is correct (4085551001).

Conclusion
You configured globalization of called- and calling-party numbers at call ingress for outbound PSTN calls at the
SJC site. Then you configured localization of called- and calling-party numbers at call egress for outbound PSTN
calls.

You determined that transformation patterns match on the pretransformed numbers, which are the numbers as they
looked at the beginning of a call request, before route pattern or route list digit manipulation settings are applied.
When you use a translation pattern, a new lookup request is generated after the translation pattern digit
manipulation settings have been applied and therefore the result of the digit manipulation is the (new)
pretransformed number for the newly generated lookup request.

Task 6: Configure Outbound PSTN Calls at the LON Site

Activity
You will configure the required dial plan elements to allow outbound PSTN calls from the LON site to the PSTN.

Everything that you need for routing globalized destination patterns is already in place from the previous task. You
already have a \+! route pattern that points to a route list. The route list refers to the standard Local Route Group.
This standard Local Route Group is then replaced by an actual route group, which is determined based on the
device pool of the calling device. The Local Route Group in the LON device pool is already preconfigured.

Now you need to add the translation patterns that allow the end users to use the UK PSTN dial rules: place calls
using PSTN access codes, national, and international access codes. The translation patterns will globalize such
localized call ingress to +E.164 format and will also inflate the calling-party number to +E.164 format.

Then you will have to configure localization at call egress based on the PSTN requirements at the egress gateway
(in this case, the LON SIP PSTN gateway).

Finally, you will configure the necessary route pattern and calling-party transformation pattern to allow emergency
calls from the LON site.

Configure Globalization of Localized Ingress

You will configure the translation patterns that are needed to allow users to continue dialing per the PSTN dial
rules. You will create the translation pattern for local calls. This pattern will translate the called pattern 9XXXXXXXX
to +44420XXXXXXXX and it will apply the external phone number mask that is configured on the UK phone lines
(+442079460XXX) to the calling-party number.

Translation patterns for globalization of national and international calls are already preconfigured. The
translation pattern for national calls translates from 90XXXXXXXXXX to +44XXXXXXXXXX. The
translation pattern for international calls translates the prefix 900 to a + sign.

Step 1
Select Call Routing > Translation Pattern, click Add New, and then configure the translation pattern with the
following settings:

Translation Pattern: 9.XXXXXXXX

Partition: UKToE164
Description: globalize UK local calls
Use Originator’s Calling Search Space: Check this check box
Do Not Wait For Interdigit Timeout On Subsequent Hops: Check this check box
Calling Party Transformations > Use Calling Party’s External Phone Number Mask: Check this check
box
Called Party Transformations > Discard Digits: PreDot
Called Party Transformations > Prefix Digits (Outgoing Calls): +4420
Configure Localized Call Egress

At this stage, you have configured everything that is needed to route the call to the egress gateway. However, this
PSTN has very specific requirements on how you have to deliver the called- and calling-party numbers.
The called-party number must be delivered in E.164 format for all types of calls (local, national, international).
The calling-party number must be delivered as a 10-digit number.

The LON gateway is a SIP gateway. SIP does not support TON, so setting the TON is not an option on this
gateway.

You will configure the called- and calling-party transformation that changes the called- and calling-party numbers
from +E.164 format per the requirements that were listed previously. Then you will apply the transformation
patterns to the egress gateway.

Step 2
Select Call Routing > Transformation > Transformation Pattern > Called Transformation Pattern, click Add
New, and then configure the transformation pattern with the following settings:

Pattern: \+.!
Partition: LONGWLocalizeCd
Description: localize all calls at LON egress
Discard Digits: PreDot
Called Party Number Type: Unknown
Called Party Numbering Plan: Unknown

Step 3
Select Device > Trunk, click Find, click the LON-GW trunk, and then set the Called Party Transformation CSS
of outbound calls to LONGWLocalizeCd.
 You must uncheck the Use Device Pool Called Party Transformation CSS check box. If this check
box is checked and a called-party transformation CSS is configured at the gateway, the called-party
transformation CSS setting of the device pool is applied and the locally configured called-party
transformation CSS is ignored.

Step 4
Place the following test calls from the LON phone (UK-CIPC-1) to the PSTN and make sure that the call is
delivered to the correct line on the PSTN phone. Also check the calling-party number that is shown on the PSTN
phone.

Call a local destination (dial 979460000 or use the speed dial labeled LON-PSTN).
Call a national destination (dial 901614960000 or use the speed dial labeled MAN-PSTN).
Call an international destination (dial 90061270100000 or use the speed dial labeled SYD-PSTN).

The first call is delivered to the fifth line (labeled LON-local).

The first call is delivered to the sixth line (labeled LON-ntl).

The first call is delivered to the seventh line (labeled LON-intl).

The calling-party number of all three calls is 99999999, which indicates that the calling-party number was not
delivered as expected by the PSTN.

Step 5
Select Call Routing > Transformation > Transformation Pattern > Calling Party Transformation Pattern,
click Add New, and then configure the transformation pattern as follows:

Pattern: \+44.2079460XXX
 Partition: LONGWLocalizeCn
Description: localize calling number at LON egress
Discard Digits: PreDot
Calling Party Number Type: Unknown
Calling Party Numbering Plan: Unknown

Step 6
Select Device > Trunk, click the LON-GW trunk, and then set the Calling Party Transformation CSS of outbound
calls LONGWLocalizeCn.

You must uncheck the Use Device Pool Calling Party Transformation CSS check box. If this check
box is checked and a calling-party transformation CSS is configured at the gateway, the calling-party
transformation CSS setting of the device pool is applied and the locally configured calling-party
transformation CSS is ignored.
Step 7
Repeat the following test calls from the LON phone (UK-CIPC-1) to the PSTN and make sure that the call is
delivered to the correct line on the PSTN phone. Also check the calling-party number that is shown on the PSTN
phone.

Call a local destination (dial 979460000 or use the speed dial labeled LON-PSTN).
Call a national destination (dial 901614960000 or use the speed dial labeled MAN-PSTN).
Call an international destination (dial 90061270100000 or use the speed dial labeled SYD-PSTN).

If the calling number is still showing incorrectly, reset the LON_GW Trunk.

In real life, the PSTN would have to inflate the calling-party number to E.164 format when delivering the
call to another country as is the case with the third test call. Here, it is sufficient if all three calls deliver
the calling-party number as a 10-digit number.

The calling-party number of all three calls is 2079460001, which indicates that the calling-party number was
delivered to the PSTN as expected (as a 10-digit number).

Configure Emergency Dialing

At this stage, you have configured local, national, and international outbound PSTN calls for the SJC site.

Emergency route patterns and the required calling-party transformation pattern that matches the pretransformed
number (21XXX) and translates it to a 10-digit number are preconfigured.

Now you have to test emergency dialing.

Step 8
Place a call from the LON phone (UK-CIPC-1) to the PSTN emergency number by dialing 9999 or by using the
speed dial labeled Emergency. Make sure that the call is received on line 8 (labeled LON-emergency) at the
PSTN phone. The calling-party number is displayed as a 10-digit number (2079460001).

A second emergency pattern 999 is already preconfigured. You can dial 9999 or 999; the result is the
same.

Conclusion

You configured globalization of called- and calling-party numbers at call ingress for outbound PSTN calls at the
LON site. Then you configured localization of called- and calling-party numbers at call egress for outbound PSTN
calls.

Your cluster is now configured with globalized call routing. You could now easily implement a dial plan-related
feature that results in calls being sent out through a gateway that is located in a different country. Examples of such
features are TEHO, Cisco Unified Device Mobility, Cisco Extension Mobility, and AAR.

Although the digit manipulation requirements at egress are different per country in such a case, the existing digit
manipulation configuration will be sufficient to handle these types of calls.