09.08.2013 Views

AT&T Wholesale Agreement - AT&T Clec Online

AT&T Wholesale Agreement - AT&T Clec Online

AT&T Wholesale Agreement - 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.

Page 57 of 94<br />

Page 57 of 105<br />

Attachment 02 – Network Interconnection/AT&T LOUISIANA<br />

Page 10 of 18<br />

Cricket Communications, Inc.<br />

Version: 3Q08 – Two-Way CMRS ICA – Wireless 02/12/09<br />

twenty (20) business day period, AT&T LOUISIANA will attempt to contact WSP to schedule a joint<br />

planning discussion. If WSP will not agree to meet within an additional five (5) business days and<br />

present adequate reason for keeping Trunks operational, AT&T LOUISIANA will issue an ASR or<br />

WSR, as applicable, to resize the Interconnection Trunks and Facilities.<br />

3.5.6 Trunk servicing responsibilities for Operator Services trunks used for stand-alone Operator Service or<br />

Directory Assistance are the sole responsibility of WSP.<br />

3.5.7 Utilization:<br />

3.5.7.1 Under utilization of Interconnection Trunk Groups exists when provisioned capacity is greater than<br />

the current need. Under utilization will be addressed in the following manner:<br />

3.5.7.2 If utilization of an Interconnection Trunk Group falls below sixty-five percent (65%) of CCS capacity<br />

for any three (3) consecutive months, either Party may request the issuance of an order to resize<br />

the Interconnection Trunk Group. In all cases, grade of service objectives shall be maintained.<br />

Cricket reserves its rights to modify this Section 3.5.7.2 consistent with the Commission’s findings<br />

in a final and effective order in Docket No. U-31350 (“Commission Order”) in accordance with<br />

Sections 39.2 and 39.3 of the General Terms and Conditions. Notwithstanding the fact that such a<br />

Commission Order may not constitute Intervening Law as set forth in Section 21 of the General<br />

Terms and Conditions of this <strong>Agreement</strong>, the Parties will implement any such modification via an<br />

amendment to this <strong>Agreement</strong> pursuant to the timelines and procedures set forth therein. Both<br />

Parties reserve their rights to modify this language pursuant to any appeals resulting from Docket<br />

No. U-31350.<br />

3.5.7.3 Either Party may send a TGSR to the other Party to trigger changes to the Interconnection Trunk<br />

Groups, based on capacity assessment. Upon receipt of a TGSR, the receiving Party will issue an<br />

ASR or WSR, as applicable, to the other Party, within twenty (20) business days after receipt of the<br />

TGSR.<br />

3.5.7.4 Upon review of the TGSR, if a Party does not agree with the resizing, the Parties will schedule a<br />

joint planning discussion within twenty (20) business days of the receiving Party’s receipt of the<br />

TGSR, to resolve and mutually agree to the disposition of the TGSR. If the Parties cannot agree<br />

on the resizing at the joint planning discussion, the Parties may invoke the dispute resolution<br />

provisions of this <strong>Agreement</strong>.<br />

3.5.7.5 If the Parties cannot agree on the changes to the Interconnection Trunk Groups at the joint<br />

planning discussion, then either Party may invoke the dispute resolution provisions of this<br />

<strong>Agreement</strong>. Further, if AT&T LOUISIANA sent the TGSR to WSP, and WSP does not schedule a<br />

discussion with AT&T LOUISIANA within the twenty (20) business day period, then AT&T<br />

LOUISIANA will attempt to contact WSP to schedule a joint planning session. If WSP will not<br />

agree to meet within an additional five (5) business days and present adequate reason for keeping<br />

trunks operational, AT&T LOUISIANA reserves the right to issue ASRs or WSRs, as applicable, to<br />

resize the Interconnection Trunk Groups.<br />

3.5.8 Design Blocking Criteria:

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

Saved successfully!

Ooh no, something went wrong!