Local Traffic and IntraLATA Toll Traffic Clause Samples

Local Traffic and IntraLATA Toll Traffic. ‌ 4.1.1 The Parties shall, pursuant to Sections 4.1.1.1 and 4. 1.1.2 below, reciprocally terminate Local Traffic and IntraLATA toll calls, when either Party is the IntraLATA toll provider. 4.1.1.1 Where technically feasible, the Parties shall make available to each other two- way trunks for the reciprocal exchange of combined Local Traffic and IntraLATA toll traffic. In such case, each Party will provide to each other its Percentage of Local Use (PLU) for billing purposes. If either Party questions the accuracy of the other’s PLU, that issue may be included in a verification review as provided in §32.0 of the General Terms and Conditions. If at any time during the term of this Agreement, the average monthly number of minutes of use (combined Local Traffic and IntraLATA toll traffic) terminated by either Party on the network of the other exceeds the generally accepted engineering practices as mutually agreed to by the Parties, the Party on whose network those minutes have been terminated may elect to require jurisdictionally separate trunks for Local Traffic and IntraLATA toll traffic. 4.1.1.2 Each Party's operator bureau shall accept BLV and BLVI inquiries from the operator bureau of the other Party in order to allow transparent provisioning of BLV/BLVI traffic between the Parties' networks. Each Party shall route BLV/BLVI inquiries between the Parties respective operator bureaus.
View SourceView Similar (14)
Local Traffic and IntraLATA Toll Traffic. Originating on AT&T, Terminating on GTE. AT&T may build trunk groups to GTE using the following representative, but not exclusive, options: (i) from AT&T collocated equipment in a Wire Center to the GTE Tandem; (ii) from AT&T collocated equipment in a GTE Wire Center to the GTE End Office Switch; or (iii) from AT&T 4ESS Switches located at AT&T POPs to the nearest GTE Tandem. Interfaces for these interconnections may be based upon, but not limited to, the following: (i) DS1: from an AT&T-collocated DDM- 2000 to a GTE Central Office Switch; (ii) SONET STS1: from an AT&T-collocated DDM-2000 to an GTE 5ESS®-2000 Central Office Switch and (iii) DS1/DS3: from an AT&T 4ESS Switch at an AT&T POP to a GTE Tandem using new trunk groups on existing facilities. 37.4.1 Upon request by either Party, the other Party shall provide, for the purpose of network planning and management, performance data regarding traffic characteristics with respect to the first Party’s trunks and interconnections to and with the other Party. The specific quantity, timing and detail of such performance data shall be mutually agreed upon by the teams implementing this Agreement.
View SourceView Similar (11)
Local Traffic and IntraLATA Toll Traffic. 4.1.1 The Parties shall reciprocally terminate Local Traffic and IntraLATA toll calls originating on each other's networks as follows: 4.1.1.1 At AT&T’s discretion, one-way trunk groups may be ordered as two-way for testing purposes, but used to carry traffic one way. Where technically feasible, the Parties may make available to each other two-way trunks for the reciprocal exchange of combined Local Traffic and IntraLATA toll traffic. In such case, each Party will provide to each other its Percentage of Local Use (PLU) for billing purposes. If either Party questions the accuracy of the other’s PLU, that issue may be included in a verification review as provided in §32.0 of the General Terms and Conditions. If at any time during the term of this Agreement, the average monthly number of minutes of use (combined Local Traffic and IntraLATA toll traffic) terminated by either Party on the network of the other exceeds the generally accepted engineering practices as mutually agreed to by the Parties, the Party on whose network those minutes have been terminated may elect to require jurisdictionally separate trunks for Local Traffic and IntraLATA toll traffic. 4.1.1.2 Separate trunks will be utilized for connecting AT&T's switch to each 911/E911 tandem, if ALLTEL becomes an E911 provider during the term of this Agreement. 4.1.1.3 Each Party's operator bureau shall accept BLV and BLVI inquiries from the operator bureau of the other Party in order to allow transparent provisioning of BLV/BLVI traffic between the Parties' networks. Each Party shall route BLV/BLVI inquiries between the Parties respective operator bureaus.
View SourceView Similar (4)
Local Traffic and IntraLATA Toll Traffic. Originating on AT&T, Terminating on GTE. AT&T may build trunk groups to GTE using the following representative, but not exclusive, options: (i) from AT&T collocated equipment in a Wire Center to the GTE Tandem; (ii) from AT&T collocated equipment in a GTE Wire Center to the GTE End Office Switch; or (iii) from AT&T 4ESS Switches located at AT&T POPs to the nearest GTE Tandem. Interfaces for these interconnections may be based upon, but not limited to, the following: (i) DS1: from an AT&T-collocated DDM- 2000 to a GTE Central Office Switch; (ii) SONET STS1: from an AT&T-collocated DDM-2000 to an GTE 5ESS®-2000 Central Office Switch and (iii) DS1/DS3: from an AT&T 4ESS Switch at an AT&T POP to a GTE Tandem using new trunk groups on existing facilities.
View Source
Local Traffic and IntraLATA Toll Traffic. (a) The LSP Originating (The LSP to SWBT) When SWBT has a combined local and access tandem in an exchange, IntraLATA Toll Traffic may be combined with the Local Traffic on the same trunk group. When SWBT has more than one combined local and access tandem in an exchange, the LSP shall provide a separate trunk group to each SWBT tandem. When there are separate SWBT access and local tandems in an exchange, a separate local trunk group shall be provided to the local tandem and a separate IntraLATA toll trunk group shall be provided to the access tandem. This trunk group(s) shall be one-way or two-way directionalized outgoing only and will utilize Signaling System 7 (SS7) or multifrequency (MF) protocol signaling. (b) The LSP Terminating (SWBT to LSP) When SWBT has a combined local and access tandem, SWBT shall normally combine the Local and IntraLATA Toll Traffic over a single trunk group to the LSP. When SWBT has a separate access and local tandem in an exchange, a trunk group shall be established from each tandem to the LSP. This trunk group(s) shall be one-way or two-way directionalized incoming only and will utilize SS7 or MF protocol signaling. (c) Direct End Office Trunking The Parties shall establish direct end office primary high usage trunk groups for Local Traffic and/or IntraLATA Toll Traffic when end office traffic requires twelve or more trunks. If LSP has established collocation to the end office, the trunks shall be provisioned over the LSP collocation facility. If the LSP has no collocation facilities, SWBT shall provision the trunks from the NIP to the end office. IntraLATA Toll Traffic shall be provided over a separate trunk group to the SWBT access tandem.
View Source

Related to Local Traffic and IntraLATA Toll Traffic

  • Local Traffic Traffic that is originated by a Customer of one Party on that Party’s network and terminates to a Customer of the other Party on that other Party’s network within Verizon's then current local calling area (including non-optional local calling scope arrangements) as defined in Verizon’s effective Customer Tariffs. A non- optional local calling scope arrangement is an arrangement that provides Customers a local calling scope (Extended Area Service, “EAS”), beyond their basic exchange serving area. Local Traffic does not include optional local calling scope traffic (i.e., traffic that under an optional rate package chosen by the Customer terminates outside of the Customer’s basic exchange serving area). IntraLATA calls originated on a 1+ presubscription basis, or on a casual dialed (10XXX/101XXXX) basis are not considered Local Traffic. Local Traffic does not include any Internet Traffic.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • Transit Traffic 7.2.2.3.1 CenturyLink will accept traffic originated by CLEC’s network and/or its end user(s) for termination to other Telecommunications Carrier’s network and/or its end users that is connected to CenturyLink's Switch. CenturyLink will also terminate traffic from these other Telecommunications Carriers’ network and/or its end users to CLEC’s network and/or its end users. For purposes of the Agreement, transit traffic does not include traffic carried by Interexchange Carriers. That traffic is defined as Jointly Provided Switched Access. 7.2.2.3.2 The Parties involved in transporting transit traffic will deliver calls to each involved network with CCS/SS7 protocol and the appropriate ISUP/TCAP messages to facilitate full Interoperability and Billing functions. 7.2.2.3.3 The originating company is responsible for payment of appropriate rates to the transit company and to the terminating company. The Parties agree to enter into traffic exchange agreements with third party Telecommunications Carriers prior to delivering traffic to be transited to third party Telecommunications Carriers. In the event one Party originates traffic that transits the second Party’s network to reach a third party Telecommunications Carrier with whom the originating Party does not have a traffic exchange agreement, then the originating Party will indemnify, defend and hold harmless the second Party against any and all charges levied by such third party Telecommunications Carrier, including any termination charges related to such traffic and any attorneys fees and expenses. In the case of IntraLATA LEC Toll traffic where CenturyLink is the designated IntraLATA Toll provider for existing LECs, CenturyLink will be responsible for payment of appropriate usage rates. 7.2.2.3.4 When CenturyLink receives an unqueried call from CLEC to a telephone number that has been ported to another local services provider, the transit rate will apply in addition to any query rates. 7.2.2.3.5 In the case of a transit call that terminates in the Local Calling Area but in a different state than the call originated, and the CLEC does not have an agreement with CenturyLink in the state where the transit call terminated, CLEC must execute an agreement for that state if it is a state served by CenturyLink. In the absence of a second agreement, the transit rate in Exhibit A of this Agreement will be billed to the CLEC.

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§▇▇-▇▇▇-▇▇▇, ▇▇-▇▇▇-▇▇▇, ▇▇-▇▇▇-▇▇▇, and ▇▇- ▇▇▇-▇▇▇, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.