Network Connections. 3.1 In each exchange area in which either Party wishes to exchange traffic with the other Party’s End Users and/or utilize the other Party’s facilities for a transiting function, each Party, at a minimum, will:
3.1.1 Route such traffic via direct network facilities to either a) each others access and local tandem(s) or End Offices (upon mutual agreement of the parties), meeting the other Party’s facilities at the existing Exchange Area Boundary (EAB) (see section 3.2.2 for exclusions); or b) another mutually agreed upon point.
3.1.1.1 Specific facility arrangements required to interconnect the Parties’ networks shall be negotiated by the Parties’. Where the LEC providing FX-NXX service, also operates as a CLEC within SBC ILEC exchange, and whose switch is located in the SBC ILEC exchange; the existing interconnection facility between the parties’ within the SBC ILEC exchange may be considered as an option for interconnection, provided a separate and distinct portion of this existing facility can be established as further defined below in section 3.5.
3.1.1.2 For FX-NXX service, the interconnection facilities and trunks between the Parties’ networks shall only be used for traffic exchanged between the Parties’. No Third Party traffic shall be routed over these facilities, except where ICG is unable to interconnect with Rural/Independent Telecommunications Carriers (or any other “exempted” carriers). Notwithstanding this exception, ICG will exert reasonable effort to interconnect with such Carriers.
3.1.2 Route such traffic to the other Party utilizing a Third Party incumbent LECs facilities and/or utilizing another Third Party Telecommunications Carrier’s facilities with whom the Party already has an agreement for exchanging like traffic. The Parties acknowledge and agree that this option may not be implemented without the written agreement of the Third Party incumbent LEC and/or Telecommunications Carrier as well as the mutual consent of each of the Parties. The Parties further agree that in order for this option to be considered, it is the responsibility of the originating Party to obtain the required written permission from the Third Party incumbent LEC and/or Telecommunications Carrier.
3.2 The Parties acknowledge and agree that when traffic destined for an SBC ILEC tandem exceeds a DS1’s amount of traffic and/or that it is more efficient to connect via direct End Office connections, ICG shall establish a direct End Office trunk group and provide transp...
Network Connections. 3.1 In each exchange area in which either Party wishes to exchange traffic with the other Party’s End Users and/or utilize the other Party’s facilities for a transiting function, each Party, at a minimum, will:
3.1.1 Route such traffic via direct network facilities to either a) each others access and local tandem(s) or End Offices (upon mutual agreement of the parties), meeting the other Party’s facilities at the existing Exchange Area Boundary (EAB) (see section 3.2.2 for exclusions); or
Network Connections. If a network connection is established between Shopify Systems and the computing environment(s) used by Affirm or Affirm Personnel in connection with this Agreement or the Program, Affirm agrees, for itself and all Affirm Personnel, to maintain an alert status regarding the security of such computing environments, including all vulnerabilities and security patches or corrective actions, by subscribing to an industry recognized service. Affirm understands that, should a Shopify review reveal any non-compliance with the Security Measures, Shopify may, in addition to other remedies it may have, remove access by Affirm Personnel to Shopify Systems until Affirm Personnel satisfactorily comply with the Security Measures.
Network Connections. If a network connection is established between Xxxxx Fargo and the computing environment(s) used by Vendor or Vendor Personnel to perform the Program Development Services, Vendor agrees, for itself and all Vendor Personnel, to (1) allow Xxxxx Fargo to perform network assessments of such computing environment(s) based on a mutually-agreed schedule, and (2) maintain an alert status regarding the security of such computing environments, including without limitation all vulnerabilities and security patches or corrective actions, by subscribing to an industry-recognized service, such as CERT or CIAC. Vendor understands that, should a Xxxxx Fargo assessment reveal inappropriate or inadequate security based on the pre-defined requirements for security, Xxxxx Fargo may, in addition to other remedies it may have, remove access by Vendor Personnel to the Xxxxx Fargo network until Vendor Personnel satisfactorily comply with the security requirements defined.
Network Connections. The user agrees that they will be responsible for providing, maintaining, and supporting a connection to the Xxx.xxx system via the Internet. The system administrator will be responsible for providing, maintaining, and supporting the Xxx.xxx system and its connection to the Internet.
Network Connections. [Name of Staff Member] agrees to pay any telephone or telecommunications charges incurred in connecting the loaned devices to private or public networks or the internet, except in the case of connection to the Local Area Network of any Trust in connection with professional duties.[Name of Staff Member] understands that the supply and use of consumables used at home are the staff member’s responsibility.
Network Connections. 1. UMD, at its sole cost and expense, will provide the County with a i. Ten-Gigabit Ethernet port, owned by UMD, to the County-owned networking equipment located in the NOC. The County shall have at all times full control of the port, which may be used and changed as determined by the County. Additionally, at no cost to the County, UMD shall provide the County with:
a. MAX Layer 3 IP routing which shall include the following:
i. Layer 2 Ethernet services;
ii. A One-Gigabit Layer 2 VLAN to Amazon Web Services (“AWS”) via the MAX AWS Direct Connect Service; and,
iii. Access to Internet2 as well as other Layer 3 routes on the MAX network. County is responsible for fees charged by Internet2 and other organizations to access their infrastructure.
2. Primary internet service to the County is not offered by UMD as part of this MOU. If the County desires connections to services other than those described in subsection C.1 above, then the County will pay for such services, and corresponding connections to obtain such services. The County will be required to pay for any connection or service fees charged to the County by any service providers for the County to obtain services from such providers.
3. UMD shall not be liable to the County for any non-UMD activity associated with the County’s Amazon and Cloud user accounts for the AWS connection through AWS Direct Connect.
Network Connections. 3.1 In each exchange area in which AMERITECH WISCONSIN or MH Telecom wishes to terminate traffic to the other Party’s End Users, AMERITECH WISCONSIN and MH Telecom at a minimum, will:
3.1.1 Route such traffic via direct network facilities to either a) each others access tandem(s), and/or each end office meeting the other Party’s facilities at the existing Exchange Area Boundary (EAB) or, b) another mutually agreed upon point.
3.1.2 Route such traffic to the other Party utilizing another ILECs facilities and/or utilizing another telecommunications carrier’s facilities with whom the Party already has an agreement for exchanging like traffic. The Parties acknowledge and agree that this option would not be implemented without the written agreement of the ILECs and/or other telecommunications carrier as well as the mutual consent of each of the Parties. The Parties further agree that in order for this option to be considered, it is the responsibility of the originating Party to obtain the required written permission from the ILECs and/or other telecommunications carrier.
3.2 The Parties have already conducted joint planning and forecasting meetings.
3.3 The Parties agree that if either Party establishes additional tandems in an exchange, the other Party may also connect to the additional tandems.
3.4 Neither Party shall deliver traffic destined to terminate at the other Party’s end office via another LEC’s end office.
3.5 Connection to a Party’s local tandem(s) will provide the connecting Party local accessibility to a Party’s end offices and NXXs which subtend that tandem(s), and to other LECs which are connected to that tandem(s). Connection to a Party’s end office(s) will provide the connecting Party accessibility only to the NXXs served by that individual end office(s) to which the connecting Party interconnects.
Network Connections. 4.1 In each exchange area in which either Party wishes to exchange traffic with the other Party’s End Users, each Party, at a minimum, will:
4.1.1 Route such traffic via direct network facilities to either a) each other’s access and local tandem(s) or End Offices (upon mutual agreement of the parties), meeting the other Party’s facilities at the existing Exchange Area Boundary (EAB) (see Section 4.2.2 for exclusions); or b) another mutually agreed upon point. .
4.1.1.1 For FX-NXX service, the interconnection facilities and trunks between the Parties’ networks shall only be used for traffic exchanged between the Parties’. No Third Party traffic shall be routed over these facilities.
4.2 Except as otherwise provided in this Agreement, the Parties understand and agree that either Party, upon ten (10) days notice to the other Party where regulatory environment permits, may block any traffic that is improperly routed over any trunk groups and/or which is routed outside of the mutual agreement of the Parties.
4.3 AT&T-21STATE shall not compensate any Third Party Incumbent Carrier and/or Telecommunications Carrier for Local, EAS, Toll, IXC or any other traffic that is inappropriately routed to AT&T-21STATE (as reflected in the LERG). Any compensation due AT&T-21STATE for such misrouted traffic shall be paid by ILEC, unless otherwise agreed to in writing by both Parties. The appropriateness of such routing and the correct AT&T-21STATE serving tandems are reflected by AT&T-21STATE in the LERG. This also includes traffic that is destined to End Offices that do not subtend AT&T-21STATE tandem.
4.4 Within thirty (30) days from the Effective Date of this Agreement, the Parties agree to have met and developed joint planning and forecasting responsibilities which are applicable to services described in this Agreement, if necessary. Either Party may delay processing the other Party’s service orders should the Parties not perform obligations as specified in this Section. Such responsibilities shall include but are not limited to the following:
4.4.1 The Parties will establish periodic reviews of network and technology plans and will notify one another no later than six (6) months in advance of changes that would impact either Party’s provision of services.
4.4.2 The Parties will furnish to each other, information that provides for state-wide annual forecasts of order activity, in-service quantity forecasts, and facility/demand forecasts.
4.4.3 The Parties will develop join...
Network Connections. Although Contractor will provide some guidance and direction, Contractor is not responsible for resolving problems relating to networks. It is the County's responsibility to keep adequate back-ups. Contractor is not responsible for loss of data.
