Telecom regulation — the economic and legal plumbing of the voice network
Most of this library is about identity and trust — how a call proves who is behind it. This section is about the layer underneath that: the economic and legal rules that decide how the voice network is paid for and what obligations ride along with carrying a call. It exists because nearly every argument about finishing the transition to an all-IP network eventually collides with one of these four questions, and none of them has an easy, readable reference.
Why this sits in the library
The all-IP transition is usually pitched as a technical upgrade, but the reasons the last stretch of the legacy TDM network persists are mostly economic and regulatory, not technical. Carriers keep legacy arrangements alive because those arrangements still carry revenue; rural service depends on subsidy mechanisms designed for a copper world; the emergency-calling system runs on a patchwork of state fees; and a set of accessibility obligations built for the old network have to survive the move to IP. Understanding the transition — the beat this site follows most closely — means understanding this plumbing.
The four questions
How the network pays itself: intercarrier compensation. When one carrier hands a call to another, who pays whom? The legacy answer was a system of per-minute access charges and reciprocal compensation. The long arc of reform — from the 2011 USF/ICC Transformation Order to the current all-IP pricing proposals — has been to move that system to bill-and-keep, where carriers stop charging each other and recover costs from their own customers. Draining those payments removes one of the biggest reasons to keep TDM interconnection alive. See intercarrier compensation and bill-and-keep.
How rural service stays comparable: universal service. Section 254 of the Communications Act commits the country to keeping rates and services in rural, insular, and high-cost areas “reasonably comparable” to urban ones. The Universal Service Fund — and its high-cost program in particular — is how that commitment is funded. Its constitutional footing was affirmed by the Supreme Court in 2025, but how it is funded going forward is an open policy fight. See universal service and the high-cost program.
How emergencies stay reachable: 911 funding and NG911. There is no federal 911 fee; 911 is paid for by a patchwork of state and local surcharges, and the move to Next Generation 911 — an IP-based emergency-calling architecture — has to be funded against that fragmented base. See 911 funding and NG911.
How the network stays accessible: relay services and real-time text. The network carries obligations to people who are deaf, hard of hearing, deafblind, or have a speech disability — through Telecommunications Relay Service and its video and captioned variants, and through the transition from legacy TTY to real-time text (RTT), the IP-native replacement that survives the move off TDM. See relay services and the move to RTT.
These four are not separate silos. They are the same transition seen from four angles — which is exactly how they showed up, panel by panel, at the FCC’s 2026 IP Transition Workshop.
Technical companions
Several of these questions have a standards-and-protocols layer beneath the policy, and each has a companion entry that goes into it:
- The architecture of all-IP 911 — the ECRIT emergency-calling RFCs, the NENA i3 profile, and how STIR/SHAKEN signs emergency priority and PSAP callbacks (and why verified identity still isn’t reaching the PSAP).
- Video relay — standards and interoperability — the iTRS numbering directory, the SIP Forum provider profile, the RUE user-equipment profile, the NANC Interoperable Video Calling reports, and what a converged all-IP relay ecosystem would require.
- Real-time text — standards and gaps — the T.140 / RFC 4103 / IMS stack, and the interoperability, TTY-gateway, and 911 shortcomings that keep RTT from being the seamless successor to TTY it is meant to be.
- 988 georouting — the FCC order requiring wireless 988 calls to route on general location rather than area code, and ATIS-0500049, which carries that location as state and county FIPS codes in existing SS7 and SIP signaling without precise geolocation.
The consent statute underneath
The four questions above are all IP-transition questions. One statute in this section is not, and it predates the transition by three decades:
- The Telephone Consumer Protection Act — the 1991 consent statute at 47 U.S.C. § 227, the do-not-call registry, and the $500-to-$1,500-per-call private right of action that drives most robocall litigation. It governs whether a caller was allowed to place a call, where the caller-authentication rules govern whether the identity in the signaling is real. Two Supreme Court decisions reshaped it: Facebook v. Duguid (2021) on the autodialer definition, and McLaughlin v. McKesson (2025) on whether courts must follow the FCC’s reading of the statute.
In this section
-
911 funding and the transition to NG911
There is no federal 911 fee. 911 in the United States is funded by a patchwork of state and local surcharges on phone bills, supplemented by state and local general funds — which means the emergency-calling system is paid for unevenly, state by state. Some states divert those fees to other uses, and the FCC names them in an annual report. The move to Next Generation 911 (NG911) — an IP-based architecture built on NENA's i3 standard that replaces the legacy circuit-switched system and can carry text, images, and data to call centers — has to be funded against that fragmented base, with remaining costs estimated in the billions and no enacted nationwide fund. This entry explains how 911 is paid for, what NG911 is, and why the funding gap is the central obstacle.
-
988 georouting — routing crisis calls without precise location
The 988 Suicide & Crisis Lifeline routes a caller to a local crisis center, and until 2024 it picked that center from the area code of the calling number. The FCC's Third Report and Order (FCC 24-111, October 2024) requires wireless carriers to georoute 988 voice calls on the device's general location instead, with a companion order covering texts. ATIS' Emergency Services Interconnection Forum published ATIS-0500049 in August 2026 specifying how carriers carry that location as state and county FIPS codes in existing SS7 and SIP signaling, explicitly without using precise geolocation data. The design point is the coarsest resolution that solves the routing problem, which is a different answer from the 911 handset-location machinery.
-
Intercarrier compensation and the move to bill-and-keep
Intercarrier compensation (ICC) is the system of payments carriers make to each other for handing off traffic — historically per-minute access charges paid by long-distance carriers to originate and terminate calls, plus reciprocal compensation between local carriers. The twenty-year arc of reform has been to drain that system and move to bill-and-keep, where carriers stop charging one another and each recovers its costs from its own end users. The 2011 USF/ICC Transformation Order set bill-and-keep as the end state and stepped terminating rates down over the 2010s; the FCC's 2026 all-IP pricing proposal (FCC 26-11) would finish the job by moving the remaining access charges to bill-and-keep in three annual steps and ending access tariffs. The reason this matters for the IP transition — legacy compensation is one of the main reasons carriers keep TDM interconnection alive.
-
The architecture of all-IP 911 — ECRIT, NENA i3, and call identity
The technical companion to the 911-funding entry. All-IP 911 is built on a mature standards stack — the IETF's ECRIT emergency-calling RFCs (the sos service URN, LoST location-to-PSAP routing, PIDF-LO location, SIP location conveyance) profiled into the North American NENA i3 architecture (ESInet, NGCS, ECRF/ESRP). What is not yet in place is verified caller identity at the PSAP — STIR/SHAKEN can already sign a call's emergency priority and its PSAP-callback marking (RFC 8443 and RFC 9027), and ATIS has profiled that signing for emergency use, but in practice 911 caller identity still rides legacy ANI/ALI rather than a verified PASSporT. This entry walks the standards and gives an honest read of what is deployed versus standardized-but-waiting.
-
Real-time text — the standards and the gaps
The technical companion to the relay-services entry, focused on Real-Time Text (RTT). RTT has a mature standards stack — ITU-T T.140 for text coding, RFC 4103 for carrying it over RTP with loss-protecting redundancy, RFC 9071 for multiparty, RFC 8865 for WebRTC, and 3GPP's IMS multimedia telephony specs for VoLTE and VoNR. On paper it is the clean IP-native successor to TTY. In practice it carries real shortcomings — inconsistent interoperability across carriers, handset makers, and operating systems; a lossy half-duplex downgrade when bridging to legacy TTY; uneven handling in 911/NG911; buffered "message mode" that defeats true character-by-character conversation; and near-absent wireline and OTT support. This entry walks the standards and then the gaps — the gaps being the more important half.
-
Relay services and the move to real-time text
The voice network carries obligations to people who are deaf, hard of hearing, deafblind, or have a speech disability. Telecommunications Relay Service (TRS) — mandated under Title IV of the ADA and paid for by the roughly $1.5-billion-a-year Interstate TRS Fund — provides the intermediary services that make phone communication possible, from video relay (VRS) and captioned telephone (IP-CTS) to text and speech-to-speech relay. Separately, the network is transitioning from legacy TTY, which does not survive the move to IP reliably, to real-time text (RTT), the IP-native replacement built into VoLTE. This entry explains the relay-service framework, how the fund and the VRS rates are set, the state of the TTY-to-RTT transition, and where relay calls sit inside STIR/SHAKEN — TRS providers cannot obtain SPC tokens, and conferenced PSTN relay calls cannot meet the criteria for A-level attestation, both now on the record in the FCC's KYUP proceeding.
-
The Telephone Consumer Protection Act (TCPA)
The TCPA is the 1991 consent statute underneath US robocall law, codified at 47 U.S.C. § 227 and implemented at 47 CFR § 64.1200. It restricts autodialed and prerecorded calls, runs the national do-not-call registry, and — unlike the caller-authentication rules — gives private plaintiffs a right of action worth $500 per call, trebled to $1,500 for willful violations. That damages structure, not FCC enforcement, is what drives most TCPA activity. Two Supreme Court decisions have reshaped it — Facebook v. Duguid (2021) narrowed the autodialer definition to equipment using a random or sequential number generator, and McLaughlin v. McKesson (2025) held that district courts are not bound by the FCC's reading of the statute. This page covers what the statute reaches, how consent works, where the litigation went after Duguid, and how the TCPA sits next to the TRACED Act and STIR/SHAKEN.
-
Universal service and the high-cost program
Universal service is the principle — codified in section 254 of the Communications Act — that everyone in the country, including people in rural, insular, and high-cost areas, should have access to telecommunications at rates reasonably comparable to urban ones. It is funded through the Universal Service Fund (USF), which USAC administers under FCC direction across four programs — High Cost, Lifeline, E-Rate (schools and libraries), and Rural Health Care. The high-cost program — now built around the Connect America Fund and the A-CAM cost models — is the one that most directly shapes the rural side of the IP transition. In 2025 the Supreme Court affirmed the fund's constitutionality; a renewed challenge to the fund and to USAC was argued before a Fifth Circuit panel on August 5, 2026, and the FCC opened WC Docket 26-173 on USAC's structure the following day. How the fund is paid for going forward, as the contribution factor climbs toward 40 percent on a shrinking revenue base, remains an open policy fight.
-
Video relay — standards, interoperability, and the all-IP vision
The technical companion to the relay-services entry, focused on Video Relay Service (VRS). VRS is delivered by competing providers over IP, addressed by ten-digit numbers in a shared iTRS Numbering Directory, and governed by an FCC interoperability rule that leans on a SIP Forum provider profile and, for user equipment, the IETF's RUE profile (RFC 9248). Cross-provider reachability and point-to-point video are mandated and partly built, and the FCC has pushed toward a neutral, provider-agnostic platform — but the codified standards baseline lags the actual specifications, and relay still lives in a numbering and identity plane separate from the carrier network. This entry maps the standards (including the two NANC Interoperable Video Calling reports and the SIP Forum work) and what a fully converged, all-IP relay ecosystem would require.
Planned
- access-stimulation · traffic pumping and the abuse cases ICC reform was aimed at
- lifeline · the low-income USF program
- e-rate-rural-health · schools-and-libraries and rural-health-care USF programs
- 911-fee-diversion · the annual FCC report and the states that divert
- usf-contribution-reform · the contribution-base debate after FCC v. Consumers' Research