Cisco Unified Communications Manager Global Transformations
CUCM version 7.0 introduced number normalization and number globalization support for E.164-based call routing. Calling and called party transformation patterns extend the power of CUCM's digit manipulation. Calling and called party transformation patterns have the following characteristics:
- Transformations are implemented in the global CUCM configuration.
- Calling and called party transformation patterns are put into partitions.
- Identical transformation patterns with different transformation settings can exit if they are put into different partitions. Partitions separate dial plan elements so that each pattern will only be evaluated if that partition is in the calling party's Calling Search Space (CSS).
- Gateways and trunks can be configured with calling and called party transformation CSSs. Calling party transformations are supported at the Cisco IP Phone, but called party transformations are not supported on the Cisco IP Phone.
- The transformation CSS determines which transformation patterns are visible to the device.
Calling and called party transformation patterns are applicable only to calls from CUCM to gateways, trunks, and phones. A call to a phone is usually not considered to be an outgoing call from a user's perspective. Think of a phone as the outgoing call leg of an internal call from another phone or incoming call.
Instead of configuring an individual calling and called party transformation CSS at each device, you can configure the devices to use calling and called party transformation CSSs configured at the device pool level. No transformation is performed if the device and associated device pool are not configured with a transformation CSS.
Calling and called party transformations are not applicable to calls that CUCM receives from devices (incoming call legs). Figure 11-15 illustrates called party transformations for four different phone numbers.
)
Figure 11-15 Called Party Transformation Patterns
Calling and called party globalized call routing has been configured in Figure 11-15, as indicated by the leading + character shown in the following four called party number strings:
- +49691234
- +14085551234
- +17035551234
- +13035551234
Transformations patterns only apply to outgoing call legs. Figure 11-15 is an example of globalized outbound call routing. Only the localization of the called number at the selected outgoing gateway is considered in this example.
Figure 11-15 is an example with four called party transformation patterns in three partitions at headquarters (HQ_GW) and branch (Branch_GW) sites. Partition A is specific to HQ (local area code 703), while partition B includes generic transformation patterns used by both HQ and Branch. Partition C is specific to the Branch site (local area code 303). The HQ gateway is configured with a called party transformation CSS that includes partitions A and B. The Branch gateway is configured with a called party transformation CSS that includes partitions B and C.
The transformation pattern in partition A modifies all 11 called party number information into a seven-digit called party number. The pattern also configures the numbering plan type to subscriber. Ten- and 11-digit dialing is normally categorized with a numbering plan type of national. Some providers require the numbering plan type to be set to the proper numbering plan type or they will reject the call. The transformation pattern in partition C provides the same function for called party numbers that are within the Branch area code of 303. Partition B is a partition that is shared between both the HQ and Branch transformation CSSs. Partition B includes two transformation patterns:
- \+1XXXXXXXXXX
- \+.!
The first pattern matches on all 11-digit patterns beginning with the E.164 + character used to route international calls followed by a 1 and any ten digits. This pattern represents all U.S. area codes within a globalized route plan. The second pattern represents all other possible numbers that begin with the + character followed by two digits or more.
Calls to the following four called party numbers are transformed differently depending on the gateway to which they are routed:
- +49691234 is matched and transformed on both gateways to 49691234 with a numbering plan type set to international. If the ISDN provider does not support number types, a prefix of 011 must be used to indicate the fact that this is an international call.
- +14085551234 is matched and transformed on both gateways to 4085551234, with type national. If the ISDN provider does not support number types, a prefix of 011 must be used.
- +17035551234 is matched and transformed on the both gateways, but the outbound calls match on different transformation patterns because of the different CSSs used at the respective gateways. The +17035551234 called party number is routed out the HQ gateway as 5551234 with a numbering plan type of subscriber. The Branch gateway matches the \+1XXXXXXXXXX with a number plan type of national. If the ISDN provider does not support numbering plan types for international call routing, a prefix of 011 must be used to route an international call.
- +13035551234 is matched and transformed on the Branch gateway with the \+1303XXXXXXX transformation pattern. The called party number is sent out the HQ gateway with a called party number of 5551234 and a numbering plan type of subscriber. The called party number is sent out the Branch gateway as 303 5551234 and a number plan type of national. If the ISDN provider does not support number types, a prefix of 011 must be used.
Figure 11-16 shows an example of calling party number transformation using calling party transformation patterns in different partitions. The HQ and Branch gateways and phones are configured with different calling party transformation CSSs to change the calling number differently depending on which gateway processes the call. Only the localization of the calling party number at the HQ outgoing gateway is considered in this example.
)
Figure 11-16 Calling Party Transformation Patterns in Partitions
There are three calling party transformation patterns in three different partitions. Partition A is specific to HQ (local area code 703), while partition B includes a generic transformation pattern for all 11 digit numbers in the North American Numbering Plan (NANP). Partition C is specific to the Branch (local area code 303).
The HQ gateway phones are configured with a calling party transformation CSS that includes partitions A and B, while the Branch gateway and phones have a calling party transformation CSS that includes partitions B and C. The transformation pattern in partition A modifies all HQ globalized numbers to a seven-digit number with a numbering plan type of subscriber. The transformation pattern in partition C provides the same functionality for local calls at the Branch site. Partition B is used by both the HQ and Branch transformation CSSs. Partition B includes the transformation pattern of \+1XXXXXXXXXX and represents all area codes in the NANP.
The calling party numbers will be transformed as follows:
- A +17035551002 call from an HQ phone to the PSTN through the HQ gateway is transformed to 5551002 with a numbering plan type of subscriber.
- A +13035551001 call from a Branch phone to the PSTN through the HQ gateway is transformed to 3035551001 with a numbering plan type of national.
Calling Party Transformation Pattern Configuration
Calling party transformation patterns are configured in CUCM Administration. Choose Call Routing > Transformation > Transformation Pattern > Calling Party Transformation Pattern. Click the Add New button to create a new calling party transformation pattern.
In the pattern configuration, define a matching pattern and assign a partition to this pattern. Specify calling party transformations in the same way as the route pattern, route list, and translation pattern configurations covered earlier in this chapter. Figure 11-17 is a screen capture of the Calling Party Transformation Pattern Configuration page in CUCM Administration.
)
Figure 11-17 Calling Party Transformation Pattern Configuration
Called Party Transformation Pattern Configuration
Called party transformation patterns are configured in CUCM Administration. Choose Call Routing > Transformation > Transformation Pattern > Called Party Transformation Pattern. Click Add New to create a new called party transformation pattern. Figure 11-18 is a screen capture of a Called Party Transformation Pattern Configuration page.
)
Figure 11-18 Called Party Transformation Pattern Configuration
Transformation Calling Search Space
The transformation Calling Search Space (CSS) configuration is identical to the CSS configuration used to configure class of service (CoS) restrictions that was covered in the last chapter. The CSS is applied differently to restrict the patterns that are matched for the purpose of digit transformation. During digit analysis, CUCM treats transformation patterns similar to any other pattern in the call-routing database. Independent CSSs are normally created for the purpose of performing calling and called party digit transformation using transformation patterns. Calling and called party transformation CSSs can be applied in the phone, gateway, and device pool configuration locations of CUCM Administration.
Figure 11-19 is a screen capture of a CSS configuration that will be used as a transformation CSS. Transformation CSSs normally only have one partition.
)
Figure 11-19 Transformation CSS
Figure 11-20 illustrates the application of the CSS created in Figure 11-19 as a calling party transformation CSS on a Phone Configuration page in CUCM Administration.
)
Figure 11-20 Transformation CSS Application
Incoming Number Settings
Incoming transformation settings have the following characteristics:
- They allow the configuration of digit prefixes, digit stripping, and transformations to be applied to calling and called party numbers for calls inbound to the CUCM cluster. Different settings can be configured per number plan type (unknown, subscriber, national, and international) if this information is in the call signaling.
- Incoming calling and called party settings can be configured at the device, device pool, and/or global service parameter configuration levels in CUCM Administration.
- Incoming calling and called party setting apply to calls received from gateways and trunks. Incoming calling and called party settings are not applicable to calls that are received from phones. The external phone number mask of directory numbers is used to globalize the calling party number from Cisco IP Phones.
H.225 trunks and H.323 gateways support incoming calling and called party settings based on numbering plan type, but Media Gateway Control Protocol (MGCP) gateways support only incoming calling party settings based on numbering plan type. Session Initiation Protocol (SIP) does not support numbering plan types.
Incoming Calling Party Prefix Example: Globalization of Calling Number
Figure 11-21 shows an example of incoming calling party digit transformation for calling party number globalization using the E.164 + international operator pattern. Figure 11-22 is performing digit transformation based on the numbering plan type provided in the incoming call signaling from the provider in Hamburg, Germany.
)
Figure 11-21 Globalization of Calling Number
)
Figure 11-22 Gateway Calling Party Settings
Gateway Incoming Calling Party Settings Configuration
The gateway is configured with the following incoming calling party number digit manipulation:
- Prefix +4940 for calls that are received with a numbering plan type of subscriber.
- Prefix +49 for calls that are received with a numbering plan type of national.
- Prefix a + and strip the leading two digits of the calling party number for calls that are received with a numbering plan type of international.
Incoming calling party settings can be configured at the bottom of the gateway or trunk configuration level of CUCM Administration. Figure 11-23 is a screen capture of the configuration required to perform the digit transformation illustrated in Figure 11-22.
)
Figure 11-23 Calling Party Transformation Mask Example
Device Pool Incoming Calling and Called Party Transformation Calling Search Space
Selecting the Use Device Pool CSS check box causes CUCM to ignore any transformation CSS configured at the gateway or trunk level. The transformation CSS defined at the device pool that is associated to the gateway or trunk is applied instead.
The configuration of incoming calling and called party settings in the device pool is nearly identical to the configuration of these settings on gateways or trunks.
The only differences are the following:
- The device pool does not include a Use Device Pool CSS check box.
- If the Default keyword is used in any Prefix field, the corresponding incoming calling or called party settings set at the Cisco CallManager service parameter configuration level are applied.