Asterisk 24 LTS: What Changed and How to Upgrade a Production Call Centre
Asterisk 24 is the next LTS, supported to October 2031: what changed since 22 and 20, the support dates, and how to upgrade a production call centre.
Usama Munawar9 min read

The short version
Asterisk 24 is the new long-term support (LTS) release. The final 24.0.0 was tagged on 5 November 2026, after four release candidates (the last on 29 October).
Three things matter if you run a call centre on Asterisk:
- Asterisk 20 moved to security fixes only on 19 October 2026 and reaches end of life on 19 October 2027. Asterisk 21 reached end of life on 18 October 2026. If you are on either, start planning now.
- Most of the new features in 23 and 24 were also backported to 22 and 20. The real difference between 22 and 24 is a set of removals (users.conf, DeadAGI, a few old functions and options) and a longer support window.
- Asterisk 22 is still fully supported until October 2028. There is no rush to leave it. If you are on 20, going straight to 24 buys you the most time, but it also means crossing the big Asterisk 21 removals (chan_sip, app_macro, res_monitor).
Is Asterisk 24 out yet?
Yes. 24.0.0 was tagged on 5 November 2026 and is a normal, non-pre-release build on the official GitHub releases page; the Asterisk Versions page on docs.asterisk.org lists 24.x as fully supported with that release date. It slipped three weeks from the 15 October date the project had planned, which is common for the first LTS build of a year.
The release candidates were small. RC2 (8 October) fixed ChanSpy bridging and PJSIP presence and dialog-info notifications. RC3 (22 October) was a single fix. RC4 (29 October) fixed two regressions that also exist in 22.11.0: park slot hints stuck at Unavailable after startup, and a segfault when a hint loses its presence part. If your dialplan leans on hints, parking or BLF, read those two issues (#2249 and #2257) before you upgrade.
My advice for a production call centre: 24.0.0 is a fine target for staging today. Move production after you have run it through a full week of real call patterns, and ideally once the first point release (24.0.1) is out. Point releases arrive roughly every four to six weeks.
Support timeline
These dates come from the Asterisk Versions page. LTS releases get four years of full support plus one year of security fixes; standard releases get at least one year of full support plus one year of security fixes. After end of life, a branch gets nothing.
| Version | Type | Released | Security fixes only from | End of life |
|---|---|---|---|---|
| 20 | LTS | 19 October 2022 | 19 October 2026 | 19 October 2027 |
| 21 | Standard | 18 October 2023 | 18 October 2025 | 18 October 2026 |
| 22 | LTS | 16 October 2024 | 16 October 2028 | 16 October 2029 |
| 23 | Standard | 15 October 2025 | 15 October 2026 | 15 October 2027 |
| 24 | LTS | 5 November 2026 | 15 October 2030 | 15 October 2031 |
The 24 row is the project's published schedule: although 24.0.0 shipped on 5 November, the support dates are still counted from 15 October.
Asterisk 23 was a standard release and is already security only. I would not plan a production move to 23 now: 24 contains everything in it and is supported for four years longer.
What actually changed between 22 and 24
I compared the release branches directly. Since the 22 branch was cut, almost every new feature that landed on the main branch was also cherry-picked into the 22 and 20 branches. So if you keep 22 patched, you already have most of what is "new in 24". The changes you only get by moving up are the removals made for Asterisk 23.
Removed in Asterisk 23 (and therefore gone in 24)
From the Asterisk 23.0.0 upgrade notes:
- users.conf is gone. Every channel driver must be configured through its own file, and the res_phoneprov settings moved to
phoneprov_users.conf. - DeadAGI is gone (deprecated since Asterisk 15). Use
AGI(), which handles the same cases. - VALID_EXTEN is gone. Use
DIALPLAN_EXISTS. - QUEUE_MEMBER_COUNT is gone. Use
QUEUE_MEMBER(<queue>,logged). - Music on hold: the old
randomoption and therflag onapplication=are gone. Usesort=random. - Voicemail:
maxmessageandminmessageare gone (usemaxsecsandminsecs), and theczlanguage code is gone (usecs). - Logger:
rotatetimestampis gone. Userotatestrategy. - CLI:
no debug channelis gone. Usecore set debug channel.
In dialplan terms, the fixes look like this:
; Before (fails on 23 and 24)
same => n,GotoIf($[${VALID_EXTEN(sales,${EXTEN},1)}]?known)
same => n,Set(AGENTS=${QUEUE_MEMBER_COUNT(support)})
; After
same => n,GotoIf($[${DIALPLAN_EXISTS(sales,${EXTEN},1)}]?known)
same => n,Set(AGENTS=${QUEUE_MEMBER(support,logged)})
; musiconhold.conf
[default]
mode=files
directory=moh
sort=random ; replaces random=yes
A config behaviour change worth testing
Two changes in 23 affect configs that use templates. When a module looks up a setting by name, it now gets the value that overrides the template, not the template's value. And when a setting is updated (through AMI, for example), the change now applies even if the section inherits from a template. The upgrade notes say breakage is unlikely, but if your configs lean heavily on templates, or your application edits config files through AMI, test that on staging.
Coming from Asterisk 20: the Asterisk 21 removals
If you are jumping from 20, you also cross everything Asterisk 21 removed. The ones that hit call centres:
- chan_sip is gone. Every trunk and phone has to be on PJSIP.
- app_macro is gone. Dialplan has to use
Gosubinstead ofMacro. TheQueue()argument order also shifted when the macro argument was removed, so check anyQueue()call that passes a gosub. - res_monitor is gone, along with the
wandWoptions ofQueue(). Call recording has to useMixMonitor. - NoCDR, ImportVar, SetAMAFlags, chan_skinny, chan_mgcp and chan_alsa are gone too.
For most older call centres, the chan_sip to PJSIP move is the real project; the Asterisk upgrade itself is the smaller part. I covered how the Asterisk and application layers fit together in Asterisk + Laravel call centre.
Newer features you may already have
These arrived during the 23 and 24 cycle and were backported, so check the version, not the major number:
- chan_websocket, a channel driver that sends call media over a websocket, also usable with ARI external media (from 20.16.0 and 22.6.0). This is the simplest route for streaming audio to an AI service; I wrote about that in AI voice agents on Asterisk.
- ARI REST requests over the same websocket used for events (from 20.14.0 and 22.4.0).
- PJSIP endpoint maintenance mode (
res_pjsip_maintenance, from 20.20.0 and 22.10.0): new calls to or from an endpoint are refused while calls in progress carry on. - Per-endpoint RTP port ranges with
rtp_port_startandrtp_port_end(from 20.20.0 and 22.10.0), useful for firewall rules per trunk. - The internal web server's
/httpstatuspage is now off by default (a security fix, from 20.18.2 and 22.8.2). Setenable_status=yesin http.conf if you relied on it.
Should you move to 24, or stay on 22?
- On 20 or 21: yes, plan it now. 21 is out of support and 20 is security only. Go to 24 once it is GA, or to 22 if your distribution does not support 24 yet.
- On 22: no hurry. Keep taking 22.x point releases and plan 24 for a quiet period in 2027. You lose nothing by waiting for 24 to settle.
- On FreePBX: Sangoma's FreePBX 17 documentation says it ships with Asterisk 22 by default. I could not find an official statement about Asterisk 24, so check your distribution's support before upgrading Asterisk underneath it.
How I would plan the upgrade
1. Take an inventory
Before touching anything, I record what is running and search the config for anything removed:
asterisk -rx "core show version"
asterisk -rx "module show" > modules-before.txt
asterisk -rx "pjsip show registrations" > registrations-before.txt
# Removed in 23
grep -rnE 'VALID_EXTEN|QUEUE_MEMBER_COUNT|DeadAGI|rotatetimestamp|maxmessage|minmessage' /etc/asterisk/
grep -rnE '^\s*random\s*=' /etc/asterisk/musiconhold.conf
ls -l /etc/asterisk/users.conf
# Removed in 21 (only if coming from 20)
grep -rnE 'Macro\(|,Monitor\(|NoCDR|ImportVar|SetAMAFlags|[(&]SIP/' /etc/asterisk/
Run the same searches over your AGI scripts and any dialplan your application generates or stores in a database. That is where old function names tend to hide.
2. Build a staging box
Same operating system, same Asterisk build options, a copy of the real config, and a test trunk or a second account on the same carrier. Build from source or packages exactly as you will in production, so the module list matches.
3. Test the call paths that make money
I test the flows the business depends on, not just "a call connects":
- Inbound to IVR, queue and agent, including queue announcements and position messages.
- Outbound campaigns, including the dialer's AGI or ARI calls and caller ID.
- Call recordings: a file is written, has audio on both legs, and lands where your application expects it.
- SIP trunk registration and failover to the backup trunk.
- Codecs: confirm what is negotiated with each trunk and phone type, and listen for one-way audio.
- AMI and ARI clients: logins, the events you consume, and the actions your CRM sends.
- CDR, CEL and queue_log rows: your reports read them, so check they still arrive with the fields you expect.
4. Update the database schema if you use realtime
If your PJSIP or queue configuration lives in a database, the alembic scripts need running. Recent releases add columns (per-endpoint RTP ports, PJSIP taskpool options) and change others:
cd contrib/ast-db-manage
cp config.ini.sample config.ini # then set sqlalchemy.url
alembic -c config.ini upgrade head
One to schedule carefully: a new revision widens the queue_log time column to microseconds on MySQL and MariaDB. The upgrade note says it rewrites the table and blocks queue_log writes while it runs, which on a large table means a maintenance window. PostgreSQL is not affected.
5. Cut over with a way back
On cut-over day I drain traffic rather than dropping it. If the old server has res_pjsip_maintenance loaded, it can refuse new calls while existing ones finish:
asterisk -rx "pjsip set maintenance on all"
asterisk -rx "core show channels count"
Maintenance state is held in memory only and clears on restart. For rollback, keep the old server, or a snapshot of it, untouched until the new one has run a full business day, and know exactly which DNS record, trunk IP allow-list or carrier setting you would switch back.
Upgrade checklist
- Check whether a 24.0.1 has followed 24.0.0 (5 November 2026), and read its changelog.
- Check your distribution or FreePBX supports 24; if not, target 22.
- Read the upgrade notes for 23.0.0 and every 24 release you will cross.
- Run the inventory searches and fix removed functions, options and users.conf.
- Coming from 20: finish chan_sip to PJSIP, Macro to Gosub, Monitor to MixMonitor first.
- Build staging, run the call path tests, check recordings, codecs and trunk failover.
- Run alembic on a copy of the database; time the queue_log change.
- Back up
/etc/asterisk, the database, AGI scripts and sounds. - Cut over in a quiet window, drain calls, keep the old server for rollback.
- Watch registrations, channel counts and error logs for the first few days.
If you are still weighing up whether to run Asterisk at all, Asterisk vs Twilio covers the cost side, and the free call center cost calculator runs the numbers for your own volume.
Need a hand?
Planning an Asterisk upgrade, or moving off chan_sip and macros? See VoIP and Asterisk, or email devusamaworks@gmail.com or WhatsApp +92 303 8004684 for a free 30-minute call.
A question about this article?Ask me on WhatsApp

