Mitel MiVoice Business Troubleshooting Manual page 60

Troubleshooting Guide
HARDWARE SYMPTOM
DSP card or DSP Run-Time Access
module. Fault.
DSP Overflow Error.
52
Table 13: Embedded Module Troubleshooting
PROBABLE CAUSE
These are mostly exceptions
that either produce an XRTC
file or simply perform a hard
reset on the system. These
can occur at any point after
the card has been taken out
of reset but are considered
separate from the Booting
Process.
As of 3300 Release 7.0,
these are now tracked and
monitored by the DSP
Service Provider. If these
occur, the dsp will be taken
out of service and a "DSP
Status" alarm is raised.
Prior to 3300 Release 7.0,
these were only reported as
PostSoftware Log:
RsrcAlloc() failed with result
DSP_OVERFLOW.
CORRECTIVE ACTION
If the system is stuck in a reboot
sequence. Remove and re-seat the
card. Reboot. They should be
looking at the connectors for bent
pins etc. NOTE: Ensure that the
screws are not over tightened! Over
tightening of one side can cause the
other side connector to rise up.
Obtain System Diagnostics
Reporting output, or at a minimum,
the XRTC and PostSoftware logs.
If this happens, and it is a HW
problem, it should be repeatable.
Remove and re-seat the card.
Reboot. Look at the connectors for
bent pins etc. NOTE: Ensure that the
screws are not over tightened! Over
tightening of one side can cause the
other side connector to rise up.
If it is a pre R7.0 system: From the
RTC shell, enter: DumpCaps (x,y)
where x is the card number and y is
the dsp number reported in the
PostSoftware Log. Capture these
results and send them to Mitel
Product Support.
Obtain System Diagnostics
Reporting output file and contact
Mitel Product Support.
Page 3 of 3