The RTP connection failed.
Bytes 2 and 3 following the sense code contain sense-code-specific
information.
- 0003
- The setting of the start-of-message bit in a received packet was
unexpected. One of the following error conditions was detected:
- During reassembly of a user message, the byte-sequence-number
field of a received packet is set to the next expected sequence number
of the user message, but the start-of-message bit is set to one.
- The byte-sequence-number field of a received packet containing
data is set to the expected starting sequence number of a user message,
but the start-of-message bit is set to zero.
- The byte-sequence-number field of a received packet is set to
the expected starting sequence number of a user message. The end-of-message
bit is set to one, but the start-of-message bit is set to zero.
- Lower sequence-numbered data was received in an earlier packet
with the last-message bit set to one, but the start-of-message bit
is set to one in the newly received packet.
- 0004
- The setting of the end-of-message (EOMI) bit in a received packet
was unexpected. One of the following error conditions was detected:
- A packet containing data has the last-message bit (LMI) set to
one, but the end-of-message bit is set to zero.
- During reassembly of a user message, the byte-sequence-number
field of a received packet is set to the next expected sequence number
of the user message; the last-message bit is set to one, but the end-of-message
bit is set to zero.
- The byte-sequence-number field of a received packet is set to
the expected starting sequence number of a user message. The start-of-message
bit (SOMI) is set to one, the last-message bit is set to one, but
the end-of-message bit is set to zero.
- 0008
- The setting of the last-message bit in a received packet was unexpected.
The following error condition was detected:
- The last-message bit is set to one in a retransmitted packet,
but higher sequence-numbered data was received in an earlier packet.
- 000B
- The setting of the "connection qualifier source identifier field
present" bits in a received packet was unexpected. The following
error condition was detected:
- The TCID-assignor bit is set to one, but the "connection qualifier/source
identifier field present" bits are not set to 01.
- 000C
- The setting of the "optional segments present" bit in a received
packet was unexpected. The following error condition was detected:
- No active context is found, the setup-packet bit is set to one,
but the "optional segments present" bit is set to zero.
- 000D
- The setting of the DATA OFFSET/4 in the THDR field in a received
packet was unexpected. One of the following error conditions was detected:
- The data-length field has a value greater than zero, but the payload-offset/4
field points to an offset beyond the end of the network layer packet.
- The data-length field has a value greater than zero, but the setting
of the DATA OFFSET/4 field is not consistent with the encodings of
the connection-qualifier/source-identifier field and the optional
segments.
- 000E
- The setting of the DATA length field in the THDR of a received
packet was unexpected. One of the following error conditions was detected:
- The data-length field has a value greater than zero, but the DATA
OFFSET/4 field points to an offset from which there is insufficient
remaining length for the data.
- The packet contains data, but lower sequence-numbered data was
received in an earlier packet with the last-message bit set to one.
- 000F
- The setting of the byte sequence number field (BSN) in a received
packet was unexpected. The following error condition was detected:
- The byte-sequence-number field of a received packet is higher
than the next expected sequence number (that is, a new gap in the
user data stream is detected), but the last-message bit was set to
one in an earlier packet.
- 0014
- The setting of the target resource identifier field present bit
of the connection setup segment in a received packet was unexpected.
The following error condition was detected:
- The target resource identifier field present bit in the connection
setup segment is set to zero, but target resource identification is
required by the receiver.
- 0016
- The setting of the ARB flow congestion control used bit of the
connection setup segment in a received packet was unexpected. The
following error condition was detected:
- The ARB flow/congestion control used bit is set to zero, but
the use of ARB flow/congestion control is required by the receiving
RTP.
- 0017
- A field setting in the topic identifier (X'28') control
vector in the connection setup segment in a received packet was unexpected.
One of the following error conditions was detected:
- The topic-identifier field within the topic-identifier (X'28')
control vector is not correctly encoded.
- The topic identifier specified in the topic-identifier (X'28')
control vector is not supported.
- 0018
- A field setting in the network identifier (X'03') control
vector in a received packet was unexpected. One of the following error
conditions was detected:
- The network-identifier field within the network-identifier (X'03')
control vector is not correctly encoded.
- The network-identifier specified in the network-identifier (X'03')
control vector within the connection-setup segment is not the network
identifier associated with the receiving RTP.
- 0019
- A field setting in the node identifier (X'00') control
vector in a received packet was unexpected. One of the following error
conditions was detected:
- The node-identifier field within the node-identifier (X'00')
control vector is not correctly encoded.
- The node-identifier specified in the node-identifier (X'00')
control vector within the connection-setup segment is not the node
identifier associated with the receiving RTP.
- 001E
- The setting of the closed bit of the status segment in a received
packet was unexpected. One of the following error conditions was detected:
- The closed bit in the status segment is set to one, but not all
reliable data sent to the partner is acknowledged.
- The closed bit in the status segment is set to one, but data is
queued for transmission.
- 001F
- The setting of the ARB level in the ARB segment in a received
packet was unexpected. The following error condition was detected:
- Progressive-mode ARB is specified in the ARB segment, but it is
not allowed on this connection.
- 0022
- The setting of the DSEQ field of the status segment in a received
packet was unexpected. The following error condition was detected:
- RSEQ and DSEQ in the status segment are not consistent. The
values indicate data not received has been delivered.
- 0032
- The beginning and ending sequence numbers for an acknowledged
byte-span pair (ABSP) in a status segment in a received packet were
unexpected. The following error condition was detected:
- The beginning and ending sequence numbers for an ABSP are not
consistent either with RSEQ or another ABSP. The sequence numbers
overlap.
- 0033
- A field setting in the HPR switching information (X'83')
control vector in a received packet was unexpected. The following
error condition was detected:
- The maximum packet size specified in the HPR switching information
(X'83') control vector is fewer than 768 bytes.
- 0035
- A field setting in the NCE identifier (X'26') control
vector in a received packet was unexpected. The following error condition
was detected:
- The NCE-identifier field within the NCE-identifier (X'26')
control vector is not correctly encoded.
- 0037
- Window flow control was requested by the calling RTP but is not
supported by the listening RTP.
- 003A
- The using layer terminated abnormally. (This error condition is
associated with the RTP user interface and is implementation dependent.)