Error Conditions Sample Clauses

Error Conditions. Error conditions are handled as described in section A.5 of Q.933. The PVC management procedures, as defined in section 2.3.1 of this implementation agreement, are based on the procedures of Q.933 Annex A. The section 2.3.1 procedures are limited to reporting status on a limited number of PVCs: “the number of PVCs that can be supported by Q.933 Annex A is limited by the maximum frame size that can be supported by the user device and the network on the bearer channel.” These enhancement procedures are required to support “any number of” (e.g., greater than 1024) PVCs per bearer channel. This annex defines optional enhanced PVC management procedures to increase the number of PVCs in Full Status reports.
Sample 1
AutoNDA by SimpleDocs
Error Conditions. The following item is added at the end of the list: No changes.
Sample 1
Error Conditions. Each error condition is identified by a cause value that is included in the Cause Information Element. Some cause values result in the inclusion of additional diagnostic information in the variable length diagnostic element of the Cause Information Element. If the diagnostic element is not used, it is empty. The cause values are defined in Table 4. INCONSISTENT_BUNDLE Possible configuration mismatch detected. 1 Expected Bundle Identification value as provisioned at the endpoint sending the Cause Information Element. Refer to Note 2, Figure 8for the format of the element. UNKNOWN_VENDOR Unrecognized OUI in a received Vendor Specific Information Element. 2 None LINK_IDLE The bundle link is not operational. 3 None LINK_DOWN The bundle link physical layer is down. 4 None DIFFERENTIAL_DELAY The bundle link differential delay exceeds the maximum allowed. 5 None LOOPBACK_DETECTED The bundle link has detected a potential loopback condition. 6 None OTHER Generic failure cause described by text in diagnostic element. 7 Textual description of failure cause. Refer to Note 2, Figure 8for the format of the element. UNEXPECTED_ ADDLINK An ADD_LINK message was received when the Bundle Link was in up state. 8 None The purpose of this annex is to provide one example of a state machine representation of the bundle link procedures, to assist in the understanding of this agreement. This example of the bundle link procedures may not meet all the requirements specified in the procedure section (Section 4). The text description of the procedures is definitive. A simplified version (for clarity) of the state machine for the MFR Link Integrity Protocol is shown in Figure
Sample 1
Error Conditions. A printer shall have mechanisms to allow software to interpret and act upon the following conditions. 1. Out of paper/paper low. 2. Printer jam/failure. 3. Printer disconnected (this may only be detected when the software attempts to print).
Sample 1
Error Conditions. If an error is present, the red HEARTBEAT indicator will flash with an unbalanced on/off pattern (on longer than it is off). The error(s) can be viewed under the DIAGNOSTICS mode. HIGH VOLTAGE INTERLOCK SWITCH FREE VEND KEYSWITCH (OPTIONAL) COIN RETURN BUTTON LOW VOLTAGE DOOR SWITCH SERVICE KEYPAD CABINET SELECTION SWITCH BILL ACCEPTOR (OPTIONAL) COIN INSERT
Sample 1
Error Conditions. Each error condition is identified by a cause value that is included in the Cause Information Field. Some cause values result in the inclusion of additional diagnostic information in the variable length diagnostic field of the Cause Information Field. If the diagnostic field is not used it is empty. The cause values are defined in Table 4. INCONSISTENT_BUNDLE Possible configuration mismatch detected. 1 Expected Bundle Identification value as provisioned at the endpoint sending the Cause Information Field. Refer to Note 2, Figure 8for the format of the field. UNKNOWN_VENDOR Unrecognized OUI in a received Vendor Specific Information Field. 2 None LINK_IDLE The bundle link is not operational. 3 None LINK_DOWN The bundle link physical layer is down. 4 None DIFFERENTIAL_DELAY The bundle link differential delay exceeds the maximum allowed. 5 None LOOPBACK_DETECTED The bundle link has detected a potential loopback condition. 6 None OTHER Generic failure cause described by text in diagnostic field. 7 Textual description of failure cause. Refer to Note 2, Figure 8for the format of the field. The purpose of this annex is to provide one example of a state machine representation of the bundle link procedures, to assist in the understanding of this agreement. This example of the bundle link procedures may not meet all the requirements specified in the procedure section (Section 4). The text description of the procedures is definitive. A simplified version (for clarity) of the state machine for the MFR Link Integrity Protocol is shown in Figure 16. The initial state is down. The picture is divided into four quadrants for clarity: Physically Up, Administratively Up The normal operational mode for a bundle link. Physically Up, Administratively Down Bundle link is not participating in bundle operation. Physically Down, Administratively Up The bundle link does not support frame transmission. Physically Down, Administratively Down Bundle link is not participating in bundle PHY Down PHY Up PH_DEACTIVATE ind PH_DEACTIVATE ind ADD_LINK (V) ADD RX ADD_LINK_ACK ADD_LINK (I) ADD_LINK_REJ REMOVE_LINK PH_DEACTIVATE ind ADD SENT UP ADD_LINK_ACK DOWN ADD_LINK (I) REMOVE_LINK BL_DEACTIVATE req PH_ACTIVATE ind ADD ACK RX ADD_LINK (V) BL_ACTIVATE req PH_DEACTIVATE ind BL_DEACTIVATE req BL_DEACTIVATE req DOWN IDLE BL_ACTIVATE req BL_DEACTIVATE req BL_DEACTIVATE req PH_ACTIVATE ind IDLE REMOVE_LINK_ACK T_ACK_EXP (MAX) IDLE PENDING PH_DEACTIVATE ind PH_DEACTIVATE ind Administratively Up ope...
Sample 1

