Common use of Interconnection Points and Methods, and Interconnection Activation Dates Clause in Contracts

Interconnection Points and Methods, and Interconnection Activation Dates. III.2.1 In each LATA identified on Schedule 2.1, Requesting Carrier and Ameritech shall Interconnect their networks at the correspondingly identified Ameritech and Requesting Carrier Central Office(s) on Schedule 2.1 for the transmission and routing within that LATA of Telephone Exchange Service traffic and Exchange Access traffic pursuant to Section 251(c)(2) of the Act. Requesting Carrier’s point of Interconnection must be in an Ameritech local service area in the LATA in which Requesting Carrier is providing service. An Interconnection Activation Date not established and set forth on Schedule 2.1 as of the Effective Date shall be determined in accordance with the procedures set forth in Section 3.4.3. III.2.2 Interconnection in each LATA shall be accomplished at any technically feasible point within the Parties’ networks through either (i) Collocation in Ameritech’s Central Offices as provided in Article XII or (ii) any other Interconnection method to which the Parties may agree in advance of the applicable Interconnection Activation Date for a given LATA and which is consistent with the Act, including a Fiber-Meet as provided in Section 3.3. III.2.3 If Requesting Carrier elects Collocation as an Interconnection method, or elects a network architecture that requires Ameritech to Interconnect with Requesting Carrier’s facilities via Collocation, then Requesting Carrier must not less than one hundred twenty five (125) days prior to its applicable Interconnection Activation Date notify Ameritech whether Requesting Carrier wishes Ameritech to Interconnect pursuant to subsection (a) or (b) below. (a) Requesting Carrier shall (i) provide the transport (whether through leased or owned facilities) of Ameritech’s traffic from the point of Interconnection to Requesting Carrier’s Central Office, (ii) not charge Ameritech for such transport and (iii) provide Ameritech with capacity to meet Ameritech’s forecasted needs. If Requesting Carrier does provide Ameritech transport as provided in this subsection (a) but then either requests Ameritech to utilize its own facilities or does not provide Ameritech capacity to meet Ameritech’s forecasted needs, then Requesting Carrier shall (x) provide Ameritech not less than two hundred (200) days’ notice prior to the date Ameritech must provide its own facilities for new trunks, (y) compensate Ameritech for the costs incurred by Ameritech to rearrange its network and (z) provide Ameritech Collocation as provided in subsection (b) below. (b) If Requesting Carrier does not elect to provide Ameritech transport as provided in subsection (a) above, then Requesting Carrier shall provide to Ameritech Collocation in Requesting Carrier’s Central Office(s) for purposes of that Interconnection on a nondiscriminatory basis and on rates, terms and conditions that are no less favorable than (i) Ameritech provides to Requesting Carrier pursuant to the terms and conditions of this Agreement and (ii) Requesting Carrier provides to other similarly situated Telecommunications Carriers. III.2.4 Unless otherwise agreed by the Parties, the Parties shall designate the Central Office Requesting Carrier has identified as its initial Routing Point in the LATA as the Requesting Carrier Interconnection Central Office (“RICO”) in that LATA and shall designate the Ameritech Tandem Central Office that is designated as the home Tandem (based on the LERG) for the Ameritech Wire Center in which the Requesting Carrier’s Central Office is located, as the Ameritech Interconnection Central Office (“AICO”) in that LATA. III.2.5 Requesting Carrier’s point of Interconnection must be within an Ameritech Wire Center in the LATA in which Requesting Carrier provides service. III.2.6 Requesting Carrier shall order all trunks and facilities used to establish Interconnection, trunking (for both the Local/IntraLATA Trunks and Access Toll Connecting Trunks), signaling and 9-1-1 Service (as described in Section 3.9) by submitting to Ameritech an electronic Access Service Request including BDS Telis and, as soon as available, an electronic service order via the Provisioning EI.

Appears in 4 contracts

Samples: Interconnection Agreement, Interconnection Agreement, Interconnection Agreement

AutoNDA by SimpleDocs

