VoIP.infoThe independent guide to business communications.
VoIP.info Guide

Asterisk AMI command inventory and permission evidence

Use ListCommands and the administrator CLI to distinguish the actions visible to one manager user from the actions registered by the running Asterisk instance.

Reviewed 2026-10-29Asterisk branch-23-generated and branch-22-generated ListCommands references plus official AMI syntax, v2 specification, manager-command, change/versioning, permission, module-loader and network-security documentation reviewed October 16, 2026; installed branch and maintenance release, build, package and module set, manager user, read and write authorizations, session mask, action registration, request framing, parameters, target objects, response, related events and service outcome remain deployment specific; no PBX, module, package, manager user, manager session, request, response, event, configuration file, channel, packet, media stream or live call was inspected or testedAdvancedDocumentation based · not lab tested

Inventory the exact manager session

Record the running Asterisk branch and maintenance release, build and package source, server identity, manager username, transport, connection time and client version. Send a uniquely generated ActionID with Action: ListCommands, retain the complete response and keep credentials out of the record.

ListCommands returns an action name and synopsis for every manager command available to that authenticated user. It is a session-scoped authorization view, not a declaration that every action compiled into Asterisk is visible.

Treat ListCommands as a user-scoped view

Search the returned headers for the exact action name and preserve its published synopsis. A listed action establishes that the current user may see that registered action at that time. It does not establish that particular parameters, object names or downstream service behavior will succeed.

An absent action is ambiguous until another surface is checked. The user may lack the relevant write authorization, the session may use a different account or host, the owning module may not be loaded, or the installed branch, maintenance release, package or build may not register that action.

Compare the administrator-side registry

From an authorized local administrative console, manager show commands lists registered manager actions and manager show command <action> provides action detail. Record the same running process and time window as the manager session. Do not expose the console or its broader command surface to an untrusted client.

If the CLI lists an action that the user-scoped ListCommands response omits, investigate the manager account and its effective manager.conf write classes. If both omit it, investigate branch support, packaging, loaded modules and registration before changing authorization.

Keep availability separate from syntax and targets

AMI messages use Header: value lines and a blank-line terminator. An action message begins with Action; response and event messages begin with their own message types. Preserve the exact action spelling, every supplied header and the raw response instead of treating an SDK constant or documentation example as runtime evidence.

A visible command can still reject an unsupported field, malformed value, unavailable object or unsafe operation. Conversely, an Error response and its optional Message describe this request; they are not a stable cross-version fault taxonomy.

Reconcile version and module boundaries

AMI uses a major, breaking and non-breaking version scheme associated with the corresponding Asterisk major release. Actions may be added during a major line, so an old client library or static allow-list can lag the running instance. Compare the installed branch and maintenance release with the action's generated documentation and the live inventory.

When an owning module is relevant, keep package presence, loaded state, action registration and manager-user visibility as separate checkpoints. Loading or reloading a module is a privileged service change, not the first diagnostic step.

Correlate responses, events and business outcome

The v2 specification defines Response: Success or Response: Error, with an optional Message. Some actions also produce related events. Use the unique ActionID where the action and related events support it, and require the documented completion event or other transaction boundary before declaring an event list complete.

A Success response proves only the action-level contract it documents. Verify the target object and intended operational result separately, retain negative tests where appropriate and grant only the write classes required. No PBX, module, manager session, request, response, event, channel, packet, media stream or live call was inspected or tested for this guide.

Authenticate before interpreting command visibility

The AMI session-authentication guide establishes server, manager identity and connection lifetime before comparing user-scoped commands.

Confirm core-query visibility before parsing values

The core status and settings diagnostic separates action availability and authorization from response-schema or value disputes.

Confirm queue-query visibility before parsing rows

The queue-snapshot diagnostic separates action visibility and authorization from empty filters or incomplete response series.

Confirm mailbox action visibility before interpreting an empty result

The mailbox-query diagnostic separates unavailable or denied actions from wrong context, stale storage and parser behavior.

Confirm the installed voicemail action before parsing

The voicemail-user diagnostic separates unavailable, denied, unsupported and incomplete results.

Check maintenance release before an MWI control

The AMI MWI control diagnostic treats an unavailable version-sensitive action separately from denial or bad state.

Distinguish denied inventory from an empty conference list

The ConfBridge list diagnostic verifies module and permission before interpreting runtime state.

Inventory ConfBridge actions before widening control rights

The ConfBridge control diagnostic uses same-account action inventory before interpreting a failed or unavailable control.

Scope parking write and observation permissions separately

The AMI parking guide distinguishes Park authority from CALL-class event and inventory visibility.

Keep AMI visibility attached to branch and build evidence

A command can be absent because the running branch or build never registered it, or hidden from a user-scoped inventory by authorization. The version/build diagnostic keeps those owners separate.

Inventory Getvar and Setvar for the actual manager user

Use the AMI variable diagnostic to prove action visibility and authority before changing manager permissions.

Inventory AstDB actions for the deployed branch

Use the AMI AstDB diagnostic to prove DBGetTree availability and manager authority before diagnosing data.

Verify the dynamic inbound-registration action exists

The inbound-registration diagnostic checks installed action inventory and manager authority before interpreting an empty result.

Verify endpoint-list actions and event access together

The AMI endpoint-state diagnostic checks deployed actions, manager authority, filters and parser framing before interpreting absence.

Verify AoR-list action and event access together

The AMI AoR-list diagnostic checks deployed action availability, manager authority, filters and completion before interpreting absence.

Verify both contact actions and status-event visibility

The AMI contact-state diagnostic checks action authority, event classes, filters and completion before interpreting silence.

Verify PJSIPShowAuths without broadening manager access

The AMI auth-list diagnostic checks action availability, authority and list completion before interpreting results.

Verify outbound-registration actions before automation

The runtime-control diagnostic checks installed action availability, manager authority and completed list parsing.

Do not invent an all-transport AMI action

The TransportDetail diagnostic verifies documented action scope and terminal framing before automation.

Do not invent an all-identify AMI action

The AMI IdentifyDetail diagnostic verifies action scope, association and completion before automation.

Version-gate PJSIP maintenance actions

The maintenance-mode diagnostic checks release support, modules and manager privilege before endpoint changes.

Inventory voicemail actions before interpreting mailbox state

The AMI voicemail message diagnostic distinguishes an unavailable or denied action from an absent message.

Inventory signalling actions before interpreting a no-effect result

The AMI signalling diagnostic confirms version, module and permission before media or endpoint diagnosis.

Inventory AbsoluteTimeout before interpreting timing

The AbsoluteTimeout diagnostic checks action availability and manager authority before timer or media diagnosis.

Inventory MuteAudio before interpreting silence

The MuteAudio diagnostic checks action availability, module and manager authority before media diagnosis.

Inventory ControlPlayback before media diagnosis

The ControlPlayback diagnostic checks the running action, module and manager authority before interpreting audio.

Let the runtime inventory reject removed Monitor actions

The AMI Monitor diagnostic checks exact version and res_monitor availability before changing permissions or files.

Inventory Hangup without granting Command as a shortcut

The AMI Hangup diagnostic keeps the dedicated action and CLI-equivalent Command authority in separate risk boundaries.

Inventory SendText without broadening manager authority

The AMI SendText diagnostic preserves action availability, permission and channel-driver outcome separately.

Inventory MessageSend without granting broad manager control

The AMI MessageSend diagnostic separates action availability, authority and downstream routing.

Inventory AOCMessage without broad manager authority

The AMI AOCMessage guide limits target, tariff source, message phase and sensitive fields.

Inventory the app_agent_pool surface before control

The AMI agent guide checks Agents and AgentLogoff availability, authority and event classes before relying on them.

Inventory the res_fax manager surface

The AMI fax-session guide checks FAXSessions, FAXSession and FAXStats support before interpreting missing data.

Inventory PJSIPShowResourceLists support

The AMI resource-list guide checks action and event authorization before treating missing rows as configuration evidence.

Inventory both DAHDI snapshot actions

The AMI DAHDI guide checks version and authorization before interpreting missing spans or channels.

Inventory PRI status and debug actions separately

The AMI PRI guide checks support and privilege before using one read action and three debug-control actions.

Interpret missing chan_sip actions against the installed release

The AMI chan_sip migration guide distinguishes expected removal from module and permission failures.

Inventory chan_iax2 actions before interpreting absence

The IAX2 AMI diagnostic separates unknown, denied, unavailable, empty and incompletely framed results.

Inventory bridge-technology controls before interpreting absence

The bridge-technology diagnostic separates unknown, denied, incomplete and completed-empty observations.

Inventory LoggerRotate before interpreting a denial

The LoggerRotate diagnostic separates missing action, manager authorization, acceptance and storage outcomes.

Bound remote debugging commands by authority and impact

The crash and backtrace guide requires an explicit owner and service-impact window for running captures and lock inspection.

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.

Continue your research

Guide · Current Asterisk interface documentation reviewed September 30, 2026; implementation must be checked against the installed branch and integration library

Asterisk AMI, ARI and AGI: choose the control boundary

Separate management events, synchronous dialplan work and application-owned call control before exposing an integration.

Read guide →
Guide · Asterisk branch-23-generated and branch-22-generated ModuleCheck, ModuleLoad and Reload action references plus official module-loader, module-type, AMI-permission and network-security documentation reviewed October 16, 2026; installed branch, package contents, module directory, dependencies, modules.conf policy, active use counts, reload support, registered capabilities, parsed configuration, runtime objects, manager privileges and service outcome remain deployment specific; no PBX, module, package, manager session, configuration file, channel, packet, media stream or live call was inspected or tested

Asterisk AMI module checks, load, reload and refresh

Use ModuleCheck, ModuleLoad and Reload without confusing a loaded shared object with registered features, parsed configuration, durable startup policy or working calls.

Read guide →
Guide · Current Asterisk branch-23-generated Events, Filter, WaitEvent, Login and Ping action references, matching branch-22 Events, Filter and WaitEvent references, the official AMI event-filtering guide and Manager TCP/IP API reviewed October 16, 2026; installed branch, manager user permissions, login mask, static and dynamic filters, connection type, event queue, client parser, reconnect behavior, action concurrency, downstream storage and call activity remain deployment specific; no PBX, AMI session, manager user, permission, configuration file, socket, HTTP session, event queue, channel, bridge, packet, media stream or live call was inspected or tested

