> From: sipx-users-boun...@list.sipfoundry.org > [sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net > [m...@grounded.net] > > >>?6) Do "merge-logs --ft=[extension] --include-method=register", where > >>?[extension] is the extension of the phone in question. ?This extracts > >>?the REGISTER requests and their responses which have From or To fields > >>?containing [extension]. > > I cannot tell which phone the call came in to.
If you have observed a phone disappearing from the Active Registrations screen (as instructed in step (2)), you'd know which phone was involved: > >>?2) Wait for the problem to be manifest, that is, a phone is first seen > >>?and then later not seen on the Active Registrations screen without any > >>?explanation. However, that isn't something to worry about at this moment. > As suggested in the past, I am rotating the logs prior to this test. > logrotate -f /etc/logrotate.d/sipxchange If you are having registration problems, it's best not to do that. The reason is that the underlying problem with registrations may have happened an hour or two previously, and when you extract the snapshot, it only sees the latest log files. In general, you should trust the snapshot process's ability to extract the time period of interest. (Actually, your registration problem is almost certainly due to your clock problem. But the empty output from merge-logs is due to something else, and I'm pursuing that right now.) > >>?4) Un-gzip and un-tar the snapshot file in some convenient directory > >>?on the system. > > I unpacked it in /new/snapshot > I also went to the history menu to see what the last call was but > >>sipx doesn't seem to have logged it. > > >>?5) cd to var/log/sipxpbx in the unpacked snapshot. > > Do you mean where I just put the files instead of the sipx log dir. > So, this should be /new/snapshot/var/log/sipxbpx then, right? Yes. > Here is the output. Same as before, nothing in merged.xml. > > # merge-logs --ft=xxxxxx1760 --include-method=register > > # ls -la > total 20008 > drwxr-xr-x 2 sipxchange sipxchange 4096 Jul 7 11:27 . > drwxr-xr-x 3 sipxchange sipxchange 4096 Jul 7 11:02 .. > -rw-r--r-- 1 sipxchange sipxchange 0 Jul 7 11:02 freeswitch_http.log > -rw----r-- 1 sipxchange sipxchange 778 Jul 7 11:02 freeswitch.log > -rw-r--r-- 1 sipxchange sipxchange 256 Jul 7 10:47 httpd_access_log > -rw-r--r-- 1 sipxchange sipxchange 286 Jul 7 10:47 httpd_error_log > -rw-r--r-- 1 sipxchange sipxchange 2768 Jul 7 10:47 httpd_rewrite_log > -rw-r--r-- 1 sipxchange sipxchange 0 Jul 7 11:02 httpd_stderr_log > -rw-r--r-- 1 sipxchange sipxchange 0 Jul 7 11:02 httpd_stdout_log > -rw-r--r-- 1 root root 79 Jul 7 11:27 merged.xml > -rw-r--r-- 1 sipxchange sipxchange 10727448 Jul 7 11:02 sipregistrar.log > -rw-r--r-- 1 root root 79 Jul 7 11:27 sipregistrar.xml > -rw-r--r-- 1 sipxchange sipxchange 167562 Jul 7 11:02 sipstatus.log > -rw-r--r-- 1 root root 79 Jul 7 11:27 sipstatus.xml > -rw-r--r-- 1 sipxchange sipxchange 0 Jul 7 11:02 sipXalarms.log > -rw-r--r-- 1 root root 79 Jul 7 11:27 sipXalarms.xml > -rw-r--r-- 1 sipxchange sipxchange 0 Jul 7 11:02 sipxconfig-audit.log > -rw-r--r-- 1 root root 79 Jul 7 11:27 sipxconfig-audit.xml > -rw-r--r-- 1 sipxchange sipxchange 56060 Jul 7 11:02 sipxconfig.log > -rw-r--r-- 1 sipxchange sipxchange 96 Jul 7 11:01 sipxconfig-logins.log > -rw-r--r-- 1 root root 79 Jul 7 11:27 sipxconfig-logins.xml > -rw-r--r-- 1 root root 79 Jul 7 11:27 sipxconfig.xml > -rw-r--r-- 1 sipxchange sipxchange 0 Jul 7 11:02 sipxivr.log > -rw-r--r-- 1 root root 79 Jul 7 11:27 sipxivr.xml > -rw-r--r-- 1 sipxchange sipxchange 218814 Jul 7 11:02 sipxpark.log > -rw-r--r-- 1 root root 79 Jul 7 11:27 sipxpark.xml > -rw-r--r-- 1 sipxchange sipxchange 7913389 Jul 7 11:02 sipXproxy.log > -rw-r--r-- 1 root root 79 Jul 7 11:27 sipXproxy.xml > -rw-r--r-- 1 sipxchange sipxchange 342080 Jul 7 11:02 sipxrls.log > -rw-r--r-- 1 root root 79 Jul 7 11:27 sipxrls.xml > -rw-r--r-- 1 sipxchange sipxchange 170304 Jul 7 11:02 sipxsaa.log > -rw-r--r-- 1 root root 79 Jul 7 11:27 sipxsaa.xml > -rw-r--r-- 1 sipxchange sipxchange 741516 Jul 7 11:02 sipxsupervisor.log > -rw-r--r-- 1 root root 79 Jul 7 11:27 sipxsupervisor.xml > -rw-r--r-- 1 sipxchange sipxchange 0 Jul 7 11:02 snapshot.err.log > -rw-r--r-- 1 sipxchange sipxchange 0 Jul 7 11:02 snapshot.output.log > > Cannot proceed to additional steps. That 'ls' is very informative. The most peculiar part is not that merged.xml has no messages in it, but that the other *.xml files don't. There are no simple explanations for that. I'm going to have to check that in some detail. Can you tar/zip that directory and put it some place that I can retrieve it? Send me the link privately, so you don't have to modify the files first. Dale _______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
