Avaya DEFINITY Server CSI Maintenance Manual page 318

Maintenance Commands
0x23 - MT_IMT (miscellaneous IMT hooks)
This message type is for miscellaneous IMT hooks. The only sub-type currently
available is for a debug button (dbut). The button number is provided in the debug
button MST message so that more than one button can be administered (through
IMT) to convey different meanings. For example, depression of button N could
signify the start of the problem symptoms, while depression of button N + X could
signify the end of the problem symptoms. Note that the button number being
logged represents the position of a button on a particular set type, and will be
different depending on set type and module type (feature, coverage, display, and
so forth). The mapping of the button number stored in the IMT_BUT_DEBUG
MST message to a position on the set is not trivial, however, the debug buttons
can be administered through TCM, debug button filtering enabled through TCM
and MST enabled using the 'enable mst' command and the resultant messages
sent to MST when each button is depressed can be examined for the button data
and noted.
Message format:
Message[1]
Message[2-3]
Message[4-7]
0x40 - internal message tracing of call_p, conn_m,
grp_m, serv_d, suser_m
Message formats: conn_m, grp_m, and suser_m:
Message[1-4]
Message[5-6]
Message[7+]
serv_d (map-type messages):
Message[1-4]
Message[5-6]
Message[7]
Message[8-11]
Message[12]
Message[13]
Message[14]
Message[15]
Message[16+]
318
Issue 5 October 2002
= 0x01 (debug button sub-type, IMT_BUT_DEBUG)
= button number
= user id
= user identifier
= hook identifier (defined in $BASEPJ/hdrs/mstencode.h)
= standard message (depends on hook type)
= user identifier
= hook identifier (defined in $BASEPJ/hdrs/mstencode.h)
= STIM type
= service identifier
= port network number
= endpoint number
= angel number
= circuit number
= message
555-233-119