RFC 4117: Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc)
In plain English — editorial summary, not part of the RFC
This document describes how to invoke transcoding services using Session Initiation Protocol (SIP) and third party call control. This way of invocation meets 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
- RFC4117
- Published
- June 2005
- Authors
- G. Camarillo; E. Burger; H. Schulzrinne; A. van Wijk
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 19
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5369Framework for Transcoding with the Session Initiation Protocol (SIP)Current
October 2008
- RFC 5370The Session Initiation Protocol (SIP) Conference Bridge Transcoding ModelCurrent
October 2008
- RFC 5194Framework for Real-Time Text over IP Using the Session Initiation Protocol (SIP)Current
June 2008
- RFC 4119A Presence-based GEOPRIV Location Object FormatUpdated
December 2005
- RFC 4114E.164 Number Mapping for the Extensible Provisioning Protocol (EPP)Current
June 2005
- RFC 4129Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions to the IUA ProtocolCurrent
September 2005
- RFC 4103RTP Payload for Text ConversationUpdated
June 2005
- RFC 4102Registration of the text/red MIME Sub-TypeUpdated
June 2005
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?