RFC 5369: Framework for Transcoding with the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document defines a framework for transcoding with SIP. This framework includes how to discover the need for transcoding services in a session and how to invoke those transcoding services. Two models for transcoding services invocation are discussed: the conference bridge model and the third-party call control model. Both models meet the requirements for SIP regarding transcoding services invocation to support deaf, hard of hearing, and speech-impaired individuals. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5369
- Published
- October 2008
- Authors
- G. Camarillo
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5370The Session Initiation Protocol (SIP) Conference Bridge Transcoding ModelCurrent
October 2008
- RFC 4117Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc)Current
June 2005
- RFC 5194Framework for Real-Time Text over IP Using the Session Initiation Protocol (SIP)Current
June 2008
- RFC 5368Referring to Multiple Resources in the Session Initiation Protocol (SIP)Updated
October 2008
- RFC 5367Subscriptions to Request-Contained Resource Lists in the Session Initiation Protocol (SIP)Current
October 2008
- RFC 5371RTP Payload Format for JPEG 2000 Video StreamsCurrent
October 2008
- RFC 5366Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)Current
October 2008
- RFC 5372Payload Format for JPEG 2000 Video: Extensions for Scalability and Main Header RecoveryCurrent
October 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?