1. Download SIPViewer from http://sipxecs.sipfoundry.org/temp/sipXecs/sipviewer-install.jar
2. or from [Download]
3. The SIP messages are logged by sipXecs components at the INFO logging level; this is a more verbose level than the default NOTICE level. The log level can be changed in the Web UI by going to "System/Logging Level/General Logging Level/ --> set to INFO". You must restart the components for the change in logging level to take effect.
To get useful trace information, at least the proxy and registrar must be set at INFO or DEBUG (INFO is sufficient for traces, and makes for much smaller log files). You should also have detailed logging for any other component you suspect to be involved in the problem.
4. If you can get the time a problem call is made, a good way to find it is to look in the proxy log file by searching the list of dialogs with the sipx-dialog-count command: sipx-dialog-count /var/log/sipxpbx/sipXproxy.log
5. it will print a list like this:
Dear Friend,
6. Then use 'sipx-trace' to create an xml file that contains trace data for messages on your system:
sipx-trace --all-components --output
example:
sipx-trace --all-components --output trace.xml c23be57c-32cb158c@172.17.2.75
trace.xml is the file captured
7. Find the file by name.extension ---> [root@sipsvr /]# find . -name 'testing.xml'
8. [root@sipsvr /]#
[root@sipsvr /]# ls
bin dev home lost+found misc net proc sbin sipacdreportpatch.log sys testing.xml tftpboot usr
boot etc lib media mnt opt root selinux srv test test.xml tmp var
[root@sipsvr /]#
9. then get the file by secure PUTTY [download]
10. the user SIP Viewer to parse the SIP trace file 'testing.xml' then file > open SIPtrace file
11.
