FreePBX conference administration

Define who may join

A conference bridge is a shared destination, not merely a phone’s local three-way calling function. Identify whether participants are internal staff, invited external callers or both. Choose a meeting number and participant access method separate from any moderator privilege.

A publicly reachable bridge can consume trunks and processing capacity even when no legitimate meeting is running. Keep its route and credentials under the same ownership discipline as ordinary extensions.

Configure the meeting behavior

Use the Conferences application to set the conference number, available participant and administrator options, and the destination callers use to reach it. The installed module and Asterisk version determine the available controls. Apply the configuration and test with a small internal meeting first.

Decide what should happen before the moderator arrives, how callers hear join and leave events, and whether recording is appropriate. Do not assume a phone’s conference button exercises the server-side bridge you just configured.

Test a full meeting lifecycle

Have one participant enter first, then the moderator, then an external participant. Check microphone mute, DTMF menu actions, double-talk and participant removal where configured. End the meeting and confirm the bridge does not retain unintended callers.

For one participant with bad audio, isolate that participant’s media leg before changing the whole conference. A codec or microphone problem on one endpoint is different from bridge capacity exhaustion.

Operate and retire access

Rotate shared meeting credentials when the audience changes and remove obsolete public routes. Count external participants against trunk capacity and measure the bridge under expected load. Pair recording decisions with recording policy, retention and access controls.