Hubbry Logo
Real-time textReal-time textMain
Open search
Real-time text
Community hub
Real-time text
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Contribute something
Real-time text
Real-time text
Real-time text
View on Wikipedia
from Wikipedia

Real-time text (RTT) is text transmitted instantly as it is typed or created. Recipients can immediately read the message while it is being written, without waiting.

Real-time text is used for conversational text, in collaboration, and in live captioning. Technologies include TDD/TTY devices for the deaf, live captioning for TV, Text over IP (ToIP), some types of instant messaging, captioning for telephony/video teleconferencing, telecommunications relay services including ip-relay, transcription services including Remote CART, TypeWell, collaborative text editing, streaming text applications, next-generation 9-1-1/1-1-2[1] emergency service. Obsolete TDD/TTY devices are being replaced by more modern real-time text technologies, including Text over IP, ip-relay, and instant messaging.

Use over instant messaging

[edit]

While standard instant messaging is not real-time text (messages are sent deliberately when the writer is ready, not transmitted while they are being composed), a real-time text option is found in some instant messaging software, including AOL Instant Messenger's "Real-Time IM"[2] feature. Real-time text is also possible over any XMPP compatible chat networks, including those used by Apple iChat, Cisco WebEx, and Google Talk, by using appropriate software that has a real-time text feature. When present in IM programs, the real-time text feature can be turned on/off, just like other chat features such as audio. Real-time text programs date at least to the 1970s, with the talk program on the DEC PDP-11, which remains in use on Unix systems.

Beam Messenger, a mobile app offering real-time text messaging, was released in 2014.[3]

Certain real-time text applications have a feature that allows the real-time text to be "turned off", for temporary purposes. This allows the sender to pre-compose the message as a standard IM or text message before transmitting.

Use by the deaf

[edit]

Real-time text is frequently used by the deaf, including IP-Relay services, TDD/TTY devices, and Text over IP. Real-time text allows the other person to read immediately, without waiting for the sender to finish composing his or her sentence/message. This allows conversational use of text, much like a hearing person can listen to someone speaking in real-time.

Captioned telephony

[edit]

Captioned telephony is the streaming of real-time text captions in parallel with speech on a phone call. This is used by people who are hard of hearing to allow them to have the full benefit of listening as best they can, hearing all the intonation etc. in speech, yet have the captions for those words they cannot hear clearly enough. In the United States, captioned telephony is one of the free relay services that is available to anyone who is hard-of-hearing. Originally developed for use on the analog phone systems (where it requires a special phone) it is now available over IP using standard devices.

Use in collaboration

[edit]

Collaborative real-time editing is the utilization of real-time text for shared editing, rather than for conversation. Split screen chat, where conversational text appears continuously, is also considered real-time text. Some examples that provide this as a service are Apache Wave and its fork SwellRT,[4] Etherpad, the editor Gobby,[5] and most notably Google Docs.

Captioning, transcriptions and other uses

[edit]

Real-time text is used in closed captioning and when captions are being streamed live continuously during live events. Transcription services including Communication Access Real-Time Translation and TypeWell frequently use real-time text, where text is streamed live to a remote display. This is used in court reporting, and is also used by deaf attendees at a conference. Also, real-time text provides an enhancement to text messaging on mobile phones, via real-time texting apps.

Real-time text protocols

[edit]

Real-time text protocols include Text over IP (ToIP) designed around ITU-T T.140,[6] IETF RFC 4103,[7] RFC 5194,[8] and XMPP Extension Protocol XEP-0301.[9]

Total conversation

[edit]

According to ITU-T Multimedia Recommendation F.703,[10] total conversation defines the simultaneous use of audio, video and real-time text. An instant messaging program that can enable all three features simultaneously would be compliant. Real time text is an important part of it.

History

[edit]

Real-time text is also historically found in the old UNIX talk, BBS software such as Celerity BBS, and older versions of ICQ messaging software.

See also

[edit]

References

