Cisco Unified Communications Manager Features and Services Guide, Release 7.0(1)
Calling Party Normalization (Revised 03/25/2010)
Downloads: This chapterpdf (PDF - 477.0KB) The complete bookPDF (PDF - 16.31MB) | Feedback

Calling Party Normalization

Table Of Contents

Calling Party Normalization

Introducing Calling Party Normalization

Globalizing the Calling Party Number

Localizing the Calling Party Number

Mapping the Global Party Calling Number to Its Local Variant

System Requirements

Interactions and Restrictions

Interactions

Globalizing and Localizing Calling Party Numbers for Transferred Calls

Globalizing and Localizing Calling Party Numbers for Forwarded Calls

Bulk Administration Tool

Call Detail Records

Cisco Unified Communications Manager CDR Analysis and Reporting

Cisco Extension Mobility

Device Mobility

Restrictions

Installing and Activating Calling Party Normalization

Configuring Calling Party Normalization

Configuration Checklist for Calling Party Normalization

Setting the Service Parameters for Calling Party Normalization

Configuring the Calling Party Number Type

Configuring Prefixes to Globalize the Calling Party Number

Applying the Calling Party Transformation CSS to Localize the Calling Party Number

Providing Information to End Users

Related Topics


Calling Party Normalization


This chapter provides the following information about calling party normalization:

Introducing Calling Party Normalization

Globalizing the Calling Party Number

Localizing the Calling Party Number

Mapping the Global Party Calling Number to Its Local Variant

System Requirements

Interactions and Restrictions

Installing and Activating Calling Party Normalization

Configuring Calling Party Normalization

Configuration Checklist for Calling Party Normalization

Providing Information to End Users

Related Topics

Introducing Calling Party Normalization

In line with E.164 standards, calling party normalization enhances the dialing capabilities of some phones and improves call back functionality when a call is routed to multiple geographical locations; that is, the feature ensures that the called party can return a call without needing to modify the directory number in the call log directories on the phone. Additionally, calling party normalization allows you to globalize and localize phone numbers, so the appropriate calling number presentation displays on the phone.


Tip Configuring calling party normalization alleviates issues with toll bypass where the call is routed to multiple locations over the IP WAN. In addition, it allows Cisco Unified Communications Manager to distinguish the origin of the call to globalize or localize the calling party number for the phone user.


This section contains information on the following topics:

Globalizing the Calling Party Number

Localizing the Calling Party Number

Mapping the Global Party Calling Number to Its Local Variant

Globalizing the Calling Party Number


Tip This section does not describe the international escape character, +, which you can configure for globalizing the calling party number. For information on the international escape character, see the "Using the International Escape Character +" in the Cisco Unified Communications Manager System Guide.


This section contains information on the following topics:

Globalization of the Calling Party Number Description

Configuration Windows in Cisco Unified Communications Manager Administration for Globalizing the Calling Party Number

Globalization of the Calling Party Number Description

To globalize the calling party number for calls that get routed to multiple geographical locations, Cisco Unified Communications Manager allows you to configure prefixes for required access codes, escape codes, country codes, and so on, based on the calling party number type that the PSTN provides. The calling party number type that the PSTN provides determines whether the incoming call arrives from the PSTN as a national, international, subscriber, or unknown call. For example, if the call comes from a caller in Hamburg to an enterprise gateway in Hamburg, the call arrives to Cisco Unified Communications Manager with calling party number 69XXXXXXX with number type of Subscriber. However, if the call comes from a caller in Frankfurt to an enterprise gateway in Hamburg, the call arrives to Cisco Unified Communications Manager with caller party number 69XXXXXXX with number type of National.

Configuring the Calling Party Number Type setting and prefixes in Cisco Unified Communications Manager Administration allows Cisco Unified Communications Manager to reformat the calling party number from the PSTN-localized version to the globally dialable version by prefixing required access codes, international access codes, and so on, to the calling party number. You can configure the Calling Party Number Type setting for various patterns, for example, translation patterns, calling party transformation patterns, and route patterns, for both called and calling parties to ensure that Cisco Unified Communications Manager stamps the number type during various stages of incoming and outgoing calls. After Cisco Unified Communications Manager globalizes the calling party number, the call gets routed as expected to its destination.

Depending on your configuration for globalizing and localizing the calling party number, the phone user may see a localized number, a globalized number with access codes and prefixes, and/or the international escape character, +, in the calling party number. If a phone supports calling party normalization, the phone can show the localized calling party number on the phone screen and the globalized number in the call log directories on the phone. In addition, these phones show both the globalized and localized calling party number in the Call Details. If a phone does not support calling party normalization, the phone shows the localized calling party on the phone screen and in the call log directories on the phone.

To ensure that the phone user does not need to edit the call log directory entry on the phone before placing a call, map the global calling party number to its local variant to route calls to the correct gateway; you can use route patterns and called party transformation patterns to route the call correctly, as the "Mapping the Global Party Calling Number to Its Local Variant" section describes.

Configuration Windows in Cisco Unified Communications Manager Administration for Globalizing the Calling Party Number

