INTERCONNECTION TRUNKING REQUIREMENTS Sample Clauses

INTERCONNECTION TRUNKING REQUIREMENTS. 3.1 Introduction 3.1.1 This Section 3 of Article V sets forth terms and conditions for Interconnection provided by CenturyLink and BendTel. 3.1.2 This Section 3 of Article V provides descriptions of the trunking requirements between BendTel and CenturyLink. All references to incoming and outgoing trunk groups are from the perspective of BendTel. The paragraphs below describe the required and optional trunk groups for local and mass calling. 3.1.3 Local trunk groups may only be used to transport traffic between the Parties’ End Users pursuant to the terms of this Article. 3.2 One Way and Two Way Trunk Groups 3.2.1 One-way trunk groups for ancillary services (e.g. mass calling) can be established between the Parties. Ancillary trunk groups will utilize Signaling System 7 (SS7) or multi-frequency (MF) signaling protocol, with SS7 signaling preferred whenever possible. The originating Party will have administrative control of one-way trunk groups. 3.2.2 The Parties agree that two-way trunk groups for local, IntraLATA and InterLATA traffic shall be established between a BendTel switch and a CenturyLink End Office switch pursuant to the terms of this Article. Trunks will utilize Signaling System 7 (SS7) or multi-frequency (MF) signaling protocol, with SS7 signaling being used whenever possible. Two-way trunking for Local Traffic will be jointly provisioned and maintained, with each Party being responsible for costs on its side of the POI. The costs associated with transporting Information Access Traffic and/or ISP-Bound Traffic to BendTel shall be the sole responsibility of BendTel. For administrative consistency BendTel will have control for the purpose of issuing Access Service Requests (ASRs) on two-way groups. Either Party will also use ASRs to request changes in trunking. Both Parties reserve the right to issue ASRs, if so required, in the normal course of business. 3.2.3 Notwithstanding 3.2 above, the Parties recognize that certain technical and billing issues may necessitate the use of one-way trunking for an interim period. If either Party wants to provision its own one-way trunks, this must be agreed to by both Parties. The Parties will negotiate the appropriate trunk configuration, whether one-way or two-way giving consideration to relevant factors, including but not limited to, existing network configuration, administrative ease, any billing system and/or technical limitations and network efficiency. Any disagreement regarding appropriate trunk config...
View SourceView Similar (10)
INTERCONNECTION TRUNKING REQUIREMENTS. AMERITECH-ILLINOIS shall provide to CLEC Interconnection of the Parties’ facilities and equipment for the transmission and routing of Telephone Exchange Service traffic and Exchange Access traffic pursuant to the applicable Appendix ITR, which is/are attached hereto and incorporated herein by reference. Methods for Interconnection and Physical Architecture shall be as defined in the applicable Appendix NIM, which is/are attached hereto and incorporated herein by reference. AMERITECH-ILLINOIS shall provide to CLEC certain trunk groups (Meet Point Trunks) under certain parameters pursuant to the applicable Appendix ITR, which is/are attached hereto and incorporated herein by reference. The applicable Appendix Compensation, which is/are attached hereto and incorporated herein by reference, prescribe traffic routing parameters for Local Interconnection Trunk Group(s) the Parties shall establish over the Interconnections specified in the applicable Appendix ITR, which is/are attached hereto and incorporated herein by reference. One or more of the ILECs making up SBC have deployed a set of AIN features and functionalities unique to the particular ILEC(s). As such, the AIN network architecture, methods of access and manner of provisioning are specific to that ILEC or those ILECs. Accordingly, any request for AIN access pursuant to this Agreement must be reviewed for technical feasibility, with all rates, terms and conditions related to such request to be determined on an individual case basis and to be negotiated between the Parties. Upon request by CLEC, and where technically feasible, AMERITECH-ILLINOIS will provide CLEC with access to Ameritech-Illinois’ Advanced Intelligent Network (AIN) platform, AIN Service Creation Environment (SCE) and AIN Service Management System (SMS) based upon ILEC-specific rates, terms, conditions and means of access to be negotiated by the Parties pursuant to Section 252 of the Act, and incorporated into this Agreement by Appendix or amendment, as applicable, subject to approval by the appropriate state Commission.
View SourceView Similar (3)
INTERCONNECTION TRUNKING REQUIREMENTS. 74.1. This Section sets forth terms and conditions for Interconnection provided by CenturyLink and **CLEC, and provides descriptions of the trunking requirements between **CLEC and CenturyLink. All references to incoming and outgoing trunk groups are from the perspective of **CLEC. The paragraphs below describe the required and optional trunk groups for local and mass calling. 74.2. Local trunk groups may only be used to transport traffic between the Parties’ End Users pursuant to the terms of this Article. A Party will not originate any Local Traffic to the other Party except via the trunk group established for the exchange of Local Traffic. 74.3. One Way and Two Way Trunk Groups 74.3.1. One-way trunk groups for ancillary services (e.g. mass calling) can be established between the Parties. Ancillary trunk groups will utilize Signaling System 7 (SS7) signaling protocol. Multi-frequency (MF) signaling protocol may only be used where **CLEC can demonstrate that it is not technically feasible to use SS7 or where CenturyLink otherwise agrees to use MF. The originating Party will have administrative control of one-way trunk groups.
View SourceView Similar (2)
INTERCONNECTION TRUNKING REQUIREMENTS. Each Party is financially responsible for transport on its side of each POI. If CLEC chooses to lease the facility from each POI to CLEC's network from CenturyLink and the facility is within CenturyLink's serving territory, CLEC will lease the facility from CenturyLink as defined in Section 2 of this Amendment. Nothing herein shall be read to require CLEC to immediately obtain additional POIs. However, CLEC agrees that it will continue to comply with the terms of the Agreement, including but not limited to the requirements to establish additional POIs based on volume thresholds in existing Interconnection Agreements. Network Interconnection Methods for Direct Interconnection
View Source
INTERCONNECTION TRUNKING REQUIREMENTS. 1.3.1. The Parties agree to initially use two-way trunks when appropriate and available for a given trunk group. 1.3.2. The Parties shall initially reciprocally terminate Local Traffic and IntraLATA/InterLATA toll calls originating on the other Party’s network as follows: 1.3.2.1. The Parties shall make available to each other two-way trunks for the reciprocal exchange of combined Local Traffic, and non-equal access IntraLATA toll traffic. Neither Party is obligated under this Agreement to order reciprocal trunks or build facilities in the establishment of interconnection arrangements for the delivery of Internet traffic. The Party serving the Internet service provider shall order trunks or facilities from the appropriate tariff of the other Party for such purposes and will be obligated to pay the full cost of such facility. 1.3.2.2. SBCT is solely responsible for the facilities that carry OS/DA, 911, mass calling and Meet-Point trunk groups. 1.3.2.3. Separate two-way trunks will be made available for the exchange of equal-access InterLATA or IntraLATA interexchange traffic that transits Sprint’s network. 1.3.2.4. Separate trunks will be utilized for connecting SBCT’s switch to each 911/E911 tandem or equivalent. 1.3.2.5. Separate trunks will be utilized for connecting SBCT’s switch to Sprint’s Choke tandem and Operator Services/Directory Assistance tandem, where available. 1.3.2.6. SBCT may choose to use the same physical facilities to provision all categories of traffic. Such use will not be for the purpose of avoiding access charges associated with InterLATA and IntraLATA traffic originated by or terminated to an End User who is not a SBCT local exchange service End User. 1.3.2.7. Separate trunk groups will be utilized for connecting SBCT’s switch to Sprint’s Operator Service center for operator-assisted busy line interrupt/verify. 1.3.2.8. Inward operator-assisted busy line interrupt/verify traffic may be routed between the two Parties via a separate dedicated trunk group. 1.3.2.9. Telcordia nomenclature convention(s) will be employed. 1.3.2.10. When end office functionality is provided in a remote end office of a host/remote configuration, the interconnection for that remote end office will be provided at the host switch.
View Source
INTERCONNECTION TRUNKING REQUIREMENTS. 58.1. This Section sets forth terms and conditions for Interconnection provided by CenturyLink and QCC. 58.2. This Section provides descriptions of the trunking requirements between QCC and CenturyLink. The paragraphs below describe the required and optional trunk groups for local and mass calling. 58.3. Local trunk groups may only be used to transport traffic between the Parties’ End Users pursuant to the terms of this Article. A Party will not originate any Local Traffic to the other Party except via the trunk group established for the exchange of Local Traffic. 58.4. One Way and Two Way Trunk Groups a. One-way trunk groups for ancillary services (e.g., mass calling) can be established between the Parties. Ancillary trunk groups will utilize Signaling System 7 (SS7) signaling protocol. Multi-frequency (MF) signaling protocol may only be used where QCC can demonstrate that it is not technically feasible to use SS7 or where CenturyLink otherwise agrees to use MF. The originating Party will have administrative control of one-way trunk groups.
View Source
INTERCONNECTION TRUNKING REQUIREMENTS. 3.1 Introduction 3.1.1 This Section 3 of Article IV sets forth terms and conditions for Interconnection provided by CenturyLink and ELTOPIA. 3.1.2 This Section 3 of Article IV provides descriptions of the trunking requirements between ELTOPIA and CenturyLink. All references to incoming and outgoing trunk groups are from the perspective of
View Source
INTERCONNECTION TRUNKING REQUIREMENTS. 58.1. Introduction 58.1.1. This Section of Article IV sets forth terms and conditions for Interconnection provided by CenturyLink and US Xchange. 58.1.2. This Section of Article IV provides descriptions of the trunking requirements between US Xchange and CenturyLink. All references to incoming and outgoing trunk groups are from the perspective of US Xchange. The paragraphs below describe the required and optional trunk groups for local and mass calling. 58.1.3. Local trunk groups may only be used to transport traffic between the Parties’ End Users pursuant to the terms of this Article. A Party will not originate any Local Traffic to the other Party except via the trunk group established for the exchange of Local Traffic.
View Source
INTERCONNECTION TRUNKING REQUIREMENTS 
View SourceView Similar (5)

