Installation guide
Table Of Contents
- About This Publication
- Document Revision History
- 1. Post-Release Developments
- 1.1 Service Update for Dialogic® System Release 6.1 CompactPCI for Windows®
- 1.2 PDK Support for Automatic Answer and Reject of Inbound Calls
- 1.3 Status Monitor Tool Support for 16 Span Boards
- 1.4 Improvement to Call Progress Analysis
- 1.5 Media Load Support for the Dialogic® DM/V1200A- 4E1-cPCI Board
- 1.6 Handling non-2xx Responses to T.38 Switch
- 1.7 Important Notice about System Release Update Installation
- 1.8 Media LAN Disconnection Alarm Notification for Dialogic® DM/IP Boards
- 1.9 Support for SFTP in Dialogic® Global Call SS7 Call Control Library
- 1.10 New Media Loads for Dialogic® DM/V4800BC Media Boards Using Special Coders
- 1.11 File Management Enhancements for DebugAngel Tool
- 1.12 File Management Enhancements for PDK Trace Tool
- 1.13 Configuring SIP Stack Parameters with Global Call
- 1.14 Disabling Automatic re-INVITE Message when Switching between Fax and Audio
- 1.15 IP Multicast Client Support
- 1.16 Troubleshooting Information for RTF Logs
- 1.17 Remote Diagnostics Package
- 1.18 Enhanced Diagnostics Tools
- 1.19 New QoS Alarms for RTCP and RTP Inactivity
- 1.20 New Operating System Support
- 1.21 Support for Compute Platforms
- 1.22 New Parameter for Adjusting Silence Threshold on Dialogic® DM3 Boards
- 1.23 File Management Enhancements for ISDNtrace Tool
- 1.24 New Media Loads for Dialogic® DM/V2400A-cPCI and DM/V4800BC Media Boards
- 1.25 Modified Alarm Events for Media LAN Disconnect
- 1.26 Enhancement to its_sysinfo Tool
- 1.27 Modify an Existing SIP Call Using re-INVITE for Dialogic® IPT Boards
- 1.28 PDK Log File Detection
- 1.29 Media Channel Reset Capability (Stuck IP Media Channel Recovery)
- 1.30 Dialogic® Global Call API Access to New H.323/Q.931 Message IEs
- 1.31 On-Demand Full Reset of Dialogic® DM3 Boards
- 1.32 New Dialogic® Diagnostics Management Console
- 1.33 New Runtime Trace Facility (RTF) Manager
- 1.34 Support for Reporting Billing Type
- 1.35 Runtime Control of Double Answer for R2MF
- 1.36 Additional Supported Operating System Security Updates
- 1.37 Media Channel Reset Capability (Stuck Channel Recovery)
- 1.38 Notification of Layer 1 Alarm Events on Dialogic® SS7 Boards
- 1.39 Dialogic® Global Call Support for Time Slots on Dialogic® SS7 Boards Running in DTI Mode
- 2. Release Issues
- 3. Documentation Updates
- 3.1 System Release Documentation Updates
- 3.2 Installation and Configuration Documentation Updates
- 3.2.1 Dialogic® System Release 6.1 CompactPCI for Windows® Software Installation Guide
- 3.2.2 Dialogic® DM3 Architecture for CompactPCI on Windows® Configuration Guide
- 3.2.3 Dialogic® IPT Series on Windows® Configuration Guide
- 3.2.4 Dialogic® Global Call Country Dependent Parameters (CDP) for PDK Protocols Configuration Guide
- 3.3 OA&M Documentation Updates
- 3.3.1 Dialogic® System Release 6.1 CompactPCI for Windows® Administration Guide
- 3.3.2 Dialogic® SNMP Agent Software for Windows® Administration Guide
- 3.3.3 Dialogic® System Software Diagnostics Guide
- 3.3.4 Dialogic® Board Management API Library Reference
- 3.3.5 Dialogic® Event Service API Programming Guide
- 3.3.6 Dialogic® Event Service API Library Reference
- 3.3.7 Dialogic® Native Configuration Manager API Programming Guide
- 3.3.8 Dialogic® Native Configuration Manager API Library Reference
- 3.4 Programming Libraries Documentation Updates
- 3.4.1 Dialogic® Audio Conferencing API Programming Guide
- 3.4.2 Dialogic® Audio Conferencing API Library Reference
- 3.4.3 Dialogic® Continuous Speech Processing API Programming Guide
- 3.4.4 Dialogic® Continuous Speech Processing API Library Reference
- 3.4.5 Dialogic® Digital Network Interface Software Reference
- 3.4.6 Dialogic® Fax Software Reference
- 3.4.7 Dialogic® Global Call API Programming Guide
- 3.4.8 Dialogic® Global Call API Library Reference
- 3.4.9 Dialogic® Global Call E1/T1 CAS/R2 Technology Guide
- 3.4.10 Dialogic® Global Call IP Technology Guide
- 3.4.11 Dialogic® Global Call ISDN Technology Guide
- 3.4.12 Dialogic® Global Call SS7 Technology Guide
- 3.4.13 Dialogic® IP Media Library API Programming Guide
- 3.4.14 Dialogic® IP Media Library API Library Reference
- 3.4.15 Dialogic® Modular Station Interface API Programming Guide
- 3.4.16 Dialogic® Modular Station Interface API Library Reference
- 3.4.17 Dialogic® Standard Runtime Library API Programming Guide
- 3.4.18 Dialogic® Standard Runtime Library API Library Reference
- 3.4.19 Dialogic® Voice API Programming Guide
- 3.4.20 Dialogic® Voice API Library Reference
- 3.5 Demonstration Software Documentation Updates
- 3.5.1 Dialogic® Continuous Speech Processing API Demo Guide
- 3.5.2 Dialogic® Global Call API Demo Guide
- 3.5.3 Dialogic® High Availability for Windows® Demo Guide
- 3.5.4 Dialogic® IP Gateway (Global Call) Demo Guide
- 3.5.5 Dialogic® IP Media Server (Global Call) Demo Guide
- 3.5.6 Dialogic® IP Media Gateway (IPML) Demo Guide
Dialogic
®
System Release 6.1 CompactPCI for Windows
®
Release Update 46
New and Enhanced Command Line Options
Two new command line options, -a and -m, have been added for PDK Trace, and the -f
option has been enhanced to allow log file management as follows:
-a#
Log file array size, specifies the maximum number of log files to maintain (optional).
The default value is 1, and the maximum value is 10.
Example:
pdktrace -b0 -f[ExampleLog] -a5
If left default (or explicitly set to 1), then PDK Trace creates a single log file that grows
without bound (that is, no limit to the log file size).
If set greater than 1 (up to 10), then PDK Trace creates an initial log file at startup.
When the log file reaches the maximum file size (either the default maximum log file
size or the value specified via the -m command line option), the log file is closed and
saved, and a new log file is created.
When the maximum number of log files (as specified by this setting) is reached, the
oldest log file is deleted and a new log file is created to replace it.
Note: When the -a option is specified, any PDK Trace log files that exist prior to
running this particular PDK Trace session are not deleted or modified in any
way.
-m#
Specifies the maximum log file size in bytes (optional). The default depends on the
setting of the -a option, as follows:
• For -a1 (one log file), the default maximum file size is unlimited.
• For -a2 through -a10 (multiple log files), the default maximum file size is 100
megabytes.
The minimum that can be specified with the -m option is 100 kilobytes, and the
maximum is 100 megabytes.
Example:
pdktrace -b0 -f[ExampleLog] -a5 -m500000
-f[filename]
Specifies the name of a file on the host system to write the trace data to (optional).
The default is pdktrace.log. The “.log” extension is appended to the specified file
name string when creating the file.
If just a file name is specified, the log file will be created in the current directory where
PDK Trace is being run from. However, if a path (either relative or absolute) is
specified with the file name, then the log file will be created in the specified directory.
This option existed in the previous version of PDK Trace. However, the processing
associated with this option has been modified to include date and time information, for
management of multiple log files.
When the -a or -m option is used, the file name will automatically have a timestamp
with the current date and time added to it. The “.log” extension will be appended to the
end of the log file name. A file name with a timestamp has the following format:
filename-MMDDYYYY-xxhyymzzs.log
where:
• filename - the name specified with the -f option (or the default if -f is not used)
• MM - month (01=January, 02=February, 03=March, … 12=December)