Error Conditions Clause Samples

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

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

Error Conditions. The following item is added at the end of the list: No changes.

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.

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

Error Conditions. Error conditions are handled as described in section A.5 of revised Q.933. Revised Q.933 is a supplement to ITU Q.933. A. Recommended procedures for equipment that can detect loopback at the physical layer: B. Recommended procedures for equipment that cannot detect loopback at the physical layer: