Toll Trunks Clause Samples

The 'Toll Trunks' clause defines the terms and conditions governing the use and management of dedicated telephone lines that connect a business's private branch exchange (PBX) to the public switched telephone network for long-distance or toll calls. Typically, this clause outlines responsibilities for installation, maintenance, and payment for these trunk lines, and may specify service levels or usage restrictions. Its core practical function is to ensure both parties understand their obligations regarding the provision and use of toll trunk services, thereby preventing disputes over service quality, costs, or access.
Toll Trunks. 2.5.2.1 Toll traffic shall not be routed on the Local Interconnection Trunks. Separate trunk groups for such Toll and Access Traffic must be established on the Direct Interconnection Facility. Standard access compensation arrangements from the Parties' respective tariffs will apply to the Access Trunks.
View SourceView Similar (4)
Toll Trunks. 3.4.2.3.1 Toll traffic shall not be routed on the Local Interconnection Trunks.
View SourceView Similar (3)
Toll Trunks. 3.4.2.3.1 Toll traffic shall not be routed on the Local Interconnection Trunks. Separate trunk groups for such toll traffic must be established on separate transport facilities. Standard Switched Access Service compensation arrangements from UBET’s respective tariffs will apply to traffic terminated over the toll trunks. 3.4.2.3.2 Bresnan shall route appropriate traffic to the respective UBET switches on the trunk groups as specified in this Attachment. UBET shall route appropriate traffic to Bresnan switches on the trunk group or trunk groups as specified in this Attachment.
View SourceView Similar (2)
Toll Trunks. 3.4.2.3.1 Toll traffic shall not be routed on the Local Interconnection Trunks. Separate trunk groups for such toll traffic must be established on the Direct Interconnection Facility. Standard Switched Access Service compensation arrangements from Champlain Telephone Company’s respective tariffs will apply to traffic terminated over the toll trunks. 3.4.2.3.2 Level 3 Communications, LLC shall route appropriate traffic to the respective Champlain Telephone Company switches on the trunk groups as specified in this Attachment. Champlain Telephone Company shall route appropriate traffic to Level 3 Communications, LLC switches on the trunk group or trunk groups as specified in this Attachment.
View Source
Toll Trunks. 3.4.2.3.1 Toll traffic shall not be routed on the Local Interconnection Trunks. Separate trunk groups for such toll traffic must be established on the Direct Interconnection Facility. Standard access compensation arrangements from ILEC’s respective tariffs will apply to traffic terminated over the toll trunks. 3.4.2.3.2 CLEC shall route appropriate traffic to the respective ILEC switches on the trunk groups as specified in this Attachment. ILEC shall route appropriate traffic to CLEC switches on the trunk group or trunk groups as specified in this Attachment.
View Source
Toll Trunks. 3.6.3.1 Toll traffic shall not be routed on the Local Interconnection Trunks. Separate trunk groups for such toll traffic must be established on the Direct Interconnection Facility. Standard Switched Access Service compensation arrangements from ILEC’s respective tariffs will apply to traffic terminated over the toll trunks. CLEC shall route appropriate traffic to the respective ILEC switches on the trunk groups as specified in this Attachment. ILEC shall route appropriate traffic to CLEC switches on the trunk group or trunk groups as specified in this Attachment. 3.6.3.2 911 Trunks CLEC shall be responsible for establishing all necessary 911 trunks for its End User traffic with the appropriate Public Safety Answering Points. 3.6.3.3 The Parties will mutually agree on the appropriate sizing of the transport facilities. The capacity of transport facilities provided by each Party will be based on mutual forecasts and sound engineering practice, as mutually agreed to by the Parties. CLEC will order trunks in the agreed- upon quantities via an Access Service Request (“ASR”) according to the Ordering Attachment.
View Source
Toll Trunks. 3.4.2.3.1 Toll Traffic, including JPSA Traffic, shall not be routed on the Local Interconnection Trunks. Separate trunk groups for such Toll Traffic and JPSA traffic must be established on the Direct Interconnection Facility. Standard Switched Access Service compensation arrangements from ILEC’s respective tariffs will apply to traffic terminated over the toll trunks. 3.4.2.3.2 CLEC shall route appropriate traffic to the respective ILEC switches on the trunk groups as specified in this Attachment. ILEC shall route appropriate traffic to CLEC switches on the trunk group or trunk groups as specified in this Attachment.
View Source
Toll Trunks. 3.4.2.3.1 Toll traffic shall not be routed on the Local Interconnection Trunks. Separate trunk groups for such toll traffic must be established on the Direct Interconnection Facility. Standard Switched Access Service compensation arrangements from the ELECTRONICALLY FILED - 2018 April 25 10:28 AM - SCPSC - Docket # 2018-145-C - Page 46 of 56 Parties’ respective tariffs will apply to traffic terminated over the toll trunks. 3.4.2.3.2 CLEC shall route appropriate traffic to the respective ILEC switches on the trunk groups as specified in this Attachment. ILEC shall route appropriate traffic to CLEC switches on the trunk group or trunk groups as specified in this Attachment.
View Source

