From SIPfoundry sipXecs IP PBX, The Open Source SIP PBX for Linux - Calivia

Single most important tip for troubleshooting is inspect log files.

You'll find all the log files in

/var/log/sipxpbx

To change the logging level, log into web ui, assuming you can access the web ui, and navigate menu to

System/General

And you should see something like the following UI (there may be different components depending on how your system is installed and the version you are running)

Setting the log level for a component to INFO will record all the SIP messages it sends and receives in the log. The DEBUG level is very verbose, and mostly of interest to software developers; INFO is sufficient for debugging most configuration problems.

How to debug a call

Once you change the log level, stop sipXpbx and move the existing log file aside, then restart sipXpbx so that you have a clean log. Make a call, then look at the log file

syslogviewer -i < /var/log/sipxpbx/sipXproxy.log | less

Make sure you set the log level back to NOTICE when done or your logs will take much more disk space. At high logging levels you may see a significant performance degradation when under high load.

For interpreting call flows, you can also Display SIP message flow using Sipviewer

Setting log level for Web UI - sipXconfig

By default sipXconfig is configured with NOTICE logging level. You can temporarily increase logging level by editing /etc/sipxpbx/sipxconfig-jetty.xml file. Fine the following lines:

  <!- - set to true to enable sipxconfig logging -->
  <Set name="debug">false</Set>

and set debug to true

  <Set name="debug">true</Set>

sipXconfig 3.4 Logging Level

 # legal values (highest to lowest): debug info warn error fatal
 log4j.rootLogger=debug, file

Setting log level for mediaserver

Edit

/etc/sipxpbx/voicemail.xml.in

and change the voicemail-cgi-log-level XML element to this:

<voicemail-cgi-log-level>DEBUG</voicemail-cgi-log-level>

then restart mediaserver