March 2026

Committee Reports

Click on a committee name below to display this month's issues.

• ESIF: Emergency Services Interconnection Forum

  • Issue: 0116
  • Title: In support of FCC’s request to identify and standardize 988 Georouting
  • Statement: The 988 Suicide and Crisis Lifeline is a national network of more than 200 crisis centers that helps thousands of people overcome crisis situations every day. These centers are supported by local and state resources as well as the U.S. Department of Health and Human Services’ SAMHSA (Substance Abuse and Mental Health Services Administration). Geolocation services are not currently enabled for 988, as they are for calls to 911. A caller’s location information is not transmitted with a 988 call for possible dispatch of emergency services. The Lifeline automatically routes calls by area code to the nearest crisis center. For example, when a caller based in Virginia with a callback number of a 703 area code calls 988, the Lifeline will route the call to a Virginia Lifeline call center regardless of the caller’s actual location at the time of the call.
  • Resolution: ESIF developed a technical report, ATIS-0500049, GeoRouting for 988 voice calls
  • Status: Initial Closure

  For more information, visit the ESIF home page or contact Drew Greco.

• INC: Industry Numbering Committee

  • Issue: 1011
  • Title: Update INC Guidelines (ATIS-0300119, ATIS-0300070) stating Service Providers to verify numbering resources prior to assigning telephone numbers
  • Statement: The current ATIS-03000119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines states service providers should check NPAC prior to assigning telephone numbers from contaminated thousands-blocks. NANPA suggests updating the language in ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines and adding language to ATIS-0300070, Guidelines for the Administration of Telephone Numbers stating service providers should verify it is the Thousands-Block Holder prior to opening a new resource for assignment and check NPAC for ported TNs prior to assigning telephone numbers to assist in the prevention of double assignments.
  • Resolution:
  • Status: New Issue

  • Issue: 1012
  • Title: Update TBCOCAG Mass Modification Process to Exclude BIRRDS Updates
  • Statement: Currently, the TBCOCAG requires that the Service Provider (or its AOCN) provide TRA with a spreadsheet from NANPA to have BIRRDS ACD and BCR records updated based on a Mass Modification submitted via NAS. Now that NANPA has implemented a mechanized interface from NAS to BIRRDS eliminating NANPA manual data entry into BIRRDS, ACD and BCR record updates based on a Mass Modification should use the mechanized interface to BIRRDS. Service Providers should no longer be required to request that TRA process a utility for the ACD and BCR updates.
  • Resolution:
  • Status: New Issue

  • Issue: 1013
  • Title: Clarification of Service Provider Responsibilities When Assuming CO Code Holder Status Due to Ported Telephone Numbers
  • Statement: This Issue seeks to clarify how numbering assignment criteria and regulatory waiver processes should be addressed when CO Code Holder status results from ported TN reassignment rather than voluntary resource request. When a Service Provider becomes a CO Code Holder due to abandonment of a pooled or non-pooled CO Code with ported TNs, the TBCOCAG describes the procedural reassignment steps but does not address potential conflicts with standard numbering assignment criteria. An SP assuming CO Code Holder status under these circumstances may: Be required to seek state commission waiver or to obtain additional Thousands-Blocks or CO Codes necessary to perform CO Code Holder responsibilities due to not meeting Months-to-Exhaust (MTE) or 75% utilization thresholds required for Growth assignments. Sections 12 (Abandoned Numbering Resources) and 19.2 (Safety Valve Process) may need modifications
  • Resolution:
  • Status: New Issue

  • Issue: 1014
  • Title: Create a single combined INC glossary of terms
  • Statement: Per an INC action item, this issue is being proposed for INC to create a single glossary of terms of all INC terms across all INC documents. Historically, when the definition of a term has been updated for one INC document, INC has not always reviewed all documents where the term is located to ensure that the definition is consistent across documents. Having a single combined glossary would prevent this from happening.
  • Resolution:
  • Status: New Issue

  • Issue: 992
  • Title: Review and update Sections 10.1 and 10.2 Mass Modifications of the TBCOCAG (Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) to allow for disconnects and inter-company transfers to be worked through the mass modification process
  • Statement: Sections 10.1 and 10.2 Mass Modifications of the TBCOCAG (Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines currently only allow for a mass modification of records of 50 or more when the modification would be considered an intra-company change. Section 10.1: When there are 50 or more Thousands-Blocks that need to be modified for intra-company OCN changes, Switching Entity/POI changes, or Part 1B modifications, a mass modification spreadsheet can be sent to the NANPA as long as the effective date is not expedited. Section 10.2: When there are 50 or more CO Codes that need modifications on intra-company OCN changes, Switching Entity/POI changes, or tandem modifications, a mass modification spreadsheet can be sent to NANPA as long as the effective date is not expedited. There is no measure for Service Providers (SPs) to complete disconnects or inter-company OCN changes via Mass Modification which causes additional work and time for SPs.
  • Resolution: INC agreed to close Issue 992 with no changes to ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines. A new Issue to address mass disconnects only will be brought in after Issue 1000 is closed and the resulting document is published.
  • Status: Final Closure

  For more information, visit the INC home page or contact Celina Gore.

• NRSC: Network Reliability Steering Committee

  • Issue: 0061
  • Title: 988 Designated Point of Contact Recertification 2026
  • Statement: FCC requirement for annual DPOC audit and recertification by the NRSC Regulatory team. (FCC 23-57)
  • Resolution: The 988 stakeholder contact information was confirmed via email on March 10, 2026.
  • Status: Initial Closure

  For more information, visit the NRSC home page or contact Celina Gore.

Definitions

• New Issue: Business, operational, or technical needs that a committee has reached consensus to address.
• Issue in Initial Closure: Issues for which a committee has reached consensus on a proposed resolution. The industry has a 21 calendar day period to review and comment on the consensus resolution developed by the committee. The committee's consensus resolution concludes its work on an issue unless new or substantive information is brought forth. During the 21 day review period, comments on a consensus resolution may be provided to the committee contact and committee leaders.
• Issue in Initial Pending: Issues previously in Initial Closure for which new and substantive information impacting the consensus resolution has been received. An issue may also be in Initial Pending if output that may impact the consensus resolution is expected from another industry group, regulatory body or similar organization.
• Issue in Final Closure: Issues for which work is completed and the resolution accepted by the industry.

Recently Approved ATIS Standards

No new Standards approved this month.

Recent Policy Filings

SNAC

• Date: 03/09/2026
• Description: Comments in Response to FCC Request to Refresh the Record on 2020 iconectiv Petition
• View filing
• Date: 03/24/2026
• Description: Reply Comments in Response to FCC Request to Refresh the Record on 2020 iconectiv Petition
• View filing

INC

• Date: 03/16/2026
• Description: Reply Comments in Response to FCC Request to Refresh the Record on 2020 iconectiv Petition
• View filing