Tracing a SIP container

We can trace a Session Initiation Protocol (SIP) container, starting either immediately or after the next server startup. This tracing writes a record of SIP events to a log file.

Follow these steps to start tracing a SIP container:

 

1. Open the admin console.

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

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

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

5. Under the Additional Properties section, click Change Log Detail Levels

6. Select one of the following options:

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

7. Replace the content of the trace specification with the following code: com.ibm.ws.sip.*=all=enabled.

   If we want monitor only specific pieces of SIP containers, expand the com.ibm.ws.sip section and select the individual items you wish to trace.

8. Make sure that the Enable trace with following spec check box is checked.

9. Click Apply > Save.

 

Next steps

When the changes take effect (refer to step 6 above), SIP-level tracing messages appear in WASProductDir/logs/serverName/trace.log, where WASProductDir is the fully qualified path name of the directory in which WAS is installed and serverName is the name of the specific instance of the appserver that is running the SIP container to be traced. These messages include application load events as well as SIP request and response parsing and SIP servlet invocation.

 

Related tasks

Set the SIP container
Browse all SIP topics