Recurring Transactions If you intend to use the Card for recurring transactions, you should monitor your Balance and ensure you have funds available in your Card Account to cover the transactions. “Recurring transactions” are transactions that are authorized in advance by you to be charged to your Card at substantially regular intervals. We are not responsible if a recurring transaction is declined because you have not maintained a sufficient Balance in your Card Account to cover the transaction. If these recurring transactions may vary in amount, the person or merchant you are going to pay should tell you, 10 days before each payment, when it will be made and how much it will be. You may choose instead to get this notice only when the payment would differ by more than a certain amount from the previous payment, or when the amount would fall outside certain limits that you set with that person or merchant. If you have told us in advance to make regular payments (i.e., Recurring Transactions) from your Card Account, you can stop the payment by notifying us orally or in writing at least three (3) Business Days before the scheduled date of the transfer. If you call, we also may require you to put your request in writing and get it to us within 14 days after you call. If you order us to stop one of these payments three (3) Business Days or more before the transfer is scheduled, and we do not do so, we will be liable for your losses or damages. If you have authorized a merchant to make the recurring payment, you should also contact the applicable merchant in order to stop the transaction. Fraudulent Card Account Activity. We may block or cancel your Card Account if, as a result of our policies and procedures, we reasonably believe your Card Account is being used for fraudulent, suspicious, or criminal activity or any activity that is inconsistent with this Agreement. We will incur no liability because of the unavailability of the funds that may be associated with your Card Account.
Loop Provisioning Involving Integrated Digital Loop Carriers 2.6.1 Where InterGlobe 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 InterGlobe. 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 InterGlobe (e.g. hairpinning):
Optional Extended Local Calling Scope Arrangement Traffic (5) special access, private line, Frame Relay, ATM, or any other traffic that is not switched by the terminating Party; (6) Tandem Transit Traffic; (7) Voice Information Service Traffic (as defined in Section 5 of the Additional Services Attachment); or, (8) Virtual Foreign Exchange Traffic (or V/FX Traffic) (as defined in the Interconnection Attachment). For the purposes of this definition, a Verizon local calling area includes a Verizon non-optional Extended Local Calling Scope Arrangement, but does not include a Verizon optional Extended Local Calling Scope Arrangement.
Unbundled Loop Modifications (Line Conditioning 2.5.1 Line Conditioning is defined as routine network modification that BellSouth regularly undertakes to provide xDSL services to its own customers. This may include the removal of any device, from a copper Loop or copper Sub-loop that may diminish the capability of the Loop or Sub-loop to deliver high-speed switched wireline telecommunications capability, including xDSL service. Such devices include, but are not limited to, load coils, excessive bridged taps, low pass filters, and range extenders. Excessive bridged taps are bridged taps that serves no network design purpose and that are beyond the limits set according to industry standards and/or the XxxxXxxxx XX 00000.
ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:
Unusual Job Requirements of Short Duration The nature of health care is such that at times it may be necessary for an employee to perform work not normally required in his/her job for the safety, health or comfort of a client or resident. It is understood that an employee shall not be expected to perform a task for which he/she is not adequately trained.
INCLEMENT CONDITIONS Section 1.
Provisioning Line Splitting and Splitter Space 3.8.1 The Data LEC, Voice CLEC or BellSouth may provide the splitter. When EZ Phone or its authorized agent owns the splitter, Line Splitting requires the following: a non-designed analog Loop from the serving wire center to the NID at the End User’s location; a collocation cross connection connecting the Loop to the collocation space; a second collocation cross connection from the collocation space connected to a voice port; the high frequency spectrum line activation, and a splitter. The Loop and port cannot be a Loop and port combination (i.e. UNE-P), but must be individual stand-alone Network Elements. When BellSouth owns the splitter, Line Splitting requires the following: a non designed analog Loop from the serving wire center to the NID at the End User’s location with CFA and splitter port assignments, and a collocation cross connection from the collocation space connected to a voice port.
Voice Grade Unbundled Copper Sub-Loop Unbundled Sub-Loop Distribution – Intrabuilding Network Cable (aka riser cable)
Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).
