Best Current Practices for Third Party Call Control in the Session Initiation Protocol
RFC 3725, “Best Current Practices for Third Party Call Control in the Session Initiation Protocol”, is a Best Current Practice document published in April 2004 by J. Rosenberg, J. Peterson, H. Schulzrinne, G. Camarillo. The canonical text is published by the RFC Editor.
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.
What “Best Current Practice” means
Documents the IETF community's recommended operational or procedural practice rather than a protocol specification.
The canonical text of RFC 3725 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3724 The Rise of the Middle and the Future of End-to-End: Reflections on the Evolution of the Internet Architecture
- RFC 3726 Requirements for Signaling Protocols
- RFC 3723 Securing Block Storage Protocols over IP
- RFC 3727 ASN.1 Module Definition for the LDAP and X.500 Component Matching Rules
- RFC 3722 String Profile for Internet Small Computer Systems Interface Names
- RFC 3728 Definitions of Managed Objects for Very High Speed Digital Subscriber Lines
- RFC 3721 Internet Small Computer Systems Interface Naming and Discovery
- RFC 3729 Application Performance Measurement MIB