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

SIP REFER and transfers: acceptance versus completion

Follow transfer requests and their outcome notifications without assuming a 202 response means the transfer succeeded.

Reviewed 2026-10-16SIP standards; extension support depends on both peersIntermediateDocumentation based · not lab tested

What REFER requests

REFER asks a recipient to contact the resource identified in Refer-To. In telephony this commonly initiates transfer, but REFER is a request mechanism rather than a guarantee that the destination answers. The recipient may reject the request, accept it and fail later, or complete the requested action. A transfer crosses authorization boundaries. The recipient must decide whether the requesting party may cause a call to the supplied destination. An external number in Refer-To should not bypass the PBX's normal outbound permissions.

Follow the result

In the base REFER mechanism, accepting the request establishes an implicit subscription to its progress. NOTIFY messages can carry a SIP status fragment describing the outcome. Read the subscription and the resulting call attempt alongside the original dialog. A successful response to REFER acknowledges that request. A subsequent NOTIFY can still report a failed target call. Conversely, some deployments use extensions that change subscription behavior; record the negotiated features before declaring a missing NOTIFY a fault.

Blind and attended transfer checks

A blind transfer sends the caller toward a destination without first consulting it. Attended transfer commonly needs additional dialog replacement behavior, including the Replaces extension; implementation support must be checked at each border. Test internal-to-internal, internal-to-external and externally originated calls separately. Include busy, no-answer and rejected destinations, and verify what happens to the original caller when transfer fails. Compare signaling success with audio continuity and caller identification. Where a provider does not support endpoint-driven transfer, a PBX can implement transfer locally with different signaling on its trunk leg.

Preserve the registered 429 referrer-identity branch

RFC 3892's SIP 429 response can reject a REFER or its triggered request when a valid Referred-By token is required. Follow the REFER, token, referenced request and NOTIFY sipfrag instead of interpreting the number as an HTTP-style rate limit.

Trace CCAI Platform escalation beyond the REFER request

Google documents SIP REFER for configured CCAI Platform BYOC transfers. The BYOC record and paired diagnostic keep the request, response, replacement dialog, header mapping, human answer and media result separate.

Keep AMI transfer evidence separate from SIP REFER

The AMI transfer-control guide uses Asterisk manager actions and transfer events; a native protocol transfer remains a distinct signaling path.

Watch the explanation

Yealink T54W Phone Tutorial｜UD Voice Video GuideUnbound Digital · 11:22 · Version-specific

Covers the T54W controls and everyday calling tasks, including attended versus blind transfer, conference management, Wi-Fi and Bluetooth. Useful for onboarding phone users.

Read applicability and editorial notes →
Watch this video here

T54W demonstration on UD Voice in 2022. The video title and narration identify T54W; its description contains copied references to other models. Review used the available transcript and primary references; audio and screen readability remain unverified.

Open on YouTube ↗

The player loads only when you choose Watch here. Playback uses YouTube’s privacy-enhanced embed; YouTube processes playback data.

Fanvil V64 on Elevate: calls, conferences and Call FlipVersion-specific

Follow a complete working-day sequence on a provisioned V64: take a waiting call, consult before transferring, manage a conference and move a call to another device. The useful distinction is between controls on the desk phone and features supplied by the hosted account. Read the parking guide alongside the demonstration to understand why a held call and a parked call behave differently.

Read applicability and editorial notes →
Watch this video here

Elevate service configuration on a Fanvil V64; the linked Loffler reference provides a written example of the same service features. Review used the available transcript and primary references; audio and screen readability remain unverified.

Open on YouTube ↗

The player loads only when you choose Watch here. Playback uses YouTube’s privacy-enhanced embed; YouTube processes playback data.

Explore all 5 related videos →

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

Reference · SIP standards; extension support depends on both peers

SIP SUBSCRIBE and NOTIFY: presence, BLF and event state

Separate event subscriptions from registration and identify stale phone indicators.

Read guide →
Guide · FreePBX 17 / Debian 12; Sangoma Feature Codes, Misc Applications and Misc Destinations guidance, FreePBX Misc Applications 17.0.3 release/17.0 metadata and current Asterisk dialplan inspection documentation reviewed October 11, 2026; installed module UI, generated dialplan and endpoint digit handling require local confirmation

FreePBX feature codes

Avoid dialplan collisions and keep phone buttons aligned with the enabled feature codes.