Asterisk AMI event delivery, filters and WaitEvent

Trace event delivery through manager read permissions, login and Events masks, configured and session filters, TCP or HTTP transport, WaitEvent queueing and client processing without treating silence as a failed PBX.

Read guide →
Guide · Operational guidance; Asterisk 22 / FreePBX 17 where applicable

Least privilege for PBX users and integrations

Separate the right to register, place calls, administer the PBX and read sensitive data.

Read guide →
Troubleshooting · Asterisk branch-23-generated and branch-22-generated ListCommands references plus official AMI syntax, v2 specification, manager-command, change/versioning, permission, module-loader and network-security documentation reviewed October 16, 2026; installed branch and maintenance release, build, package and module set, manager user, read and write authorizations, session mask, action registration, request framing, parameters, target objects, response, related events and service outcome remain deployment specific; no PBX, module, package, manager user, manager session, request, response, event, configuration file, channel, packet, media stream or live call was inspected or tested

Asterisk AMI action is missing, unknown or permission denied

Trace one unavailable AMI action through session identity, user-scoped inventory, administrator registry, release and module support, authorization, framing and target behavior.

Read guide →
Guide · Asterisk branch-23-generated Login, Challenge, Logoff and Events references, branch-22-generated Login reference, and official AMI syntax, v2, permission and network-security documentation reviewed October 16, 2026; installed branch and maintenance release, listener and transport, manager.conf ownership, username, secret rotation, ACL, read and write classes, login event mask, connection lifetime, client timeout, reconnect policy and downstream operations remain deployment specific; no PBX, manager configuration, credential, ACL, socket, manager session, request, response, event, channel, packet, media stream or live call was inspected or tested

Asterisk AMI session authentication, Login, Logoff and Challenge

Keep manager identity, authentication exchange, transport protection, event mask, permissions and session lifetime as separate AMI evidence.

Read guide →
Troubleshooting · Asterisk branch-23-generated Login, Challenge, Logoff and Events references, branch-22-generated Login reference, and official AMI syntax, v2, permission and network-security documentation reviewed October 16, 2026; installed branch and maintenance release, listener and transport, manager.conf ownership, username, secret rotation, ACL, read and write classes, login event mask, connection lifetime, client timeout, reconnect policy and downstream operations remain deployment specific; no PBX, manager configuration, credential, ACL, socket, manager session, request, response, event, channel, packet, media stream or live call was inspected or tested

Asterisk AMI login fails or the session drops

Trace one failed login or lost manager session through listener identity, protected reachability, framing, authentication fields, manager account policy and the exact termination boundary.

Read guide →
Guide · Asterisk branch-23-generated CoreStatus and CoreSettings references, branch-22-generated references for the same actions, and official AMI syntax, v2 and permission documentation reviewed October 16, 2026; installed branch and maintenance release, server identity, manager transport, account, ACL, read and write classes, action availability, returned fields, clock, restart and reload history, configured limits, runtime load, channels and downstream collector behavior remain deployment specific; no PBX, manager configuration, account, credential, socket, session, request, response, status value, setting, process, channel, packet, media stream or live call was inspected or tested

Asterisk AMI CoreStatus and CoreSettings: separate status from settings

Use the two core-query actions as correlated, node-specific evidence without turning a successful response into proof of call health, configuration ownership or capacity.

Read guide →
Troubleshooting · Asterisk branch-23-generated CoreStatus and CoreSettings references, branch-22-generated references for the same actions, and official AMI syntax, v2 and permission documentation reviewed October 16, 2026; installed branch and maintenance release, server identity, manager transport, account, ACL, read and write classes, action availability, returned fields, clock, restart and reload history, configured limits, runtime load, channels and downstream collector behavior remain deployment specific; no PBX, manager configuration, account, credential, socket, session, request, response, status value, setting, process, channel, packet, media stream or live call was inspected or tested

Asterisk AMI core status or settings is missing, stale or wrong

Trace one core query through node identity, session, framing, action visibility, response correlation, parser behavior and the independent evidence that owns the disputed value.

Read guide →
Guide · Asterisk branch-23-generated and branch-22-generated QueueSummary and QueueStatus action references plus official AMI v2, permission and queue documentation reviewed October 16, 2026; installed branch and maintenance release, app_queue version, server identity, manager transport, account, ACL, read and write classes, queue and member names, dynamic membership, event schema, completion behavior, clock, configuration owner, caller state, member reachability, device state and downstream collector behavior remain deployment specific; no PBX, queue, member, caller, manager configuration, account, credential, socket, session, request, response, event series, completion marker, channel, packet, media stream or live call was inspected or tested

Asterisk AMI QueueStatus and QueueSummary snapshots

Collect queue summaries and detailed status as separate, filtered AMI transactions with explicit correlation and completion boundaries.

Read guide →
Troubleshooting · Asterisk branch-23-generated and branch-22-generated QueueSummary and QueueStatus action references plus official AMI v2, permission and queue documentation reviewed October 16, 2026; installed branch and maintenance release, app_queue version, server identity, manager transport, account, ACL, read and write classes, queue and member names, dynamic membership, event schema, completion behavior, clock, configuration owner, caller state, member reachability, device state and downstream collector behavior remain deployment specific; no PBX, queue, member, caller, manager configuration, account, credential, socket, session, request, response, event series, completion marker, channel, packet, media stream or live call was inspected or tested

Asterisk AMI queue status or summary is missing, stale or incomplete

Trace one queue snapshot through target identity, filters, permissions, response correlation, completion, parser behavior and the queue evidence that owns the disputed fact.

Read guide →
Guide · Asterisk branch-22-generated MailboxCount, MailboxStatus, VoicemailBoxSummary, VoicemailRefresh, MWIGet, MWIUpdate and MailboxStateChange action references plus official VM_INFO, AMI v2 and manager-permission documentation reviewed October 17, 2026; installed branch and maintenance release, action availability, module selection, voicemail backend, mailbox and context identity, folder, external MWI ownership, manager transport, account, ACL, read and write classes, response field behavior, storage freshness, clock, configuration owner, endpoint subscription, phone indicator and downstream collector behavior remain deployment specific; no PBX, mailbox, voicemail store, IMAP account, manager configuration, account, credential, socket, session, request, response, MWI subscription, endpoint, phone, message, playback or live call was inspected or tested

Asterisk AMI MailboxCount and MailboxStatus queries

Query one voicemail mailbox with explicit identity, raw response preservation and a clear boundary between message counts, waiting state and downstream MWI behavior.

Read guide →
Troubleshooting · Asterisk branch-22-generated MailboxCount, MailboxStatus, VoicemailBoxSummary, VoicemailRefresh, MWIGet, MWIUpdate and MailboxStateChange action references plus official VM_INFO, AMI v2 and manager-permission documentation reviewed October 17, 2026; installed branch and maintenance release, action availability, module selection, voicemail backend, mailbox and context identity, folder, external MWI ownership, manager transport, account, ACL, read and write classes, response field behavior, storage freshness, clock, configuration owner, endpoint subscription, phone indicator and downstream collector behavior remain deployment specific; no PBX, mailbox, voicemail store, IMAP account, manager configuration, account, credential, socket, session, request, response, MWI subscription, endpoint, phone, message, playback or live call was inspected or tested

Asterisk AMI mailbox count or status is missing, stale or inverted

Trace one mailbox query through target identity, mailbox context, action availability, permissions, raw field semantics, voicemail-store freshness, response parsing and cache behavior.

Read guide →
Guide · Current Asterisk branch-23-generated and branch-22 VoicemailUsersList and VoicemailUserStatus references, branch-22 VoicemailBoxSummary and MailboxCount references, and official AMI v2 and manager-permission documentation reviewed October 17, 2026; VoicemailUsersList is documented by app_voicemail from Asterisk 1.6 while VoicemailUserStatus is documented by app_voicemail_imap from Asterisk 16, and the generated action pages do not define a shared response schema or make either response proof of message inventory, storage freshness, playback or MWI delivery; installed branch, maintenance release, module, backend, mailbox and context identity, manager permissions, response framing, parser and cache behavior remain deployment specific; no PBX, module, mailbox, voicemail user, store, IMAP account, manager configuration, credential, session, request, response, message, MWI subscription, endpoint, phone, playback or live call was inspected or tested

Asterisk AMI VoicemailUsersList and VoicemailUserStatus evidence

Keep an app_voicemail user-list request, an IMAP-specific single-user status request, mailbox counts and downstream message evidence separate.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated and branch-22 VoicemailUsersList and VoicemailUserStatus references, branch-22 VoicemailBoxSummary and MailboxCount references, and official AMI v2 and manager-permission documentation reviewed October 17, 2026; VoicemailUsersList is documented by app_voicemail from Asterisk 1.6 while VoicemailUserStatus is documented by app_voicemail_imap from Asterisk 16, and the generated action pages do not define a shared response schema or make either response proof of message inventory, storage freshness, playback or MWI delivery; installed branch, maintenance release, module, backend, mailbox and context identity, manager permissions, response framing, parser and cache behavior remain deployment specific; no PBX, module, mailbox, voicemail user, store, IMAP account, manager configuration, credential, session, request, response, message, MWI subscription, endpoint, phone, playback or live call was inspected or tested

Asterisk AMI voicemail user list or status is missing, incomplete or wrong

Trace one list or status request through target identity, module ownership, permissions, raw response framing, mailbox context, parsing and cache behavior.

Read guide →
Guide · Current Asterisk branch-23-generated and branch-22 VoicemailRefresh, MWIGet and MWIUpdate references, the branch-22-generated version-sensitive MailboxStateChange reference, and official AMI v2 and manager-permission documentation reviewed October 17, 2026; the current VoicemailRefresh page is generated under app_voicemail_imap while the branch-22 page is generated under app_voicemail_odbc, MWIGet and MWIUpdate belong to res_mwi_external_ami, and MailboxStateChange is documented for remote mailbox synchronization from specified maintenance releases rather than local mailbox mutation; installed branch and maintenance release, loaded module, mailbox ownership, context, EntityID, manager permissions, response framing, subscription, NOTIFY delivery and endpoint rendering remain deployment specific; no PBX, module, mailbox, voicemail store, IMAP or ODBC backend, manager configuration, credential, session, request, response, subscription, NOTIFY, endpoint, phone, message, playback or live call was inspected or tested

