Lucent Technologies R5SI User Manual
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-203
list mst
8
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 ’-’. 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.
the MST message type field. Subsequent versions display the version number
after the MST message type field and are connected with a ’-’. 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.
Version 1 of MST message type 0xA2 would appear on the ’list mst’ output:
Version 2of MST message type 0xA2 would appear on the ’list mst’ output:
Vector Trace
Message type: 0x10
Message format:
Vector Event Trace (D92 Only)
Message type:
0x11
Number
Date/Time
Type
Message
1
11:41:22:425
A2
17 10
Number
Date/Time
Type
Message
90
12:41:14:112
A2-02
17 10 21 03 32 05 01 80
Message[1-4]
= call identifier (CID) (defined in $BASEPJ/hdrs/capro.h)
Message[5-6]
= vector number (defined in $BASEPJ/hdrs/dpm_calls.h)
Message[7]
= step number (defined in $BASEPJ/hdrs/callr.h)
Message[8]
= step type (defined in $BASEPJ/hdrs/dpm_calls.h)
Message[9]
= step state (defined in $BASEPJ/hdrs/dpm_calls.h)
Message[10-12]
= VDN
Message[13]
= port network number
Message[14]
= endpoint number
Message[15]
= angel number
Message[16]
= circuit number
Message[17-20]
= trunk number
Message[21+]
= auxiliary data (based on step type)