Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: 4.3.1 Each Party shall initially configure a one (1)-way trunk group or, upon mutual agreement of the Parties, a two (2) way trunk group, as a direct transmission path between each RICO and AICO. If two (2) way trunk groups are established, each Party shall be responsible for fifty percent (50%) of the transport between the points of Interconnection. 4.3.1.1 Where Requesting Carrier has purchased high bandwidth facilities for multiple uses, Requesting Carrier will make available these facilities, for trunking and Interconnection, to Ameritech. Requesting Carrier will charge Ameritech at the rate Ameritech is charging Requesting Carrier for the Interconnection and trunking facilities portion of these high bandwidth facilities based upon each party’s proportionate use. 4.3.1.2 Where Requesting Carrier has purchased high bandwidth facilities for multiple use, if Ameritech chooses to install duplicative facilities, Ameritech will assume the full cost of such duplicative facilities. Such facilities must not degrade the quality of the Requesting Carrier’s high bandwidth facilities. 4.3.2 Each Party shall ensure that each Interconnection permits the completion of traffic to all End Offices within that LATA. 4.3.3 Ameritech will provide unassigned NXX codes to the Requesting Carrier, under the Inter-Carrier Compatibility Forum (“ICCF”) developed by CO-Code Assignment Guidelines, until this function is performed by a third party agency. 4.3.4 Ameritech will assign a Common Language Location Identifier (“CLLI”) code to the Requesting Carrier’s End Office Switch if so requested, to be integrated into the public network consistent with procedures used for CLLI code assignment to Ameritech’s own switches until this function is performed by a third party agency. The code must be listed in the LERG. 4.3.5 Each Party is responsible for administering its assigned NXX numbers. 4.3.6 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. 4.3.7 If a pre-existing trunk group is unable to, or consistent with standard trunk engineering practices, is forecasted to be unable to support additional traffic loads, each Party shall, upon request of the other Party, provision, within thirty (30) days of such request, additional trunks to expand the capacity of such pre-existing trunk group. If sufficient capacity does not exist, the Parties shall mutually agree on the appropriate interval to establish such additional trunks based on force and load and other applicable criteria. 4.3.8 If Party A determines that an interconnection trunk group is no longer necessary given actual and forecasted traffic, Party A shall give notice to Party B and Party B shall have thirty
Appears in 2 contracts
Samples: Interconnection Agreement, Interconnection Agreement
Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:
4.3.1 IV.3.1 Each Party shall initially configure a one (1)-way trunk group or, upon mutual agreement of the Parties, a two (2) way trunk group, as a direct transmission path between each RICO and AICO. If two (2) way trunk groups are established, each Party shall be responsible for fifty percent (50%) of the transport between the points of Interconnection.
4.3.1.1 Where Requesting Carrier has purchased high bandwidth facilities for multiple usesIV.3.2 Notwithstanding anything to the contrary contained in this Article IV, Requesting Carrier will make available these facilitiesif the traffic volumes between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, for trunking the Parties shall, within sixty (60) days after a Party receives notification of such occurrence from the other Party, establish new direct trunk groups to the applicable End Office(s) consistent with the grades of service and Interconnection, to Ameritech. Requesting Carrier will charge Ameritech at quality parameters set forth in the rate Ameritech is charging Requesting Carrier for the Interconnection and trunking facilities portion of these high bandwidth facilities based upon each party’s proportionate usePlan (as defined in Section 18.2).
4.3.1.2 Where Requesting Carrier has purchased high bandwidth facilities for multiple use, if Ameritech chooses IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to install duplicative facilities, Ameritech will assume the full cost of such duplicative facilities. Such facilities must not degrade the quality of the Requesting Carrier’s high bandwidth facilitiesthat End Office.
4.3.2 IV.3.4 Each Party shall ensure that each Interconnection Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem. To the extent that a Party desires the ubiquitous delivery of traffic within that LATAan Exchange Area, each Party shall establish and maintain Logical Trunk Groups and separate physical facilities for such Logical Trunk Groups connected to each Tandem of the other Party which serves, or is sub-tended by End Offices which serve, such other Party's Customers within the Exchange Areas served by such Tandem Switches. Requesting Carrier shall either provide Logical Trunk Groups and such facilities for Logical Trunk Groups or purchase Logical Trunk Groups and such facilities for Logical Trunk Groups from Ameritech at the rates for Dedicated Interoffice Transmission Facilities set forth in Item V of the Pricing Schedule plus any additional costs required to provision such Logical Trunk Groups. Where a Tandem also provides End Office functionality, Interconnection by a Party at such Tandem shall provide access to Tandem and End Office functionality.
4.3.3 Ameritech will provide unassigned NXX codes to the Requesting Carrier, under the Inter-Carrier Compatibility Forum (“ICCF”) developed by CO-Code Assignment Guidelines, until this function is performed by a third party agency.
4.3.4 Ameritech will assign a Common Language Location Identifier (“CLLI”) code to the Requesting Carrier’s End Office Switch if so requested, to be integrated into the public network consistent with procedures used for CLLI code assignment to Ameritech’s own switches until this function is performed by a third party agency. The code must be listed in the LERG.
4.3.5 Each Party is responsible for administering its assigned NXX numbers.
4.3.6 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches.
4.3.7 IV.3.5 If a pre-existing trunk group is unable to, or consistent with standard trunk engineering practices, is forecasted to be unable to support additional traffic loads, each Party shall, upon request of the other Party, provision, within thirty (30) days of such request, additional trunks to expand the capacity of such pre-existing trunk group. , subject to Section 19.12.
IV.3.6 If sufficient capacity does not exista Tandem through which the Parties are Interconnected is unable to, or is forecasted to be unable to, support additional traffic loads for any Busy Season, the Parties shall will mutually agree on an End Office trunking plan that will alleviate the appropriate interval to establish such additional trunks based on force Tandem capacity shortage and load ensure completion of traffic between Requesting Carrier and other applicable criteriaAmeritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.
4.3.8 If Party A determines that an interconnection trunk group is no longer necessary given actual and forecasted traffic, Party A shall give notice to Party B and Party B shall have thirty
Appears in 2 contracts
Samples: Interconnection Agreement, Interconnection Agreement
Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:
4.3.1 IV.3.1 Each Party shall initially configure a one (1)-way trunk group or, upon mutual agreement of the Parties, a two (2) way trunk group, as a direct transmission path between each RICO DIWC and AICOAIWC. If two (2) way trunk groups are established, each Party shall be responsible for fifty percent (50%) of the transport between the points of Interconnection.
4.3.1.1 Where Requesting Carrier has purchased high bandwidth facilities for multiple usesIV.3.2 Notwithstanding anything to the contrary contained in this Article IV, Requesting Carrier will make available these facilitiesif the traffic volumes between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, for trunking the Parties shall, within sixty (60) days after a Party receives notification of such occurrence from the other Party, establish new direct trunk groups to the applicable End Office(s) consistent with the grades of service and Interconnection, to Ameritech. Requesting Carrier will charge Ameritech at quality parameters set forth in the rate Ameritech is charging Requesting Carrier for the Interconnection and trunking facilities portion of these high bandwidth facilities based upon each party’s proportionate usePlan (as defined in Section 18.2).
4.3.1.2 Where Requesting Carrier has purchased high bandwidth facilities for multiple use, if Ameritech chooses IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to install duplicative facilities, Ameritech will assume the full cost of such duplicative facilities. Such facilities must not degrade the quality of the Requesting Carrier’s high bandwidth facilitiesthat End Office.
4.3.2 IV.3.4 Each Party shall ensure that each Interconnection Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem. To the extent that a Party desires the ubiquitous delivery of traffic within that LATAan Exchange Area, each Party shall establish and maintain Logical Trunk Groups and separate physical facilities for such Logical Trunk Groups connected to each Tandem of the other Party which serves, or is sub‑tended by End Offices which serve, such other Party's Customers within the Exchange Areas served by such Tandem Switches. Requesting Carrier shall either provide Logical Trunk Groups and such facilities for Logical Trunk Groups or purchase Logical Trunk Groups and such facilities for Logical Trunk Groups from Ameritech at the rates for Dedicated Interoffice Transmission Facilities set forth in Item V of the Pricing Schedule plus any additional costs required to provision such Logical Trunk Groups. Where a Tandem also provides End Office functionality, Interconnection by a Party at such Tandem shall provide access to Tandem and End Office functionality.
4.3.3 Ameritech will provide unassigned NXX codes to the Requesting Carrier, under the Inter-Carrier Compatibility Forum (“ICCF”) developed by CO-Code Assignment Guidelines, until this function is performed by a third party agency.
4.3.4 Ameritech will assign a Common Language Location Identifier (“CLLI”) code to the Requesting Carrier’s End Office Switch if so requested, to be integrated into the public network consistent with procedures used for CLLI code assignment to Ameritech’s own switches until this function is performed by a third party agency. The code must be listed in the LERG.
4.3.5 Each Party is responsible for administering its assigned NXX numbers.
4.3.6 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches.
4.3.7 IV.3.5 If a pre-existing trunk group is unable to, or consistent with standard trunk engineering practices, is forecasted to be unable to support additional traffic loads, each Party shall, upon request of the other Party, provision, within thirty (30) days of such request, additional trunks to expand the capacity of such pre-existing trunk group. , subject to Section 19.12.
IV.3.6 If sufficient capacity does not exista Tandem through which the Parties are Interconnected is unable to, or is forecasted to be unable to, support additional traffic loads for any Busy Season, the Parties shall will mutually agree on an End Office trunking plan that will alleviate the appropriate interval to establish such additional trunks based on force Tandem capacity shortage and load ensure completion of traffic between Requesting Carrier and other applicable criteriaAmeritech Customers. For purposes of this Agreement, Busy Season means any three (3) consecutive month period.
4.3.8 If Party A determines that an interconnection trunk group is no longer necessary given actual and forecasted traffic, Party A shall give notice to Party B and Party B shall have thirty
Appears in 1 contract
Samples: Interconnection Agreement
Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:
4.3.1 IV.3.1 Each Party shall initially configure a one (1)-way trunk group or, upon mutual agreement of the Parties, a two (2) way trunk group, as a direct transmission path between each RICO RIWC and AICOAIWC. If two (2) way trunk groups are established, each Party shall be responsible for fifty percent (50%) of the transport between the points of Interconnection.
4.3.1.1 Where Requesting Carrier has purchased high bandwidth facilities for multiple usesIV.3.2 Notwithstanding anything to the contrary contained in this Article IV, Requesting Carrier will make available these facilitiesif the traffic volumes between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, for trunking the Parties shall, within sixty (60) days after a Party receives notification of such occurrence from the other Party, establish new direct trunk groups to the applicable End Office(s) consistent with the grades of service and Interconnection, to Ameritech. Requesting Carrier will charge Ameritech at quality parameters set forth in the rate Ameritech is charging Requesting Carrier for the Interconnection and trunking facilities portion of these high bandwidth facilities based upon each party’s proportionate usePlan (as defined in Section 18.2).
4.3.1.2 Where Requesting Carrier has purchased high bandwidth facilities for multiple use, if Ameritech chooses IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to install duplicative facilities, Ameritech will assume the full cost of such duplicative facilities. Such facilities must not degrade the quality of the Requesting Carrier’s high bandwidth facilitiesthat End Office.
4.3.2 IV.3.4 Each Party shall ensure that each Interconnection Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem. To the extent that a Party desires the ubiquitous delivery of traffic within that LATAan Exchange Area, each Party shall establish and maintain Logical Trunk Groups and separate physical facilities for such Logical Trunk Groups connected to each Tandem of the other Party which serves, or is sub‑tended by End Offices which serve, such other Party's Customers within the Exchange Areas served by such Tandem Switches. Requesting Carrier shall either provide Logical Trunk Groups and such facilities for Logical Trunk Groups or purchase Logical Trunk Groups and such facilities for Logical Trunk Groups from Ameritech at the rates for Dedicated Interoffice Transmission Facilities set forth in Item V of the Pricing Schedule plus any additional costs required to provision such Logical Trunk Groups. Where a Tandem also provides End Office functionality, Interconnection by a Party at such Tandem shall provide access to Tandem and End Office functionality.
4.3.3 Ameritech will provide unassigned NXX codes to the Requesting Carrier, under the Inter-Carrier Compatibility Forum (“ICCF”) developed by CO-Code Assignment Guidelines, until this function is performed by a third party agency.
4.3.4 Ameritech will assign a Common Language Location Identifier (“CLLI”) code to the Requesting Carrier’s End Office Switch if so requested, to be integrated into the public network consistent with procedures used for CLLI code assignment to Ameritech’s own switches until this function is performed by a third party agency. The code must be listed in the LERG.
4.3.5 Each Party is responsible for administering its assigned NXX numbers.
4.3.6 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches.
4.3.7 IV.3.5 If a pre-existing trunk group is unable to, or consistent with standard trunk engineering practices, is forecasted to be unable to support additional traffic loads, each Party shall, upon request of the other Party, provision, within thirty (30) days of such request, additional trunks to expand the capacity of such pre-existing trunk group. , subject to Section 19.12.
IV.3.6 If sufficient capacity does not exista Tandem through which the Parties are Interconnected is unable to, or is forecasted to be unable to, support additional traffic loads for any Busy Season, the Parties shall will mutually agree on an End Office trunking plan that will alleviate the appropriate interval to establish such additional trunks based on force Tandem capacity shortage and load ensure completion of traffic between Requesting Carrier and other applicable criteriaAmeritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.
4.3.8 If Party A determines that an interconnection trunk group is no longer necessary given actual and forecasted traffic, Party A shall give notice to Party B and Party B shall have thirty
Appears in 1 contract
Samples: Interconnection Agreement
Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:
4.3.1 IV.3.1 Each Party shall initially configure a one (1)-way trunk group or, upon mutual agreement of the Parties, a two (2) way trunk group, as a direct transmission path between each RICO DIWC and AICOAIWC. If two (2) way trunk groups are established, each Party shall be responsible for fifty percent (50%) of the transport between the points of Interconnection.
4.3.1.1 Where Requesting Carrier has purchased high bandwidth facilities for multiple usesIV.3.2 Notwithstanding anything to the contrary contained in this Article IV, Requesting Carrier will make available these facilitiesif the traffic volumes between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, for trunking the Parties shall, within sixty (60) days after a Party receives notification of such occurrence from the other Party, establish new direct trunk groups to the applicable End Office(s) consistent with the grades of service and Interconnection, to Ameritech. Requesting Carrier will charge Ameritech at quality parameters set forth in the rate Ameritech is charging Requesting Carrier for the Interconnection and trunking facilities portion of these high bandwidth facilities based upon each party’s proportionate usePlan (as defined in Section 18.2).
4.3.1.2 Where Requesting Carrier has purchased high bandwidth facilities for multiple use, if Ameritech chooses IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to install duplicative facilities, Ameritech will assume the full cost of such duplicative facilitiesthat End Office. Such facilities must not degrade the quality of the Requesting Carrier’s high bandwidth facilities.8822090.1 102708 1111C 96252093
4.3.2 IV.3.4 Each Party shall ensure that each Interconnection Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem. To the extent that a Party desires the ubiquitous delivery of traffic within that LATAan Exchange Area, each Party shall establish and maintain Logical Trunk Groups and separate physical facilities for such Logical Trunk Groups connected to each Tandem of the other Party which serves, or is sub-tended by End Offices which serve, such other Party's Customers within the Exchange Areas served by such Tandem Switches. Requesting Carrier shall either provide Logical Trunk Groups and such facilities for Logical Trunk Groups or purchase Logical Trunk Groups and such facilities for Logical Trunk Groups from Ameritech at the rates for Dedicated Interoffice Transmission Facilities set forth in Item V of the Pricing Schedule plus any additional costs required to provision such Logical Trunk Groups. Where a Tandem also provides End Office functionality, Interconnection by a Party at such Tandem shall provide access to Tandem and End Office functionality.
4.3.3 Ameritech will provide unassigned NXX codes to the Requesting Carrier, under the Inter-Carrier Compatibility Forum (“ICCF”) developed by CO-Code Assignment Guidelines, until this function is performed by a third party agency.
4.3.4 Ameritech will assign a Common Language Location Identifier (“CLLI”) code to the Requesting Carrier’s End Office Switch if so requested, to be integrated into the public network consistent with procedures used for CLLI code assignment to Ameritech’s own switches until this function is performed by a third party agency. The code must be listed in the LERG.
4.3.5 Each Party is responsible for administering its assigned NXX numbers.
4.3.6 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches.
4.3.7 IV.3.5 If a pre-existing trunk group is unable to, or consistent with standard trunk engineering practices, is forecasted to be unable to support additional traffic loads, each Party shall, upon request of the other Party, provision, within thirty (30) days of such request, additional trunks to expand the capacity of such pre-existing trunk group. , subject to Section 19.12.
IV.3.6 If sufficient capacity does not exista Tandem through which the Parties are Interconnected is unable to, or is forecasted to be unable to, support additional traffic loads for any Busy Season, the Parties shall will mutually agree on an End Office trunking plan that will alleviate the appropriate interval to establish such additional trunks based on force Tandem capacity shortage and load ensure completion of traffic between Requesting Carrier and other applicable criteriaAmeritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.
4.3.8 If Party A determines that an interconnection trunk group is no longer necessary given actual and forecasted traffic, Party A shall give notice to Party B and Party B shall have thirty
Appears in 1 contract
Samples: Interconnection Agreement
Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:
4.3.1 IV.3.1 Each Party shall initially configure either a one (1)-way trunk group or, upon mutual agreement of the Parties, 1)-or a two (2) way 2)-way trunk group, group as a direct transmission path between each RICO KIWC and AICO. If AIWC.
IV.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes between any two (2) way Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, the Parties shall, within sixty (60) days after such occurrence, establish new direct trunk groups are established, each Party shall be responsible for fifty percent (50%to the applicable End Office(s) consistent with the grades of service and quality parameters set forth in the transport between the points of InterconnectionPlan.
4.3.1.1 Where Requesting Carrier has purchased high bandwidth facilities for multiple uses, Requesting Carrier will make available these facilities, for trunking and Interconnection, IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to Ameritech. Requesting Carrier will charge Ameritech at the rate Ameritech is charging Requesting Carrier for the Interconnection and trunking facilities portion of these high bandwidth facilities based upon each party’s proportionate usethat End Office.
4.3.1.2 Where Requesting Carrier has purchased high bandwidth facilities for multiple use, if Ameritech chooses to install duplicative facilities, Ameritech will assume the full cost of such duplicative facilities. Such facilities must not degrade the quality of the Requesting Carrier’s high bandwidth facilities.
4.3.2 IV.3.4 Each Party shall ensure that each Interconnection Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem. Each Party shall establish and maintain Logical Trunk Groups and separate facilities for such Logical Trunk Groups connected to each Tandem of the other Party which serves, or is sub-tended by End Offices which serve, such other Party's Customers within that LATAthe Exchange Areas served by such Tandem Switches. Urban Media may either provide such facilities for Logical Trunk Groups or purchase such facilities for Logical Trunk Groups from Ameritech at the rates for Dedicated Interoffice Transmission Facilities set forth in Item V of the Pricing Schedule. Where a Tandem also provides End Office functionality, Interconnection by a Party at such Tandem shall provide access to such Tandem's End Office functionality.
4.3.3 Ameritech will provide unassigned NXX codes to the Requesting Carrier, under the Inter-Carrier Compatibility Forum (“ICCF”) developed by CO-Code Assignment Guidelines, until this function is performed by a third party agency.
4.3.4 Ameritech will assign a Common Language Location Identifier (“CLLI”) code to the Requesting Carrier’s End Office Switch if so requested, to be integrated into the public network consistent with procedures used for CLLI code assignment to Ameritech’s own switches until this function is performed by a third party agency. The code must be listed in the LERG.
4.3.5 Each Party is responsible for administering its assigned NXX numbers.
4.3.6 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches.
4.3.7 IV.3.5 If a pre-existing trunk group is unable to, or consistent with standard trunk engineering practices, is forecasted to be unable to support additional traffic loads, each Party shall, upon request of the other Party, provision, within thirty (30) days of such request, additional trunks to expand the capacity of such pre-existing trunk group. If sufficient capacity does not exist, the Parties shall mutually agree on the appropriate interval subject to establish such additional trunks based on force and load and other applicable criteriaSection 19.12 of this Agreement.
4.3.8 If Party A determines that an interconnection trunk group is no longer necessary given actual and forecasted traffic, Party A shall give notice to Party B and Party B shall have thirty
Appears in 1 contract
Samples: Interconnection Agreement
Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:
4.3.1 IV.3.1 Each Party shall initially configure a one (1)-way trunk group or, upon mutual agreement of the Parties, a two (2) way trunk group, as a direct transmission path between each RICO and AICO. If two (2) way trunk groups are established, each Party shall be responsible for fifty percent (50%) of the transport between the points of Interconnection. 861229.2 102208 1516C 96252093
IV.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, the Parties shall, within sixty (60) days after a Party receives notification of such occurrence from the other Party, establish new direct trunk groups to the applicable End Office(s) consistent with the grades of service and quality parameters set forth in the Plan (as defined in Section 18.2).
4.3.1.1 Where Requesting Carrier has purchased high bandwidth facilities for multiple uses, Requesting Carrier will make available these facilities, for trunking and Interconnection, IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to Ameritech. Requesting Carrier will charge Ameritech at the rate Ameritech is charging Requesting Carrier for the Interconnection and trunking facilities portion of these high bandwidth facilities based upon each party’s proportionate usethat End Office.
4.3.1.2 Where Requesting Carrier has purchased high bandwidth facilities for multiple use, if Ameritech chooses to install duplicative facilities, Ameritech will assume the full cost of such duplicative facilities. Such facilities must not degrade the quality of the Requesting Carrier’s high bandwidth facilities.
4.3.2 IV.3.4 Each Party shall ensure that each Interconnection Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem. To the extent that a Party desires the ubiquitous delivery of traffic within that LATAan Exchange Area, each Party shall establish and maintain Logical Trunk Groups and separate physical facilities for such Logical Trunk Groups connected to each Tandem of the other Party which serves, or is sub-tended by End Offices which serve, such other Party's Customers within the Exchange Areas served by such Tandem Switches. Frontier shall either provide Logical Trunk Groups and such facilities for Logical Trunk Groups or purchase Logical Trunk Groups and such facilities for Logical Trunk Groups from Ameritech at the rates for Dedicated Interoffice Transmission Facilities set forth in Item V of the Pricing Schedule plus any additional costs required to provision such Logical Trunk Groups. Where a Tandem also provides End Office functionality, Interconnection by a Party at such Tandem shall provide access to Tandem and End Office functionality.
4.3.3 Ameritech will provide unassigned NXX codes to the Requesting Carrier, under the Inter-Carrier Compatibility Forum (“ICCF”) developed by CO-Code Assignment Guidelines, until this function is performed by a third party agency.
4.3.4 Ameritech will assign a Common Language Location Identifier (“CLLI”) code to the Requesting Carrier’s End Office Switch if so requested, to be integrated into the public network consistent with procedures used for CLLI code assignment to Ameritech’s own switches until this function is performed by a third party agency. The code must be listed in the LERG.
4.3.5 Each Party is responsible for administering its assigned NXX numbers.
4.3.6 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches.
4.3.7 IV.3.5 If a pre-existing trunk group is unable to, or consistent with standard trunk engineering practices, is forecasted to be unable to support additional traffic loads, each Party shall, upon request of the other Party, provision, within thirty (30) days of such request, additional trunks to expand the capacity of such pre-existing trunk group. , subject to Section 19.12.
IV.3.6 If sufficient capacity does not exista Tandem through which the Parties are Interconnected is unable to, or is forecasted to be unable to, support additional traffic loads for any Busy Season, the Parties shall will mutually agree on an End Office trunking plan that will alleviate the appropriate interval to establish such additional trunks based on force Tandem capacity shortage and load ensure completion of traffic between Frontier and other applicable criteriaAmeritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.
4.3.8 If Party A determines that an interconnection trunk group is no longer necessary given actual and forecasted traffic, Party A shall give notice to Party B and Party B shall have thirty
Appears in 1 contract
Samples: Interconnection Agreement