Table Of Contents

Special Characters and Settings

Route Pattern Wildcards and Special Characters

Discard Digits Instructions

Calling Party Transformations Settings

Called Party Transformations Settings

Special Characters and Settings

---

Cisco CallManager Administration allows you to use special characters and settings to perform the following tasks:

•Allowing a single route pattern to match a range of numbers

•Removing a portion of the dialed digit string

•Manipulating the appearance of the calling party number for outgoing calls

•Manipulating the dialed digits, or called party number, for outgoing calls

For more information on how to use special characters and settings, see the following topics:

•Route Pattern Wildcards and Special Characters

•Discard Digits Instructions

•Calling Party Transformations Settings

•Called Party Transformations Settings

Route Pattern Wildcards and Special Characters

Route pattern wildcards and special characters allow a single route pattern to match a range of numbers (addresses). Use these wildcards and special characters also to build instructions that enable the Cisco CallManager to manipulate a number before sending it to an adjacent system.

Table 22-1 describes the wildcards and special characters supported by Cisco CallManager.

Table 22-1 Wildcards and Special Characters 

Character	Description	Examples
@	The at symbol (@) wildcard matches all NANP numbers. Each route pattern can have only one @ wildcard.	The route pattern 9.@ routes or blocks all numbers that are recognized by the NANP. The following route patterns examples show NANP numbers that are encompassed by the @ wildcard: •0 •1411 •19725551234 •101028819725551234 •01133123456789
X	The X wildcard matches any single digit in the range 0 through 9.	The route pattern 9XXX routes or blocks all numbers in the range 9000 through 9999.
!	The exclamation point (!) wildcard matches one or more digits in the range 0 through 9.	The route pattern 91! routes or blocks all numbers in the range 910 through 91999999999999999999999.
?	The question mark (?) wildcard matches zero or more occurrences of the preceding digit or wildcard value.	The route pattern 91X? routes or blocks all numbers in the range 91 through 91999999999999999999999.
+	The plus sign (+) wildcard matches one or more occurrences of the preceding digit or wildcard value.	The route pattern 91X+ routes or blocks all numbers in the range 910 through 91999999999999999999999.
[ ]	The square bracket ([ ]) characters enclose a range of values.	The route pattern 813510[012345] routes or blocks all numbers in the range 8135100 through 8135105.
-	The hyphen (-) character, used with the square brackets, denotes a range of values.	The route pattern 813510[0-5] routes or blocks all numbers in the range 8135100 through 8135105.
^	The circumflex (^) character, used with the square brackets, negates a range of values. Ensure that it is the first character following the opening bracket ([). Each route pattern can have only one ^ character.	The route pattern 813510[^0-5] routes or blocks all numbers in the range 8135106 through 8135109.
.	The dot (.) character, used as a delimiter, separates the Cisco CallManager access code from the directory number. Use this special character, with the discard digits instructions, to strip off the Cisco CallManager access code before sending the number to an adjacent system. Each route pattern can have only one dot (.) character.	The route pattern 9.@ identifies the initial 9 as the Cisco CallManager access code in an NANP call.
*	The asterisk (*) character can provide an extra digit for special dialed numbers.	You can configure the route pattern *411 to provide access to the internal operator for directory assistance.
#	The octothorpe (#) character generally identifies the end of the dialing sequence. Ensure the # character is the last character in the pattern.	The route pattern 901181910555# routes or blocks an international number that is dialed from within the NANP. The # character after the last 5 identifies this digit as the last digit in the sequence.

Table 22-2 lists Cisco CallManager Administration fields that require route patterns and shows the valid entries for each field.

Table 22-2 Field Entries 

Field	Valid entries
Call Park Number/Range	[ ^ 0 1 2 3 4 5 6 7 8 9 - ] X * #
Calling Party Transform Mask	0 1 2 3 4 5 6 7 8 9 X * #
Called Party Transform Mask	0 1 2 3 4 5 6 7 8 9 X * #
Caller ID DN (Gateways)	0 1 2 3 4 5 6 7 8 9 X * #
Directory Number	[ ^ 0 1 2 3 4 5 6 7 8 9 - ] + ? ! X * # +
Directory Number (Call Pickup Group)	0 1 2 3 4 5 6 7 8 9
External Phone Number Mask	0 1 2 3 4 5 6 7 8 9 X * #
Forward All	0 1 2 3 4 5 6 7 8 9 * #
Forward Busy	0 1 2 3 4 5 6 7 8 9 * #
Forward No Answer	0 1 2 3 4 5 6 7 8 9 * #
Meet-Me Conference Number	[ ^ 0 1 2 3 4 5 6 7 8 9 - ] X * #
Prefix Digits	0 1 2 3 4 5 6 7 8 9 * #
Prefix DN (Gateways)	0 1 2 3 4 5 6 7 8 9 * #
Route Filter Tag Values	[ ^ 0 1 2 3 4 5 6 7 8 9 - ] X * #
Route Pattern	[ ^ 0 1 2 3 4 5 6 7 8 9 - ] + ? ! X * # + . @
Translation Pattern	[ ^ 0 1 2 3 4 5 6 7 8 9 - ] + ? ! X * # + . @

Discard Digits Instructions

A discard digits instruction (DDI) removes a portion of the dialed digit string before passing the number on to the adjacent system. A DDI must remove portions of the digit string, for example, when an external access code is needed to route the call to the PSTN, but the PSTN switch does not expect that access code.

Table 22-3 lists DDIs and describes the effects of applying each DDI to a dialed number.

Table 22-3 Discard Digits Instructions 

DDI	Effect	Example
10-10-Dialing	This DDI removes •IXC access code	Route pattern: 9.@ Dialed digit string: 910102889728135000 After applying DDI: 99728135000
10-10-Dialing Trailing-#	This DDI removes •IXC access code •End-of-dialing character for international calls	Route pattern: 9.@ Dialed digit string: 9101028801181910555# After applying DDI: 901181910555
11/10D->7D	This DDI removes •Long-distance direct-dialing code •Long-distance operator-assisted dialing code •IXC access code •Area code •Local area code This DDI creates a 7-digit local number from an 11- or 10-digit dialed number.	Route pattern: 9.@ Dialed digit string: 919728135000 or 99728135000 After applying DDI: 98135000
11/10D->7D Trailing-#	This DDI removes •Long-distance direct-dialing code •Long-distance operator-assisted dialing code •IXC access code •Area code •Local area code •End-of-dialing character for international calls This DDI creates a 7-digit local number from an 11- or 10-digit dialed number.	Route pattern: 9.@ Dialed digit string: 919728135000 or 99728135000 After applying DDI: 98135000
11D->10D	This DDI removes •Long-distance direct-dialing code •Long-distance operator-assisted dialing code •IXC access code	Route pattern: 9.@ Dialed digit string: 919728135000 After applying DDI: 99728135000
11D->10D Trailing-#	This DDI removes •Long-distance direct-dialing code •Long-distance operator-assisted dialing code •End-of-dialing character for international calls •IXC access code	Route pattern: 9.@ Dialed digit string: 919728135000 After applying DDI: 99728135000
Intl TollBypass	This DDI removes •International access code •International direct-dialing code •Country code •IXC access code •International operator-assisted dialing code	Route pattern: 9.@ Dialed digit string: 901181910555 After applying DDI: 9910555
Intl TollBypass Trailing-#	This DDI removes •International access code •International direct-dialing code •Country code •IXC access code •International operator-assisted dialing code •End-of-dialing character	Route pattern: 9.@ Dialed digit string: 901181910555# After applying DDI: 9910555
NoDigits	This DDI removes no digits.	Route pattern: 9.@ Dialed digit string: 919728135000 After applying DDI: 919728135000
Trailing-#	This DDI removes •End-of-dialing character for international calls	Route pattern: 9.@ Dialed digit string: 901181910555# After applying DDI: 901181910555
PreAt	This DDI removes all digits prior to the NANP portion of the route pattern, including •Cisco CallManager external access code •PBX external access code	Route pattern: 8.9@ Dialed digit string: 899728135000 After applying DDI: 9728135000
PreAt Trailing-#	This DDI removes all digits prior to the NANP portion of the route pattern, including •Cisco CallManager external access code •PBX external access code •End-of-dialing character for international calls	Route pattern: 8.9@ Dialed digit string: 8901181910555# After applying DDI: 01181910555
PreAt 10-10-Dialing	This DDI removes all digits prior to the NANP portion of the route pattern, including •Cisco CallManager external access code •PBX external access code •IXC access code	Route pattern: 8.9@ Dialed digit string: 8910102889728135000 After applying DDI: 9728135000
PreAt 10-10-Dialing Trailing-#	This DDI removes all digits prior to the NANP portion of the route pattern, including •Cisco CallManager external access code •PBX external access code •IXC access code •End-of-dialing character for international calls	Route pattern: 8.9@ Dialed digit string: 89101028801181910555# After applying DDI: 01181910555
PreAt 11/10D->7D	This DDI removes all digits prior to the NANP portion of the route pattern, including •Cisco CallManager external access code •PBX external access code •Long-distance direct-dialing code •Long-distance operator-assisted dialing code •IXC access code •Area code •Local area code This DDI creates a 7-digit local number from an 11- or 10-digit dialed number.	Route pattern: 8.9@ Dialed digit string: 8919728135000 or 899728135000 After applying DDI: 8135000
PreAt 11/10D->7D Trailing-#	This DDI removes all digits prior to the NANP portion of the route pattern, including •Cisco CallManager external access code •PBX external access code •Long-distance direct-dialing code •Long-distance operator-assisted dialing code •IXC access code •Area code •Local area code •End-of-dialing character for international calls This DDI creates a 7-digit local number from an 11- or 10-digit dialed number.	Route pattern: 8.9@ Dialed digit string: 8919728135000 or 899728135000 After applying DDI: 8135000
PreAt 11D->10D	This DDI removes all digits prior to the NANP portion of the route pattern, including •Cisco CallManager external access code •PBX external access code •Long-distance direct-dialing code •Long-distance operator-assisted dialing code •IXC access code	Route pattern: 8.9@ Dialed digit string: 8919728135000 After applying DDI: 9728135000
PreAt 11D->10D Trailing-#	This DDI removes all digits prior to the NANP portion of the route pattern, including •Cisco CallManager external access code •PBX external access code •Long-distance direct-dialing code •Long-distance operator-assisted dialing code •IXC access code •End-of-dialing character for international calls	Route pattern: 8.9@ Dialed digit string: 8919728135000 After applying DDI: 9728135000
PreAt Intl TollBypass	This DDI removes all digits prior to the NANP portion of the route pattern, including •Cisco CallManager external access code •PBX external access code •International access code •International direct-dialing code •Country code •IXC access code •International operator-assisted dialing code	Route pattern: 8.9@ Dialed digit string: 8901181910555 After applying DDI: 910555
PreAt Intl TollBypass Trailing-#	This DDI removes all digits prior to the NANP portion of the route pattern, including •Cisco CallManager external access code •PBX external access code •International access code •International direct-dialing code •Country code •IXC access code •International operator-assisted dialing code •End-of-dialing character	Route pattern: 8.9@ Dialed digit string: 8901181910555# After applying DDI: 910555
PreDot	This DDI removes •Cisco CallManager external access code	Route pattern: 8.9@ Dialed digit string: 899728135000 After applying DDI: 99728135000
PreDot Trailing-#	This DDI removes •Cisco CallManager external access code •End-of-dialing character for international calls	Route pattern: 8.9@ Dialed digit string: 8901181910555# After applying DDI: 901181910555
PreDot 10-10-Dialing	This DDI removes •Cisco CallManager external access code •IXC access code	Route pattern: 8.9@ Dialed digit string: 8910102889728135000 After applying DDI: 99728135000
PreDot 10-10-Dialing Trailing-#	This DDI removes •Cisco CallManager external access code •IXC access code •End-of-dialing character for international calls	Route pattern: 8.9@ Dialed digit string: 89101028801181910555# After applying DDI: 901181910555
PreDot 11/10D->7D	This DDI removes •Cisco CallManager external access code •Long-distance direct-dialing code •Long-distance operator-assisted dialing code •IXC access code •Area code •Local area code This DDI creates a 7-digit local number from an 11- or 10-digit dialed number.	Route pattern: 8.9@ Dialed digit string: 8919728135000 or 899728135000 After applying DDI: 98135000
PreDot 11/10D->7D Trailing-#	This DDI removes •Cisco CallManager external access code •Long-distance direct-dialing code •Long-distance operator-assisted dialing code •IXC access code •Area code •Local area code •End-of-dialing character for international calls This DDI creates a 7-digit local number from an 11- or 10-digit dialed number.	Route pattern: 8.9@ Dialed digit string: 8919728135000 or 899728135000 After applying DDI: 98135000
PreDot 11D->10D	This DDI removes •Cisco CallManager external access code •Long-distance direct-dialing code •Long-distance operator-assisted dialing code •IXC access code	Route pattern: 8.9@ Dialed digit string: 8919728135000 After applying DDI: 99728135000
PreDot 11D->10D Trailing-#	This DDI removes •Cisco CallManager external access code •Long-distance direct-dialing code •Long-distance operator-assisted dialing code •IXC access code •End-of-dialing character for international calls	Route pattern: 8.9@ Dialed digit string: 8919728135000 After applying DDI: 99728135000
PreDot Intl TollBypass	This DDI removes •Cisco CallManager external access code •International access code •International direct-dialing code •Country code •IXC access code •International operator-assisted dialing code	Route pattern: 8.9@ Dialed digit string: 8901181910555 After applying DDI: 9910555
PreDot Intl TollBypass Trailing-#	This DDI removes •Cisco CallManager external access code •International access code •International direct-dialing code •Country code •IXC access code •International operator-assisted dialing code •End-of-dialing character	Route pattern: 8.9@ Dialed digit string: 8901181910555# After applying DDI: 9910555

Calling Party Transformations Settings

Calling party transformations settings allow you to manipulate the appearance of the calling party number for outgoing calls. Cisco CallManager uses the calling party number for calling line identification (CLID). During an outgoing call, the CLID passes to each private branch exchange (PBX), central office (CO), and interexchange carrier (IXC) as the call progresses. The calling party receives the CLID when the call completes.

The assignment of the calling party transformations settings that are used in route lists goes to the individual route groups comprising the list, rather than to the route list as a whole. The calling party transformations settings that are assigned to the route groups in a route list override any calling party transformations settings that are assigned to a route pattern that is associated with that route list.

Table 22-4 describes the fields, options, and values that are used to specify calling party transformation for a route group.

Table 22-4 Calling Party Transformations Settings 

Field Name	Description
Use Calling Party's External Phone Number Mask	This field determines whether the full, external phone number is used for CLID on outgoing calls. (Configure the external number by using the Directory Number Configuration window.) The options for this field include Default, Off, and On: •Default: This setting indicates that the route group does not govern the calling party external phone number and calling party transform masks. If a calling party external phone number mask or transform mask is chosen for the route pattern, calls that are routed through this route group use those masks. •Off: This setting indicates that the calling party external phone number is not used for CLID. If no transform mask is entered for this route group, calls that are routed through this group do not get associated with a CLID. •On: This setting indicates that the calling party full, external number is used for CLID.
Calling Party Transform Mask	This field specifies the calling party transform mask for all calls that are routed through this route group. Valid values for this field range from 0 through 9, the wildcard character X, and the characters * and #. You can also leave this field blank. If it is blank and the preceding field is set to Off, this means that no calling party number is available for CLID. The calling party transform mask can contain up to 50 digits.
Prefix Digits (Outgoing Calls)	This field contains a prefix digit or a set of Prefix Digits (Outgoing Calls) that are appended to the calling party number on all calls that are routed through this route group. Valid values for this field range from 0 through 9, the characters * and #, and blank. Prefix Digits (Outgoing Calls) can contain up to 50 digits.
Calling Party Presentation (outgoing call)	This field determines whether the calling party phone number displays on the called party phone display screen. The Route Pattern Configuration, Translation Pattern Configuration, and Gateway Configuration windows use the Calling Party Presentation field. The options for this field include Default, Allowed, and Restricted. Each call made in Cisco CallManager has the calling party presentation field checked. If a translation pattern is configured for the calling party, the value set in the translation pattern gets checked first. The indicator gets set to the configuration value (default, allowed, or restricted) in the calling party presentation field. Next, if a route pattern is configured for the calling party, the value that is set in the route pattern configuration gets checked, and the indicator gets set in the calling party presentation field. The gateway configuration gets checked last, and the indicator gets set in the calling party presentation field. In other words, the value of the calling party presentation field could change from the time that the calling party initiated the call to the time that the call receives the called party. The following list gives the options for this field: •Default: If field is set to this value, calling party line presentation does not get modified. •Allowed: Setting this field in the gateway displays the calling party line number in the called party phone display screen. •Restricted: Setting this field in the gateway displays Unknown Number in the called party phone display screen.
Calling Party Presentation (incoming call)	For incoming calls, the gateway does not apply its calling party presentation setting. If the incoming call goes through a translation or route pattern and the calling party presentation setting is set to allowed or restricted, the calling party line presentation gets modified with the translation or route pattern setting. If the call comes into the Cisco CallManager system and then goes out to a PBX or the PSTN, the outgoing call rules apply as stated in Table 22-4.

Related Topics

•Route Pattern Wildcards and Special Characters

•Understanding Route Plans, Cisco CallManager System Guide

Called Party Transformations Settings

Called party transformations settings allow you to manipulate the dialed digits, or called party number, for outgoing calls. Examples of manipulating called numbers include appending or removing prefix digits (outgoing calls), appending area codes to calls dialed as seven-digit numbers, appending area codes and office codes to interoffice calls dialed as four- or five-digit extensions, and suppressing carrier access codes for equal access calls.

The assignment of the called party transformations settings that are used in route lists goes to the individual route groups that comprise the list, rather than to the route list as a whole. The called party transformations settings that are assigned to the route groups in a route list override any called party transformations settings that are assigned to a route pattern that is associated with that route list.

Table 22-5 describes the fields, options, and values that are used to specify called party transformations for a route group.

Table 22-5 Called Party Transformations Settings 

Field Name	Description
Dial Plan	This field determines which dialing plan is used. If NANP is not already chosen, change this field to North American Numbering Plan. Note The Dial Plan field only appears when a route group is inserted in a route list. After the route group is inserted, you cannot modify this field.
Discard Digits	This field contains a list of discard patterns that control the discard digit instructions. For example, in a system where users must dial 9 to make a call to the public switched telephone network (PSTN), the PreDot discard pattern causes the 9 to be stripped from the dialed digit string. See the "Discard Digits Instructions" section for more information. Note Any setting other than the default setting of <None> overrides the setting in the route pattern. The <None> setting means "do not discard digits."
Called Party Transform Mask	This field specifies the called party transform mask for all calls that are routed through this route group. Valid values for this field range from 0 through 9, the wildcard character X, and characters * and #. You can also leave this field blank. If this field is blank, no transformation takes place; Cisco CallManager sends the dialed digits exactly as dialed. The called party transform mask can contain up to 50 digits.
Prefix Digits (Outgoing Calls)	This field contains a prefix digit or a set of Prefix Digits (Outgoing Calls) that are appended to the called party number on all calls that are routed through this route group. Valid values for this field range from 0 through 9, the characters * and #, and blank. Prefix Digits (Outgoing Calls) can contain up to 50 digits.

Related Topics

•Route Pattern Wildcards and Special Characters

•Discard Digits Instructions

•Understanding Route Plans, Cisco CallManager System Guide