FCC Shortens STIR/SHAKEN Implementation Time for Some Small Voice Providers

2021-12-15T13:01:51-05:00December 15, 2021|e-Lerts|

The FCC has accelerated the deadline for those small voice service providers it suspects are the likely source of illegal robocalls to implement the STIR/SHAKEN caller ID authentication framework. The FCC now will require non-facilities-based providers to implement STIR/SHAKEN by June 30, 2022, in the IP portions of their networks. A voice service provider is considered “non-facilities based” if it offers voice service to end users solely using connections that are not sold by the provider or its affiliates.

The STIR/SHAKEN deadline for facilities-based small voice service providers with 100,000 or fewer subscriber lines remains June 30, 2023, unless the FCC’s Enforcement Bureau suspects them of originating illegal robocalls.

Non-facilities-based Providers
In addition to preparing for the new deadline, non-facilities-based small voice service providers also must update the Robocall Mitigation Database (RMD) within 10 business days of the effective date of the Order to indicate they are no longer subject to the two-year deadline extension. The Order becomes effective 30 days after publication in the Federal Register.

The Wireline Competition Bureau will send notices to non-facilities-based small providers that have not updated their filings in the Robocall Mitigation Database and implemented STIR/SHAKEN by the appropriate deadline. Carriers that receive the notice but do not comply will be referred to the Enforcement Bureau, which may pursue enforcement actions.

Facilities-based Providers
The FCC also will be changing the implementation deadline for facilities-based small providers it suspects of originating illegal robocalls on their networks. The FCC’s Enforcement Bureau will notify voice service providers suspected of originating illegal robocalls and require them to implement STIR/SHAKEN if they fail to:

  • Mitigate suspected illegal robocall traffic,
  • Provide information requested by the Enforcement Bureau in a timely manner,
  • Prove that they are not originating such traffic, and
  • Take specific steps to mitigate the future origination of suspected illegal robocalls.

If found to be originating illegal robocalls, the Enforcement Bureau will require those voice service providers to implement STIR/SHAKEN within 90 days. Those providers also will be required to indicate in the Robocall Mitigation Database within 10 days that they are subject to the new deadline and update the RMD once they have implemented STIR/SHAKEN.

If you have questions about these new deadlines or anything related to STIR/SHAKEN, you can contact Bridget Alexander White at 301-459-7590.

Numbering & Porting Essentials Service

Clients interested in educating their staff on the cavalcade of numbering, porting and robocall mitigation requirements all service providers will face in 2022 should consider subscribing to JSI’s Numbering & Porting Essentials service. The subscription includes breaking news alerts, a free webinar and web-based education sessions designed to keep companies informed about important numbering, porting and robocall mitigation decisions that will impact their internal operations and customers. Contact Bridget Alexander White for more details and to sign up.

Reminder: Robocall Mitigation Certifications Due in One Week

2021-06-23T14:35:24-04:00June 23, 2021|e-Lerts|

All voice service providers are reminded that they must file their Robocall Mitigation Program (RMP) certifications in the FCC’s Robocall Mitigation Database (RMD) by or before June 30,2021. This new requirement is part of the FCC’s efforts to solve the nation’s illegal robocall problem.

All companies must certify that they have either completed STIR/SHAKEN implementation in their networks, have partially implemented STIR/SHAKEN and are performing robocall mitigation, or that they have not yet implemented STIR/SHAKEN and are performing robocall mitigation. A provider’s robocall mitigation program must specify practices the company has deployed that can reasonably be expected to significantly reduce the origination of illegal robocalls on its network. In addition, carriers must provide a company contact who is responsible for addressing robocall mitigation-related issues. The RMP information must be filed in the Commission’s Robocall Mitigation Database.

Failure to file a certification in the RMD could result in calls originating on your company’s network to not be completed. Beginning September 28, 2021, intermediate providers and terminating voice service providers will be prohibited from accepting traffic from voice service providers not listed in the Robocall Mitigation Database.

For more information on the Robocall Mitigation Database, or anything robocall related, please contact Bridget Alexander White in JSI’s Maryland office at 301-459-7590.

Numbering & Porting Essentials Service

Clients interested in educating their staff on the cavalcade of numbering and porting requirements all service providers will face in 2021 should consider subscribing to JSI’s Numbering & Porting Essentials service. The subscription includes breaking news alerts, a free webinar and six web-based education sessions designed to keep companies informed about important numbering, porting and robocall mitigation decisions that will impact their internal operations and customers. Contact Bridget Alexander White for more details and to sign up. Contact Bridget Alexander White for more details and to sign up.

