Local Interconnection Trunks Clause Samples

Local Interconnection Trunks. 3.4.2.1.1 The Parties will establish a local trunk group for the exchange of Local/EAS Traffic (“Local Interconnection Trunks”) on the Direct Interconnection Facility. The Parties agree that all Local/EAS Traffic exchanged between them will be on trunks exclusively dedicated to such traffic. Neither Party will terminate InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks. 3.4.2.1.2 If the Parties’ originating Local/EAS Traffic is exchanged utilizing the same two-way Local Interconnection Trunk, both Parties will mutually coordinate the provisioning and quantity of trunks to be utilized in this arrangement.
View SourceView Similar (7)
Local Interconnection Trunks. 3.4.2.1.1 The Parties will establish a local trunk group for the exchange of Local/ELCS/EAS Traffic and ISP-Bound Traffic (“Local Interconnection Trunks”) on the Direct Interconnection Facility. The Parties agree that all Local/ELCS/EAS Traffic and ISP-Bound Traffic exchanged between them will be on trunks exclusively dedicated to such traffic. Neither Party will terminate CMRS traffic and/or InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks. 3.4.2.1.2 If the Parties’ originating Local/ELCS/EAS Traffic and ISP-Bound Traffic is exchanged utilizing the same two-way Local Interconnection Trunk, both Parties will mutually coordinate the provisioning and quantity of trunks to be utilized in this arrangement.
View SourceView Similar (4)
Local Interconnection Trunks. Interconnection for Local Traffic and IntraLATA Toll Traffic shall be provided via one-way trunks, or by written notice (in the form of an ASR, as defined in Section 23.1) to Ameritech from TWC, two-way trunks. Once two-way trunks are employed, TWC shall provide to Ameritech a PLU or actual minutes of use. No Party shall construct facilities which require another Party to build unnecessary facilities.
View SourceView Similar (2)
Local Interconnection Trunks. 2.5.1.1 The Parties will establish a separate trunk group for the exchange of Local/EAS Traffic and ISP-Bound Traffic ("Local Interconnection Trunks") on the Direct Interconnection Facility. The Parties agree that all Local/EAS and ISP-Bound Traffic exchanged between them will be on trunks exclusively dedicated to such Traffic. Neither Party will terminate IntraLATA or InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks. Traffic destined to RHTC End User Customers shall not be routed over the Local I_uterconnection Trunks. 2.5.1.2 If the Parties' originated Local/EAS Traffic and ISP-Botmd Traffic is exchanged utilizing the same two-way Local Interconnection Trunk, both Parties will mutually coordinate the provisioning and quantity of trunks to be utilized in this arrangement.
View SourceView Similar (2)
Local Interconnection Trunks. Unless otherwise agreed (e.g., in the case of 911 trunks) the Parties shall configure two-way trunk groups as a direct transmission path through the Interconnection Point(s) specified in Schedule 3.0. TWTC shall specify the Digital Signal Level of the trunk facilities (e.g., DS0, DS1 or higher, where available) consistent with the forecasting requirements in Section 19.3. No Party shall terminate Exchange Access traffic or originate untranslated 800/888 traffic over Local Interconnection Trunks.
View Source
Local Interconnection Trunks. 3.4.1 The Parties will establish a local trunk group for the exchange of Local Traffic, EAS Traffic, and ISP-Bound Traffic (“Local Interconnection Trunks”) on the Direct Interconnection Facility. The Parties agree that all Local Traffic, EAS Traffic and ISP-Bound Traffic exchanged between them will be on trunks exclusively dedicated to such traffic. Neither Party will terminate IntraLATA toll traffic or InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks. 3.4.2 If the Parties’ originating Local Traffic, EAS Traffic and ISP-Bound Traffic is exchanged utilizing the same two-way Local Interconnection Trunk, both Parties will mutually coordinate the provisioning and quantity of trunks to be utilized in this arrangement according to standard practices as set forth in Section 8. 3.4.3 All traffic terminated over the Local Interconnection Trunks must terminate in the End Office or subtending Remote; i.e., no Tandem switching will be performed in the End Office, including transiting to other carriers connected to that End Office except as provided in Section 5.3 of this Attachment. 3.4.4 All non-local, non-EAS and non-ISP-Bound traffic shall be completed by a separate carrier(s) or on a separate trunk group(s).
View Source
Local Interconnection Trunks. 3.3.1.1 The Parties will establish a local trunk group for the exchange of Local/EAS and ISP-Bound Traffic (“Local Interconnection Trunks”) on the Direct Interconnection Facility. Neither Party will terminate IntraLATA or InterLATA toll traffic or originate untranslated traffic to service codes (e.g., 800, 888) over Local Interconnection Trunks. 3.3.1.2 If the Parties’ originated Local/EAS and ISP-Bound Traffic is exchanged utilizing the same two-way Local Interconnection Trunk, both parties will mutually coordinate the provisioning and quantity of trunks to be utilized in this arrangement.
View Source
Local Interconnection Trunks. 2.4.1.1.1 The Parties will establish separate trunk groups for the exchanged of Local/EAS Traffic and ISP-Bound Traffic ("Interconnection Trunks") on the Direct Interconnection Facility. The Parties agree that all Local/EAS and ISP-Bound Traffic exchanged between them will be on trunks exclusively dedicated to such traffic. Neither Party will terminate IntraLATA or InterLATA toll traffic or originate untranslated traffic to servicecodes(e.g. 800,888)over Interconnection Trunks. 2.4.1.1.2 If the Parties'originatedLocal/EASTraffic andISP- BotmdTrafficis exchangeudtilizingthesametwo-way InterconnectionTrunk, both parties will mutually coordinatteheprovisioningandquantityof trunkstobe utilizedin thisarrangement. 2.4.1. 2AccessTrunks 2.4.1.2.1 Toll traffic shallnot be routedon the Interconnection Trunks.Separatterunkgroupsfor suchToll andAccess Traffic must be established on the Direct. InterconnectioFnacility. Standaradccescsompensation arrangementfsrom the ILECs respectivetariffs will applytothetoll trunks.
View Source
Local Interconnection Trunks. 2.4.1.1.1 The Parties will establish local trunk groups for the exchange of Local and EAS Traffic and ISP Bound Traffic (“Local Interconnection Trunks”) on the Direct Interconnection Facility. The Parties agree that all Local/EAS Traffic and ISP Bound Traffic exchanged between them will be on trunks exclusively dedicated to such traffic. Neither Party will terminate InterLATA toll traffic or originate untranslated traffic to service codes (e.g. 800, 888) over Local Interconnection Trunks. 2.4.1.1.2 If the Parties’ originated Local and EAS Traffic and ISP Bound Traffic is exchanged utilizing the same two- way Local Interconnection Trunk, both Parties will mutually coordinate the provisioning and quantity of trunks to be utilized in this arrangement
View Source

