[App_rpt-users] think i asked wrong... record wav files creates time stamped text summary RE: App_rpt-users Digest, Vol 79, Issue 53

[Ken H W4NOC]

Pete M,

Someone answered this earlier when he suggested the wav file recording
feature 'archivedir' (rpt.conf).  But it does a little more than just record
the wav.  The wav filename is time stamped but there is also text summary.
This feature may provide what you are looking for. 

It is listed as undocumented at http://docs.allstarlink.org/drupal/node/73.
But this HOW TO RECORD REPEATER TRAFFIC with archivedir. 
in rpt.conf insert:
archivedir = /etc/asterisk/record   ; defines file store path and enables
activity 
monminblocks = 2048   ; Min 1K blocks to be left on partition (will not save
monitor output if disk too full)

It does create the wav files (ex: 20150929214712.WAV), but it also creates a
text file with date/time stamp (ex: 20150929.txt).  The app will create a
node number directory below /etc/asterisk/record.  You can record these
files in any directory you choose. 

Example content of /etc/asterisk/record/40804/
20150929125948.WAV  20150929173946.WAV  20150929203151.WAV
20150929214712.WAV  20150929220907.WAV
20150929130010.WAV  20150929183933.WAV  20150929210819.WAV
20150929214827.WAV  20150929220930.WAV
20150929130344.WAV  20150929184442.WAV  20150929211134.WAV
20150929215033.WAV  20150929221045.WAV
20150929130950.WAV  20150929184923.WAV  20150929211241.WAV
20150929215143.WAV  20150929.txt
20150929131501.WAV  20150929193655.WAV  20150929211330.WAV
20150929215159.WAV  20150930094910.WAV
20150929132012.WAV  20150929195207.WAV  20150929211554.WAV
20150929215221.WAV  20150930095443.WAV
20150929132021.WAV  20150929200031.WAV  20150929211748.WAV
20150929215246.WAV  20150930095511.WAV
20150929133009.WAV  20150929200042.WAV  20150929213202.WAV
20150929215351.WAV  20150930095934.WAV
20150929133239.WAV  20150929200107.WAV  20150929213401.WAV
20150929215435.WAV  20150930100949.WAV
20150929134034.WAV  20150929200720.WAV  20150929213425.WAV
20150929220027.WAV  20150930105408.WAV
20150929134517.WAV  20150929201005.WAV  20150929213537.WAV
20150929220133.WAV  20150930110905.WAV
20150929135048.WAV  20150929202228.WAV  20150929213710.WAV
20150929220400.WAV  20150930111928.WAV
20150929144407.WAV  20150929202250.WAV  20150929213920.WAV
20150929220433.WAV  20150930.txt
20150929171901.WAV  20150929202348.WAV  20150929214058.WAV
20150929220500.WAV
20150929172931.WAV  20150929202353.WAV  20150929214221.WAV
20150929220658.WAV
20150929173414.WAV  20150929202413.WAV  20150929214513.WAV
20150929220832.WAV


Here is an excerpt from the 20150930.txt file that itemizes the key and
un-key along with the node from which it came.
20150929220928,TXUNKEY,MAIN
20150929220930,RXKEY,42126
20150929220930,TXKEY,29910
20150929220930,TXKEY,MAIN
20150929220930,TXKEY,42159
20150929220950,RXUNKEY,42126
20150929220950,TXUNKEY,29910
20150929220950,TXUNKEY,42159
20150929220951,RXKEY,29910
20150929220951,TXKEY,42126
20150929220951,TXKEY,42159
20150929220956,RXUNKEY,29910
20150929220956,TXUNKEY,42126
20150929220956,TXUNKEY,42159
20150929220957,RXKEY,42126
20150929220957,TXKEY,42159
20150929220957,TXKEY,29910
20150929220958,RXUNKEY,42126
20150929220958,TXUNKEY,42159
20150929220958,TXUNKEY,29910
20150929221004,TXUNKEY,MAIN
20150929221045,TXKEY,MAIN
20150929221053,TXUNKEY,MAIN
[root at w4noc-mcdn 40804]#

I used the txt and the wav files to identify a repeater node that would
sometimes hang in transmit.  You will need to clear this path periodically.


Ken
W4NOC


----------------------------------------------------------------------

Message: 1
Date: Wed, 30 Sep 2015 09:03:26 -0400
From: "Pete M" <petem001 at hotmail.com>
To: "APP RPT" <app_rpt-users at ohnosec.org>
Subject: [App_rpt-users] think I asked wrong..
Message-ID: <BAY179-DS218B8385EE9506F2374753974D0 at phx.gbl>
Content-Type: text/plain; charset="iso-8859-1"

Hi. 

We have someone on the repeater doing multiple small tx on a random pattern
(this can last 10 minute at a time) so all we ear is the telemetry of the
repeater and it kind of get on the nerve of many.

We did lower the audio level of the telemetry were we almost dont ear it,
yet the bozo continu on tx ing short (less then a second) ptt.. 

We are building some DDDF ( digital Doppler direction finder)  that will
monitor the input freq of our 2 repeater and will logs the bearing of at
least 4 of them on a central server with time stamps..

I need a way to extract from asterisk when someone do make a lots of short
ptt and compare them to the logs from our DDDF. that way after some data
collection we will see if the offender is on the move or mostly at the same
place. and at the same time we will see if it is random or if there is some
kind of pattern in time so that we will be able to find the offender and
finally be done with it.. this been going on for years..

Anyone can point me ia way to extract such data from asterisk ? or find a
way with action command to put that kind of stuff in a file?

Thanks