Common use of Two-Way Interconnection Trunks Clause in Contracts

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Onvoy, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy and Frontier. Onvoy’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyEmergency, OnvoyEmergency, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third third-party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier access this Agreement or an applicable Verizon Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyEmergency, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Emergency shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds Second (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s Verizon's network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy Emergency shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Emergency anticipates Frontier that Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Emergency and FrontierVerizon. OnvoyEmergency’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End End-Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds Second (Hundred Call SecondsSecond) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design design-blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design design-blocking objective of ▇▇▇▇-▇ ▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Emergency shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 SR-2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design design-blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Onvoy, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy and Frontier. Onvoy’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Two Way Local Interconnection Trunks for the exchange of traffic between Frontier and OnvoyTrunks, Onvoy, at its own expense, shall: 2.4.1.1 provide its own facilities prior to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing ordering any Two-Way Local Interconnection TrunksTrunks from Verizon, Onvoy Reconex shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds CCS (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Local Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Frontier’s network in (POI). 2.4.2 Two-Way Local Interconnection Trunks shall be from a LATA at which the Parties interconnect for the exchange of trafficVerizon End Office or Tandem to a mutually agreed upon POI. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection TrunksReconex is collocated in a Verizon Wire Center, the POI shall be at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection TrunksVerizon Wire Center. 2.4.4 2.4.3 On a semi-annual basis, Onvoy Reconex shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Onvoy Reconex anticipates Frontier that Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy and Frontierperiod. OnvoyReconex’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks. 2.4.6 2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) CCS equal to five (5). Either Party may disconnect End Office . 2.4.7 Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Local Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour; Two-Way Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Reconex shall engineer Two-Way Local Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275)national standards. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy 2.4.8 Reconex shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Onvoy Reconex shall order Two-Way Local Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy Reconex shall complete ASRs in accordance with OBF Ordering and Billing Forum Guidelines as in effect from time to time. 2.4.11 Frontier 2.4.9 Verizon may (but shall not be obligated to) monitor Two-Way Local Interconnection Trunk groups Groups using service results for the applicable design design-blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem final Two-Way Local Interconnection Trunk group and Onvoy Reconex has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy Reconex a Trunk Group Service Request directing Onvoy Reconex to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy Reconex will complete an ASR to establish or augment the End Office Two-Way Local Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group Group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Reconex’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Reconex shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level. 2.4.11 Upon request, Reconex will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Reconex will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour. 2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy Reconex will promptly augment all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Local Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy Reconex will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy Reconex fails to submit an ASR for Two-Way Local Interconnection Trunks in conformance with this Sectionsection, Frontier Verizon may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) ▇▇▇▇ Reconex for the excess Local Interconnection Trunks at the applicable Frontier ratesrates provided for in the Pricing Attachment. 2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.14 Because Frontier Verizon will not be in control of when the timing and how many sizing of the Two-Way Local Interconnection Trunks are established between its network and OnvoyReconex’s network, FrontierVerizon’s performance in connection with on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy 2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI. 2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic. 2.4.17 Reconex will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP-000191TAP192, including but not limited to those standards requiring that a call from Onvoy Reconex to a Frontier Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Onvoy Reconex and the Frontier Verizon End Office. 2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Reconex will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Reconex’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Reconex’s side of Reconex’s-IP, which charges shall be solely the financial responsibility of Reconex. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Reconex-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on Reconex’s side of the Reconex-IP, Reconex shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.18, if Reconex fails to provide IPs at Verizon’s Tandem or End Office(s) in accordance with this Agreement, Reconex will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Local Interconnection Trunk groups until Reconex establishes such IPs.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two2.3.1 Interconnection will be provided via two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Onvoyway trunks. Everstream, at its own expense, shall: 2.4.1.1 2.3.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 2.3.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 2.3.2 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Everstream shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. The mutually agreed upon technical and operational interfaces, procedures, grade of service and performance standards for Interconnection between the Parties will conform with all generally accepted industry standards with regard to facilities, equipment, and services. All Interconnection facilities and trunking will be ordered using industry standard ASR as referenced at ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/wholesale/ under Access Services, then Access Reference Documents. 2.3.3 Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On 2.3.4 In addition to the forecasting requirements described in Section 14.2, on a semi-annual basis, Onvoy Everstream shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Everstream anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Everstream and Frontier. OnvoyEverstream’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines Trunk Forecast template at ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/wholesale/ under Access Services, then Access Reference Documents. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as in effect at that timefacilities and/or equipment are available. 2.4.5 2.3.4.1 The forecasts will include the number, type and capacity of trunks as well as a description of major network projects anticipated for the following six months. Major network projects include trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities that are reflected by a significant increase or decrease in trunking demand for the following forecast period. 2.3.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Two- Way Interconnection Trunks. 2.4.6 2.3.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. For glare resolution, Frontier will have priority on odd trunk group member circuit identification codes, and Everstream will have priority on even trunk group member circuit identification codes, unless otherwise mutually agreed. 2.4.7 2.3.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 2.3.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy Everstream shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-SR- TSV-002275). 2.4.9 2.3.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy 2.3.10 Everstream shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy Everstream shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy Everstream shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 2.3.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy Everstream has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy Everstream a Trunk Group Service Request directing Onvoy Everstream to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy Everstream will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 2.3.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy Everstream will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy Everstream will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy Everstream fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy Everstream shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 2.3.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and OnvoyEverstream’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy 2.3.14 Everstream will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy Everstream to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy Everstream and the Frontier End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Interconnection Trunks, prior to ordering any Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoyfrom Verizon, Onvoy, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Rhythms shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds CCS (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One(POI). 2.4.2 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to Two-Way Interconnection Trunksa mutually agreed upon POI. Where the Rhythms is collocated in a Verizon Wire Center, the POI shall be at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection TrunksVerizon Wire Center. 2.4.4 2.4.3 On a semi-annual basis, Onvoy Rhythms shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Rhythms anticipates Frontier that Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy and Frontierperiod. Onvoy’s Rhythms' trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 2.4.5 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 2.4.6 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) CCS equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 2.4.7 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour; Two-Way Interconnection Trunk groups that connect to a Verizon Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Rhythms shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275)national standards. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy 2.4.8 Rhythms shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy Rhythms shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy Rhythms shall complete ASRs in accordance with OBF Ordering and Billing Forum Guidelines as in effect from time to time. 2.4.11 Frontier 2.4.9 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups Groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem Two-final Two- Way Interconnection Trunk group and Onvoy Rhythms has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy Rhythms a Trunk Group Service Request directing Onvoy Rhythms to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy Rhythms will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group Group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.10 Any Tandem Two-Way Interconnection Trunk group between the Rhythms' POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Interconnection Trunk group exceeds the 240 trunk level at any time, Rhythms shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Interconnection Trunk group does not exceed the 240 trunk level. 2.4.11 Upon request, Rhythms will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Rhythms will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy Rhythms will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy Rhythms will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy Rhythms fails to submit an ASR for Two-Two- Way Interconnection Trunks in conformance with this Sectionsection, Frontier Verizon may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) Rhythms for the excess Local Interconnection Trunks at the applicable Frontier ratesrates provided for in the Pricing Attachment. 2.4.13 The performance standard on final Two-Way Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.14 Because Frontier Verizon will not be in control of when the timing and how many sizing of the Two-Way Interconnection Trunks are established between its network and Onvoy’s Rhythms' network, FrontierVerizon’s performance in connection with on these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- tocarrier-to- carrier performance assurance guidelines or plan. 2.4.14 Onvoy 2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the applicable POI. 2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Interconnection Trunks shall only carry Reciprocal Compensation Traffic IntraLATA Toll Traffic and Internet Traffic. 2.4.17 Rhythms will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191SR- TAP192, including but not limited to those standards requiring that a call from Onvoy Rhythms to a Frontier Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Onvoy Rhythms and the Frontier Verizon End Office. 2.4.18 When the Parties implement Two-Way Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Interconnection Trunks. Rhythms will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Interconnection Trunks ride equal to Rhythms' percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Rhythms' side of Rhythms'-IP, which charges shall be solely the financial responsibility of Rhythms. Non- recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Rhythms-IP, the non- recurring charges shall be divided equally between the Parties; and,

Two-Way Interconnection Trunks. 2.4.1 2.3.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyDISH Wireless, OnvoyDISH Wireless, at its own expense, shall: 2.4.1.1 2.3.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 2.3.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a this Agreement or an applicable Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 2.3.2 Prior to establishing any Two-Way Interconnection Trunks, Onvoy DISH Wireless shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. The mutually agreed upon technical and operational interfaces, procedures, grade of service and performance standards for Interconnection between the Parties will conform with all generally accepted industry standards with regard to facilities, equipment, and services. All Interconnection facilities and trunking will be ordered using industry standard ASR as referenced at ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/wholesale/ under Access Services, then Access Reference Documents. 2.3.3 Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On 2.3.4 In addition to the forecasting requirements described in Section 14.2, on a semi-annual basis, Onvoy DISH Wireless shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy DISH Wireless anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy DISH Wireless and Frontier. OnvoyDISH Wireless’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines Trunk Forecast template at ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/wholesale/ under Access Services, then Access Reference Documents. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as in effect at that timefacilities and/or equipment are available. 2.4.5 2.3.4.1 The forecasts will include the number, type and capacity of trunks as well as a description of major network projects anticipated for the following six months. Major network projects include trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities that are reflected by a significant increase or decrease in trunking demand for the following forecast period. 2.3.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 2.3.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. For glare resolution, Frontier will have priority on odd trunk group member circuit identification codes, and DISH Wireless will have priority on even trunk group member circuit identification codes, unless otherwise mutually agreed. 2.4.7 2.3.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 2.3.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Frontier and Onvoy DISH Wireless shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 2.3.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design design-blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyNexGen, OnvoyNexGen, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier Verizon access Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyNexGen, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy NexGen shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy NexGen shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy NexGen anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy NexGen and FrontierVerizon. OnvoyNexGen’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy NexGen shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyGNAPs, OnvoyGNAPs shall order from Verizon, at its own expenseand Verizon shall provide, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Two- Way Interconnection Trunks and the Entrance Facility, on Frontierwhich such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontierapplicable Tariffs. 2.4.2 Where the Parties use Prior to ordering any Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoyfrom Verizon, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy GNAPs shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds Second (Hundred Call SecondsSecond) information, and GNAPs shall order the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks it requires and will provide Verizon and the interface specifications at the technically feasible Point(s) Point of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic(POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to the GNAPs’ designated a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Onvoy each Party GNAPs shall submit a good faith forecast to Frontier the other Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy it GNAPs anticipates Frontier that the other Party Verizon will need to provide for the next during the ensuing two (2) year period for period. to carry traffic from GNAPs to Verizon and from Verizon to GNAPs. GNAPs in its good faith performance of its obligations according to the exchange of traffic between Onvoy and Frontier. OnvoyAgreement shall provide ’s trunk forecasts in a reasonably complete manner sufficient to allow Verizon to review, process, and prepare for such trunk forecasts. shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. GNAPs will use reasonable efforts to provide forecasting according to Verizon’s reasonable forecasting guidelines as in effect at that time and Verizon will not refuse to accept, process, and act upon any such trunk forecast that substantially complies with Verizon’s reasonable and non-discriminatory trunk forecasting guidelines then in effect unless and only unless Verizon proves that GNAPs provided information that materially alters the accuracy of the information GNAPs sought to provide in the trunk forecast. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where availableavailable and where technically feasible. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds Second (Hundred Call SecondsSecond) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 B.0051 during the average time consistent busy hour. Frontier Verizon and Onvoy GNAPs shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as accepted industry standards. BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for one three (1 3) consecutive calendar traffic study months. 2.4.10 Onvoy GNAPs shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy GNAPs shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy GNAPs shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. Verizon shall reasonably accept ASRs submitted by GNAPs and shall use commercially reasonable efforts to insure timely installation and activation of such Two-Way Local Interconnection Trunks. 2.4.11 Frontier Verizon may (but shall not be obligated to) Each Party will monitor Two-Way Interconnection Trunk groups Groups using service results for the applicable design blocking objective. If Frontier a Party Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy the originating Party GNAPs has not notified Frontier the receiving Party Verizon that it has corrected such blocking, Frontier the receiving Party Verizon may submit to Onvoy the originating Party GNAPs a Trunk Group Service Request directing Onvoy the originating Party GNAPs to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy the originating Party GNAPs will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group Group with excessive blocking and submit the ASR to Frontier the receiving Party Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy GNAPs will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy GNAPs fails to submit an ASR for Two-Two- Way Interconnection Trunks in conformance with this Sectionsection, Frontier Verizon may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) GNAPs for the excess Interconnection Trunks at the applicable Frontier Verizon rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two Way Interconnection Trunks, prior to ordering any Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoyfrom Verizon, Onvoy, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy D&E shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds CCS (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One(POI). 2.4.2 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to Two-Way Interconnection Trunksa mutually agreed upon POI. Where D&E is collocated in a Verizon Wire Center, the POI shall be at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection TrunksVerizon Wire Center. 2.4.4 2.4.3 On a semi-annual basis, Onvoy D&E shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy D&E anticipates Frontier that Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy and Frontierperiod. OnvoyD&E’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 2.4.5 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 2.4.6 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) CCS equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 2.4.7 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour; Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy D&E shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275)national standards. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy 2.4.8 D&E shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy D&E shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy D&E shall complete ASRs in accordance with OBF Ordering and Billing Forum Guidelines as in effect from time to time. 2.4.11 Frontier 2.4.9 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups Groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem final Two-Way Interconnection Trunk group and Onvoy D&E has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy D&E a Trunk Group Service Request directing Onvoy D&E to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy D&E will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group Group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Daysbusiness days. 2.4.12 2.4.10 Any Tandem Two-Way Interconnection Trunk group between the D&E’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Interconnection Trunk group exceeds the 240 trunk level at any time, D&E shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Interconnection Trunk group does not exceed the 240 trunk level. 2.4.11 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy D&E will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy D&E will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy D&E fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Sectionsection, Frontier Verizon may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) ▇▇▇▇ D&E for the excess Interconnection Trunks at the applicable Frontier ratesrates provided for in the Pricing Attachment. 2.4.12 The performance standard on final Two-Way Interconnection Trunks shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.13 Because Frontier Verizon will not be in control of when the timing and how many sizing of the Two-Way Interconnection Trunks are established between its network and OnvoyD&E’s network, FrontierVerizon’s performance in connection with on these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the applicable POI. 2.4.15 Notwithstanding any other provision of this Agreement, Two-Way Interconnection Trunks shall carry only Reciprocal Compensation Traffic, IntraLATA Toll Traffic and Measured Internet Traffic. 2.4.16 D&E will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191TAP192, including but not limited to those standards requiring that a call from Onvoy D&E to a Frontier Verizon End Office will first be routed to the End Office Interconnection Trunk group between Onvoy D&E and the Frontier Verizon End Office. 2.4.17 When the Parties implement Two-Way Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Interconnection Trunks. D&E will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Interconnection Trunks ride equal to D&E’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on D&E’s side of D&E’s-IP, which charges shall be solely the financial responsibility of D&E. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the D&E-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on D&E’s side of the D&E-IP, D&E shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.18, if D&E fails to provide IPs in accordance with Section 7.1 of this Agreement, D&E will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until D&E establishes such IPs.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyCBB, OnvoyCBB, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier access this Agreement or an applicable Verizon Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyCBB, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy CBB shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy CBB shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy CBB anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy CBB and FrontierVerizon. OnvoyCBB’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy CBB shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy CBB shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy CBB shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy CBB shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy CBB has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy CBB a Trunk Group Service Request directing Onvoy CBB to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy CBB will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy CBB will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy CBB will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy CBB fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier Verizon may disconnect the excess Interconnection Trunks or bill ▇▇▇▇ (and Onvoy CBB shall pay) for the excess Interconnection Trunks at the applicable Frontier Verizon rates. 2.4.13 Because Frontier Verizon will not be in control of when and how many Two-Two- Way Interconnection Trunks are established between its network and OnvoyCBB’s network, FrontierVerizon’s performance in connection with these Two-Two- Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy CBB will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy CBB to a Frontier Verizon End Office will first be routed to the End Office Interconnection Trunk group between Onvoy CBB and the Frontier Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyCSTC, OnvoyCSTC, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third third-party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier access this Agreement or an applicable Verizon Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyCSTC, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy CSTC shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds Second (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy CSTC shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy CSTC anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy CSTC and FrontierVerizon. OnvoyCSTC’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds Second (Hundred Call SecondsSecond) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy CSTC shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyCost Plus, OnvoyCost Plus, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier Verizon access Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyCost Plus, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Cost Plus shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy Cost Plus shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Cost Plus anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Cost Plus and FrontierVerizon. OnvoyCost Plus’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Cost Plus shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyEmergency, OnvoyEmergency, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third third-party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier access this Agreement or an applicable Verizon Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyEmergency, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Emergency shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds Second (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s Verizon's network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy Emergency shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Emergency anticipates Frontier that Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Emergency and FrontierVerizon. OnvoyEmergency’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End End-Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds Second (Hundred Call SecondsSecond) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design design-blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design design-blocking objective of ▇▇▇▇-▇ ▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Emergency shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 SR-2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design design-blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two2.3.1 Interconnection will be provided via two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Onvoyway trunks. Carrier, at its own expense, shall: 2.4.1.1 2.3.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 2.3.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 2.3.2 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Carrier shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. The mutually agreed upon technical and operational interfaces, procedures, grade of service and performance standards for Interconnection between the Parties will conform with all generally accepted industry standards with regard to facilities, equipment, and services. All Interconnection facilities and trunking will be ordered using industry standard ASR as referenced at ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/wholesale/ under Access Services, then Access Reference Documents. 2.3.3 Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On 2.3.4 In addition to the forecasting requirements described in Section 14.2, on a semi-annual basis, Onvoy Carrier shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Carrier anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Carrier and Frontier. OnvoyCarrier’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines Trunk Forecast template at ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/wholesale/ under Access Services, then Access Reference Documents. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as in effect at that timefacilities and/or equipment are available. 2.4.5 2.3.4.1 The forecasts will include the number, type and capacity of trunks as well as a description of major network projects anticipated for the following six months. Major network projects include trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities that are reflected by a significant increase or decrease in trunking demand for the following forecast period. 2.3.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Two- Way Interconnection Trunks. 2.4.6 2.3.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. For glare resolution, Frontier will have priority on odd trunk group member circuit identification codes, and Carrier will have priority on even trunk group member circuit identification codes, unless otherwise mutually agreed. 2.4.7 2.3.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 2.3.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy Carrier shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 2.3.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy 2.3.10 Carrier shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy Carrier shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy Carrier shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 2.3.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy Carrier has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy Carrier a Trunk Group Service Request directing Onvoy Carrier to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy Carrier will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 2.3.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy ▇▇▇▇▇▇▇ will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy Carrier will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy Carrier fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy Carrier shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 2.3.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and OnvoyCarrier’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy 2.3.14 Carrier will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Two- Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy Carrier to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy Carrier and the Frontier End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyVoxbeam, OnvoyVoxbeam, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier Verizon access Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyVoxbeam, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Voxbeam shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy Voxbeam shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Voxbeam anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Voxbeam and FrontierVerizon. OnvoyVoxbeam’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Voxbeam shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyNUI, OnvoyNUI shall order from Verizon, at its own expenseand Verizon shall provide, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Frontier Entrance Facility, on which such Trunks will ride, and Onvoytransport and multiplexing, Frontierin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontierterms and conditions set forth in this Agreement and Verizon’s network in a LATAapplicable Tariffs. 2.4.3 2.4.2 Prior to establishing ordering any Two-Way Interconnection TrunksTrunks from Verizon, Onvoy NUI shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds Second (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic(POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Onvoy NUI shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy NUI anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Onvoy from NUI to Verizon and Frontierfrom Verizon to NUI. OnvoyNUI’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds Second (Hundred Call SecondsSecond) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy NUI shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy NUI shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy NUI shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy NUI shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups Groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy NUI has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy NUI a Trunk Group Service Request directing Onvoy NUI to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy NUI will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(sGroup(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group Group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy NUI will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy NUI will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy NUI fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Sectionsection, Frontier Verizon may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) ▇▇▇▇ NUI for the excess Interconnection Trunks at the applicable Frontier Verizon rates. 2.4.13 Because Frontier Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and OnvoyNUI’s network, FrontierVerizon’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two-Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non-complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non-complying Party’s relevant POI. 2.4.15 NUI will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy NUI to a Frontier Verizon End Office will first be routed to the End Office Interconnection Trunk group between Onvoy NUI and the Frontier Verizon End Office. 2.4.16 When the Parties implement Two-Way Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use (“PPU”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of traffic that each Party sends over the Two-Way Interconnection Trunks riding on that facility. NUI will pay a percentage of Verizon’s monthly recurring charges for each facility on which the Two-Way Interconnection Trunks ride equal to NUI’s percentage of use of that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on NUI’s side of NUI’s-IP, which charges shall be solely the financial responsibility of

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyENT, OnvoyENT, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier Verizon access Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyENT, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy ENT shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy ENT shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy ENT anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy ENT and FrontierVerizon. OnvoyENT’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy ENT shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Onvoy, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy and Frontier. Onvoy’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyCovista, OnvoyCovista, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier access this Agreement or an applicable Verizon Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyCovista, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Covista shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy Covista shall submit a good faith forecast to Frontier Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Onvoy Covista anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Covista and FrontierVerizon. OnvoyCovista’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Covista shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-SR- TSV-002275). 2.4.9 The performance standard for final Meet Point B Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy Covista shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy Covista shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy Covista shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy Covista will complete an ASR to establish or augment the End Office Meet Point A Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy Covista will promptly augment all Tandem Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy Covista will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy Covista fails to submit an ASR for Two-Two- Way Interconnection Trunks in conformance with this Section, Frontier Verizon may disconnect the excess Interconnection Trunks or bill (and Onvoy Covista shall pay) for the excess Interconnection Trunks at the applicable Frontier Verizon rates. 2.4.13 Because Frontier Verizon will not be in control of when and how many Two-Two- Way Interconnection Trunks are established between its network and OnvoyCovista’s network, FrontierVerizon’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy Covista will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-SR- TAP-000191, including but not limited to those standards requiring that a call from Onvoy Covista to a Frontier Verizon End Office will first be routed to the End Office Meet Point A Interconnection Trunk group between Onvoy Covista and the Frontier Verizon End Office. 3.1.1 Either Party may request a Fiber Meet arrangement by providing written notice thereof to the other Party; provided, however, that a Party may not make such a request if the Parties have not consistently been exchanging an amount of applicable traffic (as set forth in Section 3.1.3 below) equal to at least one (1) DS-3. Any such Fiber Meet arrangement shall be subject to the terms of this Agreement. In addition, the establishment of any Fiber Meet arrangement is expressly conditioned upon the Parties' mutually agreeing to the technical specifications and requirements for such Fiber Meet arrangement including, but not limited to, the location of the Fiber Meet points, routing, equipment (e.g., specifications of Add/Drop Multiplexers, number of strands of fiber, etc.), software, ordering, provisioning, maintenance, repair, testing, augment and on any other technical specifications or requirements necessary to implement the Fiber Meet arrangement. For each Fiber Meet arrangement the Parties agree to implement, the Parties will complete and sign a Technical Specifications and Requirements document, the form of which is attached hereto as Exhibit A to Section 2.4.14 of the Interconnection Attachment Fiber Meet Arrangement Provisions. Each such document will be treated as confidential information. 3.1.2 The Parties agree to consider the possibility of using existing fiber cable with spare capacity, where available, to implement any such request for a Fiber Meet arrangement. If existing fiber cable with spare capacity is not available, the Parties agree to minimize the construction and deployment of fiber cable necessary for any Fiber Meet arrangement to which they agree. Except as otherwise agreed by the Parties, any and all Fiber Meet points established between the Parties shall extend no further than three (3) miles from an applicable Verizon Wire Center and Verizon shall not be required to construct or deploy more than five hundred (500) feet of fiber cable for a Fiber Meet arrangement. 3.1.3 Except as otherwise agreed by the Parties, any Fiber Meet arrangements established under this Agreement shall be used only for the transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA toll traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and Measured Internet Traffic, all in accordance with this Agreement. Operator services/directory assistance traffic, 911 traffic, and Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between Covista Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem, may be exchanged over Fiber Meet arrangements subject to applicable Verizon Tariff rates and charges. Except as otherwise agreed by the Parties, point-to-point (i.e., unswitched) access services and unbundled network elements shall not be provisioned on or accessed through Fiber Meet arrangements. Notwithstanding any other provision of this Agreement or otherwise, other than the obligation to pay any applicable intercarrier compensation charges pursuant to the terms of this Agreement, neither Party shall have any obligation to pay the other Party any charges in connection with any Fiber Meet arrangements established under this Agreement. 3.1.4 Covista will include traffic to be exchanged over Fiber Meet arrangements in its forecasts provided to Verizon under this Agreement.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Two Way Local Interconnection Trunks for the exchange of traffic between Frontier and OnvoyTrunks, Onvoy, at its own expense, shall: 2.4.1.1 provide its own facilities prior to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing ordering any Two-Way Local Interconnection TrunksTrunks from Verizon, Onvoy Direct2Internet shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds CCS (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Local Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Frontier’s network in (POI). 2.4.2 Two-Way Local Interconnection Trunks shall be from a LATA at which the Parties interconnect for the exchange of trafficVerizon End Office or Tandem to a mutually agreed upon POI. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection TrunksDirect2Internet is collocated in a Verizon Wire Center, the POI shall be at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection TrunksVerizon Wire Center. 2.4.4 2.4.3 On a semi-annual basis, Onvoy Direct2Internet shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Onvoy Direct2Internet anticipates Frontier that Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy and Frontierperiod. OnvoyDirect2Internet’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks. 2.4.6 2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) CCS equal to five (5). Either Party may disconnect End Office . 2.4.7 Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Local Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour; Two-Way Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Direct2Internet shall engineer Two-Way Local Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275)national standards. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy 2.4.8 Direct2Internet shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Onvoy Direct2Internet shall order Two-Way Local Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy Direct2Internet shall complete ASRs in accordance with OBF Ordering and Billing Forum Guidelines as in effect from time to time. 2.4.11 Frontier 2.4.9 Verizon may (but shall not be obligated to) monitor Two-Way Local Interconnection Trunk groups Groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem final Two-Way Local Interconnection Trunk group and Onvoy Direct2Internet has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy Direct2Internet a Trunk Group Service Request directing Onvoy Direct2Internet to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy Direct2Internet will complete an ASR to establish or augment the End Office Two-Way Local Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group Group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Daysbusiness days. 2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Direct2Internet’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Direct2Internet shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level. 2.4.11 Upon request, Direct2Internet will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Direct2Internet will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour. 2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy Direct2Internet will promptly augment all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Local Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy Direct2Internet will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy Direct2Internet fails to submit an ASR for Two-Way Local Interconnection Trunks in conformance with this Sectionsection, Frontier Verizon may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) Direct2Internet for the excess Local Interconnection Trunks at the applicable Frontier ratesrates provided for in the Pricing Attachment. 2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.14 Because Frontier Verizon will not be in control of when the timing and how many sizing of the Two-Way Local Interconnection Trunks are established between its network and OnvoyDirect2Internet’s network, FrontierVerizon’s performance in connection with on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy 2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI. 2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic. 2.4.17 Direct2Internet will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP-000191SR- TAP192, including but not limited to those standards requiring that a call from Onvoy Direct2Internet to a Frontier Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Onvoy Direct2Internet and the Frontier Verizon End Office. 2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Direct2Internet will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Direct2Internet’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Direct2Internet’s side of Direct2Internet’s-IP, which charges shall be solely the financial responsibility of Direct2Internet. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Direct2Internet-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on Direct2Internet’s side of the Direct2Internet-IP, Direct2Internet shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.18, if Direct2Internet fails to provide IPs at Verizon’s Tandem or End Office(s) in accordance with this Agreement, Direct2Internet will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two- Way Local Interconnection Trunk groups until Direct2Internet establishes such IPs.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyTalk America, OnvoyTalk America, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier Verizon access Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyTalk America, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Talk America shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy Talk America shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Talk America anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Talk America and FrontierVerizon. OnvoyTalk America’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Talk America shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyNeutral Tandem, OnvoyNeutral Tandem, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier Verizon access Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyNeutral Tandem, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Neutral Tandem shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy Neutral Tandem shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Neutral Tandem anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Neutral Tandem and FrontierVerizon. OnvoyNeutral Tandem’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Neutral Tandem shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy Neutral Tandem shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy Neutral Tandem shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy Neutral Tandem shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy Neutral Tandem has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy Neutral Tandem a Trunk Group Service Request directing Onvoy Neutral Tandem to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy Neutral Tandem will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy Neutral Tandem will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy Neutral Tandem will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy Neutral Tandem fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier with ten (10) days prior written notice to Neutral Tandem, Verizon may disconnect the excess Interconnection Trunks or bill (and Onvoy Neutral Tandem shall pay) for the excess Interconnection Trunks at the applicable Frontier Verizon rates. 2.4.13 Because Frontier Verizon will not be in control of when and how many Two-Two- Way Interconnection Trunks are established between its network and OnvoyNeutral Tandem’s network, FrontierVerizon’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy Neutral Tandem will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191TAP- 000191, including but not limited to those standards requiring that a call from Onvoy Neutral Tandem to a Frontier Verizon End Office will first be routed to the End Office Interconnection Trunk group between Onvoy Neutral Tandem and the Frontier Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyTWCIS, OnvoyTWCIS, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier Verizon access Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyTWCIS, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy TWCIS shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy TWCIS shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy TWCIS anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy TWCIS and FrontierVerizon. OnvoyTWCIS’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy TWCIS shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and Onvoy▇▇▇, Onvoy▇▇▇ shall order from Verizon, at its own expenseand Verizon shall provide, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Frontier Entrance Facility, on which such Trunks will ride, and Onvoytransport and multiplexing, Frontierin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontierterms and conditions set forth in this Agreement and Verizon’s network in a LATAapplicable Tariffs. 2.4.3 2.4.2 Prior to establishing ordering any Two-Way Interconnection TrunksTrunks from Verizon, Onvoy IG2 shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds Second (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic(POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Onvoy IG2 shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy IG2 anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Onvoy from IG2 to Verizon and Frontierfrom Verizon to IG2. OnvoyIG2’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time.time.‌‌‌‌‌‌‌ 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds Second (Hundred Call SecondsSecond) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy IG2 shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyNavtel, OnvoyNavtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third third-party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier access this Agreement or an applicable Verizon Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyNavtel, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Navtel shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds Second (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy Navtel shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Navtel anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Navtel and FrontierVerizon. OnvoyNavtel’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds Second (Hundred Call SecondsSecond) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Navtel shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Onvoy, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy and Frontier. Onvoy’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-- ▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Two- Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Two- Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoySpectrotel, OnvoySpectrotel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoySpectrotel, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Spectrotel shall meet with Frontier to conduct a joint planning meeting (“Joint ―Joint Planning Meeting”Meeting‖). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy Spectrotel shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Spectrotel anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Spectrotel and Frontier. OnvoySpectrotel’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy Spectrotel shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyCCES, OnvoyCCES, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyCCES, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy CCES shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy CCES shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy CCES anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy CCES and Frontier. OnvoyCCES’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Frontier and Onvoy CCES shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyYmax, OnvoyYmax, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier access this Agreement or an applicable Verizon Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyYmax, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Ymax shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy Ymax shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Ymax anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Ymax and FrontierVerizon. OnvoyYmax’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Ymax shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy Ymax shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy Ymax shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy Ymax shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy Ymax has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy Ymax a Trunk Group Service Request directing Onvoy Ymax to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy Ymax will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy Ymax will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy Ymax will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy Ymax fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier Verizon may disconnect the excess Interconnection Trunks or bill ▇▇▇▇ (and Onvoy Ymax shall pay) for the excess Interconnection Trunks at the applicable Frontier Verizon rates. 2.4.13 Because Frontier Verizon will not be in control of when and how many Two-Two- Way Interconnection Trunks are established between its network and OnvoyYmax’s network, FrontierVerizon’s performance in connection with these Two-Two- Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy Ymax will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy Ymax to a Frontier Verizon End Office will first be routed to the End Office Interconnection Trunk group between Onvoy Ymax and the Frontier Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyNavtel, OnvoyNavtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third third-party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier access this Agreement or an applicable Verizon Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyNavtel, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Navtel shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds Second (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy Navtel shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Navtel anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Navtel and FrontierVerizon. OnvoyNavtel’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds Second (Hundred Call SecondsSecond) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Navtel shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and Onvoy365, Onvoy365, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier Verizon access Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and Onvoy365, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy 365 shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy 365 shall submit a good faith forecast to Frontier Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Onvoy 365 anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy 365 and FrontierVerizon. Onvoy365’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy 365 shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275TSV- 002275). 2.4.9 The performance standard for final Meet Point B Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy 365 shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy 365 shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy 365 shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem Meet Point B (final) Two-Way Interconnection Trunk group and Onvoy 365 has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy 365 a Trunk Group Service Request directing Onvoy 365 to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy 365 will complete an ASR to establish or augment the End Office Meet Point A Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy 365 will promptly augment all Tandem Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy 365 will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy 365 fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier Verizon may disconnect the excess Interconnection Trunks or bill ▇▇▇▇ (and Onvoy 365 shall pay) for the excess Interconnection Trunks at the applicable Frontier Verizon rates. 2.4.13 Because Frontier Verizon will not be in control of when and how many Two-Two- Way Interconnection Trunks are established between its network and Onvoy365’s network, FrontierVerizon’s performance in connection with these Two-Two- Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy 365 will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-TAP-000191TAP- 000191, including but not limited to those standards requiring that a call from Onvoy 365 to a Frontier Verizon End Office will first be routed to the End Office Meet Point A Interconnection Trunk group between Onvoy 365 and the Frontier Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyWVN, OnvoyWVN, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyWVN, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy WVN shall meet with Frontier to conduct a joint planning meeting (“Joint ―Joint Planning Meeting”Meeting‖). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy WVN shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy WVN anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy WVN and Frontier. OnvoyWVN’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy WVN shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Two Way Local Interconnection Trunks for the exchange of traffic between Frontier and OnvoyTrunks, Onvoy, at its own expense, shall: 2.4.1.1 provide its own facilities prior to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing ordering any Two-Way Local Interconnection TrunksTrunks from Verizon, Onvoy Norcom shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds CCS (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Local Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Frontier’s network in (POI). 2.4.2 Two-Way Local Interconnection Trunks shall be from a LATA at which the Parties interconnect for the exchange of trafficVerizon End Office or Tandem to a mutually agreed upon POI. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection TrunksNorcom is collocated in a Verizon Wire Center, the POI shall be at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection TrunksVerizon Wire Center. 2.4.4 2.4.3 On a semi-annual basis, Onvoy Norcom shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Local Interconnection Trunks that Onvoy Norcom anticipates Frontier that Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy and Frontierperiod. OnvoyNorcom’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 2.4.4 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Local Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Local Interconnection Trunks. 2.4.6 2.4.5 Two-Way Local Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 2.4.6 With respect to End Office Two-Way Local Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) CCS equal to five (5). Either Party may disconnect End Office . 2.4.7 Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Local Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour; Two-Way Local Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇ ▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Norcom shall engineer Two-Way Local Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275)national standards. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy 2.4.8 Norcom shall determine and order the number of Two-Way Local Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Local Interconnection Trunk group. Onvoy Norcom shall order Two-Way Local Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Local Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy Norcom shall complete ASRs in accordance with OBF Ordering and Billing Forum Guidelines as in effect from time to time. 2.4.11 Frontier 2.4.9 Verizon may (but shall not be obligated to) monitor Two-Way Local Interconnection Trunk groups Groups using service results for the applicable design design-blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem final Two-Way Local Interconnection Trunk Tr unk group and Onvoy Norcom has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy Norcom a Trunk Group Service Request directing Onvoy Norcom to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy Norcom will complete an ASR to establish or augment the End Office Two-Way Local Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group Group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.10 Any Tandem Two-Way Local Interconnection Trunk group between the Norcom’s POI and a Verizon Tandem will be limited to a maximum of 240 trunks unless otherwise agreed to by the Parties. In the event that any Tandem Two-Way Local Interconnection Trunk group exceeds the 240 trunk level at any time, Norcom shall promptly submit an ASR to Verizon to establish new or additional End Office Trunk groups to insure that such Tandem Two-Way Local Interconnection Trunk group does not exceed the 240 trunk level. 2.4.11 Upon request, Norcom will submit a written report to Verizon each month setting forth trunk utilization information and percentages. Norcom will calculate utilization percentages by using a traffic data analyzation system specified by Verizon, industry standard study periods and a time consistent busy hour. 2.4.12 The Parties will review all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy Norcom will promptly augment all Tandem Two-Way Local Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Local Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy Norcom will promptly submit ASRs to disconnect a sufficient number of Local Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy Norcom fails to submit an ASR for Two-Way Local Interconnection Trunks in conformance with this Sectionsection, Frontier Verizon may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) ▇▇▇▇ ▇▇▇▇▇▇ for the excess Local Interconnection Trunks at the applicable Frontier ratesrates provided for in the Pricing Attachment. 2.4.13 The performance standard on final Two-Way Local Interconnection Trunks shall be that no such Local Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.14 Because Frontier Verizon will not be in control of when the timing and how many sizing of the Two-Way Local Interconnection Trunks are established between its network and OnvoyNorcom’s network, FrontierVerizon’s performance in connection with on these Two-Way Local Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy 2.4.15 Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Local Interconnection Trunk group and install One-Way Local Interconnection Trunks to the applicable POI. 2.4.16 Notwithstanding any other provision of this Agreement, Two-Way Local Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic. 2.4.17 Norcom will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Two-Way Local Interconnection Trunks in accordance with SR-TAP-000191TAP192, including but not limited to those standards requiring that a call from Onvoy Norcom to a Frontier Verizon End Office will first be routed to the End Office Local Interconnection Trunk group between Onvoy Norcom and the Frontier Verizon End Office. 2.4.18 When the Parties implement Two-Way Local Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Local Interconnection Trunks. Norcom will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Local Interconnection Trunks ride equal to Norcom’s percentage of use of the facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Norcom’s side of Norcom’s-IP, which charges shall be solely the financial responsibility of Norcom. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the Trunks on Verizon’s side of the Norcom-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on Norcom’s side of the Norcom-IP, Norcom shall be solely responsible for the non- recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.18, if Norcom fails to provide IPs at Verizon’s Tandem or End Office(s) in accordance with this Agreement, Norcom will be responsible for one hundred percent (100%) of all recurring and non- recurring charges associated with Two-Way Local Interconnection Trunk groups until Norcom establishes such IPs.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyHello Depot, OnvoyHello Depot, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third third-party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier access this Agreement or an applicable Verizon Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyHello Depot, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Hello Depot shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds Second (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy Hello Depot shall submit a good faith forecast to Frontier Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Onvoy Hello Depot anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Hello Depot and FrontierVerizon. OnvoyHello Depot’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds Second (Hundred Call SecondsSecond) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Hello Depot shall engineer Two-Two- Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Meet Point B Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy Hello Depot shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy Hello Depot shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy Hello Depot shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem Meet Point B (final) Two-Way Interconnection Trunk group and Onvoy Hello Depot has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy Hello Depot a Trunk Group Service Request directing Onvoy Hello Depot to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy Hello Depot will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy Hello Depot will promptly augment all Tandem Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy Hello Depot will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy Hello Depot fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier Verizon may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) ▇▇▇▇ Hello Depot for the excess Interconnection Trunks at the applicable Frontier Verizon rates. 2.4.13 Because Frontier Verizon will not be in control of when and how many Two-Two- Way Interconnection Trunks are established between its network and OnvoyHello Depot’s network, FrontierVerizon’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy Hello Depot will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-SR- TAP-000191, including but not limited to those standards requiring that a call from Onvoy Hello Depot to a Frontier Verizon End Office will first be routed to the End Office Meet Point A Interconnection Trunk group between Onvoy Hello Depot and the Frontier Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy▇▇▇▇ Tell, Onvoy▇▇▇▇ Tell, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy▇▇▇▇ Tell, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy ▇▇▇▇ Tell shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy ▇▇▇▇ Tell shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy ▇▇▇▇ Tell anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy ▇▇▇▇ Tell and Frontier. Onvoy▇▇▇▇ Tell ’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy ▇▇▇▇ Tell shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 2.3.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyDISH Wireless, OnvoyDISH Wireless, at its own expense, shall: 2.4.1.1 2.3.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 2.3.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a this Agreement or an applicable Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 2.3.2 Prior to establishing any Two-Way Interconnection Trunks, Onvoy DISH Wireless shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. The mutually agreed upon technical and operational interfaces, procedures, grade of service and performance standards for Interconnection between the Parties will conform with all generally accepted industry standards with regard to facilities, equipment, and services. All Interconnection facilities and trunking will be ordered using industry standard ASR as referenced at ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/wholesale/ under Access Services, then Access Reference Documents. 2.3.3 Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On 2.3.4 In addition to the forecasting requirements described in Section 14.2, on a semi-annual basis, Onvoy DISH Wireless shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy DISH Wireless anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy DISH Wireless and Frontier. OnvoyDISH Wireless’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines Trunk Forecast template at ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/wholesale/ under Access Services, then Access Reference Documents. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as in effect at that timefacilities and/or equipment are available. 2.4.5 2.3.4.1 The forecasts will include the number, type and capacity of trunks as well as a description of major network projects anticipated for the following six months. Major network projects include trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities that are reflected by a significant increase or decrease in trunking demand for the following forecast period. 2.3.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 2.3.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. For glare resolution, Frontier will have priority on odd trunk group member circuit identification codes, and DISH Wireless will have priority on even trunk group member circuit identification codes, unless otherwise mutually agreed. 2.4.7 2.3.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 2.3.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy DISH Wireless shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 2.3.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design design-blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyCenturyLink, OnvoyCenturyLink, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATAEAB Location(s); and/or 2.4.1.2 obtain transport facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (aEAB Locations(s) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyCenturyLink, FrontierVerizon, at its own expense, shall shall: 2.4.2.1 provide its own facilities to the technically feasible Point(sEAB Locations(s); and/or 2.4.2.2 obtain facilities to the EAB Location(s) of Interconnection on Frontier’s network in from a LATAthird party. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy CenturyLink shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(sEAB Location(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On Since the Parties have a longstanding traffic history, on an as needed basis but no less frequently than semi-annual basisannually, Onvoy the Parties shall submit meet and provide to each other a good faith trunk forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy anticipates Frontier will need to provide be needed during the ensuing two (2) year period for the exchange of traffic between Onvoy CenturyLink and FrontierVerizon. OnvoyCenturyLink’s trunk forecasts shall conform to the Frontier CLEC Verizon trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling, where available. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Verizon Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy CenturyLink shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 SR-2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its the B.005 design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy The Parties shall determine and establish, via a mutually agreed order documents, the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but Both Parties shall not be obligated to) monitor the Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier either Party observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blockingblocking objective, Frontier may submit the Parties will promptly take action to Onvoy a Trunk Group Service Request directing Onvoy to remedy expedite resolution of the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Dayssituation. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy The Parties will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for establishing additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy the Parties will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy Each Party will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier the other Party over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-SR- TAP-000191, including but not limited to those standards requiring that a call from Onvoy Party A to a Frontier Party B End Office will first be routed to the End Office Interconnection Trunk group between Onvoy Party A and the Frontier Party B End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two2.3.1 Interconnection will be provided via two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Onvoyway trunks. Yorkstream, at its own expense, shall: 2.4.1.1 2.3.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 2.3.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 2.3.2 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Yorkstream shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where The mutually agreed upon technical and operational interfaces, procedures, grade of service and performance standards for Interconnection between the Parties will conform with all generally accepted industry standards with regard to facilities, equipment, and services. All Interconnection facilities and trunking will be ordered using industry standard ASR as referenced at ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/wholesale/ under Access Services, then Access Reference Documents. 2.3.3 When the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On 2.3.4 In addition to the forecasting requirements described in Section 15.2, on a semi-annual basis, Onvoy Yorkstream shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Yorkstream anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Yorkstream and Frontier. OnvoyYorkstream’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines Trunk Forecast template at ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/wholesale/ under Access Services, then Access Reference Documents. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as in effect at that timefacilities and/or equipment are available. 2.4.5 2.3.4.1 The forecasts will include the number, type and capacity of trunks as well as a description of major network projects anticipated for the following six months. Major network projects include trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities that are reflected by a significant increase or decrease in trunking demand for the following forecast period. 2.3.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 2.3.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize use B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. For glare resolution, Frontier will have priority on odd trunk group member circuit identification codes, and Yorkstream will have priority on even trunk group member circuit identification codes, unless otherwise mutually agreed. 2.4.7 2.3.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 2.3.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Frontier and Onvoy Yorkstream shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 2.3.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyTCG , OnvoyTCG , at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyTCG , Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy TCG shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy TCG shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy TCG anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy TCG and Frontier. OnvoyTCG ’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Frontier and Onvoy TCG shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyDNA, OnvoyDNA, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third third-party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier access this Agreement or an applicable Verizon Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyDNA, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy DNA shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds Second (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy DNA shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy DNA anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy DNA and FrontierVerizon. OnvoyDNA’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds Second (Hundred Call SecondsSecond) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy DNA shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyCovista, OnvoyCovista, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier access this Agreement or an applicable Verizon Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyCovista, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Covista shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy Covista shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Covista anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Covista and FrontierVerizon. OnvoyCovista’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Covista shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy Covista shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy Covista shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy Covista shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy Covista has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy Covista a Trunk Group Service Request directing Onvoy Covista to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy Covista will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy Covista will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy Covista will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy Covista fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier Verizon may disconnect the excess Interconnection Trunks or bill ▇▇▇▇ (and Onvoy Covista shall pay) for the excess Interconnection Trunks at the applicable Frontier Verizon rates. 2.4.13 Because Frontier Verizon will not be in control of when and how many Two-Two- Way Interconnection Trunks are established between its network and OnvoyCovista’s network, FrontierVerizon’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy Covista will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy Covista to a Frontier Verizon End Office will first be routed to the End Office Interconnection Trunk group between Onvoy Covista and the Frontier Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyCLC, OnvoyCLC, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyCLC, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy CLC shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy CLC shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy CLC anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy CLC and Frontier. OnvoyCLC’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Frontier and Onvoy CLC shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyPacOptic, OnvoyPacOptic, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier Verizon access Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyPacOptic, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy PacOptic shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy PacOptic shall submit a good faith forecast to Frontier Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Onvoy PacOptic anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy PacOptic and FrontierVerizon. OnvoyPacOptic’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy PacOptic shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275TSV- 002275). 2.4.9 The performance standard for final Meet Point B Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy PacOptic shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy PacOptic shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy PacOptic shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem Meet Point B (final) Two-Way Interconnection Trunk group and Onvoy PacOptic has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy PacOptic a Trunk Group Service Request directing Onvoy PacOptic to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy PacOptic will complete an ASR to establish or augment the End Office Two-Meet Point A Two- Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy PacOptic will promptly augment all Tandem Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy PacOptic will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy PacOptic fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier Verizon may disconnect the excess Interconnection Trunks or bill ▇▇▇▇ (and Onvoy PacOptic shall pay) for the excess Interconnection Trunks at the applicable Frontier Verizon rates. 2.4.13 Because Frontier Verizon will not be in control of when and how many Two-Two- Way Interconnection Trunks are established between its network and OnvoyPacOptic’s network, FrontierVerizon’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy PacOptic will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-SR- TAP-000191, including but not limited to those standards requiring that a call from Onvoy PacOptic to a Frontier Verizon End Office will first be routed to the End Office Meet Point A Interconnection Trunk group between Onvoy PacOptic and the Frontier Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyCiera, OnvoyCiera shall order from Verizon, at its own expenseand Verizon shall provide, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Frontier Entrance Facility, on which such Trunks will ride, and Onvoytransport and multiplexing, Frontierin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontierterms and conditions set forth in this Agreement and Verizon’s network in a LATAapplicable Tariffs. 2.4.3 2.4.2 Prior to establishing ordering any Two-Way Interconnection TrunksTrunks from Verizon, Onvoy Ciera shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds Second (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic(POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Onvoy Ciera shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Ciera anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Onvoy from Ciera to Verizon and Frontierfrom Verizon to Ciera. OnvoyCiera’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds Second (Hundred Call SecondsSecond) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-- ▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Ciera shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy Ciera shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy Ciera shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy Ciera shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups Groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy Ciera has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy Ciera a Trunk Group Service Request directing Onvoy Ciera to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy Ciera will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group Group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy Ciera will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy Ciera will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy Ciera fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Sectionsection, Frontier Verizon may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) ▇▇▇▇ ▇▇▇▇▇ for the excess Interconnection Trunks at the applicable Frontier Verizon rates. 2.4.13 Because Frontier Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and OnvoyCiera’s network, FrontierVerizon’s performance in connection with these Two-Two- Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI. 2.4.15 Ciera will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy Ciera to a Frontier Verizon End Office will first be routed to the End Office Interconnection Trunk group between Onvoy Ciera and the Frontier Verizon End Office. 2.4.16 When the Parties implement Two-Way Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use (“PPU”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of traffic that each Party sends over the Two-Way Interconnection Trunks riding on that facility. Ciera will pay a percentage of Verizon’s monthly recurring charges for each facility on which the Two-Way Interconnection Trunks ride equal to Ciera’s percentage of use of that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Ciera’s side of Ciera’s-IP, which charges shall be solely the financial responsibility of Ciera. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two- Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the facility on Verizon’s side of the Ciera-IP, Ciera shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on Ciera’s side of the Ciera-IP, Ciera shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if Ciera fails to provide Ciera-IPs in accordance with this Agreement, Ciera will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until Ciera establishes such Ciera-IPs.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two2.3.1 Interconnection will be provided via two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Onvoyway trunks. CTSI, at its own expense, shall: 2.4.1.1 2.3.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 2.3.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 2.3.2 Prior to establishing any Two-Way Interconnection Trunks, Onvoy CTSI shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. The mutually agreed upon technical and operational interfaces, procedures, grade of service and performance standards for Interconnection between the Parties will conform with all generally accepted industry standards with regard to facilities, equipment, and services. All Interconnection facilities and trunking will be ordered using industry standard ASR as referenced at ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/wholesale/ under Access Services, then Access Reference Documents. 2.3.3 Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On 2.3.4 In addition to the forecasting requirements described in Section 14.2, on a semi-annual basis, Onvoy CTSI shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy CTSI anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy CTSI and Frontier. OnvoyCTSI’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines Trunk Forecast template at ▇▇▇▇▇://▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/wholesale/ under Access Services, then Access Reference Documents. Orders for trunks that exceed forecasted quantities for forecasted locations will be accommodated as in effect at that timefacilities and/or equipment are available. 2.4.5 2.3.4.1 The forecasts will include the number, type and capacity of trunks as well as a description of major network projects anticipated for the following six months. Major network projects include trunking or network rearrangements, shifts in anticipated traffic patterns, or other activities that are reflected by a significant increase or decrease in trunking demand for the following forecast period. 2.3.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 2.3.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. For glare resolution, Frontier will have priority on odd trunk group member circuit identification codes, and CTSI will have priority on even trunk group member circuit identification codes, unless otherwise mutually agreed. 2.4.7 2.3.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 2.3.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy CTSI shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 2.3.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyAT&T Mobility, OnvoyAT&T Mobility, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third third-party, or, (b) if Frontier offers such transport pursuant to a this Agreement or an applicable Frontier access Tariff, from Frontier. 2.4.2 Where When AT&T Mobility orders Facilities from Frontier, AT&T shall be responsible for 70% of the recurring and non-recurring two-way facility and Frontier will be responsible for 30% of the recurring and non- recurring two-way facility. Up to two (2) times per year the Parties agree to review traffic volumes at a mutually agreeable time and adjust the billing percentages according to the then relative usage and formalize any change with an amendment to this Agreement. Any change to the relative use Twofactor will, pursuant to this Section 2.4.2 will be based on intraMTA traffic only. InterMTA traffic and transit traffic will not be taken into account when determining the relative usage on any two-Way Interconnection Trunks way facility. The Parties agree, AT&T will ▇▇▇▇ Frontier for the exchange portion of traffic between the facilities Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATAis responsible for. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy AT&T Mobility shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds Second (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s 's network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy and Frontier. Onvoy’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time.This Section Intentionally Left Blank 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End End-Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds Second (Hundred Call SecondsSecond) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design design-blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design design-blocking objective of ▇▇▇▇-▇ ▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy AT&T Mobility shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 SR-2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design design-blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyCLC , OnvoyCLC , at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyCLC, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy CLC shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). ? At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy CLC shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy CLC anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy CLC and Frontier. OnvoyCLC’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 ▇.01 during the average time consistent busy hour. Frontier and Onvoy CLC shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyEdnetics, OnvoyEdnetics, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyEdnetics, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Ednetics shall meet with Frontier to conduct a joint planning meeting (“Joint ―Joint Planning Meeting”Meeting‖). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy Ednetics shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Ednetics anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Ednetics and Frontier. OnvoyEdnetics’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy Ednetics shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 2.3.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyINdigital, OnvoyINdigital, at its own expense, shall: 2.4.1.1 2.3.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 2.3.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 2.3.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyINdigital, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 2.3.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy INdigital shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 2.3.4 On a semi-annual basis, Onvoy INdigital shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy INdigital anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy INdigital and Frontier. OnvoyINdigital’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 2.3.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 2.3.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 2.3.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 2.3.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy INdigital shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 2.3.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoySnappy Phone, OnvoySnappy Phone shall order from Verizon, at its own expenseand Verizon shall provide, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Frontier Entrance Facility, on which such Trunks will ride, and Onvoytransport and multiplexing, Frontierin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontierterms and conditions set forth in this Agreement and Verizon’s network in a LATAapplicable Tariffs. 2.4.3 2.4.2 Prior to establishing ordering any Two-Way Interconnection TrunksTrunks from Verizon, Onvoy Snappy Phone shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds Second (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic(POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Onvoy Snappy Phone shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Snappy Phone anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Onvoy from Snappy Phone to Verizon and Frontierfrom Verizon to Snappy Phone. OnvoySnappy Phone’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds Second (Hundred Call SecondsSecond) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-- ▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy Snappy Phone shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy Snappy Phone shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy Snappy Phone shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy Snappy Phone shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups Groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy Snappy Phone has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy Snappy Phone a Trunk Group Service Request directing Onvoy Snappy Phone to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy Snappy Phone will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group Group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy Snappy Phone will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy Snappy Phone will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy Snappy Phone fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Sectionsection, Frontier Verizon may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) Snappy Phone for the excess Interconnection Trunks at the applicable Frontier Verizon rates. 2.4.13 Because Frontier Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and OnvoySnappy Phone’s network, FrontierVerizon’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy Upon three (3) months prior written notice and with the mutual agreement of the Parties, either Party may withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the other Party’s relevant POI, provided that, if a Party has failed to comply with this Agreement with regard to Two- Way Interconnection Trunks, the other Party may upon three (3) months prior written notice and without mutual agreement of the non- complying Party, withdraw its traffic from a Two-Way Interconnection Trunk group and install One-Way Interconnection Trunks to the non- complying Party’s relevant POI. 2.4.15 Snappy Phone will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191TAP- 000191, including but not limited to those standards requiring that a call from Onvoy Snappy Phone to a Frontier Verizon End Office will first be routed to the End Office Interconnection Trunk group between Onvoy Snappy Phone and the Frontier Verizon End Office. 2.4.16 When the Parties implement Two-Way Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use (“PPU”) factor for each facility on which the Two-Way Interconnection Trunks ride, based on the total number of minutes of traffic that each Party sends over the Two-Way Interconnection Trunks riding on that facility. Snappy Phone will pay a percentage of Verizon’s monthly recurring charges for each facility on which the Two-Way Interconnection Trunks ride equal to Snappy Phone’s percentage of use of that facility as shown by the PPU. The PPU shall not be applied to calculate the charges for any portion of a facility that is on Snappy Phone’s side of Snappy Phone’s-IP, which charges shall be solely the financial responsibility of Snappy Phone. During the first full calendar quarter (and any partial calendar quarter preceding such first full calendar quarter) after the first Two-Way Interconnection Trunk is established on a facility, the PPU for that facility will be fifty percent (50%) for each Party. For each calendar quarter thereafter, the Parties shall recalculate the PPU using actual traffic usage data for the preceding calendar quarter. Non-recurring charges for the facility on which the Two-Way Interconnection Trunks ride shall be apportioned as follows: (a) for the portion of the facility on Verizon’s side of the Snappy Phone-IP, Snappy Phone shall pay fifty percent (50%) of the Verizon non- recurring charges; and, (b) for the portion of the facility on Snappy Phone’s side of the Snappy Phone-IP, Snappy Phone shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if Snappy Phone fails to provide Snappy Phone-IPs in accordance with this Agreement, Snappy Phone will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until Snappy Phone establishes such Snappy Phone-IPs.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyWiMacTel, OnvoyWiMacTel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier Verizon access Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyWiMacTel, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy WiMacTel shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy WiMacTel shall submit a good faith forecast to Frontier Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Onvoy WiMacTel anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy WiMacTel and FrontierVerizon. OnvoyWiMacTel’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy WiMacTel shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275TSV- 002275). 2.4.9 The performance standard for final Meet Point B Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy WiMacTel shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy WiMacTel shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy WiMacTel shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem Meet Point B (final) Two-Way Interconnection Trunk group and Onvoy WiMacTel has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy WiMacTel a Trunk Group Service Request directing Onvoy WiMacTel to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy WiMacTel will complete an ASR to establish or augment the End Office Two-Meet Point A Two- Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy WiMacTel will promptly augment all Tandem Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy WiMacTel will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy WiMacTel fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier Verizon may disconnect the excess Interconnection Trunks or bill (and Onvoy WiMacTel shall pay) for the excess Interconnection Trunks at the applicable Frontier Verizon rates. 2.4.13 Because Frontier Verizon will not be in control of when and how many Two-Two- Way Interconnection Trunks are established between its network and OnvoyWiMacTel’s network, FrontierVerizon’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy WiMacTel will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-SR- TAP-000191, including but not limited to those standards requiring that a call from Onvoy WiMacTel to a Frontier Verizon End Office will first be routed to the End Office Meet Point A Interconnection Trunk group between Onvoy WiMacTel and the Frontier Verizon End Office. 3.1.1 Each Party may request a Fiber Meet arrangement by providing written notice thereof to the other Party if each of the following conditions has been met: (a) the Parties have consistently been exchanging an amount of applicable traffic (as set forth in Section 3.1.3 below) in the relevant exchanges equal to at least one (1) DS-3 and (b) neither WiMacTel nor any of WiMacTel’s affiliates has an overdue balance on any bill rendered to WiMacTel or WiMacTel’s affiliates for charges that are not subject to a good faith dispute. Any such Fiber Meet arrangement shall be subject to the terms of this Agreement. In addition, the establishment of any Fiber Meet arrangement is expressly conditioned upon the Parties mutually agreeing to the technical specifications and requirements for such Fiber Meet arrangement including, but not limited to, the location of the Fiber Meet points, routing, equipment (e.g., specifications of Add/Drop Multiplexers, number of strands of fiber, etc.), software, ordering, provisioning, maintenance, repair, testing, augment and on any other technical specifications or requirements necessary to implement the Fiber Meet arrangement. For each Fiber Meet arrangement the Parties agree to implement, the Parties will complete and sign a Technical Specifications and Requirements document, the form of which is attached hereto as Exhibit A to Section 3 of the Interconnection Attachment Fiber Meet Arrangement Provisions. Each such document will be treated as Confidential Information. 3.1.2 The Parties agree to consider the possibility of using existing fiber cable with spare capacity, where available, to implement any such request for a Fiber Meet arrangement. If existing fiber cable with spare capacity is not available, the Parties agree to minimize the construction and deployment of fiber cable necessary for any Fiber Meet arrangement to which they agree. Except as otherwise agreed by the Parties, any and all Fiber Meet points established between the Parties shall extend no further than three (3) miles from an applicable Verizon Tandem or End Office and Verizon shall not be required to construct or deploy more than five hundred (500) feet of fiber cable for a Fiber Meet arrangement. 3.1.3 A Fiber Meet arrangement established under this Agreement may be used for the transmission and routing of only the following traffic types (over the Interconnection Trunks): 3.1.3.1 Reciprocal Compensation Traffic between the Parties’ respective Telephone Exchange Service Customers; 3.1.3.2 Translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic between the Parties’ respective Telephone Exchange Service Customers; 3.1.3.3 IntraLATA Toll Traffic between the Parties’ respective Telephone Exchange Service Customers;

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyMLTC, OnvoyMLTC, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third third-party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier access this Agreement or an applicable Verizon Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyMLTC, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy MLTC shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds Second (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy MLTC shall submit a good faith forecast to Frontier Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Onvoy MLTC anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy MLTC and FrontierVerizon. OnvoyMLTC’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds Second (Hundred Call SecondsSecond) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy MLTC shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-SR- TSV-002275). 2.4.9 The performance standard for final Meet Point B Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy MLTC shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy MLTC shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy MLTC shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem Meet Point B (final) Two-Way Interconnection Trunk group and Onvoy MLTC has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy MLTC a Trunk Group Service Request directing Onvoy MLTC to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy MLTC will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy MLTC will promptly augment all Tandem Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy MLTC will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy MLTC fails to submit an ASR for Two-Two- Way Interconnection Trunks in conformance with this Section, Frontier Verizon may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) ▇▇▇▇ MLTC for the excess Interconnection Trunks at the applicable Frontier Verizon rates. 2.4.13 Because Frontier Verizon will not be in control of when and how many Two-Two- Way Interconnection Trunks are established between its network and OnvoyMLTC’s network, FrontierVerizon’s performance in connection with these Two-Two- Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy MLTC will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-TAP-000191TAP- 000191, including but not limited to those standards requiring that a call from Onvoy MLTC to a Frontier Verizon End Office will first be routed to the End Office Meet Point A Interconnection Trunk group between Onvoy MLTC and the Frontier Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyCLC, OnvoyCLC, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyCLC, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy CLC shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy CLC shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy CLC anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy CLC and Frontier. OnvoyCLC’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy CLC shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Onvoy, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and Onvoy, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy and Frontier. Onvoy’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyPCS, OnvoyPCS shall order from Verizon, at its own expenseand Verizon shall provide, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Frontier Entrance Facility, on which such Trunks will ride, and Onvoytransport and multiplexing, Frontierin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontierterms and conditions set forth in this Agreement and Verizon’s network in a LATAapplicable Tariffs. 2.4.3 2.4.2 Prior to establishing ordering any Two-Way Interconnection TrunksTrunks from Verizon, Onvoy PCS shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Centium Call Seconds Second (Hundred Call SecondsSecond) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic(POI). Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Onvoy PCS shall submit a good faith forecast to Frontier Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy PCS anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Onvoy from PCS to Verizon and Frontierfrom Verizon to PCS. OnvoyPCS’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Centium Call Seconds Second (Hundred Call SecondsSecond) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy PCS shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyPacOptic, OnvoyPacOptic, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA (a) from a third party, or, (b) if Frontier Verizon offers such transport pursuant to a Frontier Verizon access Tariff, from FrontierVerizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier Verizon and OnvoyPacOptic, FrontierVerizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy PacOptic shall meet with Frontier Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on FrontierVerizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy PacOptic shall submit a good faith forecast to Frontier Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Onvoy PacOptic anticipates Frontier Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy PacOptic and FrontierVerizon. OnvoyPacOptic’s trunk forecasts shall conform to the Frontier Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Meet Point A (high usage) Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Frontier Verizon access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Frontier Verizon local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier Verizon and Onvoy PacOptic shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275TSV- 002275). 2.4.9 The performance standard for final Meet Point B Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy PacOptic shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy PacOptic shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within FrontierVerizon’s effective standard intervals or negotiated intervals, as appropriate. Onvoy PacOptic shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier Verizon observes blocking in excess of the applicable design objective on any Tandem Meet Point B (final) Two-Way Interconnection Trunk group and Onvoy PacOptic has not notified Frontier Verizon that it has corrected such blocking, Frontier Verizon may submit to Onvoy PacOptic a Trunk Group Service Request directing Onvoy PacOptic to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy PacOptic will complete an ASR to establish or augment the End Office Two-Meet Point A Two- Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier Verizon within five (5) Business Days. 2.4.12 The Parties will review all Tandem Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy PacOptic will promptly augment all Tandem Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy PacOptic will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy PacOptic fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier Verizon may disconnect the excess Interconnection Trunks or bill (and Onvoy PacOptic shall pay) for the excess Interconnection Trunks at the applicable Frontier Verizon rates. 2.4.13 Because Frontier Verizon will not be in control of when and how many Two-Two- Way Interconnection Trunks are established between its network and OnvoyPacOptic’s network, FrontierVerizon’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- carrier-to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy PacOptic will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier Verizon over the End Office and Tandem Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-SR- TAP-000191, including but not limited to those standards requiring that a call from Onvoy PacOptic to a Frontier Verizon End Office will first be routed to the End Office Meet Point A Interconnection Trunk group between Onvoy PacOptic and the Frontier Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyINA, OnvoyINA, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyINA, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy INA shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy INA shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy INA anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy INA and Frontier. OnvoyINA’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy INA shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyFutiva, OnvoyFutiva, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA (a) from a third party, or, (b) if Frontier offers such transport pursuant to a Frontier access Tariff, from Frontier. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier and OnvoyFutiva, Frontier, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy Futiva shall meet with Frontier to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy Futiva shall submit a good faith forecast to Frontier of the number of End Office and Tandem Two-Way Interconnection Trunks that Onvoy Futiva anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic between Onvoy Futiva and Frontier. OnvoyFutiva’s trunk forecasts shall conform to the Frontier CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, based on reasonable engineering criteria and capacity constraints, are not warranted by the actual traffic volume experienced. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- -▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier and Onvoy Futiva shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier PRTC and OnvoyCSPR, OnvoyCSPR, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierPRTC’s network in a LATAnetwork; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on FrontierPRTC’s network in a LATA (a) from a third third-party, or, (b) if Frontier PRTC offers such transport pursuant to a Frontier access this Agreement or an applicable PRTC Tariff, from FrontierPRTC. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Frontier PRTC and OnvoyCSPR, FrontierPRTC, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on FrontierPRTC’s network in a LATAnetwork. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Onvoy CSPR shall meet with Frontier PRTC to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centum Call Seconds (Hundred Call Seconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Frontier’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One-Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Onvoy shall submit a good faith forecast to Frontier of Where the number of End Office and Tandem Parties use Two-Way Interconnection Trunks that Onvoy anticipates Frontier will need to provide during the ensuing two (2) year period for the exchange of traffic, CSPR and PRTC shall negotiate a mutually agreed-to forecast of expected traffic between Onvoy and Frontieron an annual basis. Onvoy’s trunk forecasts shall conform If CSPR fails to utilize the Frontier CLEC trunk forecasting guidelines as in effect trunks at that timea level of at least sixty (60) percent of the forecasted level over a 12-month period, the parties will proceed under Section 11.2.2 of this Attachment. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. Where ESF/B8ZS is not available, CSPR agrees to use other interconnection protocols reasonably acceptable to PRTC. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centum Call Seconds (Hundred Call Seconds) equal to five (5). Either Party may disconnect End Office Two-Way Interconnection Trunks that, a service standard is based on reasonable engineering criteria average Time Consistent Busy Hour (TCBH), busy season originating attempts and capacity constraints, are not warranted by the actual traffic volume experiencedoverflows as defined in Telcordia document SR-TAP-000191 entitled Trunk Traffic Engineering Concepts and Applications. 2.4.8 Two-Way Interconnection Trunk groups that connect to a Frontier PRTC access Tandem shall be engineered using a design blocking objective of ▇▇▇▇- ▇▇▇▇▇▇▇▇▇ ▇.005 B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Frontier PRTC local Tandem shall be engineered using a design blocking objective of ▇▇▇▇-▇▇▇▇▇▇▇▇▇ B.01 during the average time consistent busy hour. Frontier PRTC and Onvoy CSPR shall engineer Two-Way Interconnection Trunks using Telcordia Notes on the Networks SR 2275 (formerly known as BOC Notes on the LEC Networks SR-TSV-002275). 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Onvoy shall determine and order the number of Two-Way Interconnection Trunks that are required to meet the applicable design blocking objective for all traffic carried on each Two-Way Interconnection Trunk group. Onvoy shall order Two-Way Interconnection Trunks by submitting ASRs to Frontier setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Frontier’s effective standard intervals or negotiated intervals, as appropriate. Onvoy shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Frontier may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Frontier observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Onvoy has not notified Frontier that it has corrected such blocking, Frontier may submit to Onvoy a Trunk Group Service Request directing Onvoy to remedy the blocking. Upon receipt of a Trunk Group Service Request, Onvoy will complete an ASR to establish or augment the End Office Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Tandem Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Frontier within five (5) Business Days. 2.4.12 The Parties will review all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of seventy percent (70%), or greater, to determine whether those groups should be augmented. Onvoy will promptly augment all Tandem Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%), unless the Parties agree that additional trunking is not required. For each Tandem Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Onvoy will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) for each respective group, unless the Parties agree that the Two-Way Interconnection Trunks should not be disconnected. In the event Onvoy fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Frontier may disconnect the excess Interconnection Trunks or bill (and Onvoy shall pay) for the excess Interconnection Trunks at the applicable Frontier rates. 2.4.13 Because Frontier will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Onvoy’s network, Frontier’s performance in connection with these Two-Way Interconnection Trunk groups shall not be subject to any performance measurements and remedies under this Agreement, and, except as otherwise required by Applicable Law, under any FCC or Commission approved carrier- to-carrier performance assurance guidelines or plan. 2.4.14 Onvoy will route its traffic, or traffic belonging to its Interconnected VoIP Provider Customers, to Frontier over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Onvoy to a Frontier End Office will first be routed to the End Office Interconnection Trunk group between Onvoy and the Frontier End Office.SR-002275