Table 7-1 lists the configuration windows in Cisco Unified Communications Manager Administration where you can configure prefixes for globalizing the calling party number. The following fields display in the windows, unless noted in Table 7-1: Incoming Calling Party National Number Prefix, Incoming Calling Party International Number Prefix, Incoming Calling Party Subscriber Number Prefix, and Incoming Calling Party Unknown Number Prefix. For information on these fields, see Table 7-7.

Table 7-1 Calling Party Normalization Prefix Configuration 

Configuration Window
Considerations

Device Pool

You can configure prefixes in the device pool, which support digital gateways or trunks.

In the Device Pool Configuration window, to delete the prefixes in all incoming calling party settings at the same time, click Clear Prefix Settings; to enter the default value for all incoming calling party settings at the same time, click Default Prefix Settings. If the word, Default, displays in the field, Cisco Unified Communications Manager applies service parameter configuration for the incoming calling party number prefix to the device.

Gateway

You can configure prefixes for H.323, MGCP (T1-PRI/BRI), and MGCP (E1-PRI/BRI) gateways.

If you have gateways in multiple geographical locations, configure the prefix settings for each gateway in the Gateway Configuration window. For example, if you have a gateway in RTP and an incoming call arrives with caller ID 555 1212, you want to prefix the caller ID with 919 to yield 9195551212. However, if the call routes to another gateway, for example, in Dallas, which uses area code 214, before reaching its final destination, you want 91214 to display for the prefix instead of 91919.

To globalize calling party numbers for incoming calls, you must configure the prefixes for gateways that handle incoming calls.

In the Gateway Configuration window, to delete the prefixes in all incoming calling party settings at the same time, click Clear Prefix Settings; to enter the default value for all incoming calling party settings at the same time, click Default Prefix Settings. If the word, Default, displays in the field, Cisco Unified Communications Manager applies the device pool configuration for the incoming calling party number prefix to the device.

Trunk

You can configure prefixes for all trunk types. SIP trunks only support the Incoming Calling Party Unknown Number Prefix setting.

In the Trunk Configuration window, to delete the prefixes in all incoming calling party settings at the same time, click Clear Prefix Settings; to enter the default value for all incoming calling party settings at the same time, click Default Prefix Settings. If the word, Default, displays in the field, Cisco Unified Communications Manager applies the device pool configuration for the incoming calling party number prefix to the device.

Service Parameter

The prefix service parameters, Incoming Calling Party National Number Prefix, Incoming Calling Party International Number Prefix, Incoming Calling Party Subscriber Number Prefix, and Incoming Calling Party Unknown Number Prefix, each display for the phone, H.323. MGCP, and SIP (Unknown only for SIP) in the Service Parameters Configuration window.

If you have a single H.323, MGCP (T1-PRI/BRI), or MGCP (E1-PRI/BRI) gateway in your network, you can configure the prefix service parameters, which support the Cisco CallManager service, for the particular gateway type in the Service Parameter Configuration window. If you configure the prefix service parameters for a particular gateway type, for example, H.323, be aware that all H.323 gateways that you configure in Cisco Unified Communications Manager Administration use the configuration from the service parameter unless you configure the prefix settings for a particular gateway in the Gateway Configuration window.


Localizing the Calling Party Number

For the final presentation of the calling party number, Cisco Unified Communications Manager allows you to configure calling party transformation patterns, so the number displays on the phone as the end user expects it to display; that is, you can configure the calling party transformation pattern to strip digits or add digits to the calling party number. To present the shortest recognizable number on the phone, you can strip unnecessary country codes, international access codes, and so on, depending on the locations of the caller and the called parties.


Tip You configure calling party transformation patterns to provide context-sensitive modifications to a calling party, not for routing purposes.


Example 7-1 shows how an administrator configured transformation patterns to localize a globalized calling party number.

Example 7-1 Localizing the Calling Party Presentation


Tip You can globalize the calling party number before localizing the number. To globalize the calling party number in Example 7-1 before localizing the number, the administrator can configure the incoming gateway in Hamburg with the following information: Number Type of Subscriber with +4940 prefix; Number Type of National with +49 prefix; Number Type of International with + prefix. After the administrator configures the gateway, he configures the transformation patterns in Table 7-2.


For example, a call occurs between two parties in Hamburg. The incoming call over the PSTN in Hamburg gets globalized as +49 40 69XXXXXXX, but the administrator has configured multiple transformation patterns to localize the calling party number before it reaches the desk phone of the called party in Hamburg. These transformation patterns, which use closest match routing to strip unnecessary digits, contain the configuration, as shown in Table 7-2:

Table 7-2 Calling Party Transformation Patterns (Example)

Calling Party Transformation Pattern 1
Calling Party Transformation Pattern 2
Calling Party Transformation Pattern 3

\+4940.! (Pattern Setting)

\+49.!

\+.!

discard Predot (Discard Digits Instructions Setting)

discard Predot

discard Predot

prefix 0 (Prefix Digits Setting)

prefix 00

prefix 000

Subscriber (Calling Party Number Type Setting)

National

International


By using digit analysis matching semantics, all the patterns in Table 7-2 match the provided dial string; however, Transformation Pattern 1, which constitutes the closest match for a call within Hamburg, indicates that if the call is from Germany and from Hamburg, strip the German country code, 49, and the Hamburg city code, 40, and add the prefix 0 to the calling party number. So, when both parties in a call are in Hamburg, +494069XXXXXXX changes to 069XXXXXXX.

