Common use of Interconnection Trunks Clause in Contracts

Interconnection Trunks. 2.3.1 The Parties agree to provision Local Interconnection Trunks on a two way basis. Prior to provisioning any initial or additional Local Interconnection Trunks, the Parties shall meet (telephonically or in person) to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate number of initial or additional Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). 2.3.2 On an annual basis or when TCA determines that actual utilization necessitates the submission of revised forecasts, TCA shall submit a good faith forecast to MTC of the number of Local Interconnection Trunks that TCA anticipates that MTC will need to provide during the ensuing two (2) year period. TCA’s trunk forecasts shall conform to the MTC TCA trunk forecasting guidelines that may be in effect at that time and made available upon request by TCA. 2.3.3 The Parties shall meet (telephonically or in person) from time to time, as requested by either Party, to review data on Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Local Interconnection Trunks. 2.3.4 Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) facilities, with a DS1, DS3 or higher interface as justified by the traffic volume exchanged between the Parties and where technically feasible and commercially available. 2.3.5 With respect to Local Interconnection Trunks, both Parties shall engineer to P.01 grade of service. 2.3.6 TCA shall provision the Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Local Interconnection Trunk group as reflected in TCA’s forecast as provided to MTC. TCA shall provision Local Interconnection Trunks by submitting ASRs to MTC setting forth the number of Local Interconnection Trunks to be installed and the requested installation dates within MTC’s effective standard intervals or negotiated intervals, as appropriate. TCA shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time. MTC may monitor Local Interconnection Groups using service results for the applicable design blocking objective. If MTC observes blocking in excess of the applicable design objective on any final Local Interconnection Trunk group and TCA has not notified MTC that it has corrected such blocking, MTC may submit to TCA a Trunk Group Service Request directing TCA to remedy the blocking. Upon receipt of a Trunk Group Service Request, TCA will complete an ASR to augment the Local Interconnection Group with excessive blocking and submit the ASR to MTC within ten

Interconnection Trunks. 2.3.1 The Parties agree to provision Local Interconnection Trunks on a two way basis. Prior to provisioning any initial or additional Local Interconnection Trunks, the Parties shall meet (telephonically or in person) to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate number of initial or additional Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). 2.3.2 On an annual basis or when TCA LEVEL 3 determines that actual utilization necessitates the submission of revised forecasts, TCA LEVEL 3 shall submit a good faith forecast to MTC HTC of the number of Local Interconnection Trunks that TCA LEVEL 3 anticipates that MTC HTC will need to provide during the ensuing two (2) year period. TCALEVEL 3’s trunk forecasts shall conform to the MTC TCA HTC LEVEL 3 trunk forecasting guidelines that may be in effect at that time and made available upon request by TCALEVEL 3. 2.3.3 The Parties shall meet (telephonically or in person) from time to time, as requested by either Party, to review data on Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Local Interconnection Trunks. 2.3.4 Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) facilities, with a DS1, DS3 or higher interface as justified by the traffic volume exchanged between the Parties and where technically feasible and commercially available. 2.3.5 With respect to Local Interconnection Trunks, both Parties shall engineer to P.01 grade of service. 2.3.6 TCA LEVEL 3 shall provision the Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Local Interconnection Trunk group as reflected in TCALEVEL 3’s forecast as provided to MTCHTC. TCA LEVEL 3 shall provision Local Interconnection Trunks by submitting ASRs to MTC HTC setting forth the number of Local Interconnection Trunks to be installed and the requested installation dates within MTC’s effective standard intervals or negotiated intervals, as appropriate. TCA shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time. MTC may monitor HTC’s 2.3.7 LEVEL 3 is solely responsible for the ordering of adequate Local Interconnection Groups using service results Trunks to carry traffic under this agreement, provided however that HTC shall provision Local Interconnection Trunks ordered by LEVEL 3 within HTC’s standard provisioning intervals for the applicable design blocking objective. If MTC observes blocking in excess of the applicable design objective on any final similarly situated carriers. 2.3.8 LEVEL 3 will bear all recurring and non-recurring charges associated with Local Interconnection Trunk group and TCA has not notified MTC that it has corrected such blockinggroups established pursuant to this Agreement. Neither Party shall have any obligation to bear any charges, MTC may submit to TCA a Trunk Group Service Request directing TCA to remedy expenses or other costs assessed in connection with transporting, transiting or switching traffic on the blocking. Upon receipt other Party’s side of a Trunk Group Service Request, TCA will complete an ASR to augment the Local Interconnection Group with excessive blocking and submit the ASR to MTC within tenPOI.