Skip to content
Phone Guides

Asterisk conferencing with ConfBridge

Use ConfBridge to connect conference participants under a defined room and access policy. Treat who may enter, how participants behave and how the room mixes media as separate configuration decisions.

Source-reviewed, 20 October 2026. Prepared from the cited documentation. These examples have not been independently tested by Phone Guides. Scope: Asterisk 22 audio conferencing; no video-client compatibility or measured participant count is claimed.

Separate the four pieces

Piece Decision it represents
Conference identifier Which participants join the same room
Bridge profile Room-wide media and bridge settings
User profile Behaviour of an individual participant
Conference menu DTMF actions available to a participant

The upstream ConfBridge concepts explain these relationships. For the current branch, use the application reference rather than assuming room identifiers must contain only digits.

Make profiles explicit

This example separates the shared bridge settings, participant permissions, moderator permissions and their DTMF menus in confbridge.conf:


[pg-bridge]
type=bridge

[pg-participant]
type=user

[pg-moderator]
type=user
admin=yes

[pg-participant-menu]
type=menu
*1=toggle_mute
*2=leave_conference

[pg-moderator-menu]
type=menu
*1=toggle_mute
*2=leave_conference
*3=admin_toggle_conference_lock
*4=admin_kick_last

It relies on the installed version's defaults for omitted options. Read and choose those defaults deliberately before deploying a room. The branch-22 module reference describes the profile options and version additions. A parameter shown in an evolving branch reference may require a later patch within that branch.

A separately controlled internal dialplan route can call those profiles. The moderator route must have its own admission control; an extension number or conference name is not a password.


[pg-conference-access]
exten => 7600,1,Answer()
 same => n,ConfBridge(pg-office-room,pg-bridge,pg-participant,pg-participant-menu)
 same => n,Hangup()
exten => 7601,1,Answer()
 same => n,ConfBridge(pg-office-room,pg-bridge,pg-moderator,pg-moderator-menu)
 same => n,Hangup()

The Asterisk 22 [ConfBridge() reference](https://docs.asterisk.org/Asterisk_22_Documentation/API_Documentation/Dialplan_Applications/ConfBridge/) defines the four arguments and warns against mixing bridge profiles in one room. The branch-22 [app_confbridge reference](https://docs.asterisk.org/Asterisk_22_Documentation/API_Documentation/Module_Configuration/app_confbridge/) documents the menu actions. The moderator-only actions require the user profile's admin=yes; putting an admin action in a menu alone does not make an ordinary participant an administrator. The example has no PIN and does not authenticate callers. Limit each route to its intended users or add a separately reviewed admission step before external use.

Decide access and lifetime

Record whether participants require authentication, a conference PIN, a moderator or a restricted inbound path. Decide whether people wait before the moderator joins, what happens when the moderator leaves, and which roles may mute, remove or invite others. Select documented user/profile options for those exact choices.

Keep recording disabled unless it is deliberately configured with appropriate access, storage and applicable requirements addressed. Do not infer a legal recording permission from the fact that the software offers a recording option.

Reader checks for the room

Inspect loaded profiles and dialplan errors using the CLI help available on your installation. In your own checks, join two intended participants and confirm each can hear the other, then verify join/leave behaviour and the configured admission rules. Check that an unauthorised route cannot enter the room. If menus or moderator roles are added, exercise each permission separately.

Do not advertise a participant limit based on an old hardware table. Codec mix, resampling, bridge settings, enabled features and host resources affect the workload. Measure the actual deployment before making a performance claim. Audio success also does not establish video interoperability; older upstream conceptual pages contain historical client observations that need their own present-day evidence.

For problems, separate admission, media and resource symptoms rather than changing all profiles together. Use NAT and RTP for the media path and backup planning to retain profile configuration. Return to Asterisk documentation.