Related to INTERCONNECTION TRUNKING REQUIREMENTS

  • Trunking Requirements The Parties will provide designed Interconnection facilities that meet the same technical criteria and service standards, such as probability of blocking in peak hours and transmission standards, in accordance with current industry standards.

  • Switching System Hierarchy and Trunking Requirements For purposes of routing ECI traffic to Verizon, the subtending arrangements between Verizon Tandem Switches and Verizon End Office Switches shall be the same as the Tandem/End Office subtending arrangements Verizon maintains for the routing of its own or other carriers’ traffic (i.e., traffic will be routed to the appropriate Verizon Tandem subtended by the terminating End Office serving the Verizon Customer). For purposes of routing Verizon traffic to ECI, the subtending arrangements between ECI Tandem Switches and ECI End Office Switches shall be the same as the Tandem/End Office subtending arrangements that ECI maintains for the routing of its own or other carriers’ traffic.

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

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

  • Traffic Measurement and Billing over Interconnection Trunks 6.1 For billing purposes, each Party shall pass Calling Party Number (CPN) information on at least ninety-five percent (95%) of calls carried over the Interconnection Trunks. 6.1.1 As used in this Section 6, “Traffic Rate” means the applicable Reciprocal Compensation Traffic rate, Measured Internet Traffic rate, intrastate Switched Exchange Access Service rate, interstate Switched Exchange Access Service rate, or intrastate/interstate Tandem Transit Traffic rate, as provided in the Pricing Attachment, an applicable Tariff, or, for Measured Internet Traffic, the FCC Internet Order. 6.1.2 If the originating Party passes CPN on ninety-five percent (95%) or more of its calls, the receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. For any remaining (up to 5%) calls without CPN information, the receiving Party shall ▇▇▇▇ the originating Party for such traffic at the Traffic Rate applicable to each relevant minute of traffic, in direct proportion to the minutes of use of calls passed with CPN information. 6.1.3 If the originating Party passes CPN on less than ninety-five percent (95%) of its calls and the originating Party chooses to combine Reciprocal Compensation Traffic and Toll Traffic on the same trunk group, the receiving Party shall ▇▇▇▇ the higher of its interstate Switched Exchange Access Service rates or its intrastate Switched Exchange Access Services rates for all traffic that is passed without CPN, unless the Parties agree that other rates should apply to such traffic. 6.2 At such time as a receiving Party has the capability, on an automated basis, to use such CPN to classify traffic delivered over Interconnection Trunks by the other Party by Traffic Rate type (e.g., Reciprocal Compensation Traffic/Measured Internet Traffic, intrastate Switched Exchange Access Service, interstate Switched Exchange Access Service, or intrastate/interstate Tandem Transit Traffic), such receiving Party shall ▇▇▇▇ the originating Party the Traffic Rate applicable to each relevant minute of traffic for which CPN is passed. If the receiving Party lacks the capability, on an automated basis, to use CPN information on an automated basis to classify traffic delivered by the other Party by Traffic Rate type, the originating Party will supply Traffic Factor 1 and Traffic Factor