Directory Listings and Directory Sample Clauses

Directory Listings and Directory. Distribution I-9 8.1 Listings...................................................................................................................VIII-9 8.2 Distribution...........................................................................................................VIII-10 9. Busy Line Verification and Busy Line Verification Interrupt X-00
AutoNDA by SimpleDocs

Related to Directory Listings and Directory

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

  • 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

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

  • Routing for Operator Services and Directory Assistance Traffic For a Verizon Telecommunications Service dial tone line purchased by MLTC for resale pursuant to the Resale Attachment, upon request by MLTC, Verizon will establish an arrangement that will permit MLTC to route the MLTC Customer’s calls for operator and directory assistance services to a provider of operator and directory assistance services selected by MLTC. Verizon will provide this routing arrangement in accordance with, but only to the extent required by, Applicable Law. Verizon will provide this routing arrangement pursuant to an appropriate written request submitted by MLTC and a mutually agreed-upon schedule. This routing arrangement will be implemented at MLTC's expense, with charges determined on an individual case basis. In addition to charges for initially establishing the routing arrangement, MLTC will be responsible for ongoing monthly and/or usage charges for the routing arrangement. MLTC shall arrange, at its own expense, the trunking and other facilities required to transport traffic to MLTC’s selected provider of operator and directory assistance services.

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

  • Directory Assistance Service shall provide up to two listing requests per call, if available and if requested by Freedom's End User. BellSouth shall provide caller- optional directory assistance call completion service at rates set forth in BellSouth's General Subscriber Services Tariff to one of the provided listings.

  • 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 Assistance Service 8.3.1 Directory Assistance Service provides local end user telephone number listings with the option to complete the call at the caller's direction separate and distinct from local switching.

  • Branding for Operator Call Processing and Directory Assistance 8.4.1 BellSouth's branding feature provides a definable announcement to Telepak Networks end users using Directory Assistance (DA)/ Operator Call Processing (OCP) prior to placing such end users in queue or connecting them to an available operator or automated operator system. This feature allows Telepak Networks’ name on whose behalf BellSouth is providing Directory Assistance and/or Operator Call Processing. Rates for the branding features are set forth in Exhibit D.

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

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