System Release 6.1 cPCI for Windows Release Guide — May 2006 28
runtime libraries that are supported by System Release 6.1 cPCI for Windows.
Support for the RTF tool is as follows:
• Rtftool command is used to stop/start the RTF tool’s tracing capabilities
• provides centralized logging for key OA&M components (OAMSYSLOG)and IP
libraries
• run the RTF tool in preservation mode. Preservation mode allows you to save
specified RTF trace information into a separate, preserved log file while the RTF
engine continues to output active trace information into the default log file. The
RTF engine will not overwrite, delete or append to the preserved log file after it
has been saved.
• trace the Audio Conferencing API (DCB) library.
Runtime Trace Facility (RTF) Output
The presentation of the trace data has been made consistent. The trace format is
identical for a given type of tracing, regardless of the library generating the trace.
Ability to trace inbound and outbound R2MF tones and CAS bit transitions/states
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.
Note: Supported on DMT160TEC only.
Ability to trace multiple ISDN trunks and enable/disable tracing via APIs
The capture of ISDN D-channel trace information can now be dynamically started and
stopped via Global Call APIs, and logs can be collected on two or more trunks at the
same time. Previously, the only available tool for collecting ISDN trace information
(isdntrace) could not be run on more than one trunk. This trace information allows
developers to determine the root cause of protocol issues in a system that uses Intel
NetStructure
®
DMT160TEC or DMN160TEC digital telephony interface boards (no
other boards support this feature).
Hardware diagnostic improvements
The DM3post tool can now run POST on an entire chassis. The autodump feature of
the dlgsnapshot tool is now disabled by default. However, you still have the option of
enabling the autodump feature if you want to use it. In the default state, no board or
DSP will be automatically reset as a result of a DSP failure. Previously, the entire
board would be brought down if a single DSP failed.
PDK protocol tracing on DM3 now supports Intel NetStructure
®
DMT160TEC boards
The DM3 PDK Protocol Trace (PDK Trace) tool allows those who use a DM3 PDK
protocol to log specific information related to the operation of the protocol. This tool
can now be used with DMT160TEC boards.
Note: PDK Tracing will work on any of the following products with a PDK protocol
loaded: Intel NetStructure
®
DM/V, DM/V-A, DM/V-B, DM/F, and DMT160TEC
boards. PDK tracing is not supported for Intel NetStructure
®
DM/IP boards
and Intel NetStructure
®
on DM3 architecture analog boards.
