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.
Watch the explanation
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.
The player loads only when you choose Watch here. Playback uses YouTube’s privacy-enhanced embed; YouTube processes playback data.
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.
The player loads only when you choose Watch here. Playback uses YouTube’s privacy-enhanced embed; YouTube processes playback data.
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.