09.08.2013 Views

TC Systems, Inc. South Carolina - AT&T Clec Online

TC Systems, Inc. South Carolina - AT&T Clec Online

TC Systems, Inc. South Carolina - AT&T Clec Online

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

6/23/04<br />

Attachment 3<br />

Page 41<br />

the customer’s behalf to provide functions that make use of communications<br />

services.<br />

14.12.1 Exchange Access Traffic includes the following category of IP Enabled Service: 1+<br />

interLATA calls that: (1) use ordinary customer premises equipment (such as a<br />

traditional telephone) with no enhanced functionality; (2) originate and terminate on<br />

the public switched telephone network (PSTN); (3) undergo no Net Protocol<br />

Conversion as defined in 14.12.2 below; and (4) provide no enhanced functionality<br />

to end users that result from the provider’s use of IP technology. To the extent that<br />

the FCC finds that this type of IP Enabled Service is not exchange access service, or<br />

is not otherwise subject to access charges, then the Parties shall amend the<br />

Agreement in accordance with Section 9 of the General Terms and Conditions.<br />

14.12.2 A “Net Protocol Conversion” occurs when a call originates in one protocol (e.g. IP)<br />

and terminates in another protocol (e.g. TDM).<br />

14.12.3 For traffic that originates from a traditional telephone device and terminates to a<br />

non-telecommunications device (“Phone-to-Computer”) or originates from a nontelecommunications<br />

device and terminates to a traditional telephone device<br />

(“Computer-to-Phone”), the Parties have been unable to agree as to whether Voice<br />

over Internet Protocol (“VOIP”) transmissions which cross local calling area<br />

boundaries constitute Exchange Access Traffic. Notwithstanding the foregoing, and<br />

without waiving any rights with respect to either Party’s position as to the<br />

jurisdictional nature of VOIP, the Parties agree to abide by any effective and<br />

applicable FCC and/or state commission rules and orders regarding the nature of<br />

such traffic and the compensation payable by the Parties for such traffic, if any.<br />

14.13 The Parties have been unable to agree as to the appropriate compensation for calls<br />

which originate in a LATA and terminate to a physical location outside of that<br />

LATA but to a number assigned to a rate center within that LATA. However,<br />

without prejudice to either Party’s position concerning the application of reciprocal<br />

compensation or access charges to such traffic, the Parties agree for purposes of this<br />

Agreement only and subject to the Parties’ agreement to the terms of Sections 14.7,<br />

and on an interim basis until the FCC issues an Order addressing this issue, neither<br />

Party shall bill the other reciprocal compensation, intercarrier compensation or<br />

switched access in connection with the exchange of any traffic as described in the<br />

first sentence of this paragraph. Once the FCC issues an Effective Order addressing<br />

this issue, the Parties agree to amend this Interconnection Agreement to comply with<br />

the Order on a prospective basis only within thirty (30) days of either Party’s written<br />

request. No “true-up” shall be required in connection with such an Effective Order.<br />

Nothing in this Section 5.3.4 is intended to change the way that the Parties treat ISPbound<br />

traffic in accordance with the FCC’s ISP Order on Remand.<br />

14.14 Billing POI Compensation. If Bell<strong>South</strong> establishes a BPOI, <strong>TC</strong> SYTEMS agrees<br />

to pay to Bell<strong>South</strong> Interoffice Dedicated Transport and any associated Multiplexing<br />

for Bell<strong>South</strong> to transport Bell<strong>South</strong>’s originated Local and ISP-bound Traffic over<br />

CCCS 217 of 433

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

Saved successfully!

Ooh no, something went wrong!