Specifications

18 System Software Diagnostics Guide — September 2006
Diagnostics Overview
• Section 4.5, “Tracing Firmware”, on page 28
• Chapter 12, “DebugAngel Reference”
• Chapter 23, “MercMon Reference”
• Chapter 24, “PDK Trace Reference”
Diagnosing a Control Processor, Signal Processor or Shared RAM Fault on a Board
You can use the dlgsnapshot tool to capture a core dump when a Control Processor (CP),
Signal Processor (SP), or Shared RAM (SRAM) fault is detected on a DM3 board. Refer to the
following:
• Section 4.6, “Diagnosing a Control Processor or Signal Processor Fault on a Board”, on
page 29
• Chapter 15, “Dlgsnapshot Reference”
Software and Application Diagnostics
The following tasks can be accomplished using the diagnostic tools:
Checking the network connections
You can use the PSTN Diagnostics, Digit Detector, and CallInfo tools to check your board’s
network connections. Refer to the following:
• Chapter 5, “Diagnosing First Call Issues”
• Chapter 26, “PSTN Diagnostics Tool Reference”
• Chapter 10, “CallInfo Reference”
Checking the PSTN protocol configuration
You can use the PSTN Diagnostics tool to check your board’s protocol configuration. Refer to
the following:
• Chapter 6, “Diagnosing PSTN Protocol Issues”
• Chapter 26, “PSTN Diagnostics Tool Reference”
Collecting CAS trace information
Inbound and outbound R2MF tones and CAS bit transitions/states can be traced using existing
Global Call APIs and a Global Call event (GCEV_TRACEDATA). This allows developers to
determine the root cause of protocol issues in a system that uses Intel NetStructure
DMT160TEC digital telephony interface boards. Refer to Chapter 8, “Tracing CAS Signaling
Using Global Call”.
Collecting system data to diagnose an application failure or crash
You can use the Intel Telecom Subsystem Summary Tool (its_sysinfo) to collect the system
data you will need to send to Intel’s Support Services to troubleshoot an application failure or
crash. Refer to the following:
• Section 7.2, “Collecting System Data to Diagnose an Application Failure or Crash”, on
page 44
• Chapter 21, “Intel Telecom Subsystem Summary Tool Reference”
Collecting ISDN trace information
The ISDNtrace tool described in Chapter 20, “ISDN Trace Reference” allows you to perform
tracing on only one trunk. The procedure described in Chapter 9, “Tracing Multiple ISDN
Trunks Using Global Call” allows you to collect ISDN D-channel trace information on two or
more trunks at the same time and the capture of the trace information can be dynamically