You can trace
a Session Initiation Protocol (SIP) proxy
server, starting either immediately or after the next server startup.
About this task
By
default, the trace messages do
not include the Authorization and Proxy-Authorization headers. If
you 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. You can also add the hideMessageBody custom
property to the settings for this channel and set it to true if
you do not want the message body included in the trace messages.
New feature: This topic
references one or more of the application server log files. Beginning
in WebSphere Application Server Version 8.0 you can configure the
server to use the High Performance Extensible Logging (HPEL) log and
trace infrastructure instead of using
SystemOut.log ,
SystemErr.log,
trace.log,
and
activity.log files or native z/OS logging
facilities. If you are using HPEL, you can access all of your log
and trace information using the LogViewer command-line tool from your
server profile bin directory. See the information about using HPEL
to troubleshoot applications for more information on using HPEL.
newfeat
To trace a
SIP proxy server, complete the following steps:
Procedure
- Start the product, and open the administrative console.
- In the administrative console, click .
- Select the name of the server for the
SIP proxy server.
- From the General Properties section,
click Diagnostic Trace Service.
- Select one of the following options:
Option |
Description |
Configuration |
To
start tracing after the next server startup |
Runtime |
To start
tracing immediately |
- Replace the content of the trace specification
with the following code: *=info:com.ibm.ws.sip.*=all:com.ibm.ws.proxy.*=all.
- Make sure that the Enable trace
with following specification check box is checked.
- Click .
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 that is running the SIP proxy server
to be traced.