metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 4733: RTP Payload for DTMF Digits, Telephony Tones, and Telephony Signals

Still current, but amended. Parts of this document are changed or extended by RFC 4734, RFC 5244. Read both.

In plain English — editorial summary, not part of the RFC

This memo describes how to carry dual-tone multifrequency (DTMF) signalling, other tone signals, and telephony events in RTP packets. It obsoletes RFC 2833. This memo captures and expands upon the basic framework defined in RFC 2833, but retains only the most basic event codes. It sets up an IANA registry to which other event code assignments may be added. Companion documents add event codes to this registry relating to modem, fax, text telephony, and channel-associated signalling events. The remainder of the event codes defined in RFC 2833 are conditionally reserved in case other documents revive their use. This document provides a number of clarifications to the original document. However, it specifically differs from RFC 2833 by removing the requirement that all compliant implementations support the DTMF events. Instead, compliant implementations taking part in out-of-band negotiations of media stream content indicate what events they support. This memo adds three new procedures to the RFC 2833 framework: subdivision of long events into segments, reporting of multiple events in a single packet, and the concept and reporting of state events. [STANDARDS-TRACK]

Document record

Document ID
RFC4733
Published
December 2006
Authors
H. Schulzrinne; T. Taylor
Status
PROPOSED STANDARD
Stream
IETF
Area
rai
Pages
49
Also known as
—
Obsoletes:
RFC 2833
Updated by:
RFC 4734, RFC 5244

Topics

Standards lineage

This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.

  1. RFC 2833 (2000)
  2. RFC 4733 (2006)
  3. RFC 4734 (2006) ✓

Read the full history of Definition of Events for Modem, Fax, and Text Telephony Signals →

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/4733-rtp-payload-for-dtmf-digits-telephony-tones-and-telephony-signals