[App_rpt-users] app_rpt logging

[Doug Crompton]

Adam,

 All the other ideas have merit but there is a built-in way to do this using the archivedir command. The command is inserted in the node definition part of the node you want to log in rpt.conf.

archivedir=/var/log/asterisk/audio
archiveaudio=0          ; Disable saving .wav files

The second command is one we added to the BBB distribution because archivedir will save all status information including wav audio files of all transactions on the node stanza where you define it. Setting archiveaudio to 0 diables the saving of the audio files. Something you would definitely want to do if you are running the BBB.  On a Pc you could just just have a cron job that deletes the wav files each day if you don't want them.

It creates daily text files named like this -

 /var/log/asterisk/audio/xxxxx/20150217.txt

xxxxx is the node number, so you can have logs for each node in separate directories. The file contents typically looks like this -

20150217000020,TXUNKEY,40879
20150217000020,TXUNKEY,41244
20150217000020,TXUNKEY,40561
20150217000022,RXKEY,28544
20150217000022,TXKEY,41167
20150217000022,TXKEY,28796
20150217000022,TXKEY,28366

There is a lot of data on a busy node!  It is the complete date and time to the second, the action taken, and the node number that action was taken on.

I have created a perl program that sorts this all out and uses the Asterisk database to create real names. It also follows the date change and selects the new days file.

02/17/2015 20:24:29 RXKEY 40961   WA3DSP  146.565 Simplex 88.5  Cape May, NJ
02/17/2015 20:24:52 RXKEY 29971   WA3EZT  446.2 simplex             Jenkintown, PA 19046
02/17/2015 20:26:37 RXKEY 28796   KC4RPP  443.100                      Naples, FL
02/17/2015 20:27:11 RXKEY 40961   WA3DSP  146.565 Simplex 88.5  Cape May, NJ
02/17/2015 20:28:17 RXKEY 29971   WA3EZT  446.2 simplex             Jenkintown, PA 19046
02/17/2015 20:29:19 RXKEY 28796   KC4RPP  443.100                      Naples, FL

In this case I only look at rxkey's but you could look at any status command you desire. This is a great way to see exactly who is keyed up on a node.

So the information is there you just have to process it. The archivedir command gives you a very complete log of everything your node did including audio recordings if you want them.
73 Doug
WA3DSP
http://www.crompton.com/hamradio


> From: ajp26 at buffalo.edu
> To: app_rpt-users at ohnosec.org
> Date: Tue, 17 Feb 2015 20:15:06 +0000
> Subject: [App_rpt-users] app_rpt logging
> 
> Afternoon all,
> 
> 	Is there a way to enable broad logging of connect, disconnect, keying, that's seen by app_rpt? Even cranked up to debug, the information about who's connected, say via echolink, is not available. I'd have to dump console output to a file, and I'm hoping I'm just missing some setting to get by this. Thoughts?
> 
> Adam, KC2YQF
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users at ohnosec.org
> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
> 
> To unsubscribe from this list please visit http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
> You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem. 
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20150217/879c1a34/attachment.html>