Page 1 of 1
Call Log....Need help
Posted:
Thu Feb 20, 2014 7:17 am
by mastrit
Hello, I need help.
My server needs every day to repair my table call_log, vicidial_dial_log, etc tables....
How can i delete but not to remove the Lists, and the statuses from lead. Only some logs that server dont need...
Thnxx
Asterisk version=1.4.44-vici
VERSION: 2.6-395a
BUILD: 130221-1736
Re: Call Log....Need help
Posted:
Fri Feb 21, 2014 7:06 pm
by mav2287
How long has this been going on for and what is the reason you need to repair the call_log table? If it keeps happening it would appear that something else is broken causing this issue
Re: Call Log....Need help
Posted:
Sat Mar 01, 2014 11:49 pm
by williamconley
If you run a vicidial server long enough, the log tables will bloat. There is an archive log tables script designed to move the excess entries into "_log_archive" tables and delete the entries from the "_log" tables. This is a safe process as nothing is deleted, but the harvested log files will no longer be available for reporting. It is up to you to "acquire" any of the old data in case you ever need it for anything. After the data has been moved, the log tables will be greatly reduced in size. You can set this script up to run monthly (or daily for that matter).
Of course, it is also possible that your HD is full ... in which case you may just need to delete some files (such as recordings in the WAV folder of monitorDONE if you have them converted to GSM or MP3 already anyway).
Also: Please always post your installation method (and version if .iso or link to instructions if manual). It helps us to know what method you used.
Re: Call Log....Need help
Posted:
Mon Mar 03, 2014 5:10 am
by geoff3dmg
williamconley wrote:Of course, it is also possible that your HD is full ... in which case you may just need to delete some files (such as recordings in the WAV folder of monitorDONE if you have them converted to GSM or MP3 already anyway).
There's a cron job you can enable to do this. Although I would highly recommend you look at using an archive server if this is the culprit.