FCC Grants Further Extension on Reassigned Number Database Implementation

Quick update for anyone wondering what has become of the FCC’s reassigned number database.

In December 2018 the FCC issued an Order creating a reassigned number database. The database would track the date of the last permanent disconnect of a cell phone number and enable potential callers to scrub against the database before attempting a call to a cell phone number. By using the database callers could avoid calls to wrong numbers—and the attendant risk of TCPA liability. And, in the event of an error in the database, callers would be granted a safe harbor if they otherwise properly scrubbed before attempting a call.

[article_ad]

The database was originally expected to be rolled out in late 2019. But a series of delays have hampered its implementation. First, the FCC issued a public notice on two petitions seeking reconsideration of certain aspects of the order creating the database. Then, the North American Numbering Council’s (NANC) Numbering Administration Oversight Working Group—the outfit responsible for making technical recommendations needed to implement the database—sought a several month extension to complete its work. Whereas NANC’s recommendations were originally due June 13, 2019, the date was extended to September by order of the FCC issued June 12, 2019.

Well, last Thursday the Commission granted a further extension—this time to January 2020– to complete the technical analysis and an additional month to set a pricing structure. NANC reported that the work was more challenging than expected and needed vendors are, apparently, not cooperating. Notably, the NANC had sought an extension to April 2020 but the FCC was reluctant to wait that long.  As the FCC put it: “We are mindful of the need to establish an operational database as soon as possible and believe that this is sufficient time for the remaining work to be completed.”

The ruling can be found here: Reassigned Number Database Requirements

After the technical specifications and pricing elements are completed an Administrator will need to be chosen and the carriers will need to supply data to populate the database. Hence, it now looks like Summer, 2020 is now the earliest possible deployment for the database.

--

Editor's note: This article is provided through a partnership between insideARM and Squire Patton Boggs LLP, which provides a steady stream of timely, insightful and entertaining takes on TCPAWorld.com of the ever-evolving, never-a-dull-moment Telephone Consumer Protection Act. Squire Patton Boggs LLP—and all insideARM articles—are protected by copyright. All rights are reserved.