June 2020

Committee Reports

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

• INC: Industry Numbering Committee
  • Issue: 0868
  • Title: New codes not in routing on and after the code effective date
  • Statement: Noticing during our testing, new NPA-NXXs are not in routing on and after our code effective date. This requires trouble tickets to the affecting carrier and usually several rounds of escalations for resolution. This is only with the carriers we are able to test with (6). No way to know how many if any other carriers dont have our new codes in routing until we get customer complaint calls. Some carriers have a separate process we are required to follow, but most are updating routing for new codes via LERG.
  • Resolution: INC agreed to add footnotes to various sections in ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG), as contained in INC-2020-00056R000, to advise readers of responsibilities around NXX code openings and the availability of trouble reporting contact information on the NGIIF website.
  • Status: Final Closure

  • Issue: 0887
  • Title: Add Clarification to the TBCOCAG Regarding Documentation Needed for Thousands-Block Transfers
  • Statement: Recently, Pooling Administration (PA) has received incorrect/incomplete documentation in regard to Thousands-Block transfers. The PA identified improvements to Sections 9.1.9, 9.2.5 and 9.3.4 of the TBCOCAG in order to provide better direction to Service Providers on the documentation required when requesting a Thousands-Block transfer.
  • Resolution: INC updated ATIS-0300119, Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Assignment Guidelines (TBCOCAG) Sections 9.1.9, 9.2.5, and 9.3.4 with clarifications on the documentation needed for Thousands-Block transfers as shown in INC-2020-00039R001.
  • Status: Final Closure

  • Issue: 0891
  • Title: TBCOCAG update to ensure all service providers are notified of expedited code activations or expedited change of porting/pooling status
  • Statement: Expedited code activations or expedited changes of Portability status beyond the expedite lead time specified in the guidelines have the potential of causing call failure in networks that have not been made aware of the expedited code activation. Additionally, the expedited code activation decision makers may not consider or be informed of the facility readiness of the requesting service providers homing tandem.
  • Resolution:
  • Status: Final Closure

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

• NGIIF: Next Generation Interconnection Interoperability Forum
  • Issue: 0064
  • Title: Update ATIS-0300106, Intercarrier Call Completion/Call Termination Handbook, to Include Analytics as a Call Completion Root Issue
  • Statement: There is a need to identify an additional root cause for call completion issues. The initial development of the call completion handbook did not contemplate the impact of call analytics to call completion.
  • Resolution: NGIIF amended Sections 5 and 7 of ATIS-0300106, Intercarrier Call Completion/Call Termination Handbook and updated the Intercarrier Troubleshooting Quick Reference Tool, to identify call analytics as a root cause for call completion/call termination issues.
  • Status: New Issue

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

• NRSC: Network Reliability Steering Committee
  • Issue: 0045
  • Title: Intra-Company Outage Reporting Consistency (previously OC3 Reporting Consistency)
  • Statement: The NRSC has been asked by the PSHSB to look at ways to align the industry on reporting for (new in 2018) OC3 667 User Minute outages. (Modified 4/16/2020. Following the clarification as noted in the Issue Statement/Business need, the NRSC determined the Suggested Solution should be The NRSC should provide a recommendation to the industry to report outages consistently within each company.)
  • Resolution: The NRSC Outage Reporting Advisory Subcommittee drafted a Best Practice for consideration by CSRIC stating, “Network Operators and Service Providers should ensure intra-company consistency for NORS and DIRS outage reporting.” This Best Practice was submitted to CSRIC on Xxx xx, 2020.
  • Status: Final Closure

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

• OBF: Ordering and Billing Forum
  • Issue: 3652
  • Title: Access Service Ordering Guidelines (ASOG): Modify Site Contact (SITE CON) (Practice 001) to include Access Customer Terminal Location (ACTL)
  • Statement: There is a business need to add ACTL to the SITE CON field description (practice 001).
  • Resolution: Added ACTL to the SITE CON field description.
  • Status: Initial Closure

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

• PTSC: Packet Technologies and Systems Committee
  • Issue: 0158
  • Title: Non-IP Call Authentication Evaluation
  • Statement: PTSC Non-IP Call Authentication Task Force (NIPCA TF) will identify and document call authentication challenges facing TDM networks, investigate the feasibility of potential solutions in this area, and evaluate the implementation viability of TDM call authentication frameworks.
  • Resolution:
  • Status: New Issue

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

