Common use of Mid-Point Meet Clause in Contracts

Mid-Point Meet. Using the Mid-Point Meet architecture, the Parties will agree upon a Network Interconnection Point (NIP). The NIP functions as a demarcation point for each Party. Each Party is responsible to transport all trunking to its side of the NIP utilizing any method of interconnection described in Section 4.3 above. Each Party is responsible for the appropriate sizing, operation, and maintenance of the transport facility and trunking to the NIP. 4.4.2.1 A second NIP can be established to eliminate a "single point of failure" when mutually agreed upon. The establishment of the second NIP should not require additional or increased trunking or facilities of either Party. Trunking from the initial NIP will be groomed or augmented to the second NIP upon mutual agreement. 4.4.2.2 When required, based on guidelines established pursuant to Appendix ITR, either Party may trunk directly to the other Party's EO. If the Party is virtually or physically collocated to the EO, then that collocation will be designated a NIP. This collocation will be used for the transport of direct EO trunking, in addition to other uses. The collocated Party is responsible for the appropriate sizing, operation, and maintenance of the transport facility. In the instance where the Party is not collocated, the EO trunk group will be handed off at the original NIP and both Parties will be responsible for the transport facility on their side of that NIP. 4.4.2.3 Unless otherwise mutually agreed upon, when Mid-Point Meet architecture has been deployed, it will remain as the architecture of choice during the term of this Agreement.

Mid-Point Meet. Using the Mid-Point Meet architecture, the Parties will agree upon a Network Interconnection Point (NIP). The NIP functions as a demarcation point for each Party. Each Party is responsible to transport all trunking to its side of the NIP utilizing any method of interconnection described in Section 4.3 above. Each Party is responsible for the appropriate sizing, operation, and maintenance of the transport facility and trunking to the NIP. 4.4.2.1 A second NIP can be established to eliminate a "single point of failure" when mutually agreed upon. The establishment of the second NIP should not require additional or increased trunking or facilities of either Party. Trunking from the initial NIP will be groomed or augmented to the second NIP upon mutual agreement.. GENERAL TERMS AND CONDITIONS PAGE 16 OF 52 SWBT/Optel J130 4.4.2.2 When required, based on guidelines established pursuant to Appendix ITR, either Party may trunk directly to the other Party's EO. If the Party is virtually or physically collocated to the EO, then that collocation will be designated a NIP. This collocation will be used for the transport of direct EO trunking, in addition to other uses. The collocated Party is responsible for the appropriate sizing, operation, and maintenance of the transport facility. In the instance where the Party is not collocated, the EO trunk group will be handed off at the original NIP and both Parties will be responsible for the transport facility on their side of that NIP. 4.4.2.3 Unless otherwise mutually agreed upon, when Mid-Mid- Point Meet architecture has been deployed, it will remain as the architecture of choice during the term of this Agreement.