Robocall Mitigation Webinar: What’s Your Plan to Protect Your Network & Customers?

2021-12-07T17:07:12-05:00June 16, 2021|Webinar Recordings|

The FCC is as frustrated with the onslaught of annoying unlawful robocalls as the general public and is trying to put measures into place to help stop these non-stop calls. Its most recent effort requires ALL voice service providers, no matter their size or makeup, to better police their networks against the origination of unlawful robocalls. To accomplish this goal, ALL voice service providers must provide the FCC with detailed robocall mitigation plans by the end of June 2021.

To help companies prepare and to offer some tips to develop and file these mitigation plans, JSI’s robocall expert, Bridget Alexander White, recently hosted a webinar where she discussed:

  • How your company can guard its network from being used to originate these unlawful calls;
  • Best practices that can help to protect customers;
  • Requirements of the upcoming FCC certification;
  • Possible consequences if companies do not comply; and
  • What’s next in robocall mitigation.

A recording of the webinar is available for $249. Subscribers to the Numbering & Porting Essentials bundle received this webinar as part of their 2021 subscription. Contact Brenda Cordwell in the Maryland office at 301-459-7590 if you’d like to purchase the recording.

FCC Announces Robocall Mitigation Database

2021-11-02T13:13:50-04:00April 23, 2021|e-Lerts|

All service providers must submit information by June 30

The FCC has created a new Robocall Mitigation Database to enforce a requirement in the 2019 Pallone-Thune Telephone Robocall Abuse Criminal Enforcement and Deterrence Act (TRACED Act), which called for voice service providers to better police their networks against illegal and unwanted robocalls. All voice service providers must file certifications in the new database before June 30, 2021, providing detailed information regarding their implementation of the STIR/SHAKEN caller ID authentication framework and/or a robocall mitigation program.

When companies file their robocall mitigation program information with the FCC, each will certify that it has either completed STIR/SHAKEN implementation in its network, has partially implemented STIR/SHAKEN and is performing robocall mitigation, or that the company has not yet implemented STIR/SHAKEN and is performing robocall mitigation.

Carriers under the STIR/SHAKEN deadline extension until June 30,2023, must state the type of extension received and detail the robocall mitigation program its company has deployed. In addition, each company is required to provide a robocall mitigation contact.

Certifications, company identification information, and contact information must be submitted via the database portal on the Commission’s website at https://fccprod.servicenowservices.com/rmd?id=rmd_welcome by June 30, 2021.

The FCC also set September 28, 2021, as the date in which intermediate providers and terminating voice service providers will be prohibited from accepting traffic from voice service providers not listed in the Robocall Mitigation Database.

For more information on the Robocall Mitigation Database, STIR/SHAKEN requirements, or anything robocall related, please contact Bridget Alexander White in JSI’s Maryland office at 301-459-7590.

Numbering & Porting Essentials Service

Clients interested in educating their staff on the cavalcade of numbering and porting requirements all service providers will face in 2021 should consider subscribing to JSI’s Numbering & Porting Essentials service. The subscription includes breaking news alerts, a free webinar and six web-based education sessions designed to keep companies informed about important numbering, porting and robocall mitigation decisions that will impact their internal operations and customers. Contact Bridget Alexander White for more details and to sign up.

Large Providers Must File TRACED Act Exemptions by December 1

2020-11-11T11:36:18-05:00November 11, 2020|e-Lerts|

The FCC has provided instructions for large voice providers who plan to file for an exemption from the STIR/SHAKEN caller ID authentication rules by the December 1 deadline. As explained in our e-Lert earlier this year, large providers have until June 30, 2021, to implement STIR/SHAKEN in their networks. Small providers have until June 30, 2023, to implement caller ID authentication, and are not subject to the December 1 deadline to file for an exemption (see our October 2nd e-Lert). Small providers are those with 100,000 or fewer voice service subscriber lines (counting the total of all business and residential fixed subscriber lines and mobile phones and aggregated over all of the provider’s affiliates).

