Table of Contents
Advertisement
10.11.2 Diagnosing DSP Module Related Issues
Refer to Mitel Knowledge Base article 05-5107-00004 for information on how to diagnose
DSP module issues.
Use the following maintenance commands to obtain information concerning DSPs:
•
DUMPDSPBOOTINFO - to display DSP resource allocation on the system.
•
SHOWDSPSTATUS - to display the current status of all detected DSP MMCs on the
system.
10.11.3 Diagnosing MSDN DPNSS Link Problems
If there is a problem with the MSDN/DPNSS link:
Establish whether all calls are affected.
•
If all calls are affected check the status of the link by using the DTSTAT READ PLID
command.
•
If the link is unavailable check the cabling. Test with a back to back cable to prove the
DS1 or CEPT card.
•
If the link is available check the errors.
•
If some calls fail check the following:
•
ARS programming
•
Digit Conflict
•
Interconnect Restriction
•
Far end fault/programming
•
If only calls to the central office fail check that the Class Of Service option of Public
Network Access via DPNSS is enabled on the extension making the call and the
MSDN trunks.
10.11.4 Loopback Testing on Digital Trunks
You can perform a loopback test on digital trunks to rule out problems with the system
hardware. If two trunks can be successfully looped, and calls made that contain no slips,
BERs, or framing losses, the system is operating properly. The loopback test requires the
use of two trunks.
To perform loopback testing:
1.
Assign a digital link descriptor to each hybrid (see the Digital Link Descriptors form).
Document Version 1.0
Troubleshooting Guide
Diagnosing Problems
318
Advertisement
Table of Contents
Troubleshooting
