Skip to content
Phone Guides

Choose an Asterisk version and installation method

Choose who will maintain the installation before choosing its commands. A distribution package, a source build and a managed PBX product have different update owners. Mixing their instructions can leave you with binaries, modules and configuration from different releases.

Source-reviewed, 20 October 2026. Prepared from the cited documentation. Installation examples have not been independently tested by Phone Guides. This series uses Asterisk 22 as a reference branch, not a claim that it is the newest available version.

Select a release branch deliberately

Check the official lifecycle table and downloads page together. Record the branch, exact release and source of updates. An old supported branch may have fewer remaining maintenance years than a newer one; an available archive download may already be outside support.

On 20 October 2026, the downloads page identified Asterisk 22.11.0 as the latest LTS and 23.5.0 as the current standard release. The all-versions page lists Asterisk 20.21.0 and Certified Asterisk 22.8-cert4. The Asterisk news page announced Certified Asterisk 20.7-cert12 on 19 October, while the all-versions page still lists 20.7-cert11. Its test-release list and the upstream release page show 20.22.0-rc2, 22.12.0-rc2, 23.6.0-rc2 and 24.0.0-rc2; these are release candidates, not final releases. The lifecycle table lists 24 as an LTS branch but marks it Pre-release, while the downloads page still names 22.11.0 as latest LTS. Keep the reference branch at 22 until a final 24 release is announced and listed as available.

The lifecycle table dates Asterisk 20's security-only period from 19 October 2026 and its EOL to 19 October 2027; it dates Asterisk 23's security-only period from 15 October 2026 and its EOL to 15 October 2027. Yet it labels both branches Fully Supported. The Asterisk 21 row has a similar mismatch: its EOL date is 18 October 2026 while its status still says Security Fix Only. Treat these current-status labels as stale until the project reconciles them with its dated release notices. Asterisk 22 is listed as fully supported until its security-only date of 16 October 2028, with EOL on 16 October 2029. Recheck upstream at installation time; these dates do not establish a distribution's package maintenance.

For an existing system, run this read-only command from a shell account allowed to access the Asterisk control socket:


asterisk -rx 'core show version'

Record the package revision too if the distributor adds patches. A branch number alone does not identify every fix or build option. The CLI reference explains how to distinguish shell and Asterisk commands.

Compare installation ownership

Path Suitable reason to choose it What you must record
Distribution package You want the distributor to supply dependency and service integration OS release, repository, package version and distributor maintenance policy
Source build You need control of the selected Asterisk release and build options Release tag/archive, dependencies, build options, runtime account and update procedure
Managed PBX product You want the product to manage configuration and related services Product version, its supported Asterisk versions and its backup/update process

The official source installation overview describes the build path. The downloads page's FreePBX section identifies FreePBX as a management option. Neither establishes that an arbitrary OS repository contains the same release as upstream.

Match documentation to the running system

Use the Asterisk 22 API reference for this series' option and application checks. For the current upstream release list, see Asterisk Downloads and All Asterisk Versions; the latter distinguishes final releases from test builds. If your system is on another branch, open its corresponding reference and compare upgrade notes before applying a setting. Also confirm that the required modules are present.

Historical documentation remains useful for concepts, but some names describe removed components. For example, Asterisk 21's changes record removal of chan_sip and app_macro. Our current call examples use PJSIP. An old sip.conf recipe cannot be made current by renaming the file to pjsip.conf.

Make the next change recoverable

For a new installation, record the chosen path in the system notes before adding phone accounts. For an existing installation, identify its maintainer and configuration owner first. Do not run a source installation over a package-managed or product-managed PBX as an incidental troubleshooting step.

Keep a copy of the version information, configuration ownership and update source with your recovery records. You should be able to answer who supplies a security fix and how you would return to the previous working installation.

Next: installing Asterisk. Return to Asterisk documentation.