For IP networks to receive an exemption, a voice service provider must:

  • Have completed the network preparations necessary to deploy the STIR/SHAKEN protocols on its network including, but not limited to, by participating in test beds and lab testing, or completing commensurate network adjustments to enable the authentication and validation of calls on its network consistent with the STIR/SHAKEN framework;
  • Have demonstrated its voluntary agreement to participate with other voice service providers in the STIR/SHAKEN framework by completing formal registration (including payment) and testing with the Policy Administrator;
  • Have completed the necessary network upgrades to at least one network element (e.g., a single switch or session border controller) to enable the authentication and verification of caller ID information consistent with the STIR/SHAKEN standards; and
  • Reasonably foresee that it will have completed all necessary network upgrades to its network infrastructure to be able to authenticate and verify caller ID information for all SIP calls exchanged with STIR/SHAKEN-enabled partners by June 30, 2021.

For Non-IP networks to receive an exemption, a voice service provider must:

  • Be working to develop a non-IP authentication solution; and
  • Reasonably foresee that it will have completed all necessary network upgrades to its infrastructure to be able to authenticate and verify caller ID information for all non-IP calls originating or terminating on its network as provided by a standardized caller ID authentication framework for non-IP networks.

Exemptions must include an officer-signed certification that the company meets the criteria for IP, Non-IP or both, accompanied by a detailed explanation of how the company meets each of the relevant criteria. Certifications and the supporting statements must be filed on ECFS in WC Docket No. 20-68 no later than December 1, 2020.

For more information about these exemptions or about the STIR/SHAKEN requirements, please contact Bridget Alexander White or Valerie Wimer at 301-459-7590.

FCC Grants STIR/SHAKEN Extension for Small Voice Providers

2021-01-27T10:23:10-05:00October 2, 2020|e-Lerts|

Small providers must file robocall mitigation certifications

Prior to its September open meeting this week, the FCC adopted a Second Report and Order further implementing the TRACED Act to fight against illegal robocalls. The Order includes a limited extension of the STIR/SHAKEN implementation deadline for small voice service providers until June 30, 2023. The FCC’s Order defined “small voice service provider” as a provider that has 100,000 or fewer voice service subscriber lines (counting the total of all business and residential fixed subscriber lines and mobile phones and aggregated over all of the provider’s affiliates).

STIR/SHAKEN enables voice service providers to verify that the caller ID information transmitted with a call matches the caller’s phone number (see our April 2, 2020, e-Lert for more about the STIR/SHAKEN requirements).

During the extension, small providers will be required to implement a robocall mitigation program to combat the origination of illegal robocalls during the course of the extension and certify that some or all of the calls that originate on its network are subject to a robocall mitigation program. Carrier certifications must:

  • Identify of the type of extension received under the Order;
  • State the specific reasonable steps the company has taken to avoid originating illegal robocall traffic as part of its robocall mitigation program; and
  • Include a statement of the provider’s commitment to respond fully and in a timely manner to all traceback requests from the Commission, law enforcement, and the industry traceback consortium (USTelecom), and to cooperate with the entities in investigating and stopping any illegal robocallers that use its service to originate calls.

The FCC’s Wireline Competition Bureau will release a Public Notice regarding the Robocall Mitigation Database and portal creation and establish a deadline for the certification filings.

Bridget Alexander White will discuss this latest Order’s allowances and requirements and how JSI can assist clients with compliance during an October 30th webinar “Numbering & Porting: Where Are We?!” Details and registration for that webinar will be sent soon. If you have questions about this STIR/SHAKEN extension, please contact Bridget at 301-459-7590.

Numbering & Porting Essentials Service

Clients interested in educating their staff on the cavalcade of numbering and porting requirements all service providers will face in 2021 should consider subscribing to JSI’s Numbering & Porting Essentials service. The subscription includes breaking news alerts, a free webinar and six web-based education sessions designed to keep companies informed about important numbering, porting and robocall mitigation decisions that will impact their internal operations and customers. Contact Bridget Alexander White for more details and to sign up.

FCC Mandates STIR/SHAKEN Implementation by June 2021

2020-04-02T10:22:34-04:00April 2, 2020|e-Lerts|

Extension Proposed for Small Providers

On Tuesday, the FCC mandated that all originating and terminating voice service providers implement STIR/SHAKEN in the Internet Protocol (IP) portions of their networks by June 30, 2021. STIR/SHAKEN enables voice service providers to verify that the caller ID information transmitted with a call matches the caller’s phone number.

