Interconnection 2.1 This section applies to linking with suppliers providing public telecommunications transport networks or services in order to allow the users of one supplier to communicate with users of another supplier and to access services provided by another supplier, where specific commitments are undertaken.
Two-Way Interconnection Trunks 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and KDL, KDL, 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 this Agreement or an applicable Verizon Tariff, from Verizon.
2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and KDL, 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.
2.4.3 Prior to establishing any Two-Way Interconnection Trunks, KDL 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 Centium 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.
2.4.4 On a semi-annual basis, KDL shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that KDL anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between KDL and Verizon. KDL’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks.
2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.
2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced.
2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Verizon and KDL shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275).
2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three
Interconnection Customer’s Interconnection Facilities The Interconnection Customer shall design, procure, construct, install, own and/or control the Interconnection Customer’s Interconnection Facilities described in Appendix A at its sole expense.
One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Onvoy’s own expense, shall:
2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or
2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier.
2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment.
2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.
Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks.
6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order.
6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall ▇▇▇▇ the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information.
6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall ▇▇▇▇ the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic.
6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor