Common use of For IntraLATA Clause in Contracts

For IntraLATA. Toll Traffic which is subject to a PTC arrangement and where Ameritech is the PTC, Ameritech shall deliver such IntraLATA Toll Traffic to or from Requesting Carrier in accordance with the terms and conditions of such PTC arrangement. Ameritech shall reimburse Requesting Carrier at Requesting Carrier’s applicable tariffed terminating switched access rates. VII.2.8 IntraLATA 800 Traffic shall be exchanged between the Parties as follows: (a) IntraLATA 800 Traffic may be delivered to Ameritech over the Local IntraLATA Trunks and if Ameritech performs the 800 query function, over the Access Toll Connecting Trunks. If the Local/IntraLATA Trunks are used and Requesting Carrier performs the 800 query function, the IntraLATA 800 Traffic will be recorded as toll calls. If the Access Toll Connecting Trunks are used, Ameritech will not record the IntraLATA 800 Traffic. (b) The Parties shall provide to each other IntraLATA 800 Access Detail Usage Data for Customers billing and IntraLATA 800 Copy Detail Usage Data for access billing. EMR exchange between the Parties will use the standard centralized message system delivery systems (CMDS). The Parties agree to provide this data to each other at no charge. In the event of errors, omissions, or inaccuracies in data received from either Party, the liability of the Party providing such data shall be limited to the provision or corrected data only. (c) IntraLATA 800 Traffic calls are billed to and paid for by the called or terminating party, regardless of which Party performs the 800 query. Because IntraLATA 800 Traffic may not be identified with a unique Carrier Identification Code (CIC), billing shall be based on originating and terminating NPA/NXX.

For IntraLATA. Toll Traffic which is subject to a PTC arrangement and where Ameritech is the PTC, Ameritech shall deliver such IntraLATA Toll Traffic to or from Requesting Carrier in accordance with the terms and conditions of such PTC arrangement. Upon receipt of verifiable Primary Toll records, Ameritech shall reimburse Requesting Carrier at Requesting Carrier’s applicable tariffed terminating switched access rates. When transport mileage cannot be determined, an average transit transport mileage shall be applied as set forth on the Pricing Schedule. VII.2.8 VII.3.9 IntraLATA 800 Traffic shall be exchanged between the Parties as follows: (a) Queried IntraLATA 800 Traffic may be delivered to Ameritech over the Local IntraLATA Trunks and if Ameritech performs the 800 query function, over the Access Toll Connecting Trunks. If the Local/IntraLATA Trunks are used and Requesting Carrier performs the 800 query function, the IntraLATA 800 Traffic will be recorded as toll calls. If the Access Toll Connecting Trunks are used, Ameritech will not record the IntraLATA 800 Traffic. (b) The Parties shall provide to each other IntraLATA 800 Access Detail Usage Data for Customers billing and IntraLATA 800 Copy Detail Usage Data for access billing. EMR exchange between the Parties will use the standard centralized message system delivery systems (CMDS). The Parties agree to provide this data to each other at no charge. In the event of errors, omissions, or inaccuracies in data received from either Party, the liability of the Party providing such data shall be limited to the provision or of corrected data only. (c) IntraLATA 800 Traffic calls are billed to and paid for by the called or terminating party, regardless of which Party performs the 800 query. Because IntraLATA 800 Traffic may not be identified with a unique Carrier Identification Code (CIC), billing shall be based on originating and terminating NPA/NXX.