911/E911 Traffic Sample Clauses

911/E911 Traffic. Each Party is solely responsible for the receipt and transmission of 911/E911 traffic originated by users of its Telephone Exchange Services. The Parties acknowledge and affirm that calls to 911/E911 services shall NOT be routed over the Traffic Exchange Trunk Groups or Access Toll Connecting Trunk Groups. To the extent that a Party incorrectly routes such traffic over such arrangements, that Party shall fully indemnify and hold harmless the other Party for any claims, including claims of third parties, related to such calls. The Parties’ full and exclusive interconnection responsibilities with respect to 911/E911 traffic are defined in Section 6.0 of the Agreement.
AutoNDA by SimpleDocs

Related to 911/E911 Traffic

  • Fire, Life Safety, and Accessibility Codes The following codes, in the versions approved by the Georgia State Fire Marshal/Fire Safety Commissioner and Department of Human Resources, shall be used. The Design Professional will designate any additional codes or special modifications in the Supplementary General Conditions.

  • Transit Traffic The following rates will apply:

  • Trunk Group Architecture and Traffic Routing The Parties shall jointly engineer and configure Local/IntraLATA Trunks over the physical Interconnection arrangements as follows:

  • Local Traffic Traffic that is originated by a Customer of one Party on that Party’s network and terminates to a Customer of the other Party on that other Party’s network within Verizon's then current local calling area (including non-optional local calling scope arrangements) as defined in Verizon’s effective Customer Tariffs. A non- optional local calling scope arrangement is an arrangement that provides Customers a local calling scope (Extended Area Service, “EAS”), beyond their basic exchange serving area. Local Traffic does not include optional local calling scope traffic (i.e., traffic that under an optional rate package chosen by the Customer terminates outside of the Customer’s basic exchange serving area). IntraLATA calls originated on a 1+ presubscription basis, or on a casual dialed (10XXX/101XXXX) basis are not considered Local Traffic. Local Traffic does not include any Internet Traffic.

  • Infrastructure Vulnerability Scanning Supplier will scan its internal environments (e.g., servers, network devices, etc.) related to Deliverables monthly and external environments related to Deliverables weekly. Supplier will have a defined process to address any findings but will ensure that any high-risk vulnerabilities are addressed within 30 days.

  • STATEWIDE CONTRACT MANAGEMENT SYSTEM If the maximum amount payable to Contractor under this Contract is $100,000 or greater, either on the Effective Date or at any time thereafter, this section shall apply. Contractor agrees to be governed by and comply with the provisions of §§00-000-000, 00-000-000, 00-000-000, and 00- 000-000, C.R.S. regarding the monitoring of vendor performance and the reporting of contract information in the State’s contract management system (“Contract Management System” or “CMS”). Contractor’s performance shall be subject to evaluation and review in accordance with the terms and conditions of this Contract, Colorado statutes governing CMS, and State Fiscal Rules and State Controller policies.

  • DELIVERY, STORAGE, AND HANDLING The Contractor shall be responsible to inspect all components on delivery to ensure that no damage occurred during shipping or handling for furnish and installation projects. For equipment only purchases, the ordering entity shall be responsible to inspect all components on delivery. Materials must be stored in original undamaged packaging in such a manner to ensure proper ventilation and drainage, and to protect against damage, weather, vandalism, and theft until ready for installation.

  • Exception Where Databases Contain Sufficient Information A Reporting Financial Institution is not required to perform the paper record search described in subparagraph D.2. of this section if the Reporting Financial Institution’s electronically searchable information includes the following:

  • SUBLOOPS 45.1. Sprint will offer unbundled access to copper subloops and subloops for access to multiunit premises wiring. Sprint will consider all requests for access to subloops through the ICB process due to the wide variety of interconnections available and the lack of standards. A written response will be provided to CLEC covering the interconnection time intervals, prices and other information based on the ICB process as set forth in this Agreement.

  • Internet Traffic Any traffic that is transmitted to or returned from the Internet at any point during the duration of the transmission.

Time is Money Join Law Insider Premium to draft better contracts faster.