Signal Tracing
The signal tracing function implements both the trace error log and the general trace function. The function implies that signals or text items are copied and preserved as the program execution is handling an activity so that the function can be analyzed later on.
The first trace individual is used by the error log function and is therefore always enabled in all servers.
Up to fifteen signal traces can be specified simultaneously.
- Error log
Error log is always enabled and stores information about error situations in the software.
- Sequential tracing
Sequential tracing is used for tracing an activity. Through the sequential trace, the signals can be followed in their logical and chronological order and thus the chain of events that led to the fault. Sequential tracing should be used when the user has an idea of the activity that went wrong and wants to locate the break in the sequence.
- Interface tracing
Interface tracing is used to trace all signals to and from a program unit or a hardware equipment position. This form of tracing is used, for example, when the unit where the fault occurs is already known or suspected, but the process that caused the fault is not known (for example, when a faulty signal in a unit has been received).
- Hardware position tracing
Hardware tracing is used when the problem is related to a hardware board where only the signaling to and from the board is wanted. This function is especially useful when several program units are cooperating to the same hardware position. For tracing on MGU/MGU2, see also the MGU COMMAND AND FAULT LOCATION GUIDE on Mitel Knowledge Base.