RFC 3725 (rfc3725) - Page 1 of 31

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

Alternative Format: Original Text Document
Next >
Network Working Group                                       J. Rosenberg
Request for Comments: 3725                                   dynamicsoft
BCP: 85                                                      J. Peterson
Category: Best Current Practice                                  Neustar
                                                          H. Schulzrinne
                                                     Columbia University
                                                            G. Camarillo
                                                                Ericsson
                                                              April 2004


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

Status of this Memo

   This document specifies an Internet Best Current Practices for the
   Internet Community, and requests discussion and suggestions for
   improvements.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).  All Rights Reserved.

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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Definitions  . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  3pcc Call Establishment  . . . . . . . . . . . . . . . . . .   3
       4.1.  Flow I . . . . . . . . . . . . . . . . . . . . . . . .   4
       4.2.  Flow II. . . . . . . . . . . . . . . . . . . . . . . .   5
       4.3.  Flow III . . . . . . . . . . . . . . . . . . . . . . .   7
       4.4.  Flow IV. . . . . . . . . . . . . . . . . . . . . . . .   8
   5.  Recommendations  . . . . . . . . . . . . . . . . . . . . . .   9
   6.  Error Handling . . . . . . . . . . . . . . . . . . . . . . .  10
   7.  Continued Processing . . . . . . . . . . . . . . . . . . . .  11
   8.  3pcc and Early Media . . . . . . . . . . . . . . . . . . . .  13



Rosenberg, et al.        Best Current Practice
Next >