A route pattern is a dial-plan rule that tells a call-control system what to do with a string of dialed digits. In Cisco Unified Communications Manager (CUCM), patterns can match individual numbers, number ranges, or longer variable-length strings. Wildcards make that possible without defining one rule for every extension or public telephone number. Their purpose is precise matching and routing—not vague, unlimited flexibility—and their meaning depends on the call-control platform in use.
Cisco CUCM route patterns are not identical to Cisco IOS voice dial-peer destination patterns. Both use digit matching, but they have different configuration objects and behavior. Before applying an example, identify the system, version, calling search space, partition, gateway or trunk, and any digit transformations involved. A syntactically valid pattern can still route a call incorrectly if its policy context is wrong.
Start with the dial plan’s intended outcomes
A dial plan should specify which callers may reach which destination types: internal extensions, emergency services, local and national public networks, international numbers, and restricted destinations. It should also describe the numbering conventions that callers see, such as whether users dial an outside-line prefix, use full E.164 numbers, or select an abbreviated internal range.
Write test cases before building the patterns. For each representative dial string, record the originating device or calling search space, the expected route, and the digits that the far end should receive. Include negative cases: calls that must not match an international pattern, attempts to dial a restricted number, and an incomplete string that should not start routing early. A pattern table with only successful examples cannot expose overlapping or overbroad matches.
The X wildcard matches one digit
In CUCM, X matches one decimal digit from 0 through 9. A route pattern such as 9XXX can match four-digit strings beginning with 9. That simplicity makes X useful for fixed-length extension ranges, access codes, and controlled destinations with known lengths. It does not match arbitrary sequences, and one X does not mean several digits.
Suppose a branch uses a five-digit internal range beginning with 73. The pattern 73XXX covers the relevant five-digit numbers, but the same range may also contain reserved service codes. A match is therefore not sufficient proof that every number should be routed: reserve exceptions, verify overlap with translation patterns, and test from the partitions and calling search spaces that will use it.
The final routing decision depends on more than the characters in the pattern. Route list configuration, partition visibility, destination availability, and any digit manipulation can change the result. Engineers should keep the matching rule and the eventual gateway or trunk selection distinct when diagnosing a call.
The exclamation point matches a variable-length sequence
The CUCM ! wildcard represents one or more digits. It is useful for dial strings whose exact length is not fixed, such as some international or carrier-specific formats. A pattern such as 9011! can cover many numbers beginning with an international-access prefix, but it is deliberately broad. In production it must be controlled by routing permissions, numbering rules, and verification against the provider’s accepted formats.
Variable-length patterns raise a practical question: when does the system have enough digits to route the call? Interdigit timing and termination characters can affect user experience. If a broad variable-length rule overlaps with fixed patterns, users may notice delay or unexpected matches. Test complete and incomplete inputs and record how the phone, CUCM, and PSTN provider behave.
Not every environment should use the same international pattern. Country-specific dial plans, SIP trunk requirements, and emergency-number handling differ. Avoid copying a generic training example into production without confirming local numbering regulation and service-provider constraints.
Understand the question mark and plus operators
In CUCM route-pattern syntax, ? means zero or more occurrences of the preceding digit or wildcard expression; + means one or more occurrences of the preceding digit or wildcard expression. These are repetition operators, not standalone substitutes for any arbitrary digit string. That distinction is easy to miss when administrators are familiar with regular expressions or with the syntax of another dial-plan platform.
For example, Cisco documentation illustrates 91X? to show an optional repeated digit-matching expression after the 91 prefix. Whether such an expression is appropriate in a real numbering plan depends on which variable lengths are valid. Use exact examples from release-specific CUCM documentation, and test the matching results rather than assuming that a symbol shares its meaning with Linux glob syntax or a programming language.
A production plan rarely needs exotic repetition for every destination. Fixed ranges with X and carefully limited variable-length patterns are easier to operate. Use complex expressions only when they clarify a real requirement and can be documented with positive and negative dialed-number examples.
Brackets, ranges, and the at symbol
Brackets group accepted digits at a particular position. A pattern such as 8[2-5]XX can cover numbers that begin with 8, contain a digit from 2 through 5, and then have two further digits. This is more precise than an unrestricted 8XXX if the numbering plan reserves the other second digits. Square-bracket patterns are particularly useful for avoiding accidental overlap with special destinations.
CUCM also supports @ in the context of recognized national numbering-plan numbers. Its behavior is specific to the call-control system’s number plan and supported pattern rules. It should not be treated as a generic wildcard that is safe in any country’s dial plan. Use explicit rules where operational requirements and provider expectations call for them.
Pattern matching must be tested in combination with route and translation rules. A source number can pass through translation or normalization before it is sent to a gateway or SIP trunk. Document the number at each stage: as dialed, as matched, as transformed, and as sent. This is more reliable than judging routing from the pattern’s name alone.
Partitions and calling search spaces control visibility
A route pattern in CUCM resides in a partition. A calling search space determines which partitions a device or line can search. This allows the same dialed digits to lead to different authorized outcomes, or to be unavailable to certain users. An international-dialing rule might be visible only to authorized devices even though the pattern technically matches a valid number.
When a phone receives reorder tone or a call follows an unexpected route, verify its effective calling search space and the pattern’s partition. A pattern can be perfectly valid yet unreachable to a particular phone because the search space does not contain its partition. Conversely, placing a broad pattern in a widely accessible partition can expose destinations that should have been restricted.
Document the policy as a matrix: caller class, allowed destination class, partition, and expected route. Reviewing that matrix with the security or telecom owner helps prevent the dial plan from becoming a collection of undocumented exceptions.
Emergency calling requires explicit design and testing
Emergency numbers must not be treated as ordinary long-distance or international patterns. Exact local emergency-service rules, emergency location identification, carrier configuration, failover behavior, and regulatory obligations must be validated with qualified personnel. A wildcard or a translation introduced for convenience can affect which digits leave the system or which location the emergency service receives.
Use an authorized emergency calling test procedure and coordinate with service providers where required. Do not place test emergency calls casually. Build representative mock routes and verify that emergency patterns have the intended priority and visibility before the controlled production test is approved.
A well-designed dial plan also considers what happens when a preferred trunk fails. Route groups and lists may provide alternatives, but emergency reachability is an end-to-end service requirement, not merely a dial-plan pattern that matches correctly.
Diagnose wrong routes by tracing each decision
Start with the dialed string and the originating device. Determine which calling search space and partition apply, then inspect the matching route or translation pattern. Verify the selected route list or gateway, associated digit manipulation, and final called number. If signaling reaches the far end, compare the received digits and response code with what CUCM was expected to send.
Use the system’s Dialed Number Analyzer or equivalent diagnostic tools where available, followed by traces and call detail records when necessary. A test tool can reveal potential matches, while signaling traces show the actual live behavior. Troubleshooting should separate no-match failures from authorization, endpoint reachability, codec negotiation, and carrier rejections.
Keep a change log for each adjustment. Record which dial strings were expected to change, which should remain unaffected, and which tests passed after installation. For complex environments, a representative automated test set can catch regression when routing partitions, site codes, or PSTN providers change.
Maintain a dial plan that other engineers can understand
Readable route-pattern descriptions, a numbering inventory, a documented translation sequence, and a concise test matrix are more valuable than clever wildcard expressions. Avoid overlapping patterns that depend on obscure tie-breaking assumptions when the numbering plan can be expressed more explicitly. Plan reviews should include the people responsible for telecom operations, security, emergency services, and network availability.
Cisco CUCM’s X, !, ?, +, brackets, and numbering-plan syntax each have defined matching semantics. Use those semantics to capture a legitimate business requirement, then test the result through the real routing and authorization context. The objective is predictable call handling with controlled access and a verifiable recovery path—not simply reducing the number of entries in the configuration database.