MANNER OF PROVISIONING Sample Clauses

MANNER OF PROVISIONING. 3.1 The following describes the manner of provisioning for SS7 services. Each Party will work cooperatively with the other Party and will each provide knowledgeable personnel in order to provision, test and install SS7 Service in a timely fashion.
AutoNDA by SimpleDocs
MANNER OF PROVISIONING. 9.2.8.5.1 The following describes the manner of provisioning for SS7 services. Each Party will work cooperatively with the other Party and will each provide knowledgeable personnel in order to provision, test and install SS7 Service in a timely fashion.
MANNER OF PROVISIONING. 4.1 MCIm acknowledges that CCS/SS7 network overload due to extraordinary volumes of Queries and/or other SS7 network messages can and will have a detrimental effect on the performance of SBC ILLINOIS’s CCS/SS7 network. MCIm further agrees that SBC ILLINOIS, at its sole discretion, shall employ on a nondiscriminatory basis certain automatic and/or manual overload controls within SBC ILLINOIS’s CCS/SS7 network to guard against these detrimental effects. SBC ILLINOIS shall apply such management controls and it will be applied to the specific problem source in a nondiscriminatory manner, to the extent technically feasible.
MANNER OF PROVISIONING. (A) SWBT shall provide to LSP, on request, SWBT-specific documentation regarding record formatting and associated hardware requirements for LSP to access each of the interfaces SWBT provides for LIDB data administration. (B) LSP shall obtain, at its own expense, all necessary documentation produced by non-SWBT entities such as Bellcore. (C) Magnetic tapes submitted by LSP must conform to the hardware specifications of each SCP node where LIDB resides. This includes 9-track and 8mm tapes as well as other site-specific limitations. SWBT shall provide LSP with all magnetic tape hardware requirements upon request. LSP shall create the magnetic tapes its submits for input into LIDB and LVAS over the tape load interface. (D) SWBT shall input information provided by LSP into LIDB for the NPA-NXXs and/or NPA-RAOs set forth in Exhibit I, EXCHANGES TO BE ADMINISTERED, attached hereto and made a part hereof. LSP shall provide all information needed by SWBT to support the services being requested. This information may include, but is not limited to, Calling Card Service information, Toll Bill Xxxeption information (such as restrictions on collect and third number billing), class of service information, originating line number screening information, ZIP code information, and calling name information. (E) LSP shall furnish, prior to the initial LVAS load, and as requested by SWBT thereafter, the following forecast data: - the number of working lines per account group - the number of working line numbers to be established - the average number of monthly changes to these records - the number of busy hour queries, by query type - the number of annual queries by query type If SWBT, at its discretion, determines that it lacks adequate storage, or processing capability, prior to the initial loading of LSP information, SWBT shall notify LSP of its intent to not provide to LSP the Services under this Appendix and this Appendix will be void. (F) LSP shall furnish all line records and group records in a format required by SWBT to establish records in LIDB for all working line numbers, not just line numbers associated with calling card PIN or Toll Billing Exceptions (TBE). (G) LSP acknowledges that SWBT's LIDB is accessible by many telecommunications companies and that these telecommunications companies expect a high degree of accuracy in the response information provided to their queries. LSP shall administer its data in such a manner that SWBT's accuracy of response information ...
MANNER OF PROVISIONING. 4.1 SBC-12STATE will provide CLEC with the following forms of access to the SCE: 4.1.1 Option 1: CLEC personnel will operate SBC-12STATE's SCE terminals themselves. 4.1.2 Option 2: CLEC will develop service logic using a CLEC SCE platform that is compatible with SBC-13STATE's systems and will transfer the file to SBC-13STATE for testing and deployment. 4.1.3 Option 3: Any other form of access mutually agreed upon by the Parties. 4.2 For each service CLEC deploys on SBC-12STATE's AIN SCP, CLEC will provide complete service documentation to SBC-12STATE and will provide SBC-12STATE with updates to such documentation so that such documentation remains current at all times. SBC-13STATE will use such documentation for troubleshooting purposes, test planning, and all other activities needed to maintain the successful operation of SBC-13STATE's network for all customers, including End Users and other telecommunications carriers.
MANNER OF PROVISIONING. AT&T-13STATE may employ certain automatic and/or manual overload controls to protect AT&T-13STATE's CCS/SS7 network(s). Network Management controls found necessary to protect LIDB and/or CNAM Database from an overload condition will be applied based on non-discriminatory guidelines and procedures. Such management controls will be applied to the specific problem source to the extent technically feasible. All Customer’s Queries to an AT&T-12STATE's LIDB and/or CNAM Database shall use the following translations types: 005 for CNAM Queries and 253 for all other LIDB Queries (including GetData). Customer shall use a subsystem number in the calling party address field that is mutually agreed to by the Parties. Customer acknowledges that such subsystem number and translation type values are necessary to properly process Queries to AT&T-12STATE's Database(s). Customer will configure its global title translations according to the routing information contained in the Calling Name Access Routing Guide (CNARG), LIDB Access Routing Guide (LARG), and/or the Number Portability Administration Centers (NPACs) as appropriate for information stored by Account Owners in an AT&T-12STATE's Database. Customer agrees to send Queries in a format that complies with the applicable ANSI approved standards for SS7 protocol and pursuant to the applicable specifications standards documents identified in Appendix II, Specifications and Standards of this Agreement. Customer acknowledges that transmission in said protocol is necessary for AT&T-12STATE to provision LIDB and/or CNAM Database Queries. AT&T-12STATE will send Responses in a format that complies with applicable ANSI approved standards for SS7 protocol and pursuant to the applicable specifications standards documents identified in Appendix II, Specifications and Standards of this Agreement. AT&T-12STATE reserves the right to modify their networks at their discretion pursuant to other specification standards that may include Telcordia Technologies specifications defining specific service applications, message types, and formats. All such changes shall be announced in advance and through industry standard procedures, such as an Accessible Letter on an account team notification process. AT&T-12STATE and Customer will cooperate to coordinate any necessary changes. The Parties agree to cooperatively test GetData for each service Customer will offer using GetData Queries.
MANNER OF PROVISIONING. 5.1 SBC-12STATE will provide to CLEC, on request, SBC-12STATE-specific documentation regarding record formatting and associated hardware requirements of the interfaces SBC-12STATE provides for LIDB data administration when CLEC chooses to use such interfaces.
AutoNDA by SimpleDocs
MANNER OF PROVISIONING 

