RFC 4867: RTP Payload Format and File Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) Audio Codecs
In plain English — editorial summary, not part of the RFC
This document specifies a Real-time Transport Protocol (RTP) payload format to be used for Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-WB) encoded speech signals. The payload format is designed to be able to interoperate with existing AMR and AMR-WB transport formats on non-IP networks. In addition, a file format is specified for transport of AMR and AMR-WB speech data in storage mode applications such as email. Two separate media type registrations are included, one for AMR and one for AMR-WB, specifying use of both the RTP payload format and the storage format. This document obsoletes RFC 3267. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4867
- Published
- April 2007
- Authors
- J. Sjoberg; M. Westerlund; A. Lakaniemi; Q. Xie
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 59
- Also known as
- —
- Obsoletes:
- RFC 3267
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5346Operational Requirements for ENUM-Based Softswitch UseCurrent
October 2008
- RFC 4103RTP Payload for Text ConversationUpdated
June 2005
- RFC 3824Using E.164 numbers with the Session Initiation Protocol (SIP)Current
June 2004
- RFC 2793RTP Payload for Text ConversationObsoleted
May 2000
- RFC 3491Nameprep: A Stringprep Profile for Internationalized Domain Names (IDN)Obsoleted
March 2003
- RFC 3489STUN - Simple Traversal of User Datagram Protocol (UDP) Through Network Address Translators (NATs)Obsoleted
March 2003
- RFC 3413Simple Network Management Protocol (SNMP) ApplicationsCurrent
December 2002
- RFC 3406Uniform Resource Names (URN) Namespace Definition MechanismsObsoleted
October 2002
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?