If the caller is from Frankfurt, Transformation Pattern 1 does not match, but Transformation Patterns 2 and 3 match. Representing the best match, Transformation Pattern 2 indicates that the system needs to strip the + and the German country code, 49, and then prefix 00 to the calling party number. So, for a long-distance call from Frankfurt to Hamburg, +494069XXXXXXX changes to 0069XXXXXXX.

If the caller is international, Transformation Pattern 3 works because Cisco Unified Communications Manager strips the international escape character, +, and prefixes the German international code, 000, to the calling party number.


Tip All phone device types, CTI route points, gateways, remote destination profiles, and trunks in Cisco Unified Communications Manager Administration localize the calling party number for themselves; to ensure that the device can localize the calling party number, you must configure the Calling Party Transformation CSS (calling search space) and assign it to the device. The Calling Party Transformation CSS takes on the attributes of the calling party transformation pattern, which you assign to the partition where the Calling Party Transformation CSS exists. If you want to do so, you can choose the Calling Party Transformation CSS in the device pool; when you assign the device pool to the device, the device uses the Calling Party Transformation CSS in the device pool; that is, if you check the Use Device Pool Calling Party Transformation CSS check box in the device configuration window.

The Calling Party Transformation CSS does not apply to T1-CAS and FXO ports on the gateway.

Before the call occurs, the device must apply the transformation by using digit analysis. If you configure the Calling Party Transformation CSS as None, the transformation does not match and does not get applied. Ensure that you configure the Calling Party Transformation Pattern in a non-null partition that is not used for routing.


Mapping the Global Party Calling Number to Its Local Variant

To ensure that the phone user does not need to edit the call log directory entry on the phone before placing a call, map the global calling party number to its local variant to route calls to the correct gateway; you can use route patterns and called party transformation patterns to route the call correctly, as Example 7-2 describes.

Example 7-2 Mapping the Global Calling Party Number to Its Local Variant

A Cisco Unified IP Phone in Hamburg (Phone Q) receives calls over the Hamburg or Frankfurt PSTN from different localized and globalized calling party numbers. To ensure that the phone user for the Phone Q does not need to edit the call log directory entry on the phone to return the call, you can associate the route patterns in Table 7-3 to the calling search space in the Phone Configuration window for Phone Q.

In Cisco Unified Communications Manager Administration, you configure the route patterns in Table 7-3 in the Route Patterns Configuration window (Call Routing > Route/Hunt > Route Patterns).

Table 7-3 Mapping the Global Calling Party Number to Its Local Variant (Example) 

Route Pattern
Configuration for Route Pattern Setting
Configuration for Discard Digits Setting

Route Pattern 1

\+4940.!

Configured for local Hamburg callers that call by using a globalized calling party number.

discard Predot

Route Pattern 2

0.!

Configured for local Hamburg callers that dial by using a localized calling party number.

discard Predot

Route Pattern 3

0.0!

Configured for Germany callers that do not have a Hamburg directory number that is associated with their device; these callers use a localized calling party number from Frankfurt or other cities in Germany.

discard Predot

Route Pattern 4

\+49.!

Configured for German callers that do not have a Hamburg directory number that is associated with their device; these callers use a globalized calling party number from Frankfurt or any other city in Germany.

discard Predot


When Phone Q in Example 7-2 receives a call from the Hamburg calling party number, 69XXXXXXX, via the PSTN, the calling party number +49406XXXXXXX displays on the phone screen for Phone Q. If the phone user for Phone Q returns the call by using the globalized calling party number, Cisco Unified Communications Manager matches the pattern, \+49.!, routes the call to the correct gateway, and sends the relevant digits. If the phone user for Phone Q returns the call by using the localized calling party number, Cisco Unified Communications Manager matches the pattern, 0.!, routes the call to the correct gateway, and sends the relevant digits.

When Phone Q in Example 7-2 gets a call from the Frankfurt calling party number XXXXXXX via the PSTN, the globalized calling party number +4969XXXXXXX displays on the phone screen for Phone Q, and the localized calling party number displays as 0069XXXXXXX. If the phone user for Phone Q returns the call by using the globalized calling party number, Cisco Unified Communications Manager matches the pattern, \+49.!, routes the call to the correct gateway, and sends the relevant digits. If the phone user for Phone Q returns the call by using the localized calling party number, Cisco Unified Communications Manager matches the pattern, 0.0!, routes the call to the correct gateway, and sends the relevant digits.

System Requirements

The following system requirements apply to calling party normalization:

Cisco Unified Communications Manager 7.0

Cisco Unified IP Phones 7906, 7911, 7931, 7961, 7962, 7965, 7970, 7971, and 7975

Interactions and Restrictions

The following sections describe the interactions and restrictions for calling party normalization:

Interactions

Restrictions

Interactions

The following sections describe how calling party normalization interacts with Cisco Unified Communications Manager features and applications:

Globalizing and Localizing Calling Party Numbers for Transferred Calls

Globalizing and Localizing Calling Party Numbers for Forwarded Calls

