[App_rpt-users] Nodeshark - where's it gone?
g4rky at yahoo.co.uk
Sun Nov 18 11:04:44 EST 2012
I wanted to download Nodeshark but I don't seem to be able to find the web
Anyone know where its gone?
Keith's web site at arizuni.com/nodehsark/ is no longer there....
On 6 September 2012 00:38, Keith Williamson <hkwilliamson at gmail.com> wrote:
> To get detailed connection logging:
> 1) create an upper-level directory for the log files and sound files (e.g.
> 2) create a sub-directory of the above using your Allstar node number.
> (e.g. /etc/asterisk/qso/2541)
> 3) edit /etc/asterisk/rpt.conf and add the following in your node stanza:
> archivedir=/etc/asterisk/qso /* For example */
> 4) restart asterisk
> You will now get daily logfiles of the form YYYYMMDD.txt. Those logfiles
> show connects and disconnects (among other things) for any Allstar or
> Echolink sessions. Any transmissions are also archived as compressed WAV
> files (13kbps GSM).
> I wrote a Windows utility you can download and use to retrieve, filter,
> and display the log entries in a more human readable format. You can also
> use it to replay any transmissions.
> Allstar: 2541
> Nodeshark: http://www.arizuni.com/NodeShark/
> On Wed, Sep 5, 2012 at 3:16 PM, Kent Ochs <kentochs at sbcglobal.net> wrote:
>> 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.
>> *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
>> 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
>> This has been logged as Mantis Issue 76.
>> _______________________________________________ App_rpt-users mailing
>> list App_rpt-users at ohnosec.org
>> App_rpt-users mailing list
>> App_rpt-users at ohnosec.org
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the App_rpt-users