AT&T KENTUCKY. 8.1.1.2.1.1 Local Intermediary Charge (LIC) - charge for Transit Service on a per MOU basis.
AT&T KENTUCKY. CLEC shall send all IntraLATA toll traffic to be terminated by an independent telephone company to the End User’s IntraLATA toll provider and shall not send such traffic to AT&T KENTUCKY as Transit Traffic. IntraLATA toll traffic shall be any traffic that originates outside of the terminating independent telephone company’s local calling area.
AT&T KENTUCKY communicates official information to CARRIERs via its Accessible Letter, or other applicable, notification processes. These processes involve electronic transmission and/or posting to the AT&T CLEC Online website, inclusive of a variety of subjects including declaration of a force majeure, changes on business processes and policies, and other product/service related notices not requiring an amendment to this Agreement.
AT&T KENTUCKY will forward the ANI to the calling party number it receives from CLEC and the associated 911 ALI to the PSAP for display. If no ANI is forwarded by CLEC, AT&T KENTUCKY will forward an Emergency Service Central Office (ESCO) identification code for display at the PSAP. If ANI is forwarded by the CLEC, but no ALI record is found in the E911 DBMS, AT&T KENTUCKY will report this “No Record Found” condition to the CLEC in accordance with NENA standards.
AT&T KENTUCKY shall provide and maintain sufficient dedicated E911 Trunks from AT&T KENTUCKY’s E911 SR to the PSAP of the E911 Customer, according to provisions of the appropriate state Commission- approved tariff and documented specifications of the E911 Customer.
AT&T KENTUCKY shall transport its End Users’ 911 calls from its Wire Centers to the INdigital telecom POI(s) on the AT&T KENTUCKY network within the LATA where the 911/E911 Customer is located. This traffic may be aggregated after AT&T KENTUCKY Wire Center origination and prior to delivery to the INdigital telecom E911 Selective Router. In the event AT&T KENTUCKY’s Wire Center has End Users served by more than one E911 Selective Router network, AT&T KENTUCKY shall transport its End Users’ 911 calls from its Wire Center to the AT&T KENTUCKY E911 Selective Router location.
4.1.1.1 Where a Wire Center serves End Users both within and outside of the INdigital telecom E911 Service area, AT&T KENTUCKY shall work cooperatively with INdigital telecom and the affected 911/E911 Customer(s) (i) to establish call routing and/or call handoff arrangements; (ii) to establish which E911 Service provider will serve as the “primary” Selective Routing provider for direct trunking from the split Wire Center, determined by a clear majority based on the Number of Access Lines (NALs) served by the Designated Primary Wireline 911/E911 Service Provider unless mutually agreed to otherwise; and (iii) to establish which 911/E911 Service provider will serve as the “secondary” Selective Routing provider receiving a call hand-off from the primary Selective Routing provider.
AT&T KENTUCKY shall forward the ANI information of the party calling 911 to the INdigital telecom E911 Selective Router.
AT&T KENTUCKY acknowledges that its End Users in a Wire Center may be served by different E911 Selective Routers, and AT&T KENTUCKY shall be responsible for providing interconnection facilities to route 911 calls from its End Users to the proper INdigital telecom POI(s).
AT&T KENTUCKY shall provide a minimum of two (2) one-way outgoing 911 Trunk(s) dedicated for originating 911 emergency service calls from its Wire Centers to each INdigital telecom E911 Selective Router, where applicable. Where SS7 connectivity is available and required by the applicable 911/E911 Customer, the Parties agree to implement Common Channel Signaling trunking rather than CAMA MF trunking.
AT&T KENTUCKY is responsible for providing a separate E911 Trunk group for each county or other geographic area that AT&T KENTUCKY serves if the 911/E911 Customer for such county or geographic area has a specified varying default routing condition. Where MF signaling is used and PSAPs do not have the technical capability to receive 10-digit ANI, E911 traffic must be transmitted over a separate trunk group specific to the underlying technology. In addition, 911 traffic originating in one (1) NPA (area code) must be transmitted over a separate 911 Trunk group from 911 traffic originating in any other NPA (area code) 911.
