# Troubleshooting calls that wait several seconds before routing in Unified CM

Canonical: https://warmtransfer.net/knowledge/cucm-interdigit-delay-troubleshooting

Last verified: 2026-10-02

In Unified CM, when a dialed number matches a pattern but a longer or overlapping pattern could still match, the T302 interdigit timer must expire before the call routes[^20][^25]. The documented ways to avoid that wait include Urgent Priority on directory numbers and patterns, Do Not Wait For Interdigit Timeout On Subsequent Hops, #-terminated patterns, SIP dial rules, and Enbloc Dialing on 8800 phones[^5][^44][^43][^15][^35][^11].

## How the interdigit wait happens

In Unified CM the T302 service parameter, in the Clusterwide Parameters (Device - General) section, sets the interdigit timer value[^41].

Sources disagree on the default value:[^40][^39]

- This is disputed: Cisco documents the default T302 as 15 seconds (15,000 ms)[^40].
- This is disputed: other Cisco documents say that, by default, a call matching a variable-length 9.@ pattern waits 10 seconds before it is placed, and describe this as the default interdigit timeout[^39].

Cisco's Preferred Architecture states that its default T302 of 15,000 ms is typically too long[^26].

When a user dials a fully qualified directory number and an overlapping pattern exists, Unified CM starts the T302 timer and waits for more digits before it routes the call[^20].

When digits are dialed one by one and a longer, possibly variable-length match still exists, Unified CM cannot yet decide which pattern applies, so T302 must expire before it selects the best route[^25].

Two route pattern characters matter here:[^2][^28]

- The `!` wildcard matches 1 or more digits 0-9, which makes the pattern variable length[^2].
- The `#` character generally marks the end of the dialing sequence[^28].

Extensions of different lengths that overlap, such as 1000 and 10000, force users who dial 1000 to wait for the interdigit timeout[^19].

## How the phone delivers digits

Type-B SIP phones without dial rules use KPML to report each key press to Unified CM, so digit analysis proceeds digit by digit, as it does with SCCP phones[^37].

Older Type-A SIP phones without dial rules collect digits en bloc and send them only when the user presses Dial or #, or after a phone-side interdigit timeout (10 seconds by default)[^36].

KPML sends digits to Unified CM digit by digit, whereas SIP dial rules collect a pattern of digits locally on the phone before sending them to Unified CM[^16]. SIP dial rules give Cisco SIP phones a local dial plan, so users do not have to press a key or wait for a timer before the call is processed[^35]. The Release 15 dial rules chapter lists the 7911, 7941, 7961, 7970 and 7971 as the phones that use the 7940_7960_OTHER SIP dial rule pattern format[^4].

On Cisco IP Phone 8800 firmware 12.1(1)SR1 and later, the Enbloc Dialing parameter in the phone's Product Specific Configuration Layout overrides the T.302 timer and sends the whole dialed string to Unified CM once dialing is complete[^11].

Cisco lists these as the 8800 scenarios that Enbloc Dialing speeds up[^13]:

- On-hook dialing and redial[^13]
- Speed dial and speed dial BLF[^13]
- Voicemail[^13]
- Calls from Recents and Directory[^13]

Cisco states that, before Enbloc Dialing, 8800 users could see a delay of up to 15 seconds when placing such calls[^12].

Enbloc Dialing on the 8800 is not supported with Forced Authorization Codes or Client Matter Codes, so sites that use FAC or CMC cannot use it[^10].

## Diagnosing it

### Test calls

Cisco's troubleshooting guide tells testers to wait at least 10 seconds after the last digit, because the interdigit timer may need to expire[^48]. We infer that 10 seconds is shorter than a T302 left at the 15,000 ms default, so on such a cluster wait longer before calling a test a failure[^26].

### SDL traces

Unified CM SDL traces record digit analysis results such as `Digit analysis: potentialMatches=PotentialMatchesExist` and `potentialMatches=NoPotentialMatchesExist`[^47]. Cisco describes PotentialMatchesExist as the digit analysis result for the digits dialed so far, until the exact match is found and the call is routed[^46].

A match is traced in the form `Digit analysis: match(fqcn=..., cn=..., pss=..., dd=...)`, where `pss` shows the partition search space and `dd` shows the dialed digits[^45].

