Which route pattern is used if the end user dials 9 for an outside line and then dials 13135551212?

9.! uses the variable-length ! wildcard that matches one or more digits, which would match this number, but CUCM's best-match algorithm selects 9.1XXXXXXXXXX first because it contains a literal digit 1 making it more specific.

9! omits the dot separator, meaning the entire dialed string including the 9 access code digit is forwarded to the destination unchanged rather than being stripped, which would cause incorrect call routing.

In CUCM route patterns the asterisk (*) character represents the physical * key on the phone keypad and is not interpreted as a zero-or-more digit wildcard, so 9.* would only match if the caller presses the * key after 9.

9.XXXXXXXXXXX uses 11 X wildcards that would technically match 9+13135551212, but because every position is a wildcard rather than a literal digit, it is less specific than 9.1XXXXXXXXXX and CUCM's match algorithm will not select it.

The dialed number 9+13135551212 breaks down as: outside access digit 9, long-distance prefix 1, and 10-digit number 3135551212. The pattern 9.1XXXXXXXXXX uses a literal 1 after the dot separator followed by exactly 10 X wildcards, which is a precise match for this format. CUCM's best-match algorithm favors patterns with literal digits over wildcards at the same position, so this pattern is selected over less specific alternatives like 9.XXXXXXXXXXX.

9.[^9]XXXXXXXXXX matches any non-9 digit followed by 10 digits after the separator, which would technically match this number since 1 is not 9, but the literal digit 1 in 9.1XXXXXXXXXX is more specific than the range expression [^9], so CUCM selects E instead.