Issue 021 · Independently publishedFriday, 20 November 2026Open Communications · Technology Watch

AsteriskASTERISKCOMMS WATCH

Brand feature · About Asterisk

Asterisk: turning a single server into a phone system

An open-source communications framework that started in 1999, now maintained by Sangoma. Every call becomes a programmable event.

If you have ever used a free office phone system, dialled through a company's voice menu, or waited in a support queue, there is a good chance Asterisk was running underneath. It is a software PBX that runs on ordinary servers and implements voice, video, messaging, conferencing and fax entirely in software, with no dedicated switch hardware required.

What it actually is

Asterisk describes itself as an open-source communications framework rather than a plain telephone switch, and the distinction matters. A switch only connects and disconnects calls. Asterisk breaks every call into events that a program can control — who is calling, which queue they landed in, how long it rang, who picked up, whether the call is recorded, whether it goes to voicemail — all of it can be driven from code.

Under the hood there are four layers: channel drivers that handle signalling (chan_pjsip is the workhorse today), codec and bridging modules that handle media, the dialplan that carries business logic, and the interfaces that expose all of it to the outside world (AMI, ARI, AGI). Stack those four together and you get a communications middleware you can reshape at will.

Asterisk's real value is not that it can make calls. It is that a call becomes something you can write as code.

Twenty-five years of history

In 1999 Mark Spencer wrote the first version of Asterisk because he needed a phone system for his own company and found commercial PBX quotes absurd. He then founded Digium and commercialised the software — maintaining the community edition while selling hardware cards and support. That open-core plus commercial-services structure became a template for countless infrastructure projects since.

Read the full brand profile →

Origin1999 · Mark Spencer
MaintainerSangoma
LicenceGPLv2 onward
Current standard23.x
T H I S I S S U E · L A T E S T S T O R I E S
Product & Technology

Asterisk 23 settles into maintenance: where this generation put its weight

From 23.0 through a year of point releases, the emphasis has not been new features but hardening the PJSIP stack, the WebRTC channel and media handling.

Industry News

AstriCon 2026 lands in Pasadena: the community moves back to the West Coast

On 5–6 March 2026, AstriCon takes place at the Pasadena Convention Center in California, sharing a venue with SCALE, the largest open-source event in Southern California.

2026-11-12 · Community Watch · approx. 5 min read
Releases

Asterisk 20 goes security-only: how to plan the upgrade

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.

2026-10-28 · Operations Notes · approx. 7 min read
Brand Story

From a garage to Sangoma: twenty-six years of the Asterisk business

A program written to avoid a phone bill ended up as part of global communications infrastructure. Its history contains almost every classic question about commercial open source.

2026-10-15 · Editorial Desk · approx. 8 min read
Product & Technology

PJSIP, IAX2 and WebRTC: choosing between Asterisk's three protocol paths

One system, three protocols, three different problems. The cost of choosing badly is rarely 'it does not work' — it is debugging with no idea where to look.

2026-09-30 · Engineering Desk · approx. 7 min read
Use Cases

From IVR to call centre: six ways Asterisk actually gets deployed

The same kernel grows into completely different shapes across six scenarios. Understanding the shapes is more useful than memorising configuration parameters.

2026-09-16 · Solutions Desk · approx. 8 min read
Product & Technology

ARI and AMI: two ways to wire Asterisk into your business systems

One is event-driven, one is control-driven. Picking the wrong interface raises no error, and becomes an unmaintainable debt six months later.

2026-08-26 · Engineering Desk · approx. 6 min read