SIP Protocol Logging with Server Tracer
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
Use Microsoft Office Communications Server Tracer to examine an application's SIP protocol logs, and to collect logs for use in advanced troubleshooting.
To install Server Tracer, install Microsoft Unified Communications Managed API version 1.0 SDK, then use ucmaredist.msi to install the Unified Communications Managed API version 1.0 Redistribution Package. The default installation path for Office Communications Server Tracer is %Program Files%\Microsoft Office Communications Server 2007\Common\Tracing.
To launch Office Communications Server Tracer
On the Windows taskbar, click Start, click Run, type cmd, and then click OK.
At the command prompt, type cd \Program Files\Microsoft Office Communications Server 2007\Common\Tracing, and then press ENTER.
Enter the appropriate OCSTracer.exe syntax, and then press ENTER.
Displaying OCSTracer.exe Help
To display the top level Help text for OCSTracer.exe syntax, at the command prompt type ocstracer and then press ENTER.
To display Help text for individual OCSTracer.exe commands, see the following example.
ocstracer list /?
Changing the Log File Directory
By default, log files are written to the directory %WINDIR%\Tracing. To change the directory log files are written to, modify the LogFileFolder attribute in the OCSTracer.ini file. By default, OCSTracer.ini is installed in the same directory as OCSTracer.exe.
Examples
//Start tracing for S4 and Collaboration.
OCSTracer.exe start /Component:S4 /Component:Collaboration
//Stop tracing.
OCSTracer Stop
//Convert an .etl file to a .txt file.
OCSTracer.exe format /LogFilePath:S4.etl /OutPutFile:S4.txt