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: 4.3.1 Each Party shall provision and maintain their own one (1)-way trunks to deliver calls originating on their own network and routed to the other Party’s network. SBC- AMERITECH will be responsible for providing all transport from its customers to the CLEC switching center. CLEC will be responsible for costs of trunking and transport from its customers to SBC-AMERITECH end offices. If CLEC establishes direct connections to SBC- AMERITECH end offices, the charges it must pay SBC-AMERITECH will reflect that arrangement. If CLEC interconnects at the tandem and uses one or more SBC-AMERITECH transport offerings to reach SBC-AMERITECH end offices, the charges will be calculated according to the offerings used. 4.3.2 A one-way trunk group for ancillary services (e.g. OS/DA, mass calling, 911) can be established between an CLEC Switch Center and an SBC-AMERITECH Tandem. This trunk group will utilize Signaling System 7 (“SS7”) or multi-frequency (“MF”) signaling protocol, with SS7 signaling preferred whenever possible. CLEC will have administrative control of one-way trunk groups from CLEC to SBC-AMERITECH (CLEC originating). 4.3.3 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes between any SBC-AMERITECH End Office and CLEC Switch Center 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 to the applicable End Office(s) consistent with the grades of service and quality parameters set forth in the Plan. 4.3.4 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. The source for the routing information for all traffic, including miscellaneous calls (e.g., time, weather, 976), shall be the LERG, unless otherwise agreed to between the Parties. 4.3.5 SBC-AMERITECH will provide the facilities between each SBC- AMERITECH Tandem Switch and the SBC-AMERITECH End Office(s) sub-tending that Tandem Switch. SBC-AMERITECH shall ensure that each Tandem Switch permits the completion of traffic to all End Offices that sub-tend that Tandem Switch. 4.3.6 [Intentionally Omitted]. 4.3.7 [Intentionally Omitted]. 4.3.8 SBC-AMERITECH deploys in its network Tandems that switch local only traffic, Tandems that switch IntraLATA and InterLATA traffic (Access Tandem) and Tandems that switch both local and IntraLATA/InterLATA traffic (local/Access Tandem). In addition SBC-AMERITECH deploys Tandems that switch ancillary traffic such as 911 (911 Tandem), Operator Services/ Directory Assistance (OPS/DA Tandem), and mass calling (choke Tandem). Traffic on Tandem trunks does not terminate at the Tandem but is switched to other trunks that terminate the traffic in End Offices and ultimately to End Users. 4.3.9 When Tandem trunks are deployed, CLEC shall route appropriate traffic (i.e. only traffic to End Offices that subtend that Tandem) to the respective SBC- AMERITECH Tandems on the trunk groups defined in this Article IV. SBC-AMERITECH shall route appropriate traffic to CLEC switches on the trunk groups defined in this Article IV. 4.3.10 In all cases except a blocking situation, either Party upon receipt of a TGSR will issue an ASR to the other Party or will initiate a joint planning discussion: 4.3.10.1 Within twenty (20) business days after receipt of the TGSR or 4.3.10.2 At any time as a result of either Party's own capacity management assessment, in order to begin the provisioning process, the intervals used for the provisioning process will be the same as those used for SBC-AMERITECH’s Switched Access service. 4.3.11 Orders between the Parties to establish, add, change or disconnect trunks shall be processed by using an Access Service Request (“ASR”). CLEC will have administrative control for the purpose of issuing ASR’s on two-way trunk groups. In SBC- AMERITECH where one-way trunks are used (as discussed in Section 4.3.1), SBC- AMERITECH will issue ASRs for trunk groups for traffic that originates in SBC- AMERITECH and terminates to CLEC. The Parties agree that neither Party shall alter trunk sizing without first conferring with the other party. 4.3.12 Both Parties will jointly manage the capacity of Local Interconnection Trunk Groups. Both Parties may send a Trunk Group Service Request (“TGSR”) to the other Party to trigger changes to the Local Interconnection Trunk Groups based on capacity assessment. The TGSR is a standard industry support interface developed by the Ordering and Billing Forum of the Carrier liaison Committee of the Alliance for Telecommunications Solutions (“ATIS”) organization. TELCORDIA TECHNOLOGIES Special Report STS000316 describes the format and use of the TGSR. 4.3.13 In a blocking final situation, a TGSR will be issued by either Party when additional capacity is required to reduce measured blocking to objective design blocking levels based upon analysis of trunk group data. Either Party upon receipt of a TGSR in a blocking situation will issue an ASR to the other Party within three (3) business days after receipt of the TGSR. The Party issuing the ASR will note “Service Affecting” on the ASR. 4.3.14 Underutilization of Interconnection trunks and facilities exists when provisioned capacity is greater than the current need. Those situations where underutilization of interconnection trunks and facilities exists will be handled in the following manner: 4.3.14.1 If a trunk group is under seventy five percent (75%) of CCS capacity on a monthly average basis, for any consecutive one-hundred thirty five (135) day period, either Party may request the issuance of an order to resize the trunk group, which shall be left with not less than twenty five percent (25%) excess capacity. In all cases grade of service objectives shall be maintained. 4.3.14.2 Either Party may send a TGSR to the other Party to trigger changes to the Local Interconnection Trunk Groups based on capacity assessment. Upon receipt of a TGSR, the receiving Party will issue an ASR to the other Party within twenty (20) business days after receipt of the TGSR 4.3.14.3 Upon review of the TGSR, if a Party does not agree with the resizing, the Parties will schedule a joint planning discussion within twenty (20) business days. The Parties will meet to resolve and mutually agree to the disposition of the TGSR. 4.3.14.4 If SBC-AMERITECH does not receive an ASR, or if CLEC does not respond to the TGSR by scheduling a joint discussion within the twenty (20) business day period, SBC-AMERITECH will contact CLEC to schedule a joint planning discussion. If CLEC will not agree to meet within an additional five (5) business days and present adequate reason for keeping trunks operational and after appropriate escalation under Section 28.3.2, SBC-AMERITECH will issue an ASR to resize the Interconnection trunks and facilities. 4.3.15 Projects require the coordination and execution of multiple orders or related activities between and among SBC-AMERITECH and CLEC work groups, including but not limited to the initial establishment of Local Interconnection or Meet Point Trunk Groups and service in an area, NXX code moves, re-homes, facility grooming, or network rearrangements. Orders that comprise a Project, i.e., greater than sixteen (16) DS-1’s, shall be submitted at the same time, and their implementation shall be jointly planned and coordinated. 4.3.16 Due dates for the installation of Local Interconnection Trunks covered by this Article shall be based on each of the SBC-AMERITECH’s intrastate Switched Access intervals. If CLEC is unable to or not ready to perform Acceptance Tests, or is unable to accept the Local Interconnection service arrangement trunk(s) by the due date, CLEC will provide SBC-AMERITECH with a requested revised service due date that is no more than forty-five (45) calendar days beyond the original service due date. If CLEC requests a service due date change that exceeds the allowable service due date change period, the ASR must be canceled by CLEC. Should CLEC fail to cancel such ASR within ten (10) days after notice to the Party specified in Section 28.3.2, SBC-AMERITECH shall treat that ASR as though it had been canceled. 4.3.17 Each Party agrees to service trunk groups to the foregoing blocking criteria in a timely manner when trunk groups exceed measured blocking thresholds on an average time consistent busy hour for a twenty (20) business day study period. The Parties agree that twenty (20) business days is the study period duration objective. However, a study period on occasion may be less than twenty (20) business days but at minimum must be at least five (5) business days to be utilized for engineering purposes, although with less statistical confidence. 4.3.18 Exchange of traffic data enables each Party to make accurate and independent assessments of trunk group service levels and requirements. Parties agree to establish a timeline for implementing an exchange of traffic data utilizing the DIXC process via a Network Data Mover (“NDM”) or FTP computer to computer file transfer process. Implementation shall be within three (3) months of the date, or such date as agreed upon, that the trunk groups begin passing live traffic. The traffic data to be exchanged will be the Originating Attempt Peg Count, Usage (measured in Hundred Call Seconds), Overflow Peg Count, and Maintenance Usage (measured in Hundred Call Seconds on a seven (7) day per week, twenty-four (24) hour per day, fifty-two (52) weeks per year basis. These reports shall be made available at a minimum on a semi-annual basis upon request. Exchange of data on one-way groups is optional.

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 provision and maintain their own one (1)-way trunks to deliver calls originating on their own network and routed to the other Party’s network. SBC- AMERITECH AT&T will be financially responsible for providing all transport from its customers the facilities to the CLEC switching center. CLEC will be responsible for costs of trunking and transport from its customers to SBC-AMERITECH end offices. If CLEC establishes direct connections Tandems that are required to deliver traffic originating on AT&T’s network to SBC- AMERITECH end offices, the charges it must pay AMERITECH. SBC-AMERITECH will reflect be financially responsible for providing the facilities to AT&T Switch Centers that arrangement. If CLEC interconnects at the tandem and uses one or more SBC-AMERITECH transport offerings are required to reach SBC-AMERITECH end offices, the charges will be calculated according deliver traffic originating on SBC- AMERITECH’s network to the offerings used.AT&T. 4.3.2 A one-way trunk group for ancillary services (e.g. OSOPS/DA, mass calling, 911) can be established between an CLEC AT&T Switch Center and an SBC-SBC- AMERITECH Tandem. This trunk group will utilize Signaling System 7 (“SS7”) or multi-frequency (“MF”) signaling protocol, with SS7 signaling preferred whenever possible. CLEC AT&T will have administrative control of one-way trunk groups from CLEC AT&T to SBC-AMERITECH (CLEC AT&T originating). 4.3.3 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes between any SBC-AMERITECH End Office and CLEC AT&T Switch Center 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 to the applicable End Office(s) consistent with the grades of service and quality parameters set forth in the Plan. These direct trunk groups will be provisioned over two interconnected facilities. AT&T will be responsible for the facility from AT&T’s Switch Center to the SBC-AMERITECH Tandem Switch Center, and SBC-AMERITECH will be responsible for the facility from the SBC-AMERITECH Tandem Switch Center to the applicable End Office. 4.3.4 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. The source for the routing information for all traffic, including miscellaneous calls (e.g., time, weather, 976), shall be the LERG, unless otherwise agreed to between the Parties. 4.3.5 SBC-AMERITECH will provide the facilities between each SBC- AMERITECH Tandem Switch and the SBC-AMERITECH End Office(s) sub-tending that Tandem Switch. SBC-AMERITECH shall ensure that each Tandem Switch permits the completion of traffic to all End Offices that sub-tend that Tandem Switch. 4.3.6 [Intentionally Omitted]Each Party shall establish and maintain separate trunk groups connected to each Tandem Switch or Switch Center, as the case may be, of the other Party that serves, or is sub-tended by End Offices that serve, such other Party's Customers within the Exchange Areas served by such Tandem Switches or Switch Centers, as the case may be. 4.3.7 [Intentionally Omitted]Each Party shall, upon request of the other Party, provision, within thirty (30) days of such request, additional trunks for use in a pre-existing Interconnection arrangement, subject to Section 19.12 of this Agreement. 4.3.8 SBC-AMERITECH deploys in its network Tandems that switch local only traffic, Tandems that switch IntraLATA and InterLATA traffic (Access Tandem) and Tandems that switch both local and IntraLATA/InterLATA traffic (local/Access Tandem). In addition SBC-SBC- AMERITECH deploys Tandems that switch ancillary traffic such as 911 (911 Tandem), Operator Services/ Directory Assistance (OPS/DA Tandem), and mass calling (choke Tandem). Traffic on Tandem trunks does not terminate at the Tandem but is switched to other trunks that terminate the traffic in End Offices and ultimately to End Users. 4.3.9 When Tandem trunks are deployed, CLEC AT&T shall route appropriate traffic (i.e. only traffic to End Offices that subtend that Tandem) to the respective SBC- AMERITECH Tandems on the trunk groups defined in this Article IV. SBC-SBC- AMERITECH shall route appropriate traffic to CLEC AT&T switches on the trunk groups defined in this Article IV. 4.3.10 In all cases except a blocking situation, either Party upon receipt of a TGSR will issue an ASR to the other Party or will initiate a joint planning discussion: 4.3.10.1 Within twenty (20) business days after receipt of the TGSR TGSR; or 4.3.10.2 At any time as a result of either Party's own capacity management assessment, in order to begin the provisioning process, the intervals used for the provisioning process will be the same as those used for SBC-AMERITECH’s Switched Access service. 4.3.11 Orders between the Parties to establish, add, change or disconnect trunks shall be processed by using an Access Service Request (“ASR”). CLEC AT&T will have administrative control for the purpose of issuing ASR’s on two-way trunk groups. In SBC- AMERITECH where one-way trunks are used (as discussed in Section 4.3.1), SBC- AMERITECH will issue ASRs for trunk groups for traffic that originates in SBC- AMERITECH and terminates to CLEC. AT&T. The Parties agree that neither Party shall alter trunk sizing without first conferring with the other party. 4.3.12 Both Parties will jointly manage the capacity of Local Interconnection Trunk Groups. Both Parties may send a Trunk Group Service Request (“TGSR”) to the other Party to trigger changes to the Local Interconnection Trunk Groups based on capacity assessment. The TGSR is a standard industry support interface developed by the Ordering and Billing Forum of the Carrier liaison Committee of the Alliance for Telecommunications Solutions (“ATIS”) organization. TELCORDIA TECHNOLOGIES Special Report STS000316 describes the format and use of the TGSR. 4.3.13 In a blocking final situation, a TGSR will be issued by either Party when additional capacity is required to reduce measured blocking to objective design blocking levels based upon analysis of trunk group data. Either Party upon receipt of a TGSR in a blocking situation will issue an ASR to the other Party within three (3) business days after receipt of the TGSR. The Party issuing the ASR will note “Service Affecting” on the ASR. 4.3.14 Underutilization of Interconnection trunks and facilities exists when provisioned capacity is greater than the current need. Those situations where underutilization of interconnection trunks and facilities exists will be handled in the following manner: 4.3.14.1 If a trunk group is under seventy five percent (75%) of CCS capacity on a monthly average basis, for any consecutive one-hundred thirty five (135) day period, either Party may request the issuance of an order to resize the trunk group, which shall be left with not less than twenty five percent (25%) excess capacity. In all cases grade of service objectives shall be maintained. 4.3.14.2 Either Party may send a TGSR to the other Party to trigger changes to the Local Interconnection Trunk Groups based on capacity assessment. Upon receipt of a TGSR, the receiving Party will issue an ASR to the other Party within twenty (20) business days after receipt of the TGSR. 4.3.14.3 Upon review of the TGSR, if a Party does not agree with the resizing, the Parties will schedule a joint planning discussion within twenty (20) business days. The Parties will meet to resolve and mutually agree to the disposition of the TGSR. 4.3.14.4 If SBC-SBC- AMERITECH does not receive an ASR, or if CLEC AT&T does not respond to the TGSR by scheduling a joint discussion within the twenty (20) business day period, SBC-SBC- AMERITECH will contact CLEC AT&T to schedule a joint planning discussion. If CLEC AT&T will not agree to meet within an additional five (5) business days and present adequate reason for keeping trunks operational and after appropriate escalation under Section 28.3.2, SBC-AMERITECH will issue an ASR to resize the Interconnection trunks and facilities. 4.3.15 Projects require the coordination and execution of multiple orders or related activities between and among SBC-AMERITECH and CLEC work groups, including but not limited to the initial establishment of Local Interconnection or Meet Point Trunk Groups and service in an area, NXX code moves, re-homes, facility grooming, or network rearrangements. Orders that comprise a Project, i.e., greater than sixteen four (164) DS-1DS- 1’s, shall be submitted at the same time, and their implementation shall be jointly planned and coordinated. 4.3.16 Due dates for the installation of Local Interconnection Trunks covered by this Article shall be based on each of the SBC-SBC- AMERITECH’s intrastate Switched Access intervals. If CLEC AT&T is unable to or not ready to perform Acceptance Tests, or is unable to accept the Local Interconnection service arrangement trunk(s) by the due date, CLEC AT&T will provide SBC-AMERITECH with a requested revised service due date that is no more than forty-five (45) calendar days beyond the original service due date. If CLEC AT&T requests a service due date change that exceeds the allowable service due date change period, the ASR must be canceled by CLEC. AT&T. Should CLEC AT&T fail to cancel such ASR within ten (10) days after notice to the Party specified in Section 28.3.2, SBC-SBC- AMERITECH shall treat that ASR as though it had been canceled. 4.3.17 Each Party agrees to service trunk groups to the foregoing blocking criteria in a timely manner when trunk groups exceed measured blocking thresholds on an average time consistent busy hour for a twenty (20) business day study period. The Parties agree that twenty (20) business days is the study period duration objective. However, a study period on occasion may be less than twenty (20) business days but at minimum must be at least five (5) business days to be utilized for engineering purposes, although with less statistical confidence. 4.3.18 Exchange of traffic data enables each Party to make accurate and independent assessments of trunk group service levels and requirements. Parties agree to establish a timeline for implementing an exchange of traffic data utilizing the DIXC process via a Network Data Mover (“NDM”) or FTP computer to computer file transfer process. Implementation shall be within three (3) months of the date, or such date as agreed upon, that the trunk groups begin passing live traffic. The traffic data to be exchanged will be the Originating Attempt Peg Count, Usage (measured in Hundred Call Seconds), Overflow Peg Count, and Maintenance Usage (measured in Hundred Call Seconds on a seven (7) day per week, twenty-four (24) hour per day, fifty-two (52) weeks per year basis. These reports shall be made available at a minimum on a semi-annual basis upon request. Exchange of data on one-way groups is optional.

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 provision and maintain their own one (1)-way trunks to deliver calls originating on their own network and routed to the other Party’s network. SBC- AMERITECH SBC will be responsible for providing all transport from its customers to the CLEC switching center. CLEC will be responsible for costs of trunking and transport from its customers to SBC-AMERITECH SBC end offices. If CLEC establishes direct connections to SBC- AMERITECH SBC end offices, the charges it must pay SBC-AMERITECH SBC will reflect that arrangement. If CLEC interconnects at the tandem and uses one or more SBC-AMERITECH SBC transport offerings to reach SBC-AMERITECH SBC end offices, the charges will be calculated according to the offerings used. 4.3.2 A one-way trunk group for ancillary services (e.g. OS/DA, mass calling, 911) can be established between an CLEC Switch Center and an SBC-AMERITECH SBC Tandem. This trunk group will utilize Signaling System 7 (“SS7”) or multi-frequency (“MF”) signaling protocol, with SS7 signaling preferred whenever possible. CLEC will have administrative control of one-way trunk groups from CLEC to SBC-AMERITECH SBC (CLEC originating). 4.3.3 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes between any SBC-AMERITECH SBC End Office and CLEC Switch Center 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 to the applicable End Office(s) consistent with the grades of service and quality parameters set forth in the Plan. 4.3.4 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. The source for the routing information for all traffic, including miscellaneous calls (e.g., time, weather, 976), shall be the LERG, unless otherwise agreed to between the Parties. 4.3.5 SBC-AMERITECH SBC will provide the facilities between each SBC- AMERITECH SBC Tandem Switch and the SBC-AMERITECH SBC End Office(s) sub-tending that Tandem Switch. SBC-AMERITECH SBC shall ensure that each Tandem Switch permits the completion of traffic to all End Offices that sub-tend that Tandem Switch. 4.3.6 [Intentionally Omitted]. 4.3.7 [Intentionally Omitted]. 4.3.8 SBC-AMERITECH SBC deploys in its network Tandems that switch local only traffic, Tandems that switch IntraLATA and InterLATA traffic (Access Tandem) and Tandems that switch both local and IntraLATA/InterLATA traffic (local/Access Tandem). In addition SBC-AMERITECH SBC deploys Tandems that switch ancillary traffic such as 911 (911 Tandem), Operator Services/ Directory Assistance (OPS/DA Tandem), and mass calling (choke Tandem). Traffic on Tandem trunks does not terminate at the Tandem but is switched to other trunks that terminate the traffic in End Offices and ultimately to End Users. 4.3.9 When Tandem trunks are deployed, CLEC shall route appropriate traffic (i.e. only traffic to End Offices that subtend that Tandem) to the respective SBC- AMERITECH SBC Tandems on the trunk groups defined in this Article IV. SBC-AMERITECH SBC shall route appropriate traffic to CLEC switches on the trunk groups defined in this Article IV. 4.3.10 In all cases except a blocking situation, either Party upon receipt of a TGSR will issue an ASR to the other Party or will initiate a joint planning discussion: 4.3.10.1 Within twenty (20) business days after receipt of the TGSR or 4.3.10.2 At any time as a result of either Party's own capacity management assessment, in order to begin the provisioning process, the intervals used for the provisioning process will be the same as those used for SBC-AMERITECH’s Switched Access service. 4.3.11 Orders between the Parties to establish, add, change or disconnect trunks shall be processed by using an Access Service Request (“ASR”). CLEC will have administrative control for the purpose of issuing ASR’s on two-way trunk groups. In SBC- AMERITECH SBC where one-way trunks are used (as discussed in Section 4.3.1), SBC- AMERITECH SBC will issue ASRs for trunk groups for traffic that originates in SBC- AMERITECH SBC and terminates to CLEC. The Parties agree that neither Party shall alter trunk sizing without first conferring with the other party. 4.3.12 Both Parties will jointly manage the capacity of Local Interconnection Trunk Groups. Both Parties may send a Trunk Group Service Request (“TGSR”) to the other Party to trigger changes to the Local Interconnection Trunk Groups based on capacity assessment. The TGSR is a standard industry support interface developed by the Ordering and Billing Forum of the Carrier liaison Committee of the Alliance for Telecommunications Solutions (“ATIS”) organization. TELCORDIA TECHNOLOGIES Special Report STS000316 describes the format and use of the TGSR. 4.3.13 In a blocking final situation, a TGSR will be issued by either Party when additional capacity is required to reduce measured blocking to objective design blocking levels based upon analysis of trunk group data. Either Party upon receipt of a TGSR in a blocking situation will issue an ASR to the other Party within three (3) business days after receipt of the TGSR. The Party issuing the ASR will note “Service Affecting” on the ASR. 4.3.14 Underutilization of Interconnection trunks and facilities exists when provisioned capacity is greater than the current need. Those situations where underutilization of interconnection trunks and facilities exists will be handled in the following manner: 4.3.14.1 If a trunk group is under seventy five percent (75%) of CCS capacity on a monthly average basis, for any consecutive one-hundred thirty five (135) day period, either Party may request the issuance of an order to resize the trunk group, which shall be left with not less than twenty five percent (25%) excess capacity. In all cases grade of service objectives shall be maintained. 4.3.14.2 Either Party may send a TGSR to the other Party to trigger changes to the Local Interconnection Trunk Groups based on capacity assessment. Upon receipt of a TGSR, the receiving Party will issue an ASR to the other Party within twenty (20) business days after receipt of the TGSR 4.3.14.3 Upon review of the TGSR, if a Party does not agree with the resizing, the Parties will schedule a joint planning discussion within twenty (20) business days. The Parties will meet to resolve and mutually agree to the disposition of the TGSR. 4.3.14.4 If SBC-AMERITECH SBC does not receive an ASR, or if CLEC does not respond to the TGSR by scheduling a joint discussion within the twenty (20) business day period, SBC-AMERITECH SBC will contact CLEC to schedule a joint planning discussion. If CLEC will not agree to meet within an additional five (5) business days and present adequate reason for keeping trunks operational and after appropriate escalation under Section 28.3.2, SBC-AMERITECH SBC will issue an ASR to resize the Interconnection trunks and facilities. 4.3.15 Projects require the coordination and execution of multiple orders or related activities between and among SBC-AMERITECH SBC and CLEC work groups, including but not limited to the initial establishment of Local Interconnection or Meet Point Trunk Groups and service in an area, NXX code moves, re-homes, facility grooming, or network rearrangements. Orders that comprise a Project, i.e., greater than sixteen (16) DS-1’s, shall be submitted at the same time, and their implementation shall be jointly planned and coordinated. 4.3.16 Due dates for the installation of Local Interconnection Trunks covered by this Article shall be based on each of the SBC-AMERITECH’s intrastate Switched Access intervals. If CLEC is unable to or not ready to perform Acceptance Tests, or is unable to accept the Local Interconnection service arrangement trunk(s) by the due date, CLEC will provide SBC-AMERITECH SBC with a requested revised service due date that is no more than forty-five (45) calendar days beyond the original service due date. If CLEC requests a service due date change that exceeds the allowable service due date change period, the ASR must be canceled by CLEC. Should CLEC fail to cancel such ASR within ten (10) days after notice to the Party specified in Section 28.3.2, SBC-AMERITECH SBC shall treat that ASR as though it had been canceled. 4.3.17 Each Party agrees to service trunk groups to the foregoing blocking criteria in a timely manner when trunk groups exceed measured blocking thresholds on an average time consistent busy hour for a twenty (20) business day study period. The Parties agree that twenty (20) business days is the study period duration objective. However, a study period on occasion may be less than twenty (20) business days but at minimum must be at least five (5) business days to be utilized for engineering purposes, although with less statistical confidence. 4.3.18 Exchange of traffic data enables each Party to make accurate and independent assessments of trunk group service levels and requirements. Parties agree to establish a timeline for implementing an exchange of traffic data utilizing the DIXC process via a Network Data Mover (“NDM”) or FTP computer to computer file transfer process. Implementation shall be within three (3) months of the date, or such date as agreed upon, that the trunk groups begin passing live traffic. The traffic data to be exchanged will be the Originating Attempt Peg Count, Usage (measured in Hundred Call Seconds), Overflow Peg Count, and Maintenance Usage (measured in Hundred Call Seconds on a seven (7) day per week, twenty-four (24) hour per day, fifty-two (52) weeks per year basis. These reports shall be made available at a minimum on a semi-annual basis upon request. Exchange of data on one-way groups is optional.

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 provision and maintain their own one (1)-way trunks to deliver calls originating on their own network and routed to the other Party’s network. SBC- SBC-AMERITECH will be responsible for providing all transport from its customers to the CLEC switching center. CLEC will be responsible for costs of trunking and transport from its customers to SBC-AMERITECH end offices. If CLEC establishes direct connections to SBC- SBC-AMERITECH end offices, the charges it must pay SBC-AMERITECH will reflect that arrangement. If CLEC interconnects at the tandem and uses one or more SBC-AMERITECH transport offerings to reach SBC-AMERITECH end offices, the charges will be calculated according to the offerings used. 4.3.2 A one-way trunk group for ancillary services (e.g. OS/DA, mass calling, 911) can be established between an CLEC Switch Center and an SBC-SBC- AMERITECH Tandem. This trunk group will utilize Signaling System 7 (“SS7”) or multi-frequency (“MF”) signaling protocol, with SS7 signaling preferred whenever possible. CLEC will have administrative control of one-way trunk groups from CLEC to SBC-AMERITECH (CLEC originating). 4.3.3 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes between any SBC-AMERITECH End Office and CLEC Switch Center 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 to the applicable End Office(s) consistent with the grades of service and quality parameters set forth in the Plan. 4.3.4 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. The source for the routing information for all traffic, including miscellaneous calls (e.g., time, weather, 976), shall be the LERG, unless otherwise agreed to between the Parties. 4.3.5 SBC-AMERITECH will provide the facilities between each SBC- AMERITECH Tandem Switch and the SBC-AMERITECH End Office(s) sub-tending that Tandem Switch. SBC-AMERITECH shall ensure that each Tandem Switch permits the completion of traffic to all End Offices that sub-tend that Tandem Switch. 4.3.6 [Intentionally Omitted]. 4.3.7 [Intentionally Omitted]. 4.3.8 SBC-AMERITECH deploys in its network Tandems that switch local only traffic, Tandems that switch IntraLATA and InterLATA traffic (Access Tandem) and Tandems that switch both local and IntraLATA/InterLATA traffic (local/Access Tandem). In addition SBC-AMERITECH deploys Tandems that switch ancillary traffic such as 911 (911 Tandem), Operator Services/ Directory Assistance (OPS/DA Tandem), and mass calling (choke Tandem). Traffic on Tandem trunks does not terminate at the Tandem but is switched to other trunks that terminate the traffic in End Offices and ultimately to End Users. 4.3.9 When Tandem trunks are deployed, CLEC shall route appropriate traffic (i.e. only traffic to End Offices that subtend that Tandem) to the respective SBC- AMERITECH Tandems on the trunk groups defined in this Article IV. SBC-SBC- AMERITECH shall route appropriate traffic to CLEC switches on the trunk groups defined in this Article IV. 4.3.10 In all cases except a blocking situation, either Party upon receipt of a TGSR will issue an ASR to the other Party or will initiate a joint planning discussion: 4.3.10.1 Within twenty (20) business days after receipt of the TGSR or 4.3.10.2 At any time as a result of either Party's own capacity management assessment, in order to begin the provisioning process, the intervals used for the provisioning process will be the same as those used for SBC-AMERITECH’s Switched Access service. 4.3.11 Orders between the Parties to establish, add, change or disconnect trunks shall be processed by using an Access Service Request (“ASR”). CLEC will have administrative control for the purpose of issuing ASR’s on two-way trunk groups. In SBC- AMERITECH where one-way trunks are used (as discussed in Section 4.3.1), SBC- AMERITECH will issue ASRs for trunk groups for traffic that originates in SBC- AMERITECH and terminates to CLEC. The Parties agree that neither Party shall alter trunk sizing without first conferring with the other party. 4.3.12 Both Parties will jointly manage the capacity of Local Interconnection Trunk Groups. Both Parties may send a Trunk Group Service Request (“TGSR”) to the other Party to trigger changes to the Local Interconnection Trunk Groups based on capacity assessment. The TGSR is a standard industry support interface developed by the Ordering and Billing Forum of the Carrier liaison Committee of the Alliance for Telecommunications Solutions (“ATIS”) organization. TELCORDIA TECHNOLOGIES Special Report STS000316 describes the format and use of the TGSR. 4.3.13 In a blocking final situation, a TGSR will be issued by either Party when additional capacity is required to reduce measured blocking to objective design blocking levels based upon analysis of trunk group data. Either Party upon receipt of a TGSR in a blocking situation will issue an ASR to the other Party within three (3) business days after receipt of the TGSR. The Party issuing the ASR will note “Service Affecting” on the ASR. 4.3.14 Underutilization of Interconnection trunks and facilities exists when provisioned capacity is greater than the current need. Those situations where underutilization of interconnection trunks and facilities exists will be handled in the following manner: 4.3.14.1 If a trunk group is under seventy five percent (75%) of CCS capacity on a monthly average basis, for any consecutive one-hundred thirty five (135) day period, either Party may request the issuance of an order to resize the trunk group, which shall be left with not less than twenty five percent (25%) excess capacity. In all cases grade of service objectives shall be maintained. 4.3.14.2 Either Party may send a TGSR to the other Party to trigger changes to the Local Interconnection Trunk Groups based on capacity assessment. Upon receipt of a TGSR, the receiving Party will issue an ASR to the other Party within twenty (20) business days after receipt of the TGSR 4.3.14.3 Upon review of the TGSR, if a Party does not agree with the resizing, the Parties will schedule a joint planning discussion within twenty (20) business days. The Parties will meet to resolve and mutually agree to the disposition of the TGSR. 4.3.14.4 If SBC-AMERITECH does not receive an ASR, or if CLEC does not respond to the TGSR by scheduling a joint discussion within the twenty (20) business day period, SBC-AMERITECH will contact CLEC to schedule a joint planning discussion. If CLEC will not agree to meet within an additional five (5) business days and present adequate reason for keeping trunks operational and after appropriate escalation under Section 28.3.2, SBC-AMERITECH will issue an ASR to resize the Interconnection trunks and facilities. 4.3.15 Projects require the coordination and execution of multiple orders or related activities between and among SBC-AMERITECH and CLEC work groups, including but not limited to the initial establishment of Local Interconnection or Meet Point Trunk Groups and service in an area, NXX code moves, re-homes, facility grooming, or network rearrangements. Orders that comprise a Project, i.e., greater than sixteen (16) DS-1’s, shall be submitted at the same time, and their implementation shall be jointly planned and coordinated. 4.3.16 Due dates for the installation of Local Interconnection Trunks covered by this Article shall be based on each of the SBC-AMERITECH’s intrastate Switched Access intervals. If CLEC is unable to or not ready to perform Acceptance Tests, or is unable to accept the Local Interconnection service arrangement trunk(s) by the due date, CLEC will provide SBC-AMERITECH with a requested revised service due date that is no more than forty-five (45) calendar days beyond the original service due date. If CLEC requests a service due date change that exceeds the allowable service due date change period, the ASR must be canceled by CLEC. Should CLEC fail to cancel such ASR within ten (10) days after notice to the Party specified in Section 28.3.2, SBC-SBC- AMERITECH shall treat that ASR as though it had been canceled. 4.3.17 Each Party agrees to service trunk groups to the foregoing blocking criteria in a timely manner when trunk groups exceed measured blocking thresholds on an average time consistent busy hour for a twenty (20) business day study period. The Parties agree that twenty (20) business days is the study period duration objective. However, a study period on occasion may be less than twenty (20) business days but at minimum must be at least five (5) business days to be utilized for engineering purposes, although with less statistical confidence. 4.3.18 Exchange of traffic data enables each Party to make accurate and independent assessments of trunk group service levels and requirements. Parties agree to establish a timeline for implementing an exchange of traffic data utilizing the DIXC process via a Network Data Mover (“NDM”) or FTP computer to computer file transfer process. Implementation shall be within three (3) months of the date, or such date as agreed upon, that the trunk groups begin passing live traffic. The traffic data to be exchanged will be the Originating Attempt Peg Count, Usage (measured in Hundred Call Seconds), Overflow Peg Count, and Maintenance Usage (measured in Hundred Call Seconds on a seven (7) day per week, twenty-four (24) hour per day, fifty-two (52) weeks per year basis. These reports shall be made available at a minimum on a semi-annual basis upon request. Exchange of data on one-way groups is optional.

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 provision and maintain their own one (1)-way trunks to deliver calls originating on their own network and routed to the other Party’s network. SBC- AMERITECH will be responsible for providing all transport from its customers to the CLEC switching center. CLEC will be responsible for costs of trunking and transport from its customers to SBC-AMERITECH end offices. If CLEC establishes direct connections to SBC- AMERITECH end offices, the charges it must pay SBC-AMERITECH will reflect that arrangement. If CLEC interconnects at the tandem and uses one or more SBC-AMERITECH transport offerings to reach SBC-AMERITECH end offices, the charges will be calculated according to the offerings used. 4.3.2 A one-way trunk group for ancillary services (e.g. OS/DA, mass calling, 911) can be established between an CLEC Switch Center and an SBC-AMERITECH Tandem. This trunk group will utilize Signaling System 7 (“SS7”) or multi-multi- frequency (“MF”) signaling protocol, with SS7 signaling preferred whenever possible. CLEC will have administrative control of one-way trunk groups from CLEC to SBC-AMERITECH (CLEC originating). 4.3.3 Notwithstanding anything to the contrary contained in this Article IV, if the traffic volumes between any SBC-AMERITECH End Office and CLEC Switch Center 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 to the applicable End Office(s) consistent with the grades of service and quality parameters set forth in the Plan. 4.3.4 Only those valid NXX codes served by an End Office may be accessed through a direct connection to that End Office. The source for the routing information for all traffic, including miscellaneous calls (e.g., time, weather, 976), shall be the LERG, unless otherwise agreed to between the Parties. 4.3.5 SBC-AMERITECH will provide the facilities between each SBC- AMERITECH Tandem Switch and the SBC-AMERITECH End Office(s) sub-tending that Tandem Switch. SBC-AMERITECH shall ensure that each Tandem Switch permits the completion of traffic to all End Offices that sub-tend that Tandem Switch. 4.3.6 [Intentionally Omitted]. 4.3.7 [Intentionally Omitted]. 4.3.8 SBC-AMERITECH deploys in its network Tandems that switch local only traffic, Tandems that switch IntraLATA and InterLATA traffic (Access Tandem) and Tandems that switch both local and IntraLATA/InterLATA traffic (local/Access Tandem). In addition SBC-AMERITECH deploys Tandems that switch ancillary traffic such as 911 (911 Tandem), Operator Services/ Directory Assistance (OPS/DA Tandem), and mass calling (choke Tandem). Traffic on Tandem trunks does not terminate at the Tandem but is switched to other trunks that terminate the traffic in End Offices and ultimately to End Users. 4.3.9 When Tandem trunks are deployed, CLEC shall route appropriate traffic (i.e. only traffic to End Offices that subtend that Tandem) to the respective SBC- AMERITECH Tandems on the trunk groups defined in this Article IV. SBC-AMERITECH shall route appropriate traffic to CLEC switches on the trunk groups defined in this Article IV. 4.3.10 In all cases except a blocking situation, either Party upon receipt of a TGSR will issue an ASR to the other Party or will initiate a joint planning discussion: 4.3.10.1 Within twenty (20) business days after receipt of the TGSR or 4.3.10.2 At any time as a result of either Party's own capacity management assessment, in order to begin the provisioning process, the intervals used for the provisioning process will be the same as those used for SBC-AMERITECH’s Switched Access service. 4.3.11 Orders between the Parties to establish, add, change or disconnect trunks shall be processed by using an Access Service Request (“ASR”). CLEC will have administrative control for the purpose of issuing ASR’s on two-way trunk groups. In SBC- AMERITECH where one-way trunks are used (as discussed in Section 4.3.1), SBC- AMERITECH will issue ASRs for trunk groups for traffic that originates in SBC- AMERITECH and terminates to CLEC. The Parties agree that neither Party shall alter trunk sizing without first conferring with the other party. 4.3.12 Both Parties will jointly manage the capacity of Local Interconnection Trunk Groups. Both Parties may send a Trunk Group Service Request (“TGSR”) to the other Party to trigger changes to the Local Interconnection Trunk Groups based on capacity assessment. The TGSR is a standard industry support interface developed by the Ordering and Billing Forum of the Carrier liaison Committee of the Alliance for Telecommunications Solutions (“ATIS”) organization. TELCORDIA TECHNOLOGIES Special Specia l Report STS000316 describes the format and use of the TGSR. 4.3.13 In a blocking final situation, a TGSR will be issued by either Party when additional capacity is required to reduce measured blocking to objective design blocking levels based upon analysis of trunk group data. Either Party upon receipt of a TGSR in a blocking situation will issue an ASR to the other Party within three (3) business days after receipt of the TGSR. The Party issuing the ASR will note “Service Affecting” on the ASR. 4.3.14 Underutilization of Interconnection trunks and facilities exists when provisioned capacity is greater than the current need. Those situations where underutilization of interconnection trunks and facilities exists will be handled in the following manner: 4.3.14.1 If a trunk group is under seventy five percent (75%) of CCS capacity on a monthly average basis, for any consecutive one-hundred thirty five (135) day period, either Party may request the issuance of an order to resize the trunk group, which shall be left with not less than twenty five percent (25%) excess capacity. In all cases grade of service objectives shall be maintained. 4.3.14.2 Either Party may send a TGSR to the other Party to trigger changes to the Local Interconnection Trunk Groups based on capacity assessment. Upon receipt of a TGSR, the receiving Party will issue an ASR to the other Party within twenty (20) business days after receipt of the TGSR 4.3.14.3 Upon review of the TGSR, if a Party does not agree with the resizing, the Parties will schedule a joint planning discussion within twenty (20) business days. The Parties will meet to resolve and mutually agree to the disposition of the TGSR. 4.3.14.4 If SBC-AMERITECH does not receive an ASR, or if CLEC does not respond to the TGSR by scheduling a joint discussion within the twenty (20) business day period, SBC-AMERITECH will contact CLEC to schedule a joint planning discussion. If CLEC will not agree to meet within an additional five (5) business days and present adequate reason for keeping trunks operational and after appropriate escalation under Section 28.3.2, SBC-AMERITECH will issue an ASR to resize the Interconnection trunks and facilities. 4.3.15 Projects require the coordination and execution of multiple orders or related activities between and among SBC-AMERITECH and CLEC work groups, including but not limited to the initial establishment of Local Interconnection or Meet Point Trunk Groups and service in an area, NXX code moves, re-homes, facility grooming, or network rearrangements. Orders that comprise a Project, i.e., greater than sixteen (16) DS-1’s, shall be submitted at the same time, and their implementation shall be jointly planned and coordinated. 4.3.16 Due dates for the installation of Local Interconnection Trunks covered by this Article shall be based on each of the SBC-AMERITECH’s intrastate Switched Access intervals. If CLEC is unable to or not ready to perform Acceptance Tests, or is unable to accept the Local Interconnection service arrangement trunk(s) by the due date, CLEC will provide SBC-AMERITECH with a requested revised service due date that is no more than forty-forty- five (45) calendar days beyond the original service due date. If CLEC requests a service due date change that exceeds the allowable service due date change period, the ASR must be canceled by CLEC. Should CLEC fail to cancel such ASR within ten (10) days after notice to the Party specified in Section 28.3.2, SBC-AMERITECH shall treat that ASR as though it had been canceled. 4.3.17 Each Party agrees to service trunk groups to the foregoing blocking criteria in a timely manner when trunk groups exceed measured blocking thresholds on an average time consistent busy hour for a twenty (20) business day study period. The Parties agree that twenty twent y (20) business days is the study period duration objective. However, a study period on occasion may be less than twenty (20) business days but at minimum must be at least five (5) business days to be utilized for engineering purposes, although with less statistical confidence. 4.3.18 Exchange of traffic data enables each Party to make accurate and independent assessments of trunk group service levels and requirements. Parties agree to establish a timeline for implementing an exchange of traffic data utilizing the DIXC process via a Network Data Mover (“NDM”) or FTP computer to computer file transfer process. Implementation shall be within three (3) months of the date, or such date as agreed upon, that the trunk groups begin passing live traffic. The traffic data to be exchanged will be the Originating Attempt Peg Count, Usage (measured in Hundred Call Seconds), Overflow Peg Count, and Maintenance Usage (measured in Hundred Call Seconds on a seven (7) day per week, twenty-four (24) hour per day, fifty-fifty- two (52) weeks per year basis. These reports shall be made available at a minimum on a semi-semi- annual basis upon request. Exchange of data on one-way groups is optional.