The FCC published an adopted real-time-text framework and a companion proposal on January 23, 2017. The final rule allowed covered wireless voice providers using internet protocol to support real-time text, or RTT, in place of TTY technology, subject to applicable accessibility tests. It specified February 22 effectiveness; publication did not mean all services had already changed. [2017-01377][2017-01382]

RTT sends text as it is created, rather than requiring a completed message first. Covered services and authorized devices had to support calls to the same telephone numbers used for voice, communication with U.S. 911 answering points, and simultaneous voice and text in both directions on one device. The rules also required interoperability with other covered RTT services and with TTYs on other networks. [2017-01377][2017-01382]

The companion notice addressed when the latter requirement might end. The FCC said a final deadline was premature without further information on deployment and the effectiveness of the transition. It proposed 2021, with the possibility of extension, and sought comments. That proposal cannot be described as an adopted date when older text-telephone users would lose compatibility. [2017-01377][2017-01382]

Nor did the final rule require recalling or retrofitting devices already in service or manufactured before applicable compliance dates. The documents supply complementary parts of one proceeding: adopted functions and an unresolved sunset. They do not independently corroborate deployment, and a requirement to communicate with emergency answering points is not evidence that every such center already supported native RTT. [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