Common use of Identification of ISP-Bound Traffic Clause in Contracts

Identification of ISP-Bound Traffic. Qwest will presume traffic delivered to CLEC that exceeds a 3:1 ratio of terminating (Qwest to CLEC) to originating (CLEC to Qwest) traffic is ISP-Bound traffic. Either Party may rebut this presumption by demonstrating the factual ratio to the Commission. Traffic exchanged that is not ISP- Bound traffic will be considered to be Section 251(b)(5) traffic. The provisions in this Section apply regardless how the ISP-Bound traffic is determined.

Appears in 11 contracts

Samples: Interconnection Agreement, Interconnection Agreement, Interconnection Agreement

AutoNDA by SimpleDocs

Identification of ISP-Bound Traffic. Qwest will presume traffic delivered to CLEC that exceeds a 3:1 ratio of terminating (Qwest to CLEC) to originating (CLEC to Qwest) traffic is ISP-Bound bound traffic. Either Party may rebut this presumption by demonstrating the factual ratio to the Commission. Traffic exchanged that is not ISP- Bound bound traffic will be considered to be Section 251(b)(5) traffic. The provisions in this Section apply regardless how the ISP-Bound traffic is determined.)

Appears in 9 contracts

Samples: Interconnection Agreement, Interconnection Agreement, Interconnection Agreement

AutoNDA by SimpleDocs

Identification of ISP-Bound Traffic. Qwest will presume traffic delivered to CLEC that exceeds a 3:1 ratio of terminating (Qwest to CLEC) to originating (CLEC to Qwest) traffic is ISP-Bound traffic. Either Party may rebut this presumption by demonstrating the factual ratio to the Commission. Traffic exchanged that is not ISP- ISP-Bound traffic will be considered to be Section 251(b)(5) traffic. The provisions in this Section apply regardless how the ISP-Bound traffic is determined.

Appears in 1 contract

Samples: Interconnection Agreement

Time is Money Join Law Insider Premium to draft better contracts faster.