Directory Entry Sample Clauses

Directory Entry. New Directory entries can be ordered or Maintel can take over existing entries for imported numbers. It should be noted that the features listed are not guaranteed to be supported on every CPE platform connected to the SIP Trunk Service because of vendor interoperability issues. A list of approved vendors is available upon request.
AutoNDA by SimpleDocs

Related to Directory Entry

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

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

  • 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

  • Office Location During the Term, the Executive's services hereunder shall be performed at the offices of the Company, which shall be within a twenty five (25) mile radius of New York, NY, subject to necessary travel requirements to the Company’s offices in Toronto, Canada and other MDC Group company locations in order to carry out his duties in connection with his position hereunder.

  • Directory Assistance 72.1 The Parties acknowledge that CenturyLink is not a Directory Assistance (DA) provider. CenturyLink provides directory listings information for its subscribers to third party DA providers to be included in the national and local databases used by such third party providers. The Parties agree that to the extent the DA provider contracted by CLEC for DA services to CLEC’s subscribers also populates the national DA database, then CLEC’s DA listings have been made available to CenturyLink’s subscribers and no further effort is needed by either Party. If for any reason, CLEC desires that CenturyLink act as a middleman conduit for the placement of CLEC’s DA listings in the DA database(s), then CenturyLink shall provide such compensable DA listings service pursuant to separate written terms and conditions between CenturyLink and CLEC which will be attached to this Agreement as an Amendment.

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

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

  • Other Directory Services 73.10.1 Both parties acknowledge that CenturyLink’s directory publisher is not a party to this Agreement and that the provisions contained in this Agreement are not binding upon CenturyLink’s directory publisher. 73.10.2 CenturyLink agrees to include critical contact information pertaining to CLEC in the “Information Pages” of those of its White Pages directories containing information pages, if CLEC meets criteria established by its directory publisher. Critical contact information includes CLEC’s business office number, repair number, billing information number, and any other information required to comply with applicable regulations, but not advertising or purely promotional material. CLEC will not be charged for inclusion of its critical contact information. The format, content and appearance of CLEC’s critical contact information must conform to applicable directory publisher’s guidelines and will be consistent with the format, content and appearance of critical contact information pertaining to all CLECs in a directory. 73.10.3 The directory publisher shall maintain full authority as publisher over its publishing policies, standards and practices, including decisions regarding directory coverage area, directory issue period, compilation, headings, covers, design, content or format of directories, and directory advertising sales.

  • 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. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

  • Program Location A. Unless otherwise agreed upon in writing, the parties acknowledge and agree that the Work of this Agreement will be performed at the following Property address: Ktr Address1 Address2

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