Common use of Network Interconnection Clause in Contracts

Network Interconnection. 3.1 This Attachment pertains only to the provision of network interconnection where ComSouth owns, leases from a third party or otherwise provides its own switch(es). 3.2 Network interconnection may be provided by the Parties at any technically feasible point within BellSouth’s network. Requests to BellSouth for interconnection at points other than as set forth in this Attachment may be made through the Bona Fide Request/New Business Request (BFR/NBR) Process set forth in Attachment 11. 3.2.1 Each Party is responsible for providing, engineering and maintaining the network on its side of the IP. The IP must be located within BellSouth’s serving territory in the LATA in which traffic is originating. The IP determines the point at which the originating Party shall pay the terminating Party for the Call Transport and Termination of Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic. In selecting the IP, both Parties will act in good faith and select the point that is most efficient for both Parties. 3.2.2 Pursuant to the provisions of this Attachment, the location of the initial IP in a given LATA shall be established by mutual agreement of the Parties. Subject to the requirements for installing additional IPs, as set forth below, any IPs existing prior to the Effective Date of the Agreement will be accepted as initial IPs and will not require re-grooming. When the Parties mutually agree to utilize two-way interconnection trunk groups for the exchange of Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic between each other, the Parties shall mutually agree to the location of IP(s). If the Parties are unable to agree to a mutual initial IP, each Party, as originating Party, shall establish a single IP in the LATA for the delivery of its originated Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic to the other Party for Call Transport and Termination by the terminating Party. 3.2.3 Additional IP(s) in a LATA may be established by mutual agreement of the Parties. Notwithstanding the foregoing, additional IP(s) in a particular LATA shall be established, at the request of either Party, when the Local Traffic and ISP-Bound Traffic exceeds eight point nine (8.9) million minutes per month for three (3) consecutive months at the proposed location of the additional IP. BellSouth will not request the establishment of an IP in a BellSouth Central Office where physical or virtual collocation space is not available or where BellSouth fiber connectivity is not available. When the Parties agree to utilize two-way interconnection trunk groups for the exchange of Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic the Parties must agree to the location of the IP(s).

Network Interconnection. 3.1 This Attachment pertains only to the provision of network interconnection where ComSouth PBT owns, leases from a third party or otherwise provides its own switch(es). 3.2 Network interconnection may be provided by the Parties at any technically feasible point within BellSouth’s network. Requests to BellSouth for interconnection at points other than as set forth in this Attachment may be made through the Bona Fide Request/New Business Request (BFR/NBR) Process process set forth out in Attachment 11this Agreement. 3.2.1 Each Party is responsible for providing, engineering and maintaining the network on its side of the IP. The IP must be located within BellSouth’s serving territory in the LATA in which traffic is originating. The IP determines the point at which the originating Party shall pay the terminating Party for the Call Transport and Termination of Local Traffic, ISP-Bound bound Traffic and IntraLATA Toll Traffic. In selecting the IP, both Parties will act in good faith and select the point that is most efficient for both Parties. 3.2.2 Pursuant to the provisions of this Attachment, the location of the initial IP in a given LATA shall be established by mutual agreement of the Parties. Subject to the requirements for installing additional IPsIP(s), as set forth below, any IPs IP(s) existing prior to the Effective Date of the Agreement will be accepted as initial IPs IP(s) and will not require re-grooming. Such existing IP(s) are currently located at each BellSouth access tandem in the LATA in which the Parties are currently exchanging traffic. In the event BellSouth establishes an additional access tandem in a LATA where PBT has an existing IP as of the Effective Date of this Agreement, the terms and conditions of Section 3.2.4 shall apply. 3.2.3 Pursuant to the provisions of this Attachment and subject to the terms and conditions of Section 3.2.2 above, the location of the initial IP(s) in a given LATA shall be established at every BellSouth access tandem in that LATA.. When the Parties mutually agree to utilize two-way interconnection trunk groups for the exchange of Local Traffic, ISP-Bound bound Traffic and IntraLATA Toll Traffic between each other, the Parties shall mutually agree to the location of IP(s). If the Parties are unable to agree to a mutual initial IP, each Party, as originating Party, shall establish a single IP in the LATA for the delivery of its originated Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic to the other Party for Call Transport and Termination by the terminating Party. 3.2.3 3.2.4 Additional IP(s) in a LATA may be established by mutual agreement of the Parties. Notwithstanding the foregoing, additional IP(s) in a particular LATA shall be established, at the request of either Party, when the Local Traffic and ISP-Bound bound Traffic exceeds eight point nine (8.9) 8.9 million minutes per month for three (3) consecutive months at the proposed location of the additional IP. BellSouth will not request the establishment of an IP in a BellSouth Central Office where physical or virtual collocation space is not available or where BellSouth fiber connectivity is not available. When the Parties agree to utilize two-way interconnection trunk groups for the exchange of Local Traffic, ISP-Bound bound Traffic and IntraLATA Toll Traffic the Parties must agree to the location of the IP(s). 3.3 Interconnection via Dedicated Facilities 3.3.1 With the exception of Transit Traffic, the Parties shall institute a “xxxx and keep” compensation plan under which neither Party will charge the other Party recurring and nonrecurring charges as set forth in Exhibit A for trunks (one-way or two- way) and associated dedicated facilities for the exchange of Local Traffic and ISP- bound Traffic. The portions of trunks and facilities utilized for Local Traffic and ISP-bound traffic subject to xxxx and keep in accordance with this section shall be determined based upon the application of the Percent Local Facility

