If setting up the Telephony Control Server in TM for the first time all the steps in this section are necessary.
If your Telephony Control Server configuration is a dual node system, you will need to follow this process for each node.
Both nodes are identified by the same "system name" in TM (i.e.:SYS1); therefore, you will need to use the same "system name" when configuring the FTP transfer process.
All trace files for both nodes will be transferred to the same system folder under the \tracedata\<system-name>
Verify connectivity from the Telephony Control Server to the TM server.
Test pinging the TM server:
>ping <TM server IP>
If ping fails, verify your network route configuration and ensure that you have connectivity to the TM server.
If the TM Server lies outside the Admin subnet, it may be necessary to setup a static route to make it accessible.
Contact your Telephony Control Server technician for support if necessary.
Pre-Setup for Trace File Exporting to TM ServerParent topic: Administration Tasks for Trace Management
For Telephony Control Server , the transferring of its traces to the TM server is controlled by a cron job that spawns a FTP session to the TM server. For Telephony Control Server , exporting of trace files to the TM server is done using an active mode FTP session initiated from the Lotus Sametime Unified Telephony system by the oprtt_server process. To allow a connection and transfers to the TM server it is necessary to configure Packet Filtering and Denial-of-Service rules on the Telephony Control Server.
How to Setup Packet Filtering Role for FTP
How to Configure Denial-of-Service Prevention
The TM server's IP address should be added to the Snort whitelist to prevent the triggering of Denial-Of-Service handling when transferring data.
How to Perform an Upgrade Installation