RFC 4788: Enhancements to RTP Payload Formats for EVRC Family Codecs
In plain English — editorial summary, not part of the RFC
This document updates the Enhanced Variable Rate Codec (EVRC) RTP payload formats defined in RFC 3558 with several enhancements and extensions. In particular, it defines support for the header-free and interleaved/bundled packet formats for the EVRC-B codec, a new compact bundled format for the EVRC and EVRC-B codecs, as well as discontinuous transmission (DTX) support for EVRC and EVRC-B-encoded speech transported via RTP. Voice over IP (VoIP) applications operating over low bandwidth dial-up and wireless networks require such enhancements for efficient use of the bandwidth. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4788
- Published
- January 2007
- Authors
- Q. Xie; R. Kapoor
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 22
- Also known as
- —
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 6884RTP Payload Format for the Enhanced Variable Rate Narrowband-Wideband Codec (EVRC-NW)Current
March 2013
- RFC 4780Management Information Base for the Session Initiation Protocol (SIP)Current
April 2007
- RFC 4776Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration InformationUpdated
November 2006
- RFC 4769IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling InformationUpdated
November 2006
- RFC 4759The ENUM Dip Indicator Parameter for the "tel" URICurrent
December 2006
- RFC 4825The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)Current
May 2007
- RFC 4826Extensible Markup Language (XML) Formats for Representing Resource ListsCurrent
May 2007
- RFC 4749RTP Payload Format for the G.729.1 Audio CodecUpdated
October 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?