<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.24.5">
<TITLE>asterisk-users Digest, Vol 63, Issue 47</TITLE>
</HEAD>
<BODY>
I have the following in /etc/asterisk/logger.conf :<BR>
<BR>
<FONT SIZE="2">debug => debug</FONT><BR>
<FONT SIZE="2">console => notice,warning,error</FONT><BR>
<FONT SIZE="2">;console => notice,warning,error,debug</FONT><BR>
<FONT SIZE="2">messages => notice,warning,error</FONT><BR>
<FONT SIZE="2">verbose => verbose</FONT><BR>
<FONT SIZE="2">;full => notice,warning,error,debug,verbose</FONT><BR>
<BR>
When I enable SIP and/or IAX debugging on the CLI and watch the logfiles, then I conclude the following :<BR>
<BR>
- debugging is not written to the debug-logfile<BR>
- debugging is written to the verbose-logfile<BR>
<BR>
What I actually want is thus the debug-information separated in one SIP and/or IAX-debug logfile : debug.iax.systemname and debug.sip.systemname or something like this...<BR>
<BR>
<BR>
<BR>
<BR>
On Mon, 2009-10-19 at 08:27 +1200, Neeraj Chand wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
There was a presentation at astricon by Clod, that covers just this "CLI Filters" <BR>
<BR>
What this does is show only the filters that you set on asterisk cli, and your /var/log/asterisk/full log file also only contains the filtered output. <BR>
<BR>
I believe it would have been handier to have filtering, but with everything going to the "full" log so that if we need to debug in greater detail / look at events outside the scope of thep filters we set, it would be available in the full logs.<BR>
<BR>
<BR>
<BR>
But thats my personal perspective. This may be useful to you. The presentation should be on astricon.net some time soon<BR>
<BR>
<BR>
<BR>
Cheers!<BR>
</BLOCKQUOTE>
<BR>
</BODY>
</HTML>