White Pages Directory Listings Requirements Sample Clauses

The White Pages Directory Listings Requirements clause sets out the obligations for including a business or individual's contact information in a public directory, such as a phone book or online listing. Typically, this clause specifies the format, accuracy, and frequency of updates required for the listings, and may outline procedures for requesting changes or removals. Its core function is to ensure that directory information remains current and reliable, thereby facilitating effective communication and minimizing confusion for users seeking contact details.
White Pages Directory Listings Requirements. 8. Local Dialing Parity . 9. Court Ordered Requests for Call Detail Records and Other Subscriber Information 10. Liability and Indemnification 11. Intellectual Property Rights and Indemnification 12. Proprietary and Confidential Information 13. Resolution of Disputes 14. Taxes 15. Network Maintenance and Management 16. Force Majeure 17. Modification of Agreement 18. Non-Waiver of Legal Rights 19. One Agreement 20. Severability 21. No Waiver 22. Governing Law 23. Assignments 24. Notices 25. Rule of Construction 26. Headings of No Force or Effect 27. Cooperation in Preventing Customer Fraud 28. Revenue Protection 29. Law Enforcement Interface 30. Multiple Counterparts 31. Filing of Agreement 32. Compliance with Applicable Law 33. Necessary Approvals 34. Good Faith Performance 35. Independent Contracting Parties 36. Subcontracting 37. Labor Relations 38. Compliance with the Communications Assistance for Law Enforcement Act of 1994 (“CALEA”) 39. Customer Inquiries 40. Additional Fair Competition Requirements 41. Posting of Agreements 42. Nonexclusive Dealings 43. Rate True-Up 44. Survival 45. Entire Agreement Attachment 1 - Resale Attachment 2 - Network Elements and Other Services Attachment 3 - Network Interconnection Attachment 4 - Collocation Attachment 5 - Access to Numbers and Number Portability Attachment 6 - Pre-Ordering, Ordering, Provisioning, Maintenance and Repair Attachment 7 - Billing Attachment 8 - Rights-of-Way, Conduits and Pole Attachments Attachment 9 - Performance Measurements and Associated Remedies Attachment 10 - AT&T Disaster Recovery Plan Attachment 11 - Bona Fide Request and New Business Request Process SE Region Pricing Schedule THIS agreement (Agreement) is made by and between AT&T Telecommunications, Inc., (“AT&T”), a Georgia corporation, and NuVox Communications, Inc. dba NuVox (“NuVox”), a Delaware corporation, and shall be effective on the Effective Date, as defined herein. This Agreement may refer to either AT&T or NuVox or both as a “Party” or “Parties.”
View SourceView Similar (6)
White Pages Directory Listings Requirements. Local Dialing Parity .
View Source
White Pages Directory Listings Requirements 
View Source

Related to White Pages Directory Listings Requirements

  • Directory Listings 15.1.1 CBT, as publisher of its White Pages, will include Primary Listings of CLEC’s resale directory customers in its White Pages, and shall cause its publisher to include primary listings of CLEC’s directory customers in its Publisher’s Yellow Pages Directories under the following terms and conditions: 15.1.1.1 CBT will publish the Primary Listing of CLEC Directory Customers located within the geographic scope of its White Pages directory and will recover costs for both resale and facility based Customers in accordance with the Act.

  • White Pages Listings 5.1 BellSouth shall provide <<customer_name>> and their customers access to white pages directory listings under the following terms:

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.

  • Proposed Policies and Procedures Regarding New Online Content and Functionality By February 1, 2017, the Division will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the Division to provide equally effective alternative access. The Plan for New Content will require the Division, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternatives are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the Division online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the Division will officially adopt and fully implement the amended policies and procedures.

  • 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 §§▇▇-▇▇▇-▇▇▇, ▇▇-▇▇▇-▇▇▇, ▇▇-▇▇▇-▇▇▇, and ▇▇- ▇▇▇-▇▇▇, 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.