Read guide →
Troubleshooting · RFC 3515, RFC 5589 and current Asterisk transfer documentation reviewed October 5, 2026; the September 16, 2026 Asterisk issue is an open single-environment report, not a reproduced or universal defect

SIP REFER transfer accepted but the call does not connect

Trace the actual transfer mechanism, REFER authorization, accepted request, notification subscription, referred call leg, attended-dialog replacement and final bridge separately.

Read guide →
SIP response reference · IANA's SIP response-code registry, RFC 3892, RFC 6585, Skyetel's current SIP Registration limitations and Asterisk's current outbound-registration and diagnostic guidance were reviewed October 8, 2026; no provider account, PBX, registration object, referral, token, credential, request rate, response, retry timer, availability result or call was inspected or tested

SIP 429 Provide Referrer Identity

The registered SIP 429 asks for valid referrer identity; it is not HTTP 429 Too Many Requests, even when a provider reuses the number for a local registration policy.

Read guide →
Diagnostic · IANA's SIP response-code registry, RFC 3892, RFC 6585, Skyetel's current SIP Registration limitations and Asterisk's current outbound-registration and diagnostic guidance were reviewed October 8, 2026; no provider account, PBX, registration object, referral, token, credential, request rate, response, retry timer, availability result or call was inspected or tested

A provider returns SIP 429 Too Many Requests

Preserve the method, reason phrase and responder, then separate a provider-local registration throttle from SIP 429's registered referrer-identity meaning.

Read guide →
Provider research · Current first-party Google Cloud CCAI Platform BYOC, IP allow-list, location, SIP URI, high-availability, virtual-agent escalation and telephony-partner documentation reviewed October 9, 2026; the public IP allow-list page is dated October 7, 2026 and must be re-read at each change window; no CCAI Platform instance, license, support case, carrier, SBC, FQDN, address, certificate, firewall, route, number, header, SIP transaction, transfer, media stream, emergency workflow, price, capacity, availability, compatibility or call was inspected or tested

Google Cloud CCAI Platform BYOC: carrier and SIP-edge boundaries

Connect an existing carrier or enterprise SBC to CCAI Platform while keeping instance activation, call direction, authentication, regional serviceability, signaling, media and transfer ownership separate.

Read guide →
Troubleshooting · Current first-party Google Cloud CCAI Platform BYOC, IP allow-list, location, SIP URI, high-availability, virtual-agent escalation and telephony-partner documentation reviewed October 9, 2026; the public IP allow-list page is dated October 7, 2026 and must be re-read at each change window; no CCAI Platform instance, license, support case, carrier, SBC, FQDN, address, certificate, firewall, route, number, header, SIP transaction, transfer, media stream, emergency workflow, price, capacity, availability, compatibility or call was inspected or tested

Google Cloud CCAI Platform BYOC call fails or has no audio

Trace one failed BYOC call through instance activation, direction, unique SIP FQDN, directional authentication, route, header mapping, signaling and media before broadening an allowlist.

Read guide →
Guide · Current Asterisk branch-23-generated AMI Redirect, BlindTransfer, Atxfer and transfer-event references plus branch 22 action references reviewed October 16, 2026; installed branch, loaded manager actions, AMI user permissions, bridge transfer policy, live channel identity, dialplan destination, event delivery, signaling, connected-line identity and media remain deployment specific; no AMI session, user, permission, host, manager action, channel, bridge, dialplan destination, packet, media stream or live call was inspected or tested

Asterisk AMI transfer control: Redirect, BlindTransfer and Atxfer

Choose the manager action that matches the intended transfer and correlate acknowledgement, bridge events, dialplan entry, target result and media.

Read guide →
Troubleshooting · Current Asterisk branch-23-generated AMI Redirect, BlindTransfer, Atxfer and transfer-event references plus branch 22 action references reviewed October 16, 2026; installed branch, loaded manager actions, AMI user permissions, bridge transfer policy, live channel identity, dialplan destination, event delivery, signaling, connected-line identity and media remain deployment specific; no AMI session, user, permission, host, manager action, channel, bridge, dialplan destination, packet, media stream or live call was inspected or tested

Asterisk AMI transfer succeeds but the call is wrong

Find the first divergence among manager authorization, action contract, live channel, bridge ownership, dialplan entry, target result and final media.

Read guide →