Optical Telecommunications, Inc.

More documents

Recommendations

Info

Version: 2Q05 Standard ICA 07/06/05 Attachment 3 Page 9 4.10.2 BellSouth Access Tandem Interconnection. BellSouth 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.2.1 Basic Architecture. In the basic architecture, OTI’s originating Local Traffic, ISP- Bound Traffic and IntraLATA Toll Traffic and originating and terminating Transit Traffic is transported on a single two-way trunk group between OTI and BellSouth Access Tandem(s) within a LATA to provide Intratandem Access. This trunk group carries Transit Traffic between OTI and ICOs, IXCs, other CLECs, CMRS providers that have a Meet Point Billing (MPB) arrangement with BellSouth, and other network providers with which OTI desires to exchange traffic. This trunk group also carries OTI originated Transit Traffic transiting a single BellSouth Access Tandem destined to third party tandems such as an ICO tandem or other CLEC tandem. BellSouth originated Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic is transported on a separate single one-way trunk group terminating to OTI. The LERG contains current routing and tandem serving arrangements. The basic Architecture is illustrated in Exhibit B. 4.10.2.2 One-Way Trunk Group Architecture. In one-way trunk group architecture, the Parties interconnect using three (3) separate trunk groups. A one-way trunk group provides Intratandem Access for OTI-originated Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic destined for BellSouth End Users. A second one-way trunk group carries BellSouth-originated Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic destined for OTI End Users. A two-way trunk group provides Intratandem Access for OTI’s originating and terminating Transit Traffic. This trunk group carries Transit Traffic between OTI and ICOs, IXCs, other CLECs, CMRS providers that have a MPB arrangement with BellSouth, and other network providers with which OTI exchanges traffic. This trunk group also carries OTI originated Transit Traffic transiting a single BellSouth Access Tandem destined to third party tandems such as an ICO tandem or other CLEC tandem. BellSouth originated Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic is transported on a separate single one-way trunk group terminating to OTI. The LERG contains current routing and tandem serving arrangements. The one-way trunk group architecture is illustrated in Exhibit C. 4.10.2.3 Two-Way Trunk Group Architecture. The two-way trunk group Architecture establishes one (1) two-way trunk group to provide Intratandem Access for the exchange of Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic between OTI and BellSouth. In addition, a separate two-way transit trunk group must be established for OTI’s originating and terminating Transit Traffic. This trunk group carries Transit Traffic between OTI and ICOs, IXCs, other CLECs, CMRS providers that have a MPB arrangement with BellSouth, and other network providers with which OTI exchanges traffic. This trunk group also carries OTI originated Transit Traffic transiting a single BellSouth Access Tandem destined to CCCS 110 of 261
Version: 2Q05 Standard ICA 07/06/05 Attachment 3 Page 10 third party tandems such as an ICO tandem or other CLEC tandem. BellSouth originated traffic may, in order to prevent or remedy traffic blocking situations, be transported on a separate single one-way trunk group terminating to OTI. However, where OTI is responsive in a timely manner to BellSouth’s transport needs for its originated traffic, BellSouth originating traffic will be placed on the two-way Local Traffic trunk group carrying ISP-Bound Traffic and IntraLATA Toll Traffic. The LERG contains current routing and tandem serving arrangements. The two-way trunk group architecture is illustrated in Exhibit D. 4.10.2.4 Supergroup Architecture. In the supergroup architecture, the Parties’ Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic and OTI’s Transit Traffic are exchanged on a single two-way trunk group between OTI and BellSouth to provide Intratandem Access to OTI. This trunk group carries Transit Traffic between OTI and ICOs, IXCs, other CLECs, CMRS providers that have a MPB arrangement with BellSouth, and other network providers with which OTI desires to exchange traffic. This trunk group also carries OTI originated Transit Traffic transiting a single BellSouth Access Tandem destined to third party tandems such as an ICO tandem or other CLEC tandem. BellSouth originated traffic may, in order to prevent or remedy traffic blocking situations, be transported on a separate single one-way trunk group terminating to OTI. However, where OTI is responsive in a timely manner to BellSouth’s transport needs for its originated traffic, BellSouth originating traffic will be placed on the Supergroup. Other trunk groups for operator services, directory assistance, emergency services and intercept must be established pursuant to the applicable BellSouth tariff if service is requested. The LERG contains current routing and tandem serving arrangements. The supergroup architecture is illustrated in Exhibit E. 4.10.2.5 Multiple Tandem Access (MTA) Interconnection 4.10.2.5.1 Where OTI does not choose access tandem interconnection at every BellSouth Access Tandem within a LATA, OTI must utilize BellSouth’s MTA interconnection. To utilize MTA OTI must establish an interconnection trunk group(s) at a minimum of one (1) BellSouth Access Tandem within each LATA as required. BellSouth will route OTI’s originated Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic for LATA wide transport and termination. OTI must also establish an interconnection trunk group(s) at all BellSouth Access Tandems where OTI NXXs are homed as described in Section 4.2.1 above. If OTI does not have NXXs homed at any particular BellSouth Access Tandem within a LATA and elects not to establish an interconnection trunk group(s) at such BellSouth Access Tandem, OTI can order MTA in each BellSouth Access Tandem within the LATA where it does have an interconnection trunk group(s) and BellSouth will terminate OTI’s Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic to End Users served through those BellSouth Access Tandems where OTI does not have an interconnection trunk group(s). MTA shall be provisioned in accordance with BellSouth’s Ordering Guidelines. CCCS 111 of 261
Page 1 and 2:
BELL BELLSOUTH BELL BELL BELL Optic
Page 3 and 4:
General Terms and Conditions Versio
Page 5 and 6:
Version: 2Q05 Standard ICA 07/06/05
Page 7 and 8:
Page 9 and 10:
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
19 Notices Version: 2Q05 Standard I
Page 21 and 22:
Page 23 and 24:
CCCS 23 of 261
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Attachment 1 Page 16 Exhibit B modu
Page 41 and 42:
Page 43 and 44:
RESALE DISCOUNTS & RATES - Florida
Page 45 and 46:
Version: 2Q05 Standard ICA - New 07
Page 47 and 48:
Page 49 and 50:
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
and 4-wire UVL) (Designed) Unbundle
Page 57 and 58:
Page 59 and 60: Version: 2Q05 Standard ICA - New 07
Page 71 and 72: 3.5 Maintenance - Line Splitting -
Page 87 and 88: UNBUNDLED NETWORK ELEMENTS-Florida
Page 99 and 100: UNBUNDLED NETWORK ELEMENTS - Florid
Page 101 and 102: UNBUNDLED NETWORK ELEMENTS - Florid
Page 103 and 104: Version: 2Q05 Standard ICA 07/06/05
Page 109: Version: 2Q05 Standard ICA 07/06/05
Page 123 and 124: 9.2 The rates, terms and conditions
Page 125 and 126: 11.3.3.3 Signaling Network Manageme
Page 131 and 132: LOCAL INTERCONNECTION - Florida CAT
Page 139 and 140: 3.3 Shared Caged Collocation Versio
Page 143 and 144: 4. Occupancy Version: 2Q05 Standard
Page 161 and 162:
8.7 Power Version: 2Q05 Standard IC
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Removing or disturbing building mat
Page 177 and 178:
COLLOCATION - Florida CATEGORY RATE
Page 179 and 180:
COLLOCATION - Florida CATEGORY RATE
Page 181 and 182:
Page 183 and 184:
1. Scope of Attachment Version: 2Q0
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
9.2 OTI shall maintain the followin
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
ENVIRONMENTAL CATEGORIES Disposal o
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
CMDS - Florida CATEGORY RATE ELEMEN
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
CONTENTS Version: 2Q05 Standard ICA
Page 251 and 252:
3.1 SITE CONTROL Version: 2Q05 Stan
Page 253 and 254:
Page 255 and 256:
5.3 COMBINED OUTAGE (CLEC AND BELLS
Page 257 and 258:
BONA FIDE REQUEST AND NEW BUSINESS
Page 259 and 260:
Page 261:
show all

Optical Telecommunications, Inc.

Create successful ePaper yourself

Delete template?

Save as template?