On Thu, Apr 17, 2014 at 11:52 AM, Bryant Zimmerman <brya...@zktech.com>wrote:
A simple way that we use to do the move is to create a cron job that looks > for a .move file. > It has the same name as the recorded file. asterisk writes the .move file > which is just a text file with some stats in it. > The .move file is written from the dial plan at the end of the recording. > In the exten = h we write a .delete file for an abandon call. > > The cron then processes the .move and .delete files at a given interval. > We actually write special instructions into our .move files that the cron > parses and can then act accordingly. So we have a single smart cron job > handling moves for each type of task. In some cases our .delete files are > processed as moves to an abandon cache for recovery if a customer did not > intend to abandon it. > > The sky's the limit on how complex you want to make it, but in the long > run it is fairly simple and it just works. > > Thanks > > Bryant Zimmerman (ZK Tech Inc.) > 616-855-1030 Ext. 2003 > > We record locally and move the files to the storage server with a cron job once a minute. The script uses lsof to check to see if Asterisk is writing to the file. /usr/sbin/lsof | grep filename | wc -l Thanks, Ryan
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users