RFC 6231: An Interactive Voice Response (IVR) Control Package for the Media Control Channel Framework
In plain English — editorial summary, not part of the RFC
This document defines a Media Control Channel Framework Package for Interactive Voice Response (IVR) dialog interaction on media connections and conferences. The package defines dialog management request elements for preparing, starting, and terminating dialog interactions, as well as associated responses and notifications. Dialog interactions are specified in a dialog language. This package defines a lightweight IVR dialog language (supporting prompt playback, runtime controls, Dual-Tone Multi-Frequency (DTMF) collection, and media recording) and allows other dialog languages to be used. The package also defines elements for auditing package capabilities and IVR dialogs. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6231
- Published
- May 2011
- Authors
- S. McGlashan; T. Melanchuk; C. Boulton
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 134
- Also known as
- —
- Updated by:
- RFC 6623
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 6230Media Control Channel FrameworkCurrent
May 2011
- RFC 6225Dynamic Host Configuration Protocol Options for Coordinate-Based Location Configuration InformationCurrent
July 2011
- RFC 6222Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)Obsoleted
April 2011
- RFC 6271Requirements for SIP-Based Session PeeringCurrent
June 2011
- RFC 6188The Use of AES-192 and AES-256 in Secure RTPCurrent
March 2011
- RFC 6185RTP Payload Format for H.264 Reduced-Complexity Decoding Operation (RCDO) VideoCurrent
May 2011
- RFC 6184RTP Payload Format for H.264 VideoCurrent
May 2011
- RFC 6280An Architecture for Location and Location Privacy in Internet ApplicationsCurrent
July 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?