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)
• DD - day of the month (01-31)
• YYYY - year (e.g., 2008)
• xx - hour (24-hour format, 00-23)
• yy - minute (00-59)
• zz - second (00-59)
Example: If PDK Trace is started on February 17, 2008, at 3:11:27 p.m., with the -f command line option of -f[ExampleLog], the name of the first log file created is:
ExampleLog-02172008-15h11m27s.log
When this file reaches the maximum size, it is closed and a new log file is created.
The new log file will have a timestamp with the current date and time in its file name.
1.28.2 Documentation
The online bookshelf provided with Dialogic® System Release 6.0 PCI for Windows® contains information about all system release features including features for application development, configuration, administration, and diagnostics.
For more information about PDK Trace, see the Dialogic® System Software Diagnostics Guide.
1.29 Runtime Control of Single or Double Hookflash on Consultation Drop for FXS/LS Protocol
With the Service Update, runtime control of sending either a single or double hookflash when dropping a consultation call on a supervised transfer is now supported for Dialogic® DM3 Boards using the United States T1 FXS/LS Bidirectional protocol. For further information about this feature, see the Dialogic® E1/T1 CAS/R2 Technology Guide.
1.30 Analog Call Transfer Support on Dialogic ® Springware Boards
With the Service Update, blind and supervised analog call transfers using the Dialogic® Global Call API are now supported on Dialogic® Springware Boards. For further information about this feature, see the Dialogic® Global Call Analog Technology Guide.
1.31 Support for Windows ® 7, Windows Vista ® , and Windows Server ® 2008 Operating Systems
With the Service Update, Dialogic® System Release 6.0 PCI for Windows® supports the Windows® 7, Windows Vista®, and Windows Server® 2008 operating systems. The following versions are supported:
• Windows 7 Ultimate
• Windows Vista Business SP1
• Windows Vista Ultimate SP1
• Windows Server 2008 Enterprise
• Windows Server 2008 Standard, Full Version
The following sections highlight some of the differences that users will see when running System Release 6.0 PCI Windows on Windows7, Windows Vista, or Windows Server 2008, as opposed to running on other Windows® operating systems.
• Hardware Requirements
• Supported Boards
• Application Considerations in 64-Bit Mode
• Separate Install Media
• Content Split into Different Locations
• Changes to Environment Variables
• Building Applications
• Consent Dialog
• UDD Not Supported
• Remote DCM Not Supported
• Physical Address Extension (32-Bit OS Versions Only)
If you plan to move existing applications to Windows7, Windows Vista, or Windows Server 2008, see:
• Guidelines for Moving Applications to Windows 7, Windows Vista, or Windows Server 2008
1.31.1 Hardware Requirements
A minimum of 2 GB RAM is required when running System Release 6.0 PCI Windows on Windows7, Windows Vista, or Windows Server 2008.
Note: For Dialogic® DM/V-B Board users: If your system has the required 2 GB RAM but DM/V-B Boards fail to download, the board may have an older boot kernel that requires updating. What happens when using Dialogic® Configuration Manager (DCM), for example, is that when you click the green (Start System) button, the progress bar will go on forever because the board is not detected. If this happens, contact Technical Support to return the board to have a new boot kernel installed.
Refer to http://www.dialogic.com/support/hwfaults/ for the Return Material Authorization (RMA) process.