Asterisk AMI VoicemailRefresh and MWI control evidence

Keep a voicemail-backend refresh request, external-MWI count ownership, remote mailbox-state synchronization and endpoint indication as separate controls.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated and branch-22 VoicemailRefresh, MWIGet and MWIUpdate references, the branch-22-generated version-sensitive MailboxStateChange reference, and official AMI v2 and manager-permission documentation reviewed October 17, 2026; the current VoicemailRefresh page is generated under app_voicemail_imap while the branch-22 page is generated under app_voicemail_odbc, MWIGet and MWIUpdate belong to res_mwi_external_ami, and MailboxStateChange is documented for remote mailbox synchronization from specified maintenance releases rather than local mailbox mutation; installed branch and maintenance release, loaded module, mailbox ownership, context, EntityID, manager permissions, response framing, subscription, NOTIFY delivery and endpoint rendering remain deployment specific; no PBX, module, mailbox, voicemail store, IMAP or ODBC backend, manager configuration, credential, session, request, response, subscription, NOTIFY, endpoint, phone, message, playback or live call was inspected or tested

Asterisk AMI VoicemailRefresh or MWI control is unavailable, rejected, broad or wrong

Trace one refresh or MWI control through release, module ownership, mailbox identity, EntityID, permissions, raw response and downstream delivery without changing unrelated state.

Read guide →
Guide · Current Asterisk branch-23-generated and branch-22 ConfbridgeListRooms and ConfbridgeList action references, current list-event references, and official ConfBridge, AMI v2 and manager-permission documentation reviewed October 17, 2026; ConfbridgeListRooms reports active conferences and ConfbridgeList reports participants for one specified conference, each as a multi-event response terminated by its documented Complete event; room presence, participant rows, configured bridge, user and menu profiles, dialplan reachability, admission, media, recording and caller experience remain separate evidence boundaries; installed branch, loaded app_confbridge module, conference identifiers, manager permissions, filters, event ordering and live state remain deployment specific; no PBX, module, manager configuration, credential, session, conference, profile, menu, participant, channel, event stream, recording, packet, audio or live call was inspected or tested

Asterisk AMI ConfbridgeListRooms and ConfbridgeList snapshots

Inventory active ConfBridge rooms and the participants in one room without treating configuration, partial event rows or manager visibility as a working conference.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated and branch-22 ConfbridgeListRooms and ConfbridgeList action references, current list-event references, and official ConfBridge, AMI v2 and manager-permission documentation reviewed October 17, 2026; ConfbridgeListRooms reports active conferences and ConfbridgeList reports participants for one specified conference, each as a multi-event response terminated by its documented Complete event; room presence, participant rows, configured bridge, user and menu profiles, dialplan reachability, admission, media, recording and caller experience remain separate evidence boundaries; installed branch, loaded app_confbridge module, conference identifiers, manager permissions, filters, event ordering and live state remain deployment specific; no PBX, module, manager configuration, credential, session, conference, profile, menu, participant, channel, event stream, recording, packet, audio or live call was inspected or tested

Asterisk AMI ConfBridge room or participant list is missing, incomplete or stale

Trace one ConfbridgeListRooms or ConfbridgeList transaction through node, module, permission, conference identity, complete framing, filtering and live conference state.

Read guide →
Guide · Current Asterisk branch-23-generated ConfbridgeLock, ConfbridgeUnlock, ConfbridgeMute, ConfbridgeUnmute, ConfbridgeKick, ConfbridgeStartRecord and ConfbridgeStopRecord action references, branch-22 lock and recording references, current recording events, and official ConfBridge AMI, CLI and manager-command documentation reviewed October 17, 2026; an accepted manager action, room lock state, participant mute state, participant membership, recording event, generated path, durable file, captured audio and caller outcome remain separate evidence boundaries; installed branch, loaded app_confbridge module, active conference identity, channel names, manager permissions, event policy, recording directory and filesystem behavior remain deployment specific; no PBX, module, manager account, credential, session, conference, participant, channel, lock, mute, kick, recorder, file, packet, audio or live call was inspected or tested

Asterisk AMI ConfBridge moderation and recording controls

Operate ConfBridge lock, mute, kick and recording actions with exact targets, bounded authority and separate response, event, state and outcome evidence.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated ConfbridgeLock, ConfbridgeUnlock, ConfbridgeMute, ConfbridgeUnmute, ConfbridgeKick, ConfbridgeStartRecord and ConfbridgeStopRecord action references, branch-22 lock and recording references, current recording events, and official ConfBridge AMI, CLI and manager-command documentation reviewed October 17, 2026; an accepted manager action, room lock state, participant mute state, participant membership, recording event, generated path, durable file, captured audio and caller outcome remain separate evidence boundaries; installed branch, loaded app_confbridge module, active conference identity, channel names, manager permissions, event policy, recording directory and filesystem behavior remain deployment specific; no PBX, module, manager account, credential, session, conference, participant, channel, lock, mute, kick, recorder, file, packet, audio or live call was inspected or tested

Asterisk AMI ConfBridge control is accepted but state does not change

Trace one lock, mute, unmute, kick or recording request through action availability, exact target, response, event, later snapshot and downstream effect.

Read guide →
Guide · Current branch-23-generated and branch-22 AMI Park, ParkedCalls and Parkinglots action references, current ParkedCall, UnParkedCall, ParkedCallGiveUp and ParkedCallTimeOut event references, branch-22 res_parking and ParkedCall application references, and the AMI v2 specification reviewed October 17, 2026; action acceptance, channel identity, parked-state event, snapshot framing, announcement, slot assignment, retrieval, media, timeout routing and caller outcome remain separate evidence boundaries; installed branch, loaded res_parking module, manager permissions, event filters, generated FreePBX configuration, parking lot, dialplan and endpoint behavior remain deployment specific; no PBX, module, config, manager account, session, parking lot, channel, bridge, event stream, endpoint, packet, audio or live call was inspected or tested

Asterisk AMI parked-call control, snapshots and lifecycle events

Separate AMI parking requests, exact channel and lot identity, parked-call snapshots, lifecycle events, slot assignment, retrieval, timeout routing and caller outcomes.

Read guide →
Troubleshooting · Current branch-23-generated and branch-22 AMI Park, ParkedCalls and Parkinglots action references, current ParkedCall, UnParkedCall, ParkedCallGiveUp and ParkedCallTimeOut event references, branch-22 res_parking and ParkedCall application references, and the AMI v2 specification reviewed October 17, 2026; action acceptance, channel identity, parked-state event, snapshot framing, announcement, slot assignment, retrieval, media, timeout routing and caller outcome remain separate evidence boundaries; installed branch, loaded res_parking module, manager permissions, event filters, generated FreePBX configuration, parking lot, dialplan and endpoint behavior remain deployment specific; no PBX, module, config, manager account, session, parking lot, channel, bridge, event stream, endpoint, packet, audio or live call was inspected or tested

Asterisk AMI parked call is missing, in the wrong slot, times out or retrieves incorrectly

Trace one disputed parked call through exact channel identity, action response, list framing, lot and space assignment, lifecycle reason, retrieval selection, timeout routing and media outcome.

Read guide →
Asterisk · First-party Asterisk lifecycle, release-candidate announcement, change-log and artifact indexes were rechecked October 30, 2026. The versions table still labelled 24.x Pre-release, the project had announced 24.0.0-rc4 on October 29, and the inspected release index exposed rc1 through rc4 without establishing a final 24.0.0 release. Lifecycle labels, scheduled dates, branch documentation, candidate artifacts, downstream packages and an installed runtime remain separate evidence. No host, repository, package channel, artifact, hash, signature, source tree, dependency, build, module, configuration, process, API, endpoint, hint, parked call, packet, media stream or call was inspected or tested

Asterisk release lifecycle: status, branch docs and module availability

Read support labels and scheduled dates as separate evidence, match documentation to the running branch, and trace a feature from source and build selection to loaded capability.

Read guide →
Troubleshooting · First-party Asterisk lifecycle, release-candidate announcement, change-log and artifact indexes were rechecked October 30, 2026. The versions table still labelled 24.x Pre-release, the project had announced 24.0.0-rc4 on October 29, and the inspected release index exposed rc1 through rc4 without establishing a final 24.0.0 release. Lifecycle labels, scheduled dates, branch documentation, candidate artifacts, downstream packages and an installed runtime remain separate evidence. No host, repository, package channel, artifact, hash, signature, source tree, dependency, build, module, configuration, process, API, endpoint, hint, parked call, packet, media stream or call was inspected or tested

Asterisk feature or module is missing after a version or build change

Find the first divergence among branch documentation, source, dependencies, build selection, installed files, load policy, running module state and registered capability.

Read guide →
Guide · Current branch-23 AMI Getvar, Setvar and VarSet references, channel-variable setting and inheritance guidance, global and shared-variable documentation, external-protocol function safeguards and AMI event filtering were reviewed October 19, 2026. Installed branch, manager permissions, channel lifetime, variable namespace, function availability, event selection, dialplan ownership and application outcomes remain deployment specific. No PBX, manager account, session, channel, variable, function, event, dialplan, packet, media stream or live call was inspected or tested

Asterisk AMI Getvar and Setvar: scope, functions and events

Read or write the intended channel, global variable or dialplan function without confusing an accepted manager response, VarSet event or later call outcome.

Read guide →
Troubleshooting · Current branch-23 AMI Getvar, Setvar and VarSet references, channel-variable setting and inheritance guidance, global and shared-variable documentation, external-protocol function safeguards and AMI event filtering were reviewed October 19, 2026. Installed branch, manager permissions, channel lifetime, variable namespace, function availability, event selection, dialplan ownership and application outcomes remain deployment specific. No PBX, manager account, session, channel, variable, function, event, dialplan, packet, media stream or live call was inspected or tested

Asterisk AMI Getvar or Setvar is wrong, blank or missing a VarSet event

Trace manager framing, ActionID, exact channel lifetime, variable namespace, function policy, event filters and the later consumer before changing the dialplan.

