Skip to content
Phone Guides

Asterisk architecture: channels, dialplans and bridges

A useful way to read an Asterisk configuration is to ask three questions: how does a call enter, which instructions can it run, and what connects its participants? Answer those separately before changing a phone account or route.

Source-reviewed, 18 October 2026. Prepared from the cited documentation. Examples have not been independently tested by Phone Guides. This guide describes Asterisk 22 concepts using PJSIP terminology.

Follow a call between two phones

Consider an office account named 6001 calling account 6002. The account configuration describes each endpoint; an active conversation creates channel instances. Asterisk takes the incoming channel into a dialplan context, finds the dialled extension and runs its instructions. A Dial() instruction can create another channel towards the destination. When connected, a bridge can join the participants.


Phone 6001
    |
Incoming PJSIP channel
    |
Dialplan context and extension
    |
Dial() creates an outgoing PJSIP channel
    |
Phone 6002

Connected participants can be joined in a bridge.
The actual media path depends on the configuration.

This original sketch describes relationships, not a packet trace or a promise that every call has exactly two channels. Transfers, Local channels and conferences can create different arrangements. The upstream channels reference explains channel creation and direction; its historical SIP/ examples should not be copied into a new PJSIP configuration.

Keep these objects distinct

Object Question it answers Common confusion
Endpoint configuration How should Asterisk handle this SIP peer? An endpoint is not an active call
Contact Where can a registered device currently be reached? A contact does not prove two-way audio
Channel What is happening on this communication leg? One business call may involve several legs
Dialplan context Which instructions are available from this entry point? A context name alone does not make a route private
Application Which operation should run at this step? An application can affect routing without being a separate external program
Bridge Which channels are connected together? A bridge is not the same object as the dialplan extension

See the official bridge explanation for creation and lifetime, and PJSIP object relationships for configuration objects.

Signalling and media need separate checks

SIP messages establish and change sessions. Audio usually travels as RTP or a protected media form negotiated by the participants. Successful ringing therefore does not prove that audio can travel through the firewall. A private address in session information can explain an audio failure even while SIP messages arrive.

The protocol distinction is described by RFC 3261 and RFC 3550. Whether Asterisk remains in the media path depends on the call and settings; use the PJSIP NAT guide for that topology.

Configuration, modules and management

Plain-text configuration is one possible source of settings. Some deployments obtain configuration from databases or a management product. Modules supply channel drivers, applications, functions and other services. Finding a setting in a reference does not prove its module was built or loaded on your system.

When diagnosing a failure, first find the channel and context involved. Then check the relevant application, endpoint and contact. If the call connects but audio fails, examine the negotiated media addresses and codec. If an external application controls the call, include that application's events and logs in the investigation.

Continue with version choices or files and CLI. Return to Asterisk documentation.