4.1 Partitions and Calling Search Spaces (CSS)

4.1 Partitions and Calling Search Spaces (CSS)

In Cisco Unified Communications Manager (CUCM), call routing decisions depend entirely on two foundational constructs: Partitions and Calling Search Spaces (CSS). Together, they establish a multi-tenant, policy-driven call routing architecture that governs which endpoints, gateways, trunks, and applications can reach specific internal and external destinations.

---

1. Foundational Architecture: Partitions vs. Calling Search Spaces

A classic physical security analogy illustrates the relationship between Partitions and Calling Search Spaces:

• Partition (The Lock): A logical container or grouping mechanism applied to addressable destinations. Assigning a partition to an entity locks that entity so that only callers possessing the appropriate key can dial it.
• Calling Search Space (The Keyring): An ordered, prioritized collection of partitions assigned to a calling party (such as an IP phone line, physical device, voice gateway port, or SIP trunk). The CSS defines which partitions the caller can search and unlock.

Dialable Entities Residing in Partitions

Partitions can be assigned to virtually any addressable target within the CUCM database, including:

• Directory Numbers (DNs) on IP phones, softphones, and analog ports
• Translation Patterns and Transformation Patterns
• Route Patterns and SIP Route Patterns
• Hunt Pilots and Call Park numbers (Standard and Directed)
• Meet-Me conference numbers and Call Pickup groups
• Cisco Unity Connection voice messaging ports and CTI Route Points

If an entity is created without specifying a partition, CUCM automatically places it into the Null Partition (designated in the interface as <None>).

---

2. Digit Analysis Engine and Matching Precedence

When a user enters digits or an ingress SIP trunk receives an INVITE with an initial Request-URI, the CUCM Digit Analysis (DA) engine evaluates the dialed digit string against the patterns contained within the caller's effective search space. Digit analysis follows two strict evaluation criteria: the Longest Match Rule and the Equal-Length Tie-Breaker Rule.

The Longest Match Rule (Maximum Specificity)

The fundamental law of CUCM digit analysis states: the closest match, meaning the pattern that matches the fewest possible digit strings, always wins, regardless of the order of partitions in the Calling Search Space. Cisco calls this the closest-match rule; it is often taught as the longest-match rule.

For example, suppose a Calling Search Space contains two partitions in this exact order:

1. Corporate_PT (listed first)
2. Branch_PT (listed second)

Assume the following patterns exist in these partitions:

• Corporate_PT contains the wildcard pattern 2XXX (matches any 4-digit number starting with 2).
• Branch_PT contains the exact pattern 2001 (matches only 2001).

When a caller dials 2001, both patterns match. However, 2001 in Branch_PT matches exactly one string, whereas 2XXX in Corporate_PT matches 1,000 strings (2000 through 2999). Even though Corporate_PT is listed first in the caller's CSS, CUCM selects 2001 in Branch_PT because specificity overrides partition ordering.

Equal-Length Matching Rule (CSS Order as Tie-Breaker)

When two or more matching patterns possess the exact same length and specificity, CUCM cannot distinguish between them based on digits alone. Under this condition, CUCM applies the partition order within the Calling Search Space as the deterministic tie-breaker:

• The pattern residing in the partition listed earlier (higher priority) in the CSS wins.
• The pattern residing in a subsequent partition is ignored.

Digit Analysis Decision Matrix

---

3. Line CSS and Device CSS Concatenation

In CUCM, Calling Search Spaces can be applied at two distinct configuration tiers on every IP phone:

1. Line CSS: Assigned directly to the Directory Number (DN) under the line configuration.
2. Device CSS: Assigned to the physical endpoint under the phone device configuration.

The Concatenation Rule

When an endpoint originates a call, CUCM combines both configurations into a single Effective Calling Search Space. The concatenation follows a strict, non-configurable architectural order:

$\text{Effective CSS} = [\text{Line CSS Partitions}] + [\text{Device CSS Partitions}]$

Partitions assigned to the Line CSS are placed at the beginning of the search space, followed immediately by the partitions assigned to the Device CSS. If a partition is listed in both the Line CSS and the Device CSS, CUCM drops the duplicate entry, keeping only the first occurrence from the Line CSS.

Line CSS:   [ Internal_PT, Local_PT ]
Device CSS: [ LongDistance_PT, International_PT ]
---------------------------------------------------------------------------
Effective:  [ Internal_PT, Local_PT, LongDistance_PT, International_PT ]

Shared Line and Shared Device Architectural Use Cases

Concatenating Line and Device CSS enables powerful policy enforcement across shared lines and shared physical hardware:

