People who rely on text to make a telephone call need to reach others, not merely own a newer device. The FCC's rule published January 23, 2017 addressed that connection by allowing covered internet-protocol wireless voice providers to support real-time text, or RTT, instead of TTY technology. The option remained subject to the applicable accessibility qualifications, rather than imposing an immediate universal switch. [2017-01377][2017-01382]

RTT transmits text as it is created. The adopted capabilities included calls using the same numbers as voice calls, communication with U.S. 911 answering points, and simultaneous two-way text and voice on one device. Covered services and devices also had to connect with TTYs on other networks. Those requirements describe access functions, not proof that every emergency center had deployed native RTT. [2017-01377][2017-01382]

The FCC did not require providers or manufacturers to recall or retrofit devices already in service or manufactured before the relevant compliance dates. Its companion proposal made the remaining legacy question explicit: ending RTT-to-TTY compatibility was premature without more information about deployment and the transition. The agency sought comment on a possible 2021 endpoint, not a binding cutoff. [2017-01377][2017-01382]

The final rule specified February 22, 2017 effectiveness, distinct from phased compliance. The two publications belong to one FCC proceeding. For users, the meaningful public-interest test is whether a transition preserves usable connections while new capabilities become available. These documents establish the design and unresolved decision, not evidence that anyone could already rely on universal availability. [2017-01377][2017-01382]

Source documents

  1. Transition From TTY to Real-Time Text Technologyhttps://www.govinfo.gov/content/pkg/FR-2017-01-23/html/2017-01377.htm
  2. Transition From TTY to Real-Time Text Technologyhttps://www.govinfo.gov/content/pkg/FR-2017-01-23/html/2017-01382.htm