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

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.

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

Freeze one request and one observed symptom

Record node, release, manager identity and permissions, ActionID, literal Channel field, exact Channel, Uniqueid, Linkedid, bridge peers, creation time, application, requested Cause, raw response, request events, final events, event filters, handler events and synchronized timestamps.

Classify the first symptom as unknown or denied action, no match, multiple matches, stale channel, wrong leg, accepted request with no final event, unexpected cause, linked leg surviving, handler delay or endpoint result mismatch. Do not combine several calls into one timeline.

Reject stale and overbroad targets first

Resolve the channel again immediately before the action and require the same Uniqueid. If the Channel field is a regular expression, enumerate every match at send time and stop if its scope is broader than the approved maintenance set.

Transfers, Local optimization, queue dialing and completed channels can invalidate a cached name. A successful response against a broad pattern does not establish which channels matched, and a caller number does not identify one channel lifetime.

Separate authorization from CLI-equivalent access

Confirm the dedicated Hangup action is present and the manager has only the required write authority. The AMI specification warns that Command authorization can execute CLI operations that overlap other action classes, including channel request hangup.

Do not grant Command or write=all to repair a denied Hangup action. Treat unavailable action, denied action and accepted action as different boundaries, and preserve the running manager configuration and action inventory rather than assuming a template is loaded.

Correlate request and final events by Uniqueid

Match the response by ActionID, then HangupRequest or SoftHangupRequest and final Hangup by exact Uniqueid. Preserve Cause, Cause-txt, TechCause and the event-filter state. A request event can precede dialplan cleanup and final disposal.

If no final event is visible, check whether the client filtered CALL events, disconnected, started listening late or followed the wrong replacement channel. Do not resend destructive Hangup requests merely because one observer missed an event.

Audit cause translation, handlers and every linked leg

Compare the requested numeric cause with the final Asterisk cause and technology-specific evidence without assuming a universal SIP result. Then inspect hangup-handler and h-extension execution on the exact channel, including any slow external dependency.

Inventory all channels sharing the Linkedid before and after the action. A surviving transfer, bridge peer or Local leg does not mean the selected Uniqueid survived; a final event for the selected leg does not prove the entire business call ended.

Repair only the first proved boundary and retest once

Correct only the demonstrated fault: stale identity, broad expression, missing authority, event filter, cause assumption, handler delay or call-flow owner. Retest on one disposable authorized call with a negative case and synchronized capture.

Use PJSIPHangup only when its documented incoming-PJSIP final-response semantics fit the call phase; do not swap it for generic Hangup by name alone. No PBX, manager session, action, regular expression, channel, event, endpoint, packet, signaling exchange, media stream or live call was inspected or tested.

Sources & applicability

Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.

Examples require adaptation to your topology. No live PBX or hardware testing is claimed.

Continue your research

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 →
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 Latest API CHANNEL_EXISTS, CHANNELS and CHANNEL references, CLI channel-operation and Local-channel optimization documentation, AMI CoreShowChannels surfaces and the upstream func_channel implementation were reviewed October 19, 2026. The generated API pages reported branch 23; installed branch, loaded modules, channel drivers, names, unique IDs, linked IDs, Local optimization, permissions, timing and call outcomes remain deployment specific. No PBX, module, dialplan, channel, bridge, manager session, packet, media stream or live call was inspected or tested

Asterisk channel inventory, identity and lifetime

Treat a channel list as a changing observation, distinguish name from unique identity, and revalidate the exact leg before an authorized operation.

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 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 HANGUPCAUSE, HANGUPCAUSE_KEYS, HangupCauseClear, Dial and CHANNEL references plus the project mapping table reviewed October 6, 2026; exact behavior still depends on the installed Asterisk branch, channel driver, dialplan and call path

Asterisk hangup causes: preserve each called-channel result

Interpret Dial status, per-channel technology causes, translated Asterisk causes and hangup source without collapsing parallel or sequential call attempts into one reason.

Read guide →
Guide · Asterisk hangup-handler, CHANNEL, AMI event, hangup-cause and Return documentation reviewed October 12, 2026; exact events and channel behavior remain dependent on the installed Asterisk branch, modules, dialplan, channel technology and observer permissions, and no PBX, dialplan, channel, handler stack, event, record, endpoint, call or teardown path was inspected or tested

Asterisk hangup handlers: channel stack, order and teardown evidence

Attach bounded hangup subroutines to the correct channel, preserve LIFO stack order and prove push, pop, run and final hangup separately.

Read guide →
Guide · Current branch-23 PJSIPHangup, generic Hangup, Hangup, HangupRequest and SoftHangupRequest AMI references, the dialplan PJSIPHangup application, AMI v2 channel-lifetime specification, hangup-cause guidance and event-filtering guidance were reviewed October 21, 2026. PJSIPHangup is documented since Asterisk 18.21.0, 20.6.0 and 21.1.0; installed branch, loaded chan_pjsip support, manager permissions and filters, exact channel lifetime, bridge membership, prior final response, cause translation, upstream signaling and peer interpretation remain deployment specific. No PBX, module, manager account, channel, bridge, dialog, SIP response, packet, endpoint, media stream or live call was inspected or tested

Asterisk AMI PJSIPHangup: response code and channel-lifecycle evidence

Use PJSIPHangup only on the intended incoming PJSIP channel before another final response, then verify the requested response, translated cause and terminal channel event separately.

Read guide →
Troubleshooting · Current branch-23 PJSIPHangup, generic Hangup, Hangup, HangupRequest and SoftHangupRequest AMI references, the dialplan PJSIPHangup application, AMI v2 channel-lifetime specification, hangup-cause guidance and event-filtering guidance were reviewed October 21, 2026. PJSIPHangup is documented since Asterisk 18.21.0, 20.6.0 and 21.1.0; installed branch, loaded chan_pjsip support, manager permissions and filters, exact channel lifetime, bridge membership, prior final response, cause translation, upstream signaling and peer interpretation remain deployment specific. No PBX, module, manager account, channel, bridge, dialog, SIP response, packet, endpoint, media stream or live call was inspected or tested

Asterisk AMI PJSIPHangup uses the wrong channel or response, or no final event appears

Trace installed-version support, exact channel identity, pre-final-response timing, action framing, cause translation, event filtering and the SIP transaction before retrying.

Read guide →
Troubleshooting · 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 events are missing, filtered, delayed or duplicated

Locate the first divergence among manager permissions, the per-session event mask, configured and dynamic filters, HTTP WaitEvent queueing, TCP reads, reconnects, parsing and downstream deduplication.

Read guide →
Troubleshooting · Current Asterisk Latest API CHANNEL_EXISTS, CHANNELS and CHANNEL references, CLI channel-operation and Local-channel optimization documentation, AMI CoreShowChannels surfaces and the upstream func_channel implementation were reviewed October 19, 2026. The generated API pages reported branch 23; installed branch, loaded modules, channel drivers, names, unique IDs, linked IDs, Local optimization, permissions, timing and call outcomes remain deployment specific. No PBX, module, dialplan, channel, bridge, manager session, packet, media stream or live call was inspected or tested

Asterisk channel exists, then disappears or maps to the wrong call

Freeze one observation window, distinguish channel name, Uniqueid and Linkedid, then locate creation, rename, Local optimization, bridge change or hangup.

Read guide →
Troubleshooting · Asterisk hangup-handler, CHANNEL, AMI event, hangup-cause and Return documentation reviewed October 12, 2026; exact events and channel behavior remain dependent on the installed Asterisk branch, modules, dialplan, channel technology and observer permissions, and no PBX, dialplan, channel, handler stack, event, record, endpoint, call or teardown path was inspected or tested

Asterisk hangup handler is missing, duplicated, out of order or slow

Trace one channel from handler push and stack order through invocation, Return, teardown timing, final cause and downstream record.

Read guide →
Hub

VoIP troubleshooting

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

Explore topic →