ACC X.25 Protocol User's Guide

X.25 Status and Completion Messages
Unsolicited Status Messages
Appendix A138
ST25RNRTO (98) A VC RNR timeout has occurred. This indicates that
the remote end of the link sent an level 3 RNR which
halted the outbound data traffic to the associated VC. If
this condition is not cleared within 180 seconds, this
status message is generated. This will cause the VC to
be reset.
ST25LCNBF (99) A buffer shortage has occurred for the associated
Virtual Circuit.
ST25BADIC (100) Bad Interrupt Confirm packet received on the
Virtual Circuit. This indicates that an Interrupt
Confirm packet was received without having sent an
interrupt data packet. This will cause the VC to be
reset.
ST25INTTO (101) Interrupt packet timeout has occurred. This
indicates that the remote end of the link has not
confirmed our sent interrupt packet within timer T26
seconds. This will cause the VC to be reset.
ST25PKLNG (102) VC interrupt or data packet too long. The remote
end of the link sent a data packet which exceeded the
X.25 level 3 packet size or an interrupt packet larger
than 32 bytes for 1984 X.25 or larger than 1 byte for
1980 X.25. This will cause the VC to be reset.
ST25BADQB (103) Inconsistent Q-bit usage detected in VC data
packets. This indicates the inbound data packets of a
complete packet sequence did not ALL contain the
same Q-bit value. This will cause the VC to be reset.
ST25NVGFI (104) An invalid GFI was received on the Virtual Circuit.
Most likely the modulo 128 bit was set (bit 6). The ACC
does not support modulo 128 sequence numbering. This
will cause the VC to be reset or cleared as appropriate.
ST25ILLDB (105) Illegal use of D-bit detected in packets for the VC.
This indicates a data packet was received with the
D-bit set when D-bit use has not been negotiated in the
call setup (non-1980 X.25). This will cause the VC to be
reset.