RFC 4722: Media Server Control Markup Language (MSCML) and Protocol
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5022.
Current version: RFC 5022 — Media Server Control Markup Language (MSCML) and Protocol
In plain English — editorial summary, not part of the RFC
Media Server Control Markup Language (MSCML) is a markup language used in conjunction with SIP to provide advanced conferencing and interactive voice response (IVR) functions. MSCML presents an application-level control model, as opposed to device-level control models. One use of this protocol is for communications between a conference focus and mixer in the IETF SIP Conferencing Framework. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4722
- Published
- November 2006
- Authors
- J. Van Dyke; E. Burger; A. Spitzer
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 81
- Also known as
- —
- Obsoleted by:
- RFC 5022
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5552SIP Interface to VoiceXML Media ServicesCurrent
May 2009
- RFC 5379Guidelines for Using the Privacy Mechanism for SIPCurrent
February 2010
- RFC 3976Interworking SIP and Intelligent Network (IN) ApplicationsCurrent
January 2005
- RFC 6193Media Description for the Internet Key Exchange Protocol (IKE) in the Session Description Protocol (SDP)Current
April 2011
- RFC 8433A Simpler Method for Resolving Alert-Info URNsCurrent
August 2018
- RFC 4769IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling InformationUpdated
November 2006
- RFC 4787Network Address Translation (NAT) Behavioral Requirements for Unicast UDPUpdated
January 2007
- RFC 4825The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)Current
May 2007
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?