cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4943
Views
15
Helpful
10
Replies

purpose of "\" in route pattern

o.tasaddaq1
Level 1
Level 1

Hi,

What is the purpose of charater "\" in route pattern? Thanks

10 Replies 10

Jitender Bhandari
Cisco Employee
Cisco Employee

Hi,

check below

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/9_1_1/ccmsys/CUCM_BK_C5565591_00_cucm-system-guide-91/CUCM_BK_C5565591_00_cucm-system-guide-91_chapter_010000.html

Table 6 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 A B C D * # +

Called Party Transform Mask

0 1 2 3 4 5 6 7 8 9 X A B C D * # +

Caller ID DN (Gateways and Trunks)

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 Number)

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 A B C D * # +

Prefix DN (Gateways and Trunks)

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 A B C D - ] + ? ! X * # + . @ \+

Translation Pattern

[ ^ 0 1 2 3 4 5 6 7 8 9 A B C D - ] + ? ! X * # + . @ \+

Hunt Pilot

[ ^ 0 1 2 3 4 5 6 7 8 9 A B C D - ] + ? ! X * # + . @ \+

HTH

JB

Table 5 Wildcards and Special Characters

Character

Description

Examples

@

The at symbol (@) wildcard matches all National Numbering Plan numbers.

Each route pattern can have only one @ wildcard.

The route pattern 9.@ routes or blocks all numbers that the National Numbering Plan recognizes.

The following route patterns examples show National Numbering Plan numbers that the @ wildcard encompasses:

  • 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 Unified Communications Manager access code from the directory number.

Use this special character, with the discard digits instructions, to strip off the Cisco Unified Communications Manager 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 Unified Communications Manager access code in a National Numbering Plan 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 National Numbering Plan. The # character after the last 5 identifies this digit as the last digit in the sequence.

\+

A plus sign preceded by a backslash, that is, \+, indicates that you want to configure the international escape character +.

Using \+ means that the international escape character + is used as a dialable digit, not as a wildcard.

For examples, see the Use the International Escape Character.

JB

Chris Deren
Hall of Fame
Hall of Fame

It does nothing, but since + was already defined as wildcard for patterns in CUCM before +e164 dial plan became a feature on CUCM, in order to allow + to be defined as an actual + digit for +e164 numbers Cisco allowed it by prefixing + with \. So anytime you see pattern/DN starting with \ it implies that + follows for +e164 numbers.

sfsdfsdf

Missed calls would imply formatting of calling number not called number, thus not any pattern. if I understand correctly you missed calls on Lync show up incorrectly? Are you saying they show the "\" as part of it? That does not make sense as "\" would not be delivered as part of any phone call it is there only for designation purposes on CUCM admin side.

Please explain the call flow and what is showing up, and what would you like to see on which side.

You can achieve all "modifications" via called or calling party transformations. 

when someone calls me from outside then then number is being displayed not in proper format in lync but in fone its ok. 

Like i reveice notification as +919123456789 called you. it should be without country code as 9123456789 (dialable number display)

in fone , i am getting correct display as 9123456789 because of incoming calling party prefix 9.

Now, we have SIP trunk between CUCM & Lync. RP is \+91123456789. Shall i make change in Incoming Calling Party Settings of SIP Trunk.

Under call routing --> transformation --> calling party transformation define calling party transformation as \+91.XXXXXXXXX, with discard digits set to PreDot, assign it to new custom partition. Build CSS with this partition assigned to it. On the SIP trunk pointing to Lync under "Outbound calls" section select this new CSS under "Calling Party Transformation CSS" and unselect "Use Device Pool Calling Party Transformation CSS". Save the trunk and reset it.

Can you please see attachement.

Looks fine, just confused about the partition name. This is to address CUCM to Lync calling transformation so why did you call the PT LyncIncoming?

shall i create another PT?

Can you please describe the work flow?

how its adding +91 number in lync missed calls notification but not in phone call display?