This FCC action is in accordance with the Pallone-Thune Telephone Robocall Abuse Criminal Enforcement and Deterrence Act (TRACED Act), which was signed into law in December 2019. The law intends to help ease the onslaught of illegal and unwanted robocalls and spoofed calls we all receive daily. The Act includes requirements for the caller authentication protocol STIR/SHAKEN, suspected robocall and spoofed call blocking, tracing the origin of suspected spoofed and illegal robocalls, one-ring scam mitigation requirements and implementation of anti-robocall best practices for carriers that provide service to hospitals, which are the most recent victims of robocall/spoofing scams.

To fulfill the STIR/SHAKEN obligation, no later than June 30, 2021, a voice service provider shall:   

  1. Authenticate and verify caller identification information for all SIP calls that exclusively transit its own network;
  2. Authenticate caller identification information for all SIP calls it originates and that will exchange with another voice service provider or intermediate provider and, to the extent technically feasible, transmit that call with caller ID authentication information to the next voice service provider or intermediate provider in the call path; and
  3. Verify caller identification information for all SIP calls it receives from another voice service provider or intermediate provider which it will terminate and for which the caller identification information has been authenticated.

Small Providers’ Extension
The Order also includes a Further Notice of Proposed Rulemaking (FNPRM), consistent with the TRACED Act, in which the FCC is seeking comment on extending the STIR/SHAKEN implementation mandate for small providers to June 30, 2022. Small provider is defined as a provider that has 100,000 or fewer voice service subscriber lines (counting the total of all business and residential fixed subscriber lines and mobile phones and aggregated over all of the provider’s affiliates).

During the period of extension, the small providers would be required to implement an appropriate robocall mitigation program to prevent unlawful robocalls from originating on their network. The FCC is also seeking comment on the requirements to adopt for the robocall mitigation program. Comments on the STIR/SHAKEN FNPRM are due May 15, 2020, with reply comments due May 29.

JSI will continue to monitor the FCC’s actions on the small provider extension and ongoing robocall mitigation program, as well as other proposed rules under the Order. If you subscribe to JSI’s LNP Essentials Bundle, we’ll be discussing the details and latest news on this Order on the April 22nd LNP Essentials Interactive Call.

For more information on the Order, the TRACED Act’s robocall mitigation efforts, or the LNP Essentials Bundle, please contact Bridget Alexander White in JSI’s Maryland office at 301-459-7590.

Robocall Fighting Legislation Signed into Law

2020-01-10T15:21:57-05:00January 10, 2020|e-Lerts|

The two main tools in the fight against illegal robocalls and spoofed calls – STIR/SHAKEN and call blocking – were cemented into federal legislation at the end of December when the president signed the Pallone-Thune Telephone Robocall Abuse Criminal Enforcement and Deterrence Act (TRACED Act). The legislation directs the FCC to fully implement call blocking, STIR/SHAKEN and a variety of other robocall relief stipulations which Congress included in the TRACED Act.

Until now, these efforts were strongly suggested but voluntary for service providers. But now that this law has been enacted, carriers should be preparing for new rules and requirements to implement these anti-robocalling responses.

STIR/SHAKEN
STIR/SHAKEN, or the Secure Telephone Identity Revisited and Signature-based Handling of Asserted Information Using Tokens, are standards to confirm that the caller ID information that appears on consumers’ phones is accurate and any unverified calls are flagged or blocked.

The TRACED Act requires providers of voice service to have implemented STIR/SHAKEN or be capable of fully implementing STIR/SHAKEN for calls on their internet protocol (IP) networks within 18 months and agree to voluntarily participate with other voice providers in the STIR/SHAKEN authentication framework.

For non-IP networks, voice service providers must take reasonable measures to implement an effective call authentication framework or have the capability of fully implementing an effective call authentication framework in their non-IP networks within 18 months of the law’s enactment.

Call Blocking
The Act also directs the FCC to take a final agency action by December 30, 2020, to ensure that carriers implement robocall blocking services which:

  • Are provided on an opt-out or opt-in basis;
  • Are provided with no additional line item charge to consumers and no additional charge to callers for resolving complaints related to erroneously blocked calls; and
  • Make all reasonable efforts to avoid blocking emergency public safety calls.

The Act establishes additional requirements for service providers and FCC actions.

JSI will summarize and discuss the TRACED Act during the next LNP Essentials interactive web session on January 22. For more information on the Act, robocall mitigation efforts, or the LNP Essentials Bundle, please contact Bridget Alexander White in JSI’s Maryland office at 301-459-7590.

Go to Top