This documentation is archived and is not being maintained.

Debugging a SIP Application

Office 2003
Microsoft Office Live Communications Server 2005 with SP1

Debugging a SIP Application

Debugging Threaded SIP Applications

To assist with debugging threaded SIP applications, the ApiLogger.exe utility is provided with Live Communications Server. For information on the errors found in the log displayed with ApiLogger.exe, see Using ApiLogger.exe. Several major application logic errors are recorded in the error log.

In the application manifest, SIP messages can be logged by before being dispatched (via the Dispatch function) to the application simply by calling the Log function before the dispatch.

Log("Debug", true);

The level of detail for each message in the log is set with the second parameter. If it is false, only the "Method", "To, "From", and "Request-Uri" headers are logged, along with the date/time and the application URI. If it is true, the entire SIP message will be logged.

The third and subsequent parameters contain optional developer messages that can be entered in the log along with the SIP message. These developer messages can contain searchable keywords or additional information that can be used to filter the log file and determine problematic situations.

  What did you think of this topic?
  © 2008 Microsoft Corporation. All rights reserved.