Common use of Trunk Group Architecture and Traffic Routing Clause in Contracts

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: 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. IV.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party shall, within sixty (60) days after such occurrence, establish new direct trunk groups to the applicable End Office(s). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. IV.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”). To the extent that a Party desires the ubiquitous delivery of traffic within an 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 Switched Access set forth in Ameritech’s access tariffs. If a Central Office Switch provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 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. IV.3.6 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. IV.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 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 and the availability of sufficient capacity. 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. IV.3.10 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: IV.3.1 4.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 two (2) way trunk groups are established, each Party shall be responsible for fifty percent (50%) of the transport between the points of InterconnectionAIWC. IV.3.2 4.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party the Parties shall, within sixty (60) days after such occurrence, establish new direct trunk groups to the applicable End Office(s). As traffic volumes increase, ) consistent with the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment grades of traffic that equals or exceeds service and quality parameters set forth in the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCSPlan. IV.3.3 4.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. IV.3.4 4.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”)Tandem. To the extent that a Party desires the ubiquitous delivery of traffic within an Exchange Area, each 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 's Customers within the Exchange Areas served by such Tandem Switches. Requesting Carrier shall may 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 Switched Access Dedicated Interoffice Transmission Facilities set forth in Ameritech’s access tariffsItem V of the Pricing Schedule. If Where a Central Office Switch Tandem also provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch Tandem shall provide access to Tandem and such Tandem's End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 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. IV.3.6 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. IV.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 4.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 and the availability of sufficient capacity. 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. IV.3.10 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: 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. IV.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party the Parties shall, within sixty (60) days after a Party receives notification of such occurrenceoccurrence 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). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. IV.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”)Tandem. To the extent that a Party desires the ubiquitous delivery of traffic within an 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 '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 Switched Access Dedicated Interoffice Transmission Facilities set forth in Ameritech’s access tariffsItem V of the Pricing Schedule plus any additional costs required to provision such Logical Trunk Groups. If Where a Central Office Switch Tandem also provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch Tandem shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 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. IV.3.6 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. IV.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 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 and the availability of sufficient capacity. 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 criteria19.12. IV.3.10 IV.3.6 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: IV.3.1 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. IV.3.2 4.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party shall, within sixty (60) days after such occurrence, establish new direct trunk groups to the applicable End Office(s). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 4.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. IV.3.4 4.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”). To the extent that a Party desires the ubiquitous delivery of traffic within an 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 Switched Access set forth in Ameritech’s access tariffs. If a Central Office Switch provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 4.3.5 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. IV.3.6 4.3.6 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. IV.3.7 4.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 4.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 4.3.9 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 and the availability of sufficient capacity. 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. IV.3.10 4.3.10 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: IV.3.1 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. IV.3.2 4.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party shall, within sixty (60) days after such occurrence, establish new direct trunk groups to the applicable End Office(s). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 4.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. IV.3.4 4.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”). To the extent that a Party desires the ubiquitous delivery of traffic within an 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 Switched Access set forth in Ameritech’s access tariffs. If a Central Office Switch provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 4.3.5 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. IV.3.6 4.3.6 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. IV.3.7 4.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 12716496.1 110201 1406C 00650405 4.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 4.3.9 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 and the availability of sufficient capacity. 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. IV.3.10 4.3.10 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: IV.3.1 4.3.1 Each Party shall initially configure either a one two (1)-way 2)-way trunk group or, upon mutual agreement of the Parties, a two one (21) 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. IV.3.2 4.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party the Parties shall, within sixty (60) days after such occurrence, 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). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 4.3.3 Only those valid NXX codes served by an End byanEnd Office may be maybe accessed through a direct connection to that End Office. IV.3.4 4.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”)Tandem. To the extent that a Party desires the ubiquitous delivery of traffic within an Exchange Area, each Party shall establish and maintain Logical Trunk Groups and separate physical facilities physicalfacilities for such Logical Trunk Groups connected to each Tandem of the other Party 12664580.1 52400 801C 96252093 16 which serves, or is sub-tended by End Offices which serve, such other Party’s '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 Switched Access Dedicated Interoffice Transmission Facilities set forth in Ameritech’s access tariffsItem V of the Pricing Schedule plus any additional costs required to provision such Logical Trunk Groups. If Where a Central Office Switch Tandem also provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch Tandem shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 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. IV.3.6 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. IV.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 4.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 and the availability of sufficient capacity. 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 criteria19.12. IV.3.10 4.3.6 If a 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 will mutually agree on an End Office trunking plan that will alleviate willalleviate the Tandem capacity shortage Tandemcapacityshortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: 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 two (2) way trunk groups are established, each Party shall be responsible for fifty percent (50%) of the transport between the points of InterconnectionAIWC. IV.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party the Parties shall, within sixty (60) days after such occurrence, establish new direct trunk groups to the applicable End Office(s). As traffic volumes increase, ) consistent with the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment grades of traffic that equals or exceeds service and quality parameters set forth in the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCSPlan. IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. IV.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”)Tandem. To the extent that a Party desires the ubiquitous delivery of traffic within an Exchange Area, each 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 's Customers within the Exchange Areas served by such Tandem Switches. Requesting Carrier shall Urban Media may 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 Switched Access Dedicated Interoffice Transmission Facilities set forth in Ameritech’s access tariffsItem V of the Pricing Schedule. If Where a Central Office Switch Tandem also provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch Tandem shall provide access to Tandem and such Tandem's End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 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. IV.3.6 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. IV.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 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 and the availability of sufficient capacity. 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. IV.3.10 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: IV.3.1 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. IV.3.2 4.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party shall, within sixty (60) days after such occurrence, establish new direct trunk groups to the applicable End Office(s). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 4.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. IV.3.4 4.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”). To the extent that a Party desires the ubiquitous delivery of traffic within an 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 Switched Access set forth in Ameritech’s access tariffs. If a Central Office Switch provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 4.3.5 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. IV.3.6 4.3.6 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. IV.3.7 4.3.7 Each Party is responsible for administering its assigned NXX numbers. its switches. IV.3.8 4.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches.to IV.3.9 4.3.9 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 and the availability of sufficient capacity. 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. IV.3.10 4.3.10 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: 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. IV.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party shall, within sixty (60) days after such occurrence, establish new direct trunk groups to the applicable End Office(s). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. IV.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”). To the extent that a Party desires the ubiquitous delivery of traffic within an 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 Switched Access set forth in Ameritech’s access tariffs. If a Central Office Switch provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 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. IV.3.6 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. IV.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 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 and the availability of sufficient capacity. 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. IV.3.10 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.Section

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: IV.3.1 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.. 12716496.1 80509 940C 00650405 IV.3.2 4.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party shall, within sixty (60) days after such occurrence, establish new direct trunk groups to the applicable End Office(s). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 4.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. IV.3.4 4.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”). To the extent that a Party desires the ubiquitous delivery of traffic within an 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 Switched Access set forth in Ameritech’s access tariffs. If a Central Office Switch provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 4.3.5 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. IV.3.6 4.3.6 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. IV.3.7 4.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 4.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 4.3.9 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 and the availability 12716496.1 80509 940C 00650405 of sufficient capacity. 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. IV.3.10 4.3.10 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: 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. IV.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party the Parties shall, within sixty (60) days after a Party receives notification of such occurrenceoccurrence 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). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office.. 8822090.1 102708 1111C 96252093 IV.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”)Tandem. To the extent that a Party desires the ubiquitous delivery of traffic within an 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 '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 Switched Access Dedicated Interoffice Transmission Facilities set forth in Ameritech’s access tariffsItem V of the Pricing Schedule plus any additional costs required to provision such Logical Trunk Groups. If Where a Central Office Switch Tandem also provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch Tandem shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 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. IV.3.6 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. IV.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 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 and the availability of sufficient capacity. 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 criteria19.12. IV.3.10 IV.3.6 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: 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. IV.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party the Parties shall, within sixty (60) days after a Party receives notification of such occurrenceoccurrence 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). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. IV.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”)Tandem. To the extent that a Party 6275755.2 101408 910C 96252093 desires the ubiquitous delivery of traffic within an 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 's Customers within the Exchange Areas served by such Tandem Switches. Requesting Carrier 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 Switched Access Dedicated Interoffice Transmission Facilities set forth in Ameritech’s access tariffsItem V of the Pricing Schedule plus any additional costs required to provision such Logical Trunk Groups. If Where a Central Office Switch Tandem also provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch Tandem shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 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. IV.3.6 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. IV.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 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 and the availability of sufficient capacity. 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 criteria19.12. IV.3.10 IV.3.6 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier Frontier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: 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 NICO 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. IV.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party shall, within sixty (60) days after such occurrence, establish new direct trunk groups to the applicable End Office(s). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. IV.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”). To the extent that a Party desires the ubiquitous delivery of traffic within an 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 Switched Access set forth in Ameritech’s access tariffs. If a Central Office Switch provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 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. IV.3.6 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. IV.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 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 and the availability of sufficient capacity. 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. IV.3.10 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: 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. IV.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party the Parties shall, within sixty (60) days after a Party receives notification of such occurrenceoccurrence 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). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. IV.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”)Tandem. To the extent that a Party desires the ubiquitous delivery of traffic within an 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 sub‑tended by End Offices which serve, such other Party’s '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 Switched Access Dedicated Interoffice Transmission Facilities set forth in Ameritech’s access tariffsItem V of the Pricing Schedule plus any additional costs required to provision such Logical Trunk Groups. If Where a Central Office Switch Tandem also provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch Tandem shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 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. IV.3.6 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. IV.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 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 and the availability of sufficient capacity. 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 criteria19.12. IV.3.10 IV.3.6 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” Busy Season means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: IV.3.1 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. IV.3.2 4.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party shall, within sixty (60) days after such occurrence, establish new direct trunk groups to the applicable End Office(s). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 4.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office.. 12716496.1 103008 1100C 00650405 IV.3.4 4.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”). To the extent that a Party desires the ubiquitous delivery of traffic within an 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 Switched Access set forth in Ameritech’s access tariffs. If a Central Office Switch provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 4.3.5 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. IV.3.6 4.3.6 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. IV.3.7 4.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 4.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 4.3.9 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 and the availability of sufficient capacity. 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. IV.3.10 4.3.10 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: 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. IV.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party the Parties shall, within sixty (60) days after a Party receives notification of such occurrenceoccurrence 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). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. IV.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”)Tandem. To the extent that a Party desires the ubiquitous delivery of traffic within an 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 sub‑tended by End Offices which serve, such other Party’s '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 Switched Access Dedicated Interoffice Transmission Facilities set forth in Ameritech’s access tariffsItem V of the Pricing Schedule plus any additional costs required to provision such Logical Trunk Groups. If Where a Central Office Switch Tandem also provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch Tandem shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 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. IV.3.6 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. IV.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 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 and the availability of sufficient capacity. 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 criteria19.12. IV.3.10 IV.3.6 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: 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 originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party the Parties shall, within sixty (60) days after a Party receives notification of such occurrenceoccurrence 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). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. IV.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”)Tandem. To the extent that a Party desires the ubiquitous delivery of traffic within an 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 's Customers within the Exchange Areas served by such Tandem Switches. Requesting Carrier 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 Switched Access Dedicated Interoffice Transmission Facilities set forth in Ameritech’s access tariffsItem V of the Pricing Schedule plus any additional costs required to provision such Logical Trunk Groups. If Where a Central Office Switch Tandem also provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch Tandem shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 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. IV.3.6 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. IV.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 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 and the availability of sufficient capacity. 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 criteria19.12. IV.3.10 IV.3.6 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier Frontier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.

Trunk Group Architecture and Traffic Routing. The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows: IV.3.1 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. IV.3.2 4.3.2 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes originated by a Party between any two (2) Central Office Switches at any time exceeds the CCS busy hour equivalent of one (1) DS1, that Party the Parties shall, within sixty (60) days after a Party receives notification of such occurrenceoccurrence 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). As traffic volumes increase, the Parties shall add additional direct trunk groups (24 DS0s) between any two (2) Central Offices for every increment of traffic that equals or exceeds the CCS busy hour equivalent of one (1) DS1. At no time shall the traffic between two (2) Central Offices, routed via Ameritech’s Tandem Switch, exceed 500 busy hour CCS. IV.3.3 4.3.3 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. IV.3.4 4.3.4 Each Party shall ensure that each Tandem connection permits the completion of traffic to all End Offices which sub-tend that Tandem as identified in the Local Exchange Routing Guide (“LERG”)Tandem. To the extent that a Party desires the ubiquitous delivery of traffic within an 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 '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 Switched Access Dedicated Interoffice Transmission Facilities set forth in Ameritech’s access tariffsItem V of the Pricing Schedule plus any additional costs required to provision such Logical Trunk Groups. If Where a Central Office Switch Tandem also provides both Tandem and End Office functionality, Interconnection by a Party at such Central Office Switch Tandem shall provide access to Tandem and End Office functionality. A Party’s NXX must home on the Tandem Switch that is in the same state as the specified NXX Rate Center. IV.3.5 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. IV.3.6 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. IV.3.7 Each Party is responsible for administering its assigned NXX numbers. IV.3.8 Each Party is responsible for obtaining a LERG listing of CLLI codes assigned to its switches. IV.3.9 4.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 and the availability of sufficient capacity. 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 criteria19.12. IV.3.10 4.3.6 If a 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 will mutually agree on an End Office trunking plan that will alleviate the Tandem capacity shortage and ensure completion of traffic between Requesting Carrier and Ameritech Customers. For purposes of this Agreement, “Busy Season” means any three (3) consecutive month period.