Presentation on theme: "Industry Numbering Committee (INC) Report to the NANC Dyan Adams, INC Co-Chair Shaunna Forshee, INC Co-Chair September 17, 2014."— Presentation transcript:
Industry Numbering Committee (INC) Report to the NANC Dyan Adams, INC Co-Chair Shaunna Forshee, INC Co-Chair September 17, 2014
INC Report to the NANC 2 Overview About INC INC Meetings/Membership Issue 748: Assess Impacts on Numbering Resources and Numbering Administration with Transition from Public Switched Telephone Network (PSTN) to Internet Protocol (IP) Issue 762: CO Codes Assigned/Transferred only to Providers who own Switching Facilities
INC Report to the NANC 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 http://www.atis.org/membership/become.asp. http://www.atis.org/membership/become.asp To understand how INC operates, see http://www.atis.org/legal/OP.asp http://www.atis.org/legal/OP.asp
INC Report to the NANC 4 INC Meetings Meetings Since the previous NANC meeting, INC held one face-to-face meeting from July 29-31, 2014, and interim meetings on July 23 and August 26, 2014. An INC meeting is being held this week in Washington, DC.
INC Report to the NANC 5 Issue 748: Assess Impacts on Numbering Resources and Numbering Administration with Transition from Public Switched Telephone Network (PSTN) to Internet Protocol (IP) INC has drafted a response to the FCC regarding the impacts of large-scale rate center consolidation during the transition from PSTN to IP. Outlined positive and negative impacts of large-scale rate center consolidation Documented impacts to carriers networks and systems Identified that regulatory changes would be necessary Concluded that, given the complexities related to large-scale rate center consolidation, it is premature to develop a plan for implementation. However, as carriers’ network architecture and the market drives the need for such consolidation, the industry and regulators should work collaboratively to develop a plan.
INC Report to the NANC 6 Issue 762: CO codes assigned/transferred only to providers who own switching facilities When a Central Office (CO) code is assigned and the Part 1 has an invalid Switching Entity or Point of Interconnection, the CO code cannot be built in iconectiv's Business Integrated Routing & Rating Database System (BIRRDS). This can result in: Delays that affect other service providers with blocks from that code. More red blocks in the pool. Stranded numbers if there is no regulatory direction to reclaim the code. INC has modified the guidelines to expand verification that the switching ID/POI is valid for an NPA-NXX assignment and is built in BIRRDS.
INC Report to the NANC 7 Issues in Initial Pending Issue 768, Updates to the Part 1B form Issue 765, Updates to the Part 1A form Issue 770, Updates to the TBPAG Part 3 Form Issue 772, Update to the TBPAG Appendix 3: MTE & Certification Worksheet
INC Report to the NANC 8 Issues in Final Closure Issue 757, Need to Review and Update Telcordia Technologies Branding Reference in all ATIS INC Documents Issue 762, CO codes assigned/transferred only to providers who own switching facilities Issue 773, Allocation of a 5XX NPA to Canadian Service Providers Issue 776, Approval of Part 4-PA prior to code effective date Issue 780, Update NPA Relief Planning and Notification Guidelines- Appendix F
INC Report to the NANC 9 Relevant INC Web Pages INC Homepage: http://www.atis.org/inc/index.asphttp://www.atis.org/inc/index.asp INC Issues (historical and active): http://www.atis.org/inc/incissue.asp http://www.atis.org/inc/incissue.asp INC Published Documents: http://www.atis.org/inc/incguides.asp http://www.atis.org/inc/incguides.asp Anyone interested in information on INC or INC documents can contact Jackie Voss, ATIS INC Manager, via email at email@example.com or (913) firstname.lastname@example.org