Tracing a SIP proxy server

We can trace a SIP proxy server, starting either immediately or after the next server startup.

By default, the trace messages do not include the Authorization and Proxy-Authorization headers. If we also do not want the other SIP message headers to appear in the trace log, add the SIP UDP transport channel custom property hideMessageHeaders custom property to the settings for the SIP inbound channel (SIP 1) and set the property to true. We can also add the hideMessageBody custom property to the settings for this channel and set it to true if we do not want the message body included in the trace messages.

IBM recommends using the High Performance Extensible Logging (HPEL) log and trace infrastructure . We view HPEL log and trace information using the logViewer .

To trace a SIP proxy server:

Tasks

1. Start the product, and open the administrative console.

2. In the administrative console, click Troubleshooting > Logs and trace.

3. Select the name of the server for the SIP proxy server.

4. From the General Properties section, click Diagnostic Trace Service.

5. Select one of the following options:

   Option	Description
   Configuration	To start tracing after the next server startup
   Runtime	To start tracing immediately

6. Replace the content of the trace specification with the following code: *=info:com.ibm.ws.sip.*=all:com.ibm.ws.proxy.*=all.

7. Verify the Enable trace with following specification check box is checked.

8. Click Apply > Save.

What to do next

When the changes take effect, SIP proxy server tracing messages display in WASProductDir/logs/serverName/trace.log on the SIP proxy server node, where WASProductDir is the fully-qualified path name of the directory where the product is installed and serverName is the name of the specific instance of the application server running the SIP proxy server to be traced.

Use the administrative console

Use High Performance Extensible Logging to troubleshoot applications