Related to Local Interconnection Trunks

  • One-Way Interconnection Trunks 2.3.1 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Onvoy to Frontier, Onvoy, at Onvoy’s own expense, shall: 2.3.1.1 provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.3.1.2 obtain transport for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.3.2 For each Tandem or End Office One-Way Interconnection Trunk group for delivery of traffic from Onvoy to Frontier with a utilization level of less than sixty percent (60%) for final trunk groups and eighty-five percent (85%) for high usage trunk groups, unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for all final trunk groups and eighty-five percent (85%) for all high usage trunk groups. In the event Onvoy fails to submit an ASR to disconnect One-Way Interconnection Trunks as required by this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the rates set forth in the Pricing Attachment. 2.3.3 Where the Parties use One-Way Interconnection Trunks for the delivery of traffic from Frontier to Onvoy, Frontier, at Frontier’s own expense, shall provide its own facilities for delivery of the traffic to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA.

  • 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.

  • Provisional Interconnection Service Prior to the completion of the Large Facility Interconnection Procedures and prior to completion of requisite Attachment Facilities, Distribution Upgrades, System Upgrade Facilities, System Distribution Upgrades, or System Protection Facilities, the Developer may request an evaluation for Provisional Interconnection Service. NYISO, in conjunction with the Connecting Transmission Owner, shall determine, through available studies or additional studies as necessary, whether stability, short circuit, thermal, and/or voltage issues would arise if the Developer interconnects without modifications to the Large Generating Facility or the New York State Transmission System (or Distribution System as applicable). NYISO, in conjunction with the Connecting Transmission Owner, shall determine whether any Attachment Facilities, Distribution Upgrades, System Upgrade Facilities, System Deliverability Upgrades, or System Protection Facilities, which are necessary to meet Applicable Laws and Regulations, Applicable Reliability Standards, and Good Utility Practice, are in place prior to the commencement of interconnection service from the Large Facility. Where available studies indicate that the Attachment Facilities, Distribution Upgrades, System Upgrade Facilities, System Deliverability Upgrades, or System Protection Facilities are required for the interconnection of a new, modified and/or expanded Large Facility but such facilities are not currently in place, NYISO, in conjunction with the Connecting Transmission Owner, will perform a study, at the Developer’s expense, to confirm the facilities that are required for Provisional Interconnection Service. The maximum permissible output of the Large Facility in the Provisional Large Facility Interconnection Agreement shall be studied, at the Developer’s expense, and updated annually. The NYISO shall issue the study’s findings in writing to the Developer and Connecting Transmission Owner(s). Following a determination by NYISO, in conjunction with the Connecting Transmission Owner, that the Developer may reliably provide Provisional Interconnection Service, NYISO shall tender to the Developer and Connecting Transmission Owner, a Provisional Large Facility Interconnection Agreement. NYISO, Developer, and Connecting Transmission Owner may execute the Provisional Large Facility Interconnection Agreement, or the Developer may request the filing of an unexecuted Provisional Large Facility Interconnection Agreement with the Commission. The Developer shall assume all risk and liabilities with respect to changes between the Provisional Large Facility Interconnection Agreement and the Large Generator Interconnection Agreement, including changes in output limits and the cost responsibilities for the Attachment Facilities, System Upgrade Facilities, System Deliverability Upgrades, and/or System Protection Facilities.

  • Interconnection 2.1 This section applies to linking with suppliers providing public telecommunications transport networks or services in order to allow the users of one supplier to communicate with users of another supplier and to access services provided by another supplier, where specific commitments are undertaken.