[App_rpt-users] Nodeshark - where's it gone?

[Keith Williamson]

I'm still trying to get to the bottom of  my DNS woes but in the meantime,
you can access the NodeShark website at:

http://hkeithw.powweb.com/NodeShark/

73's,

Keith

On Sun, Nov 18, 2012 at 11:11 AM, Keith Williamson
<hkwilliamson at gmail.com>wrote:

> Thanks for the heads up!
>
> I got caught in some DNS registrar's tuna net. I'm chewing off their arm
> currently but I'll be back in the water with all you web surfers again
> within a few hours. ;^(>)
>
> Cheers,
>
> Keith
>
>
> On Sun, Nov 18, 2012 at 10:16 AM, Jim Duuuude <telesistant at hotmail.com>wrote:
>
>>  I think I saw it floating out the door, heading towards the La Jolla
>> shark cafeteria!! :-)
>>
>> Jim
>>
>> P.S. The last time I was at the Long Beach Aquarium, I noticed that the
>> shark exhibit
>> was right next to the seal exhibit... Was that a coincidence?
>>
>> ------------------------------
>> Date: Sun, 18 Nov 2012 16:04:44 +0000
>> From: g4rky at yahoo.co.uk
>> To: hkwilliamson at gmail.com
>> CC: app_rpt-users at ohnosec.org; kentochs at sbcglobal.net
>> Subject: [App_rpt-users] Nodeshark - where's it gone?
>>
>>
>> Hi all,
>>
>> I wanted to download Nodeshark but I don't seem to be able to find the
>> web site anymore?
>>
>> Anyone know where its gone?
>>
>> Keith's web site at arizuni.com/nodehsark/ is no longer there....
>>
>> Regards,
>>
>> Matt
>> G4RKY
>>
>>
>> On 6 September 2012 00:38, Keith Williamson <hkwilliamson at gmail.com>wrote:
>>
>> Kent,
>>
>> To get detailed connection logging:
>>
>> 1) create an upper-level directory for the log files and sound files
>> (e.g. /etc/asterisk/qso)
>> 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.
>>
>> 73's,
>>
>> Keith
>> KF7DRV
>> Allstar: 2541
>> Nodeshark: http://www.arizuni.com/NodeShark/
>>
>>
>> On Wed, Sep 5, 2012 at 3: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
>>
>>
>>
>> _______________________________________________
>> 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
>>
>> _______________________________________________
>> 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/20121119/3a8909c2/attachment.html>