Furthermore, while you can vMotion a CUCM 15 VM across hosts, you cannot easily move it across vCenter instances or to a public cloud (like AWS EC2) without re-architecting the network and storage latency. CUCM’s reliance on multicast for MOH (Music on Hold) and its intolerance for >10ms of WAN latency between publisher and subscriber nodes means that "hybrid cloud" is mostly marketing. Virtualization gives you portability within the data center, not across geographies. CUCM 15’s virtualization-only strategy is not a feature; it is a reckoning. It forces the voice engineering team to merge with the virtualization and cloud teams, breaking down silos that have existed since the Avaya Definity era. The essay’s final judgment is this: CUCM 15 sacrifices the simplicity of the appliance for the agility of the virtual machine. It demands a higher level of vSphere competence—CPU reservations, PVSCSI tuning, anti-affinity rules, and distributed switch configuration—but rewards that effort with hardware independence, faster recovery, and the ability to treat call control as code.
The deep implication here is the elimination of overcommit. In traditional IT, virtualization’s economic benefit comes from oversubscription of CPU and RAM. CUCM 15 explicitly forbids this for production nodes. For a 10,000-user subscriber node, the SSM might mandate 8 vCPUs with 8,000 MHz of reservation and 32 GB of reserved RAM. This is not a suggestion; it is a support boundary. Cisco’s real-time kernel (based on the Precision Time Protocol – PTP) requires deterministic scheduling. If a hypervisor scheduler preempts a CUCM vCPU to service a print server or a development VM, call setup latency spikes, media resources glitch, and CDR logs become corrupted. cucm 15 virtualization
Thus, CUCM 15 virtualization forces a return to disciplined capacity planning. It transforms the vSphere administrator into a co-engineer. You cannot simply drop the OVA on a congested cluster; you must deploy dedicated resource pools, anti-affinity rules (to prevent two CUCM publishers on the same ESXi host), and potentially dedicated vSphere clusters. The freedom from hardware is traded for a stricter adherence to hypervisor governance. CUCM’s architectural heart is its Informix (moving toward PostgreSQL in later 15.x updates) database cluster—a "dumb" replicating system where every node holds a full read/write copy of the configuration database. Virtualizing this tier has historically been perilous due to split-brain scenarios and I/O latency. Furthermore, while you can vMotion a CUCM 15
