White Pages Basic Directory Listings Sample Clauses

White Pages Basic Directory Listings. BellSouth shall publish in all BellSouth's white pages Directories at no charge to AT&T or any AT&T Customer one white pages basic Directory Listing for each AT&T Customer for all of such Customer’s phone numbers located in the geographic region covered by any white pages Directory. Notwithstanding the foregoing, BellSouth shall not publish any white pages basic Directory Listing for any AT&T Customer whose Directory Listing has been identified as non-published. AT&T will be required to provide to BellSouth the names, addresses and telephone numbers of all AT&T end users that wish to be omitted from directories.
AutoNDA by SimpleDocs
White Pages Basic Directory Listings. BellSouth shall publish in all BellSouth's white pages Directories at no charge to TCG or any TCG Customer one white pages basic Directory Listing for each TCG Customer for all of such Customer’s phone numbers located in the geographic region covered by any white pages Directory. Notwithstanding the foregoing, BellSouth shall not publish any white pages basic Directory Listing for any TCG Customer whose Directory Listing has been identified as non-published. TCG will be required to provide to BellSouth the names, addresses and telephone numbers of all TCG end users that wish to be omitted from directories.

Related to White Pages Basic Directory Listings

  • 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:

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

  • Directory Listing and Directory Distribution 41 5. Voice Information Service Traffic 43 6. Intercept and Referral Announcements 44 7. Originating Line Number Screening (OLNS) 44 8. Operations Support Systems (OSS) Services 44 9. Poles, Ducts, Conduits and Xxxxxx-xx-Xxx 00 00. Telephone Numbers 51 11. Routing for Operator Services and Directory Assistance Traffic 51 12. Unauthorized Carrier Change Charges 52 13. Good Faith Performance 52 INTERCONNECTION ATTACHMENT. 53 1. General 53 2. Points of Interconnection and Trunk Types 53 3. Alternative Interconnection Arrangements 57 4. Initiating Interconnection 58 5. Transmission and Routing of Telephone Exchange Service Traffic 59

  • Red Hat Directory Server Use Cases Subscription Services are provided for Red Hat Directory Server only when used for its supported Use Case in accordance with the terms of this Exhibit and Table 3.1 below.

  • Directory To participate in the MnDOT TGB program, a business must be certified at the time of contract execution. Certified Targeted Group Businesses are listed in the Directory of Certified Targeted Group, Economically Disadvantaged and VET Vendors. MnDOT makes no representation as to any TGB’s technical or financial ability to perform the work. Prime contractors are solely responsible for performing due diligence in hiring TGB firms. A TGB’s failure to perform the work will not be considered justification for a compensation increase or time extension.

  • Directories BellSouth or its agent shall make available White Pages directories to <<customer_name>> subscribers at no charge or as specified in a separate BAPCO agreement.

  • Links If The Services are made available through the Internet, the Financial Institution’s website may provide links to other websites, including those of Third Parties who may also provide services to You. You acknowledge that all those other websites and Third Party services are independent from the Financial Institution’s and may be subject to separate agreements that govern their use. The Financial Institution and Central 1 have no liability for those other websites or their contents or the use of Third Party services. Links are provided for convenience only, and You assume all risk resulting from accessing or using such other websites or Third Party services.

  • Directory Publication Nothing in this Agreement shall require Verizon to publish a directory where it would not otherwise do so.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry.

  • Network Access TENANT may find it necessary to purchase a network interface card, wireless PC card or other hardware in order to connect to the internet service. LANDLORD is not responsible for the purchase of these items and LANDLORD cannot guarantee compatibility with any device TENANT may have. The computer and network card must have software installed that supports the Internet Protocol commonly referred to as TCP/IP. Any conflicts between the software compatibility of the network and the TENANT’S computer operating system or any other feature will be the responsibility of the TENANT to resolve. LANDLORD will not be responsible for software issues related to the user’s personal computer.

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