Asterisk call transfers and pickup
Identify the control path before troubleshooting a transfer. A phone's transfer button and a DTMF feature code can use different mechanisms. A setting that permits one path does not necessarily control the other.
Source-reviewed, 18 October 2026. Prepared from the cited documentation. Transfers and pickup have not been independently tested by Phone Guides. Scope: Asterisk 22 concepts and feature-code examples; device-button behaviour needs exact phone/firmware documentation.
Name the intended operation
| Operation | Intended behaviour |
|---|---|
| Blind transfer | Send the existing caller towards a new destination without an answered consultation first |
| Attended transfer | Consult the destination before completing the transfer |
| Ringing-call pickup | Answer an eligible call currently ringing elsewhere |
| Parking | Hold a call in a slot for later retrieval |
Do not use the words pickup and parking as if they described the same state. Each needs its own reachable routes and permissions.
Separate native phone transfers from feature codes
A phone may initiate a SIP transfer through its own controls. Asterisk's DTMF feature-code transfer uses configured feature strings while the parties are in the appropriate call state. For the latter path, the code must exist, the channel must permit that feature and the participants must be in the required answered/bridged state.
The official feature-code transfer guide describes those prerequisites. Preserve the distinction when reading Dial() options: lowercase t permits the called party's feature-code transfer, while uppercase T permits the calling party's. Those options do not enforce policy on every other transfer mechanism.
For an existing internal endpoint, the following illustrates granting the called party that feature-code permission:
Dial(PJSIP/6002,20,t)
This expression does not define the feature string, grant permission to the calling party, or configure the phone's own transfer button. Check the matching Dial reference and your actual features.conf/channel policy before applying it.
Design destination permissions
Record which destinations each participant may transfer to. Include provider callers, internal callers and application-originated channels. A transfer should not become an indirect route to a paid destination the caller could not dial directly.
For attended transfers, decide the behaviour when the consultation fails, the destination does not answer or the transferring user disconnects. Feature-code abort/completion settings and native phone actions need separate checking. Do not publish a generic sequence of button presses as a promise for an unverified phone model.
Restrict ringing-call pickup
Choose who may answer whose ringing calls. The branch-22 Pickup reference describes targeted and group-based forms. Group membership and a reachable pickup route are deliberate permissions, not merely convenience settings.
Check the relevant endpoint group options and any directed pickup context before publishing a site-specific configuration. A BLF button can combine state display, dialling and pickup actions; success of one part does not prove the others.
Reader checks
Record the initiating party, mechanism, source/destination and exact failure stage. In your own checks, exercise each permitted transfer direction, unanswered consultation, cancellation and an unauthorised destination. For pickup, check an allowed ringing call, a call outside the permitted group and a call that has already been answered.
Observe final channel clearing and reporting after completion. For feature codes that are not detected, review DTMF before changing transfer permissions. For delayed or missing media after a transfer, review NAT/RTP.
Return to Asterisk documentation.