Configure Called Party Transformation Patterns ---------------------------------------------- The parameters in the Called Party Transformation Patterns window provide appropriate caller information by using the Called Party Transformation calling search space on the destination device. Be aware that calls through transformation patterns are not routable. When this pattern is matched, the call does not route to any device. 1. Log in as the Provider, Reseller, or Customer Administrator. 2. Perform one of the following: * If you logged in as the Provider or Reseller Administrator, select **Device Management > CUCM > Called Party Transformation Patterns**. * If you logged in as the Customer Administrator, select **Device Management > Advanced > Called Party Transformation Patterns**. 3. Make sure that the hierarchy path is set to the correct level. 4. Perform one of the following: * To add a new called party transformation pattern, click **Add**, then go to step 5. * To edit an existing called party transformation pattern, click on the line item in the table. Go to step 6. 5. In the popup, select from the drop-down the network device list (NDL) to which you are adding the called party transformation pattern, and click **OK**. .. note:: The NDL popup will only appear when you are adding a new called party transformation pattern. If you are updating an existing pattern, go to Step 6. If you are adding the called party transformation pattern to a Site hierarchy node, the NDL popup will not appear. You will go right to the Called Party Transformation Pattern add tabs using the NDL associated to the site. 6. From the Pattern Definition tab, modify the following fields as required. .. tabularcolumns:: |p{4cm}|p{11cm}| +-----------------+------------------------------------------+ | Option | Description | +=================+==========================================+ | Pattern | Enter the transformation pattern, | | (Mandatory) | including numbers and wildcards (do not | | | use spaces); for example, for NANP, | | | enter 9.@ for typical local access, or | | | 8XXX for a typical private network | | | numbering plan. Valid characters include | | | the uppercase letters A, B, C, and D and | | | \+, which represents the international | | | escape character +. | | | | | | Note | | | | | | Ensure that the pattern is | | | unique. Check the transformation | | | pattern, route pattern, | | | translation pattern, directory | | | number, call park number, call | | | pickup number, message waiting | | | on/off, or meet me number if you | | | receive an error that indicates | | | duplicate entries. You can also | | | check the route plan report. | | | | | | Default value: None | +-----------------+------------------------------------------+ | Partition | If you want to use a partition to | | | restrict access to the transformation | | | pattern, choose the desired partition | | | from the drop-down list box. If you do | | | not want to restrict access to the | | | transformation pattern, choose | | | for the partition. | | | | | | Note | | | | | | Transformation patterns should | | | be configured in different non- | | | NULL partitions than dialing | | | patterns such as route patterns | | | and directory numbers. For | | | transformation pattern lookups, | | | the patterns in NULL partitions | | | get ignored. | | | | | | Make sure that the combination | | | of pattern, route filter, and | | | partition is unique within the | | | Cisco Unified Communications | | | Manager cluster. | +-----------------+------------------------------------------+ | Description | Enter a description of the | | | transformation pattern. The description | | | can include up to 50 characters in any | | | language, but it cannot include | | | double-quotes ("), percentage sign (%), | | | ampersand (&), or angle brackets (<>). | +-----------------+------------------------------------------+ | Numbering Plan | Choose a numbering plan. | +-----------------+------------------------------------------+ | Route Filter | If your transformation pattern includes | | | the @ wildcard, you may choose a route | | | filter. The optional act of choosing a | | | route filter restricts certain number | | | patterns. | | | | | | The route filters that display depend on | | | the numbering plan that you choose from | | | the Numbering Plan drop-down list box. | +-----------------+------------------------------------------+ | MLPP Preemption | Check this box to make the numbers in a | | Disabled | transformation pattern non-preemptable. | +-----------------+------------------------------------------+ 7. From the **Called Party Transformations** tab, modify the following fields as required. .. tabularcolumns:: |p{4cm}|p{11cm}| +---------------------+--------------------------------------+ | Option | Description | +=====================+======================================+ | Digit Discards | Choose the discard digit | | | instructions that you want to be | | | associated with this called party | | | transformation pattern. | +---------------------+--------------------------------------+ | Called Party | Enter a transformation mask value. | | Transformation Mask | Valid entries include the digits 0 | | | through 9; the wildcard characters | | | X, asterisk (*), and octothorpe (#); | | | the international escape character | | | +; and blank. If this field is blank | | | and the preceding field is not | | | checked, no transformation takes | | | place. | +---------------------+--------------------------------------+ | Prefix Digits | Enter prefix digits in the field. | | | Valid entries include the digits 0 | | | through 9, the wildcard characters | | | asterisk (*) and octothorpe (#),the | | | international escape character +, | | | and blank. | | | | | | Note | | | | | | The appended prefix digit | | | does not affect which | | | directory numbers route to | | | the assigned device. | +---------------------+--------------------------------------+ | Called Party Number | Choose the format for the number | | Type | type in called party directory | | | numbers. | | | | | | Cisco Unified Communications Manager | | | sets the called 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 called directory number to be | | | encoded to a non-national type | | | numbering plan. | | | | | | Choose one of the following options: | | | | | | * Cisco CallManager - Use when the | | | Cisco Unified Communications | | | Manager sets the directory | | | number type. | | | * Unknown - Use 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. | +---------------------+--------------------------------------+ .. tabularcolumns:: |p{4cm}|p{11cm}| +---------------------+--------------------------------------+ | Option | Description | +=====================+======================================+ | Called Party | Choose the format for the numbering | | Numbering Plan | plan in called party directory | | | numbers. | | | | | | Cisco Unified Communications Manager | | | sets the called DN numbering plan. | | | 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 PBXs by using | | | routing as a non-national type | | | number. | | | | | | Choose one of the following options: | | | | | | * Cisco CallManager - Use when the | | | Cisco Unified Communications | | | Manager sets the Numbering Plan | | | in the directory number. | | | * ISDN - Use when you are dialing | | | outside the dialing plan for | | | your country. | | | * National Standard - Use when you | | | are dialing within the dialing | | | plan for your country. | | | * Private - Use when you are | | | dialing within a private | | | network. | | | * Unknown - Use when the dialing | | | plan is unknown. | +---------------------+--------------------------------------+ 8. Click **Save**. The called party transformation pattern appears in the list. To modify any of these characteristics, click the item in the list, make your changes, and click **Save**. To delete a called party transformation pattern, check the box to the left of the Name column in the group list, and click **Delete**.