> From: sipx-users-boun...@list.sipfoundry.org > [sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net > [m...@grounded.net] > > Here it is, the complete run. I deleted the old merged.xml file just to be > 100% sure. > > # merge-logs > > # ls -la merged.xml > -rw-r--r-- 1 root root 79 Jul 6 21:53 merged.xml > > # more merged.xml > <?xml version="1.0" encoding="UTF-8" standalone="yes"?> > <sipTrace> > </sipTrace>
OK, very good, that's what we need -- you've showed me what you did and what the results were. (Since I can't sit at the console of your system, I need you "to be my eyes and ears".) Now let's compare that to the instructions I previously sent you: > 1) Set your logging level to INFO (or DEBUG if you like that better). > > 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. > > 3) Take a snapshot using the Diagnostics -> Snapshot screen. Request > the time period to be covered by the captured logs to be the present > back to about 3 hours ago. That should be enough time to capture the > genesis of the problem. > > 4) Un-gzip and un-tar the snapshot file in some convenient directory > on the system. > > 5) cd to var/log/sipxpbx in the unpacked snapshot. > > 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]. > > 7) Do "sipviewer merged.xml &" to run sipviewer and display the > filtered log information. > > 8) Stare at the sipviewer screen to see what's going wrong. What you > should see is REGISTER requests going from the phone to the proxy to > the registrar, and responses going back. The requests will come in > pairs, the first one gets a 401/407 response, the second gets a 200 > response. Then there will be a gap of several minutes, then the next > pair, etc. With the default settings, the times at the left are in > local time, so you should look around the time when the phone was > unexpectedly not registered. (You can change the times to UTC from > the pulldown menus.) Each 200 response contains a header "Expires: > [number]", where [number] is the number of seconds into the fiture > that the registration has been extended until. The next successful > REGISTER should complete within that number of seconds of each > successful REGISTER. As far as I can tell, you are trying to run merge-logs on the live logs, rather than in the log directory of an unpacked snapshot. You'll need to fix that: Carry out the parts of (4) and (5) that you haven't done yet. You also haven't run merge-logs with the correct arguments. See step (6) for what to do. After that, you can do (7) and (8) and it might reveal something interesting. At the least, you'll have walked through a complete example of how to run merge-logs and sipviewer, and started learning what sipviewer displays look like, which will help you with any future problems. 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/