• Shared Device Policy (Lobby / Common Area Phones): An enterprise deploys phones in public lobbies and conference rooms. The organization wants to restrict these devices to internal and local emergency calls only, regardless of who dials. By leaving the Line CSS empty (or restricted) and assigning a restrictive Device CSS containing only Internal_PT and Emergency_PT, any line on that device is physically barred from placing toll or international calls.
• Shared Line Across Distinct Devices: Directory Number 3001 (assigned to an executive) is shared between two physical phones: Phone A on the executive's desk and Phone B in a public conference room.
  • DN 3001 has a Line CSS containing Internal_PT and Executive_Toll_PT.
  • Phone A has a Device CSS containing International_PT.
  • Phone B has a Device CSS containing Restricted_PT.
  • Result: Calling from Phone A enables internal, toll, and international calls. Calling from Phone B allows internal and toll calls (inherited from the executive Line CSS), but international dialing is blocked because Phone B's Device CSS lacks International_PT.

Line vs. Device CSS Precedence Summary

---

4. The Null Partition (<None>) and Security Boundaries

The Null Partition (represented as <None> in CUCM administration) is a default system partition with unique properties:

1. Universal Accessibility: Any calling entity can reach patterns in the Null Partition, even if the calling entity has its Line CSS and Device CSS set to <None>.
2. Evaluation Order: Digit analysis searches the Null Partition last. CUCM checks all explicitly listed partitions in the Effective CSS first. Only if no matching pattern is found in any CSS partition does digit analysis inspect the Null Partition.
3. Toll Fraud Hazards: If an administrator creates an outbound Route Pattern (such as 9.@ or 9.1[2-9]XX[2-9]XXXXXX) or an unauthenticated SIP trunk and leaves the partition set to <None>, any device in the enterprise—including unauthenticated public phones, auto-attendant transfer legs, and external callers reaching an open transfer prompt—can dial outbound toll numbers. Best practice mandates placing all dialable patterns into dedicated, explicitly named partitions.

---

5. Time-of-Day (ToD) Routing Architecture

Time-of-Day (ToD) routing dynamically alters call routing behavior based on the date, day of week, and time of day. In CUCM, ToD routing is not configured on route patterns or directory numbers directly; instead, Time Schedules are assigned to Partitions.

Components of Time-of-Day Routing

ToD routing relies on two distinct configuration elements under Call Routing > Class of Control:

• Time Period: Defines a discrete time window, such as 08:00 to 17:00, active on Monday, Tuesday, Wednesday, Thursday, Friday. Time periods can also specify fixed calendar dates (e.g., New Year's Day holiday: January 1 to January 1).
• Time Schedule: A logical container that groups one or more Time Periods. For example, Normal_Business_Schedule might contain two Time Periods: Weekday_Hours (Mon-Fri 08:00-17:00) and Saturday_Hours (Sat 09:00-13:00).

Dynamic Partition Activation

When a Time Schedule is associated with a Partition, that partition's availability to the Digit Analysis engine becomes dynamic:

• In-Schedule: During defined time periods, the partition is Active. CUCM includes the partition in digit analysis evaluation.
• Out-of-Schedule: Outside defined time periods, the partition becomes Inactive (Dormant). The Digit Analysis engine completely bypasses the partition, behaving as if the partition does not exist in the caller's CSS.

[Incoming Call to 5000 (Main Support Line)]
               |
               v
     [Check Caller's CSS]
               |
               v
   +-----------------------+     Active (Mon-Fri 08:00-17:00)
   | Support_Day_PT        | ---------------------------------> Rings Support Hunt Pilot
   | (Linked to Schedule)  |
   +-----------------------+
               | Inactive (After Hours)
               v
   +-----------------------+
   | Support_Night_PT      | ---------------------------------> Routes to Unity Connection
   | (No Time Schedule)    |
   +-----------------------+

Real-World Implementation Pattern: Day / Night Call Routing

To route an organization's main number (5000) to live receptionist queues during the day and to voicemail after hours:

1. Create partition Main_Day_PT and attach the Business_Hours_TS Time Schedule.
2. Create partition Main_Night_PT with no Time Schedule (permanently active).
3. Assign DN 5000 in Main_Day_PT pointing to the Receptionist Hunt Pilot.
4. Assign DN 5000 in Main_Night_PT with Call Forward All configured to the Cisco Unity Connection voicemail pilot.
5. In the incoming CSS (on the PSTN gateway or inbound SIP trunk), configure partition priority:
   • 1st: Main_Day_PT
   • 2nd: Main_Night_PT

During business hours, both partitions match pattern 5000. Because both patterns have identical length and specificity, the tie-breaker rule applies: Main_Day_PT wins because it is listed first in the CSS. After hours, Main_Day_PT becomes dormant and invisible; digit analysis falls through to Main_Night_PT, seamlessly routing callers to voicemail without requiring manual attendant switches.