Read guide →
Guide · Current branch-23 AMI DBGet, DBGetTree, DBPut, DBDel and DBDelTree references, Asterisk internal-database and SQLite3 back-end guidance, and the AMI v2 specification were reviewed October 19, 2026. Installed branch, action availability, manager permissions, AstDB ownership, family and key conventions, value semantics, concurrent writers, configured storage location, backup consistency, restore procedure and downstream behavior remain deployment specific. No PBX, manager account, session, AstDB family, key, value, backend file, backup, restore, dialplan, packet, media stream or live call was inspected or tested

Asterisk AMI AstDB: get, put, delete and tree evidence

Read, change or remove the intended AstDB key without confusing an accepted manager response, a broad tree operation or a local persistent value with application outcome evidence.

Read guide →
Troubleshooting · Current branch-23 AMI DBGet, DBGetTree, DBPut, DBDel and DBDelTree references, Asterisk internal-database and SQLite3 back-end guidance, and the AMI v2 specification were reviewed October 19, 2026. Installed branch, action availability, manager permissions, AstDB ownership, family and key conventions, value semantics, concurrent writers, configured storage location, backup consistency, restore procedure and downstream behavior remain deployment specific. No PBX, manager account, session, AstDB family, key, value, backend file, backup, restore, dialplan, packet, media stream or live call was inspected or tested

Asterisk AMI AstDB value is missing, stale or a tree delete is too broad

Trace AMI framing, action availability, exact family and key, writers, readback, deletion scope, local persistence and recovery before changing the dialplan.

Read guide →
Guide · Current branch-23 and branch-22 PJSIPShowRegistrationsInbound and PJSIPShowRegistrationInboundContactStatuses references, current PJSIPShowContacts, InboundRegistrationDetail and ContactStatusDetail references, PJSIP object guidance and the AMI v2 specification were reviewed October 19, 2026. Installed branch, loaded registrar modules, manager action inventory and permissions, configuration owner, AoR and endpoint relationships, static and dynamic contacts, registration expiry, qualification policy, event framing, network path and call behavior remain deployment specific. No PBX, module, manager account, session, AoR, endpoint, static contact, dynamic registration, REGISTER transaction, qualification exchange, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP inbound registration inventories

Choose the correct AMI inventory for configured AoRs, dynamic inbound registrations or all contacts without turning one completed list into endpoint reachability or call evidence.

Read guide →
Troubleshooting · Current branch-23 and branch-22 PJSIPShowRegistrationsInbound and PJSIPShowRegistrationInboundContactStatuses references, current PJSIPShowContacts, InboundRegistrationDetail and ContactStatusDetail references, PJSIP object guidance and the AMI v2 specification were reviewed October 19, 2026. Installed branch, loaded registrar modules, manager action inventory and permissions, configuration owner, AoR and endpoint relationships, static and dynamic contacts, registration expiry, qualification policy, event framing, network path and call behavior remain deployment specific. No PBX, module, manager account, session, AoR, endpoint, static contact, dynamic registration, REGISTER transaction, qualification exchange, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP inbound registration list shows static contacts or misses a phone

Trace action choice, completion framing, AoR ownership, static versus dynamic contact creation, expiry and node scope before changing registration or NAT settings.

Read guide →
Guide · Current branch-23 PJSIPShowEndpoints, PJSIPShowEndpoint, EndpointList, EndpointListComplete, EndpointDetail and EndpointDetailComplete references, PJSIP object guidance, res_pjsip configuration reference and AMI v2 specification were reviewed October 19, 2026. Installed branch, loaded modules, manager action inventory and permissions, configuration owner, endpoint, AoR, auth, transport, identify, contact, device-state provider, active channel, registration, qualification and call behavior remain deployment specific. No PBX, module, manager account, session, endpoint, AoR, auth, transport, identify, contact, channel, registration, qualification exchange, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP endpoint lists and object detail

Use completed endpoint-list and single-endpoint transactions without turning aggregate device state, contact text or active-channel counts into registration or call proof.

Read guide →
Troubleshooting · Current branch-23 PJSIPShowEndpoints, PJSIPShowEndpoint, EndpointList, EndpointListComplete, EndpointDetail and EndpointDetailComplete references, PJSIP object guidance, res_pjsip configuration reference and AMI v2 specification were reviewed October 19, 2026. Installed branch, loaded modules, manager action inventory and permissions, configuration owner, endpoint, AoR, auth, transport, identify, contact, device-state provider, active channel, registration, qualification and call behavior remain deployment specific. No PBX, module, manager account, session, endpoint, AoR, auth, transport, identify, contact, channel, registration, qualification exchange, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP endpoint list has the wrong state, count or objects

Trace an unexpected endpoint row through list completion, exact object detail, configuration ownership, contacts, device-state calculation, channels and node scope.

Read guide →
Guide · Current branch-23 PJSIPShowAors, AorList, AorListComplete, PJSIPShowEndpoint, AorDetail, PJSIP_AOR and PJSIP_CONTACT references, PJSIP object and troubleshooting guidance, res_pjsip configuration reference and AMI v2 specification were reviewed October 19, 2026. Installed branch, loaded modules, manager action inventory and permissions, configuration owner, AoR, endpoint association, static contact, dynamic registration, contact expiry, qualification and call behavior remain deployment specific. No PBX, module, manager account, session, AoR, endpoint, contact, registration, REGISTER transaction, qualification exchange, channel, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP AoR lists, contact policy and exact inspection

Inventory every loaded AoR without turning contact text, counts or registration policy into proof of one current binding, reachable device or working call.

Read guide →
Troubleshooting · Current branch-23 PJSIPShowAors, AorList, AorListComplete, PJSIPShowEndpoint, AorDetail, PJSIP_AOR and PJSIP_CONTACT references, PJSIP object and troubleshooting guidance, res_pjsip configuration reference and AMI v2 specification were reviewed October 19, 2026. Installed branch, loaded modules, manager action inventory and permissions, configuration owner, AoR, endpoint association, static contact, dynamic registration, contact expiry, qualification and call behavior remain deployment specific. No PBX, module, manager account, session, AoR, endpoint, contact, registration, REGISTER transaction, qualification exchange, channel, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP AoR list is empty, stale or has the wrong contacts

Trace an unexpected AoR inventory through completion, exact object identity, endpoint association, generated configuration, contact ownership and lifecycle timing.

Read guide →
Guide · Current branch-23 PJSIPShowContacts, ContactList, ContactListComplete, ContactStatus, ContactStatusDetail, PJSIPShowRegistrationInboundContactStatuses, PJSIPQualify, PJSIP_CONTACT and res_pjsip references plus PJSIP troubleshooting and AMI v2 guidance were reviewed October 19, 2026. Installed branch, loaded modules, manager permissions and filters, configuration owner, contact population, registration lifecycle, qualify exchange and call behavior remain deployment specific. No PBX, module, manager account, session, AoR, endpoint, contact, registration, OPTIONS exchange, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP contact lists, status events and qualification evidence

Separate completed contact snapshots, dynamic-registration detail, asynchronous state changes and requested qualification without turning any one surface into proof of a working call.

Read guide →
Troubleshooting · Current branch-23 PJSIPShowContacts, ContactList, ContactListComplete, ContactStatus, ContactStatusDetail, PJSIPShowRegistrationInboundContactStatuses, PJSIPQualify, PJSIP_CONTACT and res_pjsip references plus PJSIP troubleshooting and AMI v2 guidance were reviewed October 19, 2026. Installed branch, loaded modules, manager permissions and filters, configuration owner, contact population, registration lifecycle, qualify exchange and call behavior remain deployment specific. No PBX, module, manager account, session, AoR, endpoint, contact, registration, OPTIONS exchange, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP contact list is stale or a status event is missing

Trace a disputed contact state through list completion, exact identity, event authority, registration lifecycle, qualification policy and node-local timing.

Read guide →
Guide · Current branch-23 PJSIPShowAuths, AuthList, AuthListComplete, AuthDetail, PJSIPShowEndpoint, EndpointDetail and res_pjsip references plus PJSIP authentication, troubleshooting and AMI guidance were reviewed October 19, 2026. Installed branch, linked pjproject and OpenSSL capabilities, loaded modules, manager action inventory, permissions and transport, configuration owner, auth population, endpoint and registration relationships, credential values, challenge exchange and call behavior remain deployment specific. No PBX, module, manager account, session, auth object, password, digest, OAuth secret, endpoint, registration, SIP challenge, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP auth lists and credential evidence

Separate the complete loaded-auth inventory from endpoint-associated detail, authentication roles, algorithm capability and protected credential material.

Read guide →
Troubleshooting · Current branch-23 PJSIPShowAuths, AuthList, AuthListComplete, AuthDetail, PJSIPShowEndpoint, EndpointDetail and res_pjsip references plus PJSIP authentication, troubleshooting and AMI guidance were reviewed October 19, 2026. Installed branch, linked pjproject and OpenSSL capabilities, loaded modules, manager action inventory, permissions and transport, configuration owner, auth population, endpoint and registration relationships, credential values, challenge exchange and call behavior remain deployment specific. No PBX, module, manager account, session, auth object, password, digest, OAuth secret, endpoint, registration, SIP challenge, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP auth list is missing, wrong or exposes secrets

Trace an auth inventory disagreement through list completion, node identity, loaded relationships, versioned digest support, credential handling and the actual SIP exchange.

Read guide →
Guide · Current Asterisk branch-23 PJSIPShowRegistrationsOutbound, OutboundRegistrationDetail, AuthDetail, PJSIPRegister, PJSIPUnregister, Registry and outbound-registration documentation was reviewed October 23, 2026. The action page and configuration guide still differ on post-unregister scheduling, so installed-branch behavior must be observed. No PBX, module, manager account, session, registration object, auth object, credential, event stream, SIP exchange, DNS answer, timer, provider binding, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP outbound-registration inventory: completion, state and secret boundaries

Collect the complete outbound-registration event list, preserve each status vocabulary and prevent associated authentication secrets from escaping.

Read guide →
Guide · Current branch-23 PJSIPShowRegistrationsOutbound, OutboundRegistrationDetail, AuthDetail, PJSIPRegister, PJSIPUnregister, Registry and res_pjsip_outbound_registration references plus outbound-registration, troubleshooting and AMI guidance were reviewed October 20, 2026. The reviewed action documentation and configuration guide differ on whether a manually unregistered object stops future attempts or later re-registers from its last expiration, so installed-branch behavior must be observed. Installed release, loaded module, manager action inventory, permissions, event delivery, object population, timer state, persistent configuration, resolver, transport, registrar response and call behavior remain deployment specific. No PBX, module, manager account, session, registration object, auth object, credential, REGISTER exchange, DNS result, timer, provider binding, packet, media stream or live call was inspected or tested

Asterisk PJSIPRegister and PJSIPUnregister: runtime control with state proof

Control one loaded outbound-registration object without confusing action acceptance, unregister semantics, later retry state, provider binding or call readiness.

Read guide →
Troubleshooting · Current branch-23 PJSIPShowRegistrationsOutbound, OutboundRegistrationDetail, AuthDetail, PJSIPRegister, PJSIPUnregister, Registry and res_pjsip_outbound_registration references plus outbound-registration, troubleshooting and AMI guidance were reviewed October 20, 2026. The reviewed action documentation and configuration guide differ on whether a manually unregistered object stops future attempts or later re-registers from its last expiration, so installed-branch behavior must be observed. Installed release, loaded module, manager action inventory, permissions, event delivery, object population, timer state, persistent configuration, resolver, transport, registrar response and call behavior remain deployment specific. No PBX, module, manager account, session, registration object, auth object, credential, REGISTER exchange, DNS result, timer, provider binding, packet, media stream or live call was inspected or tested

Asterisk PJSIPRegister or PJSIPUnregister fails, targets the wrong object or has no lasting effect

Trace action authority, completed inventory, exact object identity, conflicting unregister semantics, SIP exchange, event vocabulary and later refresh state before repeating control.

Read guide →
Troubleshooting · Current branch-23 PJSIPShowRegistrationsOutbound, OutboundRegistrationDetail, AuthDetail, PJSIPRegister, PJSIPUnregister, Registry and res_pjsip_outbound_registration references plus outbound-registration, troubleshooting and AMI guidance were reviewed October 20, 2026. The reviewed action documentation and configuration guide differ on whether a manually unregistered object stops future attempts or later re-registers from its last expiration, so installed-branch behavior must be observed. Installed release, loaded module, manager action inventory, permissions, event delivery, object population, timer state, persistent configuration, resolver, transport, registrar response and call behavior remain deployment specific. No PBX, module, manager account, session, registration object, auth object, credential, REGISTER exchange, DNS result, timer, provider binding, packet, media stream or live call was inspected or tested

Asterisk outbound registration is rejected, stopped or has no scheduled retry

Separate loaded-object state, detail and Registry vocabularies, retry classification, NextReg and runtime controls before forcing another REGISTER.

Read guide →
Guide · Current branch-23 PJSIPShowEndpoint, TransportDetail, EndpointDetail, EndpointDetailComplete, AMI action-index and res_pjsip references plus transport-selection, object-relationship, troubleshooting and AMI guidance were reviewed October 21, 2026. The reviewed action index does not document a standalone PJSIP transport-list action; endpoint-associated TransportDetail is not a complete all-transport inventory. Installed release, linked PJSIP and TLS libraries, loaded modules, manager actions and permissions, configuration owner, transport population, listener state, connection reuse, DNS, certificate validation, selected message path and call behavior remain deployment specific. No PBX, module, manager account, session, endpoint, transport, password, private key, certificate, socket, connection, DNS result, packet, media stream or live call was inspected or tested

Asterisk AMI PJSIP TransportDetail and secret-safe evidence

Read endpoint-associated transport detail without mistaking it for an all-transport inventory, listener proof, selected socket, TLS negotiation or SIP delivery.

Read guide →
Troubleshooting · Current branch-23 PJSIPShowEndpoint, TransportDetail, EndpointDetail, EndpointDetailComplete, AMI action-index and res_pjsip references plus transport-selection, object-relationship, troubleshooting and AMI guidance were reviewed October 21, 2026. The reviewed action index does not document a standalone PJSIP transport-list action; endpoint-associated TransportDetail is not a complete all-transport inventory. Installed release, linked PJSIP and TLS libraries, loaded modules, manager actions and permissions, configuration owner, transport population, listener state, connection reuse, DNS, certificate validation, selected message path and call behavior remain deployment specific. No PBX, module, manager account, session, endpoint, transport, password, private key, certificate, socket, connection, DNS result, packet, media stream or live call was inspected or tested

Asterisk AMI TransportDetail is missing, stale or exposes secrets

Trace endpoint scope, completion framing, object relationships, versioned fields, redaction and runtime transport state before changing listeners or AMI permissions.

Read guide →
Guide · Current branch-23 PJSIPShowEndpoint, IdentifyDetail, EndpointDetail, EndpointDetailComplete, AMI action-index, res_pjsip and endpoint-identifier references plus current configuration-relationship, troubleshooting and AMI guidance were reviewed October 21, 2026. The reviewed branch-23 AMI action index does not document a standalone identify-object list action. The current generated identifier reference explicitly supports hostnames, while the older troubleshooting article still says identify match values cannot be hostnames; this documentation conflict is preserved rather than flattened. Installed release, distributor patches, loaded modules, manager actions and permissions, configuration owner, Sorcery mapping, DNS expansion, identifier order, endpoint policy and inbound request behavior remain deployment specific. No PBX, module, manager account, session, endpoint, identify object, hostname, DNS answer, SIP request, packet, route, media stream or live call was inspected or tested

Asterisk AMI PJSIP IdentifyDetail and endpoint-match evidence

Read endpoint-associated identify detail without mistaking loaded criteria for a complete identify inventory, the winning identifier or proof that an inbound request matched.

Read guide →
Troubleshooting · Current branch-23 PJSIPShowEndpoint, IdentifyDetail, EndpointDetail, EndpointDetailComplete, AMI action-index, res_pjsip and endpoint-identifier references plus current configuration-relationship, troubleshooting and AMI guidance were reviewed October 21, 2026. The reviewed branch-23 AMI action index does not document a standalone identify-object list action. The current generated identifier reference explicitly supports hostnames, while the older troubleshooting article still says identify match values cannot be hostnames; this documentation conflict is preserved rather than flattened. Installed release, distributor patches, loaded modules, manager actions and permissions, configuration owner, Sorcery mapping, DNS expansion, identifier order, endpoint policy and inbound request behavior remain deployment specific. No PBX, module, manager account, session, endpoint, identify object, hostname, DNS answer, SIP request, packet, route, media stream or live call was inspected or tested

Asterisk AMI IdentifyDetail is missing, stale or names the wrong endpoint

Trace endpoint scope, completion framing, Sorcery ownership, hostname expansion, identifier order and the actual inbound request before changing match criteria.

Read guide →
Guide · Current branch-20, branch-22, certified-22.8 and branch-23 PJSIP maintenance action, status-event and completion-event references plus current AMI, Dial and upgrade guidance were reviewed October 21, 2026. The action is documented as introduced in Asterisk 20.20.0, 22.10.0 and 23.4.0, so installed release, distributor patches, loaded modules, manager actions, permissions, endpoint names, active dialogs, node scope, reload and restart behavior remain deployment specific. No PBX, module, manager account, endpoint, dialog, registration, SIP request, channel, ARI operation, packet, route, media stream or live call was inspected or tested

Asterisk AMI PJSIP maintenance mode and status evidence

Use versioned AMI actions to drain one PJSIP endpoint without treating command acceptance, status events or SIP rejection as the same proof.

Read guide →
Troubleshooting · Current branch-20, branch-22, certified-22.8 and branch-23 PJSIP maintenance action, status-event and completion-event references plus current AMI, Dial and upgrade guidance were reviewed October 21, 2026. The action is documented as introduced in Asterisk 20.20.0, 22.10.0 and 23.4.0, so installed release, distributor patches, loaded modules, manager actions, permissions, endpoint names, active dialogs, node scope, reload and restart behavior remain deployment specific. No PBX, module, manager account, endpoint, dialog, registration, SIP request, channel, ARI operation, packet, route, media stream or live call was inspected or tested

Asterisk PJSIP maintenance mode is missing, stale or calls still start

Trace release support, AMI framing, endpoint scope, node ownership and actual SIP or channel behavior before repeating or widening maintenance actions.

Read guide →
Guide · Current Asterisk branch-23-generated VoicemailBoxSummary, VoicemailForward, VoicemailMove and VoicemailRemove references and official AMI v2 and manager-permission documentation were reviewed October 25, 2026; all four current action pages are generated under app_voicemail_odbc and date the actions from Asterisk 20.5.0 and 18.20.0, while installed branch, maintenance release, loaded module, voicemail backend, folder vocabulary, message ID lifecycle, manager permissions, response framing and storage behavior remain deployment specific; no PBX, module, mailbox, voicemail store, ODBC database, manager configuration, credential, session, request, response, message, audio payload, folder, user notification, MWI state, endpoint, playback or live call was inspected or tested

Asterisk AMI voicemail message operations: ID, folder and custody evidence

Use VoicemailBoxSummary, VoicemailForward, VoicemailMove and VoicemailRemove without confusing inventory, copy, relocation, deletion, MWI or end-user playback.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated VoicemailBoxSummary, VoicemailForward, VoicemailMove and VoicemailRemove references and official AMI v2 and manager-permission documentation were reviewed October 25, 2026; all four current action pages are generated under app_voicemail_odbc and date the actions from Asterisk 20.5.0 and 18.20.0, while installed branch, maintenance release, loaded module, voicemail backend, folder vocabulary, message ID lifecycle, manager permissions, response framing and storage behavior remain deployment specific; no PBX, module, mailbox, voicemail store, ODBC database, manager configuration, credential, session, request, response, message, audio payload, folder, user notification, MWI state, endpoint, playback or live call was inspected or tested

Asterisk AMI voicemail forward, move or remove fails or targets the wrong message

Find the first divergence across action availability, permissions, mailbox identity, folder, message ID, AMI response, storage result and user-visible state before retrying a mutation.

