Trunk Types 2.2.1 In interconnecting their networks pursuant to this Attachment, the Parties will use, as appropriate, the following separate and distinct trunk groups:
2.2.1.1 Interconnection Trunks for the transmission and routing of Reciprocal Compensation Traffic, translated LEC IntraLATA toll free service access code (e.g., 800/888/877) traffic, and IntraLATA Toll Traffic, between their respective Telephone Exchange Service Customers, Tandem Transit Traffic, and, Measured Internet Traffic, all in accordance with Sections 5 through 8 of this Attachment;
2.2.1.2 Access Toll Connecting Trunks for the transmission and routing of Exchange Access traffic, including translated InterLATA toll free service access code (e.g., 800/888/877) traffic, between Ymax Telephone Exchange Service Customers and purchasers of Switched Exchange Access Service via a Verizon access Tandem in accordance with Sections 9 through 11 of this Attachment; and
2.2.1.3 Miscellaneous Trunk Groups as mutually agreed to by the Parties, including, but not limited to: (a) choke trunks for traffic congestion and testing; and, (b) untranslated IntraLATA/InterLATA toll free service access code (e.g. 800/888/877) traffic.
2.2.2 Other types of trunk groups may be used by the Parties as provided in other Attachments to this Agreement (e.g., 911/E911 Trunks) or in other separate agreements between the Parties (e.g., directory assistance trunks, operator services trunks, BLV/BLVI trunks or trunks for 500/555 traffic).
2.2.3 In accordance with the terms of this Agreement, the Parties will deploy One-Way Interconnection Trunks (trunks with traffic going in one direction, including one-way trunks and uni-directional two-way trunks) and/or Two-Way Interconnection Trunks (trunks with traffic going in both directions).
2.2.4 Ymax shall establish, at the technically feasible Point(s) of Interconnection on Verizon’s network in a LATA, separate Interconnection Trunk group(s) between such POI(s) and each Verizon Tandem in a LATA with a subtending End Office(s) to which Ymax originates calls for Verizon to terminate.
2.2.5 In the event the volume of traffic between a Verizon End Office and a technically feasible Point of Interconnection on Verizon’s network in a LATA, which is carried by a Final Tandem Interconnection Trunk group, exceeds (a) the Centium Call Seconds (Hundred Call Seconds) busy hour equivalent of one (1) DS1 at any time; (b) 200,000 minutes of use for a single month; and/or; (c) 600 busy hour Centium Call Seconds (BHCCS) of use for a single month: (i) if One-Way Interconnection Trunks are used, the originating Party shall promptly establish new or augment existing End Office One-Way Interconnection Trunk groups between the Verizon End Office and the technically feasible Point of Interconnection on Verizon’s network; or,
License Types (a) A Team License shall mean a subscription license that provides a limited number of licenses to a set amount of developers for a named Customer. Customer must procure enough active licenses for each individual who has Programmatic Access. A Team License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer. A Team License cannot be used as a floating license.
(b) A Project License shall mean a subscription license which covers one named Customer application. The license fees are based on the total number of developers working on a named project, regardless of whether such developers are directly using the Licensed Product. For the purposes of pricing and license administration, a “Project Group” is deemed to be a distinct Customer software team within a Customer’s business unit that works towards a distinct business purpose for the benefit of a single application. Customer is required to identify the name of each such Project Group to Syncfusion; such name must be unambiguous in nature. It is acknowledged and agreed by Customer that each identified Project Group shall exist for a valid business purpose and not just as a means for consolidating software licenses to minimize license fees that are otherwise due. If, in the sole opinion of Syncfusion, multiple Customer teams would each individually meet the above definition of a Project Group, such multiple teams shall not be combined for the purpose of consolidating licenses under a single Project Group. Customer is responsible for providing information about each such Project Group to Syncfusion. By entering into this Agreement, Customer represents that after the effective date, it will not withhold information that Syncfusion requires to properly license each such Project Group, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement.
(c) A Division License shall mean a subscription license which will cover one named Division and allow for development work on more than one project within such Division. A Division shall mean a business unit within Customer’s organization that works towards a distinct business purpose. Customer is required to identify the name of such Division to Syncfusion; such name must be unambiguous in nature. License fee determinations will be at the sole discretion of Syncfusion and be based on such factors including, but not limited to, Customer’s Division size, developer count, and the scope of the Division’s business purpose. By entering into this Agreement, Customer acknowledges that it is responsible for providing information about the named Customer Division to Syncfusion sufficient for Syncfusion to price the Division License, and Customer represents that it will not withhold information that Syncfusion requires to properly license each such named Customer division, and further agrees that any misrepresentation in this regard constitutes a material breach of this Agreement.
(d) A Global License shall mean a subscription license for all development for a named Customer, where the license fees are based on the overall size of a named Customer. A Global License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.
(e) A Retail License shall mean a single named user, non-transferable license to use the Licensed Product. Retail Licenses will only made available to Customers in Syncfusion’s sole discretion and only when the number of such End-Users is finite and readily ascertainable. Accordingly, Syncfusion will make a determination as to whether or not the provision of Retail Licenses is appropriate under the circumstances applicable to any given Customer, and Syncfusion reserves the right, in its sole discretion, to refuse to make available Retail Licenses to a Customer and instead require a given Customer to procure a Project License, Division License, or Global License as circumstances dictate. A Retail License only grants rights to a named Customer and does not extend any right, in any form, to any parent or subsidiary company of Customer.
Unbundled Digital Loops 2.3.1 BellSouth will offer Unbundled Digital Loops (UDL). UDLs are service specific, will be designed, will be provisioned with test points (where appropriate), and will come standard with OC and a DLR. The various UDLs are intended to support a specific digital transmission scheme or service.
2.3.2 BellSouth shall make available the following UDLs, subject to restrictions set forth herein:
Unbundled Voice Loops (UVLs) 2.2.1 BellSouth shall make available the following UVLs:
Replacing Future Benchmarks Upon the occurrence of a Benchmark Transition Event, the Benchmark Replacement will replace the then-current Benchmark for all purposes hereunder and under any Loan Document in respect of any Benchmark setting at or after 5:00 p.m. (New York City time) on the fifth (5th) Business Day after the date notice of such Benchmark Replacement is provided to the Lenders without any amendment to, or further action or consent of any other party to, this Agreement or any other Loan Document so long as the Administrative Agent has not received, by such time, written notice of objection to such Benchmark Replacement from Lenders comprising the Majority Lenders. At any time that the administrator of the then-current Benchmark has permanently or indefinitely ceased to provide such Benchmark or such Benchmark has been announced by the regulatory supervisor for the administrator of such Benchmark pursuant to public statement or publication of information to be no longer representative of the underlying market and economic reality that such Benchmark is intended to measure and that representativeness will not be restored, the Borrowers may revoke any request for a borrowing of, conversion to or continuation of Advances to be made, converted or continued that would bear interest by reference to such Benchmark until the Borrowers’ receipt of notice from the Administrative Agent that a Benchmark Replacement has replaced such Benchmark, and, failing that, the Borrowers will be deemed to have converted any such request into a request for a borrowing of or conversion to Alternate Base Rate Advances. During the period referenced in the foregoing sentence, the component of Alternate Base Rate based upon the Benchmark will not be used in any determination of Alternate Base Rate.
Account Types The Financial Institution agrees that each Collateral Account is, and will be maintained as, either a “securities account” (as defined in Section 8-501 of the UCC) or a “deposit account” (as defined in Section 9-102(a)(29) of the UCC).
License Type Your license to a Product will be under a Named User or CPU license type, as specified on an order. Each Named User license to a Product entitles a Named User to access and use that Product in one production environment and up to two non-production environments. Each CPU license to a Product entitles you to assign the Product to a single CPU in one production environment and up to two non-production environments, for use in support of an unspecified number of Named Users.
Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where Xxxx has requested an Unbundled Loop and BellSouth uses IDLC systems to provide the local service to the End User and BellSouth has a suitable alternate facility available, BellSouth will make such alternative facilities available to Xxxx. If a suitable alternative facility is not available, then to the extent it is technically feasible, BellSouth will implement one of the following alternative arrangements for Xxxx (e.g. hairpinning):
1. Roll the circuit(s) from the IDLC to any spare copper that exists to the customer premises.
2. Roll the circuit(s) from the IDLC to an existing DLC that is not integrated.
3. If capacity exists, provide "side-door" porting through the switch.
4. If capacity exists, provide "Digital Access Cross Connect System (DACS)- door" porting (if the IDLC routes through a DACS prior to integration into the switch).
2.6.2 Arrangements 3 and 4 above require the use of a designed circuit. Therefore, non- designed Loops such as the SL1 voice grade and UCL-ND may not be ordered in these cases.
2.6.3 If no alternate facility is available, and upon request from Xxxx, and if agreed to by both Parties, BellSouth may utilize its Special Construction (SC) process to determine the additional costs required to provision facilities. Xxxx will then have the option of paying the one-time SC rates to place the Loop.
YOUR BILLING RIGHTS - KEEP THIS NOTICE FOR FUTURE USE This notice tells you about your rights and our responsibilities under the Fair Credit Billing Act.
Agreement with Respect to Leased Data Processing Equipment (a) The Receiver hereby grants to the Assuming Bank an exclusive option for the period of ninety (90) days commencing the day after Bank Closing to accept an assignment from the Receiver of any or all Data Processing Leases to the extent that such Data Processing Leases can be assigned.
(b) The Assuming Bank shall (i) give written notice to the Receiver within the option period specified in Section 4.7(a) of its intent to accept or decline an assignment or sublease of any or all Data Processing Leases and promptly accept an assignment or sublease of such Data Processing Leases, and (ii) give written notice to the appropriate lessor(s) that it has accepted an assignment or sublease of any such Data Processing Leases.
(c) The Receiver agrees to facilitate the assignment or sublease of Data Processing Leases or the negotiation of new leases or license agreements by the Assuming Bank; provided, that neither the Receiver nor the Corporation shall be obligated to engage in litigation or make payments to the Assuming Bank or to any third party in connection with facilitating any such assumption, assignment, sublease or negotiation.
(d) The Assuming Bank agrees, during its period of use of any property subject to a Data Processing Lease, to pay to the Receiver or to appropriate third parties at the direction of the Receiver all operating costs with respect thereto and to comply with all relevant terms of the applicable Data Processing Leases entered into by the Failed Bank, including without limitation the timely payment of all rent, taxes, fees, charges, utilities, insurance and assessments.
(e) The Assuming Bank shall, not later than fifty (50) days after giving the notice provided in Section 4.7(b), (i) relinquish and release to the Receiver all property subject to the relevant Data Processing Lease, in the same condition as at Bank Closing, normal wear and tear excepted, or (ii) accept an assignment or a sublease thereof or negotiate a new lease or license agreement under this Section 4.7.
