47 CFR Part 52 — Numbering

PART 52—NUMBERING Authority: 47 U.S.C. 151, 152, 153, 154, 155, 201-205, 207-209, 218, 225-227, 227b-1, 251-252, 271, 303, 332, unless otherwise noted. Source: 61 FR 38637, July 25, 1996, unless otherwise noted. Subpart A—Scope and Authority Source: 61 FR 47353, Sept. 6, 1996, unless otherwise noted. § 52.1 Basis and purpose. (a) Basis. et. seq. (b) Purpose. § 52.3 General. The Commission shall have exclusive authority over those portions of the North American Numbering Plan (NANP) that pertain to the United States. The Commission may delegate to the States or other entities any portion of such jurisdiction. § 52.5 Definitions. (a) Incumbent local exchange carrier. (1) On February 8, 1996, provided telephone exchange service in such area; and (2)(i) On February 8, 1996, was deemed to be a member of the exchange carrier Association pursuant to § 69.601(b) of this chapter (47 CFR 69.601(b)); or (ii) Is a person or entity that, on or after February 8, 1996, became a successor or assign of a member described in paragraph (a)(2)(i) of this section. (b) Interconnected Voice over Internet Protocol (VoIP) service provider. (c) North American Numbering Council (d) North American Numbering Plan (e) Service provider. (f) State. (g) State commission. (h) Telecommunications. (i) Telecommunications carrier or carrier. (j) Telecommunications service. [80 FR 66477, Oct. 29, 2015, as amended at 80 FR 1131, Jan. 11, 2016] Subpart B—Administration Source: 61 FR 47353, Sept. 6, 1996, unless otherwise noted. § 52.7 Definitions. As used in this subpart: (a) Area code or numbering plan area (b) Area code relief. (c) Central office (CO) code. (d) Central office (CO) code administrator. (e) North American Numbering Plan Administrator (f) Billing and Collection Agent. (g) Pooling Administrator (PA). (h) Contamination. (i) Donation. (j) Inventory. (1) To a service provider; or (2) To a pooling administrator for the purpose of establishing or maintaining a thousands-block number pool. [61 FR 47353, Sept. 6, 1996, as amended at 62 FR 55180, Oct. 23, 1997; 65 FR 37707, June 16, 2000] § 52.9 General requirements. (a) To ensure that telecommunications numbers are made available on an equitable basis, the administration of telecommunications numbers shall, in addition to the specific requirements set forth in this subpart: (1) Facilitate entry into the telecommunications marketplace by making telecommunications numbering resources available on an efficient, timely basis to telecommunications carriers; (2) Not unduly favor or disfavor any particular telecommunications industry segment or group of telecommunications consumers; and (3) Not unduly favor one telecommunications technology over another. (b) If the Commission delegates any telecommunications numbering administration functions to any State or other entity pursuant to 47 U.S.C. 251(e)(1), such State or entity shall perform these functions in a manner consistent with this part. § 52.11 North American Numbering Council. The duties of the North American Numbering Council (NANC), may include, but are not limited to: (a) Advising the Commission on policy matters relating to the administration of the NANP in the United States; (b) Making recommendations, reached through consensus, that foster efficient and impartial number administration; (c) Initially resolving disputes, through consensus, that foster efficient and impartial number administration in the United States by adopting and utilizing dispute resolution procedures that provide disputants, regulators, and the public notice of the matters at issue, a reasonable opportunity to make oral and written presentations, a reasoned recommended solution, and a written report summarizing the recommendation and the reasons therefore; (d) [Reserved] (e) Recommending to the Commission an appropriate mechanism for recovering the costs of NANP administration in the United States, consistent with § 52.17; (f) Carrying out the duties described in § 52.25; and (g) Carrying out this part as directed by the Commission; (h) Monitoring the performance of the NANPA and the B&C Agent on at least an annual basis; and (i) Implementing, at the direction of the Commission, any action necessary to correct identified problems with the performance of the NANPA and the B&C Agent, as deemed necessary. [61 FR 47353, Sept. 6, 1996, as amended at 62 FR 55180, Oct. 23, 1997; 71 FR 65750, Nov. 9, 2006] § 52.12 North American Numbering Plan Administrator and B&C Agent. The North American Numbering Plan Administrator (“NANPA”) and the associated “B&C Agent” will conduct their respective operations in accordance with this section. The NANPA and the B&C Agent will conduct their respective operations with oversight from the Federal Communications Commission (the “Commission”) and with recommendations from the North American Numbering Council (“NANC”). (a)(1) Neutrality. (i) The NANPA and B&C Agent may not be an affiliate of any telecommunications service provider(s) as defined in the Telecommunications Act of 1996, or an affiliate of any interconnected VoIP provider as that term is defined in § 52.21(h). “Affiliate” is a person who controls, is controlled by, or is under the direct or indirect common control with another person. A person shall be deemed to control another if such person possesses, directly or indirectly— (A) An equity interest by stock, partnership (general or limited) interest, joint venture participation, or member interest in the other person ten (10%) percent or more of the total outstanding equity interests in the other person, or (B) The power to vote ten (10%) percent or more of the securities (by stock, partnership (general or limited) interest, joint venture participation, or member interest) having ordinary voting power for the election of directors, general partner, or management of such other person, or (C) The power to direct or cause the direction of the management and policies of such other person, whether through the ownership of or right to vote voting rights attributable to the stock, partnership (general or limited) interest, joint venture participation, or member interest) of such other person, by contract (including but not limited to stockholder agreement, partnership (general or limited) agreement, joint venture agreement, or operating agreement), or otherwise; (ii) The NANPA and B&C Agent, and any affiliate thereof, may not issue a majority of its debt to, nor may it derive a majority of its revenues from, any telecommunications service provider. “Majority” shall mean greater than 50 percent, and “debt” shall mean stocks, bonds, securities, notes, loans or any other instrument of indebtedness; and (iii) Notwithstanding the neutrality criteria set forth in paragraphs (a)(1) (i) and (ii) of this section, the NANPA and B&C Agent may be determined to be or not to be subject to undue influence by parties with a vested interest in the outcome of numbering administration and activities. NANC may conduct an evaluation to determine whether the NANPA and B&C Agent meet the undue influence criterion. (2) Any subcontractor that performs— (i) NANP administration and central office code administration, or (ii) Billing and Collection functions, for the NANPA or for the B&C Agent must also meet the neutrality criteria described in paragraph (a)(1). (b) Term of administration. (c) Changes to regulations, rules, guidelines or directives. (d) Performance review process. (e) Termination. (f) Required and optional enterprise services. (1) Required Enterprise Services. (2) Optional Enterprise Services. (3) Annual report. [63 FR 55180, Oct. 23, 1997, as amended at 73 FR 9481, Feb. 21, 2008] § 52.13 North American Numbering Plan Administrator. (a) The North American Numbering Plan Administrator (NANPA) shall be an independent and impartial non-government entity. (b) The NANPA shall administer the numbering resources identified in paragraph (d) of this section. It shall assign and administer NANP resources in an efficient, effective, fair, unbiased, and non-discriminatory manner consistent with industry-developed guidelines and Commission regulations. It shall support the Commission's efforts to accommodate current and future numbering needs. It shall perform additional functions, including but not limited to: (1) Ensuring the efficient and effective administration and assignment of numbering resources by performing day-to-day number resource assignment and administrative activities; (2) Planning for the long-term need for NANP resources to ensure the continued viability of the NANP by implementing a plan for number resource administration that uses effective forecasting and management skills in order to make the industry aware of the availability of numbering resources and to meet the current and future needs of the industry; (3) Complying with guidelines of the North American Industry Numbering Committee (INC) or its successor, related industry documentation, Commission regulations and orders, and the guidelines of other appropriate policy-making authorities; (4) Providing management supervision for all of the services it provides, including responsibility for achieving performance measures established by the NANC and the INC in industry guidelines; (5) Participating in the NANC annual performance review as described in §§ 52.11 and 52.12; (6) Establishing and maintaining relationships with current governmental and regulatory bodies, and their successors, including the United States Federal Communications Commission, Industry Canada, the Canadian Radio-television and Telecommunications Commission, and other United States, Canadian, and Caribbean numbering authorities and regulatory agencies, and addressing policy directives from these bodies; (7) Cooperating with and actively participating in numbering standards bodies and industry fora, such as INC and, upon request, the Canadian Steering Committee on Numbering (CSCN); (8) Representing the NANP to national and international numbering bodies; (9) Developing and maintaining communications channels with other countries who also participate in the NANP to ensure that numbering needs of all countries served by the NANP are met; (10) Attending United States Study Group A meetings and maintaining a working knowledge of Study Group 2 International Telecommunications Union activities on behalf of the United States telecommunications industry; (11) Reviewing requests for all numbering resources to implement new applications and services and making assignments in accordance with industry-developed resource planning and assignment guidelines; (12) Referring requests for particular numbering resources to the appropriate industry body where guidelines do not exist for those resources; (13) Participating in industry activities to determine whether, when new telecommunications services requiring numbers are proposed, NANP numbers are appropriate and what level of resource is required (e.g., line numbers, central office codes, NPA codes); (14) Maintaining necessary administrative staff to handle the legal, financial, technical, staffing, industry, and regulatory issues relevant to the management of all numbering resources, as well as maintaining the necessary equipment, facilities, and proper billing arrangements associated with day-to-day management of all numbering resources; (15) Managing the NANP in accordance with published guidelines adopted in conjunction with the industry and the appropriate NANP member countries' governing agencies, and referring issues to the appropriate industry body for resolution when they have not been addressed by the industry; (16) Responding to requests from the industry and from regulators for information about the NANP and its administration, as the primary repository for numbering information in the industry; (17) Providing upon request information regarding how to obtain current documents related to NANP administration; (18) Providing assistance to users of numbering resources and suggesting numbering administration options, when possible, that will optimize number resource utilization; (19) Coordinating its numbering resource activities with the Canadian Number Administrator and other NANP member countries' administrators to ensure efficient and effective management of NANP numbering resources; and (20) Determining the final allocation methodology for sharing costs between NANP countries. (c) In performing the functions outlined in paragraph (b) of this section, the NANPA shall: (1) Ensure that the interests of all NANP member countries are considered; (2) Assess fairly requests for assignments of NANP numbering resources and ensure the assignment of numbering resources to appropriate service providers; (3) Develop, operate and maintain the computer hardware, software (database) and mechanized systems required to perform the NANPA and central office (CO) Code Administration functions; (4) Manage projects such as Numbering Plan Area (NPA) relief (area code relief) planning, Numbering Resource Utilization and Forecast (NRUF) data collection, and NPA and NANP exhaust projection; (5) Facilitate NPA relief planning meetings; (6) Participate in appropriate industry activities; (7) Manage proprietary data and competitively sensitive information and maintain the confidentiality thereof; (8) Act as an information resource for the industry concerning all aspects of numbering (i.e., knowledge and experience in numbering resource issues, International Telecommunications Union (ITU) Recommendation E.164, the North American Numbering Plan (NANP), NANP Administration, INC, NANP area country regulatory issues affecting numbering, number resource assignment guidelines, central office code administration, relief planning, international numbering issues, etc.); and (9) Ensure that any action taken with respect to number administration is consistent with this part. (d) The NANPA and, to the extent applicable, the B&C Agent, shall administer numbering resources in an efficient and non-discriminatory manner, in accordance with Commission rules and regulations and the guidelines developed by the INC and other industry groups pertaining to administration and assignment of numbering resources, including, but not limited to: (1) Numbering Plan Area (NPA) codes, (2) Central Office codes for the 809 area, (3) International Inbound NPA 456 NXX codes, (4) (NPA) 500 NXX codes, (5) (NPA) 900 NXX codes, (6) N11 Service codes, (7) 855-XXXX line numbers, (8) 555-XXXX line numbers, (9) Carrier Identification Codes, (10) Vertical Service Codes, (11) ANI Information Integer (II) Digit Pairs, (12) Non Dialable Toll Points, and (13) New numbering resources as may be defined. (e) Relationships with other NANP member countries' administrators and authorities. (f) Transition plan. (g) Transfer of intellectual property. [61 FR 47353, Sept. 6, 1996, as amended at 62 FR 55181, Oct. 23, 1997; 71 FR 65750, Nov. 9, 2006] § 52.15 Central office code administration. (a) Central Office Code Administration shall be performed by the NANPA, or another entity or entities, as designated by the Commission. (b) Duties of the entity or entities performing central office code administration may include, but are not limited to: (1) Processing central office code assignment applications and assigning such codes in a manner that is consistent with this part; (2) Accessing and maintaining central office code assignment databases; (3) Conducting the Numbering Resource Utilization and Forecast (NRUF) data collection; (4) Monitoring the use of central office codes within each area code and forecasting the date by which all central office codes within that area code will be assigned; and (5) Planning for and initiating area code relief, consistent with § 52.19. (c) [Reserved] (d) Central Office (CO) Code Administration functional requirements. (e) [Reserved] (f) Mandatory reporting requirements Number use categories. (i) Administrative numbers (ii) Aging numbers are disconnected numbers that are not available for assignment to another end user or customer for a specified period of time. Numbers previously assigned to residential customers may be aged for no less than 45 days and no more than 90 days. Numbers previously assigned to business customers may be aged for no less than 45 days and no more than 365 days. (iii) Assigned numbers (iv) Available numbers (v) Intermediate numbers (vi) Reserved numbers (2) Reporting carrier. (3) Data collection procedures. (ii) Reporting shall be by separate legal entity and must include company name, company headquarters address, Operating Company Number (OCN), parent company OCN, and the primary type of business in which the reporting carrier is engaged. The term “parent company” refers to the highest related legal entity located within the state for which the reporting carrier is reporting data. (iii) All data shall be filed electronically in a format approved by the Common Carrier Bureau. (4) Forecast data reporting. (ii) In areas where thousands-block number pooling has been implemented: (A) Reporting carriers that are required to participate in thousands-block number pooling shall report forecast data at the thousands-block (NXX-X) level per rate center; (B) Reporting carriers that are not required to participate in thousands-block number pooling shall report forecast data at the central office code (NXX) level per rate center. (iii) In areas where thousands-block number pooling has not been implemented, reporting carriers shall report forecast data at the central office code (NXX) level per NPA. (iv) Reporting carriers shall identify and report separately initial numbering resources and growth numbering resources. (5) Utilization data reporting. assigned, intermediate, reserved, aging, administrative. (ii) Rural telephone companies, as defined in the Communications Act of 1934, as amended, 47 U.S.C. 153(37), that provide telecommunications service in areas where local number portability has not been implemented shall report utilization data at the central office code (NXX) level per rate center in those areas. (iii) All other reporting carriers shall report utilization data at the thousands-block (NXX-X) level per rate center. (6) Reporting frequency. (ii) State commissions may reduce the reporting frequency for NPAs in their states to annual. Reporting carriers operating in such NPAs shall file forecast and utilization reports annually on or before August 1 for the preceding reporting period ending on June 30, commencing August 1, 2000. (iii) A state commission seeking to reduce the reporting frequency pursuant to paragraph (f) (6)(ii) of this section shall notify the Wireline Competition Bureau and the NANPA in writing prior to reducing the reporting frequency. (7) Access to data and confidentiality (8) Reports of Permanently Disconnected Numbers—Reporting carriers must report information regarding NANP numbers in accordance with § 64.1200(l) of this title. (g) Applications for numbering resources General requirements. (2) Initial numbering resources. (3) Commission authorization process. (i) Definition. foreign carrier (ii) Contents of the application for interconnected VoIP provider numbering authorization. (A) The applicant's name, address, and telephone number and contact information for personnel qualified to address issues relating to regulatory requirements, compliance with Commission's rules in this chapter, 911, and law enforcement; (B) An acknowledgment that the authorization granted under this paragraph (g)(3) is subject to compliance with applicable Commission numbering rules in this part; numbering authority delegated to the states, and the state laws, regulations, and registration requirements applicable to businesses operating in each state where the applicant seeks numbering resources; and industry guidelines and practices regarding numbering as applicable to telecommunications carriers; (C) A certification that the applicant will not use the numbers obtained pursuant to an authorization under this paragraph (g)(3) to knowingly transmit, encourage, assist, or facilitate illegal robocalls, illegal spoofing, or fraud, in violation of robocall, spoofing, and deceptive telemarketing obligations under §§ 64.1200, 64.1604, and 64.6300 through 64.6308 of this chapter and 16 CFR 310.3(b); (D) A certification that the applicant has fully complied with all applicable STIR/SHAKEN caller ID authentication and robocall mitigation program requirements and filed a certification in the Robocall Mitigation Database as required by §§ 64.6301 through 64.6305 of this chapter; (E) A certification with accompanying evidence that the applicant complies with its 911 obligations under part 9 of this chapter, and that it complies with the provisions of the Communications Assistance with Law Enforcement Act, 47 U.S.C. 1001 et seq. (F) A certification that the applicant complies with the Access Stimulation rules under § 51.914 of this chapter; (G) An acknowledgment that the applicant must file requests for numbers with the relevant state commission(s) at least 30 days before requesting numbers from the Numbering Administrators; (H) Proof that the applicant is or will be capable of providing service within sixty (60) days of the numbering resources activation date in accordance with paragraph (g)(2) of this section; (I) Proof that the applicant has filed FCC Forms 477 and 499, or a statement explaining why each such form is not yet applicable; (J) A certification that the applicant complies with its applicable Universal Service Fund contribution obligations under part 54, subpart H, of this chapter, its Telecommunications Relay Service contribution obligations under § 64.604(c)(5)(iii) of this chapter, its NANP and local number portability (LNP) administration contribution obligations under §§ 52.17 and 52.32 of this chapter, and its obligations to pay regulatory fees under § 1.1154 of this chapter; (K) A certification that the applicant possesses the financial, managerial, and technical expertise to provide reliable service. This certification must include the name of applicant's key management and technical personnel, such as the Chief Operating Officer and the Chief Technology Officer, or equivalent, and state that neither the applicant nor any of the identified personnel are being or have been investigated by the Commission, law enforcement, or any regulatory agency for failure to comply with any law, rule, or order, including the Commission's rules in this chapter applicable to unlawful robocalls or unlawful spoofing; (L) The same information, disclosures, and certifications required by § 63.18(h) and (i) of this chapter; (M) A certification pursuant to §§ 1.2001 and 1.2002 of this chapter that no party to the application is subject to a denial of Federal benefits pursuant to section 5301 of the Anti-Drug Abuse Act of 1988, see (N) A declaration under penalty of perjury pursuant to § 1.16 of this chapter that all statements in the application and any appendices are true and accurate. This declaration shall be executed by an officer or other authorized representative of the applicant. (iii) Filing procedure. (iv) Public notice and review period for streamlined pleading cycle. (v) Non-streamlined processing of applications. (A) An applicant fails to respond promptly to Commission inquiries; (B) An application is associated with a non-routine request for waiver of the Commission's rules in this chapter; (C) An application would, on its face, violate a Commission rule in this chapter or the Communications Act; (D) Timely filed comments on the application raise public interest concerns that require further Commission review; or (E) The Bureau determines that the application requires further analysis to determine whether granting the application serves the public interest. (vi) Additional information. (vii) Rejection of applications. (A) The applicant cannot satisfy the qualification requirements for a Commission authorization under this paragraph (g)(3); (B) The applicant has made a false statement or certification to the Commission; (C) The applicant has engaged in behavior contrary to the public interest; or (D) Granting the application would not serve the public interest. (viii) Authorization suspension. (A) After either Bureau determines that the authorization holder acted willfully; or public health, interest, or safety requires an immediate suspension; or (B) After giving the authorization holder notice and an opportunity to demonstrate compliance with the Commission's rules in this chapter. (ix) Authorization revocation. (A) The authorization holder has failed to comply with the Commission's numbering rules in this part. (B) The authorization holder no longer meets the requirements for a Commission authorization under this paragraph (g)(3); (C) The authorization holder, or officer or authorized representative of the authorization holder, has made a false statement or certification to the Commission; or (D) Revoking and/or terminating the authorization is in the public interest. (x) Conditions applicable to all interconnected VoIP provider numbering authorizations. (A) Maintain the accuracy of all contact information, certifications, and ownership or affiliation information in its application. If any contact information, certification, or affiliation information submitted in an application pursuant to this section, is no longer accurate, the provider must file a correction with the Commission and each applicable state within thirty (30) days of the change of contact information, certification, or affiliation information. Regarding ownership information, if the holders of equity and/or voting interests in the provider change such that a provider that previously did not have reportable ownership or control information under paragraph (g)(3)(ii)(L) of this section now has reportable ownership or control information, or there is a change to the reportable ownership or control information the provider previously reported under paragraph (g)(3)(ii)(L), the provider must file a correction with the Commission and each applicable state within thirty (30) days of the change to its ownership or control information. The Commission may use the updated contact information, certifications, or ownership or affiliation information to determine whether a change in authorization status is warranted; (B) Comply with the applicable Commission numbering rules in this part; numbering authority delegated to the states; and industry guidelines and practices regarding numbering as applicable to telecommunications carriers; (C) File requests for numbers with the relevant state commission(s) at least thirty (30) days before requesting numbers from the Numbering Administrators; (D) Provide accurate regulatory and numbering contact information to each state commission when requesting numbers in that state; and (E) File updated certifications and ownership and control disclosures under paragraphs (g)(3)(ii)(B) through (F), (I), (K), (L), and (N) of this section if the authorization obtained under this section was granted before August 8, 2024. (F) Paragraph (g)(3)(x)(E) of this section contains a new information-collection requirement. Compliance with paragraph (g)(3)(x)(E) will not be required until this paragraph (g)(3)(x)(F) is removed or contains a compliance date. (4) Growth numbering resources. (A) A Months-to-Exhaust Worksheet that provides utilization by rate center for the preceding six months and projected monthly utilization for the next twelve (12) months; and (B) The applicant's current numbering resource utilization level for the rate center in which it is seeking growth numbering resources. (ii) The numbering resource utilization level shall be calculated by dividing all assigned numbers (iii) All service providers shall maintain no more than a six-month inventory of telephone numbers in each rate center or service area in which it provides telecommunications service. (iv) The NANPA shall withhold numbering resources from any U.S. carrier that fails to comply with the reporting and numbering resource application requirements established in this part. The NANPA shall not issue numbering resources to a carrier without an OCN. The NANPA must notify the carrier in writing of its decision to withhold numbering resources within ten (10) days of receiving a request for numbering resources. The carrier may challenge the NANPA's decision to the appropriate state regulatory commission. The state commission may affirm or overturn the NANPA's decision to withhold numbering resources from the carrier based on its determination of compliance with the reporting and numbering resource application requirements herein. (5) Non-compliance. (6) State access to applications. (h) National utilization threshold. (i) Reclamation of numbering resources. (2) State commissions may investigate and determine whether service providers have activated their numbering resources and may request proof from all service providers that numbering resources have been activated and assignment of telephone numbers has commenced. (3) Service providers may be required to reduce contamination levels to facilitate reclamation and/or pooling. (4) State commissions shall provide service providers an opportunity to explain the circumstances causing the delay in activating and commencing assignment of their numbering resources prior to initiating reclamation. (5) The NANPA and the Pooling Administrator shall abide by the state commission's determination to reclaim numbering resources if the state commission is satisfied that the service provider has not activated and commenced assignment to end users of their numbering resources within six months of receipt. (6) The NANPA and Pooling Administrator shall initiate reclamation within sixty days of expiration of the service provider's applicable activation deadline. (7) If a state commission declines to exercise the authority delegated to it in this paragraph, the entity or entities designated by the Commission to serve as the NANPA shall exercise this authority with respect to NXX codes and the Pooling Administrator shall exercise this authority with respect to thousands-blocks. The NANPA and the Pooling Administrator shall consult with the Wireline Competition Bureau prior to exercising the authority delegated to it in this provision. (j) Sequential number assignment. (2) A service provider that opens an uncontaminated thousands-block prior to assigning all available telephone numbers within an opened thousands-block should be prepared to demonstrate to the state commission: (i) A genuine request from a customer detailing the specific need for telephone numbers; and (ii) The service provider's inability to meet the specific customer request for telephone numbers from the available numbers within the service provider's opened thousands-blocks. (3) Upon a finding by a state commission that a service provider inappropriately assigned telephone numbers from an uncontaminated thousands-block, the NANPA or the Pooling Administrator shall suspend assignment or allocation of any additional numbering resources to that service provider in the applicable NPA until the service provider demonstrates that it does not have sufficient numbering resources to meet a specific customer request. (k) Numbering audits. (2) The Enforcement Bureau will oversee the conduct and scope of all numbering audits conducted under the Commission's jurisdiction, and determine the audit procedures necessary to perform the audit. Numbering audits performed by independent auditors pursuant to this section shall be conducted in accordance with generally accepted auditing standards and the American Institute of Certified Public Accountants' standards for compliance attestation engagements, as supplemented by the guidance and direction of the Chief of the Enforcement Bureau. (3) Requests for “for cause” audits shall be forwarded to the Chief of the Enforcement Bureau, with a copy to the Chief of the Common Carrier Bureau. Requests must state the reason for which a “for cause” audit is being requested and include documentation of the alleged anomaly, inconsistency, or violation of the Commission rules or orders or applicable industry guidelines. The Chief of the Enforcement Bureau will provide carriers up to 30 days to provide a written response to a request for a “for cause” audit. [61 FR 47353, Sept. 6, 1996, as amended at 62 FR 55182, Oct. 23, 1997; 65 FR 37707, June 16, 2000; 66 FR 9531, Feb. 8, 2001; 67 FR 6434, Feb. 12, 2002; 67 FR 13226, Mar. 21, 2002; 68 FR 25843, May 14, 2003; 71 FR 65750, Nov. 9, 2006; 80 FR 66479, Oct. 29, 2015; 84 FR 11232, Mar. 26, 2019; 88 FR 80636, Nov. 20, 2023; 89 FR 80637, Aug. 8, 2024; 91 FR 7159, Feb. 17, 2026] § 52.16 Billing and Collection Agent. The B&C Agent shall: (a) Calculate, assess, bill and collect payments for all numbering administration functions and distribute funds to the NANPA, or other agent designated by the Common Carrier Bureau that performs functions related to numbering administration, on a monthly basis; (b) Distribute to carriers the “Telecommunications Reporting Worksheet,” described in § 52.17(b). (c) Keep confidential all data obtained from carriers and not disclose such data in company-specific form unless authorized by the Commission. Subject to any restrictions imposed by the Chief of the Wireline Competition Bureau, the B & C Agent may share data obtained from carriers with the administrators of the universal service support mechanism (See 47 CFR 54.701 of this chapter), the TRS Fund (See 47 CFR 64.604(c)(4)(iii)(H) of this chapter), and the local number portability cost recovery (See 47 CFR 52.32). The B & C Agent shall keep confidential all data obtained from other administrators. The B & C Agent shall use such data, from carriers or administrators, only for calculating, collecting and verifying payments. The Commission shall have access to all data reported to the Administrator. Contributors may make requests for Commission nondisclosure of company-specific revenue information under § 0.459 of this chapter by so indicating on the Telecommunications Reporting Worksheet at the time that the subject data are submitted. The Commission shall make all decisions regarding nondisclosure of company-specific information. (d) Develop procedures to monitor industry compliance with reporting requirements and propose specific procedures to address reporting failures and late payments; (e) File annual reports with the appropriate regulatory authorities of the NANP member countries as requested; and (f) Obtain an audit from an independent auditor after the first year of operations and annually thereafter, which shall evaluate the validity of calculated payments. The B&C Agent shall submit the audit report to the Commission for appropriate review and action. [62 FR 55183, Oct. 23, 1997, as amended at 64 FR 41330, July 30, 1999; 66 FR 9532, Feb. 8, 2001; 67 FR 13226, Mar. 21, 2002; 73 FR 9481, Feb. 21, 2008; 80 FR 66479, Oct. 29, 2015] § 52.17 Costs of number administration. All telecommunications carriers in the United States shall contribute on a competitively neutral basis to meet the costs of establishing numbering administration. (a) Contributions to support numbering administration shall be the product of the contributors' end-user telecommunications revenues for the prior calendar year and a contribution factor determined annually by the Chief of the Common Carrier Bureau; such contributions to be no less than twenty-five dollars ($25). The contribution factor shall be based on the ratio of expected number administration expenses to end-user telecommunications revenues. Carriers that have no end-user telecommunications revenues shall contribute twenty-five dollars ($25). In the event that contributions exceed or are inadequate to cover administrative costs, the contribution factor for the following year shall be adjusted by an appropriate amount. (b) All telecommunications carriers in the United States shall complete and submit a “Telecommunications Reporting Worksheet” (as published by the Commission in the Federal Register [64 FR 41331, July 30, 1999, as amended at 73 FR 9481, Feb. 21, 2008; 80 FR 66479, Oct. 29, 2015] § 52.19 Area code relief. (a) State commissions may resolve matters involving the introduction of new area codes within their states. Such matters may include, but are not limited to: Directing whether area code relief will take the form of a geographic split, an overlay area code, or a boundary realignment; establishing new area code boundaries; establishing necessary dates for the implementation of area code relief plans; and directing public education efforts regarding area code changes. (b) State commissions may perform any or all functions related to initiation and development of area code relief plans, so long as they act consistently with the guidelines enumerated in this part, and subject to paragraph (b)(2) of this section. For the purposes of this paragraph, initiation and development of area code relief planning encompasses all functions related to the implementation of new area codes that were performed by central office code administrators prior to February 8, 1996. Such functions may include: declaring that the area code relief planning process should begin; convening and conducting meetings to which the telecommunications industry and the public are invited on area code relief for a particular area code; and developing the details of a proposed area code relief plan or plans. (1) The entity or entities designated by the Commission to serve as central office code administrator(s) shall initiate and develop area code relief plans for each area code in each state that has not notified such entity or entities, pursuant to paragraph (b)(2) of this section, that the state will handle such functions. (2) Pursuant to paragraph (b)(1) of this section, a state commission must notify the entity or entities designated by the Commission to serve as central office code administrator(s) for its state that such state commission intends to perform matters related to initiation and development of area code relief planning efforts in its state. Notification shall be written and shall include a description of the specific functions the state commission intends to perform. Where the NANP Administrator serves as the central office code administrator, such notification must be made within 120 days of the selection of the NANP Administrator. (c) New area codes may be introduced through the use of: (1) A geographic area code split, which occurs when the geographic area served by an area code in which there are few or no central office codes left for assignment is split into two or more geographic parts; (2) An area code boundary realignment, which occurs when the boundary lines between two adjacent area codes are shifted to allow the transfer of some central office codes from an area code for which central office codes remain unassigned to an area code for which few or no central office codes are left for assignment; or (3) An all services area code overlay, which occurs when a new area code is introduced to serve the same geographic area as one or more existing area code(s), subject to the following conditions: (i) No all services area code overlay may be implemented unless all numbering resources in the new overlay area code are assigned to those entities requesting assignment on a first-come, first-serve basis, regardless of the identity of, technology used by, or type of service provided by that entity, except to the extent that a technology- or service-specific overlay is authorized by the Commission. No group of telecommunications carriers shall be excluded from assignment of numbering resources in the existing area code, or be assigned such resources only from the all services overlay area code, based solely on that group's provision of a specific type of telecommunications service or use of a particular technology; and (ii) No area code overlay may be implemented unless there exists, at the time of implementation, mandatory ten-digit dialing for every telephone call within and between all area codes in the geographic area covered by the overlay area code. (4) A technology-specific or service-specific overlay, which occurs when a new area code is introduced to serve the same geographic area as one or more existing area code(s) and numbering resources in the new area code overlay are assigned to a specific technology(ies) or service(s). State commissions may not implement a technology-specific or service-specific overlay without express authority from the Commission. [61 FR 47353, Sept. 6, 1996, as amended at 64 FR 63617, Nov. 16, 1998; 64 FR 62984, Nov. 18, 1999; 67 FR 6434, Feb. 12, 2002] Subpart C—Number Portability Source: 61 FR 38637, July 25, 1996, unless otherwise noted. Redesignated at 61 FR 47353, Sept. 6, 1996. § 52.20 Thousands-block number pooling. (a) Definition. (b) General requirements. (c) Donation of thousands-blocks. (2) All service providers required to participate in thousands-block number pooling shall be allowed to retain at least one thousands-block per rate center, even if the thousands-block is ten percent or less contaminated, as an initial block or footprint block. (d) Thousands-Block Pooling Administrator. (2) The Pooling Administrator shall maintain no more than a six-month inventory of telephone numbers in each thousands-block number pool. [65 FR 37709, June 16, 2000, as amended at 66 FR 9532, Feb. 8, 2001; 68 FR 43009, July 21, 2003] § 52.21 Definitions. As used in this subpart: (a) The term 100 largest MSAs (b) The term broadband PCS (c) The term cellular service (d) The term covered CMRS (e) The term database method (f) The term downstream database (g) The term incumbent wide area SMR licensee (h) The term IP Relay provider (i) The term local exchange carrier (j) The term local number portability administrator (LNPA) (k) The term location portability (l) The term long-term database method (m) The term number portability (n) The term regional database (o) The term Registered Internet-based TRS User (p) The term service control point (SCP) (q) The term service management system (SMS) (1) Interconnects to an SCP and sends to that SCP the information and call processing instructions needed for a network switch to process and complete a telephone call; and (2) Provides telecommunications carriers with the capability of entering and storing data regarding the processing and completing of a telephone call. (r) The term service portability (s) The term service provider portability (t) The term transitional number portability measure (u) The term VRS provider (v) The term 2009 LNP Porting Intervals Order [61 FR 38637, July 25, 1996. Redesignated at 61 FR 47353, Sept. 6, 1996, as amended at 61 FR 47355, Sept. 6, 1996; 63 FR 68203, Dec. 10, 1998; 67 FR 6435, Feb. 12, 2002; 68 FR 43009, July 21, 2003; 73 FR 9481, Feb. 21, 2008; 73 FR 41293, July 18, 2008; 74 FR 31638, July 2, 2009; 80 FR 66479, Oct. 29, 2015] § 52.23 Deployment of long-term database methods for number portability by LECs. (a) Subject to paragraphs (b) and (c) of this section, all local exchange carriers (LECs) must provide number portability in compliance with the following performance criteria: (1) Supports network services, features, and capabilities existing at the time number portability is implemented, including but not limited to emergency services, CLASS features, operator and directory assistance services, and intercept capabilities; (2) Efficiently uses numbering resources; (3) Does not require end users to change their telecommunications numbers; (4) Does not result in unreasonable degradation in service quality or network reliability when implemented; (5) Does not result in any degradation in service quality or network reliability when customers switch carriers; (6) Does not result in a carrier having a proprietary interest; (7) Is able to migrate to location and service portability; and (8) Has no significant adverse impact outside the areas where number portability is deployed. (b)(1) All LECs must provide a long-term database method for number portability in the 100 largest Metropolitan Statistical Areas (MSAs), as defined in § 52.21(k), in switches for which another carrier has made a specific request for the provision of number portability, subject to paragraph (b)(2) of this section. (2) Any procedure to identify and request switches for deployment of number portability must comply with the following criteria: (i) Any wireline carrier that is certified (or has applied for certification) to provide local exchange service in a state, or any licensed CMRS provider, must be permitted to make a request for deployment of number portability in that state; (ii) Carriers must submit requests for deployment at least nine months before the deployment deadline for the MSA; (iii) A LEC must make available upon request to any interested parties a list of its switches for which number portability has been requested and a list of its switches for which number portability has not been requested; and (iv) After the deadline for deployment of number portability in an MSA in the 100 largest MSAs, according to the deployment schedule set forth in the appendix to this part, a LEC must deploy number portability in that MSA in additional switches upon request within the following time frames: (A) For remote switches supported by a host switch equipped for portability (“Equipped Remote Switches”), within 30 days; (B) For switches that require software but not hardware changes to provide portability (“Hardware Capable Switches”), within 60 days; (C) For switches that require hardware changes to provide portability (“Capable Switches Requiring Hardware”), within 180 days; and (D) For switches not capable of portability that must be replaced (“Non-Capable Switches”), within 180 days. (c) Beginning January 1, 1999, all LECs must make a long-term database method for number portability available within six months after a specific request by another telecommunications carrier in areas in which that telecommunications carrier is operating or plans to operate. (d) The Chief, Common Carrier Bureau, may waive or stay any of the dates in the implementation schedule, as the Chief determines is necessary to ensure the efficient development of number portability, for a period not to exceed 9 months ( i.e. (e) In the event a LEC is unable to meet the Commission's deadlines for implementing a long-term database method for number portability, it may file with the Commission at least 60 days in advance of the deadline a petition to extend the time by which implementation in its network will be completed. A LEC seeking such relief must demonstrate through substantial, credible evidence the basis for its contention that it is unable to comply with the deployment schedule set forth in the appendix to this part 52. Such requests must set forth: (1) The facts that demonstrate why the carrier is unable to meet the Commission's deployment schedule; (2) A detailed explanation of the activities that the carrier has undertaken to meet the implementation schedule prior to requesting an extension of time; (3) An identification of the particular switches for which the extension is requested; (4) The time within which the carrier will complete deployment in the affected switches; and (5) A proposed schedule with milestones for meeting the deployment date. (f) The Chief, Wireline Competition Bureau, shall monitor the progress of local exchange carriers implementing number portability, and may direct such carriers to take any actions necessary to ensure compliance with the deployment schedule set forth in the appendix to this part 52. (g) Carriers that are members of the Illinois Local Number Portability Workshop must conduct a field test of any technically feasible long-term database method for number portability in the Chicago, Illinois, area. The carriers participating in the test must jointly file with the Common Carrier Bureau a report of their findings within 30 days following completion of the test. The Chief, Common Carrier Bureau, shall monitor developments during the field test, and may adjust the field test completion deadline as necessary. (h)(1) Porting from a wireline carrier to a wireless carrier is required where the requesting wireless carrier's “coverage area,” as defined in paragraph (h)(2) of this section, overlaps the geographic location in which the customer's wireline number is provisioned, provided that the porting-in carrier maintains the number's original rate center designation following the port. (2) The wireless “coverage area” is defined as the area in which wireless service can be received from the wireless carrier. [61 FR 38637, July 25, 1996, as amended at 62 FR 18294, Apr. 15, 1997; 67 FR 13226, Mar. 21, 2002; 68 FR 43009, July 21, 2003; 73 FR 9481, Feb. 21, 2008] § 52.25 Database architecture and administration. (a) The North American Numbering Council (NANC) shall direct establishment of a nationwide system of regional SMS databases for the provision of long-term database methods for number portability. (b) All telecommunications carriers shall have equal and open access to the regional databases. (c) The NANC shall select a local number portability administrator(s) (LNPA(s)) to administer the regional databases within seven months of the initial meeting of the NANC. (d) The NANC shall determine whether one or multiple administrator(s) should be selected, whether the LNPA(s) can be the same entity selected to be the North American Numbering Plan Administrator, how the LNPA(s) should be selected, the specific duties of the LNPA(s), the geographic coverage of the regional databases, the technical interoperability and operational standards, the user interface between telecommunications carriers and the LNPA(s), the network interface between the SMS and the downstream databases, and the technical specifications for the regional databases. (e) Once the NANC has selected the LNPA(s) and determined the locations of the regional databases, it must report its decisions to the Commission. (f) The information contained in the regional databases shall be limited to the information necessary to route telephone calls to the appropriate telecommunications carriers. The NANC shall determine what specific information is necessary. (g) Any state may opt out of its designated regional database and implement a state-specific database. A state must notify the Wireline Competition Bureau and NANC that it plans to implement a state-specific database within 60 days from the release date of the Public Notice issued by the Chief, Wireline Competition Bureau, identifying the administrator selected by the NANC and the proposed locations of the regional databases. Carriers may challenge a state's decision to opt out of the regional database system by filing a petition with the Commission. (h) Individual state databases must meet the national requirements and operational standards recommended by the NANC and adopted by the Commission. In addition, such state databases must be technically compatible with the regional system of databases and must not interfere with the scheduled implementation of the regional databases. (i) Individual carriers may download information necessary to provide number portability from the regional databases into their own downstream databases. Individual carriers may mix information needed to provide other services or functions with the information downloaded from the regional databases at their own downstream databases. Carriers may not withhold any information necessary to provide number portability from the regional databases on the grounds that such data has been combined with other information in its downstream database. [61 FR 38637, July 25, 1996. Redesignated at 61 FR 47353, Sept. 6, 1996, as amended at 67 FR 13226, Mar. 21, 2002] § 52.26 NANC Recommendations on Local Number Portability Administration. (a) Local number portability administration shall comply with the recommendations of the North American Numbering Council (NANC) as set forth in the report to the Commission prepared by the NANC's Local Number Portability Administration Selection Working Group, dated April 25, 1997 ( Working Group Report Except that: Appendix D Appendix E: Working Group Report not (b) In addition to the requirements set forth in the Working Group Report (1) Each designated N-1 carrier (as described in the Working Group Report (2) If a telecommunictions carrier transmits a telephone call to a local exchange carrier's switch that contains any ported numbers, and the telecommunications carrier has failed to perform a database query to determine if the telephone number has been ported to another local exchange carrier, the local exchange carrier may block the unqueried call only if performing the database query is likely to impair network reliability; (3) The regional limited liability companies (LLCs), already established by telecommunications carriers in each of the original Bell Operating Company regions, shall manage and oversee the local number portability administrators, subject to review by the NANC, but only on an interim basis, until the conclusion of a rulemaking to examine the issue of local number portability administrator oversight and management and the question of whether the LLCs should continue to act in this capacity; and (4) The NANC shall provide ongoing oversight of number portability administration, including oversight of the regional LLCs, subject to Commission review. Parties shall attempt to resolve issues regarding number portability deployment among themselves and, if necessary, under the auspices of the NANC. If any party objects to the NANC's proposed resolution, the NANC shall issue a written report summarizing the positions of the parties and the basis for the recommendation adopted by the NANC. The NANC Chair shall submit its proposed resolution of the dispuited issue to the Chief of the Wireline Competition Bureau as a recommendation for Commission review. The Chief of the Wireline Competition Bureau will place the NANC's proposed resolution on public notice. Recommendations adopted by the NANC and forwarded to the Bureau may be implemented by the parties pending review of the recommendation. Within 90 days of the conclusion of the comment cycle, the Chief of the Wireline Competition Bureau may issue an order adopting, modifying, or rejecting the recommendation. If the Chief does not act within 90 days of the conclusion of the comment cycle, the recommendation will be deemed to have been adopted by the Bureau. (c) The NANC Working Group Report is incorporated by reference into this section with the approval of the Director of the Federal Register in accordance with 5 U.S.C. 552(a) and 1 CFR part 51. This incorporation by reference (IBR) material is available for public inspection at the FCC and the National Archives and Records Administration (NARA). Contact the FCC through the Federal Communications Commission's Reference Information Center, phone: (202) 418-0270. For information on the availability of this material at NARA, visit www.archives.gov/federal-register/cfr/ibr-locations.html [email protected] https://docs.fcc.gov/public/attachments/DOC-341177A1.pdf [62 FR 48786, Sept. 17, 1997, as amended at 65 FR 58466, Sept. 29, 2000; 67 FR 13226, Mar. 21, 2002; 69 FR 18803, Apr. 9, 2004; 74 FR 31638, July 2, 2009; 75 FR 35315, June 22, 2010; 83 FR 42052, Aug. 20, 2018; 85 FR 64407, Oct. 13, 2020; 88 FR 21442, Apr. 10, 2023] § 52.31 Deployment of long-term database methods for number portability by CMRS providers. (a) By November 24, 2003, all covered CMRS providers must provide a long-term database method for number portability, including the ability to support roaming, in the 100 largest MSAs, as defined in § 52.21(k), in compliance with the performance criteria set forth in section 52.23(a) of this part, in switches for which another carrier has made a specific request for the provision of number portability, subject to paragraph (a)(1) of this section. A licensee may have more than one CMRS system, but only the systems that satisfy the definition of covered CMRS are required to provide number portability. (1) Any procedure to identify and request switches for development of number portability must comply with the following criteria: (i) Any wireline carrier that is certified (or has applied for certification) to provide local exchange service in a state, or any licensed CMRS provider, must be permitted to make a request for deployment of number portability in that state; (ii) Carries requesting deployment in the 100 largest MSAs by November 24, 2003 must submit requests by February 24, 2003. (iii) A covered CMRS provider must make available upon request to any interested parties a list of its switches for which number portability has been requested and a list of its switches for which number portability has not been requested; (iv) After November 24, 2003, a covered CMRS provider must deploy number portability in additional switches serving the 100 largest MSAs upon request within the following time frames: (A) For remote switches supported by a host switch equipped for portability (“Equipped Remote Switches”), within 30 days; (B) For switches that require software but not hardware changes to provide portability (“Hardware Capable Switches”), within 60 days; (C) For switches that require hardware changes to provide portability (“Capable Switches Requiring Hardware”), within 180 days; and (D) For switches not capable of portability that must be replaced (“Non-Capable Switches”), within 180 days. (v) Carriers must be able to request deployment in any wireless switch that serves any area within the MSA, even if the wireless switch is outside that MSA, or outside any of the MSAs identified in the Appendix to this part. (2) By November 24, 2002, all covered CMRS providers must be able to support roaming nationwide. (b) By December 31, 1998, all covered CMRS providers must have the capability to obtain routing information, either by querying the appropriate database themselves or by making arrangements with other carriers that are capable of performing database queries, so that they can deliver calls from their networks to any party that has retained its number after switching from one telecommunications carrier to another. (c) [Reserved] (d) In the event a carrier subject to paragraphs (a) and (b) of this section is unable to meet the Commission's deadlines for implementing a long-term number portability method, it may file with the Commission at least 60 days in advance of the deadline a petition to extend the time by which implementation in its network will be completed. A carrier seeking such relief must demonstrate through substantial, credible evidence the basis for its contention that it is unable to comply with paragraphs (a) and (b) of this section. Such requests must set forth: (1) The facts that demonstrate why the carrier is unable to meet our deployment schedule; (2) A detailed explanation of the activities that the carrier has undertaken to meet the implementation schedule prior to requesting an extension of time; (3) An identification of the particular switches for which the extension is requested; (4) The time within which the carrier will complete deployment in the affected switches; and (5) A proposed schedule with milestones for meeting the deployment date. (e) The Chief, Wireless Telecommunications Bureau, may establish reporting requirements in order to monitor the progress of covered CMRS providers implementing number portability, and may direct such carriers to take any actions necessary to ensure compliance with this deployment schedule. [61 FR 38637, July 25, 1996, as amended at 62 FR 18295, Apr. 15, 1997; 63 FR 68204, Dec. 10, 1998; 64 FR 22563, Apr. 27, 1999; 68 FR 43009, July 21, 2003; 71 FR 65750, Nov. 9, 2006] § 52.32 Allocation of the shared costs of long-term number portability. (a) The local number portability administrator, as defined in § 52.21(h), of each regional database, as defined in § 52.21(1), shall recover the shared costs of long-term number portability attributable to that regional database from all telecommunications carriers providing telecommunications service in areas that regional database serves. Pursuant to its duties under § 52.26, the local number portability administrator shall collect sufficient revenues to fund the operation of the regional database by: (1) Assessing a $100 yearly contribution on each telecommunications carrier identified in paragraph (a) introductory text that has no intrastate, interstate, or international end-user telecommunications revenue derived from providing telecommunications service in the areas that regional database serves, and (2) Assessing on each of the other telecommunications carriers providing telecommunications service in areas that regional database serves, a charge that recovers the remaining shared costs of long-term number portability attributable to that regional database in proportion to the ratio of: (i) The sum of the intrastate, interstate, and international end-user telecommunications revenues that such telecommunications carrier derives from providing telecommunications service in the areas that regional database serves, ii) to the sum of the intrastate, interstate, and international end-user telecommunications revenues that all telecommunications carriers derive from providing telecommunications service in the areas that regional database serves. (b) All telecommunications carriers providing service in the United States shall complete and submit a “Telecommunications Reporting Worksheet” (as published by the Commission in the Federal Register (c) Local number portability administrators shall keep all data obtained from contributors confidential and shall not disclose such data in company-specific form unless directed to do so by the Commission. Subject to any restrictions imposed by the Chief of the Wireline Competition Bureau, the local number portability administrators may share data obtained from carriers with the administrators of the universal service support mechanism (See 47 CFR 54.701 of this chapter), the TRS Fund (See 47 CFR 64.604(c)(4)(iii)(H) of this chapter), and the North American Numbering Plan cost recovery (See 47 CFR 52.16). The local number portability administrators shall keep confidential all data obtained from other administrators. The administrators shall use such data, from carriers or administrators, only for purposes of administering local number portability. The Commission shall have access to all data reported to the Administrator. Contributors may make requests for Commission nondisclosure of company-specific revenue information under § 0.459 of this chapter by so indicating on the Telecommunications Reporting Worksheet at the time that the subject data are submitted. The Commission shall make all decisions regarding nondisclosure of company-specific information. (d) Once a telecommunications carrier has been allocated, pursuant to paragraph (a)(1) or (a)(2) of this section, its portion of the shared costs of long-term number portability attributable to a regional database, the carrier shall treat that portion as a carrier-specific cost directly related to providing number portability. [63 FR 35160, June 29, 1998, as amended at 64 FR 41331, July 30, 1999; 67 FR 13226, Mar. 21, 2002; 73 FR 9481, Feb. 21, 2008; 80 FR 66479, Oct. 29, 2015] § 52.33 Recovery of carrier-specific costs directly related to providing long-term number portability. (a) Incumbent local exchange carriers may recover their carrier-specific costs directly related to providing long-term number portability by establishing in tariffs filed with the Federal Communications Commission a monthly number-portability charge, as specified in paragraph (a)(1) of this section, a number portability query-service charge, as specified in paragraph (a)(2) of this section, and a monthly number-portability query/administration charge, as specified in paragraph (a)(3) of this section. (1) The monthly number-portability charge may take effect no earlier than February 1, 1999, on a date the incumbent local exchange carrier selects, and may end no later than 5 five years after the incumbent local exchange carrier's monthly number-portability charge takes effect. (i) An incumbent local exchange carrier may assess each end user it serves in the 100 largest metropolitan statistical areas, and each end user it serves from a number-portability-capable switch outside the 100 largest metropolitan statistical areas, one monthly number-portability charge per line except that: (A) One PBX trunk shall receive nine monthly number-portability charges. (B) One PRI ISDN line shall receive five monthly number-portability charges. (C) Lifeline Assistance Program customers shall not receive the monthly number-portability charge. (ii) An incumbent local exchange carrier may assess on carriers that purchase the incumbent local exchange carrier's switching ports as unbundled network elements under section 251 of the Communications Act, and/or Feature Group A access lines, and resellers of the incumbent local exchange carrier's local service, the same charges as described in paragraph (a)(1)(i) of this section, as if the incumbent local exchange carrier were serving those carriers' end users. (iii) An incumbent local exchange carrier may not assess a monthly number-portability charge for local loops carriers purchase as unbundled network elements under section 251. (iv) The incumbent local exchange carrier shall levelize the monthly number-portability charge over five years by setting a rate for the charge at which the present value of the revenue recovered by the charge does not exceed the present value of the cost being recovered, using a discount rate equal to the rate of return on investment which the Commission has prescribed for interstate access services pursuant to Part 65 of the Commission's Rules. (2) The number portability query-service charge may recover only carrier-specific costs directly related to providing long-term number portability that the incumbent local exchange carrier incurs to provide long-term number portability query service to carriers on a prearranged and default basis. (3) An incumbent local exchange carrier serving an area outside the 100 largest metropolitan statistical areas that is not number-portability capable but that participates in an extended area service calling plan with any one of the 100 largest metropolitan statistical areas or with an adjacent number portability-capable local exchange carrier may assess each end user it serves one monthly number-portability query/administration charge per line to recover the costs of queries, as specified in paragraph (a)(2) of this section, and carrier-specific costs directly related to the carrier's allocated share of the regional local number portability administrator's costs, except that per-line monthly number-portability query/administration charges shall be assigned as specified in paragraph (a)(1) of this section with respect to monthly number-portability charges. (i) Such incumbent local exchange carriers may assess a separate monthly number-portability charge as specified in paragraph (a)(1) of this section but such charge may recover only the costs incurred to implement number portability functionality and shall not include costs recovered through the monthly number-portability query/administration charge. (ii) The monthly number-portability query/administration charge may end no later than five years after the incumbent local exchange carrier's monthly number-portability query/administration charge takes effect. The monthly number-portability query/administration charge may be collected over a different five-year period than the monthly number-portability charge. These five-year periods may run either consecutively or concurrently, in whole or in part. (b) All telecommunications carriers other than incumbent local exchange carriers may recover their number portability costs in any manner consistent with applicable state and federal laws and regulations. [63 FR 35161, June 29, 1998, as amended at 67 FR 40620, June 13, 2002; 73 FR 9481, Feb. 21, 2008; 80 FR 66479, Oct. 29, 2015] § 52.34 Obligations regarding local number porting to and from interconnected VoIP or Internet-based TRS providers. (a) An interconnected VoIP or VRS or IP Relay provider must facilitate an end-user customer's or a Registered Internet-based TRS User's valid number portability request, as it is defined in this subpart, either to or from a telecommunications carrier or an interconnected VoIP or VRS or IP Relay provider. “Facilitate” is defined as the interconnected VoIP or VRS or IP Relay provider's affirmative legal obligation to take all steps necessary to initiate or allow a port-in or port-out itself or through the telecommunications carriers, if any, that it relies on to obtain numbering resources, subject to a valid port request, without unreasonable delay or unreasonable procedures that have the effect of delaying or denying porting of the NANP-based telephone number. (b) An interconnected VoIP or VRS or IP Relay provider may not enter into any agreement that would prohibit an end-user customer or a Registered Internet-based TRS User from porting between interconnected VoIP or VRS or IP Relay providers, or to or from a telecommunications carrier. (c) Telecommunications carriers must facilitate an end-user customer's valid number portability request either to or from an interconnected VoIP or VRS or IP Relay provider. “Facilitate” is defined as the telecommunication carrier's affirmative legal obligation to take all steps necessary to initiate or allow a port-in or port-out itself, subject to a valid port request, without unreasonable delay or unreasonable procedures that have the effect of delaying or denying porting of the NANP-based telephone number. [73 FR 9481, Feb. 21, 2008, as amended at 73 FR 41294, July 18, 2008; 80 FR 66479, Oct. 29, 2015] § 52.35 Porting Intervals. (a) All telecommunications carriers required by the Commission to port telephone numbers must complete a simple wireline-to-wireline or simple intermodal port request within one business day unless a longer period is requested by the new provider or by the customer. The traditional work week of Monday through Friday represents mandatory business days and 8 a.m. to 5 p.m. represents minimum business hours, excluding the current service provider's company-defined holidays. An accurate and complete Local Service Request (LSR) must be received by the current service provider between 8 a.m. and 1 p.m. local time for a simple port request to be eligible for activation at midnight on the same day. Any simple port LSRs received after this time will be considered received on the following business day at 8 a.m. local time. (b) Small providers, as described in the 2009 LNP Porting Interval Order, (c) Unless directed otherwise by the Commission, any telecommunications carrier granted a waiver by the Commission of the one-business day porting interval described in paragraph (a) must complete a simple wireline-to-wireline or simple intermodal port request within four business days unless a longer period is requested by the new provider or by the customer. (d) All telecommunications carriers required by the Commission to port telephone numbers must complete a non-simple wireline-to-wireline or non-simple intermodal port request within four business days unless a longer period is requested by the new provider or by the customer. (e) For purposes of this section: (1) The term “local time” means the predominant time zone of the Number Portability Administration Center (NPAC) Region in which the telephone number is being ported; and (2) The term “intermodal ports” includes (i) Wireline-to-wireless ports; (ii) Wireless-to-wireline ports; and (iii) Ports involving interconnected VoIP service. [75 FR 35315, June 22, 2010, as amended at 80 FR 66480, Oct. 29, 2015] § 52.36 Standard data fields for simple port order processing. (a) A telecommunications carrier may require only the data described in paragraphs (b) and (c) of this section to accomplish a simple port order request from an end user customer's new telecommunication's carrier. (b) Required standard data fields. (1) Ported telephone number; (2) Account number; (3) Zip code; (4) Company code; (5) New network service provider; (6) Desired due date; (7) Purchase order number; (8) Version; (9) Number portability direction indicator; (10) Customer carrier name abbreviation; (11) Requisition type and status; (12) Activity; (13) Telephone number of initiator; and (14) Agency authority status. (c) Optional standard data field. [75 FR 35315, June 22, 2010, as amended at 80 FR 66480, Oct. 29, 2015] § 52.37 Number Portability Requirements for Wireless Providers. Link to an amendment published at 88 FR 85814, Dec. 8, 2023. (a) Applicability. (b) Authentication of port-out requests. (c)-(e) [Reserved] (f) Employee Training. (g) [Reserved] (h) This section contains information-collection and/or recordkeeping requirements. Compliance with this section will not be required until this paragraph is removed or contains a compliance date. [88 FR 85813, Dec. 8, 2023] §§ 52.38-52.99 [Reserved] Subpart D—Toll Free Numbers Source: 62 FR 20127, Apr. 25, 1997, unless otherwise noted. § 52.101 General definitions. As used in this part: (a) Toll Free Numbering Administrator (TFNA). (b) Responsible Organization (“RespOrg”). (c) Service Control Points. (d) Service Management System Database (“SMS Database”). (e) Toll Free Subscriber. (f) Toll Free Number. [62 FR 20127, Apr. 25, 1997, as amended at 83 FR 53395, Oct. 23, 2018] § 52.103 Lag times. (a) Definitions. (1) Assigned Status. (2) Disconnect Status. (3) Lag Time. (4) Reserved Status. (5) Seasonal Numbers. (6) Spare Status. (7) Suspend Status. (8) Unavailable Status. (9) Working Status. (10) Transitional Status. (b) Reserved Status. (1) Toll free numbers assigned via competitive bidding may remain in reserved status for a period of unlimited duration. (2) [Reserved] (c) Assigned Status. (d) Disconnect Status. (e) Suspend Status. (f) Unavailable Status. Toll Free Numbering Administrator (TFNA) Toll Free Numbering Administrator (TFNA) Toll Free Subscriber Toll Free Numbering Administrator (TFNA) (2) Seasonal numbers shall be placed in unavailable status. The Responsible Organization for a Toll Free Subscriber Toll Free Numbering Administrator (TFNA) [62 FR 20127, Apr. 25, 1997, as amended at 83 FR 53396, Oct. 23, 2018; 84 FR 11232, Mar. 26, 2019] § 52.105 Warehousing. (a) As used in this section, warehousing is the practice whereby Responsible Organizations, either directly or indirectly through an affiliate, reserve toll free numbers from the Service Management System database without having an actual toll free subscriber for whom those numbers are being reserved. (b) Responsible Organizations shall not warehouse toll free numbers. There shall be a rebuttable presumption that a Responsible Organization is warehousing toll free numbers if: (1) The Responsible Organization does not have an identified toll free subscriber agreeing to be billed for service associated with each toll free number reserved from the Service Management System database; or (2) The Responsible Organization does not have an identified toll free subscriber agreeing to be billed for service associated with a toll free number before switching that toll free number from reserved or assigned to working status. (c) Responsible Organizations shall not maintain a toll free number in reserved status if there is not a prospective toll free subscriber requesting that toll free number. (d) A Responsible Organization's act of reserving a number from the Service Management System database shall serve as that Responsible Organization's certification that there is an identified toll free subscriber agreeing to be billed for service associated with the toll free number. (e) Tariff Provision. [T]he Federal Communications Commission (“FCC”) has concluded that warehousing, which the FCC defines as Responsible Organizations, either directly or indirectly through an affiliate, reserving toll free numbers from the SMS database without having an identified toll free subscriber from whom those numbers are being reserved, is an unreasonable practice under § 201(b) of the Communications Act and is inconsistent with the Commission's obligation under § 251(e) of the Communications Act to ensure that numbers are made available on an equitable basis; and if a Responsible Organization does not have an identified toll free subscriber agreeing to be billed for service associated with each toll free number reserved from the database, or if a Responsible Organization does not have an identified, billed toll free subscriber before switching a number from reserved or assigned to working status, then there is a rebuttable presumption that the Responsible Organization is warehousing numbers. Responsible Organizations that warehouse numbers will be subject to penalties. (f) The provisions of this section shall not apply to toll free numbers assigned via competitive bidding or to numbers transferred under this exception. [62 FR 20127, Apr. 25, 1997, as amended at 83 FR 53396, Oct. 23, 2018] § 52.107 Hoarding. (a) As used in this section, hoarding is the acquisition by a toll free subscriber from a Responsible Organization of more toll free numbers than the toll free subscriber intends to use for the provision of toll free service. The definition of hoarding also includes number brokering, which is the selling of a toll free number by a private entity for a fee. (1) Toll free subscribers shall not hoard toll free numbers. (2) No person or entity shall acquire a toll free number for the purpose of selling the toll free number to another entity or to a person for a fee. (3) Routing multiple toll free numbers to a single toll free subscriber will create a rebuttable presumption that the toll free subscriber is hoarding or brokering toll free numbers. (b) Tariff Provision. [T]he Federal Communications Commission (“FCC”) has concluded that hoarding, defined as the acquisition of more toll free numbers than one intends to use for the provision of toll free service, as well as the sale of a toll free number by a private entity for a fee, is contrary to the public interest in the conservation of the scarce toll free number resource and contrary to the FCC's responsibility to promote the orderly use and allocation of toll free numbers. (c) Toll Free Numbers Assigned via Competitive Bidding. [62 FR 20127, Apr. 25, 1997, as amended at 83 FR 53396, Oct. 23, 2018] § 52.109 Permanent cap on number reservations. (a) A Responsible Organization may have in reserve status, at any one time, either 2000 toll free numbers or 7.5 percent of that Responsible Organization's numbers in working status, whichever is greater. (b) A Responsible Organization shall never reserve more than 3 percent of the quantity of toll free numbers in spare status as of the previous Sunday at 12:01 a.m. Eastern Time. (c) The Wireline Competition Bureau shall modify the quantity of numbers a Responsible Organization may have in reserve status or the percentage of numbers in the spare pool that a Responsible Organization may reserve when exigent circumstances make such action necessary. The Wireline Competition Bureau shall establish, modify, and monitor toll free number conservation plans when exigent circumstances necessitate such action. [62 FR 20127, Apr. 25, 1997, as amended at 67 FR 13226, Mar. 21, 2002; 83 FR 53396, Oct. 23, 2018] § 52.111 Toll free number assignment. Toll free telephone numbers must be made available to Responsible Organizations and subscribers on an equitable basis. The Commission will assign toll free numbers by competitive bidding, on a first-come, first-served basis, by an alternative assignment methodology, or by a combination of the foregoing options. [83 FR 53396, Oct. 23, 2018] Subpart E—Universal Dialing Code for National Suicide Prevention and Mental Health Crisis Hotline System Source: 85 FR 57783, Sept. 16, 2020, unless otherwise noted. § 52.200 Designation of 988 for a National Suicide Prevention and Mental Health Crisis Hotline. (a) 988 is established as the 3-digit dialing code for a national suicide prevention and mental health crisis hotline system maintained by the Assistant Secretary for Mental Health and Substance Use and the Secretary of Veterans Affairs. (b) All covered providers shall transmit all calls initiated by an end user dialing 988 to the national suicide prevention and mental health crisis hotline system maintained by the Assistant Secretary for Mental Health and Substance Use and the Secretary of Veterans Affairs. (c) All covered providers shall complete 10-digit dialing implementation in areas that use 7-digit dialing and have assigned 988 as a central office code as defined in § 52.7(c) by July 16, 2022. (d) All covered providers shall complete all changes to their systems that are necessary to implement the designation of the 988 dialing code by July 16, 2022. (e) For purposes of complying with the requirements of this section, (1) The term “covered provider” means any telecommunications carrier, interconnected VoIP provider, or provider of one-way VoIP. (2) The term “one-way VoIP”— (i) Means a service that— (A) Enables real-time, two-way voice communications; (B) Requires a broadband connection from the user's location; (C) Requires internet protocol-compatible customer premises equipment; and (D) Permits users generally to receive calls that originate on the public switched telephone network or to terminate calls to the public switched telephone network. (ii) Does not include any service that is an interconnected VoIP service. [85 FR 57783, Sept. 16, 2020, as amended at 89 FR 88905, Nov. 12, 2024] § 52.201 Texting to the National Suicide Prevention and Mental Health Crisis Hotline. (a) Support for 988 text message service. (b) Access to SMS networks for 988 text messages. (c) Definitions. 988 text message. (ii) Includes and is not limited to a SMS message and a multimedia message service (MMS) message; and (iii) Does not include— (A) A real-time, two-way voice or video communication; or (B) A message sent over an IP-enabled messaging service to another user of the same messaging service, except a message described in paragraph (b) of this section. Covered 988 text message Covered text provider Multimedia message service MMS Short message service SMS [87 FR 412, Jan. 5, 2022, as amended at 89 FR 88905, Nov. 12, 2024; 90 FR 44580, Sept. 16, 2025] § 52.202 Georouting of Wireless Calls to the National Suicide Prevention and Mental Health Crisis Hotline. (a) Georouting. (1) Have the capability to provide georouting data with 988 calls to the Lifeline Administrator in a format that is compatible with the Lifeline's routing platform, to allow routing of the 988 call by the Lifeline Administrator to the appropriate crisis center based on the geographic area where the handset is located at the time the 988 call is initiated. (2) Provide georouting data, when available, with 988 calls to the Lifeline Administrator sufficient to allow routing of the 988 call by the Lifeline Administrator to the appropriate crisis center based on the geographic area where the handset is located at the time the 988 call is initiated. (b) Scope of section. (1)(i) Offer real-time, two way switched voice service that is interconnected with the public switched network; and (ii) Use an in-network switching facility that enables the provider to reuse frequencies and accomplish seamless hand-offs of subscriber calls. These requirements are applicable to entities that offer voice service to consumers by purchasing airtime or capacity at wholesale rates from CMRS licensees. (2) The requirements of this section do not apply to 988 calls transmitted using roaming capabilities. (c) Compliance. (2) By 24 months after December 12, 2024: All CMRS providers shall provide georouting data with wireless 988 calls. (d) Definitions. Commercial mobile radio service (CMRS). (i)(A) Provided for profit, i.e., (B) An interconnected service; and (C) Available to the public, or to such classes of eligible users as to be effectively available to a substantial portion of the public; or (ii) The functional equivalent of such a mobile service described in paragraph (i)(A) of this definition. (iii) A variety of factors may be evaluated to make a determination whether the mobile service in question is the functional equivalent of a commercial mobile radio service, including: Consumer demand for the service to determine whether the service is closely substitutable for a commercial mobile radio service; whether changes in price for the service under examination, or for the comparable commercial mobile radio service, would prompt customers to change from one service to the other; and market research information identifying the targeted market for the service under review. (iv) Unlicensed radio frequency devices under part 15 of this chapter are excluded from this definition of Commercial mobile radio service. Georouting data. Lifeline Administrator. Nationwide CMRS provider. Non-nationwide CMRS provider. [89 FR 88905, Nov. 12, 2024] § 52.203 Georouting of text messages to the National Suicide Prevention and Mental Health Crisis Hotline. (a) Georouting. (1) Have the capability to provide georouting data for covered 988 text messages to the Lifeline Administrator in a format that is compatible with the Lifeline's routing platform, to allow routing of the 988 text message by the Lifeline Administrator to the appropriate crisis center based on the geographic area where the handset is located at the time the 988 text is initiated. (2) Provide georouting data, when available, for covered 988 text messages to the Lifeline Administrator sufficient to allow routing of the 988 text message by the Lifeline Administrator to the appropriate crisis center based on the geographic area where the handset is located at the time the 988 text message is initiated. (b) Definitions. (1) Covered 988 text message (2) Covered text provider (3) Georouting data (4) Lifeline Administrator (5) Nationwide CMRS provider (6) Non-nationwide CMRS provider (c) Compliance. (2) All covered text providers, including non-nationwide CMRS providers, shall provide georouting data for 988 text messages in accordance with paragraph (a) of this section by 36 months after October 16, 2025. [90 FR 44580, Sept. 16, 2025] Appendix to Part 52—Deployment Schedule for Long-Term Database Methods for Local Number Portability Implementation must be completed by the carriers in the relevant MSAs during the periods specified below: Phase I—10/1/97-3/31/98 Chicago, IL 3 Philadelphia, PA 4 Atlanta, GA 8 New York, NY 2 Los Angeles, CA 1 Houston, TX 7 Minneapolis, MN 12 Phase II—1/1/98-5/15/98 Detroit, MI 6 Cleveland, OH 20 Washington, DC 5 Baltimore, MD 18 Miami, FL 24 Fort Lauderdale, FL 39 Orlando, FL 40 Cincinnati, OH 30 Tampa, FL 23 Boston, MA 9 Riverside, CA 10 San Diego, CA 14 Dallas, TX 11 St. Louis, MO 16 Phoenix, AZ 17 Seattle, WA 22 Phase III—4/1/98-6/30/98 Indianapolis, IN 34 Milwaukee, WI 35 Columbus, OH 38 Pittsburgh, PA 19 Newark, NJ 25 Norfolk, VA 32 New Orleans, LA 41 Charlotte, NC 43 Greensboro, NC 48 Nashville, TN 51 Las Vegas, NV 50 Nassau, NY 13 Buffalo, NY 44 Orange Co, CA 15 Oakland, CA 21 San Francisco, CA 29 Rochester, NY 49 Kansas City, KS 28 Fort Worth, TX 33 Hartford, CT 46 Denver, CO 26 Portland, OR 27 Phase IV—7/1/98-9/30/98 Grand Rapids, MI 56 Dayton, OH 61 Akron, OH 73 Gary, IN 80 Bergen, NJ 42 Middlesex, NJ 52 Monmouth, NJ 54 Richmond, VA 63 Memphis, TN 53 Louisville, KY 57 Jacksonville, FL 58 Raleigh, NC 59 West Palm Beach, FL 62 Greenville, SC 66 Honolulu, HI 65 Providence, RI 47 Albany, NY 64 San Jose, CA 31 Sacramento, CA 36 Fresno, CA 68 San Antonio, TX 37 Oklahoma City, OK 55 Austin, TX 60 Salt Lake City, UT 45 Tucson, AZ 71 Phase V—10/1/98-12/31/98 Toledo, OH 81 Youngstown, OH 85 Ann Arbor, MI 95 Fort Wayne, IN 100 Scranton, PA 78 Allentown, PA 82 Harrisburg, PA 83 Jersey City, NJ 88 Wilmington, DE 89 Birmingham, AL 67 Knoxville, KY 79 Baton Rouge, LA 87 Charleston, SC 92 Sarasota, FL 93 Mobile, AL 96 Columbia, SC 98 Tulsa, OK 70 Syracuse, NY 69 Springfield, MA 86 Ventura, CA 72 Bakersfield, CA 84 Stockton, CA 94 Vallejo, CA 99 El Paso, TX 74 Little Rock, AR 90 Wichita, KS 97 New Haven, CT 91 Omaha, NE 75 Albuquerque, NM 76 Tacoma, WA 77 [62 FR 18295, Apr. 15, 1997]

Related documents

• 50 CFR Part 600 — Magnuson-Stevens Act Provisions#512148
• 50 CFR Part 622 — Fisheries of the Caribbean, Gulf of America, and South Atlantic#512149
• 50 CFR Part 635 — Atlantic Highly Migratory Species#512150
• 50 CFR Part 648 — Fisheries of the Northeastern United States#512151
• 50 CFR Part 660 — Fisheries off West Coast States#512152