RFC 4579: Session Initiation Protocol (SIP) Call Control - Conferencing for User Agents
In plain English — editorial summary, not part of the RFC
This specification defines conferencing call control features for the Session Initiation Protocol (SIP). This document builds on the Conferencing Requirements and Framework documents to define how a tightly coupled SIP conference works. The approach is explored from the perspective of different user agent (UA) types: conference-unaware, conference-aware, and focus UAs. The use of Uniform Resource Identifiers (URIs) in conferencing, OPTIONS for capabilities discovery, and call control using REFER are covered in detail with example call flow diagrams. The usage of the isfocus feature tag is defined. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC4579
- Published
- August 2006
- Authors
- A. Johnston; O. Levin
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- rai
- Pages
- 43
- Also known as
- BCP119
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4730A Session Initiation Protocol (SIP) Event Package for Key Press Stimulus (KPML)Current
November 2006
- RFC 4916Connected Identity in the Session Initiation Protocol (SIP)Current
June 2007
- RFC 4189Requirements for End-to-Middle Security for the Session Initiation Protocol (SIP)Current
October 2005
- RFC 3840Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)Current
August 2004
- RFC 3329Security Mechanism Agreement for the Session Initiation Protocol (SIP)Updated
January 2003
- RFC 3327Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent ContactsUpdated
December 2002
- RFC 3324Short Term Requirements for Network Asserted IdentityCurrent
December 2002
- RFC 4409Message Submission for MailObsoleted
April 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?