ATIS 0300060-2016 9YY NXX Code Assignment Guidelines (Reissued to reflect that the amendments to 47 CFR 52 15(g)(2) and (g)(3) published at 80 FR 66454 October 29 2015 are effectiv.pdf

《ATIS 0300060-2016 9YY NXX Code Assignment Guidelines (Reissued to reflect that the amendments to 47 CFR 52 15(g)(2) and (g)(3) published at 80 FR 66454 October 29 2015 are effectiv.pdf》由会员分享，可在线阅读，更多相关《ATIS 0300060-2016 9YY NXX Code Assignment Guidelines (Reissued to reflect that the amendments to 47 CFR 52 15(g)(2) and (g)(3) published at 80 FR 66454 October 29 2015 are effectiv.pdf（25页珍藏版）》请在麦多课文档分享上搜索。

1、 ATIS-0300060 9YY NXX CODE ASSIGNMENT GUIDELINES Reissued to reflect that the amendments to 47 CFR 52.15(g)(2) and (g)(3) published at 80 FR 66454, October 29, 2015, are effective February 4, 2016. February 16, 2016 Page 2 of 25 Copyright 2016 by the Alliance for Telecommunications Industry Solution

2、s, Inc. All rights reserved. The 9YY NXX Code Assignment Guidelines dated February 16, 2016, is copyrighted, published and distributed by ATIS on behalf of the Industry Numbering Committee (INC). Except as expressly permitted, no part of this publication may be reproduced or distributed in any form,

3、 including electronic media or otherwise, without the prior express written permission of ATIS. Participants in the INC and other parties are hereby authorized to reproduce this document and distribute it within their own business organizations for business purposes, provided that this notice contin

4、ues to appear in the reproduced documentation. Resale is prohibited. For ordering information, please contact: ATIS 1200 G Street N.W., Suite 500 Washington, DC 20005 (202) 628-6380 incatis.org A complete listing of INC Documents is available on the ATIS Web Site at: http:/www.atis.org/inc/incguides

5、.asp. Page 3 of 25 As a leading technology and solutions development organization, the Alliance for Telecommunications Industry Solutions (ATIS) brings together the top global ICT companies to advance the industrys most pressing business priorities. ATIS nearly 200 member companies are currently wor

6、king to address the All-IP transition, network functions virtualization, big data analytics, cloud services, device solutions, emergency services, M2M, cyber security, network evolution, quality of service, billing support, operations, and much more. These priorities follow a fast-track development

7、lifecycle from design and innovation through standards, specifications, requirements, business use cases, software toolkits, open source solutions, and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). The organization is the North American Organizatio

8、nal Partner for the 3rd Generation Partnership Project (3GPP), a founding Partner of the oneM2M global initiative, a member of and major U.S. contributor to the International Telecommunication Union (ITU), as well as a member of the Inter-American Telecommunication Commission (CITEL). For more infor

9、mation, visit www.atis.org. - 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. This docu

10、ment is maintained under the direction of ATIS and the INC. Suggestions for improvement of this document are welcome. They should be sent to the Alliance for Telecommunications Industry Solutions, INC Staff, 1200 G Street NW, Suite 500, Washington, DC 20005. All changes to this document shall be mad

11、e through the INC issue resolution process and adopted by the INC as set forth in the ATIS Operating Procedures. - Notice of Disclaimer e.g., 700, 950, etc. However, applicants requesting one of these codes are not precluded from receiving it, if unassigned. In the event that the applicants preferre

12、d code is unavailable, the applicant may specify up to five alternative codes in order of preference. If the preferred and alternatives are not available or the applicant does not indicate a preference for another specific code, the administrator will assign a code on a random basis. 5.11 If two app

13、licants request the same NXX code simultaneously (i.e., their written requests are received by the code administrator with the same time and date stamp) one of the applicants would be randomly selected to receive the NXX code. 5.12 Code Assignment Criteria for Initial Code Requests Applicants for an

14、 initial 9YY-NXX code assignment shall provide the Code Administrator with the following information: Projected monthly demand for new TNs in the next 12 months, substantiating the need for the NXX(s) requested. A commitment to place all code(s) allocated into service within six months from the date

15、 of assignment. A commitment that the applicant is or will be capable of providing service within sixty (60) days of the numbering resources activation date.7An applicant for initial numbering resources must include in its application evidence that the applicant is authorized to provide service in t

16、he area for which the numbering resources are being requested, and that the applicant is or will be capable of providing service within sixty (60) days of the numbering resources activation date.8For an initial 9YY code request, an applicant must provide one form of documentation from both Sections

17、5.12.1 and 5.12.2 below: _ 747 CFR 52.15 (g) (2) 847 CFR 52.15 (g) (2) 8 5.12.1 License and/or Certification An applicant shall provide evidence that demonstrates the SP has a license or authorization issued by the FCC or a Certificate of Public Convenience and Necessity (CPCN) issued by a State Reg

18、ulatory Body to provide service in the area for which the 9YY code is being requested. The SP shall email to the code administrator a copy of the FCC license or authorization9or CPCN that is appropriate for the Company Code Category Type of the OCN10provided on the SPs application: 5.12.1.1 An OCN w

19、ith a Company Code Category Type of ILEC, RBOC, ULEC, or CLEC shall provide evidence that demonstrates the SP has a CPCN issued by a State Regulatory Body to provide service in the area the 9YY code is being requested. 5.12.1.2 An OCN with a Company Code Category Type of WIRE or PCS shall provide ev

20、idence that demonstrates the SP has a license issued by the FCC to provide service in the area the 9YY code is being requested. 5.12.1.3 An OCN with a Company Code Category Type of IPES shall provide evidence that demonstrates the SP has a national authorization issued by the FCC. In the case that t

21、he name on the license or authorization issued by the FCC or CPCN does not match the SPs name on the application, the applicant shall provide documentation linking the name on the application with the name on the license or authorization issued by the FCC or CPCN. 5.12.2 Facilities Readiness An appl

22、icant shall provide appropriate evidence that facilities are in place or will be in place to provide service within 60 days of the numbering resources activation date (i.e., the LERGTMRouting Guide effective date) is required. Evidence shall be provided via email to the code administrator with the P

23、art A application. A. Interconnected VoIP Providers Interconnected VoIP providers shall demonstrate proof of facilities readiness by (1) providing a combination of an agreement between the interconnected VoIP provider and its carrier partner and an interconnection agreement between that carrier and

24、the relevant local exchange carrier (LEC), or (2) proof that the interconnected VoIP provider obtains interconnection with the _ 9See 47 CFR 52.15 (g) (3). 10See Section 5.2 for a list of permitted Company Code Category Types. 9 Public Switched Telephone Network (PSTN) pursuant to a tariffed offerin

25、g or a commercial arrangement that provides access to the PSTN.11When providing such documentation to the code administrator, the applicant shall provide only the relevant pages or indicate in the email to the code administrator the page numbers for the relevant pages if providing entire agreements

26、or documents. For interconnection agreements, the relevant pages are the cover page, area covered, the expiration date and the signature page from the interconnection agreements. For tariffed offering or commercial arrangement documents, the relevant pages are the cover page, pages that describe how

27、 traffic will be exchanged, term of the contract or expiration date, and the signature page. The code administrator shall deny any application when the relevant pages are not provided or the applicant does not indicate the page numbers of the relevant pages when providing entire documents via email.

28、 In the case that the name on an agreement does not match the applicants name on the application, the applicant shall provide documentation linking the name on the application with the name on the documents. B. SPs Other Than Interconnected VoIP Providers For applicants other than interconnected VoI

29、P providers, facilities readiness evidence may be provided by emailing to the code administrator a copy of any one of the following document(s)the SP selects: 1. A current executed interconnection agreement between a Local Exchange Carrier and the SP requesting numbering resources. The relevant page

30、s are the cover page, area covered, the expiration date and the signature page from the interconnection agreement. The SP shall provide only the relevant pages or indicate in the email the page numbers for the relevant pages if providing the entire interconnection agreement. The code administrator s

31、hall deny any application when the relevant pages are not provided or the SP does not indicate the page numbers of the relevant pages when providing the entire interconnection agreement via email. In the case that the name on the interconnection agreement does not match the SPs name on the applicati

32、on, the applicant shall provide documentation linking the name on the application with the name on the interconnection agreement. 2. Documentation of the state commission approval of the current interconnection agreement. In the case that the name on the state commission documentation does not match

33、 the SPs name on the application, the applicant shall provide documentation linking the name on the application with the name on the state commission documentation. 3. The SP business plan/pre-planning checklist (see Attachment B) to show that facilities for origination or termination for calls bein

34、g used for the requested code(s) have been requested and are anticipated to be completed in order to provide service within 60 calendar days of the LERG Routing Guide effective date. If the CLLI of the switch or _ 11FCC 15-70, 37. 10 POI provided on the business plan/pre-planning checklist has not b

35、een built on the SRD screen in BIRRDS, the applicant cannot utilize this type of proof of facility readiness and must provide one of the other four types of proof of facility readiness. The code administrator shall deny the application if the switching entity/POI CLLI entered on the business plan/pr

36、e-planning checklist has not been built in BIRRDS at the time the application is processed. 4. A confirmation letter or letter of intent provided by the LEC with which the requesting SP will interconnect. Interconnecting LECs are encouraged, but not required, to provide such letters. In the case tha

37、t the name on the letter does not match the SPs name on the application, the applicant shall provide documentation linking the name on the application with the name on the confirmation letter. 5. A letter from the applicant identifying a geographic thousands-block/code in service that uses the same

38、facilities and CLLI code that will be used to serve the initial 9YY-NXX code being requested and reflected on the application. In the case that the OCN name associated with the switch CLLI serving the existing block/code does not match the SPs name on the application, the applicant shall provide doc

39、umentation linking the name on the application with the OCN name associated with the switch CLLI referenced in the letter. All documentation submitted will be held confidential pursuant to FCC confidentiality rules.125.13 Code Assignment Criteria for Growth 9YY Code Requests Assignment of additional

40、 code(s) (growth codes) shall be made by satisfying the criteria in section 3c on the Part A Form. The information submitted shall demonstrate that all of the numbers assigned to the code holder will exhaust within six months. In the Months To Exhaust calculation and Utilization Level calculations,

41、an SP shall include every 9YY-NXX code assigned to the SP. For additional codes for growth, each code holder shall supply supporting data in section 3c of the Part A which covers: Telephone Number (TNs) Available for Assignment; Growth history for the previous six months Projected demand for the com

42、ing 12 months; and The applicants shall demonstrate that existing numbering resources will exhaust within 6 months. All applicants for growth numbering resources shall achieve a 75% utilization threshold, calculated in accordance with the below calculation. _ 1247 CFR 52.13 (c) (7) 11 The numbering

43、resource utilization threshold shall be calculated by dividing all assigned numbers by the total numbering resources in the applicants inventory and multiplying the result by 100. 6.0 RESPONSIBILITIES OF CODE APPLICANTS AND HOLDERS Entities requesting new 9YY NXX code assignments as well as entities

44、 already assigned 9YY NXX codes shall comply with the following: 6.1 The code applicant may request from the 9YY NXX code administrator information associated with the assignment of NXX codes for 9YY services. This includes information on how to obtain a current copy of the “9YY NXX Code Assignment

45、Guidelines”. 6.2 The code applicant/code holder is responsible for meeting all conditions of these guidelines. 6.3 The application process for 9YY NXX assignments shall include the following: 6.3.1 Apply to the code administrator and complete all required entries on the “9YY NXX Code Forms“ that are

46、 in Attachment A of these guidelines. One form shall be completed per request. No more than 5 codes can be requested per application form. Applicants who choose to submit their Part A and/or Part C via facsimile or mailed copies will be charged a fee. See the NANPA website at for specific details r

47、egarding the associated fee structure. 6.3.2 When requesting growth codes, applicants shall meet the requirements as described in Section 5.13 and conform to the conditions contained therein. On the Part A form, applicants must provide (1) information that provides utilization for the preceding six

48、months and projected monthly utilization for the next twelve months; and (2) the applicants current numbering utilization level. 6.3.3 Provide, if desired, requests for specific and alternative NXX code assignments in order of preference. The administrator will try to satisfy such requests but cannot guarantee specific requests will be satisfied, see Section 7.4.1.1. 6.3.4 When requesting an initial 9YY-NXX code, certify on Part A of the “9YY NXX Code Forms“ that the required regulatory authority authorization has been obtained for which the code is being requested, and