Presentation is loading. Please wait.

Presentation is loading. Please wait.

Industry Numbering Committee (INC) Report to the NANC

Similar presentations


Presentation on theme: "Industry Numbering Committee (INC) Report to the NANC"— Presentation transcript:

1 Industry Numbering Committee (INC) Report to the NANC
Dyan Adams, INC Co-Chair Connie Hartman, INC Co-Chair March 28, 2017

2 Overview About INC INC Meetings
Issue 832, Add language to the Thousands-Block Pooling Administration Guidelines (TBPAG) and Central Office Code Assignment Guidelines (COCAG) Regarding Documentation Needed for Non-Exclusive Nationwide FCC Licenses Issue 835, Update TBPAG and COCAG to Clarify that the 30-Day State Notification Required by Interconnected VoIP Service Providers Applies to Growth Requests as Well as Initial Requests Issue 838, Requirements for Additional Carrier Identification Code (CIC) Assignments and Direction for Non-Use Issues in Initial Closure, Initial Pending, and Tabled Issues in Final Closure Relevant INC Web Pages

3 About INC The Industry Numbering Committee (INC) provides an open forum to address and resolve industry-wide issues associated with planning, administration, allocation, assignment, and use of North American Numbering Plan (NANP) numbering resources within the NANP area. Membership To become a member of INC or ATIS, see To understand how INC operates, see

4 INC Meetings Meetings Since the previous NANC meeting, INC met on January 25-26, February 10, and March Future Meetings Meeting Dates Location INC 154 May 9-11, 2017 Bellevue, WA INC 155 Week of July 24, 2017 Denver, CO INC 156 Week of September 18, 2017 Washington, DC INC 157 Week of November 13, 2017 Overland Park, KS

5 Issue 832, Add Language to the TBPAG and COCAG Guidelines Regarding Documentation Needed for Non-Exclusive Nationwide FCC Licenses The PA and NANPA are seeing an increased use of the non-exclusive MHz Radio Service nationwide FCC license as proof of certification, and recognized that INC Guidelines should fully document the requirements needed when using this type of license. Service providers are to provide the MHz Service Registration Acceptance Letter from the FCC to establish that the applicant has registered fixed sites or base stations, and the location of those sites. The TBPAG and the COCAG were updated to add direction to service providers using these licenses that is consistent with the language previously added to the p-ANI Guidelines.

6 Issue 835, Update Guidelines to Clarify that the 30-Day State Notification Required by Interconnected VoIP Service Providers Applies to Growth Requests as Well as Initial Requests The TBPAG and the COCAG indicate that the 30-day state notification required by interconnected VoIP service providers is required for both initial and growth requests, consistent with 47 CFR § (g) (3) and FCC , ¶ 14 and 34. INC added additional language to the TBPAG and the COCAG to draw attention to the 30-day state notification requirement for growth requests. Clarification was added to ensure applicants are aware of the requirements and to prevent the denial of those applications.

7 Issue 838, Requirements for Additional CIC Assignments and Direction for Non-Use
INC updated the CIC Assignment Guidelines to reinforce the requirement that CIC assignees shall have a current Entity Access/Usage Report on file with NANPA to: Receive additional CICs; and Demonstrate CIC use and prevent the reclamation of assigned CICs. Similar to NRUF reporting, the Entity Access/Usage Report is a required semi-annual report for CIC assignees to report CIC usage to NANPA.

8 Issues in Initial Closure and Tabled Issues
Issue 814, Verification that Switching ID/POI on NXX Application is in the Requested Rate Center LATA Issue 834, Reduce 45-day Block Aging Interval Issue 835, Update TBPAG and COCAG to Clarify that the 30-Day State Notification Required by Interconnected VoIP Service Providers Applies to Growth Requests as Well as Initial Requests Issue 836, Update COCAG Section to Reflect the Sunset Of 555 Line Number Assignments Issue 837, Can 976 NXXs Be Pooled? Issue 838, Requirements for Additional CIC Assignments and Direction for Non-Use Tabled: Issue 748: Assess Impacts on Numbering Resources and Numbering Administration with Transition from Public Switched Telephone Network (PSTN) to Internet Protocol (IP)

9 Issues in Final Closure
Issue 826, Criteria Added: to Address Conflicting Requirements Between the ATIS Packet Technologies and System Committee (PTSC) and the Industry Numbering Committee (INC) Regarding the Dual Assignment of 10-Digit Numbers as Both a Location Routing Number (LRN) and a Subscriber Directory Number (DN) Issue 827, Relevant Pages of Interconnected VoIP Provider and Carrier Partner Agreement Issue 828, Update to Table 5.1 of the 555 NXX Line Number Reference Document Issue 829, Documentation Needed when the Carrier Partner Name on the Carrier Partner Agreement does not Match the Carrier Partner Name on the Interconnection Agreement Issue 831, Revisions to Interim and Final Jeopardy Procedures Issue 832, Add language to the TBPAG and COCAG Guidelines Regarding Documentation Needed for Non-Exclusive Nationwide FCC Licenses Issue 833, Submit Part 4 for Dedicated CO Code Directly into the Pooling Administration System (PAS)

10 Relevant INC Web Pages INC Homepage: INC Published Documents: Anyone interested in information on INC or INC documents may contact Jackie Wohlgemuth, ATIS INC Manager, via at or (913)


Download ppt "Industry Numbering Committee (INC) Report to the NANC"

Similar presentations


Ads by Google