Freeze one disputed interval
Record the intended and observed Asterisk node, installed release, loaded module, conference, BridgeUniqueid, channel Uniqueid, user profile, manager account, class authorization, event filters, transport, connection and reconnect times, raw events, collector-receipt times, parser version, later snapshots and the exact symptom. Redact credentials and participant data.
Classify the earliest gap as wrong node, inactive conference, wrong conference lifetime, module or profile mismatch, denied event class, filter suppression, disconnect gap, parser or clock error, reused identity, disabled talk detection, threshold behavior or a downstream media symptom.
Prove event eligibility before interpreting absence
Confirm app_confbridge and the relevant runtime conference on the same node. Verify that the manager account can receive the documented CALL-class events and that include or exclude filters do not remove ConfBridge event names or target channels. Test the exact authenticated session rather than a broader administrator account.
An absent event can reflect authorization, filtering or connection state. Do not claim that a conference never started, a participant never joined or speech never occurred until event eligibility and continuity are established.
Reconstruct lifecycle with bridge and channel identities
Group start and end by BridgeUniqueid, and group join, leave and talking transitions by conference lifetime plus channel Uniqueid. Do not merge separate conferences solely because they reused the same conference number, caller ID or display name. Preserve collector order without inventing missing events.
Compare the disputed interval with completed ConfbridgeListRooms and ConfbridgeList snapshots on the same node. Joins and leaves between snapshots can legitimately change counts, and a snapshot cannot backfill the exact order of an event gap.
Check talk-detection enablement and thresholds
Identify the actual user profile applied to the participant. talk_detection_events defaults to no; when disabled, missing ConfbridgeTalking events are expected. When enabled, record the effective dsp_talking_threshold and dsp_silence_threshold before changing them.
Background noise can trigger onset, while a short silence threshold can report an end during a natural pause. Tune only in an authorized test conference with representative audio. A detector transition is not proof of speech content, RTP continuity, bidirectional media, audible mixing or endpoint experience.
Separate asynchronous delivery from apparent order
AMI actions and events are asynchronous, and multiple channels can produce interleaved events. Preserve full frames and connection boundaries; use server timestamps only when the deployment has enabled them, otherwise retain collector time as collector evidence. Do not sort solely by conference number or caller ID.
A missing start before a join may be a collector gap rather than an impossible server state. A leave does not prove hangup, and an end does not provide a disconnect cause. Continue to channel, dialplan or media evidence only after the event-collection boundary is sound.
Retest one known sequence and repair the first fault
In an approved window, use one disposable conference and named test participants. Capture a completed idle room snapshot, one conference start, each participant join and leave, the conference end, and—only when explicitly required—talking on and off with the intended user profile. Retain raw frames and final completed snapshots.
Repair only the proven node, module, profile, authorization, filter, transport, reconnect, identity, threshold, parser, timestamp or cache fault. No PBX, module, manager account, credential, session, conference, profile, participant, channel, event stream, packet, audio, speech or live call was inspected or tested.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.