BCP 85

RFC 3725

Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP), April 2004

File formats:
icon for text file icon for PDF icon for HTML
J. Rosenberg
J. Peterson
H. Schulzrinne
G. Camarillo
sipping (rai)

Cite this BCP: TXT  |  XML

Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC


Third party call control refers to the ability of one entity to create a call in which communication is actually between other parties. Third party call control is possible using the mechanisms specified within the Session Initiation Protocol (SIP). However, there are several possible approaches, each with different benefits and drawbacks. This document discusses best current practices for the usage of SIP for third party call control. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.

Advanced Search