# CUCM 14 End of Life: Dates, Support and Options

> Cisco published two end-of-life bulletins for Version 14 calling on the same day. On the perpetual one, both contract dates are the announcement date itself.

*Source: https://trybussolutions.com/cucm-14-end-of-life-dates/ · Trybus Solutions · Chattanooga, TN · 423-633-1817 · info@trybussolutions.com*

September 25, 2026 · 10 min read · Calling

If you are running Cisco Unified Communications Manager 14 and the cluster is not already under a service contract, there is no date in your future to plan against. The date you needed was 7 October 2024, and it was the day the bulletin was published.

That is not a transcription error. On the perpetual bulletin for Version 14 of the on-premises calling applications, End of New Service Attachment and End of Service Contract Renewal are both printed as 7 October 2024, the same day as the end-of-life announcement. There was no interval between the announcement and the close of the commercial path. If the software was covered that morning, you have options. If it was not, the option to buy coverage never opened.

## Which Bulletin Applies to You

Cisco published two on the same day, covering the same seven applications. One covers perpetual licensing. The other covers the associated on-premises Flex subscriptions. They carry different milestone tables, and most summaries quote whichever one they landed on.

*Cisco Version 14 on-premises calling end-of-life milestones, as published by Cisco in two bulletins*

| Milestone | Perpetual bulletin | On-premises Flex subscription bulletin |
|---|---|---|
| End-of-life announcement | 7 October 2024 | 7 October 2024 |
| End of sale | 7 April 2025 | 7 April 2025 |
| Last ship date | 6 July 2025 | 7 April 2025 |
| End of new service attachment | **7 October 2024** | 7 April 2025 |
| End of service contract renewal | **7 October 2024** | 7 April 2027 |
| End of change or renewal, subscription | Not applicable | 7 April 2027 |
| End of software maintenance releases | 7 April 2026 | 7 April 2026 |
| Last date of support | 30 April 2027 | 30 April 2027 |

Read the two contract rows across, because they are the whole difference. A Flex subscriber can still renew or add to an existing subscription until 7 April 2027. A perpetual customer cannot buy new coverage and cannot renew a lapsed contract, because both of those dates went by on the day the bulletin appeared.

What a perpetual customer retains is the contract already in force. Cisco's sentence is that "customers with active service contracts will continue to receive support from the Cisco Technical Assistance Center (TAC) as shown in Table 1 of the EoL bulletin." Table 1 gives the Last Date of Support as 30 April 2027, defined as the last date to receive service and support as entitled by active service contracts or warranty terms.

So the first question is not which version you are on. It is whether the entitlement under each cluster, node and Expressway pair is current, and whether it is perpetual or Flex. That is a records exercise rather than a technical one, and it decides everything downstream.

## The Seven Applications, and the Two Nobody Reads to the End Of

Both bulletins name the same seven:

- Cisco Unified Communications Manager 14
- Session Management Edition 14
- CUCM Instant Messaging and Presence Service 14
- Cisco Emergency Responder 14
- Unity Connection 14
- Cisco Prime Collaboration Deployment 14
- Cisco Expressway X14

The part number table on the perpetual bulletin reaches wider than those seven, picking up Cisco Meeting Server delivery kits, the Expressway Rich Media Session license and Unified Attendant Console 14.x not-for-resale licenses. If any of those sit in your estate, they are in scope even though the bulletin title names Unified Communications Manager.