Bulk Administration Tool

Call Detail Records

Cisco Unified Communications Manager CDR Analysis and Reporting

Cisco Extension Mobility

Device Mobility

Globalizing and Localizing Calling Party Numbers for Transferred Calls

The transfer feature relies on mid-call updates, so depending on the scenario, a transferred call may not support globalization and localization of the calling party number. (Calling party normalization supports globalization and localization during call setup for each hop of the call, not for mid-call updates.) For examples of how calling party normalization works for transferred calls, see the following sections:

Calling Party Normalization for On Net Transferred Call Across a Gateway

Calling Party Normalization for Transferred Call Through an Incoming Gateway

Calling Party Normalization for On Net Transferred Call Across a Gateway

Phone A with extension 12345 and phone number of 972 500 2345 calls Phone B with extension 54321 and phone number 972 500 4321; when the call arrives on extension 54321, calling party number 12345 displays on Phone B. Phone B transfers the call to Phone C in San Jose through a San Jose gateway. During the initiation of the transfer, Phone C displays the calling party number for Phone B as 972 500 4321. After the transfer completes, Phone C displays the calling party number for Phone A as 12345.

Calling Party Normalization for Transferred Call Through an Incoming Gateway

Via the PSTN in Dallas, a caller (Phone D) calls Phone E (Cisco Unified IP Phone), which uses extension 7891 and phone number 972 500 6789. On the incoming Dallas gateway, the caller information for Phone D displays as 500 1212/<Subscriber>. Phone E displays +1 972 500 1212 for the globalized calling party number and 500 1212 for the localized calling party number for Phone D. Phone E initiates a transfer to Phone C in San Jose across the San Jose gateway. During the initiation of the transfer, Phone C displays the calling party number for Phone  E as 972 500 6789. After the transfer completes, Phone C displays the calling party number for Phone D as +1 972 500 1212.

Globalizing and Localizing Calling Party Numbers for Forwarded Calls

Forwarded calls support globalized and localized calling party numbers. Globalization and localization of the call occur during call setup for each hop of the call. Depending on the hop for the call and the configuration of the gateway, that is, the calling party transformation and prefix configuration on the gateway, the globalized version or the localized version (or both) may display on the phone. See the following example, which describes how an incoming call via the PSTN gets forwarded to another geographic location.

For example, via the PSTN in Dallas, a caller with Phone F calls Phone G (Cisco Unified IP Phone), which has forwarded all calls to Phone H (Cisco Unified IP Phone) in San Jose. On the incoming Dallas gateway, the caller information for Phone F displays as 500 5555/<Subscriber>. On the outgoing gateway from Dallas to San Jose, the outgoing caller information for the Calling Party Transformation CSS comprises 972 500 5555/National. On the incoming gateway in San Jose, the calling party number gets prefixed with +1 for the National number type; on Phone H in San Jose, the localized calling party number for Phone F displays as 972 500 5555, and the globalized calling party number displays as +1 972 500 5555.

Bulk Administration Tool

For information on how calling party normalization relates to the Bulk Administration Tool, refer to the Cisco Unified Communications Manager Bulk Administration Guide.

Call Detail Records

For information on how calling party normalization impacts call detail records (CDRs), refer to the Cisco Unified Communications Manager Call Detail Records Administration Guide.

Cisco Unified Communications Manager CDR Analysis and Reporting

For information on how calling party normalization impacts Cisco Unified Communications Manager CDR Analysis and Reporting (CAR), refer to CDR Analysis and Reporting Administration Guide.

Cisco Extension Mobility

Cisco Extension Mobility works as expected; that is, a phone user that is logged in to a Cisco Extension Mobility phone may see globalized or localized calling party numbers on the phone screen or in the call log directories on the phone.

Device Mobility

The following example shows how calling party normalization works when you move a phone from its home location, as supported with the Device Mobility feature in Cisco Unified Communications Manager.

A Cisco Unified IP Phone (Phone N) with home location in Dallas moves to San Jose. The Cisco Unified IP Phone in Dallas uses device pool, DP_Dallas, which has the Calling Party Transformation CSS as CallingTransform_Dallas; the Calling Transform_Dallas CSS contains the DallasPhone and the CommonTransform partitions. The roaming device in San Jose uses device pool, DP_SanJose, which has the Calling Party Transformation CSS as CallingTransform_SJ; the CallingTransform_SJ CSS contains the SJPhone and the CommonTransform partitions. Cisco Unified Communications Manager Administration contains the configuration in Table 7-4:

Table 7-4 Globalizing and Localizing Calling Party Numbers with Device Mobility (Example) 

Calling Party Transformation Pattern 1
Calling Party Transformation Pattern 2
Calling Party Transformation Pattern 3

Pattern— \+.@

Partition—CommonTransform

Disregard Digits Instructions—Predot

Calling Party Number Type—National

Pattern—\+1.408!

Partition—SJPhone

Disregard Digits Instructions—Predot

Prefix—9

Calling Party Number Type—Subscriber

Pattern—\+1972.!

Partition—DallasPhone

Discard Digits Instructions—Predot

Prefix—9

Calling Party Number Type—Subscriber


