350-801 · Question #11
Which call routing pattern is used for phone numbers that are in the E.164 format?
The correct answer is B. \+.! Route pattern. For E.164 formatted phone numbers in Cisco Unified Communications Manager, the \+.! route pattern is used to match numbers starting with a plus sign followed by any digits.
Question
Which call routing pattern is used for phone numbers that are in the E.164 format?
Options
- A/+.! Route Pattern
- B+.! Route pattern
- C+.! Translation pattern
- D+1. [2-9]XX[2-9]XXXXXXX called Party Transformation pattern
How the community answered
(54 responses)- A2% (1)
- B94% (51)
- C4% (2)
Why each option
For E.164 formatted phone numbers in Cisco Unified Communications Manager, the \+.! route pattern is used to match numbers starting with a plus sign followed by any digits.
The forward slash / is not the correct escape character for the plus sign in CUCM route patterns; a backslash \ is required.
The \+.! route pattern is the correct wild-card representation for matching E.164 numbers. The backslash escapes the plus sign, indicating it is a literal plus, and the . (dot) matches any single digit, while ! (exclamation mark) matches one or more occurrences of the preceding character (the dot), effectively matching a plus sign followed by one or more digits.
While \+.! can be used in a translation pattern, the question asks for a 'call routing pattern'. A route pattern is directly used for routing calls, whereas a translation pattern is used to modify digits before routing. For E.164 routing, a route pattern is the primary mechanism.
This is a specific pattern for North American Numbering Plan (NANP) numbers, not a general pattern for all E.164 numbers. Also, it specifies a 'called Party Transformation pattern,' which is for digit manipulation, not the primary routing pattern itself.
Concept tested: E.164 route pattern in CUCM
Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/srnd/collab12/collab12/dialplan.html
Topics
Community Discussion
No community discussion yet for this question.