March 2022

Committee Reports

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

• ESIF: Emergency Services Interconnection Forum
  • Issue: 106
  • Title: Caller Authentication in Legacy E9-1-1 and Transitional NG9-1-1 Environments
  • Statement: The FCCs Second Report and Order In the Matter of Call Authentication Trust Anchor, released October 1, 2020, formalizes requirements for supporting caller identity authentication technology in the non-IP portions of voice service provider networks. Specifically, it requires that, by June 30, 2021 a voice service provider shall either: (a) upgrade its entire network to allow for the initiation, maintenance, and termination of SIP calls and fully implement the STIR/SHAKEN framework as required in 47 CFR 64.6301 throughout its network; or (b) maintain and be ready to provide the Commission on request with documented proof that it is participating, either on its own or through a representative, including third party representatives, as a member of a working group, industry standards group, or consortium that is working to develop a non-Internet Protocol caller identification authentication solution, or actively testing such a solution. While the Second Report and Order does not explicitly address 9-1-1 calls that are processed using legacy TDM-based architectures or transitional NG9-1-1 architectures that include TDM components, it also does not exempt network providers from supporting caller authentication in such networks. It is also important to note that ATIS formed the Non-IP Call Authentication Task Force under PTSC to identify and assess various alternatives for addressing the requirements related to caller authentication in non-IP networks, as described in the Second Report and Order. To date, the Task Force has not addressed mechanisms for supporting caller identity authentication for 9-1-1 calls or callback calls in a legacy 9-1-1 or transitional NG9-1-1 environment. However, in recent discussions, they have indicated an interest in doing so. Further study is required to determine whether any of the alternatives being considered by the Task Force will accommodate the unique signaling characteristics and network architectures that support 9-1-1 calling in a legacy or transitional environment. ESIF NGES has the expertise needed to perform this assessment and to evaluate the feasibility of supporting caller authentication in a legacy 9-1-1 or transitional NG9-1-1 environment.
  • Resolution: This Issue was resolved with the publication of ATIS-0500046, Analysis of Non-IP Call Authentication Mechanisms in Support of Emergency Services.
  • Status: Final Closure

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

• INC: Industry Numbering Committee
  • Issue: 0897
  • Title: Streamline INC forms for the newly combined NANPA and PA contracts and NANP Administration System (NAS)
  • Statement: With the newly combined NANPA and PA contracts, NANPA suggests consolidating and updating existing TBCOCAG forms to streamline the process of requesting thousands-blocks and CO codes, which would be part of the newly developed NANP administration system (NAS).
  • Resolution: INC agreed to update the Forms & Appendices for ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines, as proposed in the following contributions: INC-2021-00003R001, -00004R001, -00005R001, -00006R001, -00007R001, -00008R001, -00009R001, -00010R001, -00011R001, and INC-2021-00012R001. These changes that impact the new NAS and the NPAC SMS will require coordination between the two systems. This Issue will be in Initial Pending until the final implementation date of the new NAS system.
  • Status: Initial Pending

  • Issue: 0902
  • Title: Updates to the NPA Allocation Plan and Assignment Guidelines Forms for the combined NAS system
  • Statement: NANPA suggests modifications to the NPA Allocation Plan and Assignment Guidelines Forms for consistency in format with other INC resource forms.
  • Resolution: INC agreed to update the Part 1 and Part 2 Forms of ATIS-0300055, NPA Allocation Plan and Assignment Guidelines, for the combined NAS with the changes contained in INC-2021-00029R001 and INC-2021-00030R001. Pending implementation of the combined NAS.
  • Status: Initial Pending

  • Issue: 0903
  • Title: Updates to the Carrier Identification Code (CIC) Assignment Guidelines Forms for the combined NAS system
  • Statement: NANPA suggests modifications to the Carrier Identification Code (CIC) Assignment Guidelines Forms for consistency in format with other INC resource forms for the combined NAS.
  • Resolution: INC agreed to update the forms for ATIS-0300050, Carrier Identification Code (CIC) Assignment Guidelines, for the combined NAS system with the changes contained in INC-2021-00032R001, -00033R001, -00034R001, -00035R001, -00036R001, and -00037R001. Pending implementation of the combined NAS.
  • Status: Initial Pending

  • Issue: 0904
  • Title: Updates to the p-ANI Administration Guidelines Forms for the combined NAS system
  • Statement: NANPA suggests modifying the p-ANI Administration Guidelines Forms to be consistent with the Thousands-Block and Central Office Code Administration Guidelines forms so all NANP resource forms have a consistent naming format and order in the combined NAS system.
  • Resolution: INC agreed to update the forms and appendices for ATIS-0300089, p-ANI Administration Guidelines, for the combined NAS forms with the changes contained in INC-2021-00039R001, -00040R001, -00041R000, and -00042R000. Pending implementation of the combined NAS.
  • Status: Initial Pending

  • Issue: 0905
  • Title: Updates to the Non-Geographic 5XX-NXX Code Assignment Guidelines Forms for the combined NAS system
  • Statement: NANPA suggests modifications to the Non-Geographic 5XX-NXX Code Assignment Guidelines Forms for consistency in format with other INC resource forms for the combined NAS system.
  • Resolution: INC agreed to update the forms for ATIS-0300052, Non-Geographic 5XX-NXX Code Assignment Guidelines, for the combined NAS with the changes contained in INC-2021-00044R001, -00045R001, and -00046R000. Pending implementation of the combined NAS.
  • Status: Initial Pending

  • Issue: 0906
  • Title: Updates to the 9YY NXX Code Assignment Guidelines Forms for the combined NAS system
  • Statement: NANPA suggests modifications to the 9YY NXX Code Assignment Guidelines Forms for consistency in format with other INC resource forms for the combined NAS system.
  • Resolution: INC agreed to update the forms for ATIS-0300060, 9YY NXX Code Assignment Guidelines, for the combined NAS with the changes contained in INC-2021-00048R001, -00049R001, and -00050R001. Pending implementation of the combined NAS.
  • Status: Initial Pending

  • Issue: 0918
  • Title: Update language to the TBCOCAG regarding the cancellation of CO Code and Thousands-Block Disconnects for the new combined NAS
  • Statement: With the new combined NAS, some enhancements are being implemented for users who wish to withdraw and cancel Thousands-Block and CO Code Disconnect requests. With this change, NANPA is suggesting updates to the language in ATIS-0300119 Thousands-Block (NPA-NXX-X) and Central Office Code (NPA-NXX) Administration Guidelines Sections 11.1.8 (Thousands-Blocks), 11.2.14 (Pooled CO Codes), and 11.3.12 (Non-Pooled CO Codes) to incorporate changes in the new combined NAS. In addition, we recommend updating the language and formatting in Section 11.1.8 (Thousands-Blocks) to be in alignment with 11.2.14 (Pooled CO Codes), and 11.3.12 (Non-Pooled CO Codes) for consistency.
  • Resolution: INC agreed to update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines, with the updates reflected in INC-2021-00104R002. This Issue will go into Initial Pending dependent on the release of the combined NAS.
  • Status: Initial Pending

  • Issue: 0920
  • Title: Add language to TBCOCAG Section 5.3.3 c) indicating that an Appendix 2 Thousands-Block Months to Exhaust Certification Worksheet – TN Level shall not be required for an Initial Dedicated Customer Request
  • Statement: For the new combined NAS, NANPA suggests updating ATIS-0300119 Thousands-Block (NPA-NXX-X) and Central Office Code (NPA-NXX) Administration Guidelines Section 5.3.3 to state that an Appendix 2 Thousands-Block Months to Exhaust Certification Worksheet TN Level shall not be required for an Initial Dedicated Customer request since the entire NPA-NXX is assigned to a single customer and a customer letter is required and an Appendix 1 CO Code Months to Exhaust Certification Worksheet TN Level is not required for an Initial Non-Pooled CO Code.
  • Resolution: INC agreed to update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines, with the updates reflected in INC-2021-00108R000. This Issue will go into Initial Pending contingent on the release of the combined NAS.
  • Status: Initial Pending

  • Issue: 913
  • Title: Updates to TBCOCAG 7.1.15 and 7.1.16
  • Statement: Updates to TBCOCAG 7.1.15 and 7.1.16 As more NPAs are reaching exhaust, more carriers are donating blocks to the Industry Pool. Carriers are failing to protect their working TNs in those donated blocks causing double assignment by both the donating carrier and the carrier acquiring the block from the Pool.
  • Resolution: INC agreed to place Issue 914 into Initial Closure with no changes to ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines. Consensus was not reached on imposing a timeframe in which the donating carrier can request the return of a working, unprotected TN from the new Thousands-Block holder.
  • Status: Final Closure

  • Issue: 0923
  • Title: Remove and update inaccurate language from TBCOCAG Section 13.1.1 b)
  • Statement: Section 13.1.1 b) of the TBCOCAG has some inaccurate language. Currently Section 13.1.1 b)1) states when the Code Holder submits an ISP Block port and no NPAC notification is required the effective date shall be no less than 9 calendar days. However, an ISP Block Port always requires NPAC notification. Section 13.1.1 b)2) states when a non-Code Holder submits an ISP Block port the effective date shall be no less than 8 business days. ISP Block Port requests may only be submitted by the Code Holder of a non-pooled NPA-NXX and all new ISP Block Port applications have a minimum effective date of 8 business days as NPAC notification is required. This contribution suggests removing Section 13.1.1 b)1) and updating Section 13.1.1 b)2) to reflect the actual process.
  • Resolution: INC agreed to update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines, with the updates reflected in INC-2022-00004R000.
  • Status: Final Closure

  • Issue: 0924
  • Title: Add language to the Disconnect sections of the TBCOCAG stating when regulatory authority is provided NANPA/PA shall request iconectiv to disconnect NXD records in BIRRDS
  • Statement: Today when thousands-blocks and/or CO Codes are reclaimed or voluntarily returned and a new block holder/code holder cannot be found, the PA/NANPA sends notification from the appropriate regulatory authority and requests TRA to disconnect the NXD records associated with the thousands-block/CO Code when there is no AOCN of record (EMB1). This action is not captured in the current guidelines, therefore, this issue suggests adding text documenting this step.
  • Resolution: INC agreed to update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines, with the updates reflected in INC-2022-00006R001.
  • Status: Final Closure

  • Issue: 0925
  • Title: Update INC Guidelines to allow NANPA to assign the 988 Central Office Code in areas where 10-digit local dialing has been implemented
  • Statement: When 988 was first designated by the FCC as the three-digit abbreviated dialing code to reach the National Suicide Prevention Lifeline, INC added language to the TBCOCAG which restricted the 988 Central Office (CO) code from being made available for assignment in geographic NPAs on a going forward basis. In those NPAs where 988 was already assigned as a CO code and 7-digit local dialing existed, the industry is transitioning to mandatory 10-digit local dialing by July 15, 2022 in order to prevent technical issues in some switches with the use of 988 as an abbreviated dialing code. Mandatory 10-digit local dialing eliminates the issue with some switches being unable to determine whether an originating caller is attempting to dial 988 to reach the NSPL or 988-XXXX to reach a local number. Thus there are no technical reasons that the 988 CO code cannot be made available for assignment in geographic NPAs in the US and its territories where mandatory 10-digit local dialing has already been implemented (Note: More than 110 988 CO codes are already assigned in geographic NPAs in the US and its territories where mandatory 10-digit local dialing has been implemented).
  • Resolution: INC agreed to update ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines, with the updates reflected in INC-2022-00008R000. INC agreed that NANPA shall not make the 988 NXX Codes in the 82 geographic NPAs impacted by the 988 federal mandate available until January 15, 2023, to provide a 6-month buffer between activation of the 988 abbreviated dialing code and assignment of those 988 NXX codes.
  • Status: Final Closure

  • Issue: 0926
  • Title: Updates to NPA Relief Planning Guidelines on Relief Lives and Other Clarifications
  • Statement: In the current NPA Relief Planning Guidelines, a particular relief alternative must provide only 5 years of relief. That criteria has been in the Guidelines for 20+ years, likely documented at a time when geographic splits were common and frequent. Now that overlays are the most common and preferred method of relief, INC should revisit that criteria to streamline both the development and the deliberation of relief alternatives. Other sections in the Guidelines should be reviewed and updated as well, to provide clarifications and/or additional information.
  • Resolution: INC agreed to update ATIS-0300061, NPA Code Relief Planning and Notification Guidelines, with the updates reflected in INC-2022-00011R001.
  • Status: Final Closure

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

