RFC 5589: Session Initiation Protocol (SIP) Call Control - Transfer
In plain English — editorial summary, not part of the RFC
This document describes providing Call Transfer capabilities in the Session Initiation Protocol (SIP). SIP extensions such as REFER and Replaces are used to provide a number of transfer services including blind transfer, consultative transfer, and attended transfer. This work is part of the SIP multiparty call control framework. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC5589
- Published
- June 2009
- Authors
- R. Sparks; A. Johnston; D. Petrie
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- rai
- Pages
- 58
- Also known as
- BCP149
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5627Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)Current
October 2009
- RFC 3892The Session Initiation Protocol (SIP) Referred-By MechanismUpdated
September 2004
- RFC 7255Using the International Mobile station Equipment Identity (IMEI) Uniform Resource Name (URN) as an Instance IDCurrent
May 2014
- RFC 5621Message Body Handling in the Session Initiation Protocol (SIP)Updated
September 2009
- RFC 5552SIP Interface to VoiceXML Media ServicesCurrent
May 2009
- RFC 5629A Framework for Application Interaction in the Session Initiation Protocol (SIP)Current
October 2009
- RFC 5630The Use of the SIPS URI Scheme in the Session Initiation Protocol (SIP)Current
October 2009
- RFC 5767User-Agent-Driven Privacy Mechanism for SIPCurrent
April 2010
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?