Tracing a SIP proxy server
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.
Note: This topic references one or more of the application server log files. As a
recommended alternative, 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 on distributed and IBM®
i systems. You can also use HPEL in conjunction with your 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.
To trace a SIP proxy server, complete the following steps: