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

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.

Reviewed 2026-10-26Current 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 testedAdvancedDocumentation based · not lab tested

Identify the agent model before querying it

Confirm the responding node, exact Asterisk build, loaded app_agent_pool, agents.conf ownership, configured agent ID, login dialplan and queue relationship. The AMI Agents action lists agents defined by app_agent_pool; it is not a universal inventory of queue members, endpoints, extensions or contact-centre users.

Keep Agent, queue MemberName, queue Interface, channel name, Uniqueid and Linkedid as distinct identifiers. Join them only from retained evidence for one time window.

Treat Agents as a bounded event list

Send a unique ActionID, retain each Agents event with that value, and close the snapshot only when its matching AgentsComplete arrives. Each item can report AGENT_LOGGEDOFF, AGENT_IDLE or AGENT_ONCALL; the channel snapshot is documented only for idle or on-call values, and TalkingToChan plus CallStarted apply only when on call.

An empty, interrupted or filtered list is not proof that no agent exists. Record list completion, item count, receive window, connection identity and event policy before comparing snapshots.

Preserve login, authentication and configuration boundaries

AgentLogin() logs an agent into the pool and assumes any authentication has already been performed by the dialplan. INVALID and ALREADY_LOGGED_IN are dialplan AGENT_STATUS outcomes, while AgentLogin is the event raised when login succeeds. The Agent:AgentId device state and AGENT() function are additional observations, not substitutes for a completed AMI list.

Configuration such as acknowledgement DTMF, automatic logoff, music on hold, recording and wrap-up time can take effect at login or after a call disconnects. A file edit or reload therefore does not prove an already logged-in agent adopted a value.

Use soft logoff deliberately

The AMI AgentLogoff action targets an agent ID. Its Soft value set to true is documented not to hang up existing calls; omitting that protection can affect an active call and requires a stricter change window. Record operator, reason, exact agent, soft policy, ActionID, response, later AgentLogoff event and a fresh completed inventory.

An accepted action is request-processing evidence. It does not by itself prove the intended agent was current, an active call survived, the login channel ended or queue membership changed.

Correlate queue-call events without flattening the legs

AgentCalled, AgentConnect, AgentComplete, AgentDump and AgentRingNoAnswer carry caller and destination channel snapshots plus queue, member and interface fields. AgentConnect adds ring and hold time; AgentComplete adds hold time, talk time and a reason. Preserve both channel identities and their unique IDs rather than joining only by caller ID or member name.

These events describe queue-call stages. They do not make an app_agent_pool agent definition identical to a queue member, prove audio, establish payroll or billing facts, or replace queue-log, CDR, CEL and recording evidence.

Bound permissions, privacy and operational claims

Use a dedicated least-privilege manager identity with only the required action and AGENT event classes, explicit source restrictions and a narrow event policy. Redact caller identity, account codes, channel names and agent activity; retain operator identity, reason, ActionID, timestamps and rollback evidence.

No PBX, FreePBX system, module, manager account, credential, agent, queue, channel, event stream, recording, packet, media stream or live call was inspected or tested. Validate one authorized disposable agent and one bounded queue call before relying on dashboards or controls.

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 · 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 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.

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 · Current Asterisk branch-23-generated CoreShowChannelMap, CoreShowChannelMapComplete, CoreShowChannels, CoreShowChannel, CoreShowChannelsComplete, Status, StatusComplete, Newchannel and Rename references plus the branch 22 map action and completion event reviewed October 16, 2026; installed branch, loaded actions and events, manager permissions, session ordering, channel names, stable identifiers, bridge membership, variables, signaling and media remain deployment specific; no PBX, AMI session, manager user, permission, channel, bridge, variable, packet, media stream or live call was inspected or tested

Asterisk AMI channel snapshots and connected maps

Choose CoreShowChannels, CoreShowChannelMap or Status deliberately, preserve list boundaries, and correlate mutable channel, linked and bridge identities without treating a snapshot as a final call result.

Read guide →
Guide · Asterisk 22 LTS

Asterisk queues: member state, caller outcomes and evidence

Separate queue membership, device state, pauses, call attempts, answered bridges and historical outcomes.

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 →
Guide · Current branch-23-generated and branch-22 QueueAdd, QueueRemove, QueuePause and QueuePenalty action references, current QueueMemberAdded, QueueMemberRemoved, QueueMemberPenalty and QueueMemberStatus event references, the branch-22 QueueMemberPause event reference, and the AMI v2 specification reviewed October 17, 2026; action response, queue and interface scope, membership event, pause or penalty event, later snapshot, device state, ringing, bridge, answer and caller outcome remain separate evidence boundaries; installed branch, loaded app_queue module, queue strategy, manager permissions and filters, generated FreePBX configuration, persistence and endpoint behavior remain deployment specific; no PBX, module, queue, member, configuration, manager account, session, event stream, endpoint, packet, audio or live call was inspected or tested

Asterisk AMI queue-member add, remove, pause and penalty controls

Scope queue membership, pause and penalty actions to exact queue and interface identities, then verify events, snapshots, eligibility and call outcomes separately.

Read guide →
Guide · Current Asterisk device-state, extension-hint, presence-state and res_pjsip subscription documentation plus the Asterisk 22.12.0-rc2 change record were reviewed October 8, 2026; candidate fixes are not final-release availability, and providers, aggregation, event bodies and endpoint behavior still depend on the installed Asterisk branch, modules, dialplan and device

Asterisk device state, extension hints and presence

Separate a device provider's state, a hint's aggregate extension state, a user's presence choice and the PJSIP subscription that delivers updates to a phone.

Read guide →
Guide · Asterisk 22 LTS application references and current audiohook architecture reviewed September 30, 2026; no PBX, call, channel, recording, file, processor, storage or playback path was tested

Asterisk MixMonitor: channel scope, files and recording evidence

Plan recording policy, bind MixMonitor to the intended channel and verify each file lifecycle boundary.

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 · 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 →