Common use of One-Way Interconnection Trunks Clause in Contracts

One-Way Interconnection Trunks. (a) One-way Interconnection Trunk connections will be made at a DS-3 or DS- 1 level; subject to agreement of the Parties, higher speed connections (e.g., STS1, OCn) may be made, when and where available, in accordance with the Joint Process prescribed in Section 13.1 hereof. (b) Where the Parties deploy one-way Interconnection Trunks, in the event the traffic volume between any two (2) Central Office Switches at any time exceeds the centum call second (“ccs”) busy hour equivalent of one (1) DS-1, the originating Party will establish new Interconnection Trunk groups (prescribed in Section 4.1.1 hereof) to the applicable End Office(s) consistent with the grade of service and quality parameters set forth in the Joint Process prescribed in Section 13 hereof. (c) Each Party will use commercially reasonable efforts to monitor any one-way Interconnection Trunks that it orders and to alleviate blocking on such trunks using generally accepted trunk engineering standards so as to not exceed a blocking objective of B.01. Each Party agrees to use modular trunk engineering techniques (e.g., twenty- four (24) Interconnection Trunks as described in Bellcore Special Report SR-TSV- 002275) where practical. (d) At least semi-annually, AWS shall submit a good faith forecast to Verizon of the number of one-way Interconnection Trunks that AWS anticipates that it will require during the ensuing two (2) year period. Such trunk forecasts shall conform to industry standard guidelines as in effect from time to time. (e) The Parties shall meet (telephonically or in person), from time to time, as needed, to review the status of one-way trunking provisioning. The Parties shall make available to each other every month appropriate one-way trunking data (e.g., trunk usage data, trunk overflow data).

One-Way Interconnection Trunks. (a) One-way Interconnection Trunk connections will be made at a DS-3 or DS- 1 DS-1 level; subject to agreement of the Parties, higher speed connections (e.g., STS1, OCn) may be made, when and where available, in accordance with the Joint Process prescribed in Section 13.1 hereof. (b) Where the Parties deploy one-way Interconnection Trunks, in the event the traffic volume between any two (2) Central Office Switches at any time exceeds the centum call second (“ccs”) busy hour equivalent of one (1) DS-1, the originating Party will establish new Interconnection Trunk groups (prescribed in Section 4.1.1 hereof) to the applicable End Office(s) consistent with the grade of service and quality parameters set forth in the Joint Process prescribed in Section 13 hereof. (c) Each Party will use commercially reasonable efforts to monitor any one-way Interconnection Trunks that it orders and to alleviate blocking on such trunks using generally accepted trunk engineering standards so as to not exceed a blocking objective of B.01. Each Party agrees to use modular trunk engineering techniques (e.g., twenty- twenty-four (24) Interconnection Trunks as described in Bellcore Special Report SR-TSV- 002275TSV-002275) where practical. (d) At least semi-annually, AWS shall submit a good faith forecast to Verizon of the number of one-way Interconnection Trunks that AWS anticipates that it will require during the ensuing two (2) year period. Such trunk forecasts shall conform to industry standard guidelines as in effect from time to time. (e) The Parties shall meet (telephonically or in person), from time to time, as needed, to review the status of one-way trunking provisioning. The Parties shall make available to each other every month appropriate one-way trunking data (e.g., trunk usage data, trunk overflow data). Two-Way Interconnection Trunks The Parties acknowledge that they currently utilize two-way trunking for Type 2A and Type 2B Interconnection Trunks. The Parties agree that they will utilize two-way trunking for Type 2A and Type 2B Interconnection Trunks for CMRS traffic in the future, so long as Verizon can measure usage on such Interconnection Trunks, subject to the terms set forth below and the other terms of this Agreement. (a) Except to the extent that AWS may have already done so, not later than sixty (60) days after the Effective Date of this Agreement, AWS shall provide to Verizon forecast information on the appropriate initial number of high usage and final two-way Interconnection Trunks. (b) At least semi-annually, AWS shall submit a good faith forecast to Verizon including the number of high usage and final two-way Interconnection Trunks that AWS anticipates that it will require during the ensuing two (2) year period. Such trunk forecasts shall conform to industry standard guidelines as in effect from time to time. (c) The Parties shall meet (telephonically or in person), from time to time, as needed, to review the status of two-way trunk provisioning. The Parties shall make available to each other every month appropriate two-way trunking data (e.g., trunk usage data, trunk overflow (blocking) data). (d) AWS shall be responsible for determining the number of two-way Interconnection Trunks required. Accordingly, AWS shall submit ASRs, from time to time, to Verizon setting forth the number of two-way Interconnection Trunks that it is ordering, to include the dates by which AWS wishes to have such two-way Interconnection Trunks installed. AWS shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time. (e) The Parties shall use an economic ccs equal to five (5). Further general information regarding trunking may be found in Telcordia reference SR-TAP-000191. (f) In the event the traffic volume between any two (2) Central Office Switches at any time exceeds the centum call second (“CCS”) busy hour equivalent of one (1) DS-1, AWS will establish new two-way Interconnection Trunk groups (prescribed in Section 4.1.2 hereof) to the applicable End Office(s). (g) If a final two-way Interconnection Trunk has a utilization level of less than sixty percent (60%) for three (3) consecutive months, AWS shall promptly submit an ASR to disconnect such Interconnection Trunk, unless the Parties agree that this Interconnection Trunk should not be disconnected. The determination of trunk utilization levels shall be made in accordance with industry standard engineering practices. (h) Two-way Interconnection Trunks utilized hereunder shall be from a Verizon End Office or Tandem to a mutually agreeable AWS Point of Interconnection. (i) Both Parties shall use either a DS1 or DS3 interface, or higher speeds as available and agreed to by the Parties, at the Point of Interconnection. (j) As Verizon will not be in control of the sizing of two-way Interconnection Trunks between its network and the network of AWS, performance on these Interconnection Trunks shall be excluded from any performance measurements and related provisions that Verizon implements, except for unexcused missed installation appointments and maintenance service intervals. (k) Maintenance service intervals for two-way Interconnection Trunks provided by Verizon to AWS shall be in parity with the service intervals for two-way Interconnection Trunks that Verizon provides to other telecommunications carriers in Massachusetts. (l) If two-way Interconnection Trunks are provisioned using a DS-3 interface facility, AWS shall order the multiplexed DS-3 facilities to the Verizon Central Office that is designated in the NECA 4 Tariff as an intermediate hub location, unless otherwise agreed to in writing by Verizon. The specific NECA 4 intermediate hub location to be used for two-way Interconnection Trunks shall be in the appropriate Verizon Tandem subtending area based on the LERG. In the event the appropriate DS-3 intermediate hub is not used in the ordering process, AWS shall pay one hundred percent (100%) of the facility charges. (m) Type 2A two-way Interconnection Trunks may carry only Local Traffic, IntraLATA Toll Traffic and InterLATA Toll Traffic. Type 2B two-way Interconnection Trunks may carry only Local Traffic and IntraLATA Toll Traffic. For the avoidance of any doubt, the following types of traffic may not be carried over two-way Interconnection Trunks: 911/E911 traffic, directory assistance traffic, operator services traffic, information services traffic and choke trunk traffic.

One-Way Interconnection Trunks. (a) One-way Interconnection Trunk connections will be made at a DS-3 or DS- 1 DS-1 level; subject to agreement of the Parties, higher speed connections (e.g., STS1, OCn) may be made, when and where available, in accordance with the Joint Process prescribed in Section 13.1 hereof. (b) Where the Parties deploy one-way Interconnection Trunks, in the event the traffic volume between any two (2) Central Office Switches at any time exceeds the centum call second (“ccs”) busy hour equivalent of one (1) DS-1, the originating Party will establish new Interconnection Trunk groups (prescribed in Section 4.1.1 hereof) to the applicable End Office(s) consistent with the grade of service and quality parameters set forth in the Joint Process prescribed in Section 13 hereof. (c) Each Party will use commercially reasonable efforts to monitor any one-way Interconnection Trunks that it orders and to alleviate blocking on such trunks using generally accepted trunk engineering standards so as to not exceed a blocking objective of B.01. Each Party agrees to use modular trunk engineering techniques (e.g., twenty- twenty-four (24) Interconnection Trunks as described in Bellcore Special Report SR-TSV- 002275TSV-002275) where practical. (d) At least semi-annually, AWS shall submit a good faith forecast to Verizon of the number of one-way Interconnection Trunks that AWS anticipates that it will require during the ensuing two (2) year period. Such trunk forecasts shall conform to industry standard guidelines as in effect from time to time. (e) The Parties shall meet (telephonically or in person), from time to time, as needed, to review the status of one-way trunking provisioning. The Parties shall make available to each other every month appropriate one-way trunking data (e.g., trunk usage data, trunk overflow data).