Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex 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 CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). 2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center. 2.4.3 On a semi-annual basis, Teleconex shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex anticipates that Verizon will need to provide during the ensuing two (2) year period. Teleconex’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks. 2.4.5 Two-Way Local 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.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5). 2.4.7 Two-Way Local 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 Local 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 Teleconex shall engineer Two-Way Local Interconnection Trunks using national standards. 2.4.8 Teleconex shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time. 2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level. 2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour. 2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local 2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan. 2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI. 2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic. 2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office. 2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Synergem, Synergem, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Synergem, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Synergem 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Meet Point A (high usage) and Meet Point B (final) Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Synergem shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex Synergem anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Synergem and Verizon. TeleconexSynergem’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced.
2.4.8 Meet Point B 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; . Meet Point B Two-Way Local 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 Teleconex Synergem shall engineer Two-Way Local Interconnection Trunks using national standardsTelcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV- 002275).
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 Synergem shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Synergem shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Synergem shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and Synergem has not notified Verizon that it has corrected such blocking, Verizon may submit to Synergem a Trunk Group Service Request directing Synergem to remedy the blocking. Upon receipt of a Trunk Group Service Request, Synergem will complete an ASR to establish or augment the Meet Point A Two- Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Synergem will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Synergem will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Synergem fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or ▇▇▇▇ (and Synergem shall pay) for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexSynergem’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 Synergem will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192SR- TAP-000191, including but not limited to those standards requiring that a call from Teleconex Synergem to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex Synergem and the Verizon End Office.
2.4.18 When 3.1 Fiber Meet Arrangement Provisions.
3.1.1 Each Party may request a Fiber Meet arrangement by providing written notice thereof to the other Party if each of the following conditions has been met: (a) the Parties have consistently been exchanging an amount of applicable traffic (as set forth in Section 3.1.3 below) in the relevant exchanges equal to at least one (1) DS-3 and (b) neither Synergem nor any of Synergem’s affiliates has an overdue balance on any ▇▇▇▇ rendered to Synergem or Synergem’s affiliates for charges that are not subject to a good faith dispute. Any such Fiber Meet arrangement shall be subject to the terms of this Agreement. In addition, the establishment of any Fiber Meet arrangement is expressly conditioned upon the Parties mutually agreeing to the technical specifications and requirements for such Fiber Meet arrangement including, but not limited to, the location of the Fiber Meet points, routing, equipment (e.g., specifications of Add/Drop Multiplexers, number of strands of fiber, etc.), software, ordering, provisioning, maintenance, repair, testing, augment and on any other technical specifications or requirements necessary to implement Two-Way Local Interconnection Trunksthe Fiber Meet arrangement. For each Fiber Meet arrangement the Parties agree to implement, the Parties will work cooperatively complete and sign a Technical Specifications and Requirements document, the form of which is attached hereto as Exhibit A to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use Section 3 of the facility Interconnection Attachment Fiber Meet Arrangement Provisions. Each such document will be treated as shown Confidential Information.
3.1.2 The Parties agree to consider the possibility of using existing fiber cable with spare capacity, where available, to implement any such request for a Fiber Meet arrangement. If existing fiber cable with spare capacity is not available, the Parties agree to minimize the construction and deployment of fiber cable necessary for any Fiber Meet arrangement to which they agree. Except as otherwise agreed by the PPU. The PPU Parties, any and all Fiber Meet points established between the Parties shall extend no further than three (3) miles from an applicable Verizon Tandem or End Office and Verizon shall not be applied required to calculate the charges construct or deploy more than five hundred (500) feet of fiber cable for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall Fiber Meet arrangement.
3.1.3 A Fiber Meet arrangement established under this Agreement may be solely the financial responsibility of Teleconex. Non-recurring charges used for the facility on which transmission and routing of only the Two-Way following traffic types (over the Interconnection Trunks ride shall be apportioned as follows: Trunks):
3.1.3.1 Reciprocal Compensation Traffic between the Parties’ respective Telephone Exchange Service Customers;
3.1.3.2 Translated LEC IntraLATA toll free service access code (ae.g., 800/888/877) for traffic between the portion of Parties’ respective Telephone Exchange Service Customers;
3.1.3.3 IntraLATA Toll Traffic between the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.Parties’ respective Telephone Exchange Service Customers;
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and VNCI, VNCI, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and VNCI, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex VNCI 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 CCS Centium Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex VNCI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex VNCI anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between VNCI and Verizon. TeleconexVNCI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local 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 Teleconex VNCI shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and GNAPS, prior GNAPS shall order from Verizon, and Verizon shall provide, the Two- Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex GNAPS 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 CCS Centium Call Second (Hundred Call Second) information, and GNAPs the Parties shall mutually ordermutually agree on the appropriate initial number of Two-Way End Office Meet Point A (high usage) and Tandem Local Meet Point B (final) Interconnection Trunks it requires and will provide Verizon withand the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to the GNAPs’-designated a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex each PartyGNAPS shall submit a good faith forecast to Verizon the otherVerizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex itGNAPS anticipates that Verizon the other PartyVerizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from GNAPS to Verizon and from Verizon to GNAPS. TeleconexGNAPS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. GNAPs in its good faith performance of its obligations according to the Agreement shall provide trunk forecasts in a reasonably complete manner sufficient to allow Verizon to review, process, and prepare for such trunk forecasts. GNAPs will use reasonable efforts to provide forecasting according to Verizon’s reasonable forecasting guidelines as in effect at that time and Verizon will not refuse to accept, process, and act upon any such trunk forecast that substantially complies with Verizon’s reasonable and non- discriminatory trunk forecasting guidelines then in effect unless and only unless Verizon proves that GNAPs provided information that materially alters the accuracy of the information GNAPs sought to provide in the trunk forecast.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available and where technically feasible.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Meet Point B Two-Way Local 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; . Meet Point B Two-Way Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇-▇▇▇▇▇▇▇▇▇ B.01 B.0051 during the average time consistent busy hour. Verizon and Teleconex GNAPS shall engineer Two-Way Local Interconnection Trunks using national standardsaccepted industry standardsBOC Notes on the LEC Networks SR-TSV-002275.
2.4.8 Teleconex 2.4.9 The performance standard for Meet Point B Two-Way Interconnection Trunks shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for onethree (31) consecutive calendar traffic study months.
2.4.10 GNAPS shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex GNAPS shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex GNAPS shall complete ASRs in accordance with Ordering and Billing Forum OBF Guidelines as in effect from time to time.
2.4.9 . Verizon may monitor shall reasonably accept ASRs submitted by GNAPs and shall use commercially reasonable efforts to insure timely installation and activation of such Two-Way Local Interconnection Trunks.
2.4.11 Each Party willVerizon may (but shall not be obligated to) monitor Two- Way Interconnection Groups using service results for the applicable design-design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Meet Point B (final) Two-Way Local Interconnection Trunk group and Teleconex the originating PartyGNAPS has not notified Verizon the receiving PartyVerizon that it has corrected such blocking, Verizon the receiving PartyVerizon may submit to Teleconex the originating PartyGNAPS a Trunk Group Service Request directing Teleconex GNAPS to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex the originating PartyGNAPS will complete an ASR to augment the Two-Two- Way Local Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Meet Point B Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex GNAPS will promptly augment all Tandem Meet Point B Two-Way Local
2.4.13 The performance standard on final Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, GNAPS will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control promptly submit ASRs to disconnect a sufficient number of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision attain a utilization level of this Agreementapproximately sixty percent (60%) for each respective group, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When unless the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic agree that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall should not be apportioned as follows: (a) disconnected. In the event GNAPS fails to submit an ASR for Two- Way Interconnection Trunks in conformance with this section, Verizon may bill GNAPS for the portion of excess Interconnection Trunks at the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPsapplicable Verizon rates.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and VarTec, prior VarTec shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex VarTec 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex VarTec shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex VarTec anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from VarTec to Verizon and from Verizon to VarTec. TeleconexVarTec’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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-. Two- Way Local 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 Teleconex VarTec shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 VarTec shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. VarTec shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. VarTec shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and VarTec has not notified Verizon that it has corrected such blocking, Verizon may submit to VarTec a Trunk Group Service Request directing VarTec to remedy the blocking. Upon receipt of a Trunk Group Service Request, VarTec will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. VarTec will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, VarTec will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event VarTec fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ VarTec for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexVarTec’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 VarTec will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex VarTec to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex VarTec and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex VarTec will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexVarTec’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexVarTec’s side of Teleconex’sVarTec’s-IP, which charges shall be solely the financial responsibility of TeleconexVarTec. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the TeleconexVarTec-IP, VarTec shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on VarTec’s side of the VarTec-IP, VarTec shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if VarTec fails to provide VarTec-IPs in accordance with this Agreement, VarTec will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex VarTec establishes such VarTec- IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and CSTC, CSTC, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and CSTC, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex CSTC 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Meet Point A (high usage) and Meet Point B (final) Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex CSTC shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex CSTC anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between CSTC and Verizon. TeleconexCSTC’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Meet Point B Two-Way Local 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; . Meet Point B Two-Way Local 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 Teleconex CSTC shall engineer Two-Way Local Interconnection Trunks using national standardsBOC Notes on the LEC Networks SR- TSV-002275.
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 CSTC shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. CSTC shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. CSTC shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and CSTC has not notified Verizon that it has corrected such blocking, Verizon may submit to CSTC a Trunk Group Service Request directing CSTC to remedy the blocking. Upon receipt of a Trunk Group Service Request, CSTC will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. CSTC will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, CSTC will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event CSTC fails to submit an ASR for Two- Way Interconnection Trunks in conformance with this Section, Verizon may ▇▇▇▇ CSTC for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexCSTC’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 CSTC will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex CSTC to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex CSTC and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Premiere 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 CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex Premiere is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a semi-annual basis, Teleconex Premiere shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Premiere anticipates that Verizon will need to provide during the ensuing two (2) year period. TeleconexPremiere’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 With respect to End Office TwoOfficeTwo-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local 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 Teleconex Premiere shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex Premiere shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex Premiere shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex Premiere shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex Premiere has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex Premiere a Trunk Group Service Request directing Teleconex Premiere to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex Premiere will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any And Tandem Two-Way Local Interconnection Trunk group between the TeleconexPremiere’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex Premiere shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon requestAs part of the joint planning meeting between Premiere and Verizon, Teleconex Premiere will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex Premiere will calculate utilization percentages by using a traffic data analyzation system specified mutually agreed upon by Verizonthe Parties, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex Premiere will promptly augment all Tandem Two-Way LocalLocal Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Local Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Premiere will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group. In the event Premiere fails to submit an ASR for Two-Way Local Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ Premiere for the excess Local Interconnection Trunks at the applicable rates provided for in the Pricing Attachment.
2.4.13 The performance standard on final TwofinalTwo-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and TeleconexPremiere’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex Premiere will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex Premiere to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex Premiere and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex Premiere will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexPremiere’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexPremiere’s side of Teleconex’sPremiere’s-IP, which charges shall be solely the financial responsibility of TeleconexPremiere. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the TeleconexPremiere-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on Premiere’s side of the Premiere-IP, Premiere shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.18, if Premiere fails to provide IPs at Verizon’s Tandem or End Office(s) in accordance with this Agreement, Premiere will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Local Interconnection Trunk groups until Teleconex Premiere establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and CBAD, CBAD, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and CBAD, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex CBAD 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Meet Point A (high usage) and Meet Point B (final) Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex CBAD shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex CBAD anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between CBAD and Verizon. TeleconexCBAD’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced.
2.4.8 Meet Point B 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; . Meet Point B Two-Way Local 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 Teleconex CBAD shall engineer Two-Way Local Interconnection Trunks using national standardsTelcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV- 002275).
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 CBAD shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. CBAD shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. CBAD shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and CBAD has not notified Verizon that it has corrected such blocking, Verizon may submit to CBAD a Trunk Group Service Request directing CBAD to remedy the blocking. Upon receipt of a Trunk Group Service Request, CBAD will complete an ASR to establish or augment the Meet Point A Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. CBAD will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, CBAD will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event CBAD fails to submit an ASR for Two- Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or ▇▇▇▇ (and CBAD shall pay) for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexCBAD’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 CBAD will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex CBAD to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex CBAD and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and PCS, prior PCS shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex PCS 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office Meet Point A (high usage) and Tandem Local Meet Point B (final) Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex PCS shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex PCS anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from PCS to Verizon and from Verizon to PCS. TeleconexPCS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Meet Point B Two-Way Local 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. Meet Point BTwo-Way Local 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 Teleconex PCS shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeLEC Networks SR- TSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 PCS shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. PCS shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. PCS shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and PCS has not notified Verizon that it has corrected such blocking, Verizon may submit to PCS a Trunk Group Service Request directing PCS to remedy the blocking. Upon receipt of a Trunk Group Service Request, PCS will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. PCS will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, PCS will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event PCS fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ PCS for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexPCS’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 PCS will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex PCS to a Verizon End Office will first be routed to the End Office Local Interconnection Meet Point AInterconnection Trunk group between Teleconex PCS and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex PCS will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexPCS’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexPCS’s side of Teleconex’sPCS’s-IP, which charges shall be solely the financial responsibility of TeleconexPCS. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two- Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the TeleconexPCS -IP, PCS shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on PCS’s side of the PCS-IP, PCS shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if PCS fails to provide PCS -IPs in accordance with this Agreement, PCS will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex PCS establishes such PCS-IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and BullsEye, prior BullsEye shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex BullsEye 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex BullsEye shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex BullsEye anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from BullsEye to Verizon and from Verizon to BullsEye. TeleconexBullsEye’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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-. Two- Way Local 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 Teleconex BullsEye shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 BullsEye shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. BullsEye shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. BullsEye shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and BullsEye has not notified Verizon that it has corrected such blocking, Verizon may submit to BullsEye a Trunk Group Service Request directing BullsEye to remedy the blocking. Upon receipt of a Trunk Group Service Request, BullsEye will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk Group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. BullsEye will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, BullsEye will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event BullsEye fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ BullsEye for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexBullsEye’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI.
2.4.16 Notwithstanding any other provision of , provided that, if a Party has failed to comply with this Agreement, Two-Agreement with regard to Two- Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each other Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use may upon three (3) months prior written notice and without mutual agreement of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of non- complying Party, withdraw its traffic from a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally TwoTrunk group and install One-Way Local Interconnection Trunk groups until Teleconex establishes such IPsTrunks to the non- complying Party’s relevant POI.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and LifeLine, prior LifeLine shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex LifeLine 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office Meet Point A (high usage) and Tandem Local Meet Point B (final) Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex LifeLine shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex LifeLine anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from LifeLine to Verizon and from Verizon to LifeLine. TeleconexLifeLine’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Meet Point B Two-Way Local 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; . Meet Point B Two-Way Local 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 Teleconex LifeLine shall engineer Two-Way Local Interconnection Trunks using national standardsBOC Notes on the LEC Networks SR- TSV-002275.
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 LifeLine shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. LifeLine shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. LifeLine shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and LifeLine has not notified Verizon that it has corrected such blocking, Verizon may submit to LifeLine a Trunk Group Service Request directing LifeLine to remedy the blocking. Upon receipt of a Trunk Group Service Request, LifeLine will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. LifeLine will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, LifeLine will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event LifeLine fails to submit an ASR for Two- Way Interconnection Trunks in conformance with this section, Verizon may bill LifeLine for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexLifeLine’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 LifeLine will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex LifeLine to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex LifeLine and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex LifeLine will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexLifeLine’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexLifeLine’s side of Teleconex’sLifeLine’s-IP, which charges shall be solely the financial responsibility of TeleconexLifeLine. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the TeleconexLifeLine-IP, LifeLine shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on LifeLine’s side of the LifeLine-IP, LifeLine shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if LifeLine fails to provide LifeLine-IPs in accordance with this Agreement, LifeLine will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex LifeLine establishes such LifeLine-IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and GNAPS, prior GNAPS shall order from Verizon, and Verizon shall provide, the Two- Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex GNAPS 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office Meet Point A (high usage) and Tandem Local Meet Point B (final) Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Pursuant to the Arbitration Order, Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon the GNAPs- designated POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex GNAPS shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex GNAPS anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from GNAPS to Verizon and from Verizon to GNAPS. TeleconexGNAPS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Pursuant to the Arbitration Order, Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available and where technically feasible.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Meet Point B Two-Way Local 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; . Meet Point B Two-Way Local 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 Teleconex GNAPS shall engineer Two-Way Local Interconnection Trunks using national standardsBOC Notes on the LEC Networks SR- TSV-002275.
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because 2.4.10 GNAPS shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. GNAPS shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon will setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. GNAPS shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. Pursuant to the Arbitration Order, Verizon shall reasonably accept ASRs submitted by GNAPs and shall use commercially reasonable efforts to insure timely installation and activation of such Two-Way Interconnection Trunks.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in control excess of the timing applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and sizing GNAPS has not notified Verizon that it has corrected such blocking, Verizon may submit to GNAPS a Trunk Group Service Request directing GNAPS to remedy the blocking. Upon receipt of a Trunk Group Service Request, GNAPS will complete an ASR to augment the Two-Way Local Interconnection Trunks between its network Trunk Group with excessive blocking and Teleconex’s network, Verizon’s performance on these submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Local Interconnection Trunk groups shall that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. GNAPS will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, GNAPS will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be subject disconnected. In the event GNAPS fails to any performance measurements and remedies under submit an ASR for Two- Way Interconnection Trunks in conformance with this Agreementsection, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or planVerizon may ▇▇▇▇ GNAPS for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.15 2.4.13 [Intentionally left blank pursuant to the Arbitration Order.]
2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 GNAPS will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192SR- TAP-000191, including but not limited to those standards requiring that a call from Teleconex GNAPS to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex GNAPS and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex GNAPS will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexGNAPS’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexGNAPS’s side of Teleconex’sGNAPS’s-IP, which charges shall be solely the financial responsibility of TeleconexGNAPS. NonDuring the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Pursuant to the Arbitration Order, non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: equally. Notwithstanding the foregoing provisions of this Section 2.4.16, if GNAPS fails to provide GNAPS-IPs in accordance with this Agreement, GNAPS will be responsible for one hundred percent (a100%) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex GNAPS establishes such GNAPS-IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and PNG, PNG, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and PNG, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex PNG 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex PNG shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex PNG anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between PNG and Verizon. TeleconexPNG’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex PNG shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 PNG shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. PNG shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. PNG shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and PNG has not notified Verizon that it has corrected such blocking, Verizon may submit to PNG a Trunk Group Service Request directing PNG to remedy the blocking. Upon receipt of a Trunk Group Service Request, PNG will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. PNG will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, PNG will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event PNG fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may ▇▇▇▇ PNG for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexPNG’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 PNG will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex PNG to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex PNG and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where Notwithstanding anything set forth in the Interconnection Agreement, the Parties have agreed shall configure separate One-Way Interconnection Trunks for the delivery of traffic from PaeTec to use Two VERIZON, and for the delivery of traffic from VERIZON to PaeTec, respectively; provided, however, that in lieu thereof, upon receipt of PaeTec’s written request, VERIZON shall provide Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between the networks of VERIZON and PaeTec pursuant, prior and subject, to ordering the rates, terms and conditions specified in the NYPSC No. 914, as amended from time to time, and the additional terms and conditions set forth below:
(1) Prior to requesting any Two-Way Local Interconnection Trunks from VerizonVERIZON, Teleconex PaeTec shall meet with Verizon VERIZON 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 Two-Way End Office Meet Point A (high usage) and Tandem Local Interconnection Meet Point B (final)Interconnection Trunks and the interface specifications at the Point of Interconnection (“POI”).
2.4.2 . At the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for requests to convert existing Meet Point A and Meet Point B One-Way Interconnection Trunks to Meet Point A and Meet Point B Two-Way Local Interconnection Trunks.
(2) Two-Way Interconnection Trunks shall be from a Verizon VERIZON End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 (3) On a semi-annual basis, Teleconex PaeTec shall submit a good faith forecast to Verizon VERIZON of the number of End Office Meet Point A and Tandem Meet Point B Two-Way Local Interconnection Trunks that Teleconex PaeTec anticipates that Verizon the Parties will need to provide require from VERIZON during the ensuing two (2) year period. TeleconexPaeTec’s trunk forecasts shall conform to the Verizon VERIZON CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 (4) The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A and Tandem Meet Point B Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 (5) Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 (6) With respect to End Office Meet Point A Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 (7) Meet Point B Two-Way Local Interconnection Trunk groups that connect to a Verizon VERIZON access Tandem shall be engineered using a design blocking objective of N▇▇▇▇-- ▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour; Meet Point B Two-Way Local Interconnection Trunk groups that connect to a Verizon VERIZON local Tandem shall be engineered using a design blocking objective of ▇N▇▇▇ ▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Verizon VERIZON and Teleconex PaeTec shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex (8) PaeTec shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex PaeTec shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon VERIZON setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s VERIZON’S effective standard intervals or negotiated intervals, as appropriate. Teleconex PaeTec shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon . VERIZON may monitor Two-Way Local Interconnection Groups using service results for the applicable design-design blocking objective. If Verizon VERIZON observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex PaeTec has not notified Verizon VERIZON that it has corrected such blocking, Verizon VERIZON may submit to Teleconex PaeTec a Trunk Group Service Request directing Teleconex PaeTec to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex PaeTec will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon VERIZON within five (5) Business Daysbusiness days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. (9) In the event that any Tandem Two-Way Local the traffic volume between a VERIZON End Office and the PaeTec POI, which is carried by a Meet Point B Interconnection Trunk group group, exceeds the 240 trunk level CCS busy hour equivalent of one (1) DS-1 at any timetime or 200,000 combined minutes of use for a single month, Teleconex PaeTec shall promptly submit an ASR to Verizon VERIZON to establish a new or additional End Office Trunk groups to insure that such Tandem Meet Point A Two-Way Local Interconnection Trunk group does not exceed Trunks between that VERIZON End Office and the 240 trunk levelPaeTec POI.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.(10) [INTENTIONALLY LEFT BLANK]
2.4.12 (11) The Parties will review all Tandem Meet Point B Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), ) percent of the engineered capacity or greater, greater to determine whether those groups should be augmented. Teleconex PaeTec will promptly augment all Tandem Meet Point B Two-Way LocalInterconnection Trunk groups that reach a utilization level of eighty percent (80%) of the engineered capacity by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%) of the engineered capacity, unless the Parties agree that additional trunking is not required. For each Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%) of the engineered capacity, PaeTec will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) of the engineered capacity for each respective group, unless the Parties agree that the Interconnection Trunks should not be disconnected. In the event PaeTec fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, VERIZON may b▇▇▇ PaeTec for the excess Interconnection Trunks at the applicable rates set forth in Exhibit A.
2.4.13 (12) The performance standard on final Meet Point B Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 (13) Because Verizon VERIZON will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and TeleconexPaeTec’s network, Verizon’s VERIZON’S performance on these Two-Way Local Interconnection Trunk groups shall not be subject to excluded from any performance measurements and remedies under this Agreement, andremedies, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or planfor unexcused missed installation appointments.
2.4.15 (14) Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s POI.
2.4.16 (15) Both Parties shall use either a DS-1 or DS-3 interface at the POI for Two-Way Interconnection Trunks. Upon mutual agreement, the Parties may use other types of interfaces, such as STS-1 or OC-n, at the POI, when and where available. When Two-Way Interconnection Trunks are provisioned using a DS-3 interface facility, PaeTec 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 Tandem subtending area based on the LERG. In the event the appropriate DS 3 Intermediate Hub is not used in the ordering process, then PaeTec shall pay 100% of the facility charges
(16) Notwithstanding any other provision of the Interconnection Agreement or this AgreementAmendment, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex (17) If PaeTec materially breaches a material term of this Section l(a), and has not remedied such breach within thirty (30) days of written notice thereof, VERIZON may cease provisioning Two-Way Interconnection Trunks under this Amendment.
(18) Except as set forth in the next sentence or otherwise agreed in writing by the Parties, the total number of Meet Point B Two-Way Interconnection Trunks between PaeTec’s network and a VERIZON Tandem will be limited to a maximum of 240 trunks. The total number of Meet Point B Two-Way Interconnection Trunks between PaeTec’s’s network and a VERIZON Tandem described in Attachment A of this Amendment shall be limited to a maximum of 672 trunks, unless otherwise mutually agreed to in writing by the parties. In the event that the volume of traffic between PaeTec’s network and a VERIZON Tandem exceeds, or reasonably can be anticipated to exceed, the capacity of the maximum permitted number of Meet Point B Two-Way Interconnection Trunks, PaeTec shall promptly submit an ASR to VERIZON to establish new or additional Meet Point A Trunks to insure that the volume of traffic between PaeTec’s network and the VERIZON Tandem does not exceed the capacity of the maximum permitted number of Meet Point B Two-Way Interconnection Trunks.
(19) PaeTec will route its traffic to Verizon VERIZON over the End Office Meet Point A and Tandem Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those industry standards requiring that a call from Teleconex PaeTec to a Verizon VERIZON End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex PaeTec and the Verizon VERIZON End Office.
2.4.18 (20) When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on where the numerator is the total number of minutes of Traffic that each Party originates over the traffic carried from PaeTec to VERIZON on all Two-Way Local Interconnection Trunks and the denominator is the total number of minutes of traffic carried over such Two-Way Interconnection Trunks. Teleconex PaeTec will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexPaeTec’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a the facility that is on TeleconexPaeTec’s side of Teleconex’sthe PaeTec’s-IP, which charges shall be solely the financial responsibility of Teleconexthe PaeTec. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the TeleconexPaeTec-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on PaeTec’s side of the PaeTec-IP, PaeTec shall be solely responsible for the nonrecurring charges. Notwithstanding the foregoing provisions of this Section 20, if PaeTec fails to provide geographic IPs in accordance with the Interconnection Agreement, PaeTec will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Local Interconnection Trunk groups until Teleconex PaeTec establishes such IPs. During the first calendar quarter (and any partial quarter) after Two-Way Interconnection Trunks are initially established, PPU will be fifty percent (50%). In each quarter thereafter, the Parties may recalculate the PPU using actual traffic usage for the preceding three month period. When One-Way Interconnection Trunks are converted to Two-Way Interconnection Trunks, PaeTec will pay fifty percent (50%) of the non-recurring charges.
Appears in 1 contract
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and CBB, CBB, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and CBB, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex CBB 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 CCS Centium Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex CBB shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex CBB anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between CBB and Verizon. TeleconexCBB’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local 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 Teleconex CBB shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Prospeed, Prospeed, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Prospeed, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Prospeed 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Meet Point A (high usage) and Meet Point B (final) Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Prospeed shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex Prospeed anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Prospeed and Verizon. TeleconexProspeed’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Meet Point B Two-Way Local 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; . Meet Point B Two-Way Local 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 Teleconex Prospeed shall engineer Two-Way Local Interconnection Trunks using national standardsBOC Notes on the LEC Networks SR- TSV-002275.
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 Prospeed shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Prospeed shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Prospeed shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and Prospeed has not notified Verizon that it has corrected such blocking, Verizon may submit to Prospeed a Trunk Group Service Request directing Prospeed to remedy the blocking. Upon receipt of a Trunk Group Service Request, Prospeed will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Prospeed will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Prospeed will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Prospeed fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may bill Prospeed for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexProspeed’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 Prospeed will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192SR- TAP-000191, including but not limited to those standards requiring that a call from Teleconex Prospeed to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex Prospeed and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and CCA, CCA, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and CCA, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex CCA 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex CCA shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex CCA anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between CCA and Verizon. TeleconexCCA’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex CCA shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and NationNet, prior NationNet shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex NationNet 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office Meet Point A (high usage) and Tandem Local Meet Point B (final) Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex NationNet shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex NationNet anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from NationNet to Verizon and from Verizon to NationNet. TeleconexNationNet’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Meet Point B Two-Way Local 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; . Meet Point B Two-Way Local 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 Teleconex NationNet shall engineer Two-Way Local Interconnection Trunks using national standardsBOC Notes on the LEC Networks SR- TSV-002275.
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 NationNet shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. NationNet shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. NationNet shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and NationNet has not notified Verizon that it has corrected such blocking, Verizon may submit to NationNet a Trunk Group Service Request directing NationNet to remedy the blocking. Upon receipt of a Trunk Group Service Request, NationNet will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. NationNet will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, NationNet will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event NationNet fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may bill NationNet for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexNationNet’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 NationNet will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192SR- TAP-000191, including but not limited to those standards requiring that a call from Teleconex NationNet to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex NationNet and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex NationNet will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexNationNet’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexNationNet’s side of Teleconex’sNationNet’s-IP, which charges shall be solely the financial responsibility of TeleconexNationNet. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the TeleconexNationNet-IP, NationNet shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on NationNet’s side of the NationNet-IP, NationNet shall be solely responsible for the non- recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if NationNet fails to provide NationNet -IPs in accordance with this Agreement, NationNet will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex NationNet establishes such IPsNationNet -IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NLG, NLG, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and NLG, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex NLG 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex NLG shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex NLG anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between NLG and Verizon. TeleconexNLG’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex NLG shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and TNCI, TNCI, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and TNCI, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex TNCI 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex TNCI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex TNCI anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between TNCI and Verizon. TeleconexTNCI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Verizon and Teleconex TNCI shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex NOS 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 CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex NOS is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a semi-annual basis, Teleconex NOS shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex NOS anticipates that Verizon will need to provide during the ensuing two (2) year period. TeleconexNOS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local 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 Teleconex NOS shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex NOS shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex NOS shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex NOS shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex NOS has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex NOS a Trunk Group Service Request directing Teleconex NOS to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex NOS will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the TeleconexNOS’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex NOS shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex NOS will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex NOS will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex NOS will promptly augment all Tandem Two-Way LocalLocal Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Local Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, NOS will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group. In the event NOS fails to submit an ASR for Two-Way Local Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ NOS for the excess Local Interconnection Trunks at the applicable rates provided for in the Pricing Attachment.
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and TeleconexNOS’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex NOS will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-SR- TAP192, including but not limited to those standards requiring that a call from Teleconex NOS to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex NOS and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex NOS will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexNOS’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexNOS’s side of Teleconex’sNOS’s-IP, which charges shall be solely the financial responsibility of TeleconexNOS. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the TeleconexNOS-IP, the non-non- recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.between the Parties; and,
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex BTI 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 CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a semi-annual basis, Teleconex BTI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex BTI anticipates that Verizon will need to provide during the ensuing two (2) year period. TeleconexBTI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local 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 Teleconex BTI shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex BTI shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex BTI shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex BTI shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time. Nothwithstanding the foregoing, the Parties may mutually agree that BTI may provide Local Interconnection Trunks, and will then establish mutually agreeable procedures for ordering and provisioning.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex BTI has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex BTI a Trunk Group Service Request directing Teleconex BTI to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex BTI will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Daysbusiness days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the TeleconexBTI’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex BTI shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex BTI will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex BTI will calculate utilization percentages by using a traffic data analyzation analysis system specified by Verizon, industry standard study periods and a time consistent busy hour...
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex BTI will promptly augment all Tandem Two-Way LocalLocal Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Local Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, BTI will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group. In the event BTI fails to submit an ASR for Two-Way Local Interconnection Trunks in conformance with this section, Verizon may bill BTI for the excess Local Interconnection Trunks at the applicable rates provided for in the Pricing Attachment.
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and TeleconexBTI’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.]
2.4.17 Teleconex BTI will route its traffic to Verizon over the End Office and Tandem Two-Two- Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex BTI to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex BTI and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex .. BTI will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexBTI’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexBTI’s side of Teleconex’sBTI’s-IP, which charges shall be solely the financial responsibility of TeleconexBTI. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the TeleconexBTI-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on BTI’s side of the BTI-IP, BTI shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.18, if BTI fails to provide IPs in accordance with Section 7.1, BTI will be responsible for one hundred percent (100%) of all recurring and non- recurring charges attributable to that portion of Two-Way Local Interconnection Trunk groups located outside the Rate Center boundary until Teleconex BTI establishes such IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and TNCI, TNCI, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and TNCI, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex TNCI 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex TNCI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex TNCI anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between TNCI and Verizon. TeleconexTNCI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex TNCI shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 TNCI shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. TNCI shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. TNCI shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and TNCI has not notified Verizon that it has corrected such blocking, Verizon may submit to TNCI a Trunk Group Service Request directing TNCI to remedy the blocking. Upon receipt of a Trunk Group Service Request, TNCI will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. TNCI will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, TNCI will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event TNCI fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may bill TNCI for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexTNCI’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 TNCI will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex TNCI to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex TNCI and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and ICG, ICG shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks, and the Entrance Facility on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Upon the parties undertaking a Major Project, where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex ICG shall meet meet, telephonically or in person, with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party forecasted originating CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . For purposes of this Section 2.4.2, a “Major Project” is a project that requires the coordination and execution of multiple orders or related activities between and among Verizon and ICG work groups including, but not limited to, the initial establishment of Interconnection or Access Toll Connecting Trunk groups between a Verizon switch and an ICG switch, NXX code moves, re-homes, facility grooming, network rearrangements, a conversion from One Way Interconnection Trunks to Two-Way Local Interconnection Trunks, and installation of a new switch.
2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex ICG is collocated in a Verizon Wire Center, the POI shall may be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex ICG shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex ICG anticipates that Verizon will need to provide during the ensuing two (2) year period. TeleconexICG’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as provided to ICG and in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 2.4.8 Verizon and ICG shall engineer Two-Way Local Interconnection Trunks using national standards and measurement methodologies. 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 Local 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 Teleconex shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.of
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Delta Phones, prior Delta Phones shall order from Verizon, and Verizon shall provide, the Two- Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Delta Phones 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Delta Phones shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Delta Phones anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from Delta Phones to Verizon and from Verizon to Delta Phones. TeleconexDelta Phones’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex Delta Phones shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Smartrak, Smartrak, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Smartrak, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Smartrak 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Smartrak shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Smartrak anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Smartrak and Verizon. TeleconexSmartrak’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local 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 Teleconex Smartrak shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex ReFlex 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 CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex ReFlex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a semi-annual basis, Teleconex ReFlex shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex ReFlex anticipates that Verizon will need to provide during the ensuing two (2) year period. TeleconexReFlex’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local 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 Teleconex ReFlex shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex ReFlex shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex ReFlex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex ReFlex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex ReFlex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex ReFlex a Trunk Group Service Request directing Teleconex ReFlex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex ReFlex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Daysbusiness days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the TeleconexReFlex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex ReFlex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex ReFlex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex ReFlex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex ReFlex will promptly augment all Tandem Two-Way LocalLocal Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Local Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, ReFlex will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group. In the event ReFlex fails to submit an ASR for Two-Way Local Interconnection Trunks in conformance with this section, Verizon may bill ReFlex for the excess Local Interconnection Trunks at the applicable rates provided for in the Pricing Attachment.
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and TeleconexReFlex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex ReFlex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex ReFlex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex ReFlex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex ReFlex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexReFlex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexReFlex’s side of Teleconex’sReFlex’s-IP, which charges shall be solely the financial responsibility of TeleconexReFlex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the TeleconexReFlex-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on ReFlex’s side of the ReFlex-IP, ReFlex shall be solely responsible for the non- recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.18, if ReFlex fails to provide IPs at Verizon’s Tandem or End Office(s) in accordance with this Agreement, ReFlex will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Local Interconnection Trunk groups until Teleconex ReFlex establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Best 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 CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex Best is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a semi-annual basis, Teleconex Best shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Best anticipates that Verizon will need to provide during the ensuing two (2) year period. TeleconexBest’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local 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 Teleconex Best shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex Best shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex Best shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex Best shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex Best has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex Best a Trunk Group Service Request directing Teleconex Best to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex Best will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Daysbusiness days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the TeleconexBest’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex Best shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex Best will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex Best will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex Best will promptly augment all Tandem Two-Way LocalLocal Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Local Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Best will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group. In the event Best fails to submit an ASR for Two-Way Local Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ Best for the excess Local Interconnection Trunks at the applicable rates provided for in the Pricing Attachment.
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and TeleconexBest’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex Best will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex Best to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex Best and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex .. Best will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexBest’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexBest’s side of Teleconex’sBest’s-IP, which charges shall be solely the financial responsibility of TeleconexBest. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the TeleconexBest-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on Best’s side of the Best-IP, Best shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.18, if Best fails to provide IPs at Verizon’s Tandem or End Office(s) in accordance with this Agreement, Best will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Local Interconnection Trunk groups until Teleconex Best establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Budget Phone, prior Budget Phone shall order from Verizon, and Verizon shall provide, the Two- Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Budget Phone 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office Meet Point A (high usage) and Tandem Local Meet Point B (final) Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Budget Phone shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex Budget Phone anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from Budget Phone to Verizon and from Verizon to Budget Phone. TeleconexBudget Phone’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Meet Point B Two-Way Local 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; . Meet Point B Two-Way Local 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 Teleconex Budget Phone shall engineer Two- Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275.
2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 Budget Phone shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Budget Phone shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Budget Phone shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and Budget Phone has not notified Verizon that it has corrected such blocking, Verizon may submit to Budget Phone a Trunk Group Service Request directing Budget Phone to remedy the blocking. Upon receipt of a Trunk Group Service Request, Budget Phone will complete an ASR to augment the Two- Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Budget Phone will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Budget Phone will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Budget Phone fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ Budget Phone for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexBudget Phone’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 Budget Phone will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192SR- TAP-000191, including but not limited to those standards requiring that a call from Teleconex Budget Phone to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex Budget Phone and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex Budget Phone will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexBudget Phone’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexBudget Phone’s side of Teleconex’sBudget Phone’s-IP, which charges shall be solely the financial responsibility of TeleconexBudget Phone. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the TeleconexBudget Phone-IP, Budget Phone shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on Budget Phone’s side of the Budget Phone-IP, Budget Phone shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if Budget Phone fails to provide Budget Phone-IPs in accordance with this Agreement, Budget Phone will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex Budget Phone establishes such Budget Phone-IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and SBCT, prior SBCT shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility (SBCT may obtain the entrance facility from a third party provider), on which such Trunks will ride, and transport and multiplexing, in accordance with rates, terms and conditions set forth in this Agreement and Verizon's applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex SBCT 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 CCS Centium Call Second (Hundred Call Second) information, if available, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.or
2.4.3 2.4.4 On a semi-annual basis, Teleconex SBCT shall submit a good faith forecast to Verizon of the number of the End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex SBCT anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from SBCT to Verizon and from Verizon to SBCT. TeleconexSBCT’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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-. Two- Way Local 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 Teleconex SBCT shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine BOC Notes on the LEC Networks SR-TSV-002275 and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection ▇▇▇▇ Communications Research, Inc. (TELCORDIA TECHNOLOGIES) document SR TAP 000191 – Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed Traffic Engineering Concepts and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeApplications.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 The Parties shall mutually agree upon and SBCT shall order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two- Way Interconnection Trunk group. SBCT shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. SBCT shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and SBCT has not notified Verizon that it has corrected
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. SBCT will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, SBCT will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event SBCT fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ SBCT for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks that are established between its network and TeleconexSBCT’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, except for unexcused missed installation appointments, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party's relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two-Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non-complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non-complying Party's relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 SBCT will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex SBCT to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex SBCT and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex SBCT will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the TeleconexSBCT-IP, SBCT shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on SBCT’s side of the SBCT-IP, SBCT shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if SBCT fails to provide SBCT-IPs in accordance with this Agreement, SBCT will be responsible for one hundred percent (100%) of all recurring and non- recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex SBCT establishes such SBCT-IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NL, NL, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and NL, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex NL 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex NL shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex NL anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between NL and Verizon. TeleconexNL’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex NL shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 NL shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. NL shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. NL shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and NL has not notified Verizon that it has corrected such blocking, Verizon may submit to NL a Trunk Group Service Request directing NL to remedy the blocking. Upon receipt of a Trunk Group Service Request, NL will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. NL will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, NL will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event NL fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may ▇▇▇▇ NL for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexNL’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 NL will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex NL to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex NL and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Excel, prior Excel shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Excel 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office Meet Point A (high usage) and Tandem Local Meet Point B (final) Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Excel shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex Excel anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from Excel to Verizon and from Verizon to Excel. TeleconexExcel’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Meet Point B Two-Way Local 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; . Meet Point B Two-Way Local 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 Teleconex Excel shall engineer Two-Way Local Interconnection Trunks using national standardsBOC Notes on the LEC Networks SR- TSV-002275.
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 Excel shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Excel shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Excel shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and Excel has not notified Verizon that it has corrected such blocking, Verizon may submit to Excel a Trunk Group Service Request directing Excel to remedy the blocking. Upon receipt of a Trunk Group Service Request, Excel will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Excel will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Excel will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Excel fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ Excel for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexExcel’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 Excel will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex Excel to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex Excel and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex Excel will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexExcel’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexExcel’s side of Teleconex’sExcel’s-IP, which charges shall be solely the financial responsibility of TeleconexExcel. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two- Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the TeleconexExcel-IP, Excel shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on Excel’s side of the Excel-IP, Excel shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if Excel fails to provide Excel-IPs in accordance with this Agreement, Excel will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex Excel establishes such Excel-IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and BullsEye, prior BullsEye shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex BullsEye 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office Meet Point A (high usage) and Tandem Local Meet Point B (final) Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex BullsEye shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex BullsEye anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from BullsEye to Verizon and from Verizon to BullsEye. TeleconexBullsEye’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Meet Point B Two-Way Local 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; . Meet Point B Two-Way Local 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 Teleconex BullsEye shall engineer Two-Way Local Interconnection Trunks using national standardsBOC Notes on the LEC Networks SR- TSV-002275.
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 BullsEye shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. BullsEye shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. BullsEye shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and BullsEye has not notified Verizon that it has corrected such blocking, Verizon may submit to BullsEye a Trunk Group Service Request directing BullsEye to remedy the blocking. Upon receipt of a Trunk Group Service Request, BullsEye will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk Group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. BullsEye will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, BullsEye will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event BullsEye fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ BullsEye for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexBullsEye’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 BullsEye will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192SR- TAP-000191, including but not limited to those standards requiring that a call from Teleconex BullsEye to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex BullsEye and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex BullsEye will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexBullsEye’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexBullsEye’s side of Teleconex’sBullsEye’s-IP, which charges shall be solely the financial responsibility of TeleconexBullsEye. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the TeleconexBullsEye-IP, BullsEye shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on BullsEye’s side of the BullsEye-IP, BullsEye shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if BullsEye fails to provide BullsEye-IPs in accordance with this Agreement, BullsEye will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex BullsEye establishes such BullsEye-IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and PN, PN, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and PN, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex PN 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Meet Point A (high usage) and Meet Point B (final) Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex PN shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex PN anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between PN and Verizon. TeleconexPN’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced.
2.4.8 Meet Point B 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; . Meet Point B Two-Way Local 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 Teleconex PN shall engineer Two-Way Local Interconnection Trunks using national standardsTelcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV- 002275).
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 PN shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. PN shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. PN shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and PN has not notified Verizon that it has corrected such blocking, Verizon may submit to PN a Trunk Group
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. PN will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, PN will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event PN fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or ▇▇▇▇ (and PN shall pay) for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexPN’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 PN will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex PN to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex PN and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and ***CLEC Acronym TXT***, prior ***CLEC Acronym TXT*** shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex ***CLEC Acronym TXT*** 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Two- Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex ***CLEC Acronym TXT*** shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Two- Way Local Interconnection Trunks that Teleconex ***CLEC Acronym TXT*** anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from ***CLEC Acronym TXT*** to Verizon and from Verizon to ***CLEC Acronym TXT***. Teleconex***CLEC Acronym TXT***’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex ***CLEC Acronym TXT*** shall engineer Two-Two- Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 CLEC Acronym TXT*** shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two- Way Interconnection Trunk group. ***CLEC Acronym TXT*** shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. ***CLEC Acronym TXT*** shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and ***CLEC Acronym TXT*** has not notified Verizon that it has corrected such blocking, Verizon may submit to ***CLEC Acronym TXT*** a Trunk Group Service Request directing ***CLEC Acronym TXT*** to remedy the blocking. Upon receipt of a Trunk Group Service Request, ***CLEC Acronym TXT*** will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. ***CLEC Acronym TXT*** will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, ***CLEC Acronym TXT*** will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event ***CLEC Acronym TXT*** fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may bill ***CLEC Acronym TXT*** for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and Teleconex***CLEC Acronym TXT***’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 CLEC Acronym TXT*** will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex ***CLEC Acronym TXT*** to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex ***CLEC Acronym TXT*** and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex ***CLEC Acronym TXT*** will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex***CLEC Acronym TXT***’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex***CLEC Acronym TXT***’s side of Teleconex’s***CLEC Acronym TXT***’s-IP, which charges shall be solely the financial responsibility of Teleconex***CLEC Acronym TXT***. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the Teleconex***CLEC Acronym TXT***-IP, ***CLEC Acronym TXT*** shall pay fifty percent (50%) of the Verizon non-IPrecurring charges; and, (b) for the portion of the facility on ***CLEC Acronym TXT***’s side of the ***CLEC Acronym TXT***-IP, ***CLEC Acronym TXT*** shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if ***CLEC Acronym TXT*** fails to provide ***CLEC Acronym TXT***- IPs in accordance with this Agreement, ***CLEC Acronym TXT*** will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex ***CLEC Acronym TXT*** establishes such IPs***CLEC Acronym TXT***-IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and MMG, MMG, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and MMG, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex MMG 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 CCS Centium Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Meet Point A (high usage) and Meet Point B (final) Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex MMG shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex MMG anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between MMG and Verizon. TeleconexMMG’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced.
2.4.8 Meet Point B 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; . Meet Point B Two-Way Local 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 Teleconex MMG shall engineer Two-Way Local Interconnection Trunks using national standardsTelcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV- 002275).
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 MMG shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. MMG shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. MMG shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. MMG will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, MMG will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event MMG fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or ▇▇▇▇ (and MMG shall pay) for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexMMG’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 MMG will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex MMG to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex MMG and the Verizon End Office.
2.4.18 When 3.1.1 Either Party may request a Fiber Meet arrangement by providing written notice thereof to the other Party; provided, however, that a Party may not make such a request if the Parties have not consistently been exchanging an amount of applicable traffic (as set forth in Section 3.1.3 below) equal to at least one (1) DS-3. Any such Fiber Meet arrangement shall be subject to the terms of this Agreement. In addition, the establishment of any Fiber Meet arrangement is expressly conditioned upon the Parties' mutually agreeing to the technical specifications and requirements for such Fiber Meet arrangement including, but not limited to, the location of the Fiber Meet points, routing, equipment (e.g., specifications of Add/Drop Multiplexers, number of strands of fiber, etc.), software, ordering, provisioning, maintenance, repair, testing, augment and on any other technical specifications or requirements necessary to implement Two-Way Local Interconnection Trunksthe Fiber Meet arrangement. For each Fiber Meet arrangement the Parties agree to implement, the Parties will work cooperatively complete and sign a Technical Specifications and Requirements document, the form of which is attached hereto as Exhibit A to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use Section 2.4.14 of the facility Interconnection Attachment Fiber Meet Arrangement Provisions. Each such document will be treated as shown confidential information.
3.1.2 The Parties agree to consider the possibility of using existing fiber cable with spare capacity, where available, to implement any such request for a Fiber Meet arrangement. If existing fiber cable with spare capacity is not available, the Parties agree to minimize the construction and deployment of fiber cable necessary for any Fiber Meet arrangement to which they agree. Except as otherwise agreed by the PPU. The PPU Parties, any and all Fiber Meet points established between the Parties shall extend no further than three (3) miles from an applicable Verizon Wire Center and Verizon shall not be applied required to calculate construct or deploy more than five hundred (500) feet of fiber cable for a Fiber Meet arrangement.
3.1.3 Except as otherwise agreed by the charges for Parties, any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges Fiber Meet arrangements established under this Agreement shall be solely the financial responsibility of Teleconex. Non-recurring charges used only for the facility transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA toll traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and Measured Internet Traffic, all in accordance with this Agreement. Operator services/directory assistance traffic, 911 traffic, and Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between MMG Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem, may be exchanged over Fiber Meet arrangements subject to applicable Verizon Tariff rates and charges. Except as otherwise agreed by the Parties, point-to-point (i.e., unswitched) access services and unbundled network elements shall not be provisioned on which or accessed through Fiber Meet arrangements. Notwithstanding any other provision of this Agreement or otherwise, other than the Two-Way Interconnection Trunks ride obligation to pay any applicable intercarrier compensation charges pursuant to the terms of this Agreement, neither Party shall have any obligation to pay the other Party any charges in connection with any Fiber Meet arrangements established under this Agreement.
3.1.4 MMG will include traffic to be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPsexchanged over Fiber Meet arrangements in its forecasts provided to Verizon under this Agreement.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and DSCI, prior DSCI shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex DSCI 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex DSCI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex DSCI anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from DSCI to Verizon and from Verizon to DSCI. TeleconexDSCI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex DSCI shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeLEC Networks SR- TSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and API, API, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and API, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex API 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex API shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex API anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between API and Verizon. TeleconexAPI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local 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 Teleconex API shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Ymax, Ymax, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Ymax, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Ymax 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 CCS Centium Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Ymax shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Ymax anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Ymax and Verizon. TeleconexYmax’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local 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 Teleconex ▇▇▇▇ shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 Ymax shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Ymax shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Ymax shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Ymax has not notified Verizon that it has corrected such blocking, Verizon may submit to Ymax a Trunk Group Service Request directing Ymax to remedy the blocking. Upon receipt of a Trunk Group Service Request, Ymax will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Ymax will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Ymax will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Ymax fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or bill (and Ymax shall pay) for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexYmax’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 Ymax will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex Ymax to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex Ymax and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Connectel, Connectel, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Connectel, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Connectel 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Connectel shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Connectel anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Connectel and Verizon. TeleconexConnectel’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex Connectel shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 Connectel shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Connectel shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Connectel shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Connectel has not notified Verizon that it has corrected such blocking, Verizon may submit to Connectel a Trunk Group Service Request directing Connectel to remedy the blocking. Upon receipt of a Trunk Group Service Request, Connectel will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Connectel will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Connectel will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Connectel fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may ▇▇▇▇ Connectel for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexConnectel’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 Connectel will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex Connectel to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex Connectel and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and CCI, CCI, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and CCI, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex CCI 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex CCI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex CCI anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between CCI and Verizon. TeleconexCCI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office TwoTw o-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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-. Two- Way Local 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 Teleconex CCI shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 CCI shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. CCI shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. CCI shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and CCI has not notified Verizon that it has corrected such blocking, Verizon may submit to CCI a Trunk Group Service Request directing CCI to remedy the blocking. Upon receipt of a Trunk Group Service Request, CCI will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. CCI will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, CCI will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event CCI fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may bill CCI for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexCCI’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 CCI will route its traffic to Verizon over the End Office and Tandem Two-Two- Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex CCI to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex CCI and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and SLT, SLT, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and SLT, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex SLT 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex SLT shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex SLT anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between SLT and Verizon. TeleconexSLT’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local 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 Teleconex SLT shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Talk America, Talk America, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Talk America, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Talk America 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Meet Point A (high usage) and Meet Point B (final) Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTrunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Talk America shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex Talk America anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Talk America and Verizon. TeleconexTalk America’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced.
2.4.8 Meet Point B 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; . Meet Point B Two-Way Local 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 Teleconex Talk America 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 Meet Point B Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 Talk America shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Talk America shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Talk America shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and Talk America has not notified Verizon that it has corrected such blocking, Verizon may submit to Talk America a Trunk Group Service Request directing Talk America to remedy the blocking. Upon receipt of a Trunk Group Service Request, Talk America will complete an ASR to establish or augment the Meet Point A Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Talk America will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Talk America will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Talk America fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or ▇▇▇▇ (and Talk America shall pay) for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexTalk America’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 Talk America will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex Talk America to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex Talk America and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Covista, Covista, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Covista, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Covista 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 CCS Centium Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Covista shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Covista anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Covista and Verizon. TeleconexCovista’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local 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 Teleconex Covista shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Ygnition, Ygnition, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Ygnition, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Ygnition 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Ygnition shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Ygnition anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Ygnition and Verizon. TeleconexYgnition’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 ▇.005 during the average time consistent busy hour; . Two-Way Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇- ▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Verizon and Teleconex Ygnition shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 Ygnition shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Ygnition shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Ygnition shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Ygnition has not notified Verizon that it has corrected such blocking, Verizon may submit to Ygnition a Trunk Group Service Request directing Ygnition to remedy the blocking. Upon receipt of a Trunk Group Service Request, Ygnition will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Ygnition will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Ygnition will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Ygnition fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or bill (and Ygnition shall pay) for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexYgnition’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 Ygnition will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex Ygnition to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex Ygnition and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Phone-Link 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 CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex Phone-Link is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a semi-annual basis, Teleconex Phone-Link shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Phone-Link anticipates that Verizon will need to provide during the ensuing two (2) year period. TeleconexPhone-Link’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local 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 Teleconex Phone-Link shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex Phone-Link shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex Phone-Link shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex Phone-Link shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex Phone-Link has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex Phone-Link a Trunk Group Service Request directing Teleconex Phone- Link to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex Phone-Link will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Daysbusiness days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the TeleconexPhone-Link’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex Phone-Link shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex Phone-Link will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex Phone- Link will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex Phone-Link will promptly augment all Tandem Two-Way LocalLocal Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Local Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Phone-Link will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group. In the event Phone-Link fails to submit an ASR for Two-Way Local Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ Phone-Link for the excess Local Interconnection Trunks at the applicable rates provided for in the Pricing Attachment.
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and TeleconexPhone- Link’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex Phone-Link will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-SR- TAP192, including but not limited to those standards requiring that a call from Teleconex Phone-Link to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex Phone-Link and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex Phone-Link will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexPhone-Link’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexPhone-Link’s side of Teleconex’sPhone-Link’s-IP, which charges shall be solely the financial responsibility of TeleconexPhone-Link. Non-Non- recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the TeleconexPhone-Link-IP, the non-recurring charges shall be divided equally Twobetween the Parties; and, (b) for the portion of the Trunks on Phone-Link’s side of the Phone-Link-IP, Phone-Link shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.18, if Phone-Link fails to provide IPs at Verizon’s Tandem or End Office(s) in accordance with this Agreement, Phone-Link will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two- Way Local Interconnection Trunk groups until Teleconex Phone-Link establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and API, API, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and API, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex API 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex API shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex API anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between API and Verizon. TeleconexAPI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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-. Two- Way Local 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 Teleconex API shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 API shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. API shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. API shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and API has not notified Verizon that it has corrected such blocking, Verizon may submit to API a Trunk Group Service Request directing API to remedy the blocking. Upon receipt of a Trunk Group Service Request, API will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. API will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, API will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event API fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may bill API for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexAPI’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 API will route its traffic to Verizon over the End Office and Tandem Two-Two- Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex API to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex API and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and VarTec, prior VarTec shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex VarTec 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office Meet Point A (high usage) and Tandem Local Meet Point B (final) Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex VarTec shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex VarTec anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from VarTec to Verizon and from Verizon to VarTec. TeleconexVarTec’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Meet Point B Two-Way Local 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; . Meet Point B Two-Way Local 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 Teleconex VarTec shall engineer Two-Way Local Interconnection Trunks using national standardsBOC Notes on the LEC Networks SR- TSV-002275.
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 VarTec shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. VarTec shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. VarTec shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and VarTec has not notified Verizon that it has corrected such blocking, Verizon may submit to VarTec a Trunk Group Service Request directing VarTec to remedy the blocking. Upon receipt of a Trunk Group Service Request, VarTec will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. VarTec will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, VarTec will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event VarTec fails to submit an ASR for Two- Way Interconnection Trunks in conformance with this section, Verizon may bill VarTec for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexVarTec’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 VarTec will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Interc onnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex VarTec to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex VarTec and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex VarTec will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexVarTec’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexVarTec’s side of Teleconex’sVarTec’s-IP, which charges shall be solely the financial responsibility of TeleconexVarTec. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the TeleconexVarTec-IP, VarTec shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on VarTec’s side of the VarTec-IP, VarTec shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if VarTec fails to provide VarTec-IPs in accordance with this Agreement, VarTec will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex VarTec establishes such VarTec- IPs.
Appears in 1 contract
Sources: Interconnection Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and PW, PW, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and PW, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex PW 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex PW shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex PW anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between PW and Verizon. TeleconexPW’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex PW shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 PW shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. PW shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. PW shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and PW has not notified Verizon that it has corrected such blocking, Verizon may submit to PW a Trunk Group Service Request directing PW to remedy the blocking. Upon receipt of a Trunk Group Service Request, PW will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. PW will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, PW will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event PW fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may bill PW for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexPW’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 PW will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex PW to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex PW and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and ▇▇▇, prior ▇▇▇ shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex IG2 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex IG2 shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex IG2 anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from IG2 to Verizon and from Verizon to IG2. TeleconexIG2’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex IG2 shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex ECSI 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 CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex ECSI is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a semi-annual basis, Teleconex ECSI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex ECSI anticipates that Verizon will need to provide during the ensuing two (2) year period. TeleconexECSI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇▇▇▇▇▇▇▇▇ -Wlikenson B.01 during the average time consistent busy hour. Verizon and Teleconex ECSI shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex ECSI shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex ECSI shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex ECSI shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex ECSI has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex ECSI a Trunk Group Service Request directing Teleconex ECSI to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex ECSI will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the TeleconexECSI’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex ECSI shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex ECSI will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex ECSI will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex ECSI will promptly augment all Tandem Two-Way LocalInterconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, ECSI will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group. In the event ECSI fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ ▇▇▇▇ for the excess Local Interconnection Trunks at the applicable rates provided for in the Pricing Attachment.
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and TeleconexECSI’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Reciprocal Compensation Traffic, IntraLATA Toll Traffic and Measured Internet Traffic.
2.4.17 Teleconex ECSI will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex ECSI to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex ECSI and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex ECSI will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexECSI’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexECSI’s side of Teleconex’sECSI’s-IP, which charges shall be solely the financial responsibility of TeleconexECSI. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the TeleconexECSI-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on ECSI ’s side of the ECSI-IP, ECSI shall be solely responsible for the non- recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.18, if ECSI fails to provide IPs at Verizon’s Tandem or End Office(s) in accordance with this Agreement, ECSI will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Local Interconnection Trunk groups until Teleconex ECSI establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Verizon Avenue, prior Verizon Avenue shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Verizon Avenue 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office Meet Point A (high usage) and Tandem Local Meet Point B (final) Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Verizon Avenue shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex Verizon Avenue anticipates that Verizon will need to provide during the ensuing two (2) year period. Teleconex’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 Two-Way Local 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.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local 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 Teleconex shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.two
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Equal Access, prior Equal Access shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Equal Access 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).. Where the Parties
2.4.2 2.4.3 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Equal Access shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Equal Access anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from Equal Access to Verizon and from Verizon to Equal Access. TeleconexEqual Access’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex Equal Access shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeLEC Networks SR- TSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Excel, prior Excel shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Excel 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Excel shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Excel anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from Excel to Verizon and from Verizon to Excel. TeleconexExcel’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex Excel shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 Excel shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Excel shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Excel shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Excel has not notified Verizon that it has corrected such blocking, Verizon may submit to Excel a Trunk Group Service Request directing Excel to remedy the blocking. Upon receipt of a Trunk Group Service Request, Excel will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Excel will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Excel will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Excel fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ Excel for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexExcel’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two-Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non-complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non-complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 Excel will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex Excel to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex Excel and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex Excel will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexExcel’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexExcel’s side of Teleconex’sExcel’s-IP, which charges shall be solely the financial responsibility of TeleconexExcel. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the TeleconexExcel-IP, Excel shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on Excel’s side of the Excel-IP, Excel shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if Excel fails to provide Excel-IPs in accordance with this Agreement, Excel will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex Excel establishes such Excel-IPs.
Appears in 1 contract
Sources: Telecommunications (Wave2Wave Communications, Inc.)
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Marathon, Marathon, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Marathon, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Marathon 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Marathon shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Marathon anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Marathon and Verizon. TeleconexMarathon’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex Marathon shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Talk Unlimited, prior Talk Unlimited shall order from Verizon, and Verizon shall provide, the Two- Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Talk Unlimited 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).interface
2.4.2 2.4.3 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Talk Unlimited shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Talk Unlimited anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from Talk Unlimited to Verizon and from Verizon to Talk Unlimited. TeleconexTalk Unlimited’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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-. Two- Way Local 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 Teleconex Talk Unlimited shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 Talk Unlimited shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Talk Unlimited shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Talk Unlimited shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Talk Unlimited has not notified Verizon that it has corrected such blocking, Verizon may submit to Talk Unlimited a Trunk Group Service Request directing Talk Unlimited to remedy the blocking. Upon receipt of a Trunk Group Service Request, Talk Unlimited will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Talk Unlimited will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Talk Unlimited will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Talk Unlimited fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ Talk Unlimited for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexTalk Unlimited’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 Talk Unlimited will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex Talk Unlimited to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.to
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex Talk Unlimited will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexTalk Unlimited’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexTalk Unlimited’s side of Teleconex’sTalk Unlimited’s-IP, which charges shall be solely the financial responsibility of TeleconexTalk Unlimited. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the TeleconexTalk Unlimited-IP, Talk Unlimited shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on Talk Unlimited’s side of the Talk Unlimited-IP, Talk Unlimited shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if Talk Unlimited fails to provide Talk Unlimited-IPs in accordance with this Agreement, Talk Unlimited will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex Talk Unlimited establishes such Talk Unlimited-IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Denali, Denali, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Denali, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Denali 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Denali shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Denali anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Denali and Verizon. TeleconexDenali’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End End-Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design design-blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour; . Two-Way Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design design-blocking objective of ▇▇▇▇ ▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Verizon and Teleconex Denali shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR-2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design design-blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Interim Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and ECI, ECI, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and ECI, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex ECI 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex ECI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex ECI anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between ECI and Verizon. TeleconexECI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex ECI shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and KDL, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex 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 CCS Centium Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex KDL shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex KDL anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between KDL and Verizon. TeleconexKDL’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local 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 Teleconex KDL shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 KDL shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. KDL shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. KDL shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and KDL has not notified Verizon that it has corrected such blocking, Verizon may submit to KDL a Trunk Group Service Request directing KDL to remedy the blocking. Upon receipt of a Trunk Group Service Request, KDL will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. KDL will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, KDL will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event KDL fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or ▇▇▇▇ (and KDL shall pay) for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexKDL’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 KDL will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex KDL to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex KDL and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and ATI, ATI, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and ATI, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex ATI 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex ATI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex ATI anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between ATI and Verizon. TeleconexATI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex ATI shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 ATI shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. ATI shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. ATI shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and ATI has not notified Verizon that it has corrected such blocking, Verizon may submit to ATI a Trunk Group Service Request directing ATI to remedy the blocking. Upon receipt of a Trunk Group Service Request, ATI will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. ATI will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, ATI will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event ATI fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may bill ATI for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexATI’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 ATI will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex ATI to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex ATI and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Ygnition, Ygnition, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Ygnition, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Ygnition 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Ygnition shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Ygnition anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Ygnition and Verizon. TeleconexYgnition’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local 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 Teleconex Ygnition shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Talk America, Talk America, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Talk America, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Talk America 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Talk America shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Talk America anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Talk America and Verizon. TeleconexTalk America’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local 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 Teleconex Talk America shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Global Link, Global Link, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Global Link, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Global Link 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 CCS Centium Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Global Link shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Global Link anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Global Link and Verizon. TeleconexGlobal Link’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Verizon and Teleconex Global Link shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and D-Max, D-Max, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and D-Max, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex D-Max 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex D-Max shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex D-Max anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between D-Max and Verizon. TeleconexD-Max’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local 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 Teleconex D-Max shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Pac-West, Pac-West shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon's applicable Tariffs. Upon the Parties undertaking a Major Project, where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Pac-West 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point POI. For purposes of this Section 2.4.2, a "Major Project" is a project that requires the coordination and execution of multiple orders or related activities between and among Verizon and Pac-West work groups including, but not limited to, the initial establishment of Interconnection (POI).
2.4.2 or Access Toll Connecting Trunk Groups between a Verizon switch and a Pac-West switch, NXX code moves, rehomes, facility grooming, network rearrangements, a conversion from One Way Interconnection Trunks to Two-Way Local Interconnection Trunks, and installation of a new switch. Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a semi-annual basis, Teleconex Pac-West shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Pac-West anticipates that Verizon will need to provide during the ensuing two (2) year period. Teleconex’s Pac-West's trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 . The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 . Two-Way Local 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.6 available. With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 . Two-Way Local Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of ▇N▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour; . Two-Way Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of N▇▇▇▇ -▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Verizon and Teleconex Pac-West shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex BOC Notes on the LEC Networks SR-TSV-002275. 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 (3) consecutive calendar traffic study months. After a Two-Way Interconnection Trunk Group has been established, Pac-West shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex Pac-West shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s 's effective standard intervals or negotiated intervals, as appropriate. Teleconex Provisioning intervals offered by Verizon to Pac-West for Two-Way Interconnection Trunks shall be no longer than the provisioning intervals offered by Verizon to other CLECs. Pac-West shall complete ASRs in accordance with Ordering and Billing Forum OBF Guidelines as in effect from time to time.
2.4.9 Verizon . Each Party may (but shall not be obligated to) monitor Two-Way Local Interconnection Groups using service results for the applicable design-design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Tandem Two-Way Local Interconnection Trunk group and Teleconex Pac-West has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex Pac-West a Trunk Group Service Request directing Teleconex Pac-West to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex Pac-West will complete an ASR to augment the Two-Way Local Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem . If Pac-West observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Twogroup, Pac-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex West shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem augment the Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentagesGroup. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex Pac-West will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Pac-West will exceed its design blocking objective promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (B.005 or B.01, as applicable60%) for three each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Pac-West fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may b▇▇▇ Pac-West for the excess Interconnection Trunks at the applicable rates provided for in the Pricing Attachment, provided that Verizon sends Pac-West written notice, in the form of a Trunk Group Service Request, sixty (360) consecutive calendar traffic study months.
2.4.14 days prior to sending a b▇▇▇ and such notice identifies the underutilized trunks. Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and Teleconex’s Pac-West's network, Verizon’s 's performance on in connection with these Two-Way Local Interconnection Trunk groups (except for maintenance intervals and missed installation appointments) shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 . Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex . Each Party will route its traffic to Verizon the other Party over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex Pac-West to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex Pac-West and the Verizon End Office.
2.4.18 . When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges be responsible for the facility costs on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s its side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPsPOI.
Appears in 1 contract
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and ECI, ECI, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and ECI, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex ECI 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 CCS Centium Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex ECI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex ECI anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between ECI and Verizon. TeleconexECI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Verizon and Teleconex ECI shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and ECI, ECI, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and ECI, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex ECI 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex ECI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex ECI anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between ECI and Verizon. TeleconexECI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Verizon and Teleconex ECI shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex NOS 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 CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex NOS is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a semi-annual basis, Teleconex NOS shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex NOS anticipates that Verizon will need to provide during the ensuing two (2) year period. TeleconexNOS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local 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 Teleconex NOS shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex NOS shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex NOS shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex NOS shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex NOS has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex NOS a Trunk Group Service Request directing Teleconex NOS to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex NOS will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the TeleconexNOS’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex NOS shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex NOS will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex NOS will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex NOS will promptly augment all Tandem Two-Way LocalLocal Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Local Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, NOS will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group. In the event NOS fails to submit an ASR for Two-Way Local Interconnection Trunks in conformance with this section, Verizon may bill NOS for the excess Local Interconnection Trunks at the applicable rates provided for in the Pricing Attachment.
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and TeleconexNOS’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex NOS will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-SR- TAP192, including but not limited to those standards requiring that a call from Teleconex NOS to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex NOS and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex NOS will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexNOS’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexNOS’s side of Teleconex’sNOS’s-IP, which charges shall be solely the financial responsibility of TeleconexNOS. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the TeleconexNOS-IP, the non-non- recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.between the Parties; and,
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and NOW Communications, prior Inc., NOW Communications, Inc. shall order from
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex NOW Communications, Inc. 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Two- Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex NOW Communications, Inc. shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Two- Way Local Interconnection Trunks that Teleconex NOW Communications, Inc. anticipates that Verizon will need to provide during the ensuing two (2) year period. Teleconexperiod to carry traffic from NOW Communications, Inc. to Verizon and from Verizon to NOW Communications, Inc.. NOW Communications, Inc.’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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-. Two- Way Local 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 Teleconex NOW Communications, Inc. shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeLEC Networks SR- TSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.exceed
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and NTC, prior NTC shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex NTC 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex NTC shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex NTC anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from NTC to Verizon and from Verizon to NTC. TeleconexNTC’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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-. Two- Way Local 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 Teleconex NTC shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 NTC shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. NTC shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. NTC shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and NTC has not notified Verizon that it has corrected such blocking, Verizon may submit to NTC a Trunk Group Service Request directing NTC to remedy the blocking. Upon receipt of a Trunk Group Service Request, NTC will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. NTC will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, NTC will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event NTC fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ NTC for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexNTC’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI.
2.4.16 Notwithstanding any other provision of , provided that, if a Party has failed to comply with this Agreement, Two-Agreement with regard to Two- Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each other Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use may upon three (3) months prior written notice and without mutual agreement of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of non- complying Party, withdraw its traffic from a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally TwoTrunk group and install One-Way Local Interconnection Trunk groups until Teleconex establishes such IPsTrunks to the non- complying Party’s relevant POI.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex BTLLC 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 CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex BTLLC is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a semi-annual basis, Teleconex BTLLC shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex BTLLC anticipates that Verizon will need to provide during the ensuing two (2) year period. TeleconexBTLLC’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as set out on Verizon’s website and in effect at that time.
2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local 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 Teleconex BTLLC shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex BTLLC shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex BTLLC shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex BTLLC shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timetime as well as other applicable Verizon provided documentation.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex BTLLC has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex BTLLC a Trunk Group Service Request directing Teleconex BTLLC to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex BTLLC will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the TeleconexBTLLC’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex BTLLC shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex BTLLC will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex BTLLC will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex BTLLC will promptly augment all Tandem Two-Way LocalLocal Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Local Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, BTLLC will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group. In the event BTLLC fails to submit an ASR for Two-Way Local Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ BTLLC for the excess Local Interconnection Trunks at the applicable rates provided for in the Pricing Attachment; provided that Verizon shall not charge BTC for the excess Local Interconnection Trunks pursuant to this sentence if the number of trunks in the underutilized trunk group does not exceed the number of trunks in one DS-1 (i.e., 24 DS0 trunks).
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups (except for maintenance and installation intervals and missed installation appointments) shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Reciprocal Compensation Traffic, IntraLATA Toll Traffic and Measured Internet Traffic.
2.4.17 Teleconex BTLLC will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-SR- TAP192, including but not limited to those standards requiring that a call from Teleconex BTLLC to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex BTLLC and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.of
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Crocker, Crocker, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and ▇▇▇▇▇▇▇, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex ▇▇▇▇▇▇▇ 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Meet Point A (high usage) and Meet Point B (final) Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex ▇▇▇▇▇▇▇ shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex ▇▇▇▇▇▇▇ anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between ▇▇▇▇▇▇▇ and Verizon. Teleconex’s ▇▇▇▇▇▇▇’▇ trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Meet Point B Two-Way Local 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; . Meet Point B Two-Way Local 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 Teleconex ▇▇▇▇▇▇▇ shall engineer Two-Way Local Interconnection Trunks using national standardsBOC Notes on the LEC Networks SR- TSV-002275.
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 ▇▇▇▇▇▇▇ shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. ▇▇▇▇▇▇▇ shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. ▇▇▇▇▇▇▇ shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and ▇▇▇▇▇▇▇ has not notified Verizon that it has corrected such blocking, Verizon may submit to ▇▇▇▇▇▇▇ a Trunk Group Service Request directing ▇▇▇▇▇▇▇ to remedy the blocking. Upon receipt of a Trunk Group Service Request, ▇▇▇▇▇▇▇ will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. ▇▇▇▇▇▇▇ will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, ▇▇▇▇▇▇▇ will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event ▇▇▇▇▇▇▇ fails to submit an ASR for Two- Way Interconnection Trunks in conformance with this Section, Verizon may ▇▇▇▇ ▇▇▇▇▇▇▇ for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and Teleconex’s ▇▇▇▇▇▇▇’▇ network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 ▇▇▇▇▇▇▇ will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192SR- TAP-000191, including but not limited to those standards requiring that a call from Teleconex ▇▇▇▇▇▇▇ to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex ▇▇▇▇▇▇▇ and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Princeton, Princeton, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Princeton, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Princeton 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Princeton shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Princeton anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Princeton and Verizon. TeleconexPrinceton’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local 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 Teleconex Princeton shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Airespring, Airespring, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Airespring, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex ▇▇▇▇▇▇▇▇▇▇ 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Meet Point A (high usage) and Meet Point B (final) Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Airespring shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex Airespring anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Airespring and Verizon. TeleconexAirespring’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced.
2.4.8 Meet Point B 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; . Meet Point B Two-Way Local 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 Teleconex ▇▇▇▇▇▇▇▇▇▇ shall engineer Two-Way Local Interconnection Trunks using national standardsTelcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV- 002275).
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 Airespring shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Airespring shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Airespring shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and Airespring has not notified Verizon that it has corrected such blocking, Verizon may submit to Airespring a Trunk Group Service Request directing Airespring to remedy the blocking. Upon receipt of a Trunk Group Service Request, ▇▇▇▇▇▇▇▇▇▇ will complete an ASR to establish or augment the Meet Point A Two- Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Airespring will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, ▇▇▇▇▇▇▇▇▇▇ will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Airespring fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or bill (and Airespring shall pay) for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexAirespring’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 Airespring will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192SR- TAP-000191, including but not limited to those standards requiring that a call from Teleconex Airespring to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex Airespring and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Interconnection Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and ICG, ICG shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks, and the Entrance Facility on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Upon the parties undertaking a Major Project, where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex ICG shall meet meet, telephonically or in person, with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party forecasted originating CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). For purposes of this Section 2.4.2, a “Major Project” is a project that requires the coordination and execution of multiple orders or related activities between and among Verizon and ICG work groups including, but not limited to, the initial establishment of Interconnection or Access Toll Connecting Trunk groups between a Verizon switch and an ICG switch, NXX code moves, re-homes, facility grooming, network rearrangements, a conversion from One Way Interconnection Trunks to Two- Way Interconnection Trunks, and installation of a new switch.
2.4.2 2.4.3 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex ICG is collocated in a Verizon Wire Center, the POI shall may be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex ICG shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex ICG anticipates that Verizon will need to provide during the ensuing two (2) year period. TeleconexICG’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as provided to ICG and in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 2.4.8 Verizon and ICG shall engineer Two-Way Local Interconnection Trunks using national standards and measurement methodologies. 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; B.005. Two-Way Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇▇▇▇▇▇▇▇▇ B.01 during the B.01. In performing trunk blockage measurements, Verizon will use an average time consistent busy hourhour methodology, as set out in Telcordia publication SR-TAP-000191. If ICG elects to perform trunk blockage measurements using a method of measurement (for instance, a method that uses a peak busy hour measurement) that differs from that used by Verizon and Teleconex shall engineer ICG’s method of measurement indicates a need for a different number of Two-Way Local Interconnection Trunks using national standardsthan the method of measurement used by Verizon, the Parties shall negotiate in good faith to determine the number of Two-Way Interconnection Trunks that should be used. If the Parties are unable to agree upon the number of Two-Way Interconnection Trunks that should be used, either Party may submit the matter to dispute resolution pursuant to Section 14 of the General Terms and Conditions.
2.4.8 Teleconex 2.4.9 After a Two-Way Interconnection Trunk group has been established, ICG shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each such Two-Way Local Interconnection Trunk group. Teleconex ICG shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex The provisioning intervals offered by Verizon to ICG for orders for 240 or fewer DS0 Two-Way Interconnection Trunks shall be no longer than the provisioning intervals offered by Verizon to other similarly situated CLECs for orders for 240 or fewer DS0 Two-Way Interconnection Trunks. Except as otherwise provided in an applicable Verizon Tariff, the provisioning intervals offered by Verizon to ICG for orders for 240 or more DS0 Two-Way Interconnection Trunks shall be subject to negotiation by the Parties. ICG orders for Two-Way Interconnection Trunks shall be subject to Section 2.2.5 above and other applicable provisions of this Agreement and applicable Verizon Tariffs. ICG shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon 2.4.10 Each Party may monitor Two-Way Local Interconnection Trunk Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex ICG has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex ICG a Trunk Group Service Request directing Teleconex ICG to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex ICG will complete an ASR to augment the Two-Way Local Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem . If ICG observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any timegroup, Teleconex ICG shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem augment the Two-Way Local Interconnection Trunk group does not exceed the 240 trunk levelGroup.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex ICG will promptly augment all Tandem Two-Way LocalInterconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, ICG will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group. In the event ICG fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may bill ICG for the excess Interconnection Trunks at the applicable rates provided for in the Pricing Attachment, provided that Verizon sends ICG written notice, in the form of a Trunk Group Service Request, sixty (60) days prior to sending a bill and such notice identifies the underutilized trunk groups.
2.4.13 2.4.12 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.13 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and TeleconexICG’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups (except for maintenance intervals and missed installation appointments) shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 Each Party will route its traffic to Verizon the other Party over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex either Party to a Verizon the other Party's End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex ICG and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex ICG will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexICG’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexICG’s side of Teleconex’sICG’s-IP, which charges shall be solely the financial responsibility of TeleconexICG. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the TeleconexICG-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on ICG’s side of the ICG-IP, ICG shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if ICG fails to provide IPs in accordance with this Agreement, ICG will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Local Interconnection Trunk groups until Teleconex ICG establishes such IPs.
Appears in 1 contract
Sources: Adoption Under FCC Merger Conditions
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Intrado, prior Intrado shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Intrado 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Intrado shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Intrado anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from Intrado to Verizon and from Verizon to Intrado. TeleconexIntrado’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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-. Two- Way Local 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 Teleconex Intrado shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 Intrado shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Intrado shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Intrado shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Intrado has not notified Verizon that it has corrected such blocking, Verizon may submit to Intrado a Trunk Group Service Request directing Intrado to remedy the blocking. Upon receipt of a Trunk Group Service Request, Intrado will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Intrado will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Intrado will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Intrado fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ ▇▇▇▇▇▇▇ for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexIntrado’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two-Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non-complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non-complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 Intrado will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex Intrado to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex Intrado and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex Intrado will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexIntrado’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexIntrado’s side of Teleconex’sIntrado’s-IP, which charges shall be solely the financial responsibility of TeleconexIntrado. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the TeleconexIntrado-IP, Intrado shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on Intrado’s side of the Intrado-IP, Intrado shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if Intrado fails to provide Intrado-IPs in accordance with this Agreement, Intrado will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex Intrado establishes such Intrado- IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and CBB, CBB, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and CBB, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex CBB 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 CCS Centium Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Meet Point A (high usage) and Meet Point B (final) Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex CBB shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex CBB anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between CBB and Verizon. TeleconexCBB’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced.
2.4.8 Meet Point B 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; . Meet Point B Two-Way Local 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 Teleconex CBB shall engineer Two-Way Local Interconnection Trunks using national standardsTelcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV- 002275).
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 CBB shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. CBB shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. CBB shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. CBB will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, CBB will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event CBB fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or ▇▇▇▇ (and CBB shall pay) for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexCBB’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 CBB will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex CBB to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex CBB and the Verizon End Office.
2.4.18 When 3.1.1 Either Party may request a Fiber Meet arrangement by providing written notice thereof to the other Party; provided, however, that a Party may not make such a request if the Parties have not consistently been exchanging an amount of applicable traffic (as set forth in Section 3.1.3 below) equal to at least one (1) DS-3. Any such Fiber Meet arrangement shall be subject to the terms of this Agreement. In addition, the establishment of any Fiber Meet arrangement is expressly conditioned upon the Parties' mutually agreeing to the technical specifications and requirements for such Fiber Meet arrangement including, but not limited to, the location of the Fiber Meet points, routing, equipment (e.g., specifications of Add/Drop Multiplexers, number of strands of fiber, etc.), software, ordering, provisioning, maintenance, repair, testing, augment and on any other technical specifications or requirements necessary to implement Two-Way Local Interconnection Trunksthe Fiber Meet arrangement. For each Fiber Meet arrangement the Parties agree to implement, the Parties will work cooperatively complete and sign a Technical Specifications and Requirements document, the form of which is attached hereto as Exhibit A to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use Section 2.4.14 of the facility Interconnection Attachment Fiber Meet Arrangement Provisions. Each such document will be treated as shown confidential information.
3.1.2 The Parties agree to consider the possibility of using existing fiber cable with spare capacity, where available, to implement any such request for a Fiber Meet arrangement. If existing fiber cable with spare capacity is not available, the Parties agree to minimize the construction and deployment of fiber cable necessary for any Fiber Meet arrangement to which they agree. Except as otherwise agreed by the PPU. The PPU Parties, any and all Fiber Meet points established between the Parties shall extend no further than three (3) miles from an applicable Verizon Wire Center and Verizon shall not be applied required to calculate construct or deploy more than five hundred (500) feet of fiber cable for a Fiber Meet arrangement.
3.1.3 Except as otherwise agreed by the charges for Parties, any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges Fiber Meet arrangements established under this Agreement shall be solely the financial responsibility of Teleconex. Non-recurring charges used only for the facility transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA toll traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and Measured Internet Traffic, all in accordance with this Agreement. Operator services/directory assistance traffic, 911 traffic, and Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between CBB Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem, may be exchanged over Fiber Meet arrangements subject to applicable Verizon Tariff rates and charges. Except as otherwise agreed by the Parties, point-to-point (i.e., unswitched) access services and unbundled network elements shall not be provisioned on which or accessed through Fiber Meet arrangements. Notwithstanding any other provision of this Agreement or otherwise, other than the Two-Way Interconnection Trunks ride obligation to pay any applicable intercarrier compensation charges pursuant to the terms of this Agreement, neither Party shall have any obligation to pay the other Party any charges in connection with any Fiber Meet arrangements established under this Agreement.
3.1.4 CBB will include traffic to be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPsexchanged over Fiber Meet arrangements in its forecasts provided to Verizon under this Agreement.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and DMJ, prior DMJ shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex DMJ 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex DMJ shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex DMJ anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from DMJ to Verizon and from Verizon to DMJ. TeleconexDMJ’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex DMJ shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and PNG, PNG, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and PNG, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex PNG 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex PNG shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex PNG anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between PNG and Verizon. TeleconexPNG’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex PNG shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and ▇▇▇▇ Telecom, prior ▇▇▇▇ Telecom shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex ▇▇▇▇ Telecom 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex ▇▇▇▇ Telecom shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex ▇▇▇▇ Telecom anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from ▇▇▇▇ Telecom to Verizon and from Verizon to ▇▇▇▇ Telecom. Teleconex▇▇▇▇ Telecom’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex ▇▇▇▇ Telecom shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeLEC Networks SR- TSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 ▇▇▇▇ Telecom shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. ▇▇▇▇ Telecom shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. ▇▇▇▇ Telecom shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and ▇▇▇▇ Telecom has not notified Verizon that it has corrected such blocking, Verizon may submit to ▇▇▇▇ Telecom a Trunk Group Service Request directing ▇▇▇▇ Telecom to remedy the blocking. Upon receipt of a Trunk Group Service Request, ▇▇▇▇ Telecom will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. ▇▇▇▇ Telecom will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, ▇▇▇▇ Telecom will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event ▇▇▇▇ Telecom fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ ▇▇▇▇ Telecom for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and Teleconex▇▇▇▇ Telecom’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 ▇▇▇▇ Telecom will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex ▇▇▇▇ Telecom to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex ▇▇▇▇ Telecom and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex ▇▇▇▇ Telecom will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex▇▇▇▇ Telecom’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex▇▇▇▇ Telecom’s side of Teleconex’s▇▇▇▇ Telecom’s-IP, which charges shall be solely the financial responsibility of Teleconex▇▇▇▇ Telecom. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the Teleconex▇▇▇▇ Telecom-IP, ▇▇▇▇ Telecom shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on ▇▇▇▇ Telecom’s side of the ▇▇▇▇ Telecom-IP, ▇▇▇▇ Telecom shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if ▇▇▇▇ Telecom fails to provide ▇▇▇▇ Telecom-IPs in accordance with this Agreement, ▇▇▇▇ Telecom will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex ▇▇▇▇ Telecom establishes such ▇▇▇▇ Telecom-IPs.
Appears in 1 contract
Sources: Interconnection Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Rhythms 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 CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex Rhythms is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a semi-annual basis, Teleconex Rhythms shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Rhythms anticipates that Verizon will need to provide during the ensuing two (2) year period. Teleconex’s Rhythms' trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local 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 Teleconex Rhythms shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex Rhythms shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex Rhythms shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex Rhythms shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Two- Way Local Interconnection Trunk group and Teleconex Rhythms has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex Rhythms a Trunk Group Service Request directing Teleconex Rhythms to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex Rhythms will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s Rhythms' POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex Rhythms shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex Rhythms will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex Rhythms will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex Rhythms will promptly augment all Tandem Two-Way LocalInterconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Rhythms will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group. In the event Rhythms fails to submit an ASR for Two- Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ Rhythms for the excess Local Interconnection Trunks at the applicable rates provided for in the Pricing Attachment.
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s Rhythms' network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-to- carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, Reciprocal Compensation Traffic IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex Rhythms will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-SR- TAP192, including but not limited to those standards requiring that a call from Teleconex Rhythms to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex Rhythms and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex Rhythms will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s Rhythms' percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s Rhythms' side of Teleconex’s-IPRhythms'-IP, which charges shall be solely the financial responsibility of TeleconexRhythms. Non-Non- recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the TeleconexRhythms-IP, the non-non- recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.between the Parties; and,
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Velocity 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 CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex Velocity is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a semi-annual basis, Teleconex Velocity shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Velocity anticipates that Verizon will need to provide during the ensuing two (2) year period. TeleconexVelocity’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local 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 Teleconex Velocity shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex Velocity shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex Velocity shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex Velocity shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex Velocity has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex Velocity a Trunk Group Service Request directing Teleconex Velocity to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex Velocity will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the TeleconexVelocity’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex Velocity shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex Velocity will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex Velocity will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex Velocity will promptly augment all Tandem Two-Way LocalLocal Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Local Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Velocity will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group. In the event Velocity fails to submit an ASR for Two-Way Local Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ Velocity for the excess Local Interconnection Trunks at the applicable rates provided for in the Pricing Attachment.
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and TeleconexVelocity’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex Velocity will route its traffic to Verizon over the End Office and Tandem Tandem] Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex Velocity to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex Velocity and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex Velocity will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexVelocity’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexVelocity’s side of Teleconex’sVelocity’s-IP, which charges shall be solely the financial responsibility of TeleconexVelocity. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the TeleconexVelocity-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on Velocity’s side of the Velocity-IP, Velocity shall be solely responsible for the non- recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.18, if Velocity fails to provide IPs at Verizon’s Tandem or End Office(s) in accordance with this Agreement, Velocity will be responsible for one hundred percent (100%) of all recurring and non- recurring charges associated with Two-Way Local Interconnection Trunk groups until Teleconex Velocity establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and New Access, prior New Access shall order from Verizon, and Verizon shall provide, the Two- Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex New Access 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).interface
2.4.2 2.4.3 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex New Access shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex New Access anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from New Access to Verizon and from Verizon to New Access. TeleconexNew Access’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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 Local 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 Teleconex New Access shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and ECI, ECI, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and ECI, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex ECI 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Meet Point A (high usage) and Meet Point B (final) Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex ECI shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex ECI anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between ECI and Verizon. TeleconexECI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Meet Point B Two-Way Local 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; . Meet Point B Two-Way Local 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 Teleconex ECI shall engineer Two-Way Local Interconnection Trunks using national standardsBOC Notes on the LEC Networks SR- TSV-002275.
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 ECI shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. ECI shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. ECI shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and ECI has not notified Verizon that it has corrected such blocking, Verizon may submit to ECI a Trunk Group Service Request directing ECI to remedy the blocking. Upon receipt of a Trunk Group Service Request, ECI will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. ECI will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and TeleconexECI’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 ECI will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex ECI to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex ECI and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Buckeye, prior Buckeye shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Buckeye 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Buckeye shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Buckeye anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from Buckeye to Verizon and from Verizon to Buckeye. TeleconexBuckeye’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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-. Two- Way Local 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 Teleconex Buckeye shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 Buckeye shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Buckeye shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Buckeye shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Buckeye has not notified Verizon that it has corrected such blocking, Verizon may submit to Buckeye a Trunk Group Service Request directing Buckeye to remedy the blocking. Upon receipt of a Trunk Group Service Request, Buckeye will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Buckeye will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Buckeye will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Buckeye fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ Buckeye for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexBuckeye’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 Buckeye will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex Buckeye to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex Buckeye and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex Buckeye will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Way Interconnection Trunks ride equal to TeleconexBuckeye’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexBuckeye’s side of Teleconex’sBuckeye’s-IP, which charges shall be solely the financial responsibility of TeleconexBuckeye. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the TeleconexBuckeye-IP, Buckeye shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on Buckeye’s side of the Buckeye- IP, Buckeye shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if Buckeye fails to provide Buckeye-IPs in accordance with this Agreement, Buckeye will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex Buckeye establishes such Buckeye-IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where 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 Parties have agreed to use Two Way Local future, so long as Verizon can measure usage on such Interconnection Trunks, prior subject to ordering any Two-Way Local Interconnection Trunks from Verizonthe terms set forth below and the other terms of this Agreement.
(a) Except to the extent that AWS may have already done so, Teleconex shall meet with Verizon to conduct a joint planning meeting not later than sixty (“Joint Planning Meeting”). At that Joint Planning Meeting60) days after the Effective Date of this Agreement, each Party AWS shall provide to the other Party originating CCS (Hundred Call Second) information, and the Parties shall mutually agree Verizon forecast information on the appropriate initial number of Twohigh usage and final two-Way End Office and Tandem Local way Interconnection Trunks and the interface specifications at the Point of Interconnection (POI)Trunks.
2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a (b) At least semi-annual basisannually, Teleconex AWS shall submit a good faith forecast to Verizon of including the number of End Office high usage and Tandem Twofinal two-Way Local way Interconnection Trunks that Teleconex AWS anticipates that Verizon it will need to provide require during the ensuing two (2) year period. Teleconex’s Such trunk forecasts shall conform to the Verizon CLEC trunk forecasting industry standard guidelines as in effect at that from time to time.
2.4.4 (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 on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need (e.g., trunk usage data, trunk overflow (blocking) data).
(d) AWS shall be responsible for new trunk groups and to plan any necessary changes in determining the number of Twotwo-Way Local Interconnection Trunks.
2.4.5 Two-Way Local way Interconnection Trunks required. Accordingly, AWS shall have SS7 Common Channel Signaling. The Parties agree submit ASRs, from time to utilize B8ZS and Extended Super Frame (ESF) DS1 facilitiestime, where available.
2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local 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 Teleconex shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Twotwo-Way Local way Interconnection Trunks that it is ordering, to be installed and include the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriateby which AWS wishes to have such two-way Interconnection Trunks installed. Teleconex AWS shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit (e) The Parties shall use an economic ccs equal to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days). Further general information regarding trunking may be found in Telcordia reference SR-TAP-000191.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. (f) In the event that the traffic volume between any Tandem Two-Way Local Interconnection Trunk group two (2) Central Office Switches at any time exceeds the 240 trunk level at any timecentum call second (“CCS”) busy hour equivalent of one (1) DS-1, Teleconex shall promptly submit an ASR to Verizon to AWS will establish new or additional End Office Trunk groups to insure that such Tandem Twotwo-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local way Interconnection Trunk groups that reach (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 seventy less than sixty percent (7060%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study 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.
2.4.14 Because (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 timing and sizing of the Twotwo-Way Local way Interconnection Trunks between its network and Teleconex’s networkthe network of AWS, Verizon’s performance on these Two-Way Local Interconnection Trunk groups Trunks shall not be subject to excluded from any performance measurements and remedies under this Agreement, andrelated provisions that Verizon implements, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or planfor unexcused missed installation appointments and maintenance service intervals.
2.4.15 Upon three (3k) months prior written notice and Maintenance service intervals for two-way Interconnection Trunks provided by Verizon to AWS shall be in parity with the mutual agreement of the Parties, either Party may withdraw its traffic from a Twoservice intervals for two-Way Local Interconnection Trunk group and install One-Way Local way Interconnection Trunks that Verizon provides to other telecommunications carriers in New Hampshire.
(l) If two-way Interconnection Trunks are provisioned using a DS-3 interface facility, AWS shall order the multiplexed DS-3 facilities to the applicable POI.
2.4.16 Notwithstanding any other provision of this AgreementVerizon Central Office that is designated in the NECA 4 Tariff as an intermediate hub location, Twounless otherwise agreed to in writing by Verizon. The specific NECA 4 intermediate hub location to be used for two-Way Local 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 carry Local Traffic, IntraLATA Toll Traffic and Internet InterLATA Toll Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two. Type 2B two-Way Local way Interconnection Trunks in accordance with SRmay 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-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local way Interconnection Trunks: 911/E911 traffic, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factordirectory assistance traffic, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IPoperator services traffic, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPsinformation services traffic and choke trunk traffic.
Appears in 1 contract
Sources: Interconnection Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex FRCI 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 CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex FRCI is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a semi-annual basis, Teleconex FRCI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex FRCI anticipates that Verizon will need to provide during the ensuing two (2) year period. TeleconexFRCI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇▇▇▇▇▇▇▇▇ -Wlikenson B.01 during the average time consistent busy hour. Verizon and Teleconex FRCI shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex FRCI shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex FRCI shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex FRCI shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex FRCI has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex FRCI a Trunk Group Service Request directing Teleconex FRCI to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex FRCI will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the TeleconexFRCI’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex FRCI shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex FRCI will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex FRCI will calculate utilization percentages by using a traffic data dat a analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex FRCI will promptly augment all Tandem Two-Way LocalInterconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, FRCI will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group. In the event FRCI fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ FRCI for the excess Local Interconnection Trunks at the applicable rates provided for in the Pricing Attachment.
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and TeleconexFRCI’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Reciprocal Compensation Traffic, IntraLATA Toll Traffic and Measured Internet Traffic.
2.4.17 Teleconex FRCI will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex FRCI to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex FRCI and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex FRCI will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexFRCI’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexFRCI’s side of Teleconex’sFRCI’s-IP, which charges shall be solely the financial responsibility of TeleconexFRCI. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the TeleconexFRCI-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on FRCI ’s side of the FRCI-IP, FRCI shall be solely responsible for the non- recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.18, if FRCI fails to provide IPs at Verizon’s Tandem or End Office(s) in accordance with this Agreement, FRCI will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Local Interconnection Trunk groups until Teleconex FRCI establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Ymax, Ymax, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Ymax, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Ymax 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 CCS Centium Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Ymax shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Ymax anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Ymax and Verizon. TeleconexYmax’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Verizon and Teleconex ▇▇▇▇ shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Telecommunications
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and OTT, OTT, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and ▇▇▇, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex ▇▇▇ 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Meet Point A (high usage) and Meet Point B (final) Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex ▇▇▇ shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks that Teleconex ▇▇▇ anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between ▇▇▇ and Verizon. Teleconex’s ▇▇▇’▇ trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced.
2.4.8 Meet Point B 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; . Meet Point B Two-Way Local 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 Teleconex ▇▇▇ shall engineer Two-Way Local Interconnection Trunks using national standardsTelcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV- 002275).
2.4.8 Teleconex shall determine and order the number of 2.4.9 The performance standard for Meet Point B Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 ▇▇▇ shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. ▇▇▇ shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. ▇▇▇ shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and ▇▇▇ has not notified Verizon that it has corrected such blocking, Verizon may submit to ▇▇▇ a Trunk Group Service Request directing ▇▇▇ to remedy the blocking. Upon receipt of a Trunk Group Service Request, ▇▇▇ will complete an ASR to establish or augment the Meet Point A Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. ▇▇▇ will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, ▇▇▇ will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event ▇▇▇ fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or ▇▇▇▇ (and ▇▇▇ shall pay) for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the Two-how many Two- Way Local Interconnection Trunks are established between its network and Teleconex’s ▇▇▇’▇ network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 ▇▇▇ will route its traffic to Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex ▇▇▇ to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex ▇▇▇ and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and TQCI, TQCI, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and TQCI, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex TQCI 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex TQCI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex TQCI anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between TQCI and Verizon. TeleconexTQCI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local 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 Teleconex TQCI shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Telecommunications Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Princeton, Princeton, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Princeton, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Princeton 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Princeton shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Princeton anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Princeton and Verizon. TeleconexPrinceton’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Verizon and Teleconex Princeton shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Advent, Advent, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Advent, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex Advent 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Advent shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Advent anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between Advent and Verizon. TeleconexAdvent’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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-. Two- Way Local 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 Teleconex Advent shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 Advent shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Advent shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Advent shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Advent has not notified Verizon that it has corrected such blocking, Verizon may submit to Advent a Trunk Group Service Request directing Advent to remedy the blocking. Upon receipt of a Trunk Group Service Request, Advent will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two- Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Advent will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Advent will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Advent fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may ▇▇▇▇ Advent for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexAdvent’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 Advent will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex Advent to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex Advent and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Camarato, Camarato, 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and ▇▇▇▇▇▇▇▇, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex ▇▇▇▇▇▇▇▇ 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex ▇▇▇▇▇▇▇▇ shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex ▇▇▇▇▇▇▇▇ anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between ▇▇▇▇▇▇▇▇ and Verizon. Teleconex’s ▇▇▇▇▇▇▇▇’▇ trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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-. Two- Way Local 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 Teleconex ▇▇▇▇▇▇▇▇ shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 ▇▇▇▇▇▇▇▇ shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. ▇▇▇▇▇▇▇▇ shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. ▇▇▇▇▇▇▇▇ shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and ▇▇▇▇▇▇▇▇ has not notified Verizon that it has corrected such blocking, Verizon may submit to ▇▇▇▇▇▇▇▇ a Trunk Group Service Request directing ▇▇▇▇▇▇▇▇ to remedy the blocking. Upon receipt of a Trunk Group Service Request, ▇▇▇▇▇▇▇▇ will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. ▇▇▇▇▇▇▇▇ will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, ▇▇▇▇▇▇▇▇ will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event ▇▇▇▇▇▇▇▇ fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may ▇▇▇▇ ▇▇▇▇▇▇▇▇ for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and Teleconex’s ▇▇▇▇▇▇▇▇’▇ network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.14 ▇▇▇▇▇▇▇▇ will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex ▇▇▇▇▇▇▇▇ to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex ▇▇▇▇▇▇▇▇ and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.
Appears in 1 contract
Two-Way Interconnection Trunks. 2.4.1 Where 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 Parties have agreed to use Two Way Local future, so long as Verizon can measure usage on such Interconnection Trunks, prior subject to ordering any Two-Way Local Interconnection Trunks from Verizonthe terms set forth below and the other terms of this Agreement.
(a) Except to the extent that AWS may have already done so, Teleconex shall meet with Verizon to conduct a joint planning meeting not later than sixty (“Joint Planning Meeting”). At that Joint Planning Meeting60) days after the Effective Date of this Agreement, each Party AWS shall provide to the other Party originating CCS (Hundred Call Second) information, and the Parties shall mutually agree Verizon forecast information on the appropriate initial number of Twohigh usage and final two-Way End Office and Tandem Local way Interconnection Trunks and the interface specifications at the Point of Interconnection (POI)Trunks.
2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a (b) At least semi-annual basisannually, Teleconex AWS shall submit a good faith forecast to Verizon of including the number of End Office high usage and Tandem Twofinal two-Way Local way Interconnection Trunks that Teleconex AWS anticipates that Verizon it will need to provide require during the ensuing two (2) year period. Teleconex’s Such trunk forecasts shall conform to the Verizon CLEC trunk forecasting industry standard guidelines as in effect at that from time to time.
2.4.4 (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 on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need (e.g., trunk usage data, trunk overflow (blocking) data).
(d) AWS shall be responsible for new trunk groups and to plan any necessary changes in determining the number of Twotwo-Way Local Interconnection Trunks.
2.4.5 Two-Way Local way Interconnection Trunks required. Accordingly, AWS shall have SS7 Common Channel Signaling. The Parties agree submit ASRs, from time to utilize B8ZS and Extended Super Frame (ESF) DS1 facilitiestime, where available.
2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local 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 Teleconex shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Twotwo-Way Local way Interconnection Trunks that it is ordering, to be installed and include the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriateby which AWS wishes to have such two-way Interconnection Trunks installed. Teleconex AWS shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit (e) The Parties shall use an economic ccs equal to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days). Further general information regarding trunking may be found in Telcordia reference SR-TAP-000191.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. (f) In the event that the traffic volume between any Tandem Two-Way Local Interconnection Trunk group two (2) Central Office Switches at any time exceeds the 240 trunk level at any timecentum call second (“CCS”) busy hour equivalent of one (1) DS- 1, Teleconex shall promptly submit an ASR to Verizon to AWS will establish new or additional End Office Trunk groups to insure that such Tandem Twotwo-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be prescribed in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.Section
Appears in 1 contract
Sources: Interconnection Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed 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 Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and KDL, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex 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 CCS Centium Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex KDL shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex KDL anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between KDL and Verizon. TeleconexKDL’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local 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 Teleconex KDL shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and RACC, prior RACC shall order from Verizon, and Verizon shall provide, the Two-Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex RACC 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex RACC shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex RACC anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from RACC to Verizon and from Verizon to RACC. TeleconexRACC’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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-. Two- Way Local 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 Teleconex RACC shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 RACC shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. RACC shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. RACC shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and RACC has not notified Verizon that it has corrected such blocking, Verizon may submit to RACC a Trunk Group Service Request directing RACC to remedy the blocking. Upon receipt of a Trunk Group Service Request, RACC will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. RACC will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, RACC will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event RACC fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ RACC for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexRACC’s network, Verizon’s performance on in connection with these Two-Two- Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 RACC will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP-000191, including but not limited to those standards requiring that a call from Teleconex RACC to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex RACC and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex RACC will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexRACC’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexRACC’s side of Teleconex’sRACC’s-IP, which charges shall be solely the financial responsibility responsibility of TeleconexRACC. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the TeleconexRACC-IP, RACC shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on RACC’s side of the RACC-IP, RACC shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if RACC fails to provide RACC-IPs in accordance with this Agreement, RACC will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex RACC establishes such RACC-IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and API, API, 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.
2.4.2 Where the Parties use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and API, prior Verizon, at its own expense, shall provide its own facilities to ordering the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA.
2.4.3 Prior to establishing any Two-Way Local Interconnection Trunks from VerizonTrunks, Teleconex API 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 CCS Centum Call Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Two-Way Interconnection Trunks and the interface specifications at the Point technically feasible Point(s) of Interconnection (POI).
2.4.2 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 Local 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 shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire CenterTwo-Way Interconnection Trunks.
2.4.3 2.4.4 On a semi-annual basis, Teleconex API shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex API anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod for the exchange of traffic between API and Verizon. TeleconexAPI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centum Call Seconds (Hundred Call Seconds) equal to five (5).
2.4.7 . Either Party may disconnect End Office Two-Way Local 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 Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Verizon and Teleconex API shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order Telcordia Notes on the number of TwoNetworks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275).
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and Teleconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Teleconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Teleconex’s side of Teleconex’s-IP, which charges shall be solely the financial responsibility of Teleconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPs.three
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Two-Way Local Interconnection TrunksTrunks for the exchange of traffic between Verizon and Talk Unlimited, prior Talk Unlimited shall order from Verizon, and Verizon shall provide, the Two- Way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs.
2.4.2 Prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Talk Unlimited 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 . Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Local 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 2.4.4 On a semi-annual basis, Teleconex Talk Unlimited shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Talk Unlimited anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from Talk Unlimited to Verizon and from Verizon to Talk Unlimited. TeleconexTalk Unlimited’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 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 Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 2.4.6 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 2.4.7 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 2.4.8 Two-Way Local 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-. Two- Way Local 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 Teleconex Talk Unlimited shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex shall determine and order BOC Notes on the number of TwoLEC Networks SR-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to timeTSV-002275.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results The performance standard for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 2.4.10 Talk Unlimited shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Talk Unlimited shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Talk Unlimited shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Talk Unlimited has not notified Verizon that it has corrected such blocking, Verizon may submit to Talk Unlimited a Trunk Group Service Request directing Talk Unlimited to remedy the blocking. Upon receipt of a Trunk Group Service Request, Talk Unlimited will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Talk Unlimited will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Talk Unlimited will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Talk Unlimited fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may bill Talk Unlimited for the excess Interconnection Trunks at the applicable Verizon rates.
2.4.13 Because Verizon will not be in control of the timing when and sizing of the how many Two-Way Local Interconnection Trunks are established between its network and TeleconexTalk Unlimited’s network, Verizon’s performance on in connection with these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 2.4.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 2.4.15 Talk Unlimited will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex Talk Unlimited to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex Talk Unlimited and the Verizon End Office.
2.4.18 2.4.16 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Two-Way Local Interconnection TrunksTrunks riding on that facility. Teleconex Talk Unlimited will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexTalk Unlimited’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexTalk Unlimited’s side of Teleconex’sTalk Unlimited’s-IP, which charges shall be solely the financial responsibility of TeleconexTalk Unlimited. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks facility on Verizon’s side of the TeleconexTalk Unlimited-IP, Talk Unlimited shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on Talk Unlimited’s side of the Talk Unlimited-IP, Talk Unlimited shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if Talk Unlimited fails to provide Talk Unlimited-IPs in accordance with this Agreement, Talk Unlimited will be responsible for one hundred percent (100%) of all recurring and non-recurring charges shall be divided equally associated with Two-Way Local Interconnection Trunk groups until Teleconex Talk Unlimited establishes such Talk Unlimited-IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Local Interconnection Trunks, prior to ordering any Two-Way Local Interconnection Trunks from Verizon, Teleconex Reconex 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 CCS (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Local Interconnection Trunks and the interface specifications at the Point of Interconnection (POI).
2.4.2 Two-Way Local Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex Reconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 On a semi-annual basis, Teleconex Reconex shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Teleconex Reconex anticipates that Verizon will need to provide during the ensuing two (2) year period. TeleconexReconex’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks.
2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic CCS equal to five (5).
2.4.7 Two-Way Local 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 Local 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 Teleconex Reconex shall engineer Two-Way Local Interconnection Trunks using national standards.
2.4.8 Teleconex Reconex shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex Reconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex Reconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex Reconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex Reconex a Trunk Group Service Request directing Teleconex Reconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex Reconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the TeleconexReconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem any] Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex Reconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex Reconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex Reconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex Reconex will promptly augment all Tandem Two-Way LocalLocal Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two-Way Local Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Reconex will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group. In the event Reconex fails to submit an ASR for Two-Way Local Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ Reconex for the excess Local Interconnection Trunks at the applicable rates provided for in the Pricing Attachment.
2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 Because Verizon will not be in control of the timing and sizing of the Two-Way Local Interconnection Trunks between its network and TeleconexReconex’s network, Verizon’s performance on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex Reconex will route its traffic to Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from Teleconex Reconex to a Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Teleconex Reconex and the Verizon End Office.
2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Teleconex Reconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to TeleconexReconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexReconex’s side of Teleconex’sReconex’s-IP, which charges shall be solely the financial responsibility of TeleconexReconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the TeleconexReconex-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on Reconex’s side of the Reconex-IP, Reconex shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.18, if Reconex fails to provide IPs at Verizon’s Tandem or End Office(s) in accordance with this Agreement, Reconex will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Local Interconnection Trunk groups until Teleconex Reconex establishes such IPs.
Appears in 1 contract
Sources: Service Agreement
Two-Way Interconnection Trunks. 2.4.1 3.1 Where the Parties have agreed to use Two Way Local two-way Interconnection TrunksTrunks for the exchange of traffic between Verizon and Lightship, prior Lightship shall order from Verizon, and Verizon shall provide, the two-way Interconnection Trunks and the Entrance Facility, on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Attachment and Verizon’s applicable Tariffs.
3.2 Prior to ordering any Twotwo-Way Local way Interconnection Trunks from Verizon, Teleconex Lightship 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 CCS Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of TwoMeet Point A (high usage) and Meet Point B (final) two-Way End Office and Tandem Local way Interconnection Trunks and the interface specifications at the Point of Interconnection (POI). 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.2 3.3 Two-Way Local way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where the Teleconex is collocated in a Verizon Wire Center, the POI shall be at the Verizon Wire Center.
2.4.3 3.4 On a semi-annual basis, Teleconex Lightship shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem TwoMeet Point B (final) two-Way Local way Interconnection Trunks that Teleconex Lightship anticipates that Verizon will need to provide during the ensuing two (2) year periodperiod to carry traffic from Lightship to Verizon and from Verizon to Lightship. TeleconexLightship’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time.
2.4.4 3.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem TwoMeet Point B (final) two-Way Local way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local two- way Interconnection Trunks.
2.4.5 3.6 Two-Way Local way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available.available.
2.4.6 3.7 With respect to End Office TwoMeet Point A (high usage) two-Way Local way Interconnection Trunks, both Parties shall use an economic CCS Centium Call Second (Hundred Call Second) equal to five (5).
2.4.7 Two3.8 Meet Point B two-Way Local 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. Meet Point B two-Way Local 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 Teleconex Lightship shall engineer Twotwo-Way Local way Interconnection Trunks using national standardsBOC Notes on the LEC Networks SR-TSV- 002275.
2.4.8 Teleconex shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Teleconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Teleconex shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time.
2.4.9 Verizon may monitor Two-Way Local Interconnection Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Local Interconnection Trunk group and Teleconex has not notified Verizon that it has corrected such blocking, Verizon may submit to Teleconex a Trunk Group Service Request directing Teleconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Teleconex will complete an ASR to augment the Two-Way Local Interconnection Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Teleconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Teleconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level.
2.4.11 Upon request, Teleconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Teleconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour.
2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Teleconex will promptly augment all Tandem Two-Way Local
2.4.13 3.9 The performance standard on final Twofor Meet Point B two-Way Local way Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months.
2.4.14 3.10 Lightship shall determine and order the number of two-way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each two-way Interconnection Trunk group. Lightship shall order two-way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of two-way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Lightship shall complete ASRs in accordance with OBF Guidelines as in effect from time to time.
3.11 Verizon may (but shall not be obligated to) monitor two-way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) two-way Interconnection Trunk group and Lightship has not notified Verizon that it has corrected such blocking, Verizon may submit to Lightship a Trunk Group Service Request directing Lightship to remedy the blocking. Upon receipt of a Trunk Group Service Request, Lightship will complete an ASR to augment the two-way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days.
3.12 The Parties will review all Meet Point B two-way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Lightship will promptly augment all Meet Point B two-way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Meet Point B two-way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Lightship will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the two-way Interconnection Trunks should not be disconnected. In the event Lightship fails to submit an ASR for two-way Interconnection Trunks in conformance with this section, Verizon may ▇▇▇▇ Lightship for the excess Interconnection Trunks at the applicable Verizon rates.
3.13 Because Verizon will not be in control of the timing when and sizing of the Twohow many two-Way Local way Interconnection Trunks are established between its network and TeleconexLightship’s network, Verizon’s performance on in connection with these Two-Way Local two- way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreementthe Terms, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier-to-carrier performance assurance guidelines or plan.
2.4.15 3.14 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Twotwo-Way Local way Interconnection Trunk group and install Oneone-Way Local way Interconnection Trunks to the applicable other Party’s relevant POI, provided that, if a Party has failed to comply with the Terms with regard to two-way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non-complying Party, withdraw its traffic from a two-way Interconnection Trunk group and install one-way Interconnection Trunks to the non-complying Party’s relevant POI.
2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic.
2.4.17 Teleconex 3.15 Lightship will route its traffic to Verizon over the End Office and Tandem TwoMeet Point A and/or Meet Point B two-Way Local way Interconnection Trunks in accordance with SR-TAP192TAP- 000191, including but not limited to those standards requiring that a call from Teleconex Lightship to a Verizon End Office will first be routed to the End Office Local Meet Point A Interconnection Trunk group between Teleconex Lightship and the Verizon End Office.
2.4.18 3.16 When the Parties implement Twotwo-Way Local way Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or (“PPU” factor”) factor for each facility on which the two-way Interconnection Trunks ride, based on the total number of minutes of Traffic traffic that each Party originates sends over the Twotwo-Way Local way Interconnection TrunksTrunks riding on that facility. Teleconex Lightship will pay a percentage of Verizon’s monthly recurring charges for the each facility on which the Twotwo-Way Local way Interconnection Trunks ride equal to TeleconexLightship’s percentage of use of the that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on TeleconexLightship’s side of Teleconex’sLightship’s-IP, which charges shall be solely the financial responsibility of TeleconexLightship. NonDuring the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first two-recurring charges way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Teleconex-IP, the non-recurring charges shall be divided equally Two-Way Local Interconnection Trunk groups until Teleconex establishes such IPspreceding calendar quarter.
Appears in 1 contract
Sources: Interconnection Agreement