Providers Back USTelecom Robocall Blocking Recon

Telecom providers back USTelecom's robocall blocking petition for reconsideration (see 2105200074), in replies posted Tuesday in FCC docket 17-59. "Adopt a flexible approach to notification that would allow for, but not be limited to, returning specific [session initiation protocol] SIP codes when calls are blocked," CTIA said. "Rather than codifying unfinished standards work, the commission should defer to the ongoing, collaborative standards process." NCTA agreed and said the Jan. 1 implementation deadline "risks forcing providers to choose between offering consumers robust robocall mitigation tools or suspending such tools over concerns about compliance with return code mandates." Comments showed the "uncertain state of the standards" in the notification requirement, USTelecom said. An industry task force approval of industry standards is "at best, the beginning of the process," the telecom association said. Somos, the current toll-free numbering administrator and North American numbering plan administrator, echoed Lumen that there's "no value to notifying calling parties when their calls are blocked by analytic engines" (see 2106070051). Somos said calls blocked on the do not originate list shouldn't be included in notification to calling parties when such a call is blocked. Verizon said opposition to USTelecom's petition is based on "several flaws." The order on robocall blocking doesn't define what a legitimate caller or bad actor is, Verizon said, and "even some legal callers routinely take action to bypass blocking ... when they detect that their calls may have triggered blocking algorithms."