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-119list mst
8
Message format:
Events are defined in $BASEPJ/hdrs/evnt_defs.h. Events based on the call_p will
have the following auxiliary data:
Events based on the grp_m will have the following auxiliary data:
IMT (D92)
The messages described in this section cannot be controlled directly through
any of the MST screens. They are enabled/disabled through TCM but their output
goes to the MST buffer. See [IMT] for details on these messages.
A read-only field in the “change mst” screen, “Other Tracing?”, alerts the user
that one or more of these types of messages is enabled.
0x21 - IMT proc_errs
Message format:
0x22 - IMT crec
Message format:
Message[1-4] = cid (defined in $BASEPJ/hdrs/capro.h)
Message[5-6] = event
Message[7+] = auxiliary data (based on event)
Message[7-8] = vector number
Message[9-10] = step number
Message[7-10] = hunt group number
Message[1-4] = process number(lname)
Message[5-8] = sequence number (defined in *.p/hdrs/main_err.h, for
example: $BASEPJ/gmtce.ss/hmm.p/hdrs/main_err.h)
Message[9-12] = data 1
Message[13-17] = data 2
Message[1+] = call record (defined as CALLR typedef in
$BASEPJ/hdrs/callr.h)