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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelPCS, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, PCS shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel PCS shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Meet Point A (high usage) and Meet Point B (final) Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel PCS shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel PCS anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from PCS to Verizon and Verizonfrom Verizon to PCS. NavtelPCS’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. TwoMeet Point BTwo-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel PCS shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-SR- TSV-002275. 2.4.9 The performance standard for Meet Point B 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 threethree (3) consecutive calendar traffic study months. 2.4.10 PCS 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. PCS shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. PCS shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and PCS has not notified Verizon that it has corrected such blocking, Verizon may submit to PCS a Trunk Group Service Request directing PCS to remedy the blocking. Upon receipt of a Trunk Group Service Request, PCS will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. PCS will promptly augment all 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 Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, PCS 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 PCS fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may xxxx PCS for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and PCS’s network, Verizon’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 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 PCS will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-TAP- 000191, including but not limited to those standards requiring that a call from PCS to a Verizon End Office will first be routed to the Meet Point AInterconnection Trunk group between PCS and the 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. PCS will pay a percentage of Verizon’s monthly recurring charges for each facility on which the Two-Way Interconnection Trunks ride equal to PCS’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 PCS’s side of PCS’s-IP, which charges shall be solely the financial responsibility of PCS. 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 PCS -IP, PCS shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on PCS’s side of the PCS-IP, PCS shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if PCS fails to provide PCS -IPs in accordance with this Agreement, PCS will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until PCS establishes such PCS-IPs.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelNeutral Tandem, NavtelNeutral Tandem, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable a Verizon access Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelNeutral Tandem, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Neutral Tandem shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Centum Call Second Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel Neutral Tandem shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel Neutral Tandem anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Neutral Tandem and Verizon. NavtelNeutral Tandem’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel 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 threethree (3) consecutive calendar traffic study months. 2.4.10 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. Neutral Tandem shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Neutral Tandem shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Neutral Tandem has not notified Verizon that it has corrected such blocking, Verizon may submit to Neutral Tandem a Trunk Group Service Request directing Neutral Tandem to remedy the blocking. Upon receipt of a Trunk Group Service Request, 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 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. 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-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, 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 Neutral Tandem fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, with ten (10) days prior written notice to Neutral Tandem, Verizon may disconnect the excess Interconnection Trunks or bill (and Neutral Tandem shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Neutral Tandem’s network, Verizon’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 Neutral Tandem will route its traffic to 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 Neutral Tandem to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Neutral Tandem and the Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelPN, NavtelPN, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable a Verizon access Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelPN, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel PN shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 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, Navtel PN shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel PN anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel PN and Verizon. NavtelPN’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel PN 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 threethree (3) consecutive calendar traffic study months. 2.4.10 PN 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. PN shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. PN shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and PN has not notified Verizon that it has corrected such blocking, Verizon may submit to PN a Trunk Group 2.4.12 The Parties will review all 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. PN will promptly augment all 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 Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, PN 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 PN fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and PN shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and PN’s network, Verizon’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 PN will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-TAP- 000191, including but not limited to those standards requiring that a call from PN to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between PN and the Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelHalo, NavtelHalo, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA LATA, at Halo’s option, either: (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon; provided that if Halo obtains such transport from a third-party, Halo shall provide a certification that it has done so to Verizon, in a form reasonably satisfactory to Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelHalo, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Halo shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each and upon the request of a Party, the requested Party shall provide to the other Party requesting Party, originating Centium Centum Call Second (Hundred Call Second) information. Additionally, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s '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-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, Navtel Halo shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel Halo anticipates that Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Halo and Verizon. NavtelHalo’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End End-Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Centum Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design design-blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem End Office shall be engineered using a design design-blocking objective of Xxxx-Xxxx Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Halo 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 each such Interconnection Trunk group will not exceed its design design- blocking objective (B.005 or B.01, as applicable) for three (3) consecutive calendar traffic study months. 2.4.10 Halo 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. Halo shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Halo shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Halo has not notified Verizon that it has corrected such blocking, Verizon may submit to Halo a Trunk Group Service Request directing Halo to remedy the blocking. Upon receipt of a Trunk Group Service Request, Halo 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 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, during any hour in any two (2) months of a three (3) consecutive month period, to determine whether those groups should be augmented. Halo 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 or Halo is otherwise able to take actions which reduce the utilization to the seventy percent (70%) threshold. As used in this Section 2.4.12, “utilization” of a Tandem Two-Way Interconnection Trunk group shall be based on the engineering parameters specified in Sections 2.4.7 thru 2.4.9 and Section 2.4.14. If the Tandem Two-Way Interconnection Trunks in service within a Tandem Two-Way Interconnection Trunk group reaches a utilization level of less than sixty percent (60%), during any hour in any two (2) months of a three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelTalk America, NavtelTalk America, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable a Verizon access Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelTalk America, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Talk America shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 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-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, Navtel Talk America shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel Talk America anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Talk America and Verizon. NavtelTalk America’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Talk America 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-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 threethree (3) consecutive calendar traffic study months. 2.4.10 Talk America 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. Talk America shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Talk America shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and Talk America has not notified Verizon that it has corrected such blocking, Verizon may submit to Talk America a Trunk Group Service Request directing Talk America to remedy the blocking. Upon receipt of a Trunk Group Service Request, Talk America will complete an ASR to establish or augment the Meet Point A Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. Talk America will promptly augment all 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 Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Talk America 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 Talk America fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and Talk America shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Talk America’s network, Verizon’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 Talk America will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-TAP-000191, including but not limited to those standards requiring that a call from Talk America to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between Talk America and the 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 Verizon and NavtelOneStar, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, OneStar shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel OneStar shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI.‌‌‌‌‌‌‌‌ 2.4.4 On a semi-annual basis, Navtel OneStar shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel OneStar anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from OneStar to Verizon and Verizonfrom Verizon to OneStar. NavtelOneStar’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel OneStar shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 OneStar 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. OneStar shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. OneStar shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and OneStar has not notified Verizon that it has corrected such blocking, Verizon may submit to OneStar a Trunk Group Service Request directing OneStar to remedy the blocking. Upon receipt of a 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. OneStar 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, OneStar 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 OneStar fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may xxxx OneStar for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and OneStar’s network, Verizon’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 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 OneStar will route its traffic to 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 OneStar to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between OneStar and the 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. OneStar will pay a percentage of Verizon’s monthly recurring charges for each facility on which the Two-Way 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 OneStar-IP, OneStar shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on OneStar’s side of the OneStar- IP, OneStar shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if OneStar fails to provide OneStar-IPs in accordance with this Agreement, OneStar will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until OneStar establishes such OneStar-IPs.

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelPacOptic, NavtelPacOptic, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable a Verizon access Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelPacOptic, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel PacOptic shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 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, Navtel PacOptic shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel PacOptic anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel PacOptic and Verizon. NavtelPacOptic’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel 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 threethree (3) consecutive calendar traffic study months. 2.4.10 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. PacOptic shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. PacOptic shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and PacOptic has not notified Verizon that it has corrected such blocking, Verizon may submit to PacOptic a Trunk Group Service Request directing PacOptic to remedy the blocking. Upon receipt of a Trunk Group Service Request, PacOptic will complete an ASR to establish or augment the Meet Point A Two- Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. PacOptic will promptly augment all 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 Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, 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 PacOptic fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and PacOptic shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and PacOptic’s network, Verizon’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 PacOptic will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR- TAP-000191, including but not limited to those standards requiring that a call from PacOptic to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between PacOptic and the Verizon End Office.

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Navtel365, Navtel365, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable a Verizon access Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Navtel365, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel 365 shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 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, Navtel 365 shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel 365 anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel 365 and Verizon. Navtel365’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel 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 threethree (3) consecutive calendar traffic study months. 2.4.10 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. 365 shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. 365 shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and 365 has not notified Verizon that it has corrected such blocking, Verizon may submit to 365 a Trunk Group Service Request directing 365 to remedy the blocking. Upon receipt of a Trunk Group Service Request, 365 will complete an ASR to establish or augment the Meet Point A Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. 365 will promptly augment all 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 Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, 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 365 fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and 365 shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and 365’s network, Verizon’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 365 will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-TAP- 000191, including but not limited to those standards requiring that a call from 365 to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between 365 and the Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelYmax, NavtelYmax, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelYmax, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Ymax shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel Ymax shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel Ymax anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Ymax and Verizon. NavtelYmax’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Xxxx shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 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. Ymax shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Ymax shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Ymax has not notified Verizon that it has corrected such blocking, Verizon may submit to Ymax a Trunk Group Service Request directing Ymax to remedy the blocking. Upon receipt of a Trunk Group Service Request, 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 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. 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-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, 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 Ymax fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or bill (and Ymax shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Ymax’s network, Verizon’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 Ymax will route its traffic to 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 Ymax to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Ymax and the 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 Verizon and NavtelWinco, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, Winco shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel Winco shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel Winco shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel Winco anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from Winco to Verizon and Verizonfrom Verizon to Winco. NavtelWinco’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Winco shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-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

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelGlobal Link, NavtelGlobal Link, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelGlobal Link, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Global Link shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel Global Link shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel Global Link anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Global Link and Verizon. NavtelGlobal Link’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Global Link shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 Global Link 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. Global Link shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Global Link shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Global Link has not notified Verizon that it has corrected such blocking, Verizon may submit to Global Link a Trunk Group Service Request directing Global Link to remedy the blocking. Upon receipt of a Trunk Group Service Request, Global Link 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 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. Global Link 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, Global Link 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 Global Link fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and Global Link shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Global Link’s network, Verizon’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 Global Link will route its traffic to 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 Global Link to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Global Link and the Verizon End Office.

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

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelRACC, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, RACC shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel RACC shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel RACC shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel RACC anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from RACC to Verizon and Verizonfrom Verizon to RACC. NavtelRACC’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel RACC shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 RACC 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. RACC shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. RACC shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and RACC has not notified Verizon that it has corrected such blocking, Verizon may submit to RACC a Trunk Group Service Request directing RACC to remedy the blocking. Upon receipt of a Trunk Group Service Request, RACC will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to 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. RACC 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, RACC 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 RACC fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may xxxx RACC for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and RACC’s network, Verizon’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 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 RACC will route its traffic to 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 RACC to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between RACC and the 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. RACC will pay a percentage of Verizon’s monthly recurring charges for each facility on which the Two-Way Interconnection Trunks ride equal to RACC’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 RACC’s side of RACC’s-IP, which charges shall be solely the financial responsibility‌ of RACC. 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 RACC-IP, RACC shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on RACC’s side of the RACC-IP, RACC shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if RACC fails to provide RACC-IPs in accordance with this Agreement, RACC will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until RACC establishes such RACC-IPs.

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelFirst Comm, NavtelFirst Comm, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable a Verizon access Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelFirst Comm, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel First Comm shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 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, Navtel First Comm shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel First Comm anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel First Comm and Verizon. NavtelFirst Comm’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel First Comm 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-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 threethree (3) consecutive calendar traffic study months. 2.4.10 First Comm 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. First Comm shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. First Comm shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable 2.4.12 The Parties will review all 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. First Comm will promptly augment all 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 Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, First Comm 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 First Comm fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and First Comm shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and First Comm’s network, Verizon’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 First Comm will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR- TAP-000191, including but not limited to those standards requiring that a call from First Comm to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between First Comm and the Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCBAD, NavtelCBAD, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable a Verizon access Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCBAD, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel CBAD shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 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, Navtel CBAD shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel CBAD anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel CBAD and Verizon. NavtelCBAD’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel CBAD 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 threethree (3) consecutive calendar traffic study months. 2.4.10 CBAD 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. CBAD shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. CBAD shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and CBAD has not notified Verizon that it has corrected such blocking, Verizon may submit to CBAD a Trunk Group Service Request directing CBAD to remedy the blocking. Upon receipt of a Trunk Group Service Request, CBAD will complete an ASR to establish or augment the Meet Point A Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. CBAD will promptly augment all 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 Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, CBAD 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 CBAD fails to submit an ASR for Two- Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and CBAD shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and CBAD’s network, Verizon’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 CBAD will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-TAP- 000191, including but not limited to those standards requiring that a call from CBAD to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between CBAD and the Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelYmax, NavtelYmax, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelYmax, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Ymax shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel Ymax shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel Ymax anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Ymax and Verizon. NavtelYmax’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Ymax shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 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. Ymax shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Ymax shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Ymax has not notified Verizon that it has corrected such blocking, Verizon may submit to Ymax a Trunk Group Service Request directing Ymax to remedy the blocking. Upon receipt of a Trunk Group Service Request, 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 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. 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-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, 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 Ymax fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and Ymax shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Ymax’s network, Verizon’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 Ymax will route its traffic to 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 Ymax to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Ymax and the Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelYgnition, NavtelYgnition, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable a Verizon access Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelYgnition, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Ygnition shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Centum Call Second Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel Ygnition shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel Ygnition anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Ygnition and Verizon. NavtelYgnition’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 X.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 during the average time consistent busy hour. Verizon and Navtel Ygnition 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 threethree (3) consecutive calendar traffic study months. 2.4.10 Ygnition 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. Ygnition shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Ygnition shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Ygnition has not notified Verizon that it has corrected such blocking, Verizon may submit to Ygnition a Trunk Group Service Request directing Ygnition to remedy the blocking. Upon receipt of a Trunk Group Service Request, Ygnition 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 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. Ygnition 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, Ygnition 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 Ygnition fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or bill (and Ygnition shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Ygnition’s network, Verizon’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 Ygnition will route its traffic to 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 Ygnition to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Ygnition and the 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 Verizon and NavtelIntrado, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, Intrado shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel Intrado shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel Intrado shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel Intrado anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from Intrado to Verizon and Verizonfrom Verizon to Intrado. NavtelIntrado’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Intrado shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 Intrado 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. Intrado shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Intrado shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Intrado has not notified Verizon that it has corrected such blocking, Verizon may submit to Intrado a Trunk Group Service Request directing Intrado to remedy the blocking. Upon receipt of a Trunk Group Service Request, Intrado will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to 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. Intrado 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, Intrado 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 Intrado fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may xxxx Xxxxxxx for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Intrado’s network, Verizon’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 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 Intrado will route its traffic to 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 Intrado to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Intrado and the 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. Intrado will pay a percentage of Verizon’s monthly recurring charges for each facility on which the Two-Way Interconnection Trunks ride equal to Intrado’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 Intrado’s side of Intrado’s-IP, which charges shall be solely the financial responsibility of Intrado. 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 Intrado-IP, Intrado shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on Intrado’s side of the Intrado-IP, Intrado shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if Intrado fails to provide Intrado-IPs in accordance with this Agreement, Intrado will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until Intrado establishes such Intrado- IPs.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCBB, NavtelCBB, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCBB, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel CBB shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second Seconds (Hundred Call SecondSeconds) 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 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, Navtel CBB shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel CBB anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel CBB and Verizon. NavtelCBB’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel 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-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 threethree (3) consecutive calendar traffic study months. 2.4.10 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. CBB shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. CBB shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable 2.4.12 The Parties will review all 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. CBB will promptly augment all 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 Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, 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 CBB fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and CBB shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and CBB’s network, Verizon’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 CBB will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-TAP- 000191, including but not limited to those standards requiring that a call from CBB to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between CBB and the 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 CBB 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 CBB 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 use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelMLTC, NavtelMLTC, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelMLTC, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel MLTC shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office 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 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, Navtel MLTC shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel MLTC anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel MLTC and Verizon. NavtelMLTC’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel MLTC shall engineer Two-Way Interconnection Trunks using 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 threethree (3) consecutive calendar traffic study months. 2.4.10 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. MLTC shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. MLTC shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and MLTC has not notified Verizon that it has corrected such blocking, Verizon may submit to MLTC a Trunk Group Service Request directing MLTC to remedy the blocking. Upon receipt of a Trunk Group Service Request, 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 Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. MLTC will promptly augment all 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 Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, 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 MLTC fails to submit an ASR for Two- Way Interconnection Trunks in conformance with this Section, Verizon may xxxx MLTC for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and MLTC’s network, Verizon’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 MLTC will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-TAP- 000191, including but not limited to those standards requiring that a call from MLTC to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between MLTC and the Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCovista, NavtelCovista, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCovista, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Covista shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel Covista shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel Covista anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Covista and Verizon. NavtelCovista’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Covista shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 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. Covista shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Covista shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Covista has not notified Verizon that it has corrected such blocking, Verizon may submit to Covista a Trunk Group Service Request directing Covista to remedy the blocking. Upon receipt of a Trunk Group Service Request, 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 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. 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-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, 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 Covista fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and Covista shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Covista’s network, Verizon’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 Covista will route its traffic to 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 Covista to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Covista and the 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 Verizon and NavtelICG, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, ICG shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Navtel, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel and the Entrance Facility on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs. 2.4.2 Upon the parties undertaking a Major Project, where the Parties have agreed to use Two Way Interconnection Trunks, prior to ordering any Two-Way Interconnection Trunks from Verizon, ICG shall meet meet, telephonically or in person, with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party forecasted originating Centium Call Second CCS (Hundred Call Second) 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 Verizon’s (POI). For purposes of this Section 2.4.2, a “Major Project” is a project that requires the coordination and execution of multiple orders or related activities between and among Verizon and ICG work groups including, but not limited to, the initial establishment of Interconnection or Access Toll Connecting Trunk groups between a Verizon switch and an ICG switch, NXX code moves, re-homes, facility grooming, network in rearrangements, a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-conversion from 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 installation of such One- Way Interconnection Trunks to a new switch. 2.4.3 Two-Way Interconnection TrunksTrunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where ICG is collocated in a Verizon Wire Center, the POI may be at the Verizon Wire Center. 2.4.4 On a semi-annual basis, Navtel ICG shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel ICG anticipates that Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel and Verizonperiod. NavtelICG’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as provided to ICG and in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) CCS equal to five (5). 2.4.8 Verizon and ICG shall engineer Two-Way Interconnection Trunks using national standards and measurement methodologies. Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hourB.005. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 during the B.01. In performing trunk blockage measurements, Verizon will use an average time consistent busy hourhour methodology, as set out in Telcordia publication SR-TAP-000191. If ICG elects to perform trunk blockage measurements using a method of measurement (for instance, a method that uses a peak busy hour measurement) that differs from that used by Verizon and Navtel shall engineer ICG’s method of measurement indicates a need for a different number of Two-Way Interconnection Trunks using BOC Notes on than the LEC Networks SRmethod of measurement used by Verizon, the Parties shall negotiate in good faith to determine the number of Two-TSV-002275Way Interconnection Trunks that should be used. If the Parties are unable to agree upon the number of Two-Way Interconnection Trunks that should be used, either Party may submit the matter to dispute resolution pursuant to Section 14 of the General Terms and Conditions. 2.4.9 After a Two-Way Interconnection Trunk group has been established, ICG 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 such Two-Way Interconnection Trunk group. ICG shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. The performance standard provisioning intervals offered by Verizon to ICG for orders for 240 or fewer DS0 Two-Way Interconnection Trunks shall be no longer than the provisioning intervals offered by Verizon to other similarly situated CLECs for orders for 240 or fewer DS0 Two-Way Interconnection Trunks. Except as otherwise provided in an applicable Verizon Tariff, the provisioning intervals offered by Verizon to ICG for orders for 240 or more DS0 Two-Way Interconnection Trunks shall be subject to negotiation by the Parties. ICG orders for Two-Way Interconnection Trunks shall be subject to Section 2.2.5 above and other applicable provisions of this Agreement and applicable Verizon Tariffs. ICG shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time. 2.4.10 Each Party may monitor Two-Way Interconnection Trunk Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Interconnection Trunk group and ICG has not notified Verizon that it has corrected such blocking, Verizon may submit to ICG a Trunk Group Service Request directing ICG to remedy the blocking. Upon receipt of a Trunk Group Service Request, ICG will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. If ICG observes blocking in excess of the applicable design objective on any final Two-Way Interconnection Trunk group, ICG shall submit an ASR to augment the Two-Way Interconnection Trunk Group. 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. ICG 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, ICG 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. In the event ICG fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may xxxx ICG for the excess Interconnection Trunks at the applicable rates provided for in the Pricing Attachment, provided that Verizon sends ICG written notice, in the form of a Trunk Group Service Request, sixty (60) days prior to sending a xxxx and such notice identifies the underutilized trunk groups. 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 threethree (3) consecutive calendar traffic study months. 2.4.13 Because Verizon will not be in control of the timing and sizing of the Two-Way Interconnection Trunks between its network and ICG’s network, Verizon’s performance on these Two-Way Interconnection Trunk groups (except for maintenance intervals and missed installation appointments) 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 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 Each Party will route its traffic to the other Party over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR- TAP192, including but not limited to those standards requiring that a call from either Party to the other Party's End Office will first be routed to the End Office Interconnection Trunk group between ICG and the 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 or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Interconnection Trunks. ICG will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Interconnection Trunks ride equal to ICG’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 ICG’s side of ICG’s-IP, which charges shall be solely the financial responsibility of ICG. 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 ICG-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on ICG’s side of the ICG-IP, ICG shall be solely responsible for the non- recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if ICG fails to provide IPs in accordance with this Agreement, ICG will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until ICG establishes such IPs.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelHello Depot, NavtelHello Depot, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelHello Depot, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Hello Depot shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office 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 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, Navtel Hello Depot shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel Hello Depot anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Hello Depot and Verizon. NavtelHello Depot’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Hello Depot shall engineer Two-Two- Way Interconnection Trunks using 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 threethree (3) consecutive calendar traffic study months. 2.4.10 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. Hello Depot shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Hello Depot shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and Hello Depot has not notified Verizon that it has corrected such blocking, Verizon may submit to Hello Depot a Trunk Group Service Request directing Hello Depot to remedy the blocking. Upon receipt of a Trunk Group Service Request, 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 Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. Hello Depot will promptly augment all 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 Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, 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 Hello Depot fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may xxxx Hello Depot for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Hello Depot’s network, Verizon’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 Hello Depot will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR- TAP-000191, including but not limited to those standards requiring that a call from Hello Depot to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between Hello Depot and the Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelTNCI, NavtelTNCI, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelTNCI, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel TNCI shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel TNCI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel TNCI anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel TNCI and Verizon. NavtelTNCI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel TNCI shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 TNCI 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. TNCI shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. TNCI shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and TNCI has not notified Verizon that it has corrected such blocking, Verizon may submit to TNCI a Trunk Group Service Request directing TNCI to remedy the blocking. Upon receipt of a Trunk Group Service Request, TNCI 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 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. TNCI 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, TNCI 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 TNCI fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may bill TNCI for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and TNCI’s network, Verizon’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 TNCI will route its traffic to 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 TNCI to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between TNCI and the 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 Verizon and NavtelVarTec, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, VarTec shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel VarTec shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel VarTec shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel VarTec anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from VarTec to Verizon and Verizonfrom Verizon to VarTec. NavtelVarTec’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel VarTec shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 VarTec 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. VarTec shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. VarTec shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and VarTec has not notified Verizon that it has corrected such blocking, Verizon may submit to VarTec a Trunk Group Service Request directing VarTec to remedy the blocking. Upon receipt of a Trunk Group Service Request, VarTec will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to 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. VarTec 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, VarTec 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 VarTec fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may bill VarTec for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and VarTec’s network, Verizon’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 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 VarTec will route its traffic to 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 VarTec to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between VarTec and the 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. VarTec will pay a percentage of Xxxxxxx’s monthly recurring charges for each facility on which the Two-Way Interconnection Trunks ride equal to VarTec’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 VarTec’s side of VarTec’s-IP, which charges shall be solely the financial responsibility of VarTec. 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 VarTec-IP, VarTec shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on VarTec’s side of the VarTec-IP, VarTec shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if VarTec fails to provide VarTec-IPs in accordance with this Agreement, VarTec will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until VarTec establishes such VarTec- IPs.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelMMG, NavtelMMG, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelMMG, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel MMG shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second Seconds (Hundred Call SecondSeconds) 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 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, Navtel MMG shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel MMG anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel MMG and Verizon. NavtelMMG’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel MMG 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 threethree (3) consecutive calendar traffic study months. 2.4.10 MMG 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. MMG shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. MMG shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable 2.4.12 The Parties will review all 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. MMG will promptly augment all 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 Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, MMG 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 MMG fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and MMG shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and MMG’s network, Verizon’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 MMG will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-TAP- 000191, including but not limited to those standards requiring that a call from MMG to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between MMG and the 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 MMG 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 MMG 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 use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelNL, NavtelNL, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelNL, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel NL shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel NL shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel NL anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel NL and Verizon. NavtelNL’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel NL shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 NL 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. NL shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. NL shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and NL has not notified Verizon that it has corrected such blocking, Verizon may submit to NL a Trunk Group Service Request directing NL to remedy the blocking. Upon receipt of a Trunk Group Service Request, NL 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 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. NL 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, NL 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 NL fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may xxxx NL for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and NL’s network, Verizon’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 NL will route its traffic to 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 NL to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between NL and the Verizon End Office.

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelPac-West, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a thirdPac-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, West shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon's applicable Tariffs. Upon the Parties undertaking a Major Project, at its own expensewhere the Parties have agreed to use Two Way Interconnection Trunks, shall provide its own facilities prior to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing ordering any Two-Way Interconnection TrunksTrunks from Verizon, Navtel Pac-West shall meet with Verizon to conduct a joint planning meeting (“"Joint Planning Meeting”"). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) POI. For purposes of this Section 2.4.2, a "Major Project" is a project that requires the coordination and execution of multiple orders or related activities between and among Verizon and Pac-West work groups including, but not limited to, the initial establishment of Interconnection on Verizon’s or Access Toll Connecting Trunk Groups between a Verizon switch and a Pac-West switch, NXX code moves, rehomes, facility grooming, network in rearrangements, a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-conversion from 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 installation of such One- Way Interconnection Trunks to a new switch. Two-Way Interconnection Trunks. 2.4.4 Trunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. On a semi-annual basis, Navtel Pac-West shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel Pac-West anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel and Verizonperiod. Navtel’s Pac-West's trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 . The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 . Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 . With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 . Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of XxxxNxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of XxxxNxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Pac-West shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 . The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. After a Two-Way Interconnection Trunk Group has been established, Pac-West 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. Pac-West shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon's effective standard intervals or negotiated intervals, as appropriate. Provisioning intervals offered by Verizon to Pac-West for Two-Way Interconnection Trunks shall be no longer than the provisioning intervals offered by Verizon to other CLECs. Pac-West shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. Each Party may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Pac-West has not notified Verizon that it has corrected such blocking, Verizon may submit to Pac-West a Trunk Group Service Request directing Pac-West to remedy the blocking. Upon receipt of a Trunk Group Service Request, Pac-West will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. If Pac-West observes blocking in excess of the applicable design objective on any final Two-Way Interconnection Trunk group, Pac-West shall submit an ASR to augment the Two-Way Interconnection Trunk Group. 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. Pac-West 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, Pac-West 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 Pac-West fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may bxxx Pac-West for the excess Interconnection Trunks at the applicable rates provided for in the Pricing Attachment, provided that Verizon sends Pac-West written notice, in the form of a Trunk Group Service Request, sixty (60) days prior to sending a bxxx and such notice identifies the underutilized trunks. Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Pac-West's network, Verizon's performance in connection with these Two-Way Interconnection Trunk groups (except for maintenance intervals and missed installation appointments) 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. 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 relevant POI. Each Party will route its traffic to the other Party 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 Pac-West to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Pac-West and the Verizon End Office. When the Parties implement Two-Way Interconnection Trunks, each Party will be responsible for the costs on its side of the POI.

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelMMG, NavtelMMG, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable a Verizon access Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelMMG, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel MMG shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Centum Call Second Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel MMG shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel MMG anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel MMG and Verizon. NavtelMMG’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel MMG 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 threethree (3) consecutive calendar traffic study months. 2.4.10 MMG 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. MMG shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. MMG shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and MMG has not notified Verizon that it has corrected such blocking, Verizon may submit to MMG a Trunk Group Service Request directing MMG to remedy the blocking. Upon receipt of a Trunk Group Service Request, MMG 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 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. MMG 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, MMG 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 MMG fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and MMG shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and MMG’s network, Verizon’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 MMG will route its traffic to 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 MMG to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between MMG and the Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCrocker, NavtelCrocker, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelXxxxxxx, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Xxxxxxx shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office 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 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, Navtel Xxxxxxx shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel Xxxxxxx anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Xxxxxxx and Verizon. Navtel’s Xxxxxxx’x trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Xxxxxxx shall engineer Two-Way Interconnection Trunks using 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 threethree (3) consecutive calendar traffic study months. 2.4.10 Xxxxxxx 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. Xxxxxxx shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Xxxxxxx shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and Xxxxxxx has not notified Verizon that it has corrected such blocking, Verizon may submit to Xxxxxxx a Trunk Group Service Request directing Xxxxxxx to remedy the blocking. Upon receipt of a Trunk Group Service Request, Xxxxxxx 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 Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. Xxxxxxx will promptly augment all 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 Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Xxxxxxx 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 Xxxxxxx fails to submit an ASR for Two- Way Interconnection Trunks in conformance with this Section, Verizon may xxxx Xxxxxxx for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Xxxxxxx’x network, Verizon’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 Xxxxxxx will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR- TAP-000191, including but not limited to those standards requiring that a call from Xxxxxxx to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between Xxxxxxx and the Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelMLTC, NavtelMLTC, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelMLTC, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel MLTC shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel MLTC shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel MLTC anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel MLTC and Verizon. NavtelMLTC’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel MLTC shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 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. MLTC shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. MLTC shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and MLTC has not notified Verizon that it has corrected such blocking, Verizon may submit to MLTC a Trunk Group Service Request directing MLTC to remedy the blocking. Upon receipt of a Trunk Group Service Request, 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 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. MLTC 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, 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 MLTC fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may bill MLTC for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and MLTC’s network, Verizon’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 MLTC will route its traffic to 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 MLTC to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between MLTC and the Verizon End Office.

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

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

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelVNCI, NavtelVNCI, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelVNCI, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel VNCI shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel VNCI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel VNCI anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel VNCI and Verizon. NavtelVNCI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel VNCI 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 threethree (3) consecutive calendar traffic study months. 2.4.10 VNCI 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. VNCI shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. VNCI shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and VNCI has not notified Verizon that it has corrected such blocking, Verizon may submit to VNCI a Trunk Group Service Request directing VNCI to remedy the blocking. Upon receipt of a Trunk Group Service Request, VNCI 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 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. VNCI 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, VNCI 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 VNCI fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and VNCI shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and VNCI’s network, Verizon’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 VNCI will route its traffic to 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 VNCI to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between VNCI and the Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCCA, NavtelCCA, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCCA, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel CCA shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel CCA shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel CCA anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel CCA and Verizon. NavtelCCA’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel CCA shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 CCA 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. CCA shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. CCA shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and CCA has not notified Verizon that it has corrected such blocking, Verizon may submit to CCA a Trunk Group Service Request directing CCA to remedy the blocking. Upon receipt of a Trunk Group Service Request, CCA 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 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. CCA 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, CCA 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 CCA fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may bill CCA for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and CCA’s network, Verizon’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 CCA will route its traffic to 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 CCA to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between CCA and the Verizon End Office.

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

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

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelAPI, NavtelAPI, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelAPI, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel API shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel API shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel API anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel API and Verizon. NavtelAPI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel API shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 API 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. API shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. API shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and API has not notified Verizon that it has corrected such blocking, Verizon may submit to API a Trunk Group Service Request directing API to remedy the blocking. Upon receipt of a Trunk Group Service Request, API 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 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. API 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, API 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 API fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may bill API for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and API’s network, Verizon’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 API will route its traffic to 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 API to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between API and the 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 Verizon and NavtelNTE, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, NTE shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel NTE shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel NTE shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel NTE anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from NTE to Verizon and Verizonfrom Verizon to NTE. NavtelNTE’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel NTE shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 NTE 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. NTE shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. NTE shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and NTE has not notified Verizon that it has corrected such blocking, Verizon may submit to NTE a Trunk Group Service Request directing NTE to remedy the blocking. Upon receipt of a Trunk Group Service Request, NTE will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to 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. NTE 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, NTE 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 NTE fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may xxxx NTE for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and NTE’s network, Verizon’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 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 NTE will route its traffic to 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 NTE to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between NTE and the 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. NTE will pay a percentage of Verizon’s monthly recurring charges for each facility on which the Two-Way Interconnection Trunks ride equal to NTE’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 NTE’s side of NTE’s-IP, which charges shall be solely the financial responsibility of NTE. 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 NTE-IP, NTE shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on NTE’s side of the NTE-IP, NTE shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if NTE fails to provide NTE-IPs in accordance with this Agreement, NTE will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until NTE establishes such NTE-IPs.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelOTT, NavtelOTT, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable a Verizon access Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelXXX, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel XXX shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 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, Navtel XXX shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel XXX anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel XXX and Verizon. Navtel’s XXX’x trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel XXX 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 threethree (3) consecutive calendar traffic study months. 2.4.10 XXX 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. XXX shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. XXX shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and XXX has not notified Verizon that it has corrected such blocking, Verizon may submit to XXX a Trunk Group Service Request directing XXX to remedy the blocking. Upon receipt of a Trunk Group Service Request, XXX will complete an ASR to establish or augment the Meet Point A Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. XXX will promptly augment all 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 Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, XXX 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 XXX fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and XXX shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and XXX’x network, Verizon’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 XXX will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-TAP- 000191, including but not limited to those standards requiring that a call from XXX to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between XXX and the Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelATI, NavtelATI, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelATI, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel ATI shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel ATI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel ATI anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel ATI and Verizon. NavtelATI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel ATI shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 ATI 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. ATI shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. ATI shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and ATI has not notified Verizon that it has corrected such blocking, Verizon may submit to ATI a Trunk Group Service Request directing ATI to remedy the blocking. Upon receipt of a Trunk Group Service Request, ATI 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 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. ATI 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, ATI 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 ATI fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may bill ATI for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and ATI’s network, Verizon’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 ATI will route its traffic to 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 ATI to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between ATI and the 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 Verizon and NavtelTalk Unlimited, NavtelTalk Unlimited 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 which 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 Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from VerizonTariffs. 2.4.2 Where the Parties use Prior to ordering any Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Navtel, from Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Talk Unlimited shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel Talk Unlimited shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel Talk Unlimited anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from Talk Unlimited to Verizon and Verizonfrom Verizon to Talk Unlimited. NavtelTalk Unlimited’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Talk Unlimited shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 Talk Unlimited 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. Talk Unlimited shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Talk Unlimited shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Talk Unlimited has not notified Verizon that it has corrected such blocking, Verizon may submit to Talk Unlimited a Trunk Group Service Request directing Talk Unlimited to remedy the blocking. Upon receipt of a Trunk Group Service Request, Talk Unlimited will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to 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. Talk Unlimited 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, Talk Unlimited 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 Talk Unlimited fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may bill Talk Unlimited for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Talk Unlimited’s network, Verizon’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 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 Talk Unlimited will route its traffic to 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 Talk Unlimited to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Talk Unlimited and the 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. Talk Unlimited will pay a percentage of Verizon’s monthly recurring charges for each facility on which the Two-Way Interconnection Trunks ride equal to Talk Unlimited’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 Talk Unlimited’s side of Talk Unlimited’s-IP, which charges shall be solely the financial responsibility of Talk Unlimited. 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 Talk Unlimited-IP, Talk Unlimited shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on Talk Unlimited’s side of the Talk Unlimited-IP, Talk Unlimited shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if Talk Unlimited fails to provide Talk Unlimited-IPs in accordance with this Agreement, Talk Unlimited will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until Talk Unlimited establishes such Talk Unlimited-IPs.

Two-Way Interconnection Trunks. 2.4.1 Where Notwithstanding anything set forth in the Interconnection Agreement, the Parties use shall configure separate One-Way Interconnection Trunks for the delivery of traffic from PaeTec to VERIZON, and for the delivery of traffic from VERIZON to PaeTec, respectively; provided, however, that in lieu thereof, upon receipt of PaeTec’s written request, VERIZON shall provide Two-Way Interconnection Trunks for the exchange of traffic between Verizon the networks of VERIZON and NavtelPaeTec pursuant, Navteland subject, at its own expenseto the rates, shallterms and conditions specified in the NYPSC No. 914, as amended from time to time, and the additional terms and conditions set forth below: 2.4.1.1 provide its own facilities (1) Prior to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use requesting any Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Navtelfrom VERIZON, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel PaeTec shall meet with Verizon VERIZON to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) CCS information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Meet Point A (high usage) and Meet Point B (final)Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 At the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- requests to convert existing Meet Point A and Meet Point B One-Way Interconnection Trunks to Meet Point A and Meet Point B Two-Way Interconnection Trunks. 2.4.4 (2) Two-Way Interconnection Trunks shall be from a VERIZON End Office or Tandem to a mutually agreed upon POI. (3) On a semi-annual basis, Navtel PaeTec shall submit a good faith forecast to Verizon VERIZON of the number of End Office Meet Point A and Tandem Meet Point B Two-Way Interconnection Trunks that Navtel PaeTec anticipates Verizon that the Parties will need to provide require from VERIZON during the ensuing two (2) year period for the exchange of traffic between Navtel and Verizonperiod. NavtelPaeTec’s trunk forecasts shall conform to the Verizon VERIZON CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 (4) The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office Meet Point A and Tandem Meet Point B 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 (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 (6) With respect to End Office Meet Point A Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) CCS equal to five (5). 2.4.8 (7) Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon VERIZON access Tandem shall be engineered using a design blocking objective of Xxxx-Nxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. ; Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon VERIZON local Tandem shall be engineered using a design blocking objective of Xxxx-Nxxx Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon VERIZON and Navtel PaeTec shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275national standards. 2.4.9 The performance (8) PaeTec 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. PaeTec shall order Two-Way Interconnection Trunks by submitting ASRs to VERIZON setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within VERIZON’S effective standard intervals or negotiated intervals, as appropriate. PaeTec shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time. VERIZON may monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If VERIZON observes blocking in excess of the applicable design objective on any final Two-Way Interconnection Trunk group and PaeTec has not notified VERIZON that it has corrected such blocking, VERIZON may submit to PaeTec a Trunk Group Service Request directing PaeTec to remedy the blocking. Upon receipt of a Trunk Group Service Request, PaeTec will complete an ASR to augment the Two-Way Interconnection Group with excessive blocking and submit the ASR to VERIZON within five (5) business days. (9) In the event the traffic volume between a VERIZON End Office and the PaeTec POI, which is carried by a Meet Point B Interconnection Trunk group, exceeds the CCS busy hour equivalent of one (1) DS-1 at any time or 200,000 combined minutes of use for a single month, PaeTec shall promptly submit an ASR to VERIZON to establish a new Meet Point A Two-Way Interconnection Trunks between that VERIZON End Office and the PaeTec POI. (10) [INTENTIONALLY LEFT BLANK] (11) The Parties will review all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of seventy (70%) percent of the engineered capacity or greater to determine whether those groups should be augmented. PaeTec will promptly augment all Meet Point B Two-Way Interconnection Trunk groups that reach a utilization level of eighty percent (80%) of the engineered capacity by submitting ASRs for additional trunks sufficient to attain a utilization level of approximately seventy percent (70%) of the engineered capacity, unless the Parties agree that additional trunking is not required. For each Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%) of the engineered capacity, PaeTec will promptly submit ASRs to disconnect a sufficient number of Interconnection Trunks to attain a utilization level of approximately sixty percent (60%) of the engineered capacity for each respective group, unless the Parties agree that the Interconnection Trunks should not be disconnected. In the event PaeTec fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, VERIZON may bxxx PaeTec for the excess Interconnection Trunks at the applicable rates set forth in Exhibit A. (12) The performance standard on Meet Point B 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 threethree (3) consecutive calendar traffic study months. (13) Because VERIZON will not be in control of the timing and sizing of the Two-Way Interconnection Trunks between its network and PaeTec’s network, VERIZON’S performance on these Two-Way Interconnection Trunk groups shall be excluded from any performance measurements and remedies, except for unexcused missed installation appointments. (14) 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 POI. (15) Both Parties shall use either a DS-1 or DS-3 interface at the POI for Two-Way Interconnection Trunks. Upon mutual agreement, the Parties may use other types of interfaces, such as STS-1 or OC-n, at the POI, when and where available. When Two-Way Interconnection Trunks are provisioned using a DS-3 interface facility, PaeTec shall order the multiplexed DS-3 facilities to the VERIZON Central Office that is designated in the NECA 4 Tariff as an Intermediate Hub location, unless otherwise agreed to in writing by VERIZON. The specific NECA 4 Intermediate Hub location to be used for Two-Way Interconnection Trunks shall be in the appropriate Tandem subtending area based on the LERG. In the event the appropriate DS 3 Intermediate Hub is not used in the ordering process, then PaeTec shall pay 100% of the facility charges (16) Notwithstanding any other provision of the Interconnection Agreement or this Amendment, Two-Way Interconnection Trunks shall only carry Local Traffic, IntraLATA Toll Traffic and Internet Traffic. (17) If PaeTec materially breaches a material term of this Section l(a), and has not remedied such breach within thirty (30) days of written notice thereof, VERIZON may cease provisioning Two-Way Interconnection Trunks under this Amendment. (18) Except as set forth in the next sentence or otherwise agreed in writing by the Parties, the total number of Meet Point B Two-Way Interconnection Trunks between PaeTec’s network and a VERIZON Tandem will be limited to a maximum of 240 trunks. The total number of Meet Point B Two-Way Interconnection Trunks between PaeTec’s’s network and a VERIZON Tandem described in Attachment A of this Amendment shall be limited to a maximum of 672 trunks, unless otherwise mutually agreed to in writing by the parties. In the event that the volume of traffic between PaeTec’s network and a VERIZON Tandem exceeds, or reasonably can be anticipated to exceed, the capacity of the maximum permitted number of Meet Point B Two-Way Interconnection Trunks, PaeTec shall promptly submit an ASR to VERIZON to establish new or additional Meet Point A Trunks to insure that the volume of traffic between PaeTec’s network and the VERIZON Tandem does not exceed the capacity of the maximum permitted number of Meet Point B Two-Way Interconnection Trunks. (19) PaeTec will route its traffic to VERIZON over the Meet Point A and Meet Point B Two-Way Interconnection Trunks in accordance with SR-TAP192, including but not limited to those industry standards requiring that a call from PaeTec to a VERIZON End Office will first be routed to the Meet Point A Interconnection Trunk group between PaeTec and the VERIZON End Office. (20) When the Parties implement Two-Way Interconnection Trunks, the Parties will work cooperatively to calculate a Proportionate Percentage of Use or “PPU” factor, where the numerator is the total number of minutes of traffic carried from PaeTec to VERIZON on all Two-Way Interconnection Trunks and the denominator is the total number of minutes of traffic carried over such Two-Way Interconnection Trunks. PaeTec will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Interconnection Trunks ride equal to PaeTec’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 the facility that is on PaeTec’s side of the PaeTec’s-IP, which charges shall be solely the financial responsibility of the PaeTec. 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 PaeTec-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on PaeTec’s side of the PaeTec-IP, PaeTec shall be solely responsible for the nonrecurring charges. Notwithstanding the foregoing provisions of this Section 20, if PaeTec fails to provide geographic IPs in accordance with the Interconnection Agreement, PaeTec will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until PaeTec establishes such IPs. During the first calendar quarter (and any partial quarter) after Two-Way Interconnection Trunks are initially established, PPU will be fifty percent (50%). In each quarter thereafter, the Parties may recalculate the PPU using actual traffic usage for the preceding three month period. When One-Way Interconnection Trunks are converted to Two-Way Interconnection Trunks, PaeTec will pay fifty percent (50%) of the non-recurring charges.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelSnappy Phone, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, Snappy Phone shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel Snappy Phone shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel Snappy Phone shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel Snappy Phone anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from Snappy Phone to Verizon and Verizonfrom Verizon to Snappy Phone. NavtelSnappy Phone’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Snappy Phone shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 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. Snappy Phone shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Snappy Phone shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Snappy Phone has not notified Verizon that it has corrected such blocking, Verizon may submit to Snappy Phone a Trunk Group Service Request directing Snappy Phone to remedy the blocking. Upon receipt of a Trunk Group Service Request, Snappy Phone will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to 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. 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-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, 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 Snappy Phone fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may bill Snappy Phone for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Snappy Phone’s network, Verizon’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 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 to 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 Snappy Phone to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Snappy Phone and the 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 have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelICG, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, ICG shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Navtel, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel and the Entrance Facility on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs. 2.4.2 Upon the parties undertaking a Major Project, where the Parties have agreed to use Two Way Interconnection Trunks, prior to ordering any Two-Way Interconnection Trunks from Verizon, ICG shall meet meet, telephonically or in person, with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party forecasted originating Centium Call Second CCS (Hundred Call Second) 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 Verizon’s (POI). For purposes of this Section 2.4.2, a “Major Project” is a project that requires the coordination and execution of multiple orders or related activities between and among Verizon and ICG work groups including, but not limited to, the initial establishment of Interconnection or Access Toll Connecting Trunk groups between a Verizon switch and an ICG switch, NXX code moves, re-homes, facility grooming, network in rearrangements, a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-conversion from 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 installation of such One- Way Interconnection Trunks to a new switch. 2.4.3 Two-Way Interconnection TrunksTrunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where ICG is collocated in a Verizon Wire Center, the POI may be at the Verizon Wire Center. 2.4.4 On a semi-annual basis, Navtel ICG shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel ICG anticipates that Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel and Verizonperiod. NavtelICG’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as provided to ICG and in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) CCS equal to five (5). 2.4.8 Verizon and ICG shall engineer Two-Way Interconnection Trunks using national standards and measurement methodologies. Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 during the average time consistent busy hour. Verizon and Navtel shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threeof‌‌

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelSynergem, NavtelSynergem, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable a Verizon access Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelSynergem, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Synergem shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 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, Navtel Synergem shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel Synergem anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Synergem and Verizon. NavtelSynergem’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Synergem 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 threethree (3) consecutive calendar traffic study months. 2.4.10 Synergem 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. Synergem shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Synergem shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and Synergem has not notified Verizon that it has corrected such blocking, Verizon may submit to Synergem a Trunk Group Service Request directing Synergem to remedy the blocking. Upon receipt of a Trunk Group Service Request, Synergem will complete an ASR to establish or augment the Meet Point A Two- Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. Synergem will promptly augment all 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 Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Synergem 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 Synergem fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and Synergem shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Synergem’s network, Verizon’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 Synergem will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR- TAP-000191, including but not limited to those standards requiring that a call from Synergem to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between Synergem and the Verizon End Office. 3.1 Fiber Meet Arrangement Provisions. 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 Synergem nor any of Synergem’s affiliates has an overdue balance on any xxxx rendered to Synergem or Synergem’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 Verizon and NavtelAPI, NavtelAPI, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable a Verizon access Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelAPI, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel API shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Centum Call Second Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel API shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel API anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel API and Verizon. NavtelAPI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Centum Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel API 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

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelNUI, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, NUI shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel NUI shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Meet Point A (high usage) and Meet Point B (final) Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel NUI shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel NUI anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from NUI to Verizon and Verizonfrom Verizon to NUI. NavtelNUI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel NUI shall engineer Two-Way Interconnection Trunks using 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 threethree (3) consecutive calendar traffic study months. 2.4.10 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. NUI shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. NUI shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and NUI has not notified Verizon that it has corrected such blocking, Verizon may submit to NUI a Trunk Group Service Request directing NUI to remedy the blocking. Upon receipt of a Trunk Group Service Request, NUI will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. NUI will promptly augment all 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 Meet Point B Two- Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, 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 NUI fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may xxxx NUI for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and NUI’s network, Verizon’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 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 to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-TAP- 000191, including but not limited to those standards requiring that a call from NUI to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between NUI and the 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 NUI. 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 NUI-IP, NUI shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on NUI’s side of the NUI-IP, NUI shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if NUI fails to provide NUI-IPs in accordance with this Agreement, NUI will be responsible for one hundred percent (100%) of all recurring and non- recurring charges associated with Two-Way Interconnection Trunk groups until NUI establishes such NUI-IPs.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelRVP, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, RVP shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel RVP shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel RVP shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel RVP anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from RVP to Verizon and Verizonfrom Verizon to RVP. NavtelRVP’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel RVP shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 RVP 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. RVP shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. RVP shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and RVP has not notified Verizon that it has corrected such blocking, Verizon may submit to RVP a Trunk Group Service Request directing RVP to remedy the blocking. Upon receipt of a Trunk Group Service Request, RVP will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to 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. RVP 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, RVP 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 RVP fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may xxxx RVP for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and RVP’s network, Verizon’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 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 RVP will route its traffic to 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 RVP to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between RVP and the 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. RVP will pay a percentage of Verizon’s monthly recurring charges for each facility on which the Two-Way Interconnection Trunks ride equal to RVP’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 RVP’s side of RVP’s-IP, which charges shall be solely the financial responsibility of RVP. 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 RVP-IP, RVP shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on RVP’s side of the RVP-IP, RVP shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if RVP fails to provide RVP-IPs in accordance with this Agreement, RVP will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until RVP establishes such RVP-IPs.

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

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelInterGlobe, NavtelInterGlobe, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelInterGlobe, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel InterGlobe shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel InterGlobe shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel InterGlobe anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel InterGlobe and Verizon. NavtelInterGlobe’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel InterGlobe shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 InterGlobe 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. InterGlobe shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. InterGlobe shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and InterGlobe has not notified Verizon that it has corrected such blocking, Verizon may submit to InterGlobe a Trunk Group Service Request directing InterGlobe to remedy the blocking. Upon receipt of a Trunk Group Service Request, InterGlobe 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 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. InterGlobe 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, InterGlobe 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 InterGlobe fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may bill InterGlobe for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and InterGlobe’s network, Verizon’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 InterGlobe will route its traffic to 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 InterGlobe to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between InterGlobe and the Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelECI, NavtelECI, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelECI, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel ECI shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office 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 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, Navtel ECI shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel ECI anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel ECI and Verizon. NavtelECI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel ECI shall engineer Two-Way Interconnection Trunks using 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 threethree (3) consecutive calendar traffic study months. 2.4.10 ECI 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. ECI shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. ECI shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and ECI has not notified Verizon that it has corrected such blocking, Verizon may submit to ECI a Trunk Group Service Request directing ECI to remedy the blocking. Upon receipt of a Trunk Group Service Request, ECI 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 Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. ECI will promptly augment all 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 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and ECI’s network, Verizon’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 ECI will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-TAP- 000191, including but not limited to those standards requiring that a call from ECI to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between ECI and the 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 Verizon and NavtelICG, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, ICG shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Navtel, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel and the Entrance Facility on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs. 2.4.2 Upon the parties undertaking a Major Project, where the Parties have agreed to use Two Way Interconnection Trunks, prior to ordering any Two-Way Interconnection Trunks from Verizon, ICG shall meet meet, telephonically or in person, with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party forecasted originating Centium Call Second CCS (Hundred Call Second) 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 Verizon’s (POI). For purposes of this Section 2.4.2, a “Major Project” is a project that requires the coordination and execution of multiple orders or related activities between and among Verizon and ICG work groups including, but not limited to, the initial establishment of Interconnection or Access Toll Connecting Trunk groups between a Verizon switch and an ICG switch, NXX code moves, re-homes, facility grooming, network in rearrangements, a LATA at which the Parties interconnect for the exchange conversion from One Way Interconnection Trunks to Two- Way Interconnection Trunks, and installation of traffic. Where the Parties have agreed to convert existing Onea new switch. 2.4.3 Two-Way Interconnection Trunks shall be from a Verizon End Office or Tandem to Two-Way Interconnection Trunksa mutually agreed upon POI. Where ICG is collocated in a Verizon Wire Center, the POI may 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 On a semi-annual basis, Navtel ICG shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel ICG anticipates that Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel and Verizonperiod. NavtelICG’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as provided to ICG and in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) CCS equal to five (5). 2.4.8 Verizon and ICG shall engineer Two-Way Interconnection Trunks using national standards and measurement methodologies. Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hourB.005. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 during the B.01. In performing trunk blockage measurements, Verizon will use an average time consistent busy hourhour methodology, as set out in Telcordia publication SR-TAP-000191. If ICG elects to perform trunk blockage measurements using a method of measurement (for instance, a method that uses a peak busy hour measurement) that differs from that used by Verizon and Navtel shall engineer ICG’s method of measurement indicates a need for a different number of Two-Way Interconnection Trunks using BOC Notes on than the LEC Networks SRmethod of measurement used by Verizon, the Parties shall negotiate in good faith to determine the number of Two-TSV-002275Way Interconnection Trunks that should be used. If the Parties are unable to agree upon the number of Two-Way Interconnection Trunks that should be used, either Party may submit the matter to dispute resolution pursuant to Section 14 of the General Terms and Conditions. 2.4.9 After a Two-Way Interconnection Trunk group has been established, ICG 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 such Two-Way Interconnection Trunk group. ICG shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. The performance standard provisioning intervals offered by Verizon to ICG for orders for 240 or fewer DS0 Two-Way Interconnection Trunks shall be no longer than the provisioning intervals offered by Verizon to other similarly situated CLECs for orders for 240 or fewer DS0 Two-Way Interconnection Trunks. Except as otherwise provided in an applicable Verizon Tariff, the provisioning intervals offered by Verizon to ICG for orders for 240 or more DS0 Two-Way Interconnection Trunks shall be subject to negotiation by the Parties. ICG orders for Two-Way Interconnection Trunks shall be subject to Section 2.2.5 above and other applicable provisions of this Agreement and applicable Verizon Tariffs. ICG shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time. 2.4.10 Each Party may monitor Two-Way Interconnection Trunk Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Interconnection Trunk group and ICG has not notified Verizon that it has corrected such blocking, Verizon may submit to ICG a Trunk Group Service Request directing ICG to remedy the blocking. Upon receipt of a Trunk Group Service Request, ICG will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. If ICG observes blocking in excess of the applicable design objective on any final Two-Way Interconnection Trunk group, ICG shall submit an ASR to augment the Two-Way Interconnection Trunk Group. 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. ICG 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, ICG 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. In the event ICG fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may bill ICG for the excess Interconnection Trunks at the applicable rates provided for in the Pricing Attachment, provided that Verizon sends ICG written notice, in the form of a Trunk Group Service Request, sixty (60) days prior to sending a bill and such notice identifies the underutilized trunk groups. 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 threethree (3) consecutive calendar traffic study months. 2.4.13 Because Verizon will not be in control of the timing and sizing of the Two-Way Interconnection Trunks between its network and ICG’s network, Verizon’s performance on these Two-Way Interconnection Trunk groups (except for maintenance intervals and missed installation appointments) 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 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 Each Party will route its traffic to the other Party over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR-TAP192, including but not limited to those standards requiring that a call from either Party to the other Party's End Office will first be routed to the End Office Interconnection Trunk group between ICG and the 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 or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Interconnection Trunks. ICG will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Interconnection Trunks ride equal to ICG’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 ICG’s side of ICG’s-IP, which charges shall be solely the financial responsibility of ICG. 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 ICG-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on ICG’s side of the ICG-IP, ICG shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if ICG fails to provide IPs in accordance with this Agreement, ICG will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until ICG establishes such IPs.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCamarato, NavtelCamarato, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelXxxxxxxx, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Xxxxxxxx shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel Xxxxxxxx shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel Xxxxxxxx anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Xxxxxxxx and Verizon. Navtel’s Xxxxxxxx’x trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Xxxxxxxx shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 Xxxxxxxx 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. Xxxxxxxx shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Xxxxxxxx shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Xxxxxxxx has not notified Verizon that it has corrected such blocking, Verizon may submit to Xxxxxxxx a Trunk Group Service Request directing Xxxxxxxx to remedy the blocking. Upon receipt of a Trunk Group Service Request, Xxxxxxxx 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 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. Xxxxxxxx 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, Xxxxxxxx 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 Xxxxxxxx fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may xxxx Xxxxxxxx for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Xxxxxxxx’x network, Verizon’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 Xxxxxxxx will route its traffic to 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 Xxxxxxxx to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Xxxxxxxx and the Verizon End Office.

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

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelXxxxxxx.xxx Inc., NavtelXxxxxxx.xxx Inc., at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelXxxxxxx.xxx Inc., Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Xxxxxxx.xxx Inc. shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office 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 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, Navtel Xxxxxxx.xxx Inc. shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel Xxxxxxx.xxx Inc. anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Xxxxxxx.xxx Inc. and Verizon. NavtelXxxxxxx.xxx Inc.’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Xxxxxxx.xxx Inc. shall engineer Two-Way Interconnection Trunks using 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 threethree (3) consecutive calendar traffic study months.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelVarTec, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, VarTec shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel VarTec shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel VarTec shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel VarTec anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from VarTec to Verizon and Verizonfrom Verizon to VarTec. NavtelVarTec’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel VarTec shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 VarTec 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. VarTec shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. VarTec shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and VarTec has not notified Verizon that it has corrected such blocking, Verizon may submit to VarTec a Trunk Group Service Request directing VarTec to remedy the blocking. Upon receipt of a Trunk Group Service Request, VarTec will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to 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. VarTec 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, VarTec 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 VarTec fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may xxxx VarTec for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and VarTec’s network, Verizon’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 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 VarTec will route its traffic to 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 VarTec to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between VarTec and the 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. VarTec will pay a percentage of Verizon’s monthly recurring charges for each facility on which the Two-Way Interconnection Trunks ride equal to VarTec’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 VarTec’s side of VarTec’s-IP, which charges shall be solely the financial responsibility of VarTec. 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 VarTec-IP, VarTec shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on VarTec’s side of the VarTec-IP, VarTec shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if VarTec fails to provide VarTec-IPs in accordance with this Agreement, VarTec will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until VarTec establishes such VarTec- IPs.

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelProspeed, NavtelProspeed, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelProspeed, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Prospeed shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office 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 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, Navtel Prospeed shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel Prospeed anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Prospeed and Verizon. NavtelProspeed’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Prospeed shall engineer Two-Way Interconnection Trunks using 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 threethree (3) consecutive calendar traffic study months. 2.4.10 Prospeed 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. Prospeed shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Prospeed shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and Prospeed has not notified Verizon that it has corrected such blocking, Verizon may submit to Prospeed a Trunk Group Service Request directing Prospeed to remedy the blocking. Upon receipt of a Trunk Group Service Request, Prospeed 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 Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. Prospeed will promptly augment all 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 Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Prospeed 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 Prospeed fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may bill Prospeed for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Prospeed’s network, Verizon’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 Prospeed will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR- TAP-000191, including but not limited to those standards requiring that a call from Prospeed to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between Prospeed and the Verizon End Office.

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

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelPNG, NavtelPNG, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelPNG, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel PNG shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel PNG shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel PNG anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel PNG and Verizon. NavtelPNG’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel PNG shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 PNG 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. PNG shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. PNG shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and PNG has not notified Verizon that it has corrected such blocking, Verizon may submit to PNG a Trunk Group Service Request directing PNG to remedy the blocking. Upon receipt of a Trunk Group Service Request, PNG 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 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. PNG 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, PNG 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 PNG fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may xxxx PNG for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and PNG’s network, Verizon’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 PNG will route its traffic to 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 PNG to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between PNG and the 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 Verizon and NavtelXX0, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, XX0 shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel IG2 shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel IG2 shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel IG2 anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from IG2 to Verizon and Verizonfrom Verizon to IG2. NavtelIG2’s trunk forecasts shall conform to the 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 Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel IG2 shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCCI, NavtelCCI, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCCI, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel CCI shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel CCI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel CCI anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel CCI and Verizon. NavtelCCI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office TwoTw o-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel CCI shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 CCI 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. CCI shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. CCI shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and CCI has not notified Verizon that it has corrected such blocking, Verizon may submit to CCI a Trunk Group Service Request directing CCI to remedy the blocking. Upon receipt of a Trunk Group Service Request, CCI 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 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. CCI 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, CCI 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 CCI fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may bill CCI for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and CCI’s network, Verizon’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 CCI will route its traffic to 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 CCI to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between CCI and the Verizon End Office.

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

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCovista, NavtelCovista, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCovista, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Covista shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second Seconds (Hundred Call SecondSeconds) 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 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, Navtel Covista shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel Covista anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Covista and Verizon. NavtelCovista’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Covista shall engineer Two-Way Interconnection Trunks using 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 threethree (3) consecutive calendar traffic study months. 2.4.10 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. Covista shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Covista shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of Upon receipt of a Trunk Group Service Request, Covista will complete an ASR to establish or augment the Meet Point A Two-Way Interconnection Trunk group(s), or, if mutually agreed, to augment the Meet Point B Two-Way Interconnection Trunk group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. Covista will promptly augment all 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 Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, 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 Covista fails to submit an ASR for Two- Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or bill (and Covista shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and Covista’s network, Verizon’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 Covista will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR- TAP-000191, including but not limited to those standards requiring that a call from Covista to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between Covista and the 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 use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelECI, NavtelECI, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelECI, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel ECI shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel ECI shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel ECI anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel ECI and Verizon. NavtelECI’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel ECI shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelPW, NavtelPW, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelPW, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel PW shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel PW shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel PW anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel PW and Verizon. NavtelPW’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel PW shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 PW 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. PW shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. PW shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and PW has not notified Verizon that it has corrected such blocking, Verizon may submit to PW a Trunk Group Service Request directing PW to remedy the blocking. Upon receipt of a Trunk Group Service Request, PW 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 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. PW 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, PW 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 PW fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may bill PW for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and PW’s network, Verizon’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 PW will route its traffic to 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 PW to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between PW and the Verizon End Office.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCSTC, NavtelCSTC, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelCSTC, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel CSTC shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office 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 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, Navtel CSTC shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel CSTC anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel CSTC and Verizon. NavtelCSTC’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel CSTC shall engineer Two-Way Interconnection Trunks using 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 threethree (3) consecutive calendar traffic study months. 2.4.10 CSTC 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. CSTC shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. CSTC shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and CSTC has not notified Verizon that it has corrected such blocking, Verizon may submit to CSTC a Trunk Group Service Request directing CSTC to remedy the blocking. Upon receipt of a Trunk Group Service Request, CSTC 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 Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. CSTC will promptly augment all 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 Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, CSTC 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 CSTC fails to submit an ASR for Two- Way Interconnection Trunks in conformance with this Section, Verizon may xxxx CSTC for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and CSTC’s network, Verizon’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 CSTC will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR-TAP- 000191, including but not limited to those standards requiring that a call from CSTC to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between CSTC and the Verizon End Office.

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelVarTec, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, VarTec shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel VarTec shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Meet Point A (high usage) and Meet Point B (final) Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel VarTec shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel VarTec anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from VarTec to Verizon and Verizonfrom Verizon to VarTec. NavtelVarTec’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel VarTec shall engineer Two-Way Interconnection Trunks using 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 threethree (3) consecutive calendar traffic study months. 2.4.10 VarTec 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. VarTec shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. VarTec shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and VarTec has not notified Verizon that it has corrected such blocking, Verizon may submit to VarTec a Trunk Group Service Request directing VarTec to remedy the blocking. Upon receipt of a Trunk Group Service Request, VarTec will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. VarTec will promptly augment all 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 Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, VarTec 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 VarTec fails to submit an ASR for Two- Way Interconnection Trunks in conformance with this section, Verizon may bill VarTec for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and VarTec’s network, Verizon’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 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 VarTec will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interc onnection Trunks in accordance with SR-TAP- 000191, including but not limited to those standards requiring that a call from VarTec to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between VarTec and the 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. VarTec will pay a percentage of Verizon’s monthly recurring charges for each facility on which the Two-Way Interconnection Trunks ride equal to VarTec’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 VarTec’s side of VarTec’s-IP, which charges shall be solely the financial responsibility of VarTec. 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 VarTec-IP, VarTec shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on VarTec’s side of the VarTec-IP, VarTec shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if VarTec fails to provide VarTec-IPs in accordance with this Agreement, VarTec will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until VarTec establishes such VarTec- IPs.

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelKDL, NavtelKDL, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-third party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelKDL, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel KDL shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second Seconds (Hundred Call SecondSeconds) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel KDL shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel KDL anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel KDL and Verizon. NavtelKDL’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second Seconds (Hundred Call SecondSeconds) 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 Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel KDL 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 threethree (3) consecutive calendar traffic study months. 2.4.10 KDL 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. KDL shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. KDL shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and KDL has not notified Verizon that it has corrected such blocking, Verizon may submit to KDL a Trunk Group Service Request directing KDL to remedy the blocking. Upon receipt of a Trunk Group Service Request, KDL 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 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. KDL 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, KDL 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 KDL fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may disconnect the excess Interconnection Trunks or xxxx (and KDL shall pay) for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two- Way Interconnection Trunks are established between its network and KDL’s network, Verizon’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 KDL will route its traffic to 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 KDL to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between KDL and the 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 Verizon and NavtelXX0, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, XX0 shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel IG2 shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel IG2 shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel IG2 anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from IG2 to Verizon and Verizonfrom Verizon to IG2. NavtelIG2’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel IG2 shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for three

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelPrepaid, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, Prepaid shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel Prepaid shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel Prepaid shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel Prepaid anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from Prepaid to Verizon and Verizonfrom Verizon to Prepaid. NavtelPrepaid’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Prepaid shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 Prepaid 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. Prepaid shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Prepaid shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Prepaid has not notified Verizon that it has corrected such blocking, Verizon may submit to Prepaid a Trunk Group Service Request directing Prepaid to remedy the blocking. Upon receipt of a Trunk Group Service Request, Prepaid will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to 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. Prepaid 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, Prepaid 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 Prepaid fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may bill Prepaid for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Prepaid’s network, Verizon’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 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 Prepaid will route its traffic to 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 Prepaid to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Prepaid and the 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. Prepaid will pay a percentage of Xxxxxxx’s monthly recurring charges for each facility on which the Two-Way Interconnection Trunks ride equal to Prepaid’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 Prepaid’s side of Prepaid’s-IP, which charges shall be solely the financial responsibility of Prepaid. 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 Prepaid-IP, Prepaid shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on Prepaid’s side of the Prepaid-IP, Prepaid shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if Prepaid fails to provide Prepaid-IPs in accordance with this Agreement, Prepaid will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until Prepaid establishes such Prepaid-IPs.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelNTC, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, NTC shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for and the exchange of traffic between Verizon Entrance Facility, on which such Trunks will ride, and Navteltransport and multiplexing, Verizonin accordance with the rates, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on terms 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, Navtel NTC shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of Two-Way End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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 a mutually agreed upon POI. 2.4.4 On a semi-annual basis, Navtel NTC shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel NTC anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from NTC to Verizon and Verizonfrom Verizon to NTC. NavtelNTC’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel NTC shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 NTC 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. NTC shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. NTC shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and NTC has not notified Verizon that it has corrected such blocking, Verizon may submit to NTC a Trunk Group Service Request directing NTC to remedy the blocking. Upon receipt of a Trunk Group Service Request, NTC will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to 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. NTC 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, NTC 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 NTC fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may xxxx NTC for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and NTC’s network, Verizon’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 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.

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

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelTalk Unlimited, NavtelTalk Unlimited 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 which 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 Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from VerizonTariffs. 2.4.2 Where the Parties use Prior to ordering any Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Navtel, from Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Talk Unlimited shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Meet Point A (high usage) and Meet Point B (final) Interconnection Trunks and the interface specifications at the technically feasible Point(s) Point of Interconnection on Verizon’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, Navtel Talk Unlimited shall submit a good faith forecast to Verizon of the number of End Office Meet Point A (high usage) and Tandem Meet Point B (final) Two-Way Interconnection Trunks that Navtel Talk Unlimited anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of to carry traffic between Navtel from Talk Unlimited to Verizon and Verizonfrom Verizon to Talk Unlimited. NavtelTalk Unlimited’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office 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 Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hour. Meet Point B Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Talk Unlimited shall engineer Two-Two- Way Interconnection Trunks using 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 threethree (3) consecutive calendar traffic study months. 2.4.10 Talk Unlimited 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. Talk Unlimited shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Talk Unlimited shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Meet Point B (final) Two-Way Interconnection Trunk group and Talk Unlimited has not notified Verizon that it has corrected such blocking, Verizon may submit to Talk Unlimited a Trunk Group Service Request directing Talk Unlimited to remedy the blocking. Upon receipt of a Trunk Group Service Request, Talk Unlimited will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. 2.4.12 The Parties will review all 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. Talk Unlimited will promptly augment all 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 Meet Point B Two-Way Interconnection Trunk group with a utilization level of less than sixty percent (60%), unless the Parties agree otherwise, Talk Unlimited 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 Talk Unlimited fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may bill Talk Unlimited for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Talk Unlimited’s network, Verizon’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 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 Talk Unlimited will route its traffic to Verizon over the Meet Point A and/or Meet Point B Two-Way Interconnection Trunks in accordance with SR- TAP-000191, including but not limited to those standards requiring that a call from Talk Unlimited to a Verizon End Office will first be routed to the Meet Point A Interconnection Trunk group between Talk Unlimited and the 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. Talk Unlimited will pay a percentage of Verizon’s monthly recurring charges for each facility on which the Two-Way Interconnection Trunks ride equal to Talk Unlimited’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 Talk Unlimited’s side of Talk Unlimited’s-IP, which charges shall be solely the financial responsibility of Talk Unlimited. 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 Talk Unlimited-IP, Talk Unlimited shall pay fifty percent (50%) of the Verizon non-recurring charges; and, (b) for the portion of the facility on Talk Unlimited’s side of the Talk Unlimited-IP, Talk Unlimited shall be solely responsible for the non-recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if Talk Unlimited fails to provide Talk Unlimited-IPs in accordance with this Agreement, Talk Unlimited will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until Talk Unlimited establishes such Talk Unlimited-IPs.

Two-Way Interconnection Trunks. 2.4.1 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelAdvent, NavtelAdvent, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, from Verizon. 2.4.2 Where the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelAdvent, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel Advent shall meet with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party originating Centium Call Second (Hundred Call Second) information, and the Parties shall mutually agree on the appropriate initial number of End Office and Tandem Two-Way Interconnection Trunks and the interface specifications at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-Way Interconnection Trunks to Two-Way Interconnection Trunks, at the Joint Planning Meeting, the Parties shall also mutually agree on the conversion process and project intervals for conversion of such One- Way Interconnection Trunks to Two-Way Interconnection Trunks. 2.4.4 On a semi-annual basis, Navtel Advent shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel Advent anticipates Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel Advent and Verizon. NavtelAdvent’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) equal to five (5). 2.4.8 Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx B.005 during the average time consistent busy hour. Two-Two- Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxx- Xxxxxxxxx X.01 B.01 during the average time consistent busy hour. Verizon and Navtel Advent shall engineer Two-Way Interconnection Trunks using BOC Notes on the LEC Networks SR-TSV-002275. 2.4.9 The performance standard for final Two-Way Interconnection Trunk groups shall be that no such Interconnection Trunk group will exceed its design blocking objective (B.005 or B.01, as applicable) for threethree (3) consecutive calendar traffic study months. 2.4.10 Advent 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. Advent shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. Advent shall complete ASRs in accordance with OBF Guidelines as in effect from time to time. 2.4.11 Verizon may (but shall not be obligated to) monitor Two-Way Interconnection Trunk groups using service results for the applicable design blocking objective. If Verizon observes blocking in excess of the applicable design objective on any Tandem Two-Way Interconnection Trunk group and Advent has not notified Verizon that it has corrected such blocking, Verizon may submit to Advent a Trunk Group Service Request directing Advent to remedy the blocking. Upon receipt of a Trunk Group Service Request, Advent 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 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. Advent 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, Advent 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 Advent fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this Section, Verizon may xxxx Advent for the excess Interconnection Trunks at the applicable Verizon rates. 2.4.13 Because Verizon will not be in control of when and how many Two-Way Interconnection Trunks are established between its network and Advent’s network, Verizon’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 Advent will route its traffic to 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 Advent to a Verizon End Office will first be routed to the End Office Interconnection Trunk group between Advent and the Verizon End Office.

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

