It sure would be nice if someone could write a definitive guide to working with logs and traces on Sipx. I keep running across helpful little bits of info like this one Dale has provided, but there seems to be nowhere to see it all together. In my current state of ignorance, troubleshooting with traces takes way too much time. Anyone willing to create a thoughtful Wiki page for this (or improve one of the existing ones, like the SipViewer page, which is a good start)?
I would love to see descriptions of best/most effective practices for getting traces for a few common scenarios. For example: 1. Get a trace for a particular call placed to or from a certain extension, in response to a user report of a problem. Explain differences in technique if the call happened today, yesterday, or 2 weeks ago. 2. Make a list of all calls (or registrations, or subscribe attempts) over the last 24 hours that had any kind of error (which I could scan to help determine if there are unreported problems I should be addressing). 3. An efficient technique for repeatedly getting/displaying traces for test calls I am making to troubleshoot. Isn't there any kind of one-click or one-command way of popping up a trace? I would like to see a script or utility that I could run on a workstation that would show me a list of the last 10 calls, with Source, Destination and Call-ID, and let me pick one and pop up a trace in the viewer. Any takers? Thanks, Jeff On Jan 28, 2011, at 11:18 AM, Worley, Dale R (Dale) wrote: > ________________________________________ > From: [email protected] > [[email protected]] On Behalf Of Peter van der Salm > [[email protected]] > > Thanks a lot! Then we are not going to dig into this ERR issue. I have phones > that from time to time fail to register for something like 15 to 30 minutes. > After failed registration, the phones correct the situation themselves, but > of course users don't like to be unreachable for some time, especially not if > they ar enot aware if it... > I will try to find out what happens when the phone does not manage to > register, may be I can syslog some of the phones. > _______________________________________________ > > Use sipx-snapshot to get a snapshot. Then filter the logs with something > like "merge-logs --include-method=REGISTER --ft=[the extension in question]". > (These programs are tools included with sipX; if you want to debug problems, > you will need to learn how to use them.) That will give you a siptrace file > showing the REGISTERs and their errors for the phone in question. At that > point, you can at least pinpoint which REGISTER requests failed. You may > need to dig into the logs to examine the detailed processing of the REGISTER > that failed. > > Dale > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
