You are using an unsupported browser. This web site is designed for the current versions of Microsoft Edge, Google Chrome, Mozilla Firefox, or Safari.
The Office of the Federal Register publishes documents on behalf of Federal agencies but does not have any authority over their programs. We recommend you directly contact the agency associated with the content in question.
If you have comments or suggestions on how to improve the www.ecfr.gov website or have questions about using www.ecfr.gov, please choose the 'Website Feedback' button below.
If you would like to comment on the current content, please use the 'Content Feedback' button below for instructions on contacting the issuing agency
Enhanced content is provided to the user to provide additional context.
This content is from the eCFR and is authoritative but unofficial.
Navigate by entering citations or phrases (eg: 1 CFR 1.1 49 CFR 172.101 Organization and Purpose 1/1.1 Regulation Y FAR).
Choosing an item from citations and headings will bring you directly to the content. Choosing an item from full text search results will bring you to those results. Pressing enter in the search box will also bring you to search results.
Background and more details are available in the Search & Navigation guide.
The in-page Table of Contents is available only when multiple sections are being viewed.
Use the navigation links in the gray bar above to view the table of contents that this content belongs to.
47 U.S.C. 151-154, 152(a), 155(c), 157, 160, 201, 202, 208, 210, 214, 218, 219, 222, 225, 251(e), 255, 301, 302, 303, 307, 308, 309, 310, 316, 319, 332, 403, 405, 605, 610, 615, 615 note, 615a, 615b, 615c, 615a-1, 616, 620, 621, 623, 623 note, 721, and 1471, and Section 902 of Title IX, Division FF, Pub. L. 116-260, 134 Stat. 1182, unless otherwise noted.
84 FR 66760, Dec. 5, 2019, unless otherwise noted.
89 FR 78128, Sept. 24, 2024, unless otherwise noted.
This content is from the eCFR and may include recent changes applied to the CFR. The official, published CFR, is updated annually and available below under "Published Edition". You can learn more about the process here.
Subscribe to: 47 CFR 9.29
View the most recent official publication:
These links go to the official, published CFR, which is updated annually. As a result, it may not include the most recent changes applied to the CFR. Learn more.
Information and documentation can be found in our developer resources.
The Code of Federal Regulations (CFR) is the official legal print publication containing the codification of the general and permanent rules published in the Federal Register by the departments and agencies of the Federal Government. The Electronic Code of Federal Regulations (eCFR) is a continuously updated online version of the CFR. It is not an official legal edition of the CFR.
Learn more about the eCFR, its status, and the editorial process.
(a) Phase 1. Upon receipt of a 911 Authority's valid request, an originating service provider that is subject to the rules in this subpart shall, by the relevant deadline specified in § 9.30(a)(1) or (b)(1)—
(1) Deliver all 911 traffic bound for the relevant PSAPs in the IP-based SIP format requested by the 911 Authority;
(2) Obtain and deliver 911 traffic to enable the ESInet and other NG911 network facilities to transmit all 911 traffic to the destination PSAP;
(3) Deliver all such 911 traffic to NG911 Delivery Points designated by the 911 Authority pursuant to § 9.32; and
(4) Complete connectivity testing to confirm that the 911 Authority receives 911 traffic in the IP-based SIP format requested by the 911 Authority.
(b) Phase 2. Upon receipt of a 911 Authority's valid request, an originating service provider that is subject to the rules in this subpart shall, by the relevant deadline specified in § 9.30(a)(2) or (b)(2)—
(1) Comply with all Phase 1 requirements set forth in paragraph (a) of this section;
(2) Deliver all 911 traffic bound for the relevant PSAPs to NG911 Delivery Points designated by the 911 Authority pursuant to § 9.32 in the IP-based SIP format that complies with NG911 commonly accepted standards identified by the 911 Authority, including having location information embedded in the call signaling using Presence Information Data Format—Location Object (PIDF-LO) or the functional equivalent;
(3) Install and put into operation all equipment, software applications, and other infrastructure, or acquire all services, necessary to use a Location Information Server (LIS) or its functional equivalent for the verification of its customer location information and records; and
(4) Complete connectivity testing to confirm that the 911 Authority receives 911 traffic in the IP-based SIP format that complies with the identified NG911 commonly accepted standards.