Interconnection Points and Methods, and Interconnection Activation Dates. III.2.1 3.2.1 In each LATA identified on Schedule 2.1, Requesting Carrier and Ameritech shall Interconnect their networks at the correspondingly identified Ameritech and Requesting Carrier Central Office(s) on Schedule 2.1 for the transmission and routing within that LATA of Telephone Exchange Service traffic and Exchange Access traffic pursuant to Section 251(c)(2) of the Act. Requesting Carrier’s point of Interconnection must be in an Ameritech local service area in the LATA in which Requesting Carrier is providing service. An Interconnection Activation Date not established and set forth on Schedule 2.1 as of the Effective Date shall be determined in accordance with the procedures set forth in Section 3.4.3. III.2.2 3.2.2 Interconnection in each LATA shall be accomplished at any technically feasible point within the Parties’ networks through either (i) Collocation in Ameritech’s Central Offices as provided in Article XII or (ii) any other Interconnection method to which the Parties may agree in advance of the applicable Interconnection Activation Date for a given LATA and which is consistent with the Act, including a Fiber-Meet as provided in Section 3.3. III.2.3 3.2.3 If Requesting Carrier elects Collocation as an Interconnection method, or elects a network architecture that requires Ameritech to Interconnect with Requesting Carrier’s facilities via Collocation, then Requesting Carrier must not less than one hundred twenty five (125) days prior to its applicable Interconnection Activation Date notify Ameritech whether Requesting Carrier wishes Ameritech to Interconnect pursuant to subsection (a) or (b) below. (a) Requesting Carrier shall (i) provide the transport (whether through leased or owned facilities) of Ameritech’s traffic from the point of Interconnection to Requesting Carrier’s Central Office, (ii) not charge Ameritech for such transport and (iii) provide Ameritech with capacity to meet Ameritech’s forecasted needs. If Requesting Carrier does provide Ameritech transport as provided in this subsection (a) but then either requests Ameritech to utilize its own facilities or does not provide Ameritech capacity to meet Ameritech’s forecasted needs, then Requesting Carrier shall (x) provide Ameritech not less than two hundred (200) days’ notice prior to the date Ameritech must provide its own facilities for new trunks, (y) compensate Ameritech for the costs incurred by Ameritech to rearrange its network and (z) provide Ameritech Collocation as provided in subsection (b) below. (b) If Requesting Carrier does not elect to provide Ameritech transport as provided in subsection (a) above, then Requesting Carrier shall provide to Ameritech Collocation in Requesting Carrier’s Central Office(s) for purposes of that Interconnection on a nondiscriminatory basis and on rates, terms and conditions that are no less favorable than (i) Ameritech provides to Requesting Carrier pursuant to the terms and conditions of this Agreement and (ii) Requesting Carrier provides to other similarly situated Telecommunications Carriers. III.2.4 3.2.4 Unless otherwise agreed by the Parties, the Parties shall designate the Central Office Requesting Carrier has identified as its initial Routing Point in the LATA as the Requesting Carrier Interconnection Central Office (“RICO”) in that LATA and shall designate the Ameritech Tandem Central Office that is designated as the home Tandem (based on the LERG) for the Ameritech Wire Center in which the Requesting Carrier’s Central Office is located, as the Ameritech Interconnection Central Office (“AICO”) in that LATA. III.2.5 3.2.5 Requesting Carrier’s point of Interconnection must be within an Ameritech Wire Center in the LATA in which Requesting Carrier provides service. III.2.6 3.2.6 Requesting Carrier shall order all trunks and facilities used to establish Interconnection, trunking (for both the Local/IntraLATA Trunks and Access Toll Connecting Trunks), signaling and 9-1-1 Service (as described in Section 3.9) by submitting to Ameritech an electronic Access Service Request including BDS Telis and, as soon as available, an electronic service order via the Provisioning EI.

Appears in 2 contracts

Samples: Interconnection Agreement, Interconnection Agreement

Interconnection Points and Methods, and Interconnection Activation Dates. III.2.1 In each LATA identified on Schedule 2.1, Requesting Carrier and Ameritech shall Interconnect their networks at the correspondingly identified Ameritech and Requesting Carrier Central Office(s) on Schedule 2.1 for the transmission and routing within that LATA of Telephone Exchange Service traffic and Exchange Access traffic pursuant to Section 251(c)(2) of the Act. Requesting Carrier’s point of Interconnection must be in an Ameritech local service area in the LATA in which Requesting Carrier is providing service. An Interconnection Activation Date not established and set forth on Schedule 2.1 as of the Effective Date shall be determined in accordance with the procedures set forth in Section 3.4.3. III.2.2 Interconnection in each LATA shall be accomplished at any technically feasible point within the Parties’ networks through either (i) Collocation in Ameritech’s Central Offices as provided in Article XII or (ii) any other Interconnection method to which the Parties may agree in advance of the applicable Interconnection Activation Date for a given LATA and which is consistent with the Act, including a Fiber-Meet as provided in Section 3.3. III.2.3 If Requesting Carrier elects Collocation as an Interconnection method, or elects a network architecture that requires Ameritech to Interconnect with Requesting Carrier’s facilities via Collocation, then Requesting Carrier must not less than one hundred twenty five (125) days prior to its applicable Interconnection Activation Date notify Ameritech whether Requesting Carrier wishes Ameritech to Interconnect pursuant to subsection (a) or (b) below. (a) Requesting Carrier shall (i) provide the transport (whether through leased or owned facilities) of Ameritech’s traffic from the point of Interconnection to Requesting Carrier’s Central Office, (ii) not charge Ameritech for such transport and (iii) provide Ameritech with capacity to meet Ameritech’s forecasted needs. If Requesting Carrier does provide Ameritech transport as provided in this subsection (a) but then either requests Ameritech to utilize its own facilities or does not provide Ameritech capacity to meet Ameritech’s forecasted needs, then Requesting Carrier shall (x) provide Ameritech not less than two hundred (200) days’ notice prior to the date Ameritech must provide its own facilities for new trunks, (y) compensate Ameritech for the costs incurred by Ameritech to rearrange its network and (z) provide Ameritech Collocation as provided in subsection (b) below. (b) If Requesting Carrier does not elect to provide Ameritech transport as provided in subsection (a) above, then Requesting Carrier shall provide to Ameritech Collocation in Requesting Carrier’s Central Office(s) for purposes of that Interconnection on a nondiscriminatory basis and on rates, terms and conditions that are no less favorable than (i) Ameritech provides to Requesting Carrier pursuant to the terms and conditions of this Agreement and (ii) Requesting Carrier provides to other similarly situated Telecommunications Carriers. III.2.4 Unless otherwise agreed by the Parties, the Parties shall designate the Central Office Requesting Carrier has identified as its initial Routing Point in the LATA as the Requesting Carrier Interconnection Central Office (“RICONICO”) in that LATA and shall designate the Ameritech Tandem Central Office that is designated as the home Tandem (based on the LERG) for the Ameritech Wire Center in which the Requesting Carrier’s Central Office is located, as the Ameritech Interconnection Central Office (“AICO”) in that LATA. III.2.5 Requesting Carrier’s point of Interconnection must be within an Ameritech Wire Center in the LATA in which Requesting Carrier provides service. III.2.6 Requesting Carrier shall order all trunks and facilities used to establish Interconnection, trunking (for both the Local/IntraLATA Trunks and Access Toll Connecting Trunks), signaling and 9-1-1 Service (as described in Section 3.9) by submitting to Ameritech an electronic Access Service Request including BDS Telis and, as soon as available, an electronic service order via the Provisioning EI.

Appears in 1 contract

Samples: Interconnection Agreement

