Specifications

48 System Software Diagnostics Guide — September 2006
Tracing CAS Signaling Using Global Call
• Trace newly deployed spans to make sure there are no protocol issues: A new platform
consisting of 32 E1s is deployed. All spans are turned up at about the same time. All active
spans are traced for up to the first minute of operation to determine if there are any protocol
issues.
8.2 Requirements and Restrictions
Following are the prerequisites for performing this procedure:
• Intel® Dialogic® System Release
• At least one Intel NetStructure DMT160TEC digital telephony interface board
• The following registry setting modification is required to support this feature’s functionality:
HKEY_LOCAL_MACHINE\SOFTWARE\Dialogic\Cheetah\MaxMMBReplySize
The value should be changed from 0x200 (512 decimal) to 0x400 (1024 decimal).
If you use this feature without modifying the registry key, you will get the following failure
event notifications: GCEV_TASKFAIL.
• The application is responsible for starting and stopping the tracing. This is done using Global
Call APIs.
• Traced data will be presented to the application via an event (GCEV_TRACEDATA).
• The application will be responsible for retrieving, processing, and logging the traced data
returned as a result of the traced data event.
• System performance dictates the maximum spans that can be traced. This will be determined
empirically.
8.3 Enabling Tracing Using gc_StartTrace( )
The gc_StartTrace( ) function starts the logging of debug information for a specific line device.
To use this feature, the line device must be the handle for a trunk or virtual board and the
tracefilename pointer should be set to NULL. After gc_StartTrace( ) returns success, instead of
logging to a file, the application will be notified of the availability of trace data via
GCEV_TRACEDATA. The trace will continue until a gc_StopTrace( ) function is called.
Sample application code
Note: The following sample code was written for an application running on a system in which an Intel
NetStructure DMT160TEC board was used as the network interface, an Intel NetStructure
DMV2400A board was used as a play/record resource board, and the boards were connected via a
CT Bus.
#include <stdio.h>
#include <srllib.h>
#include <gclib.h>
#include <gcerr.h>