Read guide →
Guide · Current branch-23-generated and Asterisk 22 PlayDTMF, PlayMF and SendFlash action references, the current DTMFBegin event reference and res_pjsip configuration reference were reviewed October 25, 2026; installed release, loaded app_senddtmf or app_mf module, manager permission, channel technology, live channel identity, bridge topology, direction, negotiated media, DTMF mode and downstream application behavior remain deployment specific; no PBX, channel, manager session, action, digit, hook flash, signalling frame, packet, media stream, endpoint, IVR, carrier or live call was inspected or tested

Asterisk AMI DTMF, MF and hook-flash control: channel and direction evidence

Use PlayDTMF, PlayMF and SendFlash without confusing action acceptance, receive emulation, signalling family, channel leg or downstream effect.

Read guide →
Troubleshooting · Current branch-23-generated and Asterisk 22 PlayDTMF, PlayMF and SendFlash action references, the current DTMFBegin event reference and res_pjsip configuration reference were reviewed October 25, 2026; installed release, loaded app_senddtmf or app_mf module, manager permission, channel technology, live channel identity, bridge topology, direction, negotiated media, DTMF mode and downstream application behavior remain deployment specific; no PBX, channel, manager session, action, digit, hook flash, signalling frame, packet, media stream, endpoint, IVR, carrier or live call was inspected or tested

Asterisk AMI PlayDTMF, PlayMF or SendFlash hits the wrong leg or has no effect

Find the first divergence across action availability, channel identity, direction, signalling, Asterisk events and downstream behavior before retrying control input.

Read guide →
Guide · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 AbsoluteTimeout action references, the current TIMEOUT function, special-extension, HangupRequest, SoftHangupRequest, Hangup and AMI v2 references were reviewed October 25, 2026; installed release, manager permission, live channel identity, timer origin and replacement behavior, dialplan ownership, bridge topology, endpoint signaling and downstream workflow remain deployment-specific; no PBX, manager session, action, timer, dialplan, channel, bridge, event stream, endpoint, packet, media stream or live call was inspected or tested

Asterisk AMI AbsoluteTimeout: timer, channel and hangup evidence

Set a channel lifetime limit without confusing action acknowledgement, timer expiry, dialplan handling, hangup requests or the final channel outcome.

Read guide →
Troubleshooting · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 AbsoluteTimeout action references, the current TIMEOUT function, special-extension, HangupRequest, SoftHangupRequest, Hangup and AMI v2 references were reviewed October 25, 2026; installed release, manager permission, live channel identity, timer origin and replacement behavior, dialplan ownership, bridge topology, endpoint signaling and downstream workflow remain deployment-specific; no PBX, manager session, action, timer, dialplan, channel, bridge, event stream, endpoint, packet, media stream or live call was inspected or tested

Asterisk AMI AbsoluteTimeout fires early, late or on the wrong channel

Find the first divergence across action availability, channel identity, time units, timer policy, T and h dialplan handling, request events and final hangup.

Read guide →
Guide · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 MuteAudio action references, the current MUTEAUDIO function, MixMonitorMute, ConfbridgeMute, CoreShowChannel, Manager API and AMI v2 references were reviewed October 25, 2026; installed release, loaded modules and actions, manager permission, live channel identity, bridge technology, media path, recording, conference policy and endpoint state remain deployment-specific; no PBX, manager session, action, dialplan, channel, bridge, conference, recording, packet, media frame, endpoint, speaker, microphone or live call was inspected or tested

Asterisk AMI MuteAudio: channel, direction and media proof

Mute one channel stream without confusing PBX-relative direction, action acknowledgement, bridge peers, recordings, conferences or endpoint mute.

Read guide →
Troubleshooting · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 MuteAudio action references, the current MUTEAUDIO function, MixMonitorMute, ConfbridgeMute, CoreShowChannel, Manager API and AMI v2 references were reviewed October 25, 2026; installed release, loaded modules and actions, manager permission, live channel identity, bridge technology, media path, recording, conference policy and endpoint state remain deployment-specific; no PBX, manager session, action, dialplan, channel, bridge, conference, recording, packet, media frame, endpoint, speaker, microphone or live call was inspected or tested

Asterisk AMI MuteAudio uses the wrong direction, wrong leg or stays audible

Find the first divergence across action availability, live channel identity, PBX-relative direction, response, topology and the actual media path.

Read guide →
Guide · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 ControlPlayback action references, current and Asterisk 22 ControlPlayback application references, the current CONTROL STREAM FILE command, Certified Asterisk 22.8 Playback, CoreShowChannel and Manager API references were reviewed October 25, 2026; installed release, loaded modules and actions, manager permission, live channel identity, playback initiator, media file, language, format, skip interval, application state, bridge topology, packet path and endpoint output remain deployment-specific; no PBX, manager session, action, dialplan, AGI process, channel, playback, file, packet, media frame, endpoint, speaker or live call was inspected or tested

Asterisk AMI ControlPlayback: target, initiator and result evidence

Control an existing channel playback without confusing action acceptance, playback initiation, skip timing, completion variables or audible output.

Read guide →
Troubleshooting · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 ControlPlayback action references, current and Asterisk 22 ControlPlayback application references, the current CONTROL STREAM FILE command, Certified Asterisk 22.8 Playback, CoreShowChannel and Manager API references were reviewed October 25, 2026; installed release, loaded modules and actions, manager permission, live channel identity, playback initiator, media file, language, format, skip interval, application state, bridge topology, packet path and endpoint output remain deployment-specific; no PBX, manager session, action, dialplan, AGI process, channel, playback, file, packet, media frame, endpoint, speaker or live call was inspected or tested

Asterisk AMI ControlPlayback stops, targets the wrong channel or has no effect

Find the first divergence across action availability, live channel identity, playback initiator, control support, skip timing, completion state and audible output.

Read guide →
Guide · Asterisk 20 Monitor, ChangeMonitor, PauseMonitor, UnpauseMonitor and StopMonitor AMI action references, the Asterisk 20 Monitor application, the Asterisk 21 removal notice, and current branch-23-generated MixMonitor, StopMixMonitor and CoreShowChannel references were reviewed October 25, 2026; res_monitor was deprecated in Asterisk 16 and removed in Asterisk 21, so legacy Monitor actions must not be represented as current-branch capabilities; installed release, vendor patches, loaded modules, action inventory, manager permissions, exact channel identity, monitor directory, filenames, formats, file ownership, storage, mix command, audio contents, retention and generated FreePBX dialplan remain deployment-specific; no PBX, module, manager account, action, channel, file, packet, recording, processor, endpoint or live call was inspected or tested

Asterisk AMI Monitor: legacy lifecycle and MixMonitor migration

Identify the Asterisk 20-and-earlier res_monitor lifecycle, keep rename, pause, stop and file evidence distinct, and migrate without assuming the actions exist on current branches.

Read guide →
Troubleshooting · Asterisk 20 Monitor, ChangeMonitor, PauseMonitor, UnpauseMonitor and StopMonitor AMI action references, the Asterisk 20 Monitor application, the Asterisk 21 removal notice, and current branch-23-generated MixMonitor, StopMixMonitor and CoreShowChannel references were reviewed October 25, 2026; res_monitor was deprecated in Asterisk 16 and removed in Asterisk 21, so legacy Monitor actions must not be represented as current-branch capabilities; installed release, vendor patches, loaded modules, action inventory, manager permissions, exact channel identity, monitor directory, filenames, formats, file ownership, storage, mix command, audio contents, retention and generated FreePBX dialplan remain deployment-specific; no PBX, module, manager account, action, channel, file, packet, recording, processor, endpoint or live call was inspected or tested

Asterisk AMI Monitor action is missing or its recording file is wrong

Find the first divergence across Asterisk version, res_monitor availability, manager authority, channel identity, rename and pause state, stop ordering, mixing, storage and decoded audio.

Read guide →
Guide · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 Hangup action references, current HangupRequest, SoftHangupRequest and Hangup events, the official cause-mapping table, current CHANNEL, Asterisk 22 HANGUPCAUSE and the AMI v2 specification were reviewed October 25, 2026; installed release, manager authority, live channel identity, bridge topology, hangup handlers, dialplan ownership, channel technology, signaling, cause translation, event filters and downstream workflow remain deployment-specific; no PBX, manager session, action, regular expression, dialplan, channel, bridge, event stream, endpoint, packet, signaling exchange, media stream or live call was inspected or tested

Asterisk AMI Hangup: target, cause and final-event evidence

End an exact channel without confusing action acceptance, a broad regular-expression target, request events, cause translation, linked legs or final disposal.

Read guide →
Troubleshooting · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 Hangup action references, current HangupRequest, SoftHangupRequest and Hangup events, the official cause-mapping table, current CHANNEL, Asterisk 22 HANGUPCAUSE and the AMI v2 specification were reviewed October 25, 2026; installed release, manager authority, live channel identity, bridge topology, hangup handlers, dialplan ownership, channel technology, signaling, cause translation, event filters and downstream workflow remain deployment-specific; no PBX, manager session, action, regular expression, dialplan, channel, bridge, event stream, endpoint, packet, signaling exchange, media stream or live call was inspected or tested

Asterisk AMI Hangup is accepted but the wrong channel ends or no final event appears

Find the first divergence across target scope, channel lifetime, authority, cause semantics, request events, cleanup, event visibility and linked-leg outcomes.

Read guide →
Guide · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 SendText action references, current SendText and ReceiveText dialplan applications, current AMI and dialplan MessageSend references, current CHANNEL and the AMI specifications were reviewed October 26, 2026; installed release, loaded channel driver, enhanced-messaging support, live channel identity, content handling, signaling method, endpoint rendering, manager permissions, event filters and downstream workflow remain deployment-specific; no PBX, manager session, action, message body, channel, endpoint, packet, signaling exchange, user interface, recipient or live call was inspected or tested

Asterisk AMI SendText: in-call message and channel evidence

Send bounded text to one live channel without confusing action acceptance, channel-driver capability, content type, protocol transport or recipient presentation.

Read guide →
Troubleshooting · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 SendText action references, current SendText and ReceiveText dialplan applications, current AMI and dialplan MessageSend references, current CHANNEL and the AMI specifications were reviewed October 26, 2026; installed release, loaded channel driver, enhanced-messaging support, live channel identity, content handling, signaling method, endpoint rendering, manager permissions, event filters and downstream workflow remain deployment-specific; no PBX, manager session, action, message body, channel, endpoint, packet, signaling exchange, user interface, recipient or live call was inspected or tested