Related to Toll Trunks

  • Tandem Switching 4.5.1 The Tandem Switching capability Network Element is defined as: (i) trunk-connect facilities, which include, but are not limited to, the connection between trunk termination at a cross-connect panel and switch trunk card; (ii) the basic switch trunk function of connecting trunks to trunks; and (iii) the functions that are centralized in the Tandem Switches (as distinguished from separate end office switches), including but not limited to call recording, the routing of calls to operator services and signaling conversion features. 4.5.2 Where <<customer_short_name>> utilizes portions of the BellSouth network in originating or terminating traffic, the Tandem Switching rates are applied in call scenarios where the Tandem Switching Network Element has been utilized. Because switch recordings cannot accurately indicate on a per call basis when the Tandem Switching Network Element has been utilized for an interoffice call originating from a UNE port and terminating to a BellSouth, Independent Company or Facility-Based CLEC office, BellSouth has developed, based upon call studies, a melded rate that takes into account the average percentage of calls that utilize Tandem Switching in these scenarios. BellSouth shall apply the melded Tandem Switching rate for every call in these scenarios. BellSouth shall utilize the melded Tandem Switching Rate until BellSouth has the capability to measure actual Tandem Switch usage in each call scenario specifically mentioned above, at which point the rate for the actual Tandem Switch usage shall apply. The UNE Local Call Flows set forth on BellSouth's website, as amended from time to time and incorporated herein by this reference, illustrate when the full or melded Tandem Switching rates apply for specific scenarios.

  • Tandem Transit Traffic ‌ 12.1 As used in this Section, Tandem Transit Traffic is Telephone Exchange Service traffic that originates on Onvoy's network, and is transported through Frontier’s Tandem to the subtending End Office or its equivalent of another carrier (CLEC, ILEC other than Frontier, Commercial Mobile Radio Service (CMRS) carrier, or other LEC (“Other Carrier”). Neither the originating nor terminating customer is a Customer of Frontier. Subtending End Offices shall be determined in accordance with and as identified in the Local Exchange Routing Guide (LERG). For the avoidance of any doubt, under no circumstances shall Frontier be required to transit traffic through a Frontier Tandem to a Central Office that the LERG does not identify as subtending that particular Frontier Tandem. Switched Exchange Access Service traffic is not Tandem Transit Traffic. 12.2 Tandem Transit Traffic Service provides Onvoy with the transport of Tandem Transit Traffic as provided below. 12.3 Tandem Transit Traffic may be routed over the Interconnection Trunks described in Sections 2 through 6 of this Attachment. Onvoy shall deliver each Tandem Transit Traffic call to Frontier’s Tandem with CCS and the appropriate Transactional Capabilities Application Part (“TCAP”) message to facilitate full interoperability of CLASS Features and billing functions. 12.4 Onvoy may use Tandem Transit Traffic Service only for traffic that originates on Onvoy’s network and only to send traffic to an Other Carrier with whom Onvoy has a reciprocal traffic exchange arrangement (either via written agreement or mutual tariffs) that provides for the Other Carrier, to terminate or complete traffic originated by Onvoy and to bill Onvoy, and not to bill Frontier, for such traffic. Onvoy agrees not to use Frontier’s Tandem Transit Traffic Service to send traffic to an Other Carrier with whom Onvoy does not have such a reciprocal traffic exchange arrangement or to send traffic that does not originate on Onvoy’s network. 12.5 Onvoy shall pay Frontier for Tandem Transit Traffic Service at the rates specified in the Pricing Attachment. Frontier will not be liable for compensation to any Other Carrier for any traffic that is transported through Frontier’s Tandem and Frontier reserves the right to assess to Onvoy any additional charges or costs any Other Carrier imposes or levies on Frontier for the delivery or termination of such traffic, including any Switched Exchange Access Service charges. If Frontier is billed by any Other Carrier for any traffic originated by Onvoy, Frontier may provide notice to Onvoy of such billing. Upon receipt of such notice, Onvoy shall immediately stop using Frontier’s Tandem Transit Traffic Service to send any traffic to such Other Carrier until it has provided to Frontier certification that the Other Carrier has removed such billed charges from its bill to Frontier and that the Other Carrier will not bill Frontier for any traffic originated by Onvoy. Such certification must be signed by an authorized officer or agent of the Other Carrier and must be in a form acceptable to Frontier. 12.6 If Onvoy uses Tandem Transit Traffic Service for traffic volumes that exceed the Centum Call Seconds (Hundred Call Seconds) busy hour equivalent of 200,000 combined minutes of use per month (a DS1 equivalent) to the subtending End Office of a particular Other Carrier for any month (the “Threshold Level”). Onvoy shall use good faith efforts to establish direct interconnection with such Other Carrier and reduce such traffic volumes below the Threshold Level. If Frontier believes that ▇▇▇▇▇ has not exercised good faith efforts promptly to obtain such direct interconnection, either Party may use the Dispute Resolution processes of this Agreement. 12.7 If Onvoy fails to comply with Section 12 of this Attachment, such failure shall be a material breach of a material provision of this Agreement and Frontier may exercise any and all remedies under this Agreement and Applicable Law for such breach. 12.8 If or when a third party carrier plans to subtend an Onvoy switch, then Onvoy shall provide written notice to Frontier at least ninety (90) days before such subtending service arrangement becomes effective so that Frontier may negotiate and establish direct interconnection with such third party carrier. Upon written request from Frontier, Onvoy shall offer to Frontier a service arrangement equivalent to or the same as Tandem Transit Traffic Service provided by Frontier to Onvoy as defined in this Section such that Frontier may terminate calls to a Central Office or its equivalent of a CLEC, ILEC other than Frontier, CMRS carrier, or other LEC, that subtends an Onvoy Central Office or its equivalent (“Reciprocal Tandem Transit Service”). Onvoy shall offer such Reciprocal Transit Service arrangements under terms and conditions of an amendment to this Agreement or a separate agreement no less favorable than those provided in this Section. 12.9 Neither Party shall take any actions to prevent the other Party from entering into a direct and reciprocal traffic exchange arrangement with any carrier to which it originates, or from which it terminates, 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.

  • NYISO and Connecting Transmission Owner Obligations Connecting Transmission Owner and NYISO shall cause the New York State Transmission System and the Connecting Transmission Owner’s Attachment Facilities to be operated, maintained and controlled in a safe and reliable manner in accordance with this Agreement and the NYISO Tariffs. Connecting Transmission Owner and NYISO may provide operating instructions to Developer consistent with this Agreement, NYISO procedures and Connecting Transmission Owner’s operating protocols and procedures as they may change from time to time. Connecting Transmission Owner and NYISO will consider changes to their respective operating protocols and procedures proposed by Developer.

  • Signaling Each Party will provide the other Party with access to its databases and associated signaling necessary for the routing and completion of the other Party’s traffic in accordance with the provisions contained in the Unbundled Network Element Attachment or applicable access tariff.