Lucent Technologies R5SI 用户手册
DEFINITY Enterprise Communications Server Release 5
Maintenance and Test for R5vs/si
Maintenance and Test for R5vs/si
555-230-123
Issue 1
April 1997
Maintenance Commands and Trouble-Clearing Aids
Page 8-224
list mst
8
Application Control
0xA2 - X.25 application error or notification
NOTE:
The ’X.25 application error message’ category contains notifications as well
as errors.
The ’X.25 application error message’ category contains notifications as well
as errors.
0xA2, 0xF0 and 0xF2 messages will be turned on by responding ’y’ to the
’Application Errors?’ field.
’Application Errors?’ field.
Version 1:
Version 2:
Errors/Notifications:
R1/R3:
0x01 - no outgoing buffer available
0x05 - pvc session down
0x06 - pvc session up
0x07 - pvc session connect
0x08 - pvc session restart
0x09 - message buffer overload uplink
0x0A - message buffer overload downlink
0x0B - message buffer exhaustion
0x0C - max # of outgoing msgs allowed
0x0D - bad msg type in message buffer routine
0x0E - no message buffers available
0x0F - message buffer pointer error
0x10 - pm state table stimulus ignored
0x11 - bad session connect message
0x05 - pvc session down
0x06 - pvc session up
0x07 - pvc session connect
0x08 - pvc session restart
0x09 - message buffer overload uplink
0x0A - message buffer overload downlink
0x0B - message buffer exhaustion
0x0C - max # of outgoing msgs allowed
0x0D - bad msg type in message buffer routine
0x0E - no message buffers available
0x0F - message buffer pointer error
0x10 - pm state table stimulus ignored
0x11 - bad session connect message
Session Layer Control
NOTE:
The session layer header is considered part of the session layer message.
The session layer header is considered part of the session layer message.
Message[1]
= processor channel number
Message[2]
= application error/notification
Message[1]
= processor channel number
Message[2]
= application error/notification
Message[3+]
= pm stimulus ignored (For message[2] == 0x10 only)