Trace data offers a deep insight to the system and the user's sensitive data.
Access to the data and safeguards for the data
Trace data files stored in Telephony Control Server directory:
Only accessible with ‘srx' and ‘root' access
Trace data files stored on TM server:
Only accessible to Windows user “tracedata” or “administrator”
Local Read only allowed for Windows user “administrator” and SQLite account user
Web read with userid and pw from the FADE account (offers the two roles admin and user)
Remote Trace Analysis:
only via remote desktop to server (Windows administrator) and Web client (disabled by default)
Storage of Data
The TM database only stores trace data taken from external SIP, CSTA and MGCP messages. Future enhancements may add additional traces; e.g. resource data like CPU usage or signaling messages between main Telephony Control Server SW processes such as SIPSM and UCE.
Non-message data are only statistics derived from the messages and links to the associated trace files.
The trace files contain additional data useful for development debugging. There is no difference between the trace files stored on the TM server and the files stored on the Telephony Control Server disk.
Approach to data storage and use
Trace files stored on the Telephony Control Server and on the TM server are deleted automatically after a configurable number of days (default is 10 days on TM) or when space is needed for newer trace files.
Trace files are stored to be made available for error debugging by Telephony Control Server development.
Trace data stored in the TM database are used to display network signaling traffic and statistics.
Storage Size of Trace manager
The size of trace data storage is dependent of whether the files are gzipped or not. Unzipped trace files size is 20 MB, zipped file size is about 3 MB.
A 1 TByte drive is recommended for the TM server.
One SIP call may produce about 1 MByte of trace data.
Trace Configuration - Privacy Concerns
Information stored in trace files can be used to find out who called who, how often a call was placed, when a call was placed, for how long a call was up before cleared/disconnected, and what features were used on a call. Therefore it is necessary to discuss trace file collection issues with the customer during service contract negotiations up front. The local customer representative has the proper authority to discuss and decide about trace details and export of trace files when the need arises.
Safety - Password Concerns
Userid and password for the Telephony Control Server to TM trace file copy are stored on the Telephony Control Server disk and only readable by the administrator.