Two-Way Interconnection Trunks. 2.4.1 Where the Parties have agreed to use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and NavtelICG, Navtel, at its own expense, shall: 2.4.1.1 provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA; and/or 2.4.1.2 obtain transport to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA (a) from a third-party, or, (b) if Verizon offers such transport pursuant to this Agreement or an applicable Verizon Tariff, ICG shall order from Verizon. 2.4.2 Where , and Verizon shall provide, the Parties use Two-Way Interconnection Trunks for the exchange of traffic between Verizon and Navtel, Verizon, at its own expense, shall provide its own facilities to the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA. 2.4.3 Prior to establishing any Two-Way Interconnection Trunks, Navtel and the Entrance Facility on which such Trunks will ride, and transport and multiplexing, in accordance with the rates, terms and conditions set forth in this Agreement and Verizon’s applicable Tariffs. 2.4.2 Upon the parties undertaking a Major Project, where the Parties have agreed to use Two Way Interconnection Trunks, prior to ordering any Two-Way Interconnection Trunks from Verizon, ICG shall meet meet, telephonically or in person, with Verizon to conduct a joint planning meeting (“Joint Planning Meeting”). At that Joint Planning Meeting, each Party shall provide to the other Party forecasted originating Centium Call Second CCS (Hundred Call Second) 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 Verizon’s (POI). For purposes of this Section 2.4.2, a “Major Project” is a project that requires the coordination and execution of multiple orders or related activities between and among Verizon and ICG work groups including, but not limited to, the initial establishment of Interconnection or Access Toll Connecting Trunk groups between a Verizon switch and an ICG switch, NXX code moves, re-homes, facility grooming, network in rearrangements, a LATA at which the Parties interconnect for the exchange of traffic. Where the Parties have agreed to convert existing One-conversion from 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 installation of such One- Way Interconnection Trunks to a new switch. 2.4.3 Two-Way Interconnection TrunksTrunks shall be from a Verizon End Office or Tandem to a mutually agreed upon POI. Where ICG is collocated in a Verizon Wire Center, the POI may be at the Verizon Wire Center. 2.4.4 On a semi-annual basis, Navtel ICG shall submit a good faith forecast to Verizon of the number of End Office and Tandem Two-Way Interconnection Trunks that Navtel ICG anticipates that Verizon will need to provide during the ensuing two (2) year period for the exchange of traffic between Navtel and Verizonperiod. NavtelICG’s trunk forecasts shall conform to the Verizon CLEC trunk forecasting guidelines as provided to ICG and in effect at that time. 2.4.5 The Parties shall meet (telephonically or in person) from time to time, as needed, to review data on End Office and Tandem Two-Way Interconnection Trunks to determine the need for new trunk groups and to plan any necessary changes in the number of Two-Way Interconnection Trunks. 2.4.6 Two-Way Interconnection Trunks shall have SS7 Common Channel Signaling. The Parties agree to utilize B8ZS and Extended Super Frame (ESF) DS1 facilities, where available. 2.4.7 With respect to End Office Two-Way Interconnection Trunks, both Parties shall use an economic Centium Call Second (Hundred Call Second) CCS equal to five (5). 2.4.8 Verizon and ICG shall engineer Two-Way Interconnection Trunks using national standards and measurement methodologies. Two-Way Interconnection Trunk groups that connect to a Verizon access Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx B.005 during the average time consistent busy hourB.005. Two-Way Interconnection Trunk groups that connect to a Verizon local Tandem shall be engineered using a design blocking objective of Xxxx-Xxxxxxxxx X.01 during the B.01. In performing trunk blockage measurements, Verizon will use an average time consistent busy hourhour methodology, as set out in Telcordia publication SR-TAP-000191. If ICG elects to perform trunk blockage measurements using a method of measurement (for instance, a method that uses a peak busy hour measurement) that differs from that used by Verizon and Navtel shall engineer ICG’s method of measurement indicates a need for a different number of Two-Way Interconnection Trunks using BOC Notes on than the LEC Networks SRmethod of measurement used by Verizon, the Parties shall negotiate in good faith to determine the number of Two-TSV-002275Way Interconnection Trunks that should be used. If the Parties are unable to agree upon the number of Two-Way Interconnection Trunks that should be used, either Party may submit the matter to dispute resolution pursuant to Section 14 of the General Terms and Conditions. 2.4.9 After a Two-Way Interconnection Trunk group has been established, ICG 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 such Two-Way Interconnection Trunk group. ICG shall order Two-Way Interconnection Trunks by submitting ASRs to Verizon setting forth the number of Two-Way Interconnection Trunks to be installed and the requested installation dates within Verizon’s effective standard intervals or negotiated intervals, as appropriate. The performance standard provisioning intervals offered by Verizon to ICG for orders for 240 or fewer DS0 Two-Way Interconnection Trunks shall be no longer than the provisioning intervals offered by Verizon to other similarly situated CLECs for orders for 240 or fewer DS0 Two-Way Interconnection Trunks. Except as otherwise provided in an applicable Verizon Tariff, the provisioning intervals offered by Verizon to ICG for orders for 240 or more DS0 Two-Way Interconnection Trunks shall be subject to negotiation by the Parties. ICG orders for Two-Way Interconnection Trunks shall be subject to Section 2.2.5 above and other applicable provisions of this Agreement and applicable Verizon Tariffs. ICG shall complete ASRs in accordance with Ordering and Billing Forum Guidelines as in effect from time to time. 2.4.10 Each Party may monitor Two-Way Interconnection Trunk Groups using service results for the applicable design-blocking objective. If Verizon observes blocking in excess of the applicable design objective on any final Two-Way Interconnection Trunk group and ICG has not notified Verizon that it has corrected such blocking, Verizon may submit to ICG a Trunk Group Service Request directing ICG to remedy the blocking. Upon receipt of a Trunk Group Service Request, ICG will complete an ASR to augment the Two-Way Interconnection Trunk Group with excessive blocking and submit the ASR to Verizon within five (5) Business Days. If ICG observes blocking in excess of the applicable design objective on any final Two-Way Interconnection Trunk group, ICG shall submit an ASR to augment the Two-Way Interconnection Trunk Group. 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. ICG 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, ICG 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. In the event ICG fails to submit an ASR for Two-Way Interconnection Trunks in conformance with this section, Verizon may bill ICG for the excess Interconnection Trunks at the applicable rates provided for in the Pricing Attachment, provided that Verizon sends ICG written notice, in the form of a Trunk Group Service Request, sixty (60) days prior to sending a bill and such notice identifies the underutilized trunk groups. 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 threethree (3) consecutive calendar traffic study months. 2.4.13 Because Verizon will not be in control of the timing and sizing of the Two-Way Interconnection Trunks between its network and ICG’s network, Verizon’s performance on these Two-Way Interconnection Trunk groups (except for maintenance intervals and missed installation appointments) 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 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 Each Party will route its traffic to the other Party over the End Office and Tandem Two-Way Interconnection Trunks in accordance with SR- TAP192, including but not limited to those standards requiring that a call from either Party to the other Party's End Office will first be routed to the End Office Interconnection Trunk group between ICG and the 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 or “PPU” factor, based on the total number of minutes of Traffic that each Party originates over the Two-Way Interconnection Trunks. ICG will pay a percentage of Verizon’s monthly recurring charges for the facility on which the Two-Way Interconnection Trunks ride equal to ICG’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 ICG’s side of ICG’s-IP, which charges shall be solely the financial responsibility of ICG. 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 ICG-IP, the non-recurring charges shall be divided equally between the Parties; and, (b) for the portion of the Trunks on ICG’s side of the ICG-IP, ICG shall be solely responsible for the non- recurring charges. Notwithstanding the foregoing provisions of this Section 2.4.16, if ICG fails to provide IPs in accordance with this Agreement, ICG will be responsible for one hundred percent (100%) of all recurring and non-recurring charges associated with Two-Way Interconnection Trunk groups until ICG establishes such IPs.

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

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