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

Asterisk AMI UserEvent is missing, duplicated or misleading

Trace one application-owned event from its AMI action or dialplan producer through event naming, USER permission, masks, filters, transport, parsing, idempotent storage and the separate business outcome.

Reviewed 2026-10-16Current Asterisk branch-23-generated AMI UserEvent action, UserEvent event and UserEvent dialplan-application references, matching branch-22 references, plus the official AMI event-filtering, command-syntax and Manager TCP/IP material reviewed October 16, 2026; installed branch, module, dialplan, manager permissions, session mask, filters, transport, parser, retry policy, schema and application outcome remain deployment specific; no PBX, module, dialplan, manager session, event stream, channel, bridge, endpoint, packet, media stream, business system or live call was inspected or testedAdvancedDocumentation based · not lab tested

Freeze one event contract and attempt

Record installed branch and maintenance release, producer type, module or dialplan location, exact event name and case, schema version, custom correlation key, safe headers, AMI action request and response where applicable, manager user, session identity, receive timestamps, parser output, storage writes and the separately observed business result.

Classify the symptom before changing code: no action response, accepted action but no event, dialplan path not reached, event absent for one consumer, missing fields, duplicate delivery, duplicate storage or a received event whose claimed outcome is false.

Prove that the producer reached emission

For an AMI producer, correlate the UserEvent action response with its ActionID; treat that as transaction evidence, not an event-field promise. For a dialplan producer, prove that execution reached UserEvent() with the expected expanded event name and body. Confirm app_userevent is available on the installed system.

Use a safe test contract and unique application correlation key. Do not add secrets or personal data merely to make the event easier to find.

Check USER delivery controls in order

The generated event is class USER. Confirm the manager user has appropriate read access, the login and current session masks admit the class, and configured plus dynamic filters retain the exact event. Event names are case-sensitive, so a filter or consumer comparison using different case can correctly produce silence.

Then inspect raw AMI message boundaries before the client parser. An action can succeed while its resulting event is withheld from a particular session.

Compare fields with the producer contract

For dialplan emission, the optional body uses comma-delimited key:value pairs and AMI exposes additional arguments as event lines. A delimiter, empty value, variable expansion or conflicting header name can therefore change what the consumer sees. Preserve the exact sanitized emitted form and raw received message.

Channel snapshot fields, when present, describe the channel context at emission. Join Uniqueid and Linkedid according to their documented meaning, but do not infer a final call state from a transient snapshot.

Locate duplication at the first repeated boundary

Compare producer logs, raw AMI frames, parser output and storage rows using the application correlation key. Two producer invocations, producer retry, two active manager consumers, reconnect overlap and a repeated database write are different faults. Make the storage operation idempotent for the event contract rather than deleting unexplained rows after the fact.

Do not assume Asterisk replays custom events after reconnect. If the consumer missed a transition, reconcile from the authoritative application state or a suitable bounded snapshot.

Verify the outcome at its owner

A received UserEvent proves only that this custom message reached this consumer. Check remote answer, bridge or transfer state, recording completion, media quality and business-system completion at their respective owners. Correct or version the event contract when its name overstates what the producer actually knows.

No PBX, module, dialplan, manager session, event stream, channel, bridge, endpoint, packet, media stream, business system or live call was inspected or tested for this diagnostic.

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 branch-23-generated AMI UserEvent action, UserEvent event and UserEvent dialplan-application references, matching branch-22 references, plus the official AMI event-filtering, command-syntax and Manager TCP/IP material reviewed October 16, 2026; installed branch, module, dialplan, manager permissions, session mask, filters, transport, parser, retry policy, schema and application outcome remain deployment specific; no PBX, module, dialplan, manager session, event stream, channel, bridge, endpoint, packet, media stream, business system or live call was inspected or tested

Asterisk AMI UserEvent custom telemetry

Design application-owned UserEvent names, headers and correlation keys while keeping AMI action responses, dialplan emission, event delivery and downstream outcomes independently observable.

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 · Current Asterisk logging, runtime command, logger.conf, debug-collection, call-identifier and console-verbosity documentation reviewed September 30, 2026; no process, logger, trace, storage path or call tested

Asterisk logging without permanent debug overload

Map configured destinations, console levels, call identifiers and a bounded protocol trace without leaving sensitive debug collection active.

Read guide →
Guide

PBX logs and packet captures: useful evidence with limited exposure

Collect enough to diagnose a call while protecting identities, secrets and audio.

Read guide →
Hub

VoIP troubleshooting

Use symptoms and evidence to isolate registration, routing, media and device faults.

Explore topic →