• SNAC: SMS/800 Number Administration Committee
  • Issue: 3413
  • Title: Provide Unsolicited messages for any status change or record update
  • Statement: Anytime a record change is made either by GUI user at SMS/800 or an MGI user, the affected MGI user (according to the SMS screens) should have the option of getting an unsolicited message notifying the user about the change.
  • Resolution: As MGI will be sunset 2021, the business need no longer exists. It was proposed that the Issue be placed into Initial Closure.
  • Status: Initial Closure

  • Issue: 3421
  • Title: Aging Process for Toll Free Numbers
  • Statement: Toll Free Numbers are being changed from Working to Disconnect to Spare within the same business day. This is allowing numbers to be immediately re-assigned to new customers, which could give RespOrgs a means to facilitate unauthorized Service Subscriber Changes. In addition, eliminating the aging process creates residual calls for new unexpected customers, and in some cases requires immediate replacement of the new number to avoid additional employee time required to handle & address misdials.
  • Resolution: Issue 3421 was opened to work to prevent RespOrgs from disconnecting and sparing numbers on the same day, as this had caused many residual and/or unwanted calls for the future and unsuspecting Service Subscriber. Somos added a last active date to toll-free number records to help RespOrgs better identify how quickly numbers are disconnected and subsequently spared. In addition, the FCC has recently issued a 45-day mandatory aging process as part of their efforts to help mitigate fraud/spoofing. SNAC feels that this will help to reduce the amount of residual/unwanted calls on numbers in the spare pool and thus the Issue may be closed.
  • Status: Initial Closure

  • Issue: 3423
  • Title: Incorrect Originating Information
  • Statement: All Toll Free number calls, including those from wireless, VoIP providers, and local numbers that have been ported, are not always providing the actual 10-digit (standard) ANI and PSTN networks/switches. In many cases, the toll-free customer is not receiving the accurate geographic origination of the call to allow for correct routing information.
  • Resolution: North American Numbering Council (NANC) Future of Numbering (FON) FTN4 subcommittee reported in this topic and ultimately, it was recommended that companies would be most effective by filing complaints with the FCC to resolve the issue of rectifying incorrect originating information in toll-free calls.
  • Status: Initial Closure

  • Issue: 3437
  • Title: Change usage of CIC 0110 / new SOMOS requirement
  • Statement: All TF numbers (1+8xx) are managed and located in the SMS/800 database maintained by Somos, a non-profit designated as the Toll Free numbering administrator by the FCC. Responsible Organizations (RespOrgs) who are registered created the electronic records including the TF number, the POTS routeable, LATA and other relevant information. Additionally, the records entered by the RespOrg contain the CIC (Carrier Identification Code) of the Carrier who is designated to carry the call across their network to the destination POTS number defined in the record (CPR). A specific CIC, 0110, was originally allocated so Local Exchange Carriers (LEC) can manage intraLATA Toll Free traffic terminating on their networks. To use the code, a LEC must own the line of the terminating location. In the case of a CLEC that means the line must have been either facility based or a UNE-P line. Additionally, CIC 0110 was utilized to also allow network service providers (i.e., the four RBOCs and Cincinnati Bell) to manage intraLATA Toll Free traffic traveling on their networks. Due to mergers and acquisitions it is felt that the need for CIC 0110 has outlived its usefulness. In addition, these changes are being proposed to help eliminate the misuse, intentional or unintentional, of CIC 0110. This proposal is the partial retiring of CIC 0110. Two changes to the usage of CIC 0110 are proposed.
  • Resolution: Direction was given to Verizon, AT&T, and CenturyLink to go to the FCC directly. As this there are no additional items for SNAC to follow up on, this Issue will be closed.
  • Status: Initial Closure

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

• STEP: Sustainability in Telecom: Energy and Protection Committee
  • Issue: 0176
  • Title: Translation Table of Safety Related Voltages and Currents
  • Statement: There is a need to create a new technical report pertaining to a translation and comparison table of safety related voltage, current and power terminology derived from ATIS Standards, NEC 70, 70E, UL Safety Standards, IEC Safety Standards, GR 1089, etc.
  • Resolution: The translation table will be incorporated into Issue 0179, Revision of ATIS-0600001 Electrical Protection Standards and Reference Documents Associated with Telecommunication Networks.
  • Status: Final Closure

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

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

INC

• Document Number: ATIS-0300119(2020-06)
• Title: Thousands-Block (NPA-NXX-X) & Central Office Code (NPA-NXX) Administration Guidelines (TBCOCAG)
• Type: Revision
• View Here

NGIIF

• Document Number: ATIS-0300106(2020-06)
• Title: Intercarrier Call Completion/Call Termination Handbook
• Type: Revision
• View Here

PTSC

• Document Number: ATIS-1000089
• Title: Study of Full Attestation Alternatives for Enterprises and Business Entities with Multi-Homing and Other Arrangements
• Type: New
• View Here

SNAC

• Document Number: ATIS-0417001-004
• Title: Industry Guidelines for Toll Free Number Administration
• Type: Revision
• View Here

WTSC

• Document Number: ATIS-0700043
• Title: Wireless Emergency Alert (WEA) 3.0 via 5G Public Warning System Specification
• Type: New
• View Here

Recent Policy Filings

No Policy Filings this month.