Asterisk ConfBridge

Three configuration decisions

ConfBridge joins channels into a server-side audio conference. A bridge profile describes shared conference behavior, a user profile describes a participant’s behavior, and a menu maps participant actions. Keep these responsibilities separate when reading an example configuration.

Choose who may create or join a room and whether a marked or administrative participant is required. A room number is not a secret access control if an untrusted caller can dial it.

Build a controlled dialplan entry

Use a dedicated context and a test room. Select the intended bridge, user and menu profiles explicitly in the ConfBridge application call. Check the loaded application help with core show application ConfBridge on the running Asterisk 22 system; adapt options to that installed build.

Never route arbitrary external digits directly into privileged conference rooms. Limit reachability at the dialplan boundary and protect any management API used to mute, remove or list participants.

Verify the lifecycle

Join two test endpoints, speak in both directions and test the selected menu controls. Add a moderator and confirm behavior when that participant leaves. Inspect active rooms and channels rather than equating a successful SIP answer with correct conference membership.

Test a caller with a different codec and observe processing capacity under expected load. Mixing and transcoding have resource costs; the carrier channel count alone does not size the bridge.

Diagnose one participant first

When only one participant has bad audio, compare that channel’s negotiated media and endpoint before changing the bridge profile. Use call-leg evidence and keep conference recordings protected under the same retention policy as ordinary calls.