RFC 4348: Real-Time Transport Protocol (RTP) Payload Format for the Variable-Rate Multimode Wideband (VMR-WB) Audio Codec
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 the Variable-Rate Multimode Wideband (VMR-WB) speech codec. The payload format is designed to be able to interoperate with existing VMR-WB transport formats on non-IP networks. A media type registration is included for VMR-WB RTP payload format. VMR-WB is a variable-rate multimode wideband speech codec that has a number of operating modes, one of which is interoperable with AMR-WB (i.e., RFC 3267) audio codec at certain rates. Therefore, provisions have been made in this document to facilitate and simplify data packet exchange between VMR-WB and AMR-WB in the interoperable mode with no transcoding function involved. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4348
- Published
- January 2006
- Authors
- S. Ahmadi
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 32
- Also known as
- —
- Updated by:
- RFC 4424
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 5993RTP Payload Format for Global System for Mobile Communications Half Rate (GSM-HR)Current
October 2010
- RFC 6569Guidelines for Development of an Audio Codec within the IETFCurrent
March 2012
- RFC 4351Real-Time Transport Protocol (RTP) Payload for Text Conversation Interleaved in an Audio StreamCurrent
January 2006
- RFC 4352RTP Payload Format for the Extended Adaptive Multi-Rate Wideband (AMR-WB+) Audio CodecCurrent
January 2006
- RFC 4353A Framework for Conferencing with the Session Initiation Protocol (SIP)Current
February 2006
- RFC 4355IANA Registration for Enumservices email, fax, mms, ems, and smsUpdated
January 2006
- RFC 4375Emergency Telecommunications Services (ETS) Requirements for a Single Administrative DomainCurrent
January 2006
- RFC 4321Problems Identified Associated with the Session Initiation Protocol's (SIP) Non-INVITE TransactionCurrent
January 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?