Troubleshooting guide

Troubleshooting Guide
204
Call problems (dropped
calls, calls getting rejected,
set displays not correct,
and so forth)
edt trace tsp l2l3 <plid>
OR
edt trace tsp cc <plid>
OR
edt trace vdsu cp <plid>
edt trace vdsu vb <plid>
For most ISDN/QSIG problems, the “l2l3”
command will be adequate. It is recommended
that you turn on the “ccs” trace at the same time.
For problems involving eT1D4, use the “tsp cc”
command. This displays the messages
to and from the T1D4 stack.
If the problem is not protocol related, turn on the
“cp/vb” tracing.
Note: The output from these commands may
need to be interpreted by Mitel Software Design.
Call problems are
generating message
output that you need to
capture in a file for
interpretation
edt enable logtofile
(turns on message tracing)
edt disable logtofile
(turns off message tracing)
This command puts all of the traces turned on by
“edt trace …” into the “/db/LDS_Trace.rtf” file
(DigTrkTrace prior to 3300 Rls 6.1).
If you need to enable tracing on a busy switch,
you should send the output to the
trace file because the output to the response
window is slow and can impact the performance
of the 3300 ICP
This log file must be interpreted by Mitel
designers. It is not meant to be interpreted by
customers or field technicians.
T1/E1 module (embedded
PRI) issues
All ESM digital trunk
maintenance commands
available to the NSU apply to
the T1/E1 module and can be
entered through the
Maintenance commands form
of the System Administration
Tool.
Refer to Mitel Knowledge Base article
04-5191-00014
Symptom Commands Description
Page 2 of 2