Network Interconnection. 3.1 This Attachment pertains only 4.1 Interconnection between the Company Network and the Ozone Network will be achieved through a number of Interconnection Links. Each Interconnection Link will identify a connection between one of the Company Interconnection Nodes and one of the Ozone Interconnection Nodes. Details of the manner in which this shall be achieved are set out in Annex E hereof, as may be amended from time to time by the Joint Technical Committee. The technical standards supported by either Party for the purposes of this Agreement are set out in Annex H as may be amended from time to time by the Joint Technical Committee set up in accordance with this Agreement. 4.2 Interconnection Links will be provided and operated in the manner described in Service Schedule 1 of Annex C. 4.3 The actual Point of Interconnection shall be where the Requested Party’s Network connects with the Requesting Party’s Network and shall be a physical point at the site of the Requesting Party or the Requested Party, where the connection can be disconnected in order to conduct testing. Each Party shall be wholly responsible for providing sufficient capacity on an appropriate transmission medium from the Point of Interconnection to meet the agreed forecasted requirements in the Network Plan. Each Party shall be wholly responsible for the operation and maintenance of this transmission medium. Any determinations required in terms of capacity and transmission media shall be determined by the Joint Technical Committee. 4.4 Either Party shall have the right at any time during the duration of this Agreement to indicate the Interconnection Node in its Network so as to provide optimal network connectivity with the rest of its Network. In the eventuality that the Requesting Party insists upon a particular Interconnection Node and the Requested Party encounters any technical problems in regard to such Interconnection Node, the Requested Party reserves the right to refuse such Interconnection Node and to offer the Requesting Party an alternative Interconnection Node, such request not to be unreasonably withheld. 4.5 All infrastructure necessary for the purposes of this Agreement, including but not limited to the provision of network interconnection where ComSouth ownsInterconnection Links, leases from a third party or otherwise provides its own switch(es). 3.2 Network interconnection may shall be provided by the Parties themselves to one another, and only in the event that neither Party is able to provide any part of such infrastructure shall the Parties undertake to find an alternative Third Party provider of the same. 4.6 The ordering periods for new Interconnection Links shall be as defined in Annex D hereof. 4.7 The requirements for connection and capacity available at each Point of Interconnection shall be as set out in Annex E hereof. The Requested Party shall, upon written request by the Requesting Party, provide within a reasonable period additional capacity at any technically feasible point within BellSouthof the Interconnection Nodes in the Requested Party’s network. Requests to BellSouth for interconnection at points other than Network as set forth in this Attachment may be made through appropriate should this be considered technically possible and feasibly acceptable by the Bona Fide Request/New Business Request (BFR/NBR) Process set forth in Attachment 11Requested Party to enable the Requesting Party to operate its Network efficiently and effectively. 3.2.1 Each Party is 4.8 The Parties will not be responsible for providing, engineering and maintaining the network on its side content of the IP. The IP must be located within BellSouth’s serving territory in the LATA in which traffic is originating. The IP determines the point at which the originating Party shall pay the terminating Party for the Call Transport and Termination of Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic. In selecting the IP, both Parties will act in good faith and select the point that is most efficient for both Partiesconveyed through their respective Networks. 3.2.2 Pursuant 4.9 The Parties have agreed to the provisions of this Attachment, the location of the initial IP in a given LATA shall interconnect using session initiation protocal (SIP) and therefore anticipate that no costs will be established required to be incurred by mutual agreement either of the Parties. Subject to In the requirements for installing additional IPs, as set forth below, any IPs existing prior to the Effective Date of the Agreement will be accepted as initial IPs and will not require re-grooming. When event that the Parties mutually agree to utilize two-way interconnection trunk groups for the exchange utilise another method of Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic between each otherinterconnection, the Parties shall mutually also agree to which Party shall bear the location of IP(s). If the Parties are unable to agree to a mutual initial IP, each Party, as originating Party, shall establish a single IP in the LATA for the delivery of its originated Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic to the other Party for Call Transport and Termination by the terminating Partycosts. 3.2.3 Additional IP(s) in a LATA may be established by mutual agreement of the Parties. Notwithstanding the foregoing, additional IP(s) in a particular LATA shall be established, at the request of either Party, when the Local Traffic and ISP-Bound Traffic exceeds eight point nine (8.9) million minutes per month for three (3) consecutive months at the proposed location of the additional IP. BellSouth will not request the establishment of an IP in a BellSouth Central Office where physical or virtual collocation space is not available or where BellSouth fiber connectivity is not available. When the Parties agree to utilize two-way interconnection trunk groups for the exchange of Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic the Parties must agree to the location of the IP(s).

