Additional Interconnection(s) Sample Clauses

Additional Interconnection(s). 3.4.1 If Requesting Carrier determines to offer Telephone Exchange Service within Ameritech’s service areas that require additional points of Interconnection, Requesting Carrier shall provide written notice to Ameritech of its need to establish such additional points of Interconnection pursuant to this Agreement. 3.4.2 The notice provided in Section 3.4.1 shall include (i) Requesting Carrier’s requested RICO(s) and AICO(s) (including address and CLLI Code);
Sample 1Sample 2Sample 3See All (8)
AutoNDA by SimpleDocs
Additional Interconnection(s). III.4.1 If Requesting Carrier determines to offer Telephone Exchange Service within Ameritech’s service areas that require additional points of Interconnection, Requesting Carrier shall provide written notice to Ameritech of its need to establish such additional points of Interconnection pursuant to this Agreement. III.4.2 The notice provided in Section 3.4.1 shall include (i) Requesting Carrier’s requested RICO(s) and AICO(s) (including address and CLLI Code); (ii) Requesting Carrier’s requested Interconnection Activation Date; and (iii) a non-binding forecast of Requesting Carrier’s trunking and facilities requirements. III.4.3 Within ten (10) Business Days of Ameritech’s receipt of Requesting Carrier’s notice specified in Section 3.4.1, Ameritech and Requesting Carrier shall schedule a meeting to mutually agree on the network architecture (including trunking), the AICO(s), the RICO(s) and Interconnection Activation Date(s) applicable to such Interconnection(s). The Interconnection Activation Date for an Interconnection shall be established based on then-existing force and load, the scope and complexity of the requested Interconnection and other relevant factors. The Parties acknowledge that, as of the Effective Date, the interval to establish Interconnection via Collocation or Fiber-Meet is one-hundred fifty (150) calendar days for up to 24 T1’s of trunking after the Parties have agreed on the AICO(s), RICO(s) and network architecture and Requesting Carrier has furnished Ameritech a non-binding forecast in accordance with Section 3.4.
Sample 1Sample 2See All (5)
Additional Interconnection(s). As defined in Section 7.1 of this Agreement.
Sample 1Sample 2Sample 3See All (4)
Additional Interconnection(s). 3.4.1 If Requesting Carrier determines that it requires additional points of Interconnection, Requesting Carrier shall provide written notice to Ameritech of its need to establish such additional points of Interconnection pursuant to this Agreement. 3.4.2 The notice provided in Section 3.4.1 shall include (i) Requesting Carrier’s requested RICO(s) and AICO(s) (including address and CLLI Code); (ii) Requesting Carrier’s requested Interconnection Activation Date; and (iii) a non-binding forecast of Requesting Carrier’s trunking and facilities requirements. 3.4.3 Within ten (10) Business Days of Ameritech’s receipt of Requesting Carrier’s notice specified in Section 3.4.1, Ameritech and Requesting Carrier shall agree upon the trunking, the AICO(s), the RICO(s) and Interconnection Activation Date(s) applicable to such Interconnection(s). The Interconnection Activation Date for an Interconnection shall be established based on then-existing force and load, the scope and complexity of the requested Interconnection and other relevant factors. The Parties acknowledge that, as of the Effective Date, the interval to establish Interconnection via Collocation or Joint Fiber-Meet is one-hundred fifty (150) days for up to 24 T1s of trunking, after the Parties have agreed on the AICO(s), RICO(s) and trunking and Requesting Carrier has furnished Ameritech a non-binding forecast in accordance with Section 3.4.2. The interval to establish Interconnection for trunking in excess of up to 24 T1s is 6 T1s per Business Day after one hundred fifty (150) days.
Sample 1Sample 2
Additional Interconnection(s). Subject to the conditions imposed by this IMA and any other conditions which might be imposed by the Parties at the time, additional interconnections between the wastewater collection systems of the District, Fairfax, WSSC and Non-Party Users shall be allowed.
Sample 1Sample 2
Additional Interconnection(s). If Requesting Carrier determines to offer circuit switched Telephone Exchange Service within Ameritech’s service areas that require additional points of Interconnection, Requesting Carrier shall provide written notice to Ameritech of its need to establish such additional points of Interconnection pursuant to this Agreement.
Sample 1

Related to Additional Interconnection(s)

  • Interconnection 2.1 This section applies to linking with suppliers providing public telecommunications transport networks or services in order to allow the users of one supplier to communicate with users of another supplier and to access services provided by another supplier, where specific commitments are undertaken.

  • Two-Way Interconnection Trunks 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Navtel, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Navtel, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel and Verizon. Navtel’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 during the average time consistent busy hour. Verizon and Navtel shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three

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