The Trace Information Flow describes the interactions between the Lotus Sametime Unified Telephony System , the Voice-Trace Manager Interface (TM), Users and External Servers.
Telephony Control Server
Trace statements are collected in a trace bufferTelephony Control Server <-> Telephony Control Server-Trace Manager
Trace buffer content is stored in trace files
Trace files are transferred via (S)FTP to the TM Server
Push method with (S)FTP protected by userid and passwordTelephony Control Server-Trace Manager
Only possible to pre-configured Telephony Control ServerTM server identified by IP address. Enforced by Telephony Control Server packet filter rules
Files are deleted once successfully sent or when space is needed for newer files
Trace files are stored in a trace file directoryTelephony Control Server-Trace Manager <-> User
Trace files are deleted after a certain time
Trace files are parsed for external signaling messages and main signaling information is stored in a database (e.g. tme, type of message, DN, CallID, error code)
Data records are deleted when database becomes too big.
Data queries and traffic graphs visible via Web clientTelephony Control Server-Trace Manager <-> External Server
Trace file export via SFTP for trace files identified by time, DN, error code, ...
Statically the number of supported network elements is:
20 Telephony Control ServersParent topic: Data Collection
How to Set DIPAZ Configuration
How to install TM (Lotus Sametime Unified Telephony - Trace Management) on Windows 2008 R2 - Full Installation
How to install TM (Lotus Sametime Unified Telephony - Trace Management) on Windows 2003 - Full Installation
Number of phones is not checked