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 68
Details about these command line options follow:
-a<n>
This command line option allows the user to specify the maximum number of log files
to maintain.
The user can specify a log file array size between 1 and 10. By default, the number of
log files to be archived is 1. If the user specifies the -f command line option but does
not specify this option (or specifies it with an array size of 1), then ISDNtrace creates
a single log file that grows without bound (that is, no limit to the log file size).
If the user specifies this option with an array size greater than 1 (but less than or equal
to 10), then ISDNtrace 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 a new log file is created.
Whenever ISDNtrace attempts to open a new log file, it first checks to see if the
current number of log files created is equal to the number of files specified for the log
file array. If not, then the new log file is created. Otherwise, the oldest log file is
deleted and a new log file is created to replace it.
It should be noted that any ISDNtrace log files that exist prior to running the
ISDNtrace tool are not deleted or modified in any way. Due to the new log file naming
convention (see -f option), all ISDNtrace log files have unique timestamps in their log
file names and are not overwritten when ISDNtrace starts up.
-f <file>
This option existed in the previous versions of ISDNtrace. However, the processing
associated with this option has been modified to include date and time information.
This command line option specifies the log file name of the log file into which the trace
can be captured. If this option is not specified on the command line, then no trace
output will be saved to a log file.
The naming of ISDNtrace log files has been modified to fit the following format:
<File>-MMDDYYYY-xxhyymzzs.log
where:
• MM - current month (01=Jan, 02=Feb, 03=Mar, … 12=Dec)
• DD - current day of the month
• YYYY - current year (e.g., 2006)
• xx - current hour in day (24 hour format, 00-23)
• yy - current minute in hour (00 - 59)
• zz - current second in minute (00 - 59)
In the description above, the log file name is what the user specified on the command
line. If the user specifies a -f command line option as the last parameter on the
command line and does not specify a log file name, then the default log file name of
ISDNTRACE will be used.
Note: In order to get a default log file name, the -f option has to be used at the end
of the command line.
For example, if the user started ISDNtrace specifying the -f command line option
without a log file name on January 17, 2007 at 03:11:27 pm, the log file created would
be:
isdntrace-01172007-15h11m27s.log