Configuration of Lotus Sametime Unified Telephony-Trace Management needs a Setting Up Tracing for the Telephony Control Server with the steps Pre-Setup for Trace File Exporting (FTPing) to TM Server, Setup a Packet Filtering Rule for the FTP connection, Configure Denial-Of-Service Prevention and the Configuration for Telephony Control Server R2 and R3.
Transfer Tracing Scripts to the Telephony Control ServerParent topic: Administration Tasks for Trace Management
The set of tracing scripts needed to be copied to configure continuous tracing in Telephony Control Server is based on the installed patch set level.
Setup Tracing and Configure FTP Transfer to TM Server
When tracing is enabled, the RTT trace files are stored in a local directory in the Telephony Control Server (/software/RTT/). The two scripts (setup_tracing.ksh and setup_trace_transfer.ksh) copied from the TM installation folder need to be run to enable tracing and setup the ftp jobs to transfer the trace files to the TM server for processing and analysis.
Configuration Script "setup_tracing.ksh"
The "setup_tracing.ksh" script calls the 24_7_extern script (default) which enables a subset of trace facilities and flags for ccm and ttudProc. The script also calls OP_RTT_READ with the parameters of 75 files, 10 Mb file size, and file wrapping enabled. If the user wants to change these default values then the script needs to be rerun. The setup_tracing.ksh script has two optional parameters: the tracing mode/level (-24_7|-24_7_extern|-24_7_min) and the tracing file size.
Transfer Script "setup_trace_transfer.ksh"
The "setup_trace_transfer.ksh" script modifies the .netrc file, and creates a second script that is run via a cron job. This cron script compresses the raw trace files, sends the trace files via ftp to the TM server, deletes the ftp'ed files from the local directory (/software/RTT/), and generates a ".pid" file to keep track of the transfers. The ftp transfer script maintains a log file in /var/log/rttftp.log.
How to Set Script Permissions and Modes