Installation guide

Dialogic
®
System Release 6.1 CompactPCI for Windows
®
Release Update 140
Update to Chapter 12, DebugAngel Reference
Because of a new feature in the Service Update, the DebugAngel tool has been
enhanced to provide more capabilities for managing multiple log files. For more
information about this feature, see Section 1.11, “File Management Enhancements for
DebugAngel Tool”, on page 40 of this Release Update.
Update to Chapter 20, ISDN Trace Reference
Because of a new feature in the Service Update, the ISDNtrace tool has been
enhanced to include new command line options to set the output log file size and to
create multiple backup log files to be archived. For more information about this
feature, see Section 1.23, “File Management Enhancements for ISDNtrace Tool”, on
page 66 of this Release Update.
Update to Chapter 21, Telecom Subsystem Summary Tool Reference
Because of an enhancement in the Service Update, the its_sysinfo.htm file now
includes a Windows Package Info section at the beginning of the file. For further
information about this feature, see Section 1.26, “Enhancement to its_sysinfo Tool”,
on page 75 of this Release Update.
Update to Chapter 24, PDK Trace Reference
Because of a new feature in the Service Update, PDK Trace has new command line
options to set the output log file size and to create multiple log files. For more
information about this feature, see Section 1.12, “File Management Enhancements for
PDK Trace Tool”, on page 45 of this Release Update.
Update to Chapter 26, PSTN Diagnostics Tool Reference
An enhanced version of the PSTN Diagnostics tool (pstndiag) is provided in the
Service Update. The previous version of the tool is still supported. For information
about the new version, see Section 1.18, “Enhanced Diagnostics Tools”, on page 59
of this Release Update.
Update to Chapter 28, Runtime Trace Facility (RTF) Reference (IPY00037518)
The following information about using binary log files should be added to Section
28.3.2, Logfile Tag:
For installations with high channel densities, or which have enabled all or most RTF
trace levels, the volume of logging may result in an increased CPU utilization by the
RtfServer executable as a result of the increased volume of log messages.
As shipped, the RTF log files are generated in ASCII text mode. There is a
configuration parameter in the RTF configuration file (RtfConfigWin.xml for Windows,
RtfConfigLinux.xml for Linux) that allows log files to be generated in either “text” or
“binary” format. Testing on high channel density systems with most or all of the RTF
trace levels enabled has shown that the generation of binary format RTF log files has
less of an impact on CPU usage than does the generation of text format RTF log files.
If the volume of logging results in high CPU usage, then using binary format will
reduce the usage.
Enabling Binary Format RTF Log Files
The XML file contains the following line, which allows changes to log file parameters
to be made:
<Logfile path="$(INTEL_DIALOGIC_DIR)\log" size="300" maxbackups="10"
preserve_size="300" preserve_maxbackups="10"
duplicate_to_debug_console="0" log_format="text" />