Asterisk AMI SendText is accepted but the message is missing or reaches the wrong channel

Locate the first divergence across channel identity, manager authority, content handling, driver support, protocol transport and endpoint presentation.

Read guide →
Guide · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 MessageSend action references, current MessageSend, MESSAGE and MESSAGE_DATA dialplan references, current ARI endpoint messaging, PJSIP transport selection and AMI specifications were reviewed October 26, 2026; installed release, loaded message technology, endpoint, AoR, contact, Request-URI, To and From headers, transport, body handling, remote policy, user-agent presentation, manager permissions and downstream workflow remain deployment-specific; no PBX, manager session, action, endpoint, contact, message body, packet, SIP transaction, remote service, user interface, recipient or live call was inspected or tested

Asterisk AMI MessageSend: out-of-call routing and delivery evidence

Construct an out-of-call message without confusing its technology destination, SIP Request-URI, To and From headers, body handling, action response or recipient outcome.

Read guide →
Troubleshooting · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 MessageSend action references, current MessageSend, MESSAGE and MESSAGE_DATA dialplan references, current ARI endpoint messaging, PJSIP transport selection and AMI specifications were reviewed October 26, 2026; installed release, loaded message technology, endpoint, AoR, contact, Request-URI, To and From headers, transport, body handling, remote policy, user-agent presentation, manager permissions and downstream workflow remain deployment-specific; no PBX, manager session, action, endpoint, contact, message body, packet, SIP transaction, remote service, user interface, recipient or live call was inspected or tested

Asterisk AMI MessageSend is accepted but the message is missing or reaches the wrong destination

Find the first divergence across AMI framing, technology destination, endpoint and contact choice, SIP addressing, transport, remote response and client presentation.

Read guide →
Guide · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 AOCMessage references, current and Asterisk 22 AOC-S, AOC-D and AOC-E event references, and the AMI v2 specification were reviewed October 26, 2026; installed release, channel technology, channel identity, driver support, Advice of Charge signaling, rating authority, currency and unit policy, manager permissions, event delivery and remote presentation remain deployment-specific; no PBX, manager session, action, channel, charge, tariff, bill, carrier, endpoint, packet, signaling exchange, display or live call was inspected or tested

Asterisk AMI AOCMessage: charge, channel and event evidence

Generate Advice of Charge signaling without confusing channel selection, AOC-S, AOC-D or AOC-E structure, encoded units or currency, AMI acceptance, AOC events, remote presentation or billing authority.

Read guide →
Troubleshooting · Current branch-23-generated, Asterisk 22 and Certified Asterisk 22.8 AOCMessage references, current and Asterisk 22 AOC-S, AOC-D and AOC-E event references, and the AMI v2 specification were reviewed October 26, 2026; installed release, channel technology, channel identity, driver support, Advice of Charge signaling, rating authority, currency and unit policy, manager permissions, event delivery and remote presentation remain deployment-specific; no PBX, manager session, action, channel, charge, tariff, bill, carrier, endpoint, packet, signaling exchange, display or live call was inspected or tested

Asterisk AMI AOCMessage uses the wrong channel or charge, or no AOC event appears

Find the first divergence across manager framing, live channel identity, message phase, units or currency encoding, AOC event delivery, signaling support and remote presentation.

Read guide →
Guide · Current branch-23-generated Asterisk Agents and AgentLogoff actions, agent inventory, login, logoff and queue-call events, AgentLogin, AGENT(), app_agent_pool, AMI v2 and network-security documentation were reviewed October 26, 2026; installed version, app_agent_pool availability, agents.conf, dialplan authentication, queue membership, manager permissions and event filters, live agent channel, device state, call result, recording and FreePBX ownership remain deployment-specific; no PBX, FreePBX system, module, manager account, credential, agent, queue, channel, event stream, recording, packet, media stream or live call was inspected or tested

Asterisk AMI agent inventory, logoff and call-event evidence

Separate app_agent_pool definitions, agent login state, queue membership, AMI list completion, logoff semantics and per-call events without treating one identifier as the whole state model.

Read guide →
Troubleshooting · Current branch-23-generated Asterisk Agents and AgentLogoff actions, agent inventory, login, logoff and queue-call events, AgentLogin, AGENT(), app_agent_pool, AMI v2 and network-security documentation were reviewed October 26, 2026; installed version, app_agent_pool availability, agents.conf, dialplan authentication, queue membership, manager permissions and event filters, live agent channel, device state, call result, recording and FreePBX ownership remain deployment-specific; no PBX, FreePBX system, module, manager account, credential, agent, queue, channel, event stream, recording, packet, media stream or live call was inspected or tested

Asterisk AMI agent is missing, logoff fails or events do not correlate

Find the first divergence across agent model, module and configuration, list completion, login channel, queue identity, event delivery, soft logoff and the final post-action snapshot.

Read guide →
Guide · Current branch-23-generated Asterisk FAXSession, FAXSessions and FAXStats actions and response events, FAXStatus, ReceiveFAX, SendFAX, FAXOPT, AMI v2 and network-security documentation were reviewed October 26, 2026; installed Asterisk version, res_fax and technology module availability, manager permissions and filters, session timing, counter lifetime, channel and dialplan ownership, storage, notification and FreePBX behavior remain deployment-specific; no PBX, FreePBX system, module, manager account, credential, fax session, channel, TIFF/F file, notification, packet, media stream or document delivery was inspected or tested

Asterisk AMI fax session inventory and statistics evidence

Use FAXSessions, FAXSession and FAXStats as bounded runtime observations while keeping progress events, terminal application results, negotiated mode and delivered-document evidence separate.

Read guide →
Troubleshooting · Current branch-23-generated Asterisk FAXSession, FAXSessions and FAXStats actions and response events, FAXStatus, ReceiveFAX, SendFAX, FAXOPT, AMI v2 and network-security documentation were reviewed October 26, 2026; installed Asterisk version, res_fax and technology module availability, manager permissions and filters, session timing, counter lifetime, channel and dialplan ownership, storage, notification and FreePBX behavior remain deployment-specific; no PBX, FreePBX system, module, manager account, credential, fax session, channel, TIFF/F file, notification, packet, media stream or document delivery was inspected or tested

Asterisk AMI fax session is missing, stale or statistics do not match

Find the first divergence across module support, completed active-session inventory, session timing, conditional detail fields, manager delivery, process-counter scope and terminal fax evidence.

Read guide →
Guide · Current branch-23-generated Asterisk PJSIPShowResourceLists and ResourceListDetail documentation, resource-list subscription and res_pjsip_pubsub configuration guidance, PJSIP troubleshooting, AMI v2, event-filtering and network-security documentation were reviewed October 26, 2026; installed Asterisk version, module availability, pjsip.conf object graph, endpoint support, active subscription state, manager permissions and filters, SIP signaling, notification size and device behavior remain deployment-specific; no PBX, FreePBX system, module, configuration, manager account, credential, endpoint, subscription, SIP message, packet, notification or device was inspected or tested

Asterisk AMI PJSIP resource-list inventory and configuration evidence

Use PJSIPShowResourceLists as a completed configuration inventory while keeping configured list membership, active subscriptions, SIP NOTIFY delivery and endpoint display state separate.

Read guide →
Troubleshooting · Current branch-23-generated Asterisk PJSIPShowResourceLists and ResourceListDetail documentation, resource-list subscription and res_pjsip_pubsub configuration guidance, PJSIP troubleshooting, AMI v2, event-filtering and network-security documentation were reviewed October 26, 2026; installed Asterisk version, module availability, pjsip.conf object graph, endpoint support, active subscription state, manager permissions and filters, SIP signaling, notification size and device behavior remain deployment-specific; no PBX, FreePBX system, module, configuration, manager account, credential, endpoint, subscription, SIP message, packet, notification or device was inspected or tested

Asterisk AMI PJSIP resource list is missing, stale or incomplete

Find the first divergence across module support, completed AMI inventory, pjsip.conf ownership, list semantics, subscription refresh, NOTIFY delivery and endpoint state.

Read guide →
Guide · Current branch-23-generated Asterisk DAHDIShowStatus, DAHDIShowChannels, DAHDIChannel, SpanAlarm and SpanAlarmClear documentation, channel fundamentals, AMI v2, event-filtering and network-security guidance were reviewed October 27, 2026; installed Asterisk and DAHDI versions, chan_dahdi availability, kernel drivers, spans, timing, signaling, hardware, carrier facilities, analog lines, manager permissions and filters, channel activity and alarm state remain deployment-specific; no PBX, FreePBX system, module, driver, card, gateway, span, channel, line, carrier circuit, configuration, manager account, credential, event stream, call, packet or audio was inspected or tested

Asterisk AMI DAHDI span and channel inventory with alarm evidence

Use DAHDIShowStatus, DAHDIShowChannels and DAHDI events as separate span, channel and change observations without turning an AMI response into proof of physical-circuit health.

Read guide →
Troubleshooting · Current branch-23-generated Asterisk DAHDIShowStatus, DAHDIShowChannels, DAHDIChannel, SpanAlarm and SpanAlarmClear documentation, channel fundamentals, AMI v2, event-filtering and network-security guidance were reviewed October 27, 2026; installed Asterisk and DAHDI versions, chan_dahdi availability, kernel drivers, spans, timing, signaling, hardware, carrier facilities, analog lines, manager permissions and filters, channel activity and alarm state remain deployment-specific; no PBX, FreePBX system, module, driver, card, gateway, span, channel, line, carrier circuit, configuration, manager account, credential, event stream, call, packet or audio was inspected or tested

Asterisk AMI DAHDI span or channel is missing, alarmed or inconsistent

Find the first divergence across version support, module and driver state, span snapshot, channel snapshot, configuration ownership, alarm events and the physical circuit.

