Interconnection Trunks Clause Samples
POPULAR SAMPLE Copied 1 times
Interconnection Trunks. Subject to mutual agreement of the Parties, not to be unreasonably withheld, the Parties shall configure, pursuant to Section 4.4.1 hereof, separate one-way Interconnection Trunks for CMRS traffic from AWS to Verizon, and for CMRS traffic from Verizon to AWS, respectively, or, alternatively, the Parties shall configure two-way Interconnection Trunks for CMRS traffic as provided for under Section 4.4.2 hereof.
Interconnection Trunks. Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and BLC, BLC, at its own expense, shall:
2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon's network in a LATA; and/or
2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon's network in a LATA (a) from a third party, or, (b) if Verizon offers such transport pursuant to a Verizon access Tariff, from Verizon. Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and BLC, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon's network in a LATA. Prior to establishing any Two-Way Interconnection Trunks, BLC shall meet with Verizon to conduct a joint planning meeting ("Joint Planning Meeting"). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon's network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. BLC SCcomp v3.3 56 2.4.4 2.4.5 2.4.6 2.4.7 2.4.8 2.4.9 2.4.10
Interconnection Trunks. 2.3.1 The Parties agree to provision Local Interconnection Trunks on a two way basis. If requested by either Party, prior to provisioning any Local Interconnection Trunks, the Parties may 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 initial number of Local Interconnection Trunks and the interface specifications at the Point of Interconnection (“POI”).
2.3.2 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.3 With respect to Local Interconnection Trunks, both Parties shall engineer to P.01 grade of service.
2.3.4 TCA shall determine and provision the number of Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Local Interconnection Trunk group. TCA shall provision Local Interconnection Trunks by submitting ASRs to ▇▇▇▇▇ setting forth the number of Local Interconnection Trunks to be installed and the requested installation dates within ▇▇▇▇▇’▇ 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.
2.3.5 TCA is solely responsible for the ordering of adequate Local Interconnection Trunks to carry traffic under this agreement, provided however that ▇▇▇▇▇ shall provision Local Interconnection Trunks ordered by TCA within ▇▇▇▇▇’▇ standard provisioning intervals for similarly situated carriers.
2.3.6 Each Party will bear all recurring and non-recurring charges associated with Local Interconnection Trunk groups on its side of the POI established pursuant to this Agreement. Neither Party shall have any obligation to bear any charges, expenses or other costs assessed in connection with transporting, transiting or switching traffic on the other Party’s side of the POI.
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 observe...
Interconnection Trunks. NYNEX shall pay ANTC as Liquidated Damages according to the schedule set forth in Section 33.7.1.4 following. Excluded from Missed Appointments will be Customer misses, where ANTC is not ready or required access is not available. Also excluded will be Trunks missed when Trunks exceed the annual forecast by over five percent (5%) in the specific location.
Interconnection Trunks. The Parties agree to provision Local Interconnection Trunks on a two way basis. If requested by either Party, prior to provisioning any Local Interconnection Trunks, the Parties may 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 initial number of Local Interconnection Trunks and the interface specifications at the Point of Interconnection (“POI”).
Interconnection Trunks. 1. Performance Category 7 – Interconnection Trunk Provisioning Calculation of Performance Credit:
Interconnection Trunks. Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from BLC to Verizon, BLC, at BLC's own expense, shall:
Interconnection Trunks. The publication “Telcordia Technical Publication GR-342-CORE; High Capacity Digital Special Access Service, Transmission Parameter Limits and Interface Combination” describes the specification and interfaces generally utilized by Verizon and is referenced herein to assist the Parties in meeting their respective Interconnection responsibilities. If a Party elects, and the other Party agrees, to provision its own One Way trunks, that Party will be responsible for the expense of providing the transmission facilities supporting those trunks, in accordance with the terms of this Agreement. Where switch limitations in combination with use of Two-Way trunking would degrade service or materially inhibit traffic recording capability necessary for billing (which, as of the Effective Date Verizon understands to be applicable to certain of its DMS switches), a Party may elect to use One-Way trunks without the agreement of the other Party.
Interconnection Trunks. Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from HTCC to Verizon, HTCC, at HTCC's own expense, shall: