<div dir="ltr">you could also try rxondelay if you're using a URIx. It's a kerchunk filter more or less. <div><br></div><div>Trying to track someone down that is doing very short transmissions will be tough but a good exercise in fox hunting.</div><div><br></div><div>I actually stream all my audio to broadcastify so everything is recorded but as others have mentioned the "archive" function works well too. You can use it with nodeshark <a href="http://hkeithw.powweb.com/NodeShark/">http://hkeithw.powweb.com/NodeShark/</a> if you like.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 30, 2015 at 10:37 AM, Ken H W4NOC <span dir="ltr"><<a href="mailto:kenh@tsg-us.com" target="_blank">kenh@tsg-us.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Pete M,<br>
<br>
Someone answered this earlier when he suggested the wav file recording<br>
feature 'archivedir' (rpt.conf). But it does a little more than just record<br>
the wav. The wav filename is time stamped but there is also text summary.<br>
This feature may provide what you are looking for.<br>
<br>
It is listed as undocumented at <a href="http://docs.allstarlink.org/drupal/node/73" rel="noreferrer" target="_blank">http://docs.allstarlink.org/drupal/node/73</a>.<br>
But this HOW TO RECORD REPEATER TRAFFIC with archivedir.<br>
in rpt.conf insert:<br>
archivedir = /etc/asterisk/record ; defines file store path and enables<br>
activity<br>
monminblocks = 2048 ; Min 1K blocks to be left on partition (will not save<br>
monitor output if disk too full)<br>
<br>
It does create the wav files (ex: 20150929214712.WAV), but it also creates a<br>
text file with date/time stamp (ex: 20150929.txt). The app will create a<br>
node number directory below /etc/asterisk/record. You can record these<br>
files in any directory you choose.<br>
<br>
Example content of /etc/asterisk/record/40804/<br>
20150929125948.WAV 20150929173946.WAV 20150929203151.WAV<br>
20150929214712.WAV 20150929220907.WAV<br>
20150929130010.WAV 20150929183933.WAV 20150929210819.WAV<br>
20150929214827.WAV 20150929220930.WAV<br>
20150929130344.WAV 20150929184442.WAV 20150929211134.WAV<br>
20150929215033.WAV 20150929221045.WAV<br>
20150929130950.WAV 20150929184923.WAV 20150929211241.WAV<br>
20150929215143.WAV 20150929.txt<br>
20150929131501.WAV 20150929193655.WAV 20150929211330.WAV<br>
20150929215159.WAV 20150930094910.WAV<br>
20150929132012.WAV 20150929195207.WAV 20150929211554.WAV<br>
20150929215221.WAV 20150930095443.WAV<br>
20150929132021.WAV 20150929200031.WAV 20150929211748.WAV<br>
20150929215246.WAV 20150930095511.WAV<br>
20150929133009.WAV 20150929200042.WAV 20150929213202.WAV<br>
20150929215351.WAV 20150930095934.WAV<br>
20150929133239.WAV 20150929200107.WAV 20150929213401.WAV<br>
20150929215435.WAV 20150930100949.WAV<br>
20150929134034.WAV 20150929200720.WAV 20150929213425.WAV<br>
20150929220027.WAV 20150930105408.WAV<br>
20150929134517.WAV 20150929201005.WAV 20150929213537.WAV<br>
20150929220133.WAV 20150930110905.WAV<br>
20150929135048.WAV 20150929202228.WAV 20150929213710.WAV<br>
20150929220400.WAV 20150930111928.WAV<br>
20150929144407.WAV 20150929202250.WAV 20150929213920.WAV<br>
20150929220433.WAV 20150930.txt<br>
20150929171901.WAV 20150929202348.WAV 20150929214058.WAV<br>
20150929220500.WAV<br>
20150929172931.WAV 20150929202353.WAV 20150929214221.WAV<br>
20150929220658.WAV<br>
20150929173414.WAV 20150929202413.WAV 20150929214513.WAV<br>
20150929220832.WAV<br>
<br>
<br>
Here is an excerpt from the 20150930.txt file that itemizes the key and<br>
un-key along with the node from which it came.<br>
20150929220928,TXUNKEY,MAIN<br>
20150929220930,RXKEY,42126<br>
20150929220930,TXKEY,29910<br>
20150929220930,TXKEY,MAIN<br>
20150929220930,TXKEY,42159<br>
20150929220950,RXUNKEY,42126<br>
20150929220950,TXUNKEY,29910<br>
20150929220950,TXUNKEY,42159<br>
20150929220951,RXKEY,29910<br>
20150929220951,TXKEY,42126<br>
20150929220951,TXKEY,42159<br>
20150929220956,RXUNKEY,29910<br>
20150929220956,TXUNKEY,42126<br>
20150929220956,TXUNKEY,42159<br>
20150929220957,RXKEY,42126<br>
20150929220957,TXKEY,42159<br>
20150929220957,TXKEY,29910<br>
20150929220958,RXUNKEY,42126<br>
20150929220958,TXUNKEY,42159<br>
20150929220958,TXUNKEY,29910<br>
20150929221004,TXUNKEY,MAIN<br>
20150929221045,TXKEY,MAIN<br>
20150929221053,TXUNKEY,MAIN<br>
[root@w4noc-mcdn 40804]#<br>
<br>
I used the txt and the wav files to identify a repeater node that would<br>
sometimes hang in transmit. You will need to clear this path periodically.<br>
<br>
<br>
Ken<br>
W4NOC<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Wed, 30 Sep 2015 09:03:26 -0400<br>
From: "Pete M" <<a href="mailto:petem001@hotmail.com">petem001@hotmail.com</a>><br>
To: "APP RPT" <<a href="mailto:app_rpt-users@ohnosec.org">app_rpt-users@ohnosec.org</a>><br>
Subject: [App_rpt-users] think I asked wrong..<br>
Message-ID: <BAY179-DS218B8385EE9506F2374753974D0@phx.gbl><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Hi.<br>
<br>
We have someone on the repeater doing multiple small tx on a random pattern<br>
(this can last 10 minute at a time) so all we ear is the telemetry of the<br>
repeater and it kind of get on the nerve of many.<br>
<br>
We did lower the audio level of the telemetry were we almost dont ear it,<br>
yet the bozo continu on tx ing short (less then a second) ptt..<br>
<br>
We are building some DDDF ( digital Doppler direction finder) that will<br>
monitor the input freq of our 2 repeater and will logs the bearing of at<br>
least 4 of them on a central server with time stamps..<br>
<br>
I need a way to extract from asterisk when someone do make a lots of short<br>
ptt and compare them to the logs from our DDDF. that way after some data<br>
collection we will see if the offender is on the move or mostly at the same<br>
place. and at the same time we will see if it is random or if there is some<br>
kind of pattern in time so that we will be able to find the offender and<br>
finally be done with it.. this been going on for years..<br>
<br>
Anyone can point me ia way to extract such data from asterisk ? or find a<br>
way with action command to put that kind of stuff in a file?<br>
<br>
Thanks<br>
<br>
<br>
_______________________________________________<br>
App_rpt-users mailing list<br>
<a href="mailto:App_rpt-users@ohnosec.org">App_rpt-users@ohnosec.org</a><br>
<a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" rel="noreferrer" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a><br>
<br>
To unsubscribe from this list please visit <a href="http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users" rel="noreferrer" target="_blank">http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"<br>
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.<br>
</blockquote></div><br></div>