RFC 5244: Definition of Events for Channel-Oriented Telephony Signalling
In plain English — editorial summary, not part of the RFC
This memo updates RFC 4733 to add event codes for telephony signals used for channel-associated signalling when carried in the telephony event RTP payload. It supersedes and adds to the original assignment of event codes for this purpose in Section 3.14 of RFC 2833. As documented in Appendix A of RFC 4733, some of the RFC 2833 events have been deprecated because their specification was ambiguous, erroneous, or redundant. In fact, the degree of change from Section 3.14 of RFC 2833 is such that implementations of the present document will be fully backward compatible with RFC 2833 implementations only in the case of full ABCD-bit signalling. This document expands and improves the coverage of signalling systems compared to RFC 2833. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5244
- Published
- June 2008
- Authors
- H. Schulzrinne; T. Taylor
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 23
- Also known as
- —
- Updates:
- RFC 4733
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5239A Framework for Centralized ConferencingCurrent
June 2008
- RFC 5261An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) SelectorsCurrent
September 2008
- RFC 5262Presence Information Data Format (PIDF) Extension for Partial PresenceCurrent
September 2008
- RFC 5263Session Initiation Protocol (SIP) Extension for Partial Notification of Presence InformationUpdated
September 2008
- RFC 5264Publication of Partial Presence InformationCurrent
September 2008
- RFC 5219A More Loss-Tolerant RTP Payload Format for MP3 AudioCurrent
February 2008
- RFC 5215RTP Payload Format for Vorbis Encoded AudioCurrent
August 2008
- RFC 5278IANA Registration of Enumservices for Voice and Video MessagingUpdated
July 2008
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?