When the phone is in its home location in Dallas, a call comes via the PSTN from 408 500 1212 <National> in San Jose. On the incoming Dallas gateway, the calling party number number gets converted to the global format of + 1 408 500 1212. On the phone that is currently in Dallas, the calling party number displays as 1 408 500 1212.

When the phone is in its home location in Dallas, a call comes via the PSTN from 400 2323 <Subscriber> from a seven-digit dialing area in Dallas. On the incoming Dallas gateway, the calling party number gets converted to the global format of + 1 972 400 2323. On the phone that is currently in Dallas, the calling party number displays as 9 400 2323.

When the phone is roaming in San Jose, a call comes via the PSTN from 972 500 1212 <National> in Dallas. On the incoming San Jose gateway, the calling party number gets converted to the global format of + 1 408 500 1212. On the phone that currently is in San Jose, the calling party number displays as 1 972 500 1212.

When the phone is roaming in San Jose, a call comes via the PSTN from 500 1212 <Subscriber> from a seven-digit dialing area in San Jose. On the incoming San Jose gateway, the calling party number gets converted to the global format of + 1 408 500 1212. On the phone that currently is in San Jose, the calling party number displays as 9 500 1212.

Restrictions

Before you configure calling party normalization, review the following restrictions:

The calling party number that displays for a shared line depends on the sequence of call control events in Cisco Unified Communications Manager. To avoid displaying an incorrect localized calling party number on a shared line, especially when the shared line occurs in different geographical locations, make sure that you configure the same Calling Party Transformation CSS for different devices that share the same line.

SIP trunks and MGCP gateways can support sending the international escape character, +, for calls. H.323 gateways do not support the +. QSIG trunks do not attempt to send the +. For outgoing calls through a gateway that supports +, Cisco Unified Communications Manager can send the + with the dialed digits to the gateway. For outgoing calls through a gateway that does not support +, the gateway strips the + when Cisco Unified Communications Manager sends the call information to the gateway.

SIP does not support the number type, so calls through SIP trunks only support the Incoming Calling Party Unknown Number Prefix settings.

A QSIG configuration usually supports a uniform dial plan. Transformation of numbers and prefixes may cause feature interaction issues if you have use QSIG.

For localizing the calling party number, the device must apply the transformation by using digit analysis. If you configure the Calling Party Transformation CSS as None, the transformation does not match and does not get applied. Ensure that you configure the Calling Party Transformation Pattern in a non-null partition that is not used for routing.

The Calling Party Transformation CSS does not apply to T1-CAS and FXO ports on the gateway.

Installing and Activating Calling Party Normalization

After you install Cisco Unified Communications Manager 7.0, you can configure calling party normalization. Calling party normalization service parameters support the Cisco CallManager service, so activate the Cisco CallManager service in Cisco Unified Serviceability before you configure calling party normalization.

Configuring Calling Party Normalization

This section contains information on the following topics:

Configuration Checklist for Calling Party Normalization

Setting the Service Parameters for Calling Party Normalization

Configuring Prefixes to Globalize the Calling Party Number

Applying the Calling Party Transformation CSS to Localize the Calling Party Number

Configuration Checklist for Calling Party Normalization

Table 7-5 lists the tasks that you perform to globalize and localize the calling party number.

Table 7-5 Configuration Checklist for Calling Party Normalization 

Configuration Steps
Related Procedures and Topics

Step 1 

Review the interactions and restrictions for this feature.

Globalizing the Calling Party Number

Localizing the Calling Party Number

Interactions

Restrictions

Step 2 

If you have not already done so, activate the Cisco CallManager service in Cisco Unified Serviceability.

Cisco Unified Serviceability Administration Guide

Globalizing the Calling Party Number

Step 3 

If you want to do so, configure the Calling Party Number Type.

Globalizing the Calling Party Number

Configuring the Calling Party Number Type

Step 4 

For national, international, subscriber, and unknown calls, create the prefixes that you want to associate with these types of calls. You create prefixes for device types; for example, phones, MGCP gateways, H.323 gateways/trunks, SIP trunks, and so on.

Globalizing the Calling Party Number

Setting the Service Parameters for Calling Party Normalization

Configuring Prefixes to Globalize the Calling Party Number

Localizing the Calling Party Number

Step 1 

Create a partition for the calling party transformation pattern under Calling Routing > Class of Control > Calling Search Space.

Configuring a Partition, Cisco Unified Communications Manager Administration Guide

Step 2 

Create the Calling Party Transformation calling search space (CSS) under Calling Routing > Class of Control > Calling Search Space; in the Calling Search Space Configuration window for the Calling Party Transformation CSS, move the partition that you created for the calling party transformation pattern to the Available Partitions pane.

Configuring a Calling Search Space, Cisco Unified Communications Manager Administration Guide

Step 3 

Choose Call Routing > Transformation Patterns > Calling Party Transformation Pattern to create the Calling Party Transformation Pattern; in the Calling Party Transformation Pattern Configuration window, assign the partition that you associated with the calling party transformation CSS to the calling party transformation pattern.

Configuring a Calling Party Transformation Pattern, Cisco Unified Communications Manager Administration Guide

Step 4 

