Local Traffic, ISP Sample Clauses
Local Traffic, ISP. Bound Traffic, IntraLATA Interexchange Traffic, InterLATA Interexchange Traffic, Transit Traffic or Toll VOIP Traffic
4.1.1 The Parties shall reciprocally terminate Local Traffic, ISP Bound Traffic, IntraLATA Interexchange Traffic, InterLATA Interexchange Traffic, Transit Traffic or Toll VOIP Traffic originating on each other's networks as follows:
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, ISP Bound Traffic, IntraLATA Interexchange Traffic, InterLATA Interexchange Traffic, Transit Traffic or Toll VOIP Traffic. In such case, each Party will provide to each other its Percentage of Local Use (PLU) for billing purposes on a quarterly basis. If a Necessary Factor is not provided, the one already in effect stays in effect. 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. Pending such verification review, the PLU in effect immediately prior to the verification review shall remain in effect. If at any time during the term of this Agreement, the average monthly number of minutes of use (combined Local Traffic, ISP Bound Traffic, IntraLATA Interexchange Traffic, InterLATA Interexchange Traffic, Transit Traffic or Toll VOIP 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, ISP Bound Traffic, IntraLATA Interexchange Traffic, InterLATA Interexchange Traffic, Transit Traffic or Toll VOIP 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.
4.1.2 Neither Party shall utilize the interconnection facilities for delivery of any other type of traffic to the other Party.
Local Traffic, ISP. Bound Traffic or Tandem Transit Traffic delivered by CENTURYLINK through indirect Interconnection as provided in Section 4.4.
Local Traffic, ISP. Bound Traffic, IntraLATA Traffic, InterLATA Traffic, Transit Traffic or Toll VOIP Traffic 30 4.2 Trunking and Facilities 31 5.1 Protective Protocols 31 5.2 Expansive Protocols 31 5.3 Mass Calling 32 2.2 Acknowledgment of Floor Space Availability 45
Local Traffic, ISP. Bound Traffic or Tandem Transit Traffic delivered by MEDIACOM through indirect Interconnection as provided in Section 4.4.
Local Traffic, ISP. Bound Traffic, IntraLATA Traffic exchanged between the Parties, InterLATA Traffic, Transit Traffic or Toll VOIP Traffic
4.1.1 The Parties shall reciprocally terminate Local Traffic, ISP Bound Traffic, IntraLATA Traffic, InterLATA Traffic, Transit Traffic or Toll VOIP Traffic originating on each other's networks as follows:
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, ISP Bound Traffic, IntraLATA Traffic exchanged between the Parties, InterLATA Traffic, Transit Traffic or Toll VOIP Traffic. In such case, each Party will provide to each other its Percentage of Local Use (PLU) for billing purposes on a quarterly basis. If the PLU is not provided, the one already in effect stays in effect. If either Party questions the accuracy of the other’s PLU, that issue may be included in a verification review as provided in §31.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, ISP Bound Traffic, IntraLATA Traffic, InterLATA Traffic, Transit Traffic or Toll VOIP Traffic )