We use sipviewer to view the logs as use of tcpdump means that a problem is reproducible at will and some issues are not. The logs may be the only source of information. So use of the log in many instances leads to quicker root cause than waiting for a problem to reoccur.
I agree that INFO level is sufficient for troubleshooting most problems. However, there are times when I have found debug mode useful so I can see how sipXecs is processing information. Changing the log level to DEBUG is something that we should still be able to set. Providing a warning when making that change is reasonable. Dave Deutschman Managing Partner Innovational IP Solutions, LLC PO Box 983 Bothell, WA 98011 206.965.9586 x 301 (o) 425.478.9642 (m) [email protected] (s) www.innovational.net -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of M. Ranganathan Sent: Tuesday, March 02, 2010 3:40 PM To: Mardy Marshall Cc: sipXecs developers Subject: Re: [sipX-dev] Logging guidelines - discouraging DEBUG On Tue, Mar 2, 2010 at 6:29 PM, Mardy Marshall <[email protected]> wrote: > > On Mar 2, 2010, at 5:29 PM, Scott Lawrence wrote: > > On Tue, 2010-03-02 at 17:11 -0500, Mardy Marshall wrote: > > On Mar 2, 2010, at 4:45 PM, Scott Lawrence wrote: > > > What you are claiming is contrary to everything that I hear from Avaya > support personnel. Even Avaya's SCS product engineer has been quoted > as saying "Nobody uses sipviewer". Their preference is to use more > traditional tools such as WIreshark and tcpdump which provide them a > more encompassing view of the deployed network. I suggest that before > you subject the end user with excessively large log files bloated with > information that they do not use that you look at this objectively and > focus on what is best for the customer. > -Mardy Mardy, Agreed that support personnel do not use it but I would not know how to debug without it. I must disagree with you on that point. SIpviewer is an extremely handy tool at least for me as a hacker. Eventually, it is us poor sods who wind up having to debug our own dog food so please lets have the tools we like. I want add some capabilities to sipviewer and logging so I can add limited amounts of context information to the log at the INFO level. For example in java, you can log which file/line the messaage was sent or received at. Such things are not possible in tcpdump. I wish we could support things like that to make our lives easier. Thanks Ranga. > > > > _______________________________________________ > sipx-dev mailing list [email protected] List Archive: > http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev > sipXecs IP PBX -- http://www.sipfoundry.org/ > -- M. Ranganathan _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