Choose the Calling Party Transformation CSS in the device configuration window; for example, in the Gateway Configuration, Phone Configuration, H.323 Client Configuration, and the CTI Route Point Configuration window.

Tip To choose the Calling Party Transformation CSS in the device configuration window, configure the Calling Party Transformation CSS setting (not the Calling Search Space setting). If you want the device to use the Calling Party Transformation CSS that is assigned to the device pool that the device uses, check the Use the Device Pool Calling Party Transformation CSS.

Applying the Calling Party Transformation CSS to Localize the Calling Party Number

Setting the Service Parameters for Calling Party Normalization

To locate the service parameters in Cisco Unified Communications Manager Administration, choose System > Service Parameters; choose the server and the Cisco CallManager service. After the parameters display, click Advanced. For information on the service parameter, click the hyperlink for the service parameter name or the question mark that displays in the upper, right corner of the window.

Clusterwide Parameters (Device - PRI and MGCP Gateway)

Incoming Calling Party National Number Prefix - MGCP

Incoming Calling Party International Number Prefix - MGCP

Incoming Calling Party Subscriber Number Prefix - MGCP

Incoming Calling Party Unknown Number Prefix - MGCP


Tip If you have a single H.323, MGCP (T1-PRI/BRI), or MGCP (E1-PRI/BRI) gateway in your network, you can configure the prefix service parameters, which support the Cisco CallManager service, for the particular gateway type in the Service Parameter Configuration window. If you configure the prefix service parameters for a particular gateway type, for example, H.323, be aware that all H.323 gateways that you configure in Cisco Unified Communications Manager Administration use the configuration from the service parameter unless you configure the prefix settings for a particular gateway in the Gateway Configuration window.


Clusterwide Parameters (Device - H323)

Incoming Calling Party National Number Prefix - H.323

Incoming Calling Party International Number Prefix - H.323

Incoming Calling Party Subscriber Number Prefix - H.323

Incoming Calling Party Unknown Number Prefix - H.323


Tip If the incoming prefix service parameters for H.323 use the same prefix as the incoming prefix service parameters for the phone, the prefix gets used twice for the calling party; first, when the incoming call gets to the gateway and again, when the call terminates at the phone.


Clusterwide Parameters (Device - SIP)

Incoming Calling Party Unknown Number Prefix - SIP

Configuring the Calling Party Number Type

Configuring the Calling Party Number Type setting and prefixes in Cisco Unified Communications Manager Administration allows Cisco Unified Communications Manager to reformat the calling party number from the PSTN-localized version to the globally dialable version by prefixing required access codes, international access codes, and so on to the calling party number. You can configure the Calling Party Number Type setting for various patterns for both called and calling parties to ensure that Cisco Unified Communications Manager stamps the number type during various stages of incoming and outgoing calls.

You configure the Calling Party Number Type setting in the Calling Party Transformation Pattern Configuration, Route Pattern Configuration, Hunt Pilot Configuration, Translation Pattern Configuration, and the Route List Detail Configuration windows in Cisco Unified Communications Manager Administration.

Route Pattern Configuration, Cisco Unified Communications Manager Administration Guide

Hunt Pilot Configuration, Cisco Unified Communications Manager Administration Guide

Configuring a Calling Party Transformation Pattern, Cisco Unified Communications Manager Administration Guide

Table 7-6 describes the Calling Party Number Type setting that displays in Cisco Unified Communications Manager Administration.

Table 7-6 Description for Calling Party Number Type

Setting
Description

Calling Party Number Type

Choose the format for the number type in calling party directory numbers.

Cisco Unified Communications Manager sets the calling directory number (DN) type. Cisco recommends that you do not change the default value unless you have advanced experience with dialing plans such as NANP or the European dialing plan. You may need to change the default in Europe because Cisco Unified Communications Manager does not recognize European national dialing patterns. You can also change this setting when you are connecting to a PBX that expects the calling directory number to be encoded to a non-national numbering plan type.

Choose one of the following options:

Cisco Unified Communications Manager—The Cisco Unified Communications Manager sets the directory number type.

Unknown—Choose when the dialing plan is unknown.

National—Use when you are dialing within the dialing plan for your country.

International—Use when you are dialing outside the dialing plan for your country.

Subscriber—Use when you are dialing a subscriber by using a shortened subscriber number.

In the following windows in Cisco Unified Communications Manager Administration, you can configure the Calling Party Number Type setting:

Route List Detail Configuration—Call Routing > Route/Hunt > Hunt List (Add the hunt list; after you click Save, the Add a Route Group button displays. To display the Route List Detail Configuration window, click the Add a Route Group button.)

Route Pattern Configuration—Calling Routing > Route/Hunt > Route Pattern

Hunt Pilot Configuration—Calling Routing > Route/Hunt > Hunt Pilot

Translation Pattern Configuration—Call Routing > Translation Pattern

Calling Party Transformation Pattern Configuration—Call Routing > Transformation Pattern > Calling Party Transformation Pattern

Tip In the Gateway and Trunk Configuration window, you can configure the Calling Party IE Number Type Unknown setting. If you can configure this setting and choose any other option except for Cisco Unified Communications Manager, which is the default, your configuration for this field overwrites the Calling Party Number Type setting for the outgoing call through a particular gateway.