Related to MANNER OF PROVISIONING

  • Construction of Provisions Although certain provisions of this Agreement contain express language which precludes the Servicer's recovery of, or reimbursement for, expenses incurred hereunder, no inference to the contrary shall be drawn from absence of such, or similar, language in any other provision hereof regarding expenses.

  • Waiver of Provisions Any waiver of any terms and conditions hereof must be in writing and signed by the parties hereto. The waiver of any of the terms and conditions of this Agreement shall not be construed as a waiver of any subsequent breach of the same or any other terms and conditions hereof.

  • Duration of Processing Subject to any Section of the DPA and/or the Agreement dealing with the duration of the Processing and the consequences of the expiration or termination thereof, Data Processor will Process Personal Data for the duration of the Agreement, unless otherwise agreed upon in writing.

  • Terms of procurement Terms of submission: Electronic submission: Required Languages in which tenders or requests to participate may be submitted: English Electronic catalogue: Not allowed Deadline for receipt of tenders: 2024­02­19Z 12:00:00Z Information about public opening: Terms of contract: Electronic invoicing: Required

  • Scheduling Provisions The scheduling and premium provisions relating to consecutive weekends off in Article 16 do not apply to employees who accept positions under this provision.

  • Adoption of Procedures State Street and each Fund may from time to time adopt such procedures as they agree upon, and State Street may conclusively assume that no procedure approved or directed by a Fund, a Fund’s or Portfolio’s accountants or other advisors conflicts with or violates any requirements of the prospectus, articles of incorporation, bylaws, declaration of trust, any applicable law, rule or regulation, or any order, decree or agreement by which the Fund may be bound. Each Fund will be responsible for notifying State Street of any changes in statutes, regulations, rules, requirements or policies which may impact State Street responsibilities or procedures under this Agreement.

  • Provisioning 2.4.1 BellSouth shall provision services during its regular working hours. To the extent OneTone requests provisioning of service to be performed outside BellSouth’s regular working hours, or the work so requested requires BellSouth’s technicians or project managers to work outside of regular working hours, overtime charges set forth in BellSouth’s intrastate Access Services Tariff, Section E13.2, shall apply. Notwithstanding the foregoing, if such work is performed outside of regular working hours by a BellSouth technician or project manager during his or her scheduled shift and BellSouth does not incur any overtime charges in performing the work on behalf of OneTone, BellSouth will not assess OneTone additional charges beyond the rates and charges specified in this Agreement. 2.4.2 In the event BellSouth must dispatch to the End User’s location more than once due to incorrect or incomplete information provided by OneTone (e.g., incomplete address, incorrect contact name/number, etc.), BellSouth will xxxx OneTone for each additional dispatch required to provision the circuit due to the incorrect/incomplete information provided. BellSouth will assess the applicable Maintenance of Service rates from BellSouth’s XXX Xx. 0 Xxxxxx, Xxxxxxx 13.3.1.

  • Priority of Provisions If there is a conflict or inconsistency between any term, statement, requirement, or provision of any document or exhibit attached to, referenced by, or incorporated in this Agreement and any provision of Articles 1 through 11 of this Agreement, the provisions contained in Articles 1 through 11 shall prevail and be given effect.

  • Incorporation of Provisions Attachments A through H are attached hereto and incorporated into this contract as if fully set forth herein.

  • Continuing Nature of Provisions This Agreement shall continue to be effective, and shall not be revocable by any party hereto, until the First Priority Obligation Payment Date shall have occurred subject to the reinstatement as expressly set forth herein. This is a continuing agreement and the First Priority Secured Parties and the Second Priority Secured Parties may continue, at any time and without notice to the other parties hereto, to extend credit and other financial accommodations, lend monies and provide indebtedness to, or for the benefit of, Borrower or any other Loan Party on the faith hereof.

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