Read guide →
Guide · Current branch-23-generated Asterisk PRIShowSpans, PRIDebugSet, PRIDebugFileSet, PRIDebugFileUnset, SpanAlarm and SpanAlarmClear documentation, AMI v2, event-filtering, logging and network-security guidance were reviewed October 27, 2026; installed Asterisk, libpri and DAHDI versions, chan_dahdi availability, manager permissions, spans, debug levels, file paths, signaling, timing, framing, coding, alarms, hardware and carrier facilities remain deployment-specific; no PBX, FreePBX system, module, driver, card, gateway, span, D channel, B channel, line, circuit, configuration, manager account, credential, event stream, debug file, signaling frame, call, packet or audio was inspected or tested

Asterisk AMI PRI span inventory and bounded debug evidence

Use PRIShowSpans for a bounded PRI status snapshot, then govern PRI debug level and file output as separate operational changes without treating either as physical-line proof.

Read guide →
Troubleshooting · Current branch-23-generated Asterisk PRIShowSpans, PRIDebugSet, PRIDebugFileSet, PRIDebugFileUnset, SpanAlarm and SpanAlarmClear documentation, AMI v2, event-filtering, logging and network-security guidance were reviewed October 27, 2026; installed Asterisk, libpri and DAHDI versions, chan_dahdi availability, manager permissions, spans, debug levels, file paths, signaling, timing, framing, coding, alarms, hardware and carrier facilities remain deployment-specific; no PBX, FreePBX system, module, driver, card, gateway, span, D channel, B channel, line, circuit, configuration, manager account, credential, event stream, debug file, signaling frame, call, packet or audio was inspected or tested

Asterisk AMI PRI span is missing, down or its debug evidence is incomplete

Find the first divergence across action support, chan_dahdi and libpri state, PRI and DAHDI inventory, alarm chronology, bounded debug output and the carrier circuit.

Read guide →
Guide · Asterisk 20-generated SIPpeers, SIPshowpeer, SIPpeerstatus and SIPshowregistry action documentation, current PJSIPShowEndpoints and ListCommands contracts, chan_sip deprecation and removal records, migration guidance, AMI v2 and network-security guidance were reviewed October 27, 2026; installed Asterisk and FreePBX versions, build options, loaded modules, channel driver, manager permissions, configuration ownership, endpoint objects, registrations, contacts, authentication, transports, routing and media remain deployment-specific; no PBX, FreePBX system, module, configuration, manager account, credential, peer, endpoint, AoR, contact, registration, packet, call or audio was inspected or tested

Asterisk AMI chan_sip peer inventory and PJSIP migration evidence

Interpret legacy SIPpeers, SIPshowpeer, SIPpeerstatus and SIPshowregistry only within the chan_sip version boundary, then map the operational question to current PJSIP objects and bounded inventories.

Read guide →
Troubleshooting · Asterisk 20-generated SIPpeers, SIPshowpeer, SIPpeerstatus and SIPshowregistry action documentation, current PJSIPShowEndpoints and ListCommands contracts, chan_sip deprecation and removal records, migration guidance, AMI v2 and network-security guidance were reviewed October 27, 2026; installed Asterisk and FreePBX versions, build options, loaded modules, channel driver, manager permissions, configuration ownership, endpoint objects, registrations, contacts, authentication, transports, routing and media remain deployment-specific; no PBX, FreePBX system, module, configuration, manager account, credential, peer, endpoint, AoR, contact, registration, packet, call or audio was inspected or tested

Asterisk AMI SIPpeers or SIPshowpeer is missing after an upgrade

Separate expected chan_sip removal from manager permissions, module state, collector assumptions and incomplete PJSIP migration before diagnosing a missing peer or registration.

Read guide →
Guide · Current and Asterisk 22-generated IAXpeers, IAXpeerlist, IAXregistry and IAXnetstats action documentation, IAX2 security guidance, iax.conf sample, chan_iax2 source and AMI v2 specification were reviewed October 27, 2026; installed Asterisk and FreePBX versions, downstream patches, build options, loaded chan_iax2 module, manager permissions, peer configuration, dynamic binding, outbound registration, qualification, active channels, network-stat fields and units, routing, packets and media remain deployment-specific; no PBX, FreePBX system, module, configuration, manager account, credential, peer, registry, channel, packet, call or audio was inspected or tested

Asterisk AMI IAX2 peer, registry and netstats evidence

Use IAXpeerlist, IAXpeers, IAXregistry and IAXnetstats as separate chan_iax2 observations without inventing undocumented event schemas, completion markers, filters or proof of call quality.

Read guide →
Troubleshooting · Current and Asterisk 22-generated IAXpeers, IAXpeerlist, IAXregistry and IAXnetstats action documentation, IAX2 security guidance, iax.conf sample, chan_iax2 source and AMI v2 specification were reviewed October 27, 2026; installed Asterisk and FreePBX versions, downstream patches, build options, loaded chan_iax2 module, manager permissions, peer configuration, dynamic binding, outbound registration, qualification, active channels, network-stat fields and units, routing, packets and media remain deployment-specific; no PBX, FreePBX system, module, configuration, manager account, credential, peer, registry, channel, packet, call or audio was inspected or tested

Asterisk AMI IAX2 peer, registry or netstats is missing, stale or incomplete

Separate action availability, manager permissions, undocumented list framing, peer and registry state, active-channel timing and collector assumptions before changing IAX2 configuration.

Read guide →
Guide · Current branch-23-generated and Asterisk 22 BridgeTechnologyList, BridgeTechnologySuspend and BridgeTechnologyUnsuspend action documentation, current bridge-core source, BridgeList, BridgeInfo, bridge concepts, AMI v2 and network-security guidance were reviewed October 28, 2026; installed Asterisk and FreePBX versions, downstream patches, compiled and loaded bridge modules, registered technology names, capabilities, priorities, suspension state, manager permissions, active bridges, channel membership, media topology and call outcomes remain deployment-specific; no PBX, FreePBX system, module, bridge technology, manager account, credential, bridge, channel, packet, media frame, endpoint or live call was inspected or tested

Asterisk AMI bridge-technology inventory, suspend and unsuspend evidence

Inventory registered bridge technologies and bound suspend or unsuspend changes to future bridge selection without treating action acceptance as proof of active-bridge, media or call behavior.

Read guide →
Troubleshooting · Current branch-23-generated and Asterisk 22 BridgeTechnologyList, BridgeTechnologySuspend and BridgeTechnologyUnsuspend action documentation, current bridge-core source, BridgeList, BridgeInfo, bridge concepts, AMI v2 and network-security guidance were reviewed October 28, 2026; installed Asterisk and FreePBX versions, downstream patches, compiled and loaded bridge modules, registered technology names, capabilities, priorities, suspension state, manager permissions, active bridges, channel membership, media topology and call outcomes remain deployment-specific; no PBX, FreePBX system, module, bridge technology, manager account, credential, bridge, channel, packet, media frame, endpoint or live call was inspected or tested

Asterisk AMI bridge technology is missing, suspended or selects differently

Trace one bridge-technology contradiction through release, module registration, manager framing, exact technology identity, suspension state, capability requirements and a separately observed bridge instance.

Read guide →
Guide · Current branch-23-generated and Asterisk 22 LoggerRotate action documentation, AMI framing and authorization guidance, logging commands and configuration, bounded debug collection, ARI logging, current logger source and sample configuration, and source-install logrotate guidance were reviewed October 28, 2026; installed Asterisk and FreePBX versions, downstream patches, logger configuration ownership, runtime channels, file paths, rotation strategy, filesystem permissions and labels, free space, external logrotate or post-rotate commands, syslog, collectors, compression, retention and downstream ingestion remain deployment-specific; no PBX, FreePBX system, logger channel, manager account, credential, command, file, directory, inode, descriptor, filesystem, collector, packet, call or media stream was inspected or tested

Asterisk AMI LoggerRotate and log-file lifecycle evidence

Use LoggerRotate as one bounded logger action while keeping configuration reload, file reopen, filename strategy, filesystem state, post-rotate work and downstream collection independently verifiable.

Read guide →
Troubleshooting · Current branch-23-generated and Asterisk 22 LoggerRotate action documentation, AMI framing and authorization guidance, logging commands and configuration, bounded debug collection, ARI logging, current logger source and sample configuration, and source-install logrotate guidance were reviewed October 28, 2026; installed Asterisk and FreePBX versions, downstream patches, logger configuration ownership, runtime channels, file paths, rotation strategy, filesystem permissions and labels, free space, external logrotate or post-rotate commands, syslog, collectors, compression, retention and downstream ingestion remain deployment-specific; no PBX, FreePBX system, logger channel, manager account, credential, command, file, directory, inode, descriptor, filesystem, collector, packet, call or media stream was inspected or tested

Asterisk AMI LoggerRotate is accepted but a log file is missing, stale or wrong

Trace one LoggerRotate contradiction through manager acceptance, effective logger policy, strategy-dependent filename, file reopen, filesystem state, post-rotate work and downstream ingestion.

Read guide →
Guide · Current Asterisk backtrace, logging, issue-report, debugging-CLI and Menuselect documentation was reviewed October 29, 2026; installed branch, packaging, executable, modules, debug symbols, build flags, service manager, kernel core policy, filesystem capacity, crash signal, core file, stack frames, locks, logs, packet capture, reproduction, production impact, root cause, fix and support response remain deployment-specific; no Asterisk host, FreePBX system, binary, module, debug-symbol package, kernel setting, core dump, backtrace, log, packet, crash, deadlock, live call or support case was inspected or tested

Asterisk crash, core dump and backtrace evidence

Prepare, capture, preserve, inspect and share Asterisk crash or deadlock evidence without assuming a core file is complete, symbols match or the root cause is known.

Read guide →
Troubleshooting · Current Asterisk backtrace, logging, issue-report, debugging-CLI and Menuselect documentation was reviewed October 29, 2026; installed branch, packaging, executable, modules, debug symbols, build flags, service manager, kernel core policy, filesystem capacity, crash signal, core file, stack frames, locks, logs, packet capture, reproduction, production impact, root cause, fix and support response remain deployment-specific; no Asterisk host, FreePBX system, binary, module, debug-symbol package, kernel setting, core dump, backtrace, log, packet, crash, deadlock, live call or support case was inspected or tested

Asterisk core dump is missing or the backtrace is incomplete

Find the first evidence gap across incident identity, dump policy, matching binaries and modules, debug symbols, report generation, thread coverage, logs and secure escalation.

Read guide →