BCP 85

Get notified when:

An RFC is added to or removed from this BCP
A RFC within the collection changes status, obsoleted by, updates, updated by, or subseries.

BCPs are stable identifiers for Best Current Practices. A BCP may consist of a single RFC or a group of RFCs related to a specific IETF process or recommended guidelines. The collection may become empty as the BCP evolves.

RFC 3725: BCP 85: Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)

Best Current Practice

J. Rosenberg
J. Peterson
H. Schulzrinne
G. Camarillo

April 2004
IETF publication
Real-time Applications and Infrastructure Area

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.

BCP 85

Subscribe to BCP 85

RFC 3725: BCP 85: Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)

Abstract

Abstract