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.
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.
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.
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.
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). ------------------
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.
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.
AutoNDA by SimpleDocs
Requesting Carrier and Ameritech shall work cooperatively to apply sound network management principles by invoking network management controls to alleviate or to prevent congestion.

Related to Requesting Carrier

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

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

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