We infer that a post-dial delay that consistently matches the configured T302 value, with PotentialMatchesExist logged after the final digit, points to an overlapping or variable-length pattern in the caller's partitions rather than to trunk or far-end delay[^3].

### Dialed Number Analyzer

Dialed Number Analyzer is enabled by activating the Cisco Dialed Number Analyzer and Cisco Dialed Number Analyzer Server services in Unified CM Serviceability > Tools > Service Activation[^7]. Once activated, Dialed Number Analyzer is reached at https://<cucm-host>/dna[^9].

Dialed Number Analyzer simulates routing from the dialed digits, the calling party number, and a calling search space or device, and shows the matched translation and route patterns and the destination[^8].

Cisco's urgent-priority-on-DN tech note states that no verification procedure and no specific troubleshooting information are available for that configuration[^18].

## Removing the wait

### Urgent Priority on directory numbers

An Urgent Priority check box is available on the Directory Number Configuration page from Unified CM 10.0[^6]. Before Unified CM 10.0, a DN could not be marked urgent, so a user dialing a directory number had to wait out T302 before the call routed whenever an overlapping pattern was configured[^29].

With Urgent Priority enabled on a directory number, Unified CM routes a call to that fully qualified DN at once without starting T302, even if an overlapping pattern exists[^5]. Cisco gives these examples:[^32][^33]

- A translation pattern 666X that transforms to urgent DN 7770 routes without interdigit wait, even though an overlapping route pattern 777XX exists[^32].
- Urgent DN 919555888899, with an overlapping translation pattern 91XXXXXXXXXX that is also marked urgent, routes without interdigit wait[^33].

When the Speed Dial Await Further Digits parameter is true, Unified CM still routes a speed-dialed number immediately if the matched pattern is urgent, and otherwise waits for the interdigit timeout[^38].

### Urgent Priority on translation and route patterns

The field help for the translation pattern Urgent Priority field says that with overlapping patterns Unified CM does not route until the interdigit timer expires, and that selecting the box interrupts interdigit timing when the call must route immediately[^44].

The route pattern Urgent Priority field has long been documented as interrupting interdigit timing when overlapping route patterns would otherwise hold the call until the interdigit timer expires[^31].

Urgent Priority ends the T302 wait only when the urgent pattern is already the best match; it does not give the pattern priority over other patterns, and closest-match logic still applies[^50]. Cisco's examples[^49]:

- With 1XX urgent and 12! not urgent, dialing 123 does not route immediately, because 12! is the closer match[^49].
- With 12[2-5] urgent and 12! regular, dialing 123 routes immediately[^49].

Field reports suggest that marking a `!` pattern urgent can make Unified CM route after the first matching digit during digit-by-digit dialing, cutting off the rest of the number[^1].

### Do Not Wait For Interdigit Timeout On Subsequent Hops

Do Not Wait For Interdigit Timeout On Subsequent Hops takes effect when it is selected together with Urgent Priority on the translation pattern and the pattern matches the dialed digits, or is the only matching pattern[^42].

When it is in effect, Unified CM does not start the interdigit timer on subsequent matches, even if those patterns are variable length or overlap[^43].

Cisco's Preferred Architecture sets this option on fixed-length dialing normalization translation patterns so the call routes without interdigit timeout even if the secondary lookup hits a variable-length route pattern[^21].

In the field, practitioners report that interdigit timeout is evaluated at each hop of a translation-to-route-pattern chain, so urgency on the first hop does not by itself stop a wait at the route pattern[^27].

### Dial plan design

Cisco's Preferred Architecture dial plan uses distinct access codes, such as 9 for PSTN, so that no dialing habit overlaps any other enterprise dialing habit[^22]. In that architecture, all dialing normalization translation patterns are provisioned as urgent patterns with Use Originator's Calling Search Space set[^23].

Cisco's variable-length dial plan tech note recommends granular explicit route patterns over broad wildcards, so that calls route as soon as the required digits are dialed[^14]. Cisco's example dial plan pairs a variable-length international pattern with a #-terminated variant (0.0011!#), so users can end dialing with # instead of waiting[^15].

For a 10-second wait on 7-digit calls matching 9.@, Cisco advises applying a route filter with LOCAL-AREA-CODE DOES-NOT-EXIST and END-OF-DIALING DOES-NOT-EXIST[^30].

### Changing T302