Network Interconnection. Version: 4Q04 Standard ICA 06/15/05 3.1 This Attachment pertains only to the provision of network interconnection where ComSouth TWTC owns, leases from a third party or otherwise provides its own switch(es). 3.2 Network interconnection may be provided by the Parties at any technically feasible point within BellSouth’s network. Requests to BellSouth for interconnection at points other than as set forth in this Attachment may be made through the Bona Fide Request/New Business Request (BFR/NBR) Process process set forth out in Attachment 11this Agreement. 3.2.1 Each Party is responsible for providing, engineering and maintaining the network on its side of the IP. The IP must be located within BellSouth’s serving territory in the LATA in which traffic is originating. The IP determines the point at which the originating Party shall pay the terminating Party for the Call Transport and Termination of Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic. In selecting the IP, both Parties will act in good faith and select the point that is most efficient for both Parties. 3.2.2 Pursuant to the provisions of this Attachment, the location of the initial IP in a given LATA shall be established by mutual agreement of the Parties. Subject to the requirements for installing additional IPs, as set forth below, any IPs existing prior to the Effective Date of the Agreement will be accepted as initial IPs and will not require re-grooming. When the Parties mutually agree to utilize two-way interconnection trunk groups for the exchange of Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic between each other, the Parties shall mutually agree to the location of IP(s). If the Parties are unable to agree to a mutual initial IP, each Party, as originating Party, shall establish a single IP in the LATA for the delivery of its originated Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic to the other Party for Call Transport and Termination by the terminating Party. 3.2.3 Additional IP(s) in a LATA may be established by mutual agreement of the Parties. Notwithstanding the foregoing, additional IP(s) in a particular LATA shall be established, at the request of either Party, when the Local Traffic and ISP-Bound Traffic exceeds eight point nine (8.9) million minutes per month for three (3) consecutive months at the proposed location of the additional IP. BellSouth will not request the establishment of an IP in a BellSouth Central Office where physical or virtual collocation space is not available or where BellSouth fiber connectivity is not available. When the Parties agree to utilize two-way interconnection trunk groups for the exchange of Local Traffic, ISP-Bound Traffic and IntraLATA Toll Traffic the Parties must agree to the location of the IP(s).