**Expressway X14** is the one to inventory first. Expressway is the edge, and on most estates it is doing three jobs at once: mobile and remote access for softphones and desk phones outside the building, business-to-business video calling, and in some deployments the connection to a cloud service. It sits inside a bulletin whose title says Unified Communications Manager, so it gets missed. If your remote workers reach call control through X14, the edge of the voice estate is on the same support clock as the core, and the edge is the part exposed to the public internet. That is a conversation with the security team, and an unpatched edge node leads fairly quickly to [network segmentation work](https://trybussolutions.com/network-segmentation-without-stopping-the-business/) if the replacement is not going to land soon.

**Prime Collaboration Deployment 14** is the second. PCD is the tool most people use to run the upgrade itself, and it is on the end-of-life list alongside the software it upgrades. Decide which PCD version you will use as part of the plan, rather than discovering on the maintenance weekend that the migration tool is as old as the source cluster.

## Software Maintenance Ended in April 2026, Which Is the Part That Bites

End of software maintenance releases passed on 7 April 2026 on both bulletins. Cisco defines that milestone as the last date its engineering may release maintenance releases or bug fixes, after which it will no longer develop, repair, maintain or test the product software.

The practical reading: the code running on Version 14 is the code you keep. New defects found in it are not fixed on that version, and that includes defects with a security advisory attached. Support through 30 April 2027 means the Technical Assistance Center will work your case. It does not mean a fix exists to give you. For a call manager that is a production irritation. For an internet-facing Expressway it is a risk item the security lead will want written down with a date next to it.

This is also the sentence to take into a budget conversation. "Support ends in 2027" sounds like a 2027 problem. "We stopped receiving fixes in April 2026 and we are running the release we are stuck on" is a current-year problem.

## What Version 15 Actually Requires

Cisco directs Version 14 customers to the latest on-premises release or to cloud calling under Collaboration Flex Plan 3.0. Taking the on-premises path first, the upgrade guide is more specific than the bulletin, and three details decide how the project is scoped.

**The direct path exists, but not for everyone.** Release 12.5 and Release 14 with its service updates support a direct standard upgrade to Release 15, run from the operating system administration interface, the command line or Prime Collaboration Deployment. Releases 10.0, 10.5, 11.0, 11.5 and 12.0 cannot upgrade directly; Cisco routes those through a PCD migration task or a fresh install with data import. If part of the estate predates 12.5, that part is a migration rather than an upgrade, and it carries a different plan and a different weekend.

**14SU4 has a narrower set of destinations than the rest of the estate.** Cisco states that upgrades from Release 14SU4 to a cluster with a destination version lower than Release 15SU2, meaning 15 or 15SU1a, are not supported and will not be shown as a valid upgrade option, and recommends 15SU2 or higher as the destination instead. A cluster already on 14SU4 therefore cannot take the media you staged for the others. This is the kind of constraint that surfaces in a change window rather than in a design document.

**The hosts move too.** Cisco states that Version 15 on VMware ESXi requires the virtual machine settings to be updated to meet the new release requirements, including a higher virtual hardware version and a different guest operating system type, and that a direct upgrade of the Instant Messaging and Presence Service fails where the older release does not have enough virtual memory. Cisco states those qualitatively on the planning page and refers the reader to the release readme for figures, so establish the numbers from that readme against your own hosts rather than from any summary, including this one.

## The Successor Is Planned for 2027, Which Settles a Question People Leave Open

Cisco stated on its own collaboration blog, in a Cisco Live post published on 3 June 2026, that "version 16 is planned for calendar year 2027." That is a corporate blog statement rather than a bulletin or a roadmap commitment, and it should be read as one.

Read against the Version 14 dates, it still settles something. Waiting for the next on-premises generation is not a plan for an estate whose support ends on 30 April 2027, because the next generation is not scheduled to exist in a deployable form before that date arrives. The realistic destinations for a decision made now are Version 15 with a refresh cycle understood, or a move to the cloud.

## What the Options Actually Are

Three, and the cost sits in a different place in each.

**Upgrade to Version 15 and stay on-premises.** The dial plan, the integrations and the endpoints carry over. The work lands in staging, in hypervisor and hardware refresh, and in the testing window. It keeps the estate inside a support horizon without changing how anything is administered, which matters where the team is small.

**Move calling to the cloud.** This is a migration, not an upgrade, and we have written the shape of it in the [CUCM to Webex Calling migration guide](https://trybussolutions.com/cucm-to-webex-calling-migration/). It gets scoped as a call control swap and it is not one: numbering, emergency calling, analog devices, contact center integration and survivability all have to be answered before a platform is chosen. The 30 April 2027 date is a useful forcing function for that decision, not a reason to shorten it.

**Do neither, deliberately.** Sometimes the estate is being replaced for other reasons inside the window and Version 14 is running out its contract in the meantime. That is a legitimate position if it is written down, if the contract is genuinely active, and if somebody owns the risk on the unpatched edge. It stops being legitimate when it is nobody's decision.

Emergency Responder deserves its own line. If CER 14 is what tracks phone location for emergency calls, whatever replaces it has to do that job on day one rather than in a later phase. That obligation does not move with a project plan, and it is one of the items we insist on scoping early in [contact center and calling migrations](https://trybussolutions.com/what-to-scope-before-choosing-a-contact-center/) for regulated environments such as [healthcare](https://trybussolutions.com/healthcare/).

## The Order to Do This In

1. Pull the entitlement records and establish, per cluster and per Expressway pair, whether the licensing is perpetual or on-premises Flex, and whether the contract is active today.
2. If it is Flex, put 7 April 2027 in the calendar as the last day to renew or add, and decide before then rather than on that day.
3. If it is perpetual and the contract lapsed, accept that new coverage cannot be bought, and move the replacement decision forward accordingly.
4. Record the release and service update actually running on each node, since that is now fixed, and flag any node on 14SU4.
5. Inventory the Expressway estate separately, with the security team in the room.
6. Check the hosts against the Version 15 virtual machine requirements before the project is costed.
7. Then choose the destination, with those constraints written down rather than discovered.

Trybus Solutions designs and runs [collaboration and unified communications](https://trybussolutions.com/collaboration-unified-communications/) environments on-premises and in the cloud. We handle the upgrade or the migration as an [implementation and migration](https://trybussolutions.com/implementation-migration/) project, and we provide [managed services and support](https://trybussolutions.com/managed-services-and-support/) for whichever destination you pick.

## Common Questions

**Does the phone system stop working on 30 April 2027?** No. Last date of support is the last day Cisco provides support under contract. The software continues to run. What you lose is the route to a fix, and fixes themselves stopped in April 2026.

**We have an active perpetual contract. Can we renew it when it expires?** No. On the perpetual bulletin the end of service contract renewal date is 7 October 2024. Support under the contract already in force runs to the last date of support, 30 April 2027, and there is no renewal past that.

**Can we upgrade straight from Version 14 to Version 15?** Yes. Cisco supports a direct standard upgrade from Release 12.5 and from Release 14 and its service updates. Releases 10.0 through 12.0 require a migration by way of Prime Collaboration Deployment instead.

**We are on 14SU4. Does anything change?** Yes. Cisco states that upgrades from Release 14SU4 to a destination lower than Release 15SU2 are not supported, which rules out 15 and 15SU1a as targets for that cluster.

**Is Version 15 the long-term destination?** Version 15 is the current on-premises release, and no end-of-life notice for it appears on Cisco's end-of-life listing for the product line. That is absence from the index rather than a published support horizon. Cisco has separately said version 16 is planned for calendar year 2027. Plan Version 15 inside a refresh cycle rather than as a permanent answer.

**We are on Version 12.5. Does this bulletin apply to us?** No, and your position is worse rather than better. Cisco publishes a separate end-of-life bulletin for Version 12.5 of the on-premises calling applications and the associated on-premises Flex subscriptions, announced on 1 March 2023. On the subscription rows of that bulletin, end of software maintenance releases passed on 31 August 2024 and both end of change or renewal and last date of support passed on **31 August 2025**. A Version 12.5 estate is already outside the support window, not approaching it.

## Sources

- [Cisco — End-of-Sale and End-of-Life Announcement for the Cisco Version 14 of On-premises Calling applications (including Cisco Unified Communications Manager), Perpetual](https://www.cisco.com/c/en/us/products/collateral/unified-communications/unified-communications-manager-callmanager/v-14-premises-calling-applications-eol.html)
- [Cisco — End-of-Sale and End-of-Life Announcement for the Cisco Version 14 of On-premises Calling applications and associated On-premises Flex subscriptions](https://www.cisco.com/c/en/us/products/collateral/unified-communications/unified-communications-manager-callmanager/v-14-premises-flex-subscriptions-eol.html)
- [Cisco — End-of-Sale and End-of-Life Announcement for the Cisco Version 12.5 of On-premises Calling applications and associated On-premises Flex subscriptions](https://www.cisco.com/c/en/us/products/collateral/unified-communications/unified-communications-manager-callmanager/v-12-5-on-premises-calling-applications-eol.html)
- [Cisco — Upgrade and Migration Guide for Unified Communications Manager and the IM and Presence Service, Release 15 and SUs: Planning the Upgrade](https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/upgrade/15/cucm_b_upgrade-and-migration-guide_15/cucm_m_planning-the-upgrade-15.html)
- [Cisco — Unified Communications Manager (CallManager) End-of-Life and End-of-Sale Notices](https://www.cisco.com/c/en/us/products/unified-communications/unified-communications-manager-callmanager/eos-eol-notice-listing.html)
- [Cisco — Cisco Live 2026: Advancing Cisco Calling with AI, Hybrid Flexibility and Resilience, 3 June 2026](https://blog.webex.com/collaboration/cisco-live-2026-advancing-cisco-calling-with-ai-hybrid-flexibility-resilience/)

## Keep reading

- [CUCM to Webex Calling Migration](https://trybussolutions.com/cucm-to-webex-calling-migration/) — Migration, 8 min read
- [Cisco BE6000 and BE7000 End of Support Dates](https://trybussolutions.com/webex-calling-upgrade-your-business-edition-to-the-cloud/) — Cloud Calling, 9 min read
- [UCCX End of Life: Two Bulletins, Two Different Dates](https://trybussolutions.com/uccx-end-of-life-dates/) — Contact Center, 8 min read

## Find out which bulletin applies to your estate

Trybus Solutions reads the entitlement, records the version on each node, inventories the Expressway edge and gives you the constraints in writing before a destination is proposed.

Or call [423-633-1817](tel:+14236331817) · [info@trybussolutions.com](mailto:info@trybussolutions.com)