RFC 5194: Framework for Real-Time Text over IP Using the Session Initiation Protocol (SIP)
In plain English — editorial summary, not part of the RFC
This document lists the essential requirements for real-time Text-over-IP (ToIP) and defines a framework for implementation of all required functions based on the Session Initiation Protocol (SIP) and the Real-Time Transport Protocol (RTP). This includes interworking between Text-over-IP and existing text telephony on the Public Switched Telephone Network (PSTN) and other networks. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5194
- Published
- June 2008
- Authors
- A. van Wijk; G. Gybels
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 31
- Also known as
- —
Topics
- text telephone
- textphone
- deaf
- hard-of-hearing
- speech-impaired
- interactive text
- transcoding
- speech-to-text
- user alerting
- emergency services
- gateway
- analog terminal adapters
- PSTN interworking
- text presentation
- instant messaging
- conversation
- conversational text
- interactivity
- total conversation
- user requirements
- text gateway
- relay
- relay service
- text relay
- TTY
- text transport
- text interworking
- combination gateway
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 4117Transcoding Services Invocation in the Session Initiation Protocol (SIP) Using Third Party Call Control (3pcc)Current
June 2005
- RFC 3351User Requirements for the Session Initiation Protocol (SIP) in Support of Deaf, Hard of Hearing and Speech-impaired IndividualsCurrent
August 2002
- RFC 5598Internet Mail ArchitectureCurrent
July 2009
- RFC 5344Presence and Instant Messaging Peering Use CasesCurrent
October 2008
- RFC 5438Instant Message Disposition Notification (IMDN)Current
February 2009
- RFC 4597Conferencing ScenariosCurrent
August 2006
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?