RTP Payload Format for a 64 kbit/s Transparent Call
RFC 4040
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['realtime transport protocol']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "R. Kreuter": changed name from "Ruediger Kreuter" to "R. Kreuter", cleared country (was "81730 Munich, Germany"), changed order from "0" to "1" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2018-12-20
|
(System) | Received changes through RFC Editor sync (changed abstract to 'This document describes how to carry 64 kbit/s channel data transparently in RTP packets, using a … Received changes through RFC Editor sync (changed abstract to '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]') |
|
2005-05-03
|
Amy Vezza | State Changes to RFC Published from RFC Ed Queue by Amy Vezza |
|
2005-05-03
|
Amy Vezza | [Note]: 'RFC 4040' added by Amy Vezza |
|
2005-04-20
|
(System) | RFC published |