Cisco notes that the interdigit timer can be shortened, but this can cause problems for users who pause midway through dialing[^34].

WarmTransfer's reading of the sources is that shortening the interdigit timer shortens every overlap-induced wait across the cluster, but unlike urgent priority, Do Not Wait, # termination or en bloc dialing it does not remove the wait, and it risks routing calls for users who pause mid-number[^17].

## See also

- [Unified CM translation and transformation patterns](https://warmtransfer.net/knowledge/cucm-translation-patterns)
- [Unified CM route patterns and partitions configuration](https://warmtransfer.net/knowledge/cucm-config-route-patterns-and-partitions)
- [Unified CM dial plan partitions and calling search spaces](https://warmtransfer.net/knowledge/cucm-dial-plan)
- [Enterprise dial plan design and normalization](https://warmtransfer.net/knowledge/dial-plan-design)
- [CUCM CallManager SDL trace files](https://warmtransfer.net/knowledge/cucm-sdl-trace-files)

## Applicability

Applies to: Cisco Unified Communications Manager and Cisco IP Phone 8800 Series. Deployments: on-premises. Sources checked 2026-10-02. Urgent Priority on directory numbers is available from Unified CM 10.0, and earlier releases could not mark a DN urgent[^6][^29]. Enbloc Dialing applies to Cisco IP Phone 8800 firmware 12.1(1)SR1 and later[^11]. The SIP dial rule phone list comes from the Release 15 dial rules chapter[^4].

## What remains uncertain

Sources disagree on the default interdigit timeout: one Cisco document gives 15 seconds (15,000 ms), and another describes 10 seconds for a 9.@ match[^40][^39].

Field reports suggest these behaviours, which a reader should verify before relying on them[^1][^27]:

- Field reports suggest urgent `!` patterns can cut off dialing after the first digit[^1].
- In the field, interdigit timeout is reported to be evaluated at each hop of a translation-to-route-pattern chain[^27].

Cisco's urgent-priority-on-DN tech note provides no verification procedure or specific troubleshooting information[^18].

Whether current releases use the same wording for the route pattern Urgent Priority field help is not covered by the sources below. How Enbloc Dialing behaves on phone families other than the 8800 is also not covered by the sources below.

## Sources

[^1]: Practitioners report that marking a ! pattern urgent can make Unified CM route after the first matching digit during digit-by-digit dialing, cutting off the rest of the number (field report). Source: [UC Corner: Revisit "Urgent Priority"](http://htluo.blogspot.com/2020/10/revisit-urgent-priority.html), Post body, discussion of urgent priority on ! patterns. Checked 2026-10-02.
[^2]: In Unified CM route patterns the ! wildcard matches one or more digits 0-9, making the pattern variable length. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Wildcards and Special Characters in Route Patterns. Checked 2026-10-02.
[^3]: A post-dial delay that consistently matches the configured T302 value, with PotentialMatchesExist logged after the final digit, points to an overlapping or variable-length pattern in the caller's partitions rather than to trunk or far-end delay (inferred). Source: [Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/trouble/12_5_1/cucm_b_troubleshooting-guide-1251/cucm_b_troubleshooting-guide-1251_chapter_0101.html), Dial Plan Issues > Problem When Dialing a Number; combined with PA Service Parameter Settings. Checked 2026-10-02.
[^4]: The Release 15 dial rules chapter lists the 7911, 7941, 7961, 7970 and 7971 as the phones using the 7940_7960_OTHER SIP dial rule pattern format. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Dial Rules](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010111.html), Configure SIP Dial Rules > Pattern Formats. Checked 2026-10-02.
[^5]: With Urgent Priority enabled on a directory number, Unified CM routes a call to that fully qualified DN at once without starting T302, even if an overlapping pattern exists. Source: [Urgent Priority Configuration on Directory Number](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200477-Urgent-Priority-Configuration-on-Directo.html), User Experience. Checked 2026-10-02.
[^6]: An Urgent Priority check box on the Directory Number Configuration page is available from Unified CM 10.0. Source: [Urgent Priority Configuration on Directory Number](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200477-Urgent-Priority-Configuration-on-Directo.html), Components Used; Configure. Checked 2026-10-02.
[^7]: Dialed Number Analyzer is enabled by activating the Cisco Dialed Number Analyzer and Cisco Dialed Number Analyzer Server services in Unified CM Serviceability > Tools > Service Activation. Source: [Troubleshoot Call Routing Issue via CUCM Dialed Number Analyzer](https://www.cisco.com/c/en/us/support/docs/troubleshooting/222342-troubleshoot-call-routing-issue-via-cucm.html), Service activation section. Checked 2026-10-02.
[^8]: Dialed Number Analyzer simulates routing from dialed digits, calling party number and a calling search space or device, and shows the matched translation and route patterns and the destination. Source: [Troubleshoot Call Routing Issue via CUCM Dialed Number Analyzer](https://www.cisco.com/c/en/us/support/docs/troubleshooting/222342-troubleshoot-call-routing-issue-via-cucm.html), Analysis inputs and results sections. Checked 2026-10-02.
[^9]: Once activated, Dialed Number Analyzer is reached at https://<cucm-host>/dna. Source: [Troubleshoot Call Routing Issue via CUCM Dialed Number Analyzer](https://www.cisco.com/c/en/us/support/docs/troubleshooting/222342-troubleshoot-call-routing-issue-via-cucm.html), Access section. Checked 2026-10-02.
[^10]: Enbloc Dialing on the 8800 is not supported with Forced Authorization Codes or Client Matter Codes; sites using FAC or CMC cannot use it. Source: [Cisco IP Phone 8800 Series Release Notes for Firmware Release 12.1(1)SR1](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8800-series/firmware/12-1-1-SR1/releasenotes/p881_b_8800-series-release-notes-1211SR1.html), New and Changed Features > Enbloc Dialing. Checked 2026-10-02.
[^11]: On Cisco IP Phone 8800 firmware 12.1(1)SR1 and later, the Enbloc Dialing parameter in the phone's Product Specific Configuration Layout overrides the T.302 timer and sends the whole dialed string to Unified CM once dialing is complete. Source: [Cisco IP Phone 8800 Series Release Notes for Firmware Release 12.1(1)SR1](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8800-series/firmware/12-1-1-SR1/releasenotes/p881_b_8800-series-release-notes-1211SR1.html), New and Changed Features > Enbloc Dialing. Checked 2026-10-02.
[^12]: Cisco states that before Enbloc Dialing, 8800 users could see a delay of up to 15 seconds when placing such calls. Source: [Cisco IP Phone 8800 Series Release Notes for Firmware Release 12.1(1)SR1](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8800-series/firmware/12-1-1-SR1/releasenotes/p881_b_8800-series-release-notes-1211SR1.html), New and Changed Features > Enbloc Dialing. Checked 2026-10-02.
[^13]: Cisco lists on-hook dialing and redial, speed dial and speed dial BLF, voicemail, and calls from Recents and Directory as the 8800 scenarios Enbloc Dialing speeds up. Source: [Cisco IP Phone 8800 Series Release Notes for Firmware Release 12.1(1)SR1](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cuipph/8800-series/firmware/12-1-1-SR1/releasenotes/p881_b_8800-series-release-notes-1211SR1.html), New and Changed Features > Enbloc Dialing. Checked 2026-10-02.
[^14]: Cisco's variable-length dial plan tech note recommends granular explicit route patterns over broad wildcards so calls route as soon as the required digits are dialed. Source: [Supporting Variable Length Dial Plans for Cisco CallManager Route Patterns - an Exercise in Designing a Route Pattern that Covers a National Dial Plan](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/210536-Supporting-Variable-Length-Dial-Plans-fo.html), Background Information; dial plan table. Checked 2026-10-02.
[^15]: Cisco's example dial plan pairs a variable-length international pattern with a #-terminated variant (0.0011!#) so users can end dialing with # instead of waiting. Source: [Supporting Variable Length Dial Plans for Cisco CallManager Route Patterns - an Exercise in Designing a Route Pattern that Covers a National Dial Plan](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/210536-Supporting-Variable-Length-Dial-Plans-fo.html), Dial plan table, row 0.0011!#. Checked 2026-10-02.
[^16]: KPML sends digits to Unified CM digit by digit, whereas SIP dial rules collect a pattern of digits locally on the phone before sending to Unified CM. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Dial Rules](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010111.html), Dial Rules Interactions and Restrictions > SIP Dial Rules Interactions. Checked 2026-10-02.
[^17]: Lowering T302 shortens every overlap-induced wait across the cluster, but unlike urgent priority, Do Not Wait, # termination or en bloc dialing it does not remove the wait, and it risks routing calls for users who pause mid-number (inferred). Source: [Preferred Architecture for Cisco Collaboration 12.x Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/12x/120/collbcvd/control.html), Service Parameter Settings; combined with tech note 210536 Background Information. Checked 2026-10-02.
[^18]: Cisco's urgent-priority-on-DN tech note states that no verification procedure and no specific troubleshooting information are available for the configuration. Source: [Urgent Priority Configuration on Directory Number](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200477-Urgent-Priority-Configuration-on-Directo.html), Verify; Troubleshoot. Checked 2026-10-02.
[^19]: Extensions of different lengths that overlap, such as 1000 and 10000, force users dialing 1000 to wait for the interdigit timeout. Source: [Cisco Unified Communications SRND Based on Cisco Unified Communications Manager 5.x - Dial Plan](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/5x/50dialpl.html), Dial Plan chapter, extension/overlap guidance. Checked 2026-10-02.
[^20]: When a fully qualified directory number is dialed and an overlapping pattern exists, Unified CM starts the T302 timer and waits for further digits before routing. Source: [Urgent Priority Configuration on Directory Number](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200477-Urgent-Priority-Configuration-on-Directo.html), Background Information. Checked 2026-10-02.
[^21]: Cisco's Preferred Architecture sets Do Not Wait For Interdigit Timeout On Subsequent Hops on fixed-length dialing normalization translation patterns so the call routes without interdigit timeout even if the secondary lookup hits a variable-length route pattern. Source: [Preferred Architecture for Cisco Collaboration 12.x Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/12x/120/collbcvd/control.html), Dialing Normalization Translation Patterns. Checked 2026-10-02.
[^22]: Cisco's Preferred Architecture dial plan uses distinct access codes (such as 9 for PSTN) so that each dialing habit does not overlap any other enterprise dialing habit. Source: [Preferred Architecture for Cisco Collaboration 12.x Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/12x/120/collbcvd/control.html), Dialing Habits. Checked 2026-10-02.
[^23]: In Cisco's Preferred Architecture, all dialing normalization translation patterns are provisioned as urgent patterns with Use Originator's Calling Search Space set. Source: [Preferred Architecture for Cisco Collaboration 12.x Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/12x/120/collbcvd/control.html), Dialing Normalization Translation Patterns. Checked 2026-10-02.
[^24]: Cisco's 12.x Preferred Architecture recommends setting T302 to 5000 ms. Source: [Preferred Architecture for Cisco Collaboration 12.x Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/12x/120/collbcvd/control.html), Service Parameter Settings (T302 Timer recommended value). Checked 2026-10-02.
[^25]: When digits are dialed one by one and Unified CM cannot yet decide which pattern applies because a longer (possibly variable-length) match exists, T302 must expire before it selects the best route. Source: [Preferred Architecture for Cisco Collaboration 12.x Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/12x/120/collbcvd/control.html), Service Parameter Settings (T302 Timer). Checked 2026-10-02.
[^26]: Cisco's Preferred Architecture states the default T302 of 15,000 ms is typically too long. Source: [Preferred Architecture for Cisco Collaboration 12.x Enterprise On-Premises Deployments, CVD - Call Control](https://www.cisco.com/c/en/us/td/docs/solutions/CVD/Collaboration/enterprise/12x/120/collbcvd/control.html), Service Parameter Settings (T302 Timer). Checked 2026-10-02.
[^27]: Practitioners report that interdigit timeout is evaluated at each hop of a translation-to-route-pattern chain, so urgency on the first hop does not by itself stop a wait at the route pattern (field report). Source: [UC Corner: Revisit "Urgent Priority"](http://htluo.blogspot.com/2020/10/revisit-urgent-priority.html), Post body, multi-tier dial plan discussion. Checked 2026-10-02.
[^28]: In Unified CM route patterns the # character generally identifies the end of the dialing sequence. Source: [System Configuration Guide for Cisco Unified Communications Manager Release 15 and SUs - Configure Call Routing](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010010.html), Wildcards and Special Characters in Route Patterns. Checked 2026-10-02.
[^29]: Before Unified CM 10.0, a user dialing a directory number had to wait out T302 before the call routed if an overlapping pattern was configured, because a DN could not be marked urgent. Source: [Urgent Priority Configuration on Directory Number](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200477-Urgent-Priority-Configuration-on-Directo.html), User Experience. Checked 2026-10-02.
[^30]: For a 10-second wait on 7-digit calls matching 9.@, Cisco advises applying a route filter with LOCAL-AREA-CODE DOES-NOT-EXIST and END-OF-DIALING DOES-NOT-EXIST. Source: [Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/trouble/12_5_1/cucm_b_troubleshooting-guide-1251/cucm_b_troubleshooting-guide-1251_chapter_0101.html), Dial Plan Issues > Problem When Dialing a Number. Checked 2026-10-02.
[^31]: The route pattern Urgent Priority field has long been documented as interrupting interdigit timing when overlapping route patterns would otherwise hold the call until the interdigit timer expires. Source: [Cisco CallManager Administration Guide, Release 4.1(2) - Route Pattern Configuration](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/admin/4_1_2/ccmcfg/b03rtpat.html), Table 22-1 Route Pattern Configuration Settings, Urgent Priority. Checked 2026-10-02.
[^32]: Cisco's example: a translation pattern 666X that transforms to urgent DN 7770 routes without interdigit wait even though an overlapping route pattern 777XX exists. Source: [Urgent Priority Configuration on Directory Number](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200477-Urgent-Priority-Configuration-on-Directo.html), Call Scenarios > Scenario 1. Checked 2026-10-02.
[^33]: Cisco's example: urgent DN 919555888899 with an overlapping translation pattern 91XXXXXXXXXX that is also marked urgent routes without interdigit wait. Source: [Urgent Priority Configuration on Directory Number](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200477-Urgent-Priority-Configuration-on-Directo.html), Call Scenarios > Scenario 2. Checked 2026-10-02.
[^34]: Cisco notes the interdigit timer can be shortened, but this can cause problems for users who pause midway through dialing. Source: [Supporting Variable Length Dial Plans for Cisco CallManager Route Patterns - an Exercise in Designing a Route Pattern that Covers a National Dial Plan](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/210536-Supporting-Variable-Length-Dial-Plans-fo.html), Background Information. Checked 2026-10-02.
[^35]: SIP dial rules give Cisco SIP phones a local dial plan so users do not have to press a key or wait for a timer before the call is processed. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Dial Rules](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/systemConfig/cucm_b_system-configuration-guide-15/cucm_b_system-configuration-guide-14_chapter_010111.html), Configure SIP Dial Rules. Checked 2026-10-02.
[^36]: Older Type-A SIP phones without dial rules collect digits en bloc and send them only when the user presses Dial or #, or after a phone-side interdigit timeout (10 seconds by default). Source: [Cisco Unified Communications SRND Based on Cisco Unified Communications Manager 5.x - Dial Plan](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/5x/50dialpl.html), Dial Plan chapter, SIP phone dialing (Type-A phones). Checked 2026-10-02.
[^37]: Type-B SIP phones without dial rules use KPML to report each key press to Unified CM, so digit analysis proceeds digit by digit as with SCCP phones. Source: [Cisco Unified Communications SRND Based on Cisco Unified Communications Manager 5.x - Dial Plan](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/5x/50dialpl.html), Dial Plan chapter, SIP phone dialing (Type-B phones). Checked 2026-10-02.
[^38]: When the Speed Dial Await Further Digits parameter is true, Unified CM still routes a speed-dialed number immediately if the matched pattern is urgent, and otherwise waits for the interdigit timeout. Source: [Urgent Priority Configuration on Directory Number](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200477-Urgent-Priority-Configuration-on-Directo.html), Interaction with Speed Dial Parameter (SP). Checked 2026-10-02.
[^39]: Other Cisco documents state that, by default, a call matching a variable-length 9.@ pattern waits 10 seconds before being placed, describing this as the default interdigit timeout (disputed). Source: [Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/trouble/12_5_1/cucm_b_troubleshooting-guide-1251/cucm_b_troubleshooting-guide-1251_chapter_0101.html), Dial Plan Issues > Problem When Dialing a Number. Checked 2026-10-02.
[^40]: Cisco documents the default T302 interdigit timer as 15 seconds (15,000 ms) (disputed). Source: [Urgent Priority Configuration on Directory Number](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200477-Urgent-Priority-Configuration-on-Directo.html), Background Information (Default Value = 15 seconds). Checked 2026-10-02.
[^41]: In Unified CM the interdigit timer value is set by the T302 service parameter in the Clusterwide Parameters (Device - General) section. Source: [Urgent Priority Configuration on Directory Number](https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/200477-Urgent-Priority-Configuration-on-Directo.html), Background Information. Checked 2026-10-02.
[^42]: Do Not Wait For Interdigit Timeout On Subsequent Hops takes effect when selected together with Urgent Priority on the translation pattern and the pattern matches the dialed digits (or is the only matching pattern). Source: [How to Configure Cisco Unified Communications Manager Translation Patterns](https://documentation.voss-solutions.com/release_19.3.4/html/src/user/e_configure-cucm-translation-patterns.html), Field: Do Not Wait for Interdigit Timeout on Subsequent Hops. Checked 2026-10-02.
[^43]: With Do Not Wait For Interdigit Timeout On Subsequent Hops in effect, Unified CM does not start the interdigit timer on subsequent matches even if those patterns are variable length or overlap. Source: [How to Configure Cisco Unified Communications Manager Translation Patterns](https://documentation.voss-solutions.com/release_19.3.4/html/src/user/e_configure-cucm-translation-patterns.html), Field: Do Not Wait for Interdigit Timeout on Subsequent Hops. Checked 2026-10-02.
[^44]: The translation pattern Urgent Priority field help says that with overlapping patterns Unified CM does not route until the interdigit timer expires, and selecting the box interrupts interdigit timing when the call must route immediately. Source: [How to Configure Cisco Unified Communications Manager Translation Patterns](https://documentation.voss-solutions.com/release_19.3.4/html/src/user/e_configure-cucm-translation-patterns.html), Field: Urgent Priority. Checked 2026-10-02.
[^45]: A Unified CM digit analysis match is traced in the form 'Digit analysis: match(fqcn=..., cn=..., pss=..., dd=...)', where pss shows the partition search space and dd the dialed digits. Source: [Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/trouble/12_5_1/cucm_b_troubleshooting-guide-1251/cucm_b_troubleshooting-guide-1251_chapter_0101.html), Dial Plan Issues > Problem When Dialing a Number (trace example). Checked 2026-10-02.
[^46]: Cisco describes PotentialMatchesExist as the digit analysis result for the digits dialed so far, until the exact match is found and the call is routed. Source: [Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/trouble/12_5_1/cucm_b_troubleshooting-guide-1251/cucm_b_troubleshooting-guide-1251_chapter_0101.html), Dial Plan Issues > Problem When Dialing a Number. Checked 2026-10-02.
[^47]: Unified CM SDL traces record digit analysis results such as 'Digit analysis: potentialMatches=PotentialMatchesExist' and 'potentialMatches=NoPotentialMatchesExist'. Source: [Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/trouble/12_5_1/cucm_b_troubleshooting-guide-1251/cucm_b_troubleshooting-guide-1251_chapter_0101.html), Dial Plan Issues > Problem When Dialing a Number (trace example). Checked 2026-10-02.
[^48]: Cisco's troubleshooting guide tells testers to wait at least 10 seconds after the last digit because the interdigit timer may need to expire. Source: [Troubleshooting Guide for Cisco Unified Communications Manager, Release 12.5(1) - Dial Plans and Routing Issues](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/trouble/12_5_1/cucm_b_troubleshooting-guide-1251/cucm_b_troubleshooting-guide-1251_chapter_0101.html), Dial Plan Issues > Problem When Dialing a Number. Checked 2026-10-02.
[^49]: Cisco's example: with 1XX urgent and 12! not urgent, dialing 123 does not route immediately because 12! is the closer match; with 12[2-5] urgent and 12! regular, dialing 123 routes immediately. Source: [Cisco Unified Communications SRND Based on Cisco Unified Communications Manager 5.x - Dial Plan](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/5x/50dialpl.html), Dial Plan chapter, urgent priority example. Checked 2026-10-02.
[^50]: Urgent Priority only ends the T302 wait when the urgent pattern is already the best match; it does not give the pattern priority over other patterns, and closest-match logic still applies. Source: [Cisco Unified Communications SRND Based on Cisco Unified Communications Manager 5.x - Dial Plan](https://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/5x/50dialpl.html), Dial Plan chapter, urgent priority discussion. Checked 2026-10-02.