Interconnection Points and Methods, and Interconnection Activation Dates. III.2.1 3.2.1 In each LATA identified on Schedule 2.1, Requesting Carrier and Ameritech shall Interconnect their networks at the correspondingly identified Ameritech and Requesting Carrier Central Office(s) on Schedule 2.1 for the transmission and routing within that LATA of Telephone Exchange Service traffic and Exchange Access traffic pursuant to Section 251(c)(2) of the Act. Requesting Carrier’s point of Interconnection must be in an Ameritech local service area in the LATA in which Requesting Carrier is providing service. An Interconnection Activation Date not established and set forth on Schedule 2.1 as of the Effective Date shall be determined in accordance with the procedures set forth in Section 3.4.3. III.2.2 3.2.2 Interconnection in each LATA shall be accomplished at any technically feasible point within the Parties’ networks through either (i) Collocation in Ameritech’s Central Offices as provided in Article XII or (ii) any other Interconnection method to which the Parties may agree in advance of the applicable Interconnection Activation Date for a given LATA and which is consistent with the Act, including a Fiber-Meet as provided in Section 3.3. III.2.3 3.2.3 If Requesting Carrier elects Collocation as an Interconnection method, or elects a network architecture that requires Ameritech to Interconnect with Requesting Carrier’s facilities via Collocation, then Requesting Carrier must not less than one hundred twenty five (125) days prior to its applicable Interconnection Activation Date notify Ameritech whether Requesting Carrier wishes Ameritech to Interconnect pursuant to subsection (a) or (b) below. (a) Requesting Carrier shall (i) provide the transport (whether through leased or owned facilities) of Ameritech’s traffic from the point of Interconnection to Requesting Carrier’s Central Office, (ii) not charge Ameritech for such transport and (iii) provide Ameritech with capacity to meet Ameritech’s forecasted needs. If Requesting Carrier does provide Ameritech transport as provided in this 12716496.1 110201 1406C 00650405 subsection (a) but then either requests Ameritech to utilize its own facilities or does not provide Ameritech capacity to meet Ameritech’s forecasted needs, then Requesting Carrier shall (x) provide Ameritech not less than two hundred (200) days’ notice prior to the date Ameritech must provide its own facilities for new trunks, (y) compensate Ameritech for the costs incurred by Ameritech to rearrange its network and (z) provide Ameritech Collocation as provided in subsection (b) below. (b) If Requesting Carrier does not elect to provide Ameritech transport as provided in subsection (a) above, then Requesting Carrier shall provide to Ameritech Collocation in Requesting Carrier’s Central Office(s) for purposes of that Interconnection on a nondiscriminatory basis and on rates, terms and conditions that are no less favorable than (i) Ameritech provides to Requesting Carrier pursuant to the terms and conditions of this Agreement and (ii) Requesting Carrier provides to other similarly situated Telecommunications Carriers. III.2.4 3.2.4 Unless otherwise agreed by the Parties, the Parties shall designate the Central Office Requesting Carrier has identified as its initial Routing Point in the LATA as the Requesting Carrier Interconnection Central Office (“RICO”) in that LATA and shall designate the Ameritech Tandem Central Office that is designated as the home Tandem (based on the LERG) for the Ameritech Wire Center in which the Requesting Carrier’s Central Office is located, as the Ameritech Interconnection Central Office (“AICO”) in that LATA. III.2.5 Requesting Carrier’s point of Interconnection must be within an Ameritech Wire Center in the LATA in which Requesting Carrier provides service. III.2.6 Requesting Carrier shall order all trunks and facilities used to establish Interconnection, trunking (for both the Local/IntraLATA Trunks and Access Toll Connecting Trunks), signaling and 9-1-1 Service (as described in Section 3.9) by submitting to Ameritech an electronic Access Service Request including BDS Telis and, as soon as available, an electronic service order via the Provisioning EI.

Appears in 1 contract

Samples: Interconnection Agreement

