Specifications

System Software Diagnostics Guide — September 2006 47
8
8.Tracing CAS Signaling Using
Global Call
This chapter describes how to trace CAS signaling in systems with Intel NetStructure
®
DMT160TEC digital telephony interface boards using Global Call APIs and a Global Call event.
The following information is provided:
• Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
• Requirements and Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
• Enabling Tracing Using gc_StartTrace( ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
• Disabling Tracing Using gc_StopTrace( ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
• Reporting Trace Data via GCEV_TRACEDATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
• Setting the Trace Queue Size Using gc_SetConfigData( ) . . . . . . . . . . . . . . . . . . . . . . 52
8.1 Introduction
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.
This capability provides a single interface through which every component on a DMT160TEC
board can send trace data to the host in a generic format. The application that runs on the host and
requires the trace data can start and stop the trace as needed using Global Call APIs. Trace data are
presented to the application via a Global Call event and the application is responsible for the
retrieval, processing, and logging of the traced data from the event.
Notes: 1. For more information about Global Call APIs, refer to the Global Call API for Linux and
Windows Operating Systems Library Reference.
2. Chapter 18, “GCEV_TRACEDATA Reference” describes the data layout in the
GCEV_TRACEDATA so that a parser can be designed for viewing the data. A sample parser and
sample parser output is also included.
Some use cases for performing this procedure are as follows:
• Troubleshoot protocol problems that occur after provisioning a span for a new carrier:
After some time of handling traffic, an unused span is provisioned for a new carrier for Least
Cost Routing (LCR). After the span is turned up, protocol problems occur. The protocol for the
inbound and outbound spans must be traced to capture the error condition and determine a fix.
Tracing can occur on two spans on the same board or on different boards. To gain a complete
understanding of the entire call path, the call on the inbound span needs to be traced as well as
the call on the outbound span.