[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Real-time text

View on Grokipedia
from Grokipedia
Real-time text (RTT) is an accessibility technology that enables the instantaneous transmission of text characters over (IP) networks as they are typed, allowing users to communicate in near real-time without the need to press send after completing a . Developed primarily to support individuals who are deaf, hard of hearing, deaf-blind, or have speech disabilities, RTT serves as a modern successor to legacy teletypewriter (TTY) systems by integrating seamlessly with voice and video calls on IP-based devices such as smartphones and computers. The foundational standards for RTT were established by the (IETF) in the mid-2000s, with RFC 4103 (published June 2005) defining the (RTP) payload format for text conversations using ITU-T Recommendation T.140 encoding, which supports character-by-character delivery with redundancy mechanisms to mitigate in IP networks. This was complemented by RFC 5194 (June 2008), which outlines a framework for RTT over IP using the (SIP), addressing session setup, interworking with traditional telephone networks, and integration with multimedia services to meet accessibility requirements for conversational text. In the United States, the (FCC) adopted rules in December 2016 to facilitate the transition from TTY to RTT, permitting wireless carriers and device manufacturers to implement RTT as a universal, interoperable text solution across IP-enabled services, including support for (TRS) and emergency communications like 911. RTT has been widely adopted in telecommunications platforms since 2016, with ongoing global expansion, enabling its use during phone calls on Android and devices, in applications like for character-by-character text during meetings, and in Azure Communication Services for multiparty sessions with source identification. It also extends to services through organizations like the , where RFC 4103-compliant RTT allows direct text-to-911 access without additional hardware, enhancing response times for disabled users, including through the FCC's August 2024 requirement for location-based routing of RTT 911 messages. Globally, RTT aligns with guidelines such as the U.S. Section 508 Standards and European implementations for total conversation services, In the , the , effective June 28, 2025, mandates RTT implementation in public communications networks to ensure accessibility. ensuring reliable, low-latency text in diverse IP environments while supporting interworking with legacy systems.

Fundamentals

Definition and Principles

Real-time text (RTT), also known as text over IP (ToIP), is a communication technology based on Recommendation T.140 that enables the instantaneous transmission of text characters as they are typed, facilitating a fluid, character-by-character exchange over networks to support conversational interactions equivalent to voice-based services. This method allows recipients to read messages in near real-time while the sender is composing them, using protocols that stream text without requiring the completion of entire messages. The operational principles of RTT emphasize low-latency delivery to mimic the pacing of live conversations, with characters transmitted soon after entry to achieve an of no more than one second, though up to two seconds may be acceptable in some scenarios. Buffering is employed minimally—typically around 300 milliseconds—to smooth out network variations while preventing excessive delays, ensuring that text flows continuously without whole-line accumulation. To mitigate in IP networks, T.140 includes redundancy mechanisms where recent text is repeated in dedicated redundancy packets within the RTP payload. Flow control mechanisms, such as the "cps" parameter in session descriptions, cap transmission rates (defaulting to 30 characters per second) to manage bandwidth and prevent overload, while aligns text streams with other media like audio or video using shared timing references in real-time transport protocols. These elements collectively enable full-duplex, simultaneous two-way communication. Unlike non-real-time text methods such as or , which involve batch transmission of complete messages with inherent delays, RTT prioritizes streaming delivery for immediate visibility and interactivity. This distinction supports its role in time-sensitive exchanges rather than asynchronous correspondence. RTT requires IP-based networks as a foundational prerequisite, leveraging session initiation protocols (SIP) for establishing connections and for media handling, with encoding to ensure international compatibility. These elements form the basis for RTT's integration into multimedia sessions, as outlined in frameworks like RFC 5194.

Key Characteristics

One of the defining features of real-time text (RTT) is its provision of immediate visibility of typing activity, where text is transmitted and displayed character by character or in small bursts as it is entered, enabling recipients to read partial messages and respond in a manner that mimics the natural flow of spoken . This real-time streaming, often with minimal buffering of 300 milliseconds or less, allows users to observe pauses, ongoing composition, and incremental progress, fostering more interactive and fluid exchanges compared to batch-sent messages. Complementing this visibility is RTT's support for editability during transmission, permitting users to delete, correct, or revise characters on the fly before or as the message is fully conveyed, with these changes appearing instantaneously to the recipient for a seamless correction process. This capability enhances accuracy and reduces misunderstandings by allowing mid-stream adjustments without interrupting the overall conversation rhythm. RTT accommodates multilingual character sets through its use of encoding based on ISO 10646-1 (), enabling the real-time transmission of text from diverse languages and scripts without loss of fidelity. Additionally, it supports emojis and other international symbols, such as the "@" key, expanding expressive options in live text streams to include visual elements common in modern digital communication. In terms of , RTT significantly reduces for users with hearing or speech disabilities by providing a more natural, voice-like interaction pace, with transmission speeds that surpass traditional TTY (up to 45 , roughly 60 maximum) and approach conversational typing rates through low-latency delivery. This immediacy minimizes delays inherent in send-and-wait models, allowing independent participation in calls or chats with reduced frustration and higher reliability over IP networks. Security in RTT involves unique considerations due to its streaming nature, where can be implemented to protect live text flows but is not universally supported across all platforms, potentially exposing partial messages to if relying solely on transport-layer . In multiparty scenarios, encryption must balance real-time performance with , often achievable through protocol enhancements, though implementation varies by system to avoid compromising speed or .

Applications

Instant Messaging and Chat

While real-time text (RTT) standards exist for instant messaging (e.g., XEP-0301 for XMPP-based systems), most consumer platforms use typing indicators rather than full character-by-character text transmission. These indicators provide visual feedback that a user is composing a message, enhancing conversational flow. In Apple's iMessage, typing indicators appear as animated dots in one-on-one and group conversations when a user begins composing a message, allowing recipients to anticipate responses in real time. Similarly, WhatsApp displays a "typing..." indicator with three dots beneath the contact's name during active composition, supporting both individual and group chats to simulate synchronous interaction. Signal incorporates optional typing indicators as animated dots, which users can enable or disable in settings, ensuring privacy while facilitating real-time awareness in private and group discussions. These features deliver key consumer benefits by enabling quick, informal exchanges that mimic face-to-face , reducing wait times and fostering more dynamic interactions in daily communication. In group chats, typing indicators allow multiple participants to see who is contributing at any moment, preventing overlaps and encouraging collaborative input without the need for voice or video. For users with hearing or speech challenges, this provides a subtle bridge by promoting text-based immediacy, though specialized RTT adaptations are covered elsewhere. Overall, such capabilities boost engagement in casual scenarios, like coordinating plans or sharing updates among friends and family. Technical adaptations for typing indicators in mobile and web-based address network variability through optimized event signaling and buffering mechanisms, ensuring indicators remain responsive even on fluctuating connections. On mobile devices, apps employ lightweight push notifications to transmit typing events with minimal latency, throttling updates during poor signal to avoid overwhelming the . Web versions leverage persistent connections like WebSockets for seamless across browsers, with fallback to polling on unstable networks to maintain indicator accuracy without interrupting the chat flow. These strategies prioritize low-bandwidth efficiency, allowing real-time feedback in diverse environments from high-speed to intermittent cellular data. In chats, typing indicators have evolved with post-2020 updates to better support community interactions; for instance, X (formerly ) enhanced its Direct Messages with refined typing indicators via improvements, enabling more reliable real-time cues in private conversations. similarly updated its typing indicators in 2021 and beyond, repositioning them for better visibility in text channels and integrating them with forum-style discussions to handle larger group dynamics on mobile and desktop. These enhancements underscore the growing role of typing indicators in informal social exchanges, making platforms feel more alive and responsive, though true RTT remains limited to niche or enterprise implementations.

Accessibility for Deaf and Hard-of-Hearing Users

Real-time text (RTT) serves as a critical tool for deaf and hard-of-hearing individuals by instantaneous text transmission during phone calls, thereby providing equivalent access to voice-based communication without the need for intermediaries or delays. This functionality replaces outdated teletypewriter (TTY) systems, which relied on slower, hardware-dependent relay services and were incompatible with modern IP networks, allowing users to engage in fluid, character-by-character conversations similar to spoken dialogue. RTT has been integrated into mainstream smartphones to enhance usability for hearing-impaired users. On devices, software-based RTT support was introduced in 2017, enabling built-in text communication through the Phone app without additional hardware. Android devices offer RTT via accessibility settings starting from Android 9, allowing activation for calls over IP-enabled networks like VoLTE or . In the United States, legal frameworks have driven RTT adoption through (FCC) mandates requiring wireless carriers and device manufacturers to support RTT in IP-based services as a TTY replacement, with phased implementation beginning December 2017 and full compliance by June 2021 for resellers. These regulations ensure that RTT is available for emergency services like 911, promoting equitable access under the Americans with Disabilities Act. For deaf and hard-of-hearing users, RTT significantly reduces by facilitating real-time interactions in personal calls, group conversations, and professional settings, where previous TTY limitations often hindered spontaneous communication. In emergencies, it enables direct text-based reporting to responders, improving response times and accuracy over legacy systems. Despite these advancements, global adoption of RTT remains uneven as of , with limited support in non-English-speaking regions due to ongoing regulatory implementation and network compatibility challenges; for instance, the sets a June 2025 deadline for RTT integration into public networks, with potential derogation until June 2027 for emergency services. As of November , EU member states are in the process of full compliance, with trials showing improved interoperability via ETSI TS 103 919.

Telephony and Captioning

Real-time text (RTT) plays a crucial role in captioned services, enabling seamless integration of live captions with voice communications for users with hearing impairments. Captioned Telephone Service (IP CTS), a form of , allows individuals who can speak but have difficulty hearing to engage in phone calls while receiving near-simultaneous text captions of the other party's speech via an connection. In IP CTS, the user's voice is transmitted directly to the called party over the , while a communications assistant (CA) provides captions using voice recognition or re-voicing, displayed on the user's device such as a or captioned . This service supports real-time IP-based caption transmission to ensure captions appear nearly simultaneously with speech, facilitating natural conversation flow without interrupting the voice exchange. Hybrid systems combining voice and RTT streams further enhance by permitting hearing users to speak while deaf or hard-of-hearing users type responses, with text transmitted character-by-character over IP-based networks. Unlike traditional text (TTY) systems that require , RTT supports simultaneous voice and text within the same call, using standard phone numbers and allowing both parties to communicate concurrently. This bidirectional capability bridges the gap between voice-dominant and text-based interactions, making it particularly effective for mixed-hearing conversations where one party relies on typed input for clarity. In (VoIP) systems, RTT is implemented to provide real-time subtitles during video and audio calls, extending captioned to digital platforms. Similarly, Zoom incorporates real-time captioning features that generate live subtitles from spoken audio using automatic speech recognition (ASR), supporting in video conferences by displaying text overlays that users can view or save as transcripts. These VoIP integrations ensure low-latency text delivery, comparable to voice, and are compatible with international character sets for multilingual support. Advancements in automatic speech-to-text (ASR) integration have enabled dynamic captioning of voice content during calls, automatically transcribing spoken words into real-time text streams for users who cannot hear. This hybrid approach combines ASR engines with real-time text protocols to provide captions without manual intervention, achieving word accuracy rates of up to 95-98% in controlled environments with clear audio and minimal as of 2023. Such systems improve upon traditional services by reducing dependency on human CAs, though accuracy can vary in noisy settings, typically maintaining 85-90% in practical VoIP scenarios. Regulatory developments have accelerated RTT adoption in , particularly for services. The (EAA), effective across the EU as of June 28, 2025, mandates RTT implementation on public networks for communications, including calls to 112, to ensure equivalent accessibility to voice services with features like location sharing and no-cost access. This requirement, with a potential until June 2027 for full integration, promotes interoperability via standards like ETSI TS 103 919, enabling deaf users to text responders in real-time while hearing users continue voice calls. As of 2025, initial compliance reports indicate varying progress across member states, with enhanced focus on 112 integration.

Collaborative and Professional Uses

Real-time text (RTT) in collaborative and professional environments supports character-by-character text transmission during voice or video sessions, enabling immediate conversational feedback in tools like . In , RTT allows participants to type messages during meetings and calls, with text appearing instantly for all, facilitating faster communication for deaf or hard-of-hearing users without needing to press send. This integrates with broader collaboration features, such as live chat overlays, permitting contributors to input notes or decisions alongside verbal discussions. In environments, RTT provides immediate text-based participation in brainstorming sessions, allowing teams to iterate on ideas through typed responses during calls, which reduces delays in hybrid meetings. This fosters dynamic idea exchange, particularly for accessibility needs. RTT integrates with video conferencing platforms to enable text-based participation via dedicated RTT modes during calls. In meetings, for instance, RTT can be enabled for real-time text alongside audio, supporting hybrid participation without interrupting flows. Professional standards for RTT in emphasize and , aligning with IETF frameworks for IP-based communications. In and , RTT enhances in virtual sessions, enabling real-time text for inclusive .

Other Specialized Uses

Real-time text (RTT) has found niche applications in live event captioning, where it enables instantaneous text transmission during broadcasts, webinars, and conferences to enhance . In platforms like , RTT supports character-by-character text sharing during meetings and calls, allowing participants to type and view messages in real time without a send button, which is particularly useful for live webinars and virtual events. This feature integrates with automated live captions powered by AI , often requiring human oversight for accuracy in high-stakes broadcasts, ensuring compliance with standards while providing near-instantaneous text overlays for deaf and hard-of-hearing attendees. For example, during live streams or town halls, RTT can be enabled alongside AI-generated captions to facilitate interactive Q&A sessions, with text appearing as it is composed. In transcription services, RTT facilitates immediate archiving of conversations in sensitive sectors like legal proceedings and consultations. In telehealth environments, RTT enables real-time text communication between providers and patients who are deaf or hard of hearing, with the resulting text streams stored as official records for compliance and review. This approach replaces traditional TTY systems and supports HIPAA-compliant by capturing verbatim exchanges during virtual visits, allowing for quick retrieval and analysis without post-session transcription delays. Legal applications similarly leverage RTT for depositions or court sessions conducted via video platforms, where the text is archived directly, reducing errors and enabling real-time verification by participants. Data privacy remains a significant challenge in specialized RTT applications, particularly in healthcare contexts governed by HIPAA. RTT streams containing (PHI) during sessions must employ and secure storage to prevent unauthorized access, as unencrypted text transmission could lead to breaches similar to those in standard messaging. Compliance requires platforms to implement audit logs and patient consent mechanisms, with federal guidelines emphasizing the risks of remote communication technologies in medical settings. For instance, audio-only or text-based using RTT demands verifiable security measures to align with HIPAA's privacy rule, addressing vulnerabilities like device loss or interception.

Technical Standards

Core Protocols and Frameworks

The framework for Real-Time Text over IP (ToIP) is outlined in RFC 5194, which establishes the essential requirements and architectural components for implementing real-time text communication using the (SIP). This framework leverages SIP for session initiation, modification, and termination, while the (SDP) handles media negotiation and description of text streams. Session setup involves exchanging SDP offers and answers to agree on parameters such as payload types and transport protocols, enabling endpoints to establish dedicated text sessions alongside other media like audio or video. is standardized as to support international text, ensuring compatibility with diverse languages and scripts without additional framing beyond the RTP payload format. Transport occurs over RTP, integrating seamlessly with IP networks to facilitate low-latency text exchange. A core component of this framework is the RTP payload format for text conversation defined in RFC 4103, which specifies how real-time text is packetized and transmitted in RTP sessions. This standard uses the T.140 format for text, transmitted in a separate RTP session to avoid interference with other media streams. Flow control mechanisms include timestamping at 1000 Hz to synchronize text arrival, sequence numbers for detecting , and the use of payloads (per RFC 2198) to retransmit recent text in subsequent packets, mitigating losses in unreliable networks. The marker (M) bit in RTP headers signals the start of new text after idle periods, while buffering at the receiver—recommended at 300 ms and not exceeding 500 ms—handles without introducing excessive delay. An SDP parameter "cps" (characters per second) caps the transmission rate at a default of 30 cps to prevent overload, with higher rates negotiable for specific scenarios. In mobile networks, real-time text (RTT) is implemented through specifications, particularly TS 26.114 (Release 19, v19.1.0, July 2025), which details media handling for () multimedia in LTE and environments. This standard mandates RTT support for IMS-capable terminals, transporting text over RTP using the RFC 4103 payload format within RTP/AVP or RTP/AVPF profiles over UDP/IP. Session negotiation mirrors the ToIP framework via SIP/SDP, with mandatory encoding and optional redundancy up to 200% to ensure robustness over wireless links. For , TS 26.114 integrates RTT into the Multimedia Service for IMS (MTSI), supporting enhanced features like multiparty sessions as guided by TR 26.982 (Release 19, v19.0.0, October 2025), which provides implementation details for mixing multiple RTT streams in IMS core networks. QoS is enforced through resource allocation via the Policy and Charging Control (PCC) framework, prioritizing RTT as conversational traffic. Interworking with legacy systems, such as circuit-switched text , is handled by media gateways converting between RTP-based RTT and formats like H.223. Security for RTT streams in IP environments relies on established protocols to protect signaling and media integrity. SIP signaling is secured using (TLS), often via SIPS URIs, to encrypt session setup and prevent eavesdropping or tampering during SDP exchanges. For the RTP-based text transport, Secure RTP (SRTP) provides media encryption, message authentication, and replay protection, as specified in RFC 3711 and integrated into TS 26.114 for IMS deployments. Authentication occurs through key exchange mechanisms like SDES (Session Description Protocol Security Descriptions) or DTLS-SRTP, ensuring endpoints verify each other's identity before transmitting sensitive text data. In LTE/ networks, these protocols align with the IMS security architecture, mandating TLS for SIP and SRTP for media to meet end-to-end requirements. Performance targets for RTT emphasize low latency and minimal bandwidth to support fluid conversations. should not exceed 1 second for acceptable quality, with RTP buffering limited to 500 ms to maintain interactivity; specifies a 95th transfer delay of 130 ms for conversational QoS classes. Bandwidth usage is efficient, typically 1-2 kbps per stream including overhead, as negotiated in SDP with an "AS" attribute of 2 kbps and GBR allocations up to 2 kbps in LTE/, scaling with redundancy levels but remaining far below voice or video requirements. These metrics ensure RTT integrates into multimodal sessions, such as Total Conversation platforms, without degrading overall performance.

Interoperability and Total Conversation

Real-time text (RTT) achieves interoperability with legacy systems such as text telephone (TTY) devices through gateways in (IMS) and Long-Term Evolution (LTE) environments. These gateways, often implemented as IMS media gateways (IMS-MGW), convert RTT packets—transported via RFC 4103—into TTY-compatible audio tones (based on V.18 Annex A or TIA-825A standards) and vice versa, enabling seamless text exchange between modern IP-based devices and older analog TTY systems. Invocation of interworking occurs when an IMS terminal signals RTT support, triggering the gateway function as specified in TS 29.163 Annex I, allowing simultaneous or alternating text and voice flows. However, challenges include TTY's half-duplex nature requiring strict turn-taking protocols to prevent character loss, and potential quality degradation from audio encoding, echo cancellation, or exceeding 0.15%, necessitating robust error handling per TS 26.114. The Total Conversation model, standardized by in TS 23.226 (Release 19, v19.0.0, October 2025), integrates RTT with video and voice to provide full for users with hearing, speech, or mobility impairments, offering simultaneous or subset multimodal communication as defined in ITU-T Recommendation F.703. This framework ensures synchronized delivery of text (via ITU-T T.140), video for , and voice, supporting conversational flows in IMS networks while allowing subsets like text-only for bandwidth-constrained scenarios. By combining these media, Total Conversation addresses barriers in traditional , promoting inclusive real-time interactions as a core service in mobile ecosystems. Global standards efforts emphasize RTT integration in emergency services, with ITU-T recommendations such as the F.760 series (latest F.760.3, March 2025) outlining requirements for accessible response systems, including text-based alerting and location sharing. In , the system—mandatory for new vehicles since 2018—extends to RTT support under the (Directive (EU) 2019/882), requiring public safety answering points (PSAPs) to handle RTT or Total Conversation by June 28, 2025, with possible extensions to June 28, 2027; as of November 2025, implementation varies across Member States, with ongoing adoption efforts. This aligns with Y.4467 for eCall data structures, ensuring RTT with pan-European emergency networks for faster, multimodal response. ETSI standards further support this through TR 104 020, harmonizing RTT definitions for emergency communications across EU member states. Cross-platform compatibility for RTT faces challenges in heterogeneous environments, particularly with web-based systems requiring extensions to for standardized text handling. 's data channels can transport RTT, but mapping to RFC 4103 requires interoperability profiles to bridge browser implementations with legacy IMS or SIP endpoints, as outlined in RFC 9248 for relay user equipment. Key issues include varying browser support for T.140-compliant text, complications, and ensuring low-latency synchronization across devices, often addressed via standards like 's RTCDataChannel with custom extensions for character-by-character streaming. These challenges are mitigated through adherence to IETF RFC 5194 for SIP-based RTT frameworks, promoting end-to-end compatibility in multi-vendor deployments. The PEMEA (Pan-European Mobile Emergency Application) protocol enhances RTT for multimedia sessions in emergency contexts, extending the ETSI TS 103 871 framework to support synchronized text alongside audio and video via , with recent extensions noted in ETSI ES 204 009 (V1.1.1, August 2025). Synchronization is achieved through timestamps in milliseconds since the Unix epoch (January 1, 1970), embedded in JOIN and RTC_SESSION_NEGOTIATION messages, enabling alignment of RTT packets—sent in batches every 0.5 seconds per T.140—with video and voice streams during SDP negotiations (RFC 4566) and ICE candidate exchanges (RFC 8445). In PEMEA sessions, an Audio_Video Signalling Server manages peer-to-peer streams, using TURN servers (RFC 5766) for and ensuring real-time text delivery without disrupting concurrent media, thus facilitating accessible emergency interactions.

Historical Development

Origins and Early Innovations

Real-time text technology originated in the 1960s as an adaptation of existing teletypewriter systems to enable communication for deaf and hard-of-hearing individuals over telephone lines. In 1964, deaf physicist Robert Weitbrecht invented the acoustic coupler, a device that allowed teletypewriters to transmit text signals via standard telephones without direct electrical connection, marking the birth of the telecommunications device for the deaf (TDD) or teletypewriter (TTY). This innovation built on surplus military teletype machines from World War II, enabling real-time character-by-character text exchange at speeds up to 10 characters per second. By the late 1960s, Paul Taylor, a deaf engineer, further advanced the technology by integrating modems with these machines and distributing early TTY units through the National Association of the Deaf, facilitating the first widespread peer-to-peer text conversations among deaf users. Early TTY devices relied on the , a five-bit telegraphy encoding scheme developed by in the 1870s, which supported a limited set of uppercase letters, numbers, and symbols suitable for basic text relay. Adopted as the for U.S. TTYs due to compatibility with existing telegraphic infrastructure from and , Baudot enabled reliable analog transmission but lacked the flexibility of later ASCII-based systems. The National Technical Institute for the Deaf (NTID), established in 1965 under federal legislation to advance technical education and employment for deaf individuals, played a pioneering role in promoting these RTT concepts through research, training programs, and advocacy for accessible communication tools during the 1970s. By the mid-1970s, about 12,000 TTY units were in use across the U.S., underscoring the technology's growing impact on deaf community connectivity. In , initial adoption of real-time text occurred in the 1980s through the French system, a nationwide network launched by Télécom in that distributed millions of free terminals for online services. The 1986 introduction of specifically catered to deaf and speech-impaired users, allowing direct real-time text chats between terminals over telephone lines and significantly reducing reliance on relay services due to its accessibility and low cost. This marked one of the earliest large-scale deployments of RTT outside dedicated TTY networks, influencing broader text-based communication models. By the 1990s, RTT began evolving from analog TTY systems to digital formats amid the rise of the , with key milestones including the Recommendation T.140 in 1998, which standardized a protocol for text conversations. Concurrent IETF efforts on text protocols laid the groundwork for IP-based transmission, culminating in RFC 2793 (2000), which defined RTP payloads for real-time text, enabling the shift from circuit-switched analog lines to packet-switched networks. These developments addressed Baudot's limitations by supporting richer character sets and integration with emerging digital telephony.

Modern Evolution and Adoption

In the mid-2010s, real-time text (RTT) transitioned from legacy text (TTY) systems to IP-based networks, driven by regulatory mandates in key markets. In the United States, the (FCC) adopted rules on December 15, 2016, to facilitate this shift, requiring wireless carriers and device manufacturers to support RTT as a replacement for TTY over IP protocols starting in December 2017, with full compliance phased in by 2021 for resellers. This move addressed TTY's limitations in modern environments, enabling character-by-character text transmission during calls without specialized hardware. Smartphone operating systems rapidly integrated native RTT support to align with these regulations. Apple introduced RTT functionality in , released in September 2016, allowing users to enable it via settings for real-time texting during voice calls on compatible carriers. Similarly, Google added RTT capabilities in Android 9 (), launched in August 2018, building on earlier TTY features to provide seamless text relay without additional accessories, accessible through the Phone app's menu. These integrations expanded RTT's reach, making it available to millions of users on dominant mobile platforms and promoting interoperability with IP multimedia subsystems (IMS). Recent technological advancements have further enhanced RTT's performance and accessibility. The rollout of networks from 2023 onward has reduced latency to as low as 1-5 milliseconds in optimal conditions, benefiting real-time applications like RTT by minimizing in text transmission and improving reliability for time-sensitive communications. Concurrently, standardization by the W3C and IETF has enabled browser-based RTT, using data channels to support real-time text alongside audio and video, allowing web applications to facilitate RTT without plugins since the protocol's maturation in the early 2020s. These developments, including 5G-Advanced features under Release 18, position RTT for broader use in low-latency scenarios like emergency services and collaborative tools. Global adoption of RTT has accelerated through regulatory frameworks, though progress varies by region. In the , the (EAA), effective June 28, 2025, mandates RTT support in emergency services (112) and public communications, requiring synchronized voice and text capabilities in devices and networks to ensure for people with disabilities across member states. This has spurred implementation in infrastructure, with public safety answering points (PSAPs) now obligated to handle real-time text alongside voice and video. Looking ahead, RTT's evolution includes explorations of AI enhancements for improved usability, such as real-time transcription integrated with in pilot tools like ElevateAI's Echo RTT, tested in 2025 to provide contextual summaries during calls. These pilots signal potential for AI to augment RTT with features like error correction and predictive suggestions, further embedding it in diverse communication ecosystems by the late 2020s.

References

  1. https://www.fcc.gov/consumers/guides/real-time-text-improving-accessible-telecommunications
  2. https://www.federalregister.gov/documents/2016/05/25/2016-12057/transition-from-tty-to-real-time-text-technology
  3. https://www.rfc-editor.org/rfc/rfc4103.html
  4. https://datatracker.ietf.org/doc/html/rfc5194
  5. https://www.fcc.gov/document/adoption-real-time-text-rtt-rules
  6. https://source.android.com/docs/core/connect/rtt
  7. https://support.microsoft.com/en-us/topic/use-real-time-text-rtt-in-microsoft-teams-37719c3f-1083-4ce5-ba82-ec92a27c21b0
  8. https://learn.microsoft.com/en-us/azure/communication-services/concepts/voice-video-calling/real-time-text
  9. https://kb.nena.org/wiki/RTT_%28Real-Time_Text%29
  10. https://www.fcc.gov/consumer-governmental-affairs/fcc-adopts-location-based-routing-wireless-911-calls-and-rtt-911-messages
  11. https://www.access-board.gov/ict/
  12. https://eena.org/knowledge-hub/documents/rtt-and-tc-implementation-in-europe/
  13. https://nwise.se/real-time-text-rtt-now-a-legal-standard/
  14. https://www.itu.int/rec/T-REC-T.140/en
  15. https://tap.gallaudet.edu/IPTransition/Real-Time%20Text%20and%20TTY%20interworking%20in%20various%20technical%20environments.pdf
  16. https://www.nice.com/info/what-is-rtt-calling-a-nice-guide
  17. https://datatracker.ietf.org/doc/html/rfc4103
  18. https://caconnect.org/rtt/
  19. https://www.burnerapp.com/blog/what-is-rtt-calling
  20. https://www.cricketwireless.com/support/accessibility/real-time-text-rtt
  21. https://www.ctia.org/news/real-time-text-is-wireless-accessibility-for-the-21st-century
  22. https://learn.microsoft.com/en-us/microsoftteams/end-to-end-encrypted-meetings
  23. https://datatracker.ietf.org/doc/rfc9071/
  24. https://www.qoli.ai/glossary/what-is-rtt-calling
  25. https://support.apple.com/en-us/104972
  26. https://faq.whatsapp.com/1244276003970936
  27. https://support.signal.org/hc/en-us/articles/360020798451-Typing-Indicators
  28. https://www.pubnub.com/guides/how-a-typing-indicator-enables-chat-engagement/
  29. https://developer.x.com/en/docs/x-api/v1/direct-messages/typing-indicator-and-read-receipts/overview
  30. https://support.discord.com/hc/en-us/community/posts/1500000195162-Revamped-Typing-Indicators
  31. https://www.fcc.gov/real-time-text
  32. https://www.slashgear.com/1703772/iphone-rtt-meaning/
  33. https://www.fcc.gov/sites/default/files/documents/events/fact_sheet_about_real-time_text_for_public_safety_answering_points.pdf
  34. https://www.businessinsider.com/reference/what-is-rtt-call
  35. https://eena.org/blog/where-are-we-with-real-time-text/
  36. https://www.fcc.gov/consumers/guides/internet-protocol-ip-captioned-telephone-service
  37. https://support.zoom.com/hc/en/article?id=zm_kb&sysparm_article=KB0058810
  38. https://www.interprefy.com/resources/blog/ai-closed-captions-accuracy
  39. https://www.researchgate.net/publication/376600706_The_accuracy_of_automatic_and_human_live_captions_in_English
  40. https://www.etsi.org/deliver/etsi_ts/126100_126199/126114/19.01.00_60/ts_126114v190100p.pdf
  41. https://www.etsi.org/deliver/etsi_tr/126900_126999/126982/19.00.00_60/tr_126982v190000p.pdf
  42. https://www.3gpp.org/ftp/Specs/html-info/23226.htm
  43. https://www.itu.int/rec/T-REC-F.703/en
  44. https://www.itu.int/rec/T-REC-F.760.3-202503-I/en
  45. https://eur-lex.europa.eu/legal-content/EN/TXT/HTML/?uri=CELEX:52024DC0575
  46. https://eena.org/knowledge-hub/news/european-accessibility-act-begins-applying-across-the-eu/
  47. https://www.etsi.org/deliver/etsi_tr/104000_104099/104020/01.01.01_60/tr_104020v010101p.pdf
  48. https://datatracker.ietf.org/doc/rfc9248/
  49. https://www.etsi.org/deliver/etsi_ts/103800_103899/103871/01.02.01_60/ts_103871v010201p.pdf
  50. https://www.etsi.org/deliver/etsi_es/204000_204099/204009/01.01.01_60/es_204009v010101p.pdf
  51. https://www.pemea.eu/wp-content/uploads/2021/09/Real-Time-Text-for-PEMEA-consortium-1.0d.pdf
  52. https://www.etsi.org/deliver/etsi_ts/103900_103999/103945/01.01.01_60/ts_103945v010101p.pdf
  53. https://www.nad.org/resources/technology/telephone-and-relay-services/tty-and-tty-relay-services/
  54. https://gallaudet.edu/museum/exhibits/history-through-deaf-eyes/awareness-access-and-change/how-ttys-made-telephones-accessible-to-the-deaf/
  55. https://www.smecc.org/tty___tdd_history_and_resources.htm
  56. https://tap.gallaudet.edu/Text/TTYBasics.html
  57. https://www.princeton.edu/~ota/disk3/1982/8225/822505.PDF
  58. https://www.smecc.org/relay_and_message_services_for_the_deaf.htm
  59. https://www.etsi.org/deliver/etsi_ts/126200_126299/126235/06.05.00_60/ts_126235v060500p.pdf
  60. https://datatracker.ietf.org/doc/rfc2793/
  61. https://www.federalregister.gov/documents/2017/01/23/2017-01377/transition-from-tty-to-real-time-text-technology
  62. https://support.apple.com/en-ca/guide/iphone/iph3e2e47fe/ios
  63. https://support.google.com/accessibility/android/answer/9042284?hl=en
  64. https://www.zbtwifi.com/blogs/frontier-technology-news/how-fast-is-5g-unpacking-the-blazing-speeds-of-the-next-generation-network-in-2025
  65. https://www.w3.org/TR/webrtc/
  66. https://www.5gamericas.org/why-5g-advanced-matters-now/
  67. https://commission.europa.eu/news-and-media/news/eu-becomes-more-accessible-all-2025-07-31_en
  68. https://eud.eu/eud/toolkits/european-accessibility-act-toolkit-for-transposition/
  69. https://www.elevateai.com/announcements/echo-real-time-transcription/
Add your contribution
Related Hubs
Contribute something
User Avatar
No comments yet.