Interconnection Points and Methods, and Interconnection Activation Dates. III.2.1 3.2.1 In each LATA identified on Schedule 2.1, Requesting Carrier and Ameritech shall Interconnect their networks at the correspondingly identified Ameritech and Requesting Carrier Central Office(s) on Schedule 2.1 for the transmission and routing within that LATA of Telephone Exchange Service traffic and Exchange Access traffic pursuant to Section 251(c)(225 1 (c)(2) of the Act. Requesting Carrier’s point of Interconnection must be in an Ameritech local service area in the LATA in which Requesting Carrier is providing service. An Interconnection Activation Date not established and set forth on Schedule 2.1 as of the Effective Date shall be determined in accordance with the procedures set forth in Section 3.4.3. III.2.2 3.2.2 Interconnection in each LATA shall be accomplished at any technically feasible point within the Parties’ networks through either (i) Collocation in Ameritech’s Central Offices as provided in Article XII or (ii) any other Interconnection method to which the Parties may agree in advance of the applicable Interconnection Activation Date for a given LATA and which is consistent with the Act, including a Fiber-Meet as provided in Section 3.3. III.2.3 3.2.3 If Requesting Carrier elects Collocation as an Interconnection method, or elects a network architecture that requires Ameritech to Interconnect with Requesting Carrier’s facilities via Collocation, then Requesting Carrier must not less than one hundred twenty five (125) days prior to its applicable Interconnection Activation Date notify Ameritech whether Requesting Carrier wishes Ameritech to Interconnect pursuant to subsection (a) or (b) below. (a) . Requesting Carrier shall (i) provide the transport (whether through leased or owned facilities) of Ameritech’s traffic from the point of Interconnection to Requesting Carrier’s Central Office, (ii) not charge Ameritech for such transport and (iii) provide Ameritech with capacity to meet Ameritech’s forecasted needs. If Requesting Carrier does provide Ameritech transport as provided in this subsection (a) but then either requests Ameritech to utilize its own facilities or does not provide Ameritech capacity to meet Ameritech’s forecasted needs, then Requesting Carrier shall (x) provide Ameritech not less than two hundred (200) days’ notice prior to the date Ameritech must provide its own facilities for new trunks, (y) compensate Ameritech for the costs incurred by Ameritech to rearrange its network and (z) provide Ameritech Collocation as provided in subsection (b) below. (b) . If Requesting Carrier does not elect to provide Ameritech transport as provided in subsection (a) above, then Requesting Carrier shall provide to Ameritech Collocation in Requesting Carrier’s Central Office(s) for purposes of that Interconnection on a nondiscriminatory basis and on rates, terms and conditions that are no less favorable than (i) Ameritech provides to Requesting Carrier pursuant to the terms and conditions of this Agreement and (ii) Requesting Carrier provides to other similarly situated Telecommunications Carriers. III.2.4 3.2.4 Unless otherwise agreed by the Parties, the Parties shall designate the Central Office Requesting Carrier has identified as its initial Routing Point in the LATA as the Requesting Carrier Interconnection Central Office (“RICO”) in that LATA and shall designate the Ameritech Tandem Central Office that is designated as the home Tandem (based on the LERG) for the Ameritech Wire Center in which the Requesting Carrier’s Central Office is located, as the Ameritech Interconnection Central Office (“AICO”) in that LATA.the III.2.5 3.2.5 Requesting Carrier’s point of Interconnection must be within an Ameritech Wire Center in the LATA in which Requesting Carrier provides service. III.2.6 3.2.6 Requesting Carrier shall order all trunks and facilities used to establish Interconnection, trunking (for both the Local/IntraLATA Trunks and Access Toll Connecting Trunks), signaling and 9-1l-1 l Service (as described in Section 3.9) by submitting to Ameritech an electronic Access Service Request including BDS Telis and, as soon as available, an electronic service order via the Provisioning EI.

Appears in 1 contract

Samples: Interconnection Agreement

Interconnection Points and Methods, and Interconnection Activation Dates. III.2.1 3.2.1 In each LATA identified on Schedule 2.1, Requesting Carrier and Ameritech shall Interconnect their networks at the correspondingly identified Ameritech and Requesting Carrier Central Office(s) on Schedule 2.1 for the transmission and routing within that LATA of Telephone Exchange Service traffic and Exchange Access traffic pursuant to Section 251(c)(2) of the Act. Requesting Carrier’s point of Interconnection must be in an Ameritech local service area in the LATA in which Requesting Carrier is providing service. An Interconnection Activation Date not established and set forth on Schedule 2.1 as of the Effective Date shall be determined in accordance with the procedures set forth in Section 3.4.3. III.2.2 3.2.2 Interconnection in each LATA shall be accomplished at any technically feasible point within the Parties’ networks through either (i) Collocation in Ameritech’s Central Offices as provided in Article XII or (ii) any other Interconnection method to which the Parties may agree in advance of the applicable Interconnection Activation Date for a given LATA and which is consistent with the Act, including a Fiber-Meet as provided in Section 3.3. III.2.3 3.2.3 If Requesting Carrier elects Collocation as an Interconnection method, or elects a network architecture that requires Ameritech to Interconnect with Requesting Carrier’s facilities via Collocation, then Requesting Carrier must not less than one hundred twenty five (125) days prior to its applicable Interconnection Activation Date notify Ameritech whether Requesting Carrier wishes Ameritech to Interconnect pursuant to subsection (a) or (b) below. (a) Requesting Carrier shall (i) provide the transport (whether through leased or owned facilities) of Ameritech’s traffic from the point of Interconnection to Requesting Carrier’s Central Office, (ii) not charge Ameritech for such transport and (iii) provide Ameritech with capacity to meet Ameritech’s forecasted needs. If Requesting Carrier does provide Ameritech transport as provided in this subsection (a) but then either requests Ameritech to utilize its own facilities or does not provide Ameritech capacity to meet Ameritech’s forecasted needs, then Requesting Carrier shall (x) provide Ameritech not less than two hundred (200) days’ notice prior to the date Ameritech must provide its own facilities for new trunks, (y) compensate Ameritech for the costs incurred by Ameritech to rearrange its network and (z) provide Ameritech Collocation as provided in subsection (b) below. (b) If Requesting Carrier does not elect to provide Ameritech transport as provided in subsection (a) above, then Requesting Carrier shall provide to Ameritech Collocation in Requesting Carrier’s Central Office(s) for purposes of that Interconnection on a nondiscriminatory basis and on rates, terms and conditions that are no less favorable than (i) Ameritech provides to Requesting Carrier pursuant to the terms and conditions of this Agreement and (ii) Requesting Carrier provides to other similarly situated Telecommunications Carriers. III.2.4 3.2.4 Unless otherwise agreed by the Parties, the Parties shall designate the Central Office Requesting Carrier has identified as its initial Routing Point in the LATA as the Requesting Carrier Interconnection Central Office (“RICO”) in that LATA and shall designate the Ameritech Tandem Central Office that is designated as the home Tandem (based on the LERG) for the Ameritech Wire Center in which the Requesting Carrier’s Central Office is located, as the Ameritech Interconnection Central Office (“AICO”) in that LATA. III.2.5 Requesting Carrier’s point of Interconnection must be within an Ameritech Wire Center in the LATA in which Requesting Carrier provides service. III.2.6 Requesting Carrier shall order all trunks and facilities used to establish Interconnection, trunking (for both the Local/IntraLATA Trunks and Access Toll Connecting Trunks), signaling and 9-1-1 Service (as described in Section 3.9) by submitting to Ameritech an electronic Access Service Request including BDS Telis and, as soon as available, an electronic service order via the Provisioning EI.

Appears in 1 contract

Samples: Interconnection Agreement

AutoNDA by SimpleDocs

Interconnection Points and Methods, and Interconnection Activation Dates. III.2.1 3.2.1 In each LATA identified on Schedule 2.1, Requesting Carrier and Ameritech shall Interconnect their networks at the correspondingly identified Ameritech and Requesting Carrier Central Office(s) on Schedule 2.1 for the transmission and routing within that LATA of Telephone Exchange Service traffic and Exchange Access traffic pursuant to Section 251(c)(2) of the Act. Requesting Carrier’s point of Interconnection must be in an Ameritech local service area in the LATA in which Requesting Carrier is providing service. An Interconnection Activation Date not established and set forth on Schedule 2.1 as of the Effective Date shall be determined in accordance with the procedures set forth in Section 3.4.3. III.2.2 3.2.2 Interconnection in each LATA shall be accomplished at any technically feasible point within the Parties’ networks through either (i) Collocation in Ameritech’s Central Offices as provided in Article XII or (ii) any other Interconnection method to which the Parties may agree in advance of the applicable Interconnection Activation Date for a given LATA and which is consistent with the Act, including a Fiber-Meet as provided in Section 3.3. III.2.3 3.2.3 If Requesting Carrier elects Collocation as an Interconnection method, or elects a network architecture that requires Ameritech to Interconnect with Requesting Carrier’s facilities via Collocation, then Requesting Carrier must not less than one hundred twenty five (125) days prior to its applicable Interconnection Activation Date notify Ameritech whether Requesting Carrier wishes Ameritech to Interconnect pursuant to subsection (a) or (b) below. (a) Requesting Carrier shall (i) provide the transport (whether through leased or owned facilities) of Ameritech’s traffic from the point of Interconnection to Requesting Carrier’s Central Office, (ii) not charge Ameritech for such transport and (iii) provide Ameritech with capacity to meet Ameritech’s forecasted needs. If Requesting Carrier does provide Ameritech transport as provided in this subsection (a) but then either requests Ameritech to utilize its own facilities or does not provide Ameritech capacity to meet Ameritech’s 12716496.1 80509 940C 00650405 forecasted needs, then Requesting Carrier shall (x) provide Ameritech not less than two hundred (200) days’ notice prior to the date Ameritech must provide its own facilities for new trunks, (y) compensate Ameritech for the costs incurred by Ameritech to rearrange its network and (z) provide Ameritech Collocation as provided in subsection (b) below. (b) If Requesting Carrier does not elect to provide Ameritech transport as provided in subsection (a) above, then Requesting Carrier shall provide to Ameritech Collocation in Requesting Carrier’s Central Office(s) for purposes of that Interconnection on a nondiscriminatory basis and on rates, terms and conditions that are no less favorable than (i) Ameritech provides to Requesting Carrier pursuant to the terms and conditions of this Agreement and (ii) Requesting Carrier provides to other similarly situated Telecommunications Carriers. III.2.4 3.2.4 Unless otherwise agreed by the Parties, the Parties shall designate the Central Office Requesting Carrier has identified as its initial Routing Point in the LATA as the Requesting Carrier Interconnection Central Office (“RICO”) in that LATA and shall designate the Ameritech Tandem Central Office that is designated as the home Tandem (based on the LERG) for the Ameritech Wire Center in which the Requesting Carrier’s Central Office is located, as the Ameritech Interconnection Central Office (“AICO”) in that LATA. III.2.5 3.2.5 Requesting Carrier’s point of Interconnection must be within an Ameritech Wire Center in the LATA in which Requesting Carrier provides service. III.2.6 3.2.6 Requesting Carrier shall order all trunks and facilities used to establish Interconnection, trunking (for both the Local/IntraLATA Trunks and Access Toll Connecting Trunks), signaling and 9-1-1 Service (as described in Section 3.9) by submitting to Ameritech an electronic Access Service Request including BDS Telis and, as soon as available, an electronic service order via the Provisioning EI.

Appears in 1 contract

Samples: Interconnection Agreement

Interconnection Points and Methods, and Interconnection Activation Dates. III.2.1 3.2.1 In each LATA identified on Schedule 2.1, Requesting Carrier and ------------ Ameritech shall Interconnect their networks at the correspondingly identified Ameritech and Requesting Carrier Central Office(s) on Schedule 2.1 for the ------------ transmission and routing within that LATA of Telephone Exchange Service traffic and Exchange Access traffic pursuant to Section 251(c)(2) of the Act. Requesting Carrier’s 's point of Interconnection must be in an Ameritech local service area in the LATA in which Requesting Carrier is providing service. An Interconnection Activation Date not established and set forth on Schedule 2.1 as ------------ of the Effective Date shall be determined in accordance with the procedures set forth in Section 3.4.3.. ------------- III.2.2 3.2.2 Interconnection in each LATA shall be accomplished at any technically feasible point within the Parties' networks through either (i) Collocation in Ameritech’s 's Central Offices as provided in Article XII or (ii) ----------- any other Interconnection method to which the Parties may agree in advance of the applicable Interconnection Activation Date for a given LATA and which is consistent with the Act, including a Fiber-Meet as provided in Section 3.3.. ----------- III.2.3 3.2.3 If Requesting Carrier elects Collocation as an Interconnection method, or elects a network architecture that requires Ameritech to Interconnect with Requesting Carrier’s 's facilities via Collocation, then Requesting Carrier must not less than one hundred twenty five (125) days prior to its applicable Interconnection Activation Date notify Ameritech whether Requesting Carrier wishes Ameritech to Interconnect pursuant to subsection (a) or (b) below.. -------------- --- (a) Requesting Carrier shall (i) provide the transport (whether through leased or owned facilities) of Ameritech’s 's traffic from the point of Interconnection to Requesting Carrier’s 's Central Office, (ii) not charge Ameritech for such transport and (iii) provide Ameritech with capacity to meet Ameritech’s 's forecasted needs. If Requesting Carrier does provide Ameritech transport as provided in this subsection (a) but then either -------------- requests Ameritech to utilize its own facilities or does not provide Ameritech capacity to meet Ameritech’s 's forecasted needs, then Requesting Carrier shall (x) provide Ameritech not less than two hundred (200) days' notice prior to the date Ameritech must provide its own facilities for new trunks, (y) compensate Ameritech for the costs incurred by Ameritech to rearrange its network and (z) provide Ameritech Collocation as provided in subsection (b) below.. -------------- (b) If Requesting Carrier does not elect to provide Ameritech transport as provided in subsection (a) above, then Requesting -------------- Carrier shall provide to Ameritech Collocation in Requesting Carrier’s 's Central Office(s) for purposes of that Interconnection on a nondiscriminatory basis and on rates, terms and conditions that are no less favorable than (i) Ameritech provides to Requesting Carrier pursuant to the terms and conditions of this Agreement and (ii) Requesting Carrier provides to other similarly situated Telecommunications Carriers. III.2.4 3.2.4 Unless otherwise agreed by the Parties, the Parties shall designate the Central Office Requesting Carrier has identified as its initial Routing Point in the LATA as the Requesting Carrier Interconnection Central Office ("RICO") in that LATA and shall designate the Ameritech Tandem Central Office that is designated as the home Tandem (based on the LERG) for the Ameritech Wire Center in which the Requesting Carrier’s 's Central Office is located, as the Ameritech Interconnection Central Office ("AICO") in that LATA. III.2.5 3.2.5 Requesting Carrier’s 's point of Interconnection must be within an Ameritech Wire Center in the LATA in which Requesting Carrier provides service. III.2.6 Requesting Carrier shall order all trunks and facilities used to establish Interconnection, trunking (for both the Local/IntraLATA Trunks and Access Toll Connecting Trunks), signaling and 9-1-1 Service (as described in Section 3.9) by submitting to Ameritech an electronic Access Service Request including BDS Telis and, as soon as available, an electronic service order via the Provisioning EI.

Appears in 1 contract

Samples: Interconnection Agreement (Madison River Capital LLC)

Interconnection Points and Methods, and Interconnection Activation Dates. III.2.1 3.2.1 In each LATA identified on Schedule 2.1, Requesting Carrier and Ameritech shall Interconnect their networks at the correspondingly identified Ameritech and Requesting Carrier Central Office(s) on Schedule 2.1 for the transmission and routing within that LATA of Telephone Exchange Service traffic and Exchange Access traffic pursuant to Section 251(c)(2) of the Act. Requesting Carrier’s point of Interconnection must be in an Ameritech local service area in the LATA in which Requesting Carrier is providing service. An Interconnection Activation Date not established and set forth on Schedule 2.1 as of the Effective Date shall be determined in accordance with the procedures set forth in Section 3.4.3. III.2.2 3.2.2 Interconnection in each LATA shall be accomplished at any technically feasible point within the Parties’ networks through either (i) Collocation in Ameritech’s Central Offices as provided in Article XII or (ii) any other Interconnection method to which the Parties may agree in advance of the applicable Interconnection Activation Date for a given LATA and which is consistent with the Act, including a Fiber-Meet as provided in Section 3.3. III.2.3 3.2.3 If Requesting Carrier elects Collocation as an Interconnection method, or elects a network architecture that requires Ameritech to Interconnect with Requesting Carrier’s facilities via Collocation, then Requesting Carrier must not less than one hundred twenty five (125) days prior to its applicable Interconnection Activation Date notify Ameritech whether Requesting Carrier wishes Ameritech to Interconnect pursuant to subsection (a) or (b) below. (a) Requesting Carrier shall (i) provide the transport (whether through leased or owned facilities) of Ameritech’s traffic from the point of Interconnection to Requesting Carrier’s Central Office, (ii) not charge Ameritech for such transport and (iii) provide Ameritech with capacity to meet Ameritech’s forecasted needs. If Requesting Carrier does provide Ameritech transport as provided in this subsection (a) but then either requests Ameritech to utilize its own facilities or does not provide Ameritech capacity to meet Ameritech’s forecasted needs, then Requesting Carrier shall (x) provide Ameritech not less than two hundred (200) days’ notice prior to the date Ameritech must provide its own facilities for new trunks, (y) compensate Ameritech for the 12716496.1 103008 1100C 00650405 costs incurred by Ameritech to rearrange its network and (z) provide Ameritech Collocation as provided in subsection (b) below. (b) If Requesting Carrier does not elect to provide Ameritech transport as provided in subsection (a) above, then Requesting Carrier shall provide to Ameritech Collocation in Requesting Carrier’s Central Office(s) for purposes of that Interconnection on a nondiscriminatory basis and on rates, terms and conditions that are no less favorable than (i) Ameritech provides to Requesting Carrier pursuant to the terms and conditions of this Agreement and (ii) Requesting Carrier provides to other similarly situated Telecommunications Carriers. III.2.4 3.2.4 Unless otherwise agreed by the Parties, the Parties shall designate the Central Office Requesting Carrier has identified as its initial Routing Point in the LATA as the Requesting Carrier Interconnection Central Office (“RICO”) in that LATA and shall designate the Ameritech Tandem Central Office that is designated as the home Tandem (based on the LERG) for the Ameritech Wire Center in which the Requesting Carrier’s Central Office is located, as the Ameritech Interconnection Central Office (“AICO”) in that LATA. III.2.5 3.2.5 Requesting Carrier’s point of Interconnection must be within an Ameritech Wire Center in the LATA in which Requesting Carrier provides service. III.2.6 3.2.6 Requesting Carrier shall order all trunks and facilities used to establish Interconnection, trunking (for both the Local/IntraLATA Trunks and Access Toll Connecting Trunks), signaling and 9-1-1 Service (as described in Section 3.9) by submitting to Ameritech an electronic Access Service Request including BDS Telis and, as soon as available, an electronic service order via the Provisioning EI.

Appears in 1 contract

Samples: Interconnection Agreement

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!