From October 2026 Asterisk 20 accepts security fixes only, and in October 2027 it reaches end of life. Upgrading is not a package swap, so here is an executable path.
Under Asterisk's release policy, 20 LTS entered security-only maintenance in October 2026. From that point no functional defects, compatibility issues or new hardware support return to the branch — only security vulnerabilities are addressed. In October 2027 even that stops.
Plenty of teams are not certain which branch production is running, especially on inherited systems. The direct method is to check the version in the Asterisk CLI and confirm the versions of third-party modules in the module directory. Pay particular attention to channel drivers you compiled yourself — they are usually pinned to a major version and must move with it.
There are three options:
Upgrading Asterisk itself is usually about twenty percent of the effort. The other eighty percent sits around it: dialplan syntax compatibility, field changes in AMI/ARI clients, recording and CDR post-processing scripts, and every custom module. Experience says run two weeks of real traffic in a canary environment before a major upgrade rather than doing feature-point tests.
Nine out of ten upgrade incidents in communications do not happen at the moment of upgrade. They happen in a traffic peak three weeks later.
Step one: freeze configuration changes and put the current config files, dialplans and module inventory under version control. Step two: bring the new version up in an isolated environment with the same configuration and verify four paths — basic calls, transfers, conferencing, recording. Step three: recompile and validate each third-party module. Step four: move one real traffic path across and watch it for a week. Step five: cut over fully, keeping a rollback package.
It sounds plodding, and it is the only way to be back to the old state within ten minutes of something going wrong. For a phone system, being able to roll back matters far more than being current.