Configuring Prefixes to Globalize the Calling Party Number

Table 7-7 describes the prefix settings that display in the Device Pool, Gateway, and Trunk Configuration windows. For configuration procedures for each configuration window, refer to the following sections:

Configuring a Device Pool, Cisco Unified Communications Manager Administration Guide

Gateway Configuration, Cisco Unified Communications Manager Administration Guide

Configuring a Trunk, Cisco Unified Communications Manager Administration Guide

Service Parameters Configuration, Cisco Unified Communications Manager Administration Guide


Tip In the Device Pool, Gateways, and Trunk Configuration windows, to delete the prefixes in all incoming calling party settings at the same time, click Clear Prefix Settings; to enter the default value for all incoming calling party settings at the same time, click Default Prefix Settings.

If the word, Default, displays in the field in the Gateway or Trunk Configuration window, Cisco Unified Communications Manager applies the device pool configuration for the incoming calling party prefix. If the word, Default, displays in the incoming calling party prefix field in the Device Pool Configuration window, Cisco Unified Communications Manager applies the service parameter configuration for the incoming calling party prefix.


Table 7-7 Prefix Settings for Globalizing the Calling Party Number 

Setting
Description

Incoming Calling Party National Number Prefix

Used for globalizing the calling party number, Cisco Unified Communications Manager applies the prefix that you enter in this field to calling party numbers that use National for the Calling Party Numbering Type. You can enter up to 8 characters, which include digits, the international escape character (+), asterisk (*), or the pound sign (#). When the prefix in this parameter is applied to the incoming calling party number on the device, Cisco Unified Communications Manager includes the prefix in the calling party number field for all additional actions that pertain to the call, such as supplementary services including call forwarding, call park, voice messaging, CDR data, and so on.

This setting displays in the following windows in Cisco Unified Communications Manager Administration:

Device Pool (System > Device Pool)—Applies the configuration to all digital gateways and trunks; that is, if you choose the device pool for the device.

Service Parameter (System > Service Parameters)—Applies to Phone, MGCP, and H.323 service parameters; in the Service Parameter Configuration window for the Cisco CallManager service, click the Advanced button to display the parameters. For example, parameters display as Incoming Calling Party National Number Prefix - Phone or Incoming Calling Party National Number Prefix - MGCP.

Gateway (Device > Gateway)—Displays setting in the H.323 gateway configuration window and in the port windows (Gateway Configuration window) for MGCP (T1-PRI/BRI) and MGCP (E1-PRI/BRI).

Trunk (Device > Trunk)—Displays setting in all trunk configuration windows except the SIP trunk.

Incoming Calling Party International Number Prefix

Used for globalizing the calling party number, Cisco Unified Communications Manager applies the prefix that you enter in this field to calling party numbers that use International for the Calling Party Numbering Type. You can enter up to 8 characters, which include digits, the international escape character (+), asterisk (*), or the pound sign (#). When the prefix in this parameter is applied to the incoming calling party number on the device, Cisco Unified Communications Manager includes the prefix in the calling party number field for all additional actions that pertain to the call, such as supplementary services including call forwarding, call park, voice messaging, CDR data, and so on.

This setting displays in the following windows in Cisco Unified Communications Manager Administration:

Device Pool (System > Device Pool)—Applies the configuration to all digital gateways and trunks; that is, if you choose the device pool for the device.

Service Parameter (System > Service Parameters)—Applies to Phone, MGCP, and H.323 service parameters; in the Service Parameter Configuration window for the Cisco CallManager service, click the Advanced button to display the parameters. For example, parameters display as Incoming Calling Party National Number Prefix - Phone or Incoming Calling Party National Number Prefix - MGCP.

Gateway (Device > Gateway)—Displays setting in H.323 gateway configuration window and in the port windows (Gateway Configuration) for MGCP (T1-PRI/BRI) and MGCP (E1-PRI/BRI).

Trunk (Device > Trunk)—Displays setting in all trunk configuration windows except the SIP trunk.

Incoming Calling Party Subscriber Number Prefix

Used for globalizing the calling party number, Cisco Unified Communications Manager applies the prefix that you enter in this field to calling party numbers that use Subscriber for the Calling Party Numbering Type. You can enter up to 8 characters, which include digits, the international escape character (+), asterisk (*), or the pound sign (#). When the prefix in this parameter is applied to the incoming calling party number on the device, Cisco Unified Communications Manager includes the prefix in the calling party number field for all additional actions that pertain to the call, such as supplementary services including call forwarding, call park, voice messaging, CDR data, and so on.

This setting displays in the following windows in Cisco Unified Communications Manager Administration:

Device Pool (System > Device Pool)—Applies the configuration to all digital gateways and trunks; that is, if you choose the device pool for the device.

Service Parameter (System > Service Parameters)—Applies to Phone, MGCP, and H.323 service parameters; in the Service Parameter Configuration window for the Cisco CallManager service, click the Advanced button to display the parameters. For example, parameters display as Incoming Calling Party National Number Prefix - Phone or Incoming Calling Party National Number Prefix - MGCP.

Gateway (Device > Gateway)—Displays setting in H.323 gateway configuration window and in the port windows for MGCP (T1-PRI/BRI) MGCP (E1-PRI/BRI).

Trunk (Device > Trunk)—Displays setting in all trunk configuration windows except the SIP trunk.

Incoming Calling Party Unknown Number Prefix

Used for globalizing the calling party number, Cisco Unified Communications Manager applies the prefix that you enter in this field to calling party numbers that use Unknown for the Calling Party Numbering Type. You can enter up to 8 characters, which include digits, the international escape character (+), asterisk (*), or the pound sign (#). When the prefix in this parameter is applied to the incoming calling party number on the device, Cisco Unified Communications Manager includes the prefix in the calling party number field for all additional actions that pertain to the call, such as supplementary services including call forwarding, call park, voice messaging, CDR data, and so on.

This setting displays in the following windows in Cisco Unified Communications Manager Administration:

Device Pool (System > Device Pool)—Applies the configuration to all digital gateways and trunks; that is, if you choose the device pool for the device.

Service Parameter (System > Service Parameters)—Applies to Phone, MGCP, H.323, and SIP service parameters; in the Service Parameter Configuration window for the Cisco CallManager service, click the Advanced button to display the parameters. For example, parameters display as Incoming Calling Party National Number Prefix - Phone or Incoming Calling Party National Number Prefix - MGCP.

Gateway (Device > Gateway)—Displays setting in H.323 gateway configuration window and in the port windows for MGCP (T1-PRI/BRI) MGCP (E1-PRI/BRI).

Trunk (Device > Trunk)—Displays setting in all trunk configuration windows, including the SIP trunk.


Applying the Calling Party Transformation CSS to Localize the Calling Party Number

Before you configure the Calling Party Transformation CSS, make sure that you understand the steps that are required to localize the calling party number; for example, configuring the partition, configuring the calling search space, and so on. For more information, see the "Configuration Checklist for Calling Party Normalization" section.

Table 7-8 describes the Calling Party Transformation CSS and the Use the Device Pool Calling Party Transformation CSS settings and lists the configuration windows in Cisco Unified Communications Manager Administration where you assign the settings.

Table 7-8 Configuring the Calling Party Transformation CSS 

Setting
Description

Calling Party Transformation CSS

This setting allows you to localize the calling party number on the device. Make sure that the Calling Party Transformation CSS that you choose contains the calling party transformation pattern that you want to assign to this device.

Tip Before the call occurs, the device must apply the transformation by using digit analysis. If you configure the Calling Party Transformation CSS as None, the transformation does not match and does not get applied. Ensure that you configure the Calling Party Transformation Pattern in a non-null partition that is not used for routing.

All phone device types, CTI route points, gateways, remote destination profiles, and trunks in Cisco Unified Communications Manager Administration can localize the calling party number for themselves; therefore, you can access this setting in the following windows in Cisco Unified Communications Manager Administration:

Device Pool (System > Device Pool)

Phone (Device > Phone)

CTI Route Points (Device > CTI Route Point)

Gateway (Device > Gateway)—Depending on the gateway type, the setting may display in the port configuration window or the gateway configuration window.

Trunk (Device > Trunk)

Remote Destination Profile (Device > Device Settings > Remote Destination Profile)

Use Device Pool Calling Party Transformation CSS

To use the Calling Party Transformation CSS that is configured in the device pool that is assigned to this device, check this check box. If you do not check this check box, the device uses the Calling Party Transformation CSS that you configured in the device configuration window.

All phone device types, CTI route points, gateways, remote destination profiles, and trunks in Cisco Unified Communications Manager Administration can localize the calling party number for themselves; therefore, you can access this setting in the following windows in Cisco Unified Communications Manager Administration:

Phone (Device > Phone)

CTI Route Points (Device > CTI Route Point)

Gateway (Device > Gateway)—Depending on the gateway type, the setting may display in the port configuration window or the gateway configuration window.

Trunk (Device > Trunk)

Remote Destination Profile (Device > Device Settings > Remote Destination Profile)


Providing Information to End Users

Depending on your configuration, a phone user may not need to edit the call log directory entry on the phone before placing a call. Depending on your configuration, the phone user may see the international escape character, +, in the call log directories on the phone.

Related Topics

Globalizing the Calling Party Number

Localizing the Calling Party Number

Mapping the Global Party Calling Number to Its Local Variant

System Requirements

Interactions and Restrictions

Installing and Activating Calling Party Normalization

Configuration Checklist for Calling Party Normalization

Setting the Service Parameters for Calling Party Normalization

Configuring the Calling Party Number Type

Configuring Prefixes to Globalize the Calling Party Number

Applying the Calling Party Transformation CSS to Localize the Calling Party Number

Providing Information to End Users

Using the International Escape Character +, Cisco Unified Communications Manager System Guide

Additional Cisco Documentation

Cisco Unified Communications Manager System Guide

Cisco Unified Communications Manager Administration Guide

Cisco Unified Serviceability Administration Guide

CDR Analysis and Reporting Administration Guide

Cisco Unified Communications Manager Bulk Administration Guide

Cisco Unified IP Phone documentation that supports your phone model and this version of Cisco Unified Communications Manager