top of page

Cisco UCM 15: Modernising Mission‑Critical Hybrid Calling

  • Writer: Tim Banting
    Tim Banting
  • Apr 10
  • 2 min read

Cisco Webex has launched Unified Communications Manager (UCM) 15, a significant update to its enterprise calling foundation that bridges the gap between secure, on-premises infrastructure and agile cloud innovation.


Data Center (Source: Cisco Webex)

With over 30 million users relying on UCM, version 15 marks a strategic shift from a "cloud-only" narrative to a "cloud-connected" reality. By transitioning to a 64-bit architecture built on AlmaLinux 9 and removing legacy dependencies like CentOS 7, Cisco is offering a long-term roadmap for highly regulated and air-gapped environments while providing a low-friction path to Webex cloud services.

The Strategy

The release of UCM 15 addresses a critical market need: the ability to modernise without forced migration. Many global enterprises in government, healthcare, and finance operate under strict regulatory requirements that necessitate on-premises or hybrid control. UCM 15 acknowledges this by committing to an on-premises roadmap that extends through versions 16, 17, and beyond, ensuring over a decade of continued innovation.


Recent comparable developments in the collaboration space have often pushed for a total cloud transition, but Cisco’s approach focuses on "Hybrid Calling." This model allows organisations to keep their existing call control on-premises while selectively integrating cloud-powered analytics, AI background noise removal, and troubleshooting tools.

Technical Overhaul

Technically, the update is a foundational overhaul. The move to Python 3, modern cryptographic components, and TLS 1.3 support (introduced in Service Update 2) aligns the platform with the latest security benchmarks. Critically, the platform is designed to meet FIPS 140-3 standards, moving past the now-historical FIPS 140-2 requirements.


Furthermore, Cisco is expanding infrastructure flexibility in response to shifting virtualisation markets. By introducing support for alternate hypervisors, including Nutanix AHV (as of SU4) and Cisco’s own NFVIS-for-UC, IT leaders are granted more choice in their virtualisation strategy and potential licensing costs.

Capabilities & Limitations


Capabilities

  • Modernised Security Architecture: Features a 64-bit AlmaLinux 9 core, Python 3, and support for TLS 1.3 to meet modern federal and enterprise security requirements.

  • Webex Cloud-Connected UC: Enables on-premises users to access cloud-driven features like AI-powered noise removal and advanced analytics without moving their entire infrastructure.

  • Broad Interoperability: Offers deep integration with Microsoft Teams for presence synchronisation, call history, and voicemail, as well as support for multiple hypervisors including Nutanix and NFVIS.

Limitations

  • Hardware Dependencies: The removal of legacy OS dependencies like CentOS 7 may require hardware refreshes or specific migration steps for older deployments.

  • Phased Security Implementation: Some advanced security features, such as TLS 1.3, are not in the initial release but are available starting with Service Update 2 (SU2).

Signals to Watch

  • Hypervisor Diversification: Whether the addition of Nutanix and NFVIS support signals a broader trend of Cisco opening its UC stack to more third-party infrastructure to lower total cost of ownership (TCO).

  • The "Jabber-to-Webex" Transition: How quickly on-premises customers adopt "Hybrid Calling" features as a middle-ground before a full cloud migration.

  • Federal Compliance Deadlines: As USGv6 and FIPS 140-3 standards become the baseline, UCM 15’s adoption rate within government sectors will indicate if Cisco’s "air-gapped" commitment is meeting public sector needs.


Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page