Related to Error Conditions

  • SUPERIOR CONDITIONS 21.01 All existing benefits, rights, privileges, practices, terms or conditions of employment which may be considered to be superior to those contained herein and which are set out in Appendix 4 are specifically retained by this Agreement unless otherwise agreed by the local parties. The parties agree to remove from Appendix 4 those superior conditions which no longer have application. Where the parties cannot agree on whether a superior condition continues to have application, the issue will be reduced to a grievance and referred to arbitration. 21.02 The Union and the Participating Hospitals agree to establish a committee consisting of two (2) representatives of the Union and two (2) representatives of the Participating Hospitals to review the superior conditions appendices in each of the participating hospitals. This committee will report to their respective negotiating committees prior to the next round of central negotiations.

  • Prior Conditions Satisfied All conditions set forth in §10 shall continue to be satisfied as of the date upon which any Loan is to be made or any Letter of Credit is to be issued.

  • Specific Conditions If applicable, specific conditions required after a risk assessment will be included in Exhibit G. Grantee shall adhere to the specific conditions listed therein.

  • Conditions for Advance and Conditions to Closing Section 7.1.

  • Other Conditions 4.1 The Bank may at any time vary, modify or amend the terms and conditions of the Program as it may, in its reasonable discretion, think fit, and the Cardholder shall be bound by such variations and amendments after such variations and amendments have been communicated to the Cardholder. 4.2 Any abuse or fraud in respect of the issuance of Points or redemption of Rewards (including any Points transfer to designated airlines’ programmes), may result in the cancellation of accrued Points and any Rewards already issued. 4.3 Without prejudice to any of the Bank’s rights and remedies, the Bank is entitled, at any time, in its reasonable discretion with reasonable notice, to terminate the Program or withdraw, cancel or invalidate any Reward and/ or Points already issued. 4.4 The Bank is not liable if it is unable to perform its obligations under these terms and conditions, due directly or indirectly to the failure of any machine or communication system, industrial dispute, war, Act of God, or anything outside the control of the Bank, its agents or any third party. The Bank shall not be responsible for any delay in the transmission to the Bank of evidence of Retail Purchases by the participating merchants or any other third party. 4.5 The Cardholder hereby authorizes the Bank to disclose information regarding himself/herself and his/her Card Account(s) to such third parties as the Bank deems necessary for the purposes of the Program. 4.6 The Bank’s records of all matters relating to this program are conclusive and binding on the Cardholder, save in the case of the Bank’s manifest or clerical error. The Bank is entitled to, for any reason and at any time, with reasonable notice, suspends the calculation or accrual of Points to rectify any errors in the calculation, or otherwise adjust such calculation. 4.7 The Bank’s decision on all matters relating to the Program shall be final and binding on the Cardholder. 4.8 Any redemption of any Reward shall be governed by the Citi ThankYou Rewards Program Terms and Conditions as amended from time to time.

  • Satisfaction of Conditions The conditions precedent set out in Section 6.1, Section 6.2 and Section 6.3 shall be conclusively deemed to have been satisfied, waived or released at the Effective Time.

  • Unsafe Conditions In accordance with 29 CFR § 1977, occasions might arise when an employee is confronted with a choice between not performing assigned tasks or subjecting himself/herself to serious injury or death arising from a hazardous condition at the workplace. If the employee, with no reasonable alternative, refuses in good faith to expose himself/herself to the dangerous condition, he/she would be protected against subsequent discrimination. The condition causing the employee's apprehension of death or injury must be of such a nature that a reasonable person, under the circumstances then confronting the employee, would conclude that there is a real danger of death or serious injury and that there is insufficient time, due to the urgency of the situation, to eliminate the danger by resorting to regular statutory enforcement channels. In addition, in such circumstances, the employee, where possible, must also have sought from his Employer, and been unable to obtain, a correction of the dangerous condition.

  • Weather Conditions The Contractor will be required to protect all work and materials against damage or injury from the weather. If, in the opinion of the County, any work or materials shall have been damaged or injured by reason of failure to protect such, all such materials or work shall be removed and replaced at the expense of the Contractor.

  • Adverse Weather Conditions Except in emergency conditions, the Employer shall not require an employee to work outside under extreme weather conditions.

  • Conditions The Limited Damage Waiver Program has certain conditions. Covered Damage does not include, and the Covered Guest remains liable for, the following: • Damages caused by Intentional Acts of a Covered Guest • Damages caused by gross negligence or willful and wanton conduct. • Any damage that the Covered Guest does not report to iTrip staff in writing by the time the Covered Guest checks out of the unit. • Damage from theft without a valid police report. • Damage caused by any pet or other animals brought onto the premises by any Guests, whether or not the property is "pet friendly". • Damage or loss of any property owned by or brought onto the premises by a Covered Guests or invitee of Covered Guest. • Property Damage resulting from any motorized vehicle or watercraft operated by a Covered Guest. • Damaged Caused by any forbidden items or property usage including but not limited to BBQ Grills, Candles, Cigarettes, etc.

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