Toll Trunks Sample Clauses

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.
AutoNDA by SimpleDocs
Toll Trunks. 3.4.2.3.1 Toll traffic shall not be routed on the Local Interconnection Trunks.
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.
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.
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.
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.
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.
AutoNDA by SimpleDocs

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 Xxxxx 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 Interconnection Trunks for the exchange of traffic between Verizon and PCS, 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 Interconnection Trunks from Verizon, 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 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 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.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. 2.4.4 On a semi-annual basis, PCS shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that PCS anticipates Verizon will need to provide during the ensuing two (2) year period to carry traffic from PCS to Verizon and from Verizon to PCS. PCS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 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 Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way 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.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.01 during the average time consistent busy hour. Verizon and PCS shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 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

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

  • Local Switching 4.1.1 BellSouth shall provide non-discriminatory access to local circuit switching capability, and local tandem switching capability, on an unbundled basis, except as set forth below in Section 4.1.

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

  • Unbundled Channelization (Multiplexing) 5.7.1 To the extent NewPhone is purchasing DS1 or DS3 or STS-1 Dedicated Transport pursuant to this Agreement, Unbundled Channelization (UC) provides the optional multiplexing capability that will allow a DS1 (1.544 Mbps) or DS3 (44.736 Mbps) or STS-1 (51.84 Mbps) Network Elements to be multiplexed or channelized at a BellSouth central office. Channelization can be accomplished through the use of a multiplexer or a digital cross-connect system at the discretion of BellSouth. Once UC has been installed, NewPhone may request channel activation on a channelized facility and BellSouth shall connect the requested facilities via COCIs. The COCI must be compatible with the lower capacity facility and ordered with the lower capacity facility. This service is available as defined in NECA 4. 5.7.2 BellSouth shall make available the following channelization systems and interfaces: 5.7.2.1 DS1 Channelization System: channelizes a DS1 signal into a maximum of twenty- four (24)

  • Provisioning Line Splitting and Splitter Space 3.8.1 The Data LEC, Voice CLEC or BellSouth may provide the splitter. When Southern Telecom or its authorized agent owns the splitter, Line Splitting requires the following: a non-designed analog Loop from the serving wire center to the NID at the End User’s location; a collocation cross connection connecting the Loop to the collocation space; a second collocation cross connection from the collocation space connected to a voice port; the high frequency spectrum line activation, and a splitter. The Loop and port cannot be a Loop and port combination (i.e. UNE-P), but must be individual stand-alone Network Elements. When BellSouth owns the splitter, Line Splitting requires the following: a non designed analog Loop from the serving wire center to the NID at the End User’s location with CFA and splitter port assignments, and a collocation cross connection from the collocation space connected to a voice port. 3.8.2 An unloaded 2-wire copper Loop must serve the End User. The meet point for the Voice CLEC and the Data LEC is the point of termination on the MDF for the Data LEC's cable and pairs. 3.8.3 The foregoing procedures are applicable to migration to Line Splitting Service from a UNE-P arrangement, BellSouth Retail Voice Service, BellSouth High Frequency Spectrum (CO Based) Line Sharing. 3.8.4 For other migration scenarios to line splitting, BellSouth will work cooperatively with CLECs to develop methods and procedures to develop a process whereby a Voice CLEC and a Data LEC may provide services over the same Loop.

  • Loop A transmission path that extends from a Main Distribution Frame or functionally comparable piece of equipment in a Customer's serving End Office, to the Rate Demarcation Point (or NID if installed at the Rate Demarcation Point) in or at the Customer's premises. The actual transmission facilities used to provide a Loop may utilize any of several technologies.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!