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

Attachment 3
Page 7
4.9 Each Party shall order interconnection trunks and trunk group including trunk and
trunk group augmentations via the ASR process. A Firm Order Confirmation
(FOC) shall be returned to the ordering Party, after receipt of a valid, error free
ASR, within the timeframes set forth in each state’s applicable Performance
Measures. The ordering party shall be timely notified in the event that an ASR is
deemed to be invalid. In addition, the receiving Party will issue a Design
Layout Record (“DLR”), if appropriate, to the ordering Party within the same
timeframe as the FOC is returned if the Party has a mechanized receipt process. If
the FOC and/or the DLR are not received within each state’s applicable
timeframe, then both Parties agree to escalate within the respective network and
operations organizations as appropriate. Notwithstanding the foregoing, blocking
situations and projects shall be managed through AT&T’s Local Interconnection
Switching Center (LISC) Project Management Group and BHN’s equivalent
trunking group, and FOCs for such orders shall be returned in the timeframes
applicable to the project. A project is defined as (1) a new trunk group or (2) a
request for more than 192 trunks on a single or multiple group(s) in a given
AT&T local calling area, or (3) new switch deployments for switches deployed by
either Party. The Parties agree to jointly plan and coordinate new projects.
4.10 Interconnection Trunk Groups for Exchange of Local Traffic and Transit
Traffic
Upon mutual agreement of the Parties in a joint planning meeting, the Parties’
shall exchange Local Traffic on two-way interconnection trunk group(s) with the
quantity of trunks being mutually determined and the provisioning being jointly
coordinated. Furthermore, the Parties shall agree upon the IP(s) for two-way
interconnection trunk groups transporting both Parties’ Local Traffic. BHN shall
order such two-way trunks via the Access Service Request (ASR) process.
AT&T will use the Trunk Group Service Request (TGSR) to request changes in
trunking. Furthermore, semi-annually the Parties shall jointly review trunk
performance and AT&T shall assist in the development of BHN’s trunking
forecast.. The Parties’ use of two-way interconnection trunk groups for the
transport of Local Traffic between the Parties does not preclude either Party from
establishing additional one-way interconnection trunks for the delivery of its
originated Local Traffic to the other Party.
4.10.1 AT&T Access Tandem Interconnection
AT&T access tandem interconnection at a single access tandem provides access
to those end offices subtending that access tandem (“Intratandem Access”).
Access tandem interconnection is available for any of the following access
tandem architectures.
4.10.1.1 Basic Architecture
In the basic architecture, BHN’s originating Local Traffic and originating and
terminating Transit Traffic is transported on a single two-way trunk group
between BHN and AT&T access tandem(s) within a LATA to provide
Intratandem Access. This trunk group carries Transit Traffic between BHN and
Independent Companies, Interexchange Carriers, other CLECs, CMRS providers
CCCS 108 of 369