RFC 4040: RTP Payload Format for a 64 kbit/s Transparent Call
In plain English — editorial summary, not part of the RFC
This document describes how to carry 64 kbit/s channel data transparently in RTP packets, using a pseudo-codec called "Clearmode". It also serves as registration for a related MIME type called "audio/clearmode". "Clearmode" is a basic feature of VoIP Media Gateways. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4040
- Published
- April 2005
- Authors
- R. Kreuter
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4421RTP Payload Format for Uncompressed Video: Additional Colour Sampling ModesCurrent
February 2006
- RFC 4855Media Type Registration of RTP Payload FormatsUpdated
February 2007
- RFC 4856Media Type Registration of Payload Formats in the RTP Profile for Audio and Video ConferencesCurrent
February 2007
- RFC 5109RTP Payload Format for Generic Forward Error CorrectionCurrent
December 2007
- RFC 5215RTP Payload Format for Vorbis Encoded AudioCurrent
August 2008
- RFC 4815RObust Header Compression (ROHC): Corrections and Clarifications to RFC 3095Current
February 2007
- RFC 4032Update to the Session Initiation Protocol (SIP) Preconditions FrameworkCurrent
March 2005
- RFC 4028Session Timers in the Session Initiation Protocol (SIP)Current
May 2005
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?