• NGIIF: Next Generation Interconnection Interoperability Forum
  • Issue: 0066
  • Title: Voice over Internet Protocol (VoIP) Interconnection Best Practices
  • Statement: There is an industry need for a document that focuses on VoIP interconnection issues. NGIIF should review current documentation for areas that address VoIP and consider how to consolidate this information into a single source.
  • Resolution: NGIIF added a new Section 7.1.3.7 (SIP Option Testing) to ATIS-0300118, NGIIF NGN Reference Document NGN Interconnection, and made additional editorial updates throughout.
  • Status: Final Closure

  • Issue: 0069
  • Title: Adding Robocall Mitigation Database (RMD) language to the Call Completion Handbook
  • Statement: The FCC has required all voice service providers to certify their SHAKEN/STIR implementation status in the Robocall Mitigation Database (RMD). VSPs that are not appropriately registered should expect calls to be blocked as of September 28, 2021 by other VSPs who they exchange traffic with, causing call failures. This contribution is to add applicable language to the Call Completion Handbook to help VSPs identify RMD related call failures and means by which to correct.
  • Resolution: Language was added to Section 5.5.1 (Use of Call Analytics) of ATIS-0300106, Intercarrier Call Completion/Call Termination Handbook, referencing industry best practices for redress.
  • Status: Final Closure

  For more information, visit the NGIIF home page or contact Mignot Asefa.

• SNAC: SMS/800 Number Administration Committee
  • Issue: 3439
  • Title: Modification to the implementation of FCC Mandate for Disconnected Toll-Free Numbers
  • Statement: To ensure the integrity of Toll-Free and support the fight against illegal robocalls, a mandate was issued that impacts Toll-Free Number (TFN) statuses in the SMS/800 TFN Registry. Per the new rule, all disconnected numbers including disconnected Toll-Free Numbers will not go into SPARE status until forty-five (45) days after their date of disconnection. The implementation of this feature requires the Resp Org to be responsible for paying the Tariff on these numbers for an additional 45 days and modify their Disconnect/Spare procedures. It is unclear this new FCC Procedure has a benefit to the Toll Free Industry.
  • Resolution:
  • Status: New Issue

  • Issue: 3440
  • Title: Distribution of the unclaimed 833 numbers
  • Statement: In May of 2017, 147 Resp Orgs participated in the 833 NPA pre-code opening. The results were 72,028 TFNs where requested, 17,638 of which received multiple requests. All but the 17,638 numbers were released to the Eco-System. These 17,638 numbers were held by Somos until an FCC designed auction was run on December 17, 2019. The results of the auction were 1,660 of the 17,638 TFNs received bids. Of those 1,660 numbers, 1,406 had a single bidder. Only 254 TFNs had multiple bids. The 15,978 TFNs, with zero bids are still being held by Somos, awaiting instructions from the FCC. The FCC also needs to determine what to do with the other 800 TFNs that have been set aside for potential auction/market based assignment. With the 833 Auction, the FCC allowed entities to sell and buy those Auctioned numbers in an open market. The current holders of these Auctioned numbers can sell these numbers to anyone willing to pay for them, at prices negotiated by the buyer and seller. It doesnt seem logical to treat certain Toll Free Numbers differently than the rest of the inventory. Extending this capability to all Toll Free Numbers may stimulate the Toll Free Market and may put an end to the current Gray Market. The purpose of this issue is to determine the best way to release these 15,978 TFNs which have been kept out of circulation since May of 2017.
  • Resolution:
  • Status: New Issue

  • Issue: 3441
  • Title: LRN being sent as the Calling Party Number
  • Statement: The LRN is being sent on some toll-free calls as the calling party number. In these instances, the true calling party number is not being included in the call record. This could result in calls being mis-routed on Shared-Use Numbers, as well as instances where advanced routing is in place. This could also present issues with the company thats receiving these calls as theyre not able to return a missed call or follow up on a potential lead.
  • Resolution:
  • Status: New Issue

  For more information, visit the SNAC home page or contact .

• STEP: Sustainability in Telecom: Energy and Protection Committee
  • Issue: 0191
  • Title: Review of Battery plant questions and ATIS 0600315, Voltage Levels for DC-Powered Equipment Used in the Telecommunications Environment
  • Statement: Review ATIS 0600315 to determine if any changes in the requirements and test procedures are needed.
  • Resolution: This Issue was resolved with the publication of ATIS-0600315.2022, Voltage Levels for DC-Powered Equipment Used in the Telecommunications Environment.
  • Status: Final Closure

  For more information, visit the STEP home page or contact Mignot Asefa.

