[App_rpt-users] CLI Echolink Call Sign Logging

Chuck Henderson rpt2 at chuck.midlandsnetworking.com
Thu Sep 6 02:04:48 UTC 2012


I also prefer to have the audit trail of who connected when in the log
files. I don't really want to see any of the database update messages.  If
one can't be had without the other then I would rather have the logging
like it was before.   Are the lines Kent identified the right ones to get
the old logging back or is it more complicated than that?
Chuck
On Sep 5, 2012 5:16 PM, "Kent Ochs" <kentochs at sbcglobal.net> wrote:

> Jim,
>
> Yes,  all the Echolink database connection info was noise. Yes, setting
> verbosity to 4 causes "new call" to be displayed on the console, but
> specifically, new call is no longer written into the/var/log/asterisk/messages file, even with verbosity set to 4.
>
> I guess I am in the minority that thought it was nice to have an "audit
> log" of Echolink call sign connections in the asterisk messages file.
>
> Thanks.
>
> Kent
>   ------------------------------
> *From:* Jim Duuuude <telesistant at hotmail.com>
> *To:* kentochs at sbcglobal.net; app_rpt mailing list <
> app_rpt-users at ohnosec.org>
> *Sent:* Wednesday, September 5, 2012 10:29 AM
> *Subject:* RE: [App_rpt-users] CLI Echolink Call Sign Logging
>
>
> Mantis?? Do we even HAVE a mantis?? (Yes, I know we 'have' one, last I
> looked, but YEARS ago
> it was determined to be utterly useless and has been ignored ever since).
> Why is it still there?
>
> Look, more people (by a factor of about 3) did enough BITCH,,MOAN - ing
> to indicate that it was appropriate to make it NOT log 'all that stuff'
> (or whatever
> else some people may have been calling it at the time), so that was the
> direction
> it went. If you want the verbose log output, set verbose level to 4 and
> 'all that stuff'
> will be "back".
>
> Jim WB6NIL
> ------------------------------
> Date: Tue, 4 Sep 2012 19:08:46 -0700
> From: kentochs at sbcglobal.net
> To: app_rpt-users at ohnosec.org
> Subject: [App_rpt-users] CLI Echolink Call Sign Logging
>
> This problem appears to be related to the following code change where the
> ast_log function is no longer being called at connection time when
> Verbosity > 3
>
> Chan_Echolink (Rev 971)
> ast_log(LOG_NOTICE, "new CALL=%s,ip=%s,name=%s\n",
>
> Chan_Echolink (Rev 1201)
> if (option_verbose > 3) ast_verbose(VERBOSE_PREFIX_3 "new
> CALL=%s,ip=%s,name=%s\n",
>
> This has been logged as Mantis Issue 76.
>
> Thanks.
>
> Kent
> W9KAO
>
> _______________________________________________ App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20120905/3e51fb10/attachment.html>


More information about the App_rpt-users mailing list