Skip to content
Phone Guides

Asterisk paging and intercom paths

Define what the caller should hear and which devices should answer before choosing a paging method. Asterisk calling several SIP endpoints, a phone accepting a vendor-specific auto-answer instruction and a multicast speaker receiving audio are different paths.

Source-reviewed, 19 October 2026. Prepared from the cited documentation. No endpoint auto-answer, speaker or multicast path has been independently tested by Phone Guides. Scope: Asterisk 22 Page application concepts; exact device behaviour needs model/firmware documentation.

Choose the intended path

Path Decision to establish
SIP calls to a paging group Which individual endpoints are called and how they answer
One-way announcement Which participant may transmit audio
Two-way intercom Whether both ends may speak and how the call ends
Multicast paging Which devices/protocol/network scope handle the media

Do not substitute a phone's marketing label for a complete control path. A device may support manual answering, one form of auto-answer or a separate multicast receiver without supporting every other form.

Understand Page's default model

The branch-22 Page reference describes calls to listed destinations and a conference-based paging arrangement. Its options change behaviour, so read the intended mode and timeout before adding it to a route.

This original expression illustrates two already-configured PJSIP destinations:


Page(PJSIP/6001&PJSIP/6002,,15)

It is not a complete dialplan or auto-answer configuration. The destination phones still need to accept/answer the calls under their own supported settings. It does not establish multicast support or grant a phone permission to activate a microphone remotely.

The Asterisk 22 Page() options change the conference behaviour after a destination answers:

Option Documented effect Review before enabling
Default Called channels join muted; the original caller is a speaker Confirm this one-way announcement model matches the intended use
d Makes the audio full duplex Decide whether paged participants may speak back
s Dials a channel only when device state is NOT_INUSE Treat this as a state-based selection rule, not permission control
q Suppresses the beep to the caller Check that the caller still gets a clear indication of page setup
A(file) Plays an announcement to paged participants Confirm the sound file exists and is suitable for the audience

The third argument is a connection-attempt timeout: unanswered page calls are hung up when it expires. It is not a limit on how long an answered page lasts. These controls are documented in the branch-22 Page reference. None of them proves that a phone accepted a vendor-specific auto-answer request.

Verify auto-answer from exact sources

For a named phone, record model, firmware, account, permitted initiator and the documented signalling/settings used to request auto-answer. Use the manufacturer's official configuration guide for that exact path. Do not copy a SIP header from another brand or assume a general alert header has identical meaning everywhere.

If endpoint evidence is absent, keep its support Unknown and describe only the Asterisk side. That still allows a useful general guide without advertising an unproven branded recipe.

Restrict who may page

Keep the paging extension reachable only from the intended internal or application entry contexts. Review includes and group membership. Public callers should not inherit an office-wide announcement route because it happens to be in a shared context.

For two-way intercom, state whether users can decline, mute or terminate the interaction according to the actual device's supported controls. For multicast, establish the network scope and supported device/protocol separately. A successful ordinary unicast call is not evidence for a multicast path.

Reader checks

Inspect the loaded route and selected endpoints. On your own deployment, check the intended group, an unavailable device, a busy device, timeout and caller hangup. Verify which participants can speak and whether each endpoint visibly behaves as the design requires.

Check that unintended callers cannot reach the paging route. Keep announcement levels, device permissions and caller identity tied to the real environment rather than a generic recommended setting. Preserve the previous route/group so a misdirected announcement change can be reversed.

See security, conferencing and NAT/RTP for the related boundaries. Return to Asterisk documentation.