Directory Number Sample Clauses

Directory Number. “Directory Number” is a phone number assigned to a specific phone or voice endpoint.
Sample 1
AutoNDA by SimpleDocs
Directory Number. (DN) A dialable 10-digit telephone number associated with a telephone subscriber or call destination. Disaster Any event which can cause a significant disruption to emergency calling capability. Disaster Recovery A specific set of procedures designed to reduce the damaging consequences of unexpected events resulting in the loss of 9-1-1 capabilities. Discrepancies A Service Provider term used to describe subscriber records that do not match the MSAG and are referred to an error file or report for resolution. Discrete Multi Tone (DMT) The transmission medium for ADSL. Term Definition N)ew U)pdate Disk Operating System (DOS) A personal computer operating system which manages the computer’s resources. Diverse Routing The practice of routing circuits along different physical paths in order to prevent total loss of 9-1-1 service in the event of a facility failure.
Sample 1
Directory Number. Route Indexing (DNRI) DNRI permits incoming calls to be ported to the INP Requestor's Switch via a route index. A permanent route index is assigned to the end user's ported number in the INP Provider's Switch. The INP Provider will deliver the dialed seven digit telephone number to the INP requestor’s central office. INP Requestor may terminate the call as desired. Additional capacity for simultaneous call forwarding is available where technically feasible. The INP Requestor will need to specify the number of simultaneous calls to be forwarded for each number ported. DNRI tandem routing requires an additional thirty
Sample 1

Related to Directory Number

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

  • Contact Numbers The Parties agree to provide one another with toll-free nation- wide (50 states) contact numbers for the purpose of ordering, provisioning and maintenance of services.

  • Print Name Designation ...................................

  • 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

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

  • Place of Business; Name The Borrower will not transfer its chief executive office or principal place of business, or move, relocate, close or sell any business location. The Borrower will not permit any tangible Collateral or any records pertaining to the Collateral to be located in any state or area in which, in the event of such location, a financing statement covering such Collateral would be required to be, but has not in fact been, filed in order to perfect the Security Interest. The Borrower will not change its name or jurisdiction of organization.

  • Corporate Name No Borrower has been known by any other corporate name in the past five years and does not sell Inventory under any other name except as set forth on Schedule 5.6, nor has any Borrower been the surviving corporation of a merger or consolidation or acquired all or substantially all of the assets of any Person during the preceding five (5) years.

  • Project Number The project number has been assigned by the Commission as the unique identifier for your project, and it cannot be changed. The project number should appear on each page of the grant agreement preparation documents to prevent errors during its handling.

  • Name; Location of Chief Executive Office Except as disclosed in the Schedule, Borrower has not done business under any name other than that specified on the signature page hereof. The chief executive office of Borrower is located at the address indicated in Section 10 hereof.

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