# Unified CM route patterns and partitions configuration Systems: Cisco Unified Communications Manager For Unified CM administrators configuring route patterns, calling search spaces, and partitions on Release 15 or 14. Canonical: https://warmtransfer.net/guides/cucm-config-route-patterns-and-partitions Last verified: 2026-09-24 Unified CM searches for a route pattern that matches an external dial string and uses it to send the call to a gateway or route list[^42]. A calling search space is a prioritized list of partitions that determines which call destinations a caller can reach[^6]. ## Before you start Cisco lists completing the partition configuration task flow as a prerequisite for call routing configuration[^30]. In Unified CM a partition is a logical group that can hold route patterns, directory numbers, translation patterns, transformation patterns, URIs and hunt pilots[^32]. ## What changes by situation - Where should your route patterns send off-net calls? Through a route list and route groups (Cisco's recommendation); Straight to one gateway or trunk. - How do your users dial external numbers? With an access code such as 9, compulsory stripped before the call leaves; With an access code that a translation pattern rewrites to +E.164, and route patterns match the + form. - Where do you assign calling search spaces? On the phone (device) only; On both the line (directory number) and the phone. - Should any class of service change with the time of day? No, permissions are the same around the clock; Yes, some partitions should only be reachable during set hours. ## Step 1: Plan class-of-service tiers and names ### Do Decide the tiers you need; Cisco documents building classes of service from partitions and CSSs, with an example ladder of Base_CSS (emergency and internal), LocalPSTN_CSS, NationalPSTN_CSS and InternationalPSTN_CSS, each adding call types to the previous one[^3]. For each tier, plan one partition for the patterns it unlocks and one calling search space that lists the partitions that tier may reach[^3][^6]. Name partitions using alphanumeric characters, spaces, hyphens and underscores[^21]. Keep partition names short: the list of partitions in a calling search space is limited to a maximum of 1024 characters[^4]. Cisco's table shows that the maximum number of partitions in a CSS falls as name length increases: 340 partitions for 2-character names, 172 for 5-character names, 92 for 10-character names, and 64 for 15-character names[^22]. A calling search space name can be up to 50 alphanumeric characters[^9]. ### Verify Suggested check: write down the planned partition names for each tier and sum their character lengths to ensure the total remains within the calling search space limit. ### Rollback Suggested rollback: no changes have been applied to the cluster yet. ## Step 2: Create the partitions ### Do In Unified CM Administration, navigate to Call Routing > Class of Control > Partition and click Add New[^33]. Enter the partitions, placing each on its own line to create multiple entries at once[^33]. Put every dial plan entry into a named partition; any calling device can reach an entry left in the <None> partition, and Cisco recommends not leaving dial plan entries there[^24]. Digit analysis treats an unassigned item as belonging to the Null default partition, which all users can reach and which the system always searches last[^25]. ### Verify Suggested check: return to Call Routing > Class of Control > Partition and confirm each created partition appears in the list. ### Rollback Before a partition can be deleted, the items that use it must be moved to a different partition or deleted[^31]. Deleted partitions cannot be retrieved[^10]. ## Step 3: Apply time schedules to partitions **No, permissions are the same around the clock** ### Do Leave the Time Schedule drop-down menu unset for each partition[^34]. ### Verify Suggested check: open each partition at Call Routing > Class of Control > Partition and verify that the Time Schedule field remains unassigned. ### Rollback Suggested rollback: no schedule settings were applied. **Yes, some partitions should only be reachable during set hours** ### Do Configure time-of-day routing by creating a time period, then a time schedule[^47]. Open Call Routing > Class of Control > Partition, select the schedule in the partition's Time Schedule drop-down, and save[^47]. Select either Originating Device or a Specific Time Zone to determine which clock the schedule evaluates against[^34]. ### Verify In Dialed Number Analyzer, test a call with a chosen calling search space and time to simulate a caller's permissions during and outside active schedule windows[^13]. ### Rollback Open Call Routing > Class of Control > Partition, change the Time Schedule drop-down to None, and save the partition[^47]. ## Step 4: Create the calling search spaces in priority order ### Do Navigate to Call Routing > Class of Control > Calling Search Space and choose Add New[^7]. For each tier, move partitions from Available Partitions to Selected Partitions and set their sequence using the arrow buttons[^7]. If two patterns match the dialed digits equally well, digit analysis chooses the one in the partition listed first in the calling search space[^46]. WarmTransfer's reading of the sources is that partition order in a CSS does not make a less specific pattern in an earlier partition win over a more specific pattern in a later one, because order decides only between equally good matches[^27]. ### Verify Suggested check: re-open each calling search space under Call Routing > Class of Control > Calling Search Space and verify that the Selected Partitions list preserves the intended tier hierarchy and partition sequence. ### Rollback Suggested rollback: remove the calling search space assignments from any associated lines, devices, or translation patterns, then delete the calling search space from Call Routing > Class of Control > Calling Search Space. ## Step 5: Build the PSTN destination **Through a route list and route groups (Cisco's recommendation)** ### Do Follow Cisco's call routing task flow order by creating route groups and route lists before route patterns[^45]. Navigate to Call Routing > Route/Hunt > Route Group to configure a route group, which sets the order in which the system selects gateways for outgoing calls[^36]. Go to Call Routing > Route/Hunt > Route List, add the route group with Add Route Group, save the list, and select Apply Config[^38]. A route list can contain only route groups and local route groups, not individual gateways or trunks[^37]. If local gateway egress is required, configure local route group names at Call Routing > Route/Hunt > Local Route Group Names and map the Standard Local Route Group to a route group under the device pool settings at System > Device Pool[^20][^59]. ### Verify Suggested check: open Call Routing > Route/Hunt > Route List, verify that the route group appears in the member list, and confirm that Apply Config has been applied. ### Rollback Suggested rollback: remove the route group from the route list and delete the route list at Call Routing > Route/Hunt > Route List, then delete the route group at Call Routing > Route/Hunt > Route Group. **Straight to one gateway or trunk** ### Do Skip route group and route list creation; in the next step, select the destination gateway or trunk directly in the Gateway/Route List drop-down on the route pattern[^40]. Although a route pattern can point directly to a gateway, Cisco recommends configuring route lists and route groups for flexibility and scalability[^39]. Note that a gateway or trunk that a route pattern points to directly is not available for association with a route group[^11]. ### Verify Suggested check: confirm that the destination trunk or gateway is registered and active in Unified CM Administration. ### Rollback Suggested rollback: no route lists or route groups were created in this step. ## Step 6: Create the outbound route patterns **With an access code such as 9, compulsory stripped before the call leaves** ### Do Navigate to Call Routing > Route/Hunt > Route Pattern to create a pattern for each tier, selecting the destination in the Gateway/Route List drop-down[^40]. Assign each route pattern to the partition of the tier it unlocks[^41]. In route patterns, the dot (.) separates an access code from the rest of the dialed number[^52], X matches any single digit 0 through 9[^55], square brackets enclose a range of values with a hyphen denoting a range[^54],! matches one or more digits 0 through 9[^51], and @ matches all National Numbering Plan numbers (with only one @ allowed per pattern)[^50]. For a pattern such as 9.@, set the Discard Digits option to PreDot to strip the external access code so the PSTN can route the call[^29]. Classifying a route pattern as Off-Net lets users hear a secondary dial tone that indicates the call is leaving the organization[^26]. ### Verify Test the dial string in Dialed Number Analyzer using the target calling search space to verify that the matched pattern and outgoing trunk or gateway appear in sequence[^13][^15]. ### Rollback Suggested rollback: locate the route pattern at Call Routing > Route/Hunt > Route Pattern and delete it. **With an access code that a translation pattern rewrites to +E.164, and route patterns match the + form** ### Do Configure translation patterns at Call Routing > Translation Pattern to rewrite dialed strings into +E.164[^56][^15]. Assign each translation pattern to a partition and configure its Calling Search Space field to reach the +E.164 route patterns[^56]. Unified CM applies the translation and then routes the call again using the translation pattern's calling search space[^57]. Each translation pattern's combination of partition, route filter and numbering plan must be unique[^58]. Next, create the outbound route patterns at Call Routing > Route/Hunt > Route Pattern, using \+ as the international escape character to match a leading plus sign[^40][^53]. Assign these route patterns to a partition included in the translation pattern's calling search space, and choose the destination in the Gateway/Route List drop-down[^40][^41][^57]. ### Verify In Dialed Number Analyzer, verify that test output displays the translation pattern match first, followed in sequence by the rewritten +E.164 route pattern and trunk[^15]. ### Rollback Suggested rollback: navigate to Call Routing > Route/Hunt > Route Pattern to delete the route patterns, then delete the translation patterns at Call Routing > Translation Pattern. ## Step 7: Add block patterns **With an access code such as 9, compulsory stripped before the call leaves** ### Do Configure route patterns configured to block calls that should not be routed, such as Cisco's example pattern 91900XXXXXXX to prevent calls to 900 services or specific area codes to mitigate toll fraud[^1]. Assign the block patterns to a partition included in calling search spaces alongside broader dialing patterns[^41]. WarmTransfer's reading of the sources is that a block pattern that provides a more specific match will take precedence over a broader route pattern regardless of partition order within the calling search space[^27]. ### Verify In Dialed Number Analyzer, enter a blocked test number under the calling search space to verify that the block pattern matches[^13][^15]. ### Rollback Suggested rollback: navigate to Call Routing > Route/Hunt > Route Pattern, select the block pattern, and delete it. **With an access code that a translation pattern rewrites to +E.164, and route patterns match the + form** ### Do WarmTransfer's reading of the sources is that when a translation pattern rewrites dialed numbers to +E.164 before route patterns are matched, block patterns have to be written against the rewritten string and placed in a partition that the translation pattern's CSS reaches[^2]. Configure route patterns to block calls that should not be routed, including 900 services or specific area codes for toll fraud prevention[^1]. ### Verify In Dialed Number Analyzer, test a blocked dialed number to verify that digit analysis traces through the initial translation pattern and matches the +E.164 block pattern[^15]. ### Rollback Suggested rollback: delete the block route patterns at Call Routing > Route/Hunt > Route Pattern. ## Step 8: Check for overlaps that delay calls ### Do Identify patterns where a dialed string fully matches one entry but overlaps a longer pattern, including expressions using the exclamation-mark wildcard[^51][^28]. When a dialed string fully matches one entry but overlaps a longer pattern, Unified CM runs the T302 interdigit timer to allow further digits before routing[^28]. The interdigit timeout is set by the T302 service parameter in the Clusterwide Parameters (Device - General) section, with a default of 15 seconds[^44]. With Urgent Priority enabled on a directory number, a call to that number routes at once without waiting for the interdigit timeout, even when an overlapping pattern exists[^48]. WarmTransfer's reading of the sources is that marking a route or translation pattern as urgent is expected to route the call as soon as that pattern matches instead of waiting for T302[^49]. ### Verify When testing dialed patterns on an endpoint, wait at least 10 seconds after the last digit before evaluating an uncompleted call as a failure, because the call may be waiting for the interdigit timer to expire[^18]. ### Rollback Suggested rollback: uncheck the Urgent Priority setting on modified directory numbers, route patterns, or translation patterns. ## Step 9: Place directory numbers and assign calling search spaces **On the phone (device) only** ### Do Assign each directory number to an internal partition rather than leaving it in the <None> partition[^24][^41]. Set the Calling Search Space on the phone device to the appropriate tier CSS[^3]. Ensure every tier CSS includes the internal directory number partition, because a calling search space determines which call destinations a caller can reach[^6]. ### Verify Suggested check: place internal and external calls from a test phone assigned the target device CSS. In Cisco's troubleshooting case where the dialed number matched no pattern in any partition the caller's CSS could reach, the phone received reorder tone[^23]. ### Rollback Suggested rollback: revert the phone's Calling Search Space setting to its previous configuration. **On both the line (directory number) and the phone** ### Do Assign each directory number to an internal partition rather than the <None> partition[^24][^41]. Assign a Calling Search Space on the line configuration and a Calling Search Space on the phone configuration[^5]. When a calling search space is assigned both to the caller's phone and to the caller's directory number, Unified CM concatenates the two and searches the partitions of both[^5]. On an IP phone that has both a line CSS and a device CSS, the line CSS takes precedence over the device CSS[^19]. If two patterns match the dialed digits equally well, digit analysis chooses the one in the partition listed first[^46]. ### Verify Suggested check: make test calls across different classes of service to verify line and device CSS interactions. In Cisco's troubleshooting case, when a dialed number matched no pattern in any partition reachable through either the line or device CSS, the phone received reorder tone[^23]. ### Rollback Suggested rollback: restore the prior Calling Search Space values on both the directory number and the phone device. ## Step 10: Prove the dial plan with Dialed Number Analyzer ### Do Dialed Number Analyzer lets an administrator test a Unified CM dial plan configuration before deploying it[^16]. Dialed Number Analyzer is enabled at Tools > Service Activation by activating Cisco Dialed Number Analyzer and Cisco Dialed Number Analyzer Server, and is then reached at https://<node>/dna[^12]. Cisco recommends activating the Dialed Number Analyzer services on only one cluster node, the one with the least call-processing activity[^14]. Cisco warns that the Dialed Number Analyzer service consumes a lot of resources and should be activated only during off-peak hours[^17]. Test numbers using the calling search space and time input options to evaluate dial plan logic across tiers[^13]. ### Verify Dialed Number Analyzer output shows each pattern matched in sequence, such as a translation pattern that rewrites the number followed by the route pattern and trunk the call would use[^15]. ### Rollback Suggested rollback: navigate to service activation under tools and deactivate both dialed number analyzer services once testing completes. ## Step 11: Record the route plan ### Do Access Call Routing > Route Plan Report to review the detailed route plan, and save the output as a CSV file to preserve an as-built audit record[^43]. If route filters were implemented, note that Cisco cautions against assigning a single route filter to too many route patterns[^35]. ### Verify Suggested check: open the exported CSV file and confirm that all route patterns, translation patterns, and directory numbers reside in their intended partitions, with none remaining in the Null or <None> partition[^24][^43]. ### Rollback Suggested rollback: this is a read-only reporting step; no configuration changes need to be reversed. ## See also See also [Unified CM dial plan partitions and calling search spaces](https://warmtransfer.net/knowledge/cucm-dial-plan). See also [Unified CM device pools and device configuration model](https://warmtransfer.net/knowledge/cucm-device-pools). See also [Unified CM Bulk Administration Tool export formats](https://warmtransfer.net/knowledge/cucm-bulk-administration-tool). ## Applicability Applies to: Cisco Unified Communications Manager. Deployments: on-premises and dedicated instance. Sources checked 2026-09-24. Dialed Number Analyzer activation and analysis procedures apply to releases 12.x, 14.x, and 15.x[^12]. ## What remains uncertain Whether the default value for the T302 interdigit timer remains 15 seconds in every SU of Release 15 is not covered by the sources below. Whether line CSS precedence over device CSS applies identically to CTI ports or other non-phone endpoints is not covered by the sources below. Specific route group gateway selection distribution algorithms (such as circular or top-down) are not covered by the sources below. Specific non-North American national numbering plan wildcard implementations are not covered by the sources below. ## Sources [^1]: Block patterns prevent calls that should not be routed; Cisco's example blocks 91900XXXXXXX to stop calls to 900 services and suggests blocking area codes to prevent toll fraud. 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), Example of Block and Route Patterns. Checked 2026-09-24. [^2]: When a translation pattern rewrites dialed numbers to +E.164 before route patterns are matched, block patterns have to be written against the rewritten string and placed in a partition that the translation pattern's CSS reaches (inferred). 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), Call Routing Overview > Translation Patterns; Example of Block and Route Patterns. Checked 2026-09-24. [^3]: Cisco documents building classes of service from partitions and CSSs, with an example ladder of Base_CSS (emergency and internal), LocalPSTN_CSS, NationalPSTN_CSS and InternationalPSTN_CSS, each adding call types to the previous one. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Partitions](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_010000.html), Class of Service (table). Checked 2026-09-24. [^4]: The list of partitions in a calling search space is limited to a maximum of 1024 characters. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Partitions](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_010000.html), Partition Name Guidelines. Checked 2026-09-24. [^5]: When a calling search space is assigned both to the caller's phone and to the caller's directory number, Unified CM concatenates the two and searches the partitions of both. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Partitions](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_010000.html), Calling Search Space Overview. Checked 2026-09-24. [^6]: A calling search space is a prioritized (ordered) list of partitions that determines which call destinations a caller can reach. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Partitions](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_010000.html), Calling Search Space Overview. Checked 2026-09-24. [^7]: Calling search spaces are created at Call Routing > Class of Control > Calling Search Space, by moving partitions from Available Partitions to Selected Partitions and ordering them with the arrow buttons. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Partitions](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_010000.html), Configure Calling Search Spaces (procedure). Checked 2026-09-24. [^8]: A caller reaches a destination only if the destination's partition is in the caller's calling search space; otherwise the call is rejected, or a translation pattern is ignored. Source: [Configure Partition and Calling Search Space](https://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/22325-part-css-tn.html), Background Information. Checked 2026-09-24. [^9]: A calling search space name can be up to 50 alphanumeric characters. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Partitions](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_010000.html), Configure Calling Search Spaces (Name step). Checked 2026-09-24. [^10]: Deleted partitions cannot be retrieved. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Partitions](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_010000.html), Partition Interactions and Restrictions. Checked 2026-09-24. [^11]: A gateway or trunk that a route pattern points to directly is not available for association with a route group. 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), Configure Route Patterns. Checked 2026-09-24. [^12]: Dialed Number Analyzer is enabled at Tools > Service Activation by activating Cisco Dialed Number Analyzer and Cisco Dialed Number Analyzer Server, and is then reached at https:///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), How to Enable and Access Dialed Number Analyzer. Checked 2026-09-24. [^13]: A Dialed Number Analyzer analysis takes the dialed number and can optionally use a chosen calling search space and time to simulate a caller's permissions. 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), Key Features and Use Cases of Dialed Number Analyzer. Checked 2026-09-24. [^14]: Cisco recommends activating the Dialed Number Analyzer services on only one cluster node, the one with the least call-processing activity. Source: [Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Services](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/adminGd/cucm_b_administration-guide-15/cucm_b_test-adminguide_chapter_010111.html), Cisco Dialed Number Analyzer; Cisco Dialed Number Analyzer Server. Checked 2026-09-24. [^15]: Dialed Number Analyzer output shows each pattern matched in sequence, for example a translation pattern that rewrites the number followed by the route pattern and trunk the call would use. 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), Key Features and Use Cases of Dialed Number Analyzer (example output). Checked 2026-09-24. [^16]: Dialed Number Analyzer lets an administrator test a Unified CM dial plan configuration before deploying it. 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), Troubleshooting with Dialed Number Analyzer. Checked 2026-09-24. [^17]: Cisco warns that the Dialed Number Analyzer service consumes a lot of resources and should be activated only during off-peak hours. Source: [Administration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Services](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/admin/15/adminGd/cucm_b_administration-guide-15/cucm_b_test-adminguide_chapter_010111.html), Cisco Dialed Number Analyzer. Checked 2026-09-24. [^18]: Cisco's troubleshooting guide advises waiting at least 10 seconds after the last digit when testing, because the call may be waiting for the interdigit timer 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 Plans and Routing Issues chapter (interdigit timer advice). Checked 2026-09-24. [^19]: On an IP phone that has both a line CSS and a device CSS, the line CSS takes precedence over the device CSS. Source: [Configure Partition and Calling Search Space](https://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/22325-part-css-tn.html), Background Information. Checked 2026-09-24. [^20]: Local route group names are added at Call Routing > Route/Hunt > Local Route Group Names, and a device pool maps the Standard Local Route Group to a real route group at System > Device Pool. 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), Configure Local Route Group Names; Associate a Local Route Group with a Device Pool. Checked 2026-09-24. [^21]: Partition names may contain alphanumeric characters, spaces, hyphens and underscores. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Partitions](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_010000.html), Partition Name Guidelines. Checked 2026-09-24. [^22]: Because of the 1024-character limit, the number of partitions a CSS can hold falls as partition names get longer: Cisco's table gives 340 for 2-character names, 172 for 5, 92 for 10 and 64 for 15. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Partitions](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_010000.html), Partition Name Guidelines, table Partition Name Length / Maximum Number of Partitions. Checked 2026-09-24. [^23]: In Cisco's troubleshooting case where the dialed number matched no pattern in any partition the caller's CSS could reach, the phone received reorder tone. 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), Route Partitions and Calling Search Spaces (case example). Checked 2026-09-24. [^24]: Any calling device can reach a dial plan entry left in the partition, and Cisco recommends not leaving dial plan entries there. Source: [Configure Partition and Calling Search Space](https://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/22325-part-css-tn.html), Background Information. Checked 2026-09-24. [^25]: An item not assigned to any partition is in the Null (default) partition, every user can call it, and the system always searches the Null partition last. 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), Route Partitions and Calling Search Spaces. Checked 2026-09-24. [^26]: Classifying a route pattern as Off-Net lets users hear a secondary dial tone that tells them the call is leaving the organisation. 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), Example of On-Net and Off-Net Patterns. Checked 2026-09-24. [^27]: Partition order in a CSS therefore does not make a less specific pattern in an earlier partition win over a more specific pattern in a later one; order decides only between equally good matches (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), Route Partitions and Calling Search Spaces (tie-break sentence). Checked 2026-09-24. [^28]: When a dialed string fully matches one entry but overlaps a longer pattern, Unified CM runs the T302 interdigit timer to allow 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-09-24. [^29]: For a pattern such as 9.@, where 9 is the external access code, the Discard Digits option strips the pre-dot digits so the PSTN can route the call. 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), Example of Pre-dot Digit Removal. Checked 2026-09-24. [^30]: Cisco lists completing the partition configuration task flow as a prerequisite for call routing configuration. 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), Call Routing Prerequisites. Checked 2026-09-24. [^31]: Before a partition can be deleted, the items that use it must be moved to a different partition or deleted. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Partitions](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_010000.html), Partition Interactions and Restrictions. Checked 2026-09-24. [^32]: In Unified CM a partition is a logical group that can hold route patterns, directory numbers, translation patterns, transformation patterns, URIs and hunt pilots. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Partitions](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_010000.html), Partitions Overview. Checked 2026-09-24. [^33]: Partitions are created at Call Routing > Class of Control > Partition with Add New, and several partitions can be entered at once by putting each on its own line. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Partitions](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_010000.html), Configure Partitions (procedure). Checked 2026-09-24. [^34]: A partition can carry a time schedule, and a time-zone setting (Originating Device or a Specific Time Zone) decides which clock the schedule is compared against. Source: [System Configuration Guide for Cisco Unified Communications Manager, Release 15 and SUs - Configure Partitions](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_010000.html), Configure Partitions (procedure, time schedule and time zone steps). Checked 2026-09-24. [^35]: Cisco cautions against assigning a single route filter to too many route patterns. 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), Call Routing Restrictions > Route Filter Associations. Checked 2026-09-24. [^36]: Route groups are configured at Call Routing > Route/Hunt > Route Group, and a route group sets the order in which the system selects gateways for outgoing calls. 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), Configure Route Groups. Checked 2026-09-24. [^37]: A route list can contain only route groups and local route groups, not individual gateways or trunks. 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), Configure Route Lists. Checked 2026-09-24. [^38]: Route lists are configured at Call Routing > Route/Hunt > Route List, where route groups are added with Add Route Group and the list is saved and then applied with Apply Config. 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), Configure Route Lists. Checked 2026-09-24. [^39]: Although a route pattern can point directly to a gateway, Cisco recommends configuring route lists and route groups for flexibility and scalability. 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), Configure Route Patterns. Checked 2026-09-24. [^40]: Route patterns are configured at Call Routing > Route/Hunt > Route Pattern, where the Gateway/Route List drop-down selects where matching calls are sent. 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), Configure Route Patterns. Checked 2026-09-24. [^41]: A route pattern, directory number or translation pattern is placed in a partition by choosing that partition when it is configured. Source: [Configure Partition and Calling Search Space](https://www.cisco.com/c/en/us/support/docs/voice-unified-communications/unified-communications-manager-callmanager/22325-part-css-tn.html), Configure. Checked 2026-09-24. [^42]: Unified CM searches for a route pattern that matches an external dial string and uses it to send the call to a gateway or route list. 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), Call Routing Overview > Route Patterns. Checked 2026-09-24. [^43]: The Route Plan Report at Call Routing > Route Plan Report shows the detailed route plan and can be saved as a CSV file. 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), Call Routing Restrictions > Route Plan Report. Checked 2026-09-24. [^44]: The interdigit timeout is set by the T302 service parameter in the Clusterwide Parameters (Device - General) section, with a default of 15 seconds. 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 / T302 timer description. Checked 2026-09-24. [^45]: Cisco's call routing task flow orders the work as translation patterns, transformation patterns, local route groups, route groups, route lists, route filters and then route patterns. 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), Call Routing Configuration Task Flow. Checked 2026-09-24. [^46]: If two patterns match the dialed digits equally well, digit analysis chooses the one in the partition listed first in the calling search space. 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), Route Partitions and Calling Search Spaces. Checked 2026-09-24. [^47]: Time-of-day routing is configured by creating a time period, then a time schedule, then choosing the schedule in the partition's Time Schedule drop-down at Call Routing > Class of Control > Partition and saving. 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), Configure Time of Day Routing; Associate a Time Schedule with a Partition. Checked 2026-09-24. [^48]: With Urgent Priority enabled on a directory number, a call to that number routes at once without waiting for the interdigit timeout, even when 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), Introduction / Background Information. Checked 2026-09-24. [^49]: Marking a route or translation pattern as urgent is expected to have the same effect as on a directory number: the call routes as soon as that pattern matches instead of waiting for T302 (inferred). 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), Introduction (urgent patterns) / Background Information. Checked 2026-09-24. [^50]: The @ wildcard matches all National Numbering Plan numbers, and a route pattern can contain only one @. 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-09-24. [^51]: In a route pattern the ! wildcard matches one or more digits 0 through 9. 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-09-24. [^52]: The dot (.) in a route pattern separates the access code from the rest of the number. 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-09-24. [^53]: In a route pattern \+ is the international escape character, used to match a leading plus sign. 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-09-24. [^54]: Square brackets enclose a range of values in a route pattern, a hyphen inside them denotes a range, and # generally marks 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-09-24. [^55]: In a route pattern the X wildcard matches any single digit 0 through 9. 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-09-24. [^56]: Translation patterns are configured at Call Routing > Translation Pattern, with a partition and a Calling Search Space field among the settings. 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), Configure Translation Patterns. Checked 2026-09-24. [^57]: Translation patterns use the same rules and wildcards as route patterns; on a match Unified CM applies the translation and then routes the call again using the translation pattern's calling search space. 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), Call Routing Overview > Translation Patterns. Checked 2026-09-24. [^58]: Each translation pattern's combination of partition, route filter and numbering plan must be unique. 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), Configure Translation Patterns. Checked 2026-09-24. [^59]: A device learns its local route group through the device pool: the local route group is associated in the Local Route Group Settings section of System > Device Pool. 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), Configure Call Routing / Associate a Local Route Group with a Device Pool. Checked 2026-09-24.