Freeze one caller and one disputed sequence
Record the Asterisk node and release, module state, call time, channel identity, conference name, exact ConfBridge() arguments, generated dialplan, resolved bridge, user and menu profiles, dynamic CONFBRIDGE() writes, endpoint and channel DTMF mode, pressed sequence, prompt expected and heard, action expected and observed, lifecycle events and final CONFBRIDGE_RESULT. Redact credentials and participant data.
Classify the earliest fault as wrong dialplan branch, wrong profile or fallback, stale dynamic option, DTMF not received, partial or ambiguous sequence, unauthorized action, suppressed or missing prompt, failed dialplan excursion, conference state change or misunderstood exit result.
Prove the effective profiles before changing media
Inspect the generated and custom dialplan that reached the application and preserve empty positional arguments. A blank profile argument can select a dynamic channel profile and then default_bridge, default_user or default_menu; it does not mean the feature is disabled. Confirm the section type and exact case-sensitive name in the configuration used by the running process.
For dynamic profiles, preserve template and option writes in execution order and verify whether clear ran on the same channel. Do not mix bridge profiles in one runtime conference to test alternatives: the documentation calls that undefined. Recreate a new disposable room for a bridge-profile comparison.
Follow the digit into the menu matcher
Confirm the endpoint and active PJSIP channel DTMF mode, then capture whether Asterisk received the intended digits once and in order. The current res_pjsip reference distinguishes RFC 4733, in-band, SIP INFO, automatic and disabled modes, while PJSIP_DTMF_MODE() reads or changes the active SIP call mode. Preserve negotiation and received frames rather than treating an endpoint setting as receipt proof.
After receipt, compare the complete collected sequence with the effective menu. playback_and_continue is expected to stop its prompt when DTMF arrives while continuing sequence collection. A cut-off menu prompt can therefore be expected behavior, not an audio failure.
Check role, state and prompt ownership
For lock, participant mute and kick-style menu actions, verify that the user profile is marked admin where the documented action requires it. For join and leave announcements, inspect quiet; for waiting and end behavior, inspect marked-user options; for a per-user announcement, inspect the filename and channel language.
Verify the sound package, resolved file, supported format, file access and playback result on the affected node. The official prompt list describes the current English core package. Do not substitute a filename, language label or successful local file read for audible delivery to the caller.
Correlate the action, conference change and return
Preserve evidence for the matched menu action, any temporary dialplan_exec, lifecycle or moderation event, completed room or participant snapshot and the application return. Concurrent admin actions, marked-user departure or another participant leaving can change conference state after the caller presses a key.
Read CONFBRIDGE_RESULT on the same channel immediately after return. DTMF identifies a DTMF exit from the application, not every menu key; ENDMARKED, KICKED, HANGUP, TIMEOUT and FAILED have separate documented meanings. None proves media quality or a complete endpoint outcome.
Repair the first proven boundary and retest
Correct only the demonstrated dialplan, profile fallback, dynamic option order, DTMF mode, sequence, role, prompt asset, language, file access, dialplan target or result-handling defect. Preserve the previous state and use a new disposable room when changing bridge-profile behavior.
Repeat one known menu sequence and a control call, retaining profile resolution, received digits, prompt behavior, action evidence, application return and later completed snapshots. No PBX, module, dialplan, generated configuration, profile, menu, prompt, sound package, endpoint, channel, DTMF frame, packet, media stream, conference 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.