Skip to end of metadata
Go to start of metadata




Asterisk 12 and Later


This content only applies to Asterisk 12 and later.

In Asterisk 12, a new core component was added to Asterisk: the Stasis Message Bus. As the name suggests, Stasis is an internal publish/subscribe message bus that lets the real-time core of Asterisk inform other modules or components – who subscribe for specific information topic – about events that occurred that they were interested in.

While the Stasis Message Bus is mostly of interest to those developing Asterisk, its existence is a useful piece of information in understanding how the Asterisk architecture works.

On This Page

Key Concepts

The Stasis Message Bus has many concepts that work in concert together. Some of the most important are:


A Publisher is some core component that wants to inform other components in Asterisk about some event that took place. More rarely, this can be a dynamically loadable module; most publishers however are real-time components in the Asterisk core (such as the Channel Core or the Bridging Framework).


A Topic is a high level, abstract concept that provides a way to group events together. For example, a topic may be all changes to a single channel, or all changes to all bridges in Asterisk.


A Message contains the information about the event that just occurred. A Publisher publishes a Message under a specific Topic to the Stasis Message Bus.


A Subscriber subscribes to a particular topic, and chooses which messages it is interested in. When the Stasis Message Bus receives a Message from a Publisher, it delivers the Message to each subscribed Subscriber.


Some Messages - particularly those that affect core communications primitives in Asterisk (such as channels or bridges) are stored in a special cache in Stasis. Subscribers have the option to query the cache for the last known state of those primitives.


Example: Channel Hangup

Stasis Bus Copy


Prior to Asterisk 12, various parts of the real-time core of Asterisk itself would have been responsible for updating AMI, the CDR Engine, and other modules/components during key operations. By decoupling the consumers of state (such as AMI or the CDR Engine) from the producer (such as the Channel Core), we have the following benefits:

  • Improved Modularity: the logic for AMI, CDRs, and other consumers of state is no longer tightly coupled with the real-time components. This simplifies both the producers and the consumers.

  • Insulation: because the APIs are now based on the Stasis Message Bus, changes to other parts of the Asterisk core do not immediately affect the APIs. The APIs have the ability to transform, buffer, or even discard messages from the message bus, and can choose how to represent Asterisk to their consumers. This provides increased stability for Asterisk users.

  • Extensibility: because real-time state is now readily available over the message bus, adding additional consumers of state becomes much easier. New interfaces and APIs can be added to Asterisk without modifying the Asterisk core.

  • No labels


  1. Hi, thanks for the docs! But I can't see the example diagram, it says:

    "Gliffy Macro Error

    You do not have permission to view this diagram."

    1. I don't think anyone reads this bit down here, so I've logged a ticket at  ASTERISK-27611 - Giffy charts embedded in the Wiki now give an error Closed

      1. But they certainly respond to tickets helluva fast! Thanks for fixing this so quickly, Joshua!

      2. Well, somebody should.

        1. Confluence doesn't make it easy to keep track of all the comments and sort through them, unless you are actively watching a page. In this case as I was editing this page I'm now watching it and get emails as a result of these comments. JIRA issues automatically generate an email for every action (filing, comments, transitions, etc) to a mailing list so keeping on top of them is much easier.