Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)
Metadata
- Publisher
- IETF
- Doc Type
- Best Practice
- Pages
- 31
- Abstract
- 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.
- Publication Date
- 2004-04-01
- Status Note
- Best Current Practice
- DOI
10.17487/RFC3725- Link
- https://doi.org/10.17487/RFC3725
- Author(s)
- Jonathan RosenbergJon PetersonHenning SchulzrinneGonzalo Camarillo
- Keyword(s)
- 3PCC, Third Party Call Control, SIP
Latest version of IETF RFC 3725
Document Versions — IETF RFC 3725
-
▶ IETF RFC 3725 (2004-04-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3261 [Active*]
- IETF RFC 3262 [Active*]
- IETF RFC 3264 [Active*]
- IETF RFC 3311 [Active*]
- RFC3312 — 2 EXTERNAL
- IETF RFC 3326 [Active*]
Bibliographic Reference(s)
- Andreasen, F., Baugher, M. and D. Wing, "SDP Security Descriptions for Media Streams", Work in Progress, October 2003. EXTERNAL
- Lennox, J., Wu, X. and H. Schulzrinne, "CPL: A Language for User Control of Internet Telephony Services", Work in Progress, August 2003. EXTERNAL
- IETF RFC 2848 [Active*]
- IETF RFC 3550 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC3725.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 3725, Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC3725
Snippet:
IETF RFC 3725, Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC3725
HTML (ISO 690 compliant)
Preview:
IETF RFC 3725, Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP). Available at https://doi.org/10.17487/RFC3725
Snippet:
<span class="citation"><cite>IETF RFC 3725</cite>, Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP). Available at <a href="https://doi.org/10.17487/RFC3725" target="_blank" rel="noopener">https://doi.org/10.17487/RFC3725</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 3725, Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)
doi: 10.17487/RFC3725
url: https://doi.org/10.17487/RFC3725
doi: 10.17487/RFC3725
url: https://doi.org/10.17487/RFC3725
Snippet:
<li> <cite id="bib-rfc3725">IETF RFC 3725</cite>, Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP) <span class="doi">10.17487/RFC3725</span> </li>
Referenced By
- IETF RFC 3891 [Active*]
- IETF RFC 4006 [Superseded*]
- IETF RFC 4145 [Active*]
- IETF RFC 4235 [Active*]
- IETF RFC 4353 [Active*]
- IETF RFC 4975 [Active*]
- IETF RFC 5630 [Active*]
- IETF RFC 6230 [Active*]