Specifications

System Software Diagnostics Guide — September 2006 55
9
9.Tracing Multiple ISDN Trunks
Using Global Call
This section describes how to collect ISDN D-channel trace information on multiple trunks.
• Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
• Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
• Enabling Tracing Using gc_StartTrace( ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
• Disabling Tracing Using gc_StopTrace( ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
• Reporting Trace Data via GCEV_TRACEDATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
• Setting the Trace Queue Size Using gc_SetConfigData( ) . . . . . . . . . . . . . . . . . . . . . . 60
9.1 Introduction
The ISDNtrace tool described in Chapter 20, “ISDN Trace Reference” allows you to perform
tracing on only one trunk. This procedure 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
started and stopped via Global Call APIs. The trace information collected with this procedure
allows developers to determine the root cause of protocol issues in a system that uses Intel
NetStructure
®
DMT160TEC or DMN160TEC digital telephony interface boards.
Caution: Enabling ISDN tracing on a higher number of trunks will cause the call performance to be severely
degraded and must not be left permanently enabled in a production environment.
Trace data are presented to the application via an event (GCEV_TRACEDATA) and the application
is responsible for the retrieval, processing, and logging of the traced data from the event. Traced
data events will be generated for all signaling frames on the D-channel on both inbound and
outbound calls. Tracing is started by using the gc_StartTrace( ) API after the ISDN firmware
downloads. Tracing is stopped using the gc_StopTrace( ) API. This is described in Section 9.3,
“Enabling Tracing Using gc_StartTrace( )”, on page 56 and Section 9.4, “Disabling Tracing Using
gc_StopTrace( )”, on page 57.
The GCEV_TRACEDATA event is received asynchronously on a board device whenever a Layer 2
(LAP_D) INFORMATION frame is sent or received by the firmware. Refer to Chapter 18,
“GCEV_TRACEDATA Reference” for more information about the structure of
GCEV_TRACEDATA for ISDN.