Troubleshooting Direct SIP to an IP-PBX 101

Here is a quick getting-started reference for debugging direct SIP traffic between OCS and an IP-PBX.

OCSLogger.exe Overview

The Office Communications Server 2007 R2 Logging Tool (OCSLogger.exe) is installed by default on most OCS server roles. It can be used to capture logging and tracing information while the server is running. You can analyze protocol logs for the following components:

  • Office Communications Server SipStack (SIP)
  • Office Communications Server S4 (SIP)
  • Office Communications Server Conferencing signaling traffic (C3P), including MCU Infra C3P and Focus C3P
  • Office Communications Server Web conferencing traffic (PSOM)
  • Office Communications Server Unified Communications Client Platform client (UCCP)
  • Error reports from the archiving database

To Start a Debugging Session

1 .Run the OCS logging tool: OCSLogger.exe. It is located in “%ProgramFiles%\Common Files\Microsoft Office Communications Server 2007 R2\Tracing”
2. Set a folder for the OCSLogger.exe log files (e.g. C:\Windows\Temp)
3. Select your logging level:  If you are trying to debug a problem, start with just “Errors”. If you are investigating something, start with “All”

To View the Incoming SIP traffic from the IP-PBX to the OCS Mediation Server & the Protocol Traffic from the OCS Mediation Server to the OCS Front-End

4. Select the following Components in the Logging Options:

  • Mediation Server (this will give all the Mediation server protocol in/out processing)
  • S4 (this will log the SIP protocol requests – including the SIP traffic to/from the IP/PBX)

5. Select “Start Logging” and place a sample call. Select “Stop Logging” after the sample call is finished.
6. After you have ended the debug session, click Analyze Log Files to view the log files. Note, the Snooper tool is launched to view the log files.
7. Notes:

  • The underlying log files are in .ETL format.
  • The times displayed in OCSLogger are in GMT!

View the Protocol Communication and Internal Tracing of the Microsoft Office Communicator End-point

When debugging direct SIP sessions, it is also useful to see the full end-to-end information. In some circumstances the call will make it through to the Communicator end-point, and Communicator will reject the call. Do view the internal tracing of the Communicator end-point:

1. Turn on tracing in Microsoft Office Communicator 2007 R2: Tools | Options | General | Turn on logging in Communicator.
2. Navigate to the Communicator 2007 R2 trace file directory (i.e. C:\Users\<user-id>\Tracing)
3. Open the most recent Communicator trace file named Communicator-uccapi-<integer>.uccapilog with the Snopper.exe tool. Snooper.exe is a tool included in the OCS 2007 R2 Resource Kit that can be used to help you analyze SIP and C3P protocol logs.
4. Note: the Resource Kit installed into “C:\Program Files\Microsoft Office Communications Server 2007 R2\ResKit”.

More Information

Share and Enjoy:
  • Twitter
  • Digg
  • StumbleUpon
  • del.icio.us
  • Facebook
  • LinkedIn
  • MySpace
  • Reddit
  • Technorati

Leave a Reply

 

 

 

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>