• WTSC: Wireless Technologies and Systems Committee
  • Issue: 0096
  • Title: Feasibility Study for WEA enhancements via a data transport path between AOs and a managed app
  • Statement: In the current standards and implementation of WEA, specific parameters are sent over the C interface (as defined in ATIS-0700037) which contain the elements necessary for the CMSP to broadcast the WEA alert. The broadcast WEA message is received by the mobile device, typically processed by the mobile device in the operating system and WEA-specific messaging software, and displayed to the user if appropriate WEA enhancements in the future would likely result in a number of impacts to the C interface, the CMSP Gateway and infrastructure, and mobile devices (including the device OS). These enhancements require not only standards changes, but require development, testing, and deployment of updates in the impacted elements. The standards updates, development and deployment require significant planning and effort, and consideration must be given to backwards compatibility and other deployment considerations. Thus, the timelines to implement enhancements could be on the order of 18-30 months or more, depending on the extent of the changes. In order to support the continued evolution of WEA, a study is proposed to determine the feasibility of developing a transport path between Alert Originators (AOs) and a well-managed WEA app in the mobile device. A goal of the development of this transport path is to be able to allow AOs to add WEA-related information applicable to a WEA alert without requiring changes to CMSP network elements and without requiring changes to WEA-supporting mobile devices other than updates, as needed, to the WEA app functionality.
  • Resolution:
  • Status: New Issue

  For more information, visit the WTSC home page or contact Anna Karditzas.

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

NGIIF

• Document Number: ATIS-0300106(2022-03)
• Title: Intercarrier Call Completion/Call Termination Handbook
• Type: Revision
• View Here
• Document Number: ATIS-0300118(2022-03)
• Title: Next Generation Interconnection Interoperability Forum (NGIIF) NGN Reference Document NGN
• Type: Revision
• View Here

OBF

• Document Number: ATIS-0404110-0040
• Title: Unified Ordering Model - Access Service Request (UOM-ASR) Volume I
• Type: Revision
• View Here
• Document Number: ATIS-0410002-0040
• Title: Unified Ordering Model (UOM) Volume II – Analysis - For Access Service Ordering Guidelines (ASOG)
• Type: Revision
• View Here
• Document Number: ATIS-0410003-0040
• Title: Unified Ordering Model (UOM) - Volume III – Design - For Access Service Ordering Guidelines (ASOG)
• Type: Revision
• View Here
• Document Number: ATIS-0404000-0065-ATIS-0404028-0065
• Title: Access Service Request (ASR) Guidelines Version 65
• Type: Revision
• View Here

STEP

• Document Number: ATIS-0600315.2022
• Title: Voltage Levels for DC-Powered Equipment Used in the Telecommunications Environment
• Type: Revision
• View Here

WTSC

• Document Number: ATIS-0700037.v003
• Title: Wireless Emergency Alert (WEA) 3.0 Federal Alert Gateway to CMSP Gateway Interface Specification
• Type: Revision
• View Here
• Document Number: ATIS-0700038.v003
• Title: WEA 3.0 Federal Alert Gateway to CMSP Gateway Interface Test Specification
• Type: Revision
• View Here

Recent Policy Filings

NRSC

• Date: 3/9/22
• Description: Comments in response to FCC NRPM on potential safeguards in connection with the sharing of Network Outage Reporting System (NORS) and Disaster Information Reporting System (DIRS) data with agencies acting on behalf of the Federal government, U.S. states and/or territories, the District of Columbia, and Tribal Nations.
• View filing

INC

• Date: 3/11/22
• Description: Comments in response to the WCB Public Notice on whether the public interest would be served if the Bureau were to issue a waiver that would forestall exhaustion of the single area codes used in Maine and North Dakota, area codes 207 and 701, respectively.
• View filing
• Date: 3/28/22
• Description: Reply Comments in response to comments submitted to the WCB Public Notice on a waiver that would forestall exhaustion of the single area codes used in Maine and North Dakota, area codes 207 and 701.
• View filing