RFC 6504: Centralized Conferencing Manipulation Protocol (CCMP) Call Flow Examples
In plain English — editorial summary, not part of the RFC
This document provides detailed call flows for the scenarios documented in the Framework for Centralized Conferencing (XCON) (RFC 5239) and in the XCON scenarios (RFC 4597). The call flows document the use of the interface between a conference control client and a conference control server using the Centralized Conferencing Manipulation Protocol (CCMP) (RFC 6503). The objective is to provide detailed examples for reference by both protocol researchers and developers. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6504
- Published
- March 2012
- Authors
- M. Barnes; L. Miniero; R. Presta; S P. Romano
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 78
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6503Centralized Conferencing Manipulation ProtocolCurrent
March 2012
- RFC 6505A Mixer Control Package for the Media Control Channel FrameworkCurrent
March 2012
- RFC 6502Conference Event Package Data Format Extension for Centralized Conferencing (XCON)Current
March 2012
- RFC 6501Conference Information Data Model for Centralized Conferencing (XCON)Current
March 2012
- RFC 6447Filtering Location Notifications in the Session Initiation Protocol (SIP)Current
January 2012
- RFC 6567Problem Statement and Requirements for Transporting User-to-User Call Control Information in SIPCurrent
April 2012
- RFC 6406Session PEERing for Multimedia INTerconnect (SPEERMINT) ArchitectureCurrent
November 2011
- RFC 6405Voice over IP (VoIP) SIP Peering Use CasesCurrent
November 2011
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?