Filter
Top Products
DEFINITY Enterprise Communications Server Release 6
Maintenance for R6vs/si
555-230-127
Issue 1
August 1997
Maintenance Commands and Trouble-Clearing Aids
Page 8-117list mst
8
Detailed description of Messages**
Note that the X.25 messages discussed below really follow the BX.25 Message
Protocol.
The terminology Message[n] used below refers to the byte at offset n in the
message being displayed.
MST message types contain a version number. Whenever the structure of the
MST message changes, the version field in the MST buffer is changed. Version 1
(default) displays a blank in the version field which is immediately after the MST
message type field. Subsequent versions display the version number after the
MST message type field and are connected with a hyphen (“-”). For example:
Version 2 of the X.25 Application error/notification message has added the text of
the pm state table stimulus which was ignored.
0xA0 X.25 Outgoing application data message
0xA1 X.25 Incoming application data message
0xA2 X.25 Application error message
0xB0 X.25 Outgoing session layer control message
0xB1 X.25 Incoming session layer control message
0xCF X.25 Message confirmation
0xD0 X.25 Outgoing processor channel control message
0xD1 X.25 Incoming processor channel control message
0xD2 X.25 Link control message
0xD3 X.25 Link status message
0xE2 X.25 Session Timer Expirations
0xF0 X.25 Error Message (Outgoing Message Lost)
0xF1 X.25 Unrecognized Messages
0xF2 X.25 Error Message (DIP ICOM Record Aborted) (R2 Only)
0xF9 Snapper instrumentation message
0xFA Snapper continuation message (for large msgs)
Table 8-2. Summary of MST Message Types — Continued
Code Description
Continued on next page