Call Detail Records; End-User DataBase Access Sample Clauses

Call Detail Records; End-User DataBase Access. 1. If Eschelon requires call detail records (“CDR”) for the Services it has the option of (i) receiving CDR on a monthly basis via CD-ROM or magnetic tape (“CDR Tape”), and/or (ii) receiving CDR on a daily basis via electronic data exchange, which may include dial-in remote access, on-line access via the Internet or such other method made available by Global Crossing (collectively, “Electronic Exchange”). CDR must be rated by Eschelon at its rates in order for it to xxxx its End-Users. 2. If Eschelon elects option 1. (i), then on or about the fifth Business Day following the end of a Billing Cycle, Global Crossing will deposit with an overnight delivery service for delivery to Eschelon a CDR Tape for the media selected by Eschelon in the format established by Global Crossing. 3. If Eschelon elects option 1. (ii), then Global Crossing will make CDR available to Eschelon on a daily basis via the Electronic Exchange method available from Global Crossing as selected by Eschelon. Eschelon is liable for all transmission charges as well as the cost of hardware and software compatible with Global Crossing’s systems as necessary for its use of Electronic Exchange. 4. Electronic Exchange will provide Eschelon with access to its End-User information and records resident on certain of Global Crossing’s systems. Such access will allow Eschelon to add and delete ANIs, Toll-Free Numbers, Codes and PIN Numbers, as well as to terminate accounts and check trouble ticket status and history. Eschelon agrees to comply with the following acceptable use policies, procedures and security measures for Eschelon’s use of Electronic Exchange. Global Crossing reserves the right to immediately discontinue Eschelon’s Electronic Exchange access if Global Crossing determines in its reasonable business judgment that Eschelon is using Electronic Exchange or information obtained therefrom in a manner detrimental to Global Crossing or in violation of said policies, procedures or security measures or the confidentiality provisions of this Agreement.
Sample 1
AutoNDA by SimpleDocs

Related to Call Detail Records; End-User DataBase Access

  • Data Use Each party may use Connected Account Data in accordance with this Agreement and the consent (if any) each obtains from each Connected Account. This consent includes, as to Stripe, consent it receives via the Connected Account Agreement.

  • Data Storage Where required by applicable law, Student Data shall be stored within the United States. Upon request of the LEA, Provider will provide a list of the locations where Student Data is stored.

  • Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.

  • User Data We will maintain certain data that you transmit to the Services for the purpose of managing the performance of the Services, as well as data relating to your use of the Services. Although we perform regular routine backups of data, you are solely responsible for all data that you transmit or that relates to any activity you have undertaken using the Services. You agree that we shall have no liability to you for any loss or corruption of any such data, and you hereby waive any right of action against us arising from any such loss or corruption of such data.

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.

  • Client Records 25.2.1 CONTRACTOR shall prepare and maintain accurate and 26 complete records of clients served and dates and type of services provided 27 under the terms of this Agreement in a form acceptable to ADMINISTRATOR.

  • Data Location 1.1. The CONTRACTOR shall not store or transfer non-public COUNTY data outside of the United States. This includes backup data and Disaster Recovery locations. The CONTRACTOR will permit its personnel and contractors to access COUNTY data remotely only as required to provide technical support. (Remote access to data from outside the continental United States is prohibited unless approved in advance and in writing by the County.) 1.2. The CONTRACTOR must notify the COUNTY in advance and in writing of any location changes to CONTRACTOR’s data center(s) that will process or store County data.

  • Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

  • Information Access Each Party (“Disclosing Party”) shall make available to another Party (“Requesting Party”) information that is in the possession of the Disclosing Party and is necessary in order for the Requesting Party to: (i) verify the costs incurred by the Disclosing Party for which the Requesting Party is responsible under this Agreement; and (ii) carry out its obligations and responsibilities under this Agreement. The Parties shall not use such information for purposes other than those set forth in this Article 25.1 of this Agreement and to enforce their rights under this Agreement.

  • Access to Data Operator shall make Data in the possession of the Operator available to the LEA within five (5) business days of a request by the LEA.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!