Requesting Carrier Sample Clauses

Requesting Carrier will monitor the 9-1-1 circuits for the purpose of determining originating network traffic volumes. Requesting Carrier will notify Ameritech if the traffic study information indicates that additional circuits are required to meet the current level of 9-1-1 call volumes.
Sample 1Sample 2Sample 3See All (12)
AutoNDA by SimpleDocs
Requesting Carrier and Ameritech shall work cooperatively to install and maintain a reliable network. Requesting Carrier and Ameritech shall exchange appropriate information (e.g., maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government and such other information as the Parties shall mutually agree) to achieve this desired reliability.
Sample 1Sample 2Sample 3See All (7)
Requesting Carrier grants to Ameritech during the Term a non-exclusive, license to use the DA listings provided pursuant to this Agreement. DA listings provided to Ameritech by Requesting Carrier under this Agreement will be maintained by Ameritech only for purposes of providing DA information to Requesting Carrier Customers, and will not be disclosed to third parties. This section does not prohibit Ameritech and Requesting Carrier from entering into a separate agreement which would allow Ameritech to provide or sell Requesting Carrier’s DA listing information to third parties, but such provision or sale would only occur under the terms and conditions of the separate agreement.
Sample 1
Requesting Carrier shall provide, at a minimum, the following information with respect to each piece of equipment it intends to Collocate in Ameritech’s Premises: (1) Name of Hardware and Software Manufacturer; (2) Model and Release Number; and (3) Third-party certification by an independent qualified testing facility and any necessary documentation that evidences compliance with the standards set forth in Section 12.4.2. Ameritech will review and confirm or deny Requesting Carrier’s list and description of equipment within ten
Sample 1
Requesting Carrier and Ameritech shall work cooperatively to apply sound network management principles by invoking network management controls to alleviate or to prevent congestion. III.8 9-1-1 Service. III.8.1 Ameritech shall provide 9-1-1 Service to Requesting Carrier as described in this Section 3.9 in each Rate Center in which (i) Requesting Carrier is authorized to provide local Telephone Exchange Service and (ii) Ameritech is the 9-1-1 service provider.
Sample 1
Requesting Carrier shall access Ameritech’s Interoffice Transmission Facilities via Collocation or any technically feasible method pursuant to Section 2.2 of Schedule 9.5 at the Ameritech Central Office where that element exists and each DSX or OCN circuit will be delivered to Requesting Carrier’s Collocation space for an additional charge by means of a Cross-Connection, Requesting Carrier shall order Interoffice Transmission Facilities from Ameritech by delivering to Ameritech a valid and complete service order via an electronic Access Services Request interface. If after the Effective Date Ameritech makes available the ability to order Interoffice Transmission Facilities via the Provisioning EI. Requesting Carrier agrees to transition its ordering of such facilities from ASR to the Provisioning EI within thirty (30) days after Ameritech is capable of receiving such orders via Provisioning EI.
Sample 1
Requesting Carrier. If utilizing Ameritech's database to perform the query function, Ameritech will xxxx the Requesting Carrier (or the Initial Billing Company (as defined in the MECAB)) for the query charges at Ameritech's tariffed rate.
Sample 1
AutoNDA by SimpleDocs
Requesting Carrier shall establish the Provisioning El on or before the Service Start Date so that it will submit all requests for CSRs and all orders for LNP through Ameritech's Provisioning EI. Ameritech shall have no obligation to accept manual or faxed requests for CSRs or provision any manual or faxed LNP Orders except as set forth in Section 10,13.2(b). ------------------
Sample 1
Requesting Carrier shall provide its Requesting Carrier Directory Customer Listings to Ameritech or its Publisher in a form and format acceptable to Ameritech or its Publisher. Requesting Carrier acknowledges that Ameritech or its Publisher may impose a charge for changes to Requesting Carrier Directory Customer Listings previously provided by Requesting Carrier to Ameritech or its Publisher.
Sample 1

Related to Requesting Carrier

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

  • Listing Application If shares of any class of stock of the Company shall be listed on a national securities exchange, the Company shall, at its expense, include in its listing application all of the shares of the listed class then owned by any Investor.

  • Ineligibility to Use Form S-3 In the event that Form S-3 is not available for the registration of the resale of Registrable Securities hereunder, the Company shall (i) register the resale of the Registrable Securities on Form S-1 or another appropriate form reasonably acceptable to the Required Holders and (ii) undertake to register the resale of the Registrable Securities on Form S-3 as soon as such form is available, provided that the Company shall maintain the effectiveness of all Registration Statements then in effect until such time as a Registration Statement on Form S-3 covering the resale of all the Registrable Securities has been declared effective by the SEC and the prospectus contained therein is available for use.

  • Eligibility to use Form S-3 The conditions for use of Form S-3, in connection with the offer and sale of the Securities, as set forth in the General Instructions thereto, have been satisfied.

  • AGREED FACTS Registration History 7. Since June 2006, the Respondent has been registered in Ontario as a mutual fund salesperson (now known as a dealing representative)1 with WFG Securities Inc. (the “Member”), a Member of the MFDA. 8. At all material times, the Respondent conducted business in the Vaughan, Ontario area. 9. At all material times, the Member’s policies and procedures prohibited Approved Persons from signing a client’s name to a document. 10. Between January 2018 and September 2018, while the Respondent was an Approved Person of the Member, the Respondent signed the initials of clients on 8 trade tickets next to alterations he made to information on the trade tickets, and submitted them to the Member for processing. 11. The alterations made by the Respondent on the trade tickets included alterations to: trade instructions, client signature dates and special instructions. 12. At all material times, the Member’s policies and procedures prohibited Approved Persons from altering information on a signed document without the client initialing the document to show that the changes were approved. 13. In May 2018, while the Respondent was an Approved Person of the Member, he altered 1 account form in respect of 1 client by altering information on a trade ticket without having the client initial the alterations, and used this altered form to process a transaction. 1 In September 2009, the registration category mutual fund salesperson was changed to “dealing representative” when National Instrument 31-103 came into force. 14. The Respondent altered the trading instructions, special instructions and representative commission percentage on the trade ticket without having the client initial these alterations. 15. At all material times, the Member’s policies and procedures prohibited Approved Persons from holding an account form which was signed by a client and was blank or only partially completed. 16. Between January 2015 and October 2018, while the Respondent was an Approved Person of the Member, he obtained, possessed and used to process transactions, 30 pre-signed account forms in respect of 21 clients. 17. The pre-signed account forms consisted of: 25 Trade Tickets, 3 New Account Application Forms and 2 Non Financial Information Update Forms.

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • Listing Approval The Shares to be delivered on the Closing Date or any Additional Closing Date, as the case may be, shall have been approved for listing on the Exchange, subject to official notice of issuance. If (i) any of the conditions specified in this Section 5 shall not have been fulfilled when and as provided in this Agreement, or (ii) any of the opinions and certificates mentioned above or elsewhere in this Agreement shall not be reasonably satisfactory in form and substance to the Representative and its counsel, this Agreement and all obligations of the Underwriters hereunder may be cancelled on, or at any time prior to, the Closing Date or any Additional Closing Date, as the case may be, by the Representative. Notice of such cancellation shall be given to the Company in writing or by telephone or facsimile confirmed in writing.

  • Designated Record Set “Designated Record Set” shall have the same meaning as the term “designated record set” in Section 164.501.

  • Data Universal Number System (DUNS) number Requirement Grantee will provide their valid DUNS number contemporaneous with execution of this Agreement.

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