§9.29. Next Generation 911 transition requirements. — Inbound Citations

A 911 Authority may designate one or more NG911 Delivery Points where originating service providers must deliver 911 traffic to the ESInet pursuant to § 9.29, provided that—

(a) Originating service providers are responsible for the costs of complying with the applicable Phase 1 and Phase 2 requirements assigned to them under § 9.29, including the costs of—

(1) Transmitting 911 traffic to NG911 Delivery Points;

(2) Delivering 911 traffic in the required IP-based SIP format at each phase, including the cost of IP conversion using a Legacy Network Gateway or the functional equivalent, if necessary; and

(3) Obtaining and delivering location and routing information using ALI/ANI databases, selective routers, or other means at Phase 1, and using LIS functionalities or other equivalent means at Phase 2.

(a) Nothing in this subpart shall prevent 911 Authorities and originating service providers from establishing, by mutual consent, terms different from the requirements set forth in §§ 9.29 through 9.33.

(1) Comply with the Phase 1 requirements set forth in § 9.29(a) by six months after receiving a Phase 1 valid request from a 911 Authority, as set forth in § 9.31(a); and

(a) A 911 Authority's request for delivery of 911 traffic in the manner specified in § 9.29(a) is a Phase 1 valid request if the requesting 911 Authority—

(1) Certifies that it has installed and placed into operation all of the infrastructure needed to receive 911 traffic in an IP-based SIP format and transmit such traffic to the PSAP(s) connected to it;

(2) Certifies that it has obtained commitments from any ESInet provider, Next Generation 911 Core Services provider, and/or call handling equipment provider needed to facilitate and complete connectivity testing within the compliance timeframe applicable to the originating service provider;

(3) Certifies that it is authorized to submit a valid request for the NG911 network to receive 911 traffic in an IP-based SIP format;

(4) Identifies the NG911 Delivery Point(s) designated pursuant to § 9.32; and

(5) Provides notification to the originating service provider that includes the information and certifications set forth in paragraphs (a)(1) through (4) of this section. Notification by the 911 Authority via a registry made available by the Commission in accordance with requirements established in connection therewith, or any other written notification reasonably acceptable to the originating service provider, shall constitute sufficient notification for purposes of this paragraph.

(2) Comply with the Phase 2 requirements set forth in § 9.29(b) by:

(i) Six months after receiving a Phase 2 valid request from a 911 Authority, as set forth in § 9.31(b); or

(ii) If the 911 Authority's Phase 2 valid request is made before the originating service provider is compliant with the Phase 1 requirements or is made before the Phase 1 implementation deadline, six months after the earlier of:

(A) The date when the originating service provider is compliant with the Phase 1 requirements set forth in § 9.29(a); or

(b) A 911 Authority's request for delivery of 911 traffic in the manner specified in § 9.29(b) is a Phase 2 valid request if the requesting 911 Authority—

(1) Certifies that it has installed and placed into operation all of the infrastructure needed to receive 911 traffic in an IP-based SIP format that complies with NG911 commonly accepted standards and transmit such traffic to the PSAP(s) connected to it;

(2) Certifies that its ESInet is connected to a fully functioning Next Generation 911 Core Services network that can provide access to a Location Validation Function and interface with a Location Information Server or its functional equivalent provided by the originating service provider;

(3) Certifies that it has obtained commitments from any ESInet provider, Next Generation 911 Core Services provider, and/or call handling equipment provider needed to facilitate and complete connectivity testing within the compliance timeframe applicable to the originating service provider;

(4) Certifies that it is authorized to submit a valid request for the NG911 network to receive 911 traffic in an IP-based SIP format that complies with NG911 commonly accepted standards;

(5) Identifies the NG911 Delivery Point(s) designated pursuant to § 9.32; and

(6) Provides notification to the originating service provider that includes the information and certifications set forth in paragraphs (b)(1) through (5) of this section. Notification by the 911 Authority via a registry made available by the Commission in accordance with requirements established in connection therewith, or any other written notification reasonably acceptable to the originating service provider, shall constitute sufficient notification for purposes of this paragraph.