The future of voice wasn't in beige boxes anymore. It was in a few gigabytes of RAM, a reservation policy, and an engineer who knew when to break the rules.
The first phone in Tokyo lit up. Then twenty. Then two hundred. Registration requests flooded the virtual CUCM. She watched vCenter performance charts: CPU utilization spiked to 60%, then settled at 22%. Memory steady at 7.9GB. Network latency between nodes: 0.3ms. cucm virtualization
She had said that. Back in 2014, at a Cisco Live breakout session, a bearded engineer had mentioned "UCS and VMware support." But actual production? At 11:47 PM, with Tokyo waking up? The future of voice wasn't in beige boxes anymore
Tokyo's first early riser would be picking up a phone in sixty seconds. Then twenty
Mariana opened her third energy drink and her pre-built VMware template. For months, she'd been quietly building this—a virtualized CUCM cluster on their internal UCS blade chassis. No one knew. "Sandbox testing," she'd called it. Really, it was insurance.
CUCM is picky about MAC addresses. Change a virtual NIC's MAC after installation, and the entire node's certificate chain explodes. She'd learned that the hard way during testing. Tonight, she triple-checked the port group settings: VLAN 10 for PUB, VLAN 11 for SUB1, VLAN 12 for SUB2. The Cisco switchports were pre-configured with spanning-tree portfast and switchport voice vlan . The VMs would never know they weren't physical.