Week ending July 10, 2026

The reply round on the Commission’s numbering-and-robocalls NPRM closed Tuesday, and the record came back with a striking amount of agreement — not on what to do, but on what not to do. Nearly every serious filer told the Commission the same thing: if you want to stop illegal robocalls, keep the accountability on the call, not on the number.

The numbering NPRM’s reply round: a near-unanimous “wrong tool”

The proceeding is Combatting Illegal Robocalls Through FCC Numbering Policies — NPRM FCC 26-17, the Commission’s attempt to run TRACED Act Section 6(a)’s “know your customer” mandate through the numbering system itself. It rides across four dockets (WC 26-49, 20-67, 13-97, 07-243), and the ideas on the table are structural: heavier NRUF reporting, mandatory use of the AltSPID field to expose resellers, a single-level resale limit, new limits on number “cycling,” and fresh authority for state commissions over number assignment. Reply comments were due July 7, and the industry showed up in force.

The through-line is best stated by Inteliquent, filing through Cooley: “robocall accountability travels with the call, through STIR/SHAKEN origination-signing and industry traceback, and not with a telephone number’s chain of assignment.” That is the whole argument in one sentence. Because you can identify the source of illegal traffic through call signing and traceback no matter how many assignment levels sit beneath a number, re-engineering the numbering rules to chase resellers is, in the record’s telling, effort spent in the wrong place. Inteliquent doesn’t contest the Commission’s authority or its goal — it just points the Commission at the KYC/KYUP proceedings and the Robocall Mitigation Database FNPRM instead, and asks that any numbering changes be “targeted, operationally practical refinements.”

Bandwidth put it more bluntly, calling the Commission’s premise “misplaced” and arguing the real win is finishing the IP transition: unlock full STIR/SHAKEN across every call path and you strengthen number-resource conservation at the same time, rather than “adopting new, burdensome reporting requirements premised on outdated technologies and architectures.” It’s the cleanest statement of the position that TDM-era numbering plumbing is the problem, not the lever.

The trade associations converged on the same landing spot from the cost side. CTIA argued that more extensive NRUF reporting or mandatory AltSPID use “would impose significant additional costs and burdens without providing actionable information about resellers,” and warned that handing states more authority over number assignment “would undermine the Commission’s longstanding national numbering policies without reducing robocalls.” USTelecom wanted the same door left open only a crack — “incremental changes,” “measured adjustments to NRUF reporting to help identify resellers that provide large blocks of numbers,” and explicitly not “a complex overhaul.” ATIS pushed hard on keeping NRUF data confidential and out of the hands of state attorneys general.

Where the record got genuinely interesting was the reseller-identification sub-debate, because that’s where the “how” actually lives. iconectiv — wearing its LNPA hat — quietly reminded everyone that the plumbing already exists: “the NPAC already supports both Alternative Service Provider Identifier (‘AltSPID’) and Last Alternative Service Provider Identifier (‘LastAltSPID’) fields,” and those fields are available for use today. In other words, if the Commission wants reseller visibility, it needn’t invent a new data structure; it needs to decide whether to mandate populating one that’s already there. The Voice on the Net Coalition offered the lightest-touch alternative — require resellers to keep a list of the resellers they hand numbers to, produce it on request, and certify annually — which is really a records-and-attestation regime dressed as a numbering rule.

Number cycling, and INCOMPAS’s shot at the labeling stack

The sharpest fight in the record is over paragraphs 51–58 — the Commission’s musing about prohibiting or limiting number “cycling” or “rotation.” Here the opposition is close to unanimous and, for once, comes with concrete operational detail. The Alarm Industry Communications Committee filed narrowly on exactly this point: monitoring centers place high volumes of short, safety-critical verification calls that analytics routinely mistake for robocalls, and rotating “rested” numbers is how legitimate alarm traffic gets back through erroneous blocking. AICC pointed to Convoso’s data — roughly a fifth to a quarter of its active numbers submitted for label correction every month, treated inconsistently across analytics vendors — as evidence that the labeling system, not the callers, is misfiring. AT&T made the competition version of the argument: “Multi-level resale and number rotation/cycling are not proxies for illegal or abusive number use and serve legitimate business purposes,” and a blanket ban “would be overinclusive, impede competition, limit consumer choice, and increase costs.” ATIS and NCTA said the same in different words.

But the filing worth reading twice is INCOMPAS, because it turns the whole cycling problem around and aims it at the terminating side. Its diagnosis: “the actual driver of the harms the Notice identifies is not that numbers are reassigned or resold, but that terminating providers and their analytics vendors are declining to rely on the authenticated Rich Call Data (‘RCD’) that STIR/SHAKEN already makes available to them, opting instead for proprietary branded-calling and number-registration products.” That is a direct challenge to the branded-calling and number-registration economy — the paid overlays that sit on top of the authentication stack — and it asks the Commission to require terminating providers to use authenticated RCD and to mandate transparency into how labeling decisions get made. Whatever you think of the merits, it’s the most pointed articulation I’ve seen in this docket of the tension between the open, standards-based caller-identity we built (STIR/SHAKEN carrying signed RCD) and the proprietary trust products that have grown up beside it.

Almost alone among the major filers, Verizon leaned toward the Commission rather than away — not on numbering restrictions, but on obligations. It urged “a unified approach to robocall mitigation certifications,” under which every entity that receives numbering resources, regardless of its position in the chain of custody, would carry the same baseline duties: file in the Robocall Mitigation Database, respond to traceback, respond to audits. That’s a KYC-adjacent idea the Commission can act on without touching resale or cycling at all, and it’s the kind of proposal a delegated-authority order could pick up cleanly.

The Covered List gets a new Section 214 name

Away from the numbering record, the Public Safety and Homeland Security Bureau added Digitalsystem Technology Inc. to the Covered List on July 7 (DA-26-673) — specifically, “International telecommunications services provided by Digitalsystem Technology Inc., subject to section 214.” It’s paired with a companion Memorandum Opinion and Order (FCC 26-44) denying Digitalsystem’s Section 214 application outright. The Committee for the Assessment of Foreign Participation — Team Telecom, now formally staffed by Justice, Homeland Security, and the Department of War — recommended denial for “the unmitigable and unacceptable risks to the national security and law enforcement interests of the United States,” and the Commission agreed that foreign-adversary control posed “substantial and unacceptable national security and law enforcement risks,” citing the company’s PRC and Hong Kong relationships. This is the first fresh Section 214 international-services name on the Covered List since China Unicom back in September 2022 — the list has grown lately through equipment categories (Kaspersky, drones, foreign-produced routers), so a new carrier-services entry is worth marking.

The enforcement side of the same national-security push showed up July 10, when the Commission proposed fines against eight entities — Cogito Tech, Fikaxo, Lyno Dynamics, Skyhigh, Spatial Hover, SZ Knowact, WaveGo, and Xtra Technology — for apparently blowing off Enforcement Bureau letters of inquiry into whether they were marketing restricted radiofrequency gear tied to the Covered List. The dollar figures are modest, but the signal is that non-response to a Covered-List LOI is itself now a finable event. In the background, the Bureau also issued a round of router conditional approvals under the foreign-produced-router entry it added in March.

Honorable mentions

The Wireline Competition Bureau put out the agenda for its IP-transition workshop (DA-26-665, July 6) — panels on the legacy-voice-to-all-IP migration, IP interconnection, intercarrier compensation, and the legacy USF questions that ride along with it. It’s a useful bookend to Bandwidth’s reply in the numbering docket: the same “finish the IP transition and the rest gets easier” argument, now with a Commission venue and a date. The onshoring and consent-revocation comment wave in WC 17-59 / 02-278 also kept trickling in, mostly individual filers plus a comment from the Delaware Bankers Association, but nothing that reshaped last week’s picture.

Looking ahead

The big one is the July 22 open meeting, where the Robocall Mitigation Database FNPRM is expected — Inteliquent already framed its numbering reply around it, and several filers are plainly hoping the Commission routes its KYC ambitions through the RMD rather than through numbering rules. Watch, too, whether anything comes of INCOMPAS’s ask to force terminating providers onto authenticated Rich Call Data and to open up the labeling black box; that’s the thread most likely to matter for anyone building on branded calling. The numbering NPRM record is now closed, so a delegated-authority order or a narrower further notice could follow at any point — and if it does, Verizon’s “unified certification” framing is the low-friction path the Commission is most likely to reach for first. The IP-transition workshop lands mid-month.