Inclusion of MRC End Users in Directory Assistance Database. BellSouth will include and maintain MRC End User listings in BellSouth’s Directory Assistance databases. MRC shall provide such Directory Assistance listings to BellSouth at no charge.
Inclusion of MRC End Users in Directory Assistance Database Sample Clauses
Related to Inclusion of MRC End Users in Directory Assistance Database
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.
AIN Selective Carrier Routing for Operator Services, Directory Assistance and Repair Centers 4.3.1 BellSouth will provide AIN Selective Carrier Routing at the request of <<customer_name>>. AIN Selective Carrier Routing will provide <<customer_name>> with the capability of routing operator calls, 0+ and 0- and 0+ NPA (LNPA) 555-1212 directory assistance, 1+411 directory assistance and 611 repair center calls to pre-selected destinations.
Directory Assistance Service Updates 8.3.3.1 BellSouth shall update end user listings changes daily. These changes include:
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.
The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.
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.
Custom Branding for Directory Assistance (DA) is not available for certain classes of service, including but not limited to Hotel/Motel services, WATS service, and certain PBX services.
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.
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.
Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.
