May 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: Final Closure

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

• INC: Industry Numbering Committee

  • Issue: 0994
  • Title: Review if NANPA can deny requests for resources due to a Service Provider’s inability to fulfill code holder’s responsibilities, e.g. having an AOCN.
  • Statement: There is a current pooled CO Code assigned to a Service Provider (SP) where the SP does not have an AOCN (and has never had an AOCN). This is also the first resource the SP has obtained. In this case, the CO Code cannot be built in the NPAC due to the fact they have no AOCN to build the record in BIRRDS, thus they are not able to fulfill code holder responsibilities per the TBCOCAG. The lack of an AOCN will negatively impact the SP and their end-users and any other SP obtaining blocks in this CO Code. The negative impacts include no-default routing due to no LERG data, no NPA-NXX built in the NPAC thus no LRN can be built in the NPAC.
  • Resolution: INC agreed to add a new Section 4.7, Active Administrative Operating Company Number (AOCN) Requirement, to ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines, as shown in INC-2026-00075R001. This will be a no cost NANPA Change Order and the Issue will remain in Initial Pending until FCC approval and implementation.
  • Status: Initial Closure

  • Issue: 1001
  • Title: Toll Free Carrier Identification Code (CIC) Use
  • Statement: There is a need to update the INC’s CIC assignment guidelines specifying appropriate CIC use consistent with the Toll Free subscriber’s agreement with the Resp Org. This will assist with ensuring that industry follows the application and use of CICs specified and expected by the Resp. Org. and its Toll Free subscriber.
  • Resolution: INC agreed to update ATIS-0300050, Carrier Identification Code (CIC) Assignment Guidelines, with edits to sections 1.4 and 5.3, as reflected in contribution INC-2026-00078R000.
  • Status: Initial Closure

  • Issue: 1006
  • Title: Add language regarding Effective Date Changes on Pooled CO Code modifications to ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines Section 9.2
  • Statement: Currently there is no direction in ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines Section 9.2 regarding effective date changes to Pooled CO Codes. NANPA suggests adding language to ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines regarding effective date changes to Pooled CO Codes. NANPA suggests adding the following to a new Section 9.2.8:
    • an effective date change may be modified to an earlier effective date,
    • an effective date change may be modified to a later effective date when there are no Thousands-Blocks assigned to SPs other than the Code Holder,
    • an effective date change shall be denied when there are Thousands-Blocks assigned to SPs other than the Code Holder.
    Each item would indicate the impacts on the Part 4 Due Date, Available Date of Thousands-Blocks in the Industry Inventory Pool, and direction on how to update the Thousands-Block Holders when an effective date change is denied.
  • Resolution: INC agreed to add a new section, Section 9.2.8 to ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines outlining the processes for Pooled CO Code Effective Date changes, as reflected in INC-2026-00050R001.
  • Status: Initial Closure

  • Issue: 1015
  • Title: Review "In-Service" definition in TBCOCAG compared to NRO Orders
  • Statement: The TBCOCAG definition of "In Service" seems more vague than the NRO language. NANPA is enforcing the in-service requirement according to the NRO, meaning the carrier who obtained the code or block must have activated numbers within it. However, further clarification is needed: Do any active TNs with the current SP qualify them to submit a Part 4, or must the activation be after the effective date? For example, if an SP acquires a block in which they have ported TNs, would they be able to submit a Part 4 once the block is effective, given they can confirm those TNs are active? Numbering Resource Optimization order FCC 00-104, paragraph 240 states "....we conclude that the definition of placing an NXX code “in service” should be clarified to mean not just activation of the code through transmission of the local routing information to the LERG, but also that the carrier has begun to activate and assign to end users numbers within the NXX code." The TBCOCAG definition of "In-Service" is: "A Central Office (CO) Code (NPA-NXX) or Thousands-Block (NPA-NXX-X) for which local routing information appears in the LERG™ Routing Guide, and one (1) or more Telephone Numbers (TN) within the CO Code or Thousands-Block has been Assigned to an end user (FCC 00-104, ¶240). Numbers that are categorized as Administrative, Aging, Intermediate, Reserved, or Available cannot also be Assigned and do not satisfy the In Service requirement." This definition does not explicitly state that the TNs have to be assigned to an end user of the current carrier.
  • Resolution: ATIS-INC updated ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines, with the updates in contribution INC-2026-00113R001.
  • Status: Initial 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: Final 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

ESIF

• Document Number: ATIS-0500049
• Title: GeoRouting for 988 voice calls
• Type: New
• View Here

Recent Policy Filings

INC

• Date: 02/19/2026
• Description: Intervention in Response to Telecom Notice of Consultation CRTC 2026-61
• View filing