Generate the full object chain — Voicemail Pilot, Voicemail Profile, Hunt Pilot, Hunt List, Line Group, and the SCCP/SIP Ports that tie CUCM to Unity Connection — in one screen. Copy, paste, build.
Wiring CUCM to Unity Connection is a multi-object chain — miss one object and phones' voicemail button rings forever. This tool takes three inputs (pilot DN, number of ports, SIP vs SCCP) and emits every object with exact field-level values, plus the Unity side (Call Handler for Opening Greeting, Phone System, Port Group). If you're replacing a legacy voicemail or standing up a new cluster, run this first, then build top-down.
Fill in the pilot DN + port count, click Generate config.
SIP Trunk (or Ports) → Line Group → Hunt List → Hunt Pilot → Voicemail Pilot → Voicemail Profile.
Phone System → Port Group → Ports → Phone System integration.
Voicemail Profile on every user DN whose voicemail button should route to this pilot.
SCCP integrations create one "port" per concurrent call. Each port is a device in CUCM, each has a DN, each has its own failover target. For 24 ports you manage 24 DNs, 24 line-appearance configs, 24 unregistration alarms. SIP trunks collapse all that into a single object — one trunk with a destination FQDN, one DP assignment, one security profile. That's why every modern Unity deployment runs SIP.
SCCP still has one niche: older Unity Connection 9.x clusters where TLS between CUCM and Unity is fragile, or deployments where network-team restrictions prevent opening SIP 5060/5061 between the two. If you're on Unity 12.5+ and CUCM 12.5+, there's no reason not to migrate to SIP as part of the next upgrade cycle.
One mistake we see weekly: the voicemail pilot DN and the hunt pilot DN are the same number. The Voicemail Pilot is just a reference to the Hunt Pilot — they don't both dial the DN. Create one DN (say 7000) as a Hunt Pilot, then create the Voicemail Pilot with the same DN + Partition. CUCM knows to chain them.
Start with 12–16 ports. Monitor port-in-use counter for a month; scale up if you hit > 70% utilization at peak.
TLS + SRTP. Mixed-mode CUCM + Unity 12.5+ supports it end-to-end; it's the only mode auditors accept.
Usually the Voicemail Profile isn't assigned to the line. Check Line Details → Voicemail Profile.
Only if sites have different Unity clusters or distinct pilot DNs. Most single-cluster deployments share one profile.
Pilot 7000, 8 SIP ports, Unity pub + sub in one cluster.
Pilot 7000, 32 SIP ports, per-site Voicemail Profiles (VMProfile_HQ, VMProfile_BR1, VMProfile_BR2).
Existing SCCP with 16 ports. Plan: build parallel SIP trunk + Hunt Pilot 7001, shift users in waves.
Our UC Modernization Sprint handles the full Unity migration + CUCM integration rebuild — zero-downtime cutover, parallel-run verified.