Enter your site list and calling-permission tiers — get a consistent Partition list and a per-tier, per-site Calling Search Space matrix that scales to 100+ sites without becoming unmaintainable.
CSS + Partition is CUCM's access-control mechanism for dial plans, and it's also the part of the dial plan that most often looks like "whatever the last engineer invented on a Tuesday." This tool takes a clean site list and permission-tier definition (Internal / Local / LD / Intl / Restricted) and produces a Partition name list, a CSS name list, and a matrix showing which Partitions belong in which CSS for each site. The naming convention is Cisco-SRND-aligned (PT_Site_Tier and CSS_Site_Tier). Generate once, import to CUCM via BAT or AXL.
Enter sites + tiers, click Generate matrix.
Containers for DNs, Translation Patterns, and Route Patterns. Group by site and by tier.
Ordered list of Partitions a device is allowed to see. Assigned at phone, line, or device profile level.
Which CSS can reach which Partitions defines your calling permissions.
Most CUCM dial plans over 5 sites drift into unmaintainable territory within two years because each new site gets Partition and CSS names invented on the fly by whichever engineer provisioned it. By year three, you have SiteDAL_PT, DAL_Partition, PT_DAL_Local, and dallas_css_ld all coexisting, and nobody is confident which ones are still in use. The fix is mechanical: pick a naming convention up front and generate names from a template. This tool uses PT_{SITE}_{TIER} and CSS_{SITE}_{TIER} — Cisco-SRND-aligned, sorted correctly in the CUCM admin UI, self-documenting.
The second design choice is which Partitions each CSS includes. The rule: CSS for tier N includes Partitions for tiers 1 through N. So CSS_DAL_LD includes PT_DAL_Internal, PT_DAL_Local, PT_DAL_LD, plus a shared PT_Common (for things like directory, voicemail, 911). International users get PT_DAL_Intl added on top. Restricted users get only Internal + Emergency + Common. This layered-include model makes the CSS membership obvious from the name.
Emergency (911) goes in every CSS, always. It's in a Partition called PT_Common_Emergency so even the restricted lobby phones and the tightest lock-down profiles still reach 911. Kari's Law and RAY BAUM'S Act both mandate this; it's also just the right engineering decision.
So you can assign per-site outbound caller ID and per-site emergency response location without cross-site bleed.
Yes. Kari's Law and RAY BAUM'S Act make this a compliance requirement in the US.
No hard ceiling, but the practical limit is what your team can audit. A 100-site deployment with 5 tiers = 500 Partitions is fine if generated from a template; it becomes unmaintainable if invented by hand.
BAT doesn't natively create Partitions/CSS — you use AXL or the GUI. The tool output is copy-paste ready for the GUI; AXL XML export is on the roadmap.
DAL, HOU, NYC · Internal + Local + LD + Emergency
20 sites × 5 tiers (Internal / Local / LD / Intl / Restricted) + Emergency + Common
Merging two 10-site companies. Pre-existing Partitions renamed to the PT_{SITE}_{TIER} convention.
The Network & UC Health Assessment includes a dial-plan audit — CSS, Partitions, Translations, and Route Patterns — with a rename/consolidate plan.