Asterisk AMI transfer succeeds but the call is wrong

Freeze one transfer chronology

Record installed branch, timestamp, manager identity, action name, ActionID when the action supports it, supplied channel values, stable channel IDs, bridge IDs, destination context, extension and priority, action response, transfer events, dialplan execution and caller-visible result.

Classify the first symptom: rejection, accepted action with no transfer event, wrong leg moved, wrong peer transferred, wrong context or priority, transfer event failure, Success with busy or no answer, wrong connected identity, missing recording, one-way audio or teardown.

Verify the installed action and authorization

Check local AMI action help, loaded module state and the manager account read and write permissions on the running branch. Correlate the exact request and response; do not assume that a later generated reference proves action availability on an older or packaged host.

Separate transport, parsing, authentication, authorization and action-level failures before changing dialplan or endpoint settings.

Re-resolve the live channel and bridge

Map every supplied channel to one intended live party at mutation time and retain Uniqueid and Linkedid where available. For BlindTransfer, prove the channels currently bridged to the supplied channel. For Atxfer, prove that the supplied leg is the transferer. For dual-leg Redirect, resolve both channel destinations independently.

Account for rename, Local-channel optimization, masquerade, hangup and replacement. Retrying a stale name can move a different or nonexistent leg.

Prove the complete dialplan destination

For Redirect, validate context, extension and priority for each requested leg. For BlindTransfer and Atxfer, validate the destination context and extension and preserve the matched dialplan execution. Reject an implicit context, an unreviewed caller-controlled target or a primary-leg success that hides an invalid extra-leg destination.

A transfer event Success proves dialplan placement, not target contact. Continue through outbound selection, target response and final bridge.

Interpret the event without overclaiming

For BlindTransfer, preserve Result, IsExternal, transferer, transferee, bridge and destination. For AttendedTransfer, preserve original and second transferer channels and bridges, transferee, transfer target and DestType; missing bridge fields can be valid when a leg ran an application instead of joining a bridge.

Treat Fail, Invalid and Not Permitted as different boundaries. Treat Success as expected dialplan placement only, exactly as the current event documentation states.

Follow topology into identity, recording and media

After dialplan entry, trace target progress, final bridge membership, connected-line updates, recording segments, hangup causes and both media directions. A correct transfer event can precede busy, no answer, routing rejection, early teardown or unusable audio.

Do not repair a control-contract or destination error by changing codecs, NAT or registration. No AMI session, user, permission, host, manager action, channel, bridge, dialplan destination, packet, media stream or live call was inspected or tested for this diagnostic.

Follow accepted transfer into cancellation and recovery

The CancelAtxfer diagnostic covers abort availability, active transferer selection, re-bridging and callback timing.

Check whether a Local identity optimized away

The Local optimization diagnostic distinguishes intended name disappearance from the wrong surviving party set.

Exclude a stale pre-transfer channel snapshot

The channel snapshot diagnostic re-resolves the transfer leg and current bridge before mutation.

Check the transfer-event path independently

The AMI event diagnostic traces authorization, filters, transport and downstream deduplication.