09.08.2013 Views

Bright House Networks Information Services ... - AT&T Clec Online

Bright House Networks Information Services ... - AT&T Clec Online

Bright House Networks Information Services ... - AT&T Clec Online

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Attachment 3<br />

Page 16<br />

LATA. ISP-bound traffic is subject to compensation to the extent provided by the<br />

FCC in its Order on Remand and Report and Order, CC Docket Nos. 96-98, FCC<br />

01-31 (released April 27, 2001) (“ISP Remand Order”).<br />

7.1.3 Notwithstanding the definitions of Local Traffic and ISP-bound traffic above, and<br />

pursuant to the FCC’s Order on Remand and Report and Order in CC Docket 99-<br />

68 released April 27, 2001 (“ISP Order on Remand”), AT&T and BHN agree to<br />

the rebuttable presumption that all combined circuit switched Local and ISPbound<br />

Traffic delivered to AT&T or BHN that exceeds a 3:1 ratio of terminating<br />

to originating traffic on a statewide basis shall be considered ISP-bound traffic for<br />

compensation purposes. AT&T and BHN further agree to the rebuttable<br />

presumption that all combined circuit switched Local and ISP-bound Traffic<br />

delivered to AT&T or BHN that does not exceed a 3:1 ratio of terminating to<br />

originating traffic on a statewide basis shall be considered Local Traffic for<br />

compensation purposes.<br />

7.1.4 Neither Party shall pay compensation to the other Party for per minute of use rate<br />

elements associated with the Call Transport and Termination of Local Traffic or<br />

ISP-bound Traffic.<br />

7.1.4.1 The elemental rates set forth in Exhibit A of this Agreement shall apply<br />

throughout the term of this Agreement for Multiple Tandem Access, as described<br />

in Section 4.10.1.5 above, and Transit Traffic, as described in Section 7.6 below.<br />

7.1.5 Neither Party shall represent Switched Access Traffic as Local Traffic or ISPbound<br />

Traffic for purposes of determining compensation for the call.<br />

7.1.6 If BHN assigns NPA/NXXs to specific AT&T rate centers within the LATA and<br />

assigns numbers from those NPA/NXXs to BHN end users physically located<br />

outside of that LATA, AT&T traffic originating from within the LATA where the<br />

NPA/NXXs are assigned and delivered to a BHN customer physically located<br />

outside of such LATA, shall not be deemed Local Traffic. Further, BHN agrees<br />

to identify such interLATA traffic to AT&T and to compensate AT&T for<br />

originating and transporting such interLATA traffic to BHN at AT&T’s switched<br />

access tariff rates. This section is not intended to conflict with the definition of<br />

Local Traffic set forth in Section 7.1.1 above.<br />

7.2 If BHN does not identify such interLATA traffic to AT&T, to the best of AT&T’s<br />

ability AT&T will determine which whole BHN NPA/NXXs on which to charge<br />

the applicable rates for originating network access service as reflected in AT&T’s<br />

Access Service Tariff. AT&T shall make appropriate billing adjustments if BHN<br />

can provide sufficient information for AT&T to determine whether or not said<br />

traffic is Local Traffic.<br />

7.3 Jurisdictional Reporting<br />

7.3.1 Percent Local Use. Each Party shall report to the other a Percent Local Usage<br />

(“PLU”) factor. The application of the PLU will determine the amount of local<br />

minutes to be billed to the other Party. For purposes of developing the PLU, each<br />

Party shall consider every local call and every long distance call, excluding<br />

Transit Traffic. Each Party shall update its PLU on the first of January, April,<br />

CCCS 117 of 369

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!