andrewgroup Posted May 9, 2009 Report Posted May 9, 2009 when the CDR folder consumes the remaining space on a CS410, (15,000+ calls) the CS410 simply stops recording.... Using DF and DU while logged in as the root user we see the trouble and deleted the many cdr files... Have we overlooked provisions in PBXnSIP to prevent or limit the growth of these or other folders? If not I suppose I'll cron a job to get these values and mail the output to our ticket system.. (Maybe Grep for a certain value) then mail to manage the exceptions. A better solution would be adding a new SNMP variable that goes from 0 to 100 that would represent either used or available space. I'll post that on SNMP too...as a reminder. Quote
Vodia PBX Posted May 9, 2009 Report Posted May 9, 2009 when the CDR folder consumes the remaining space on a CS410, (15,000+ calls) the CS410 simply stops recording....Using DF and DU while logged in as the root user we see the trouble and deleted the many cdr files... Have we overlooked provisions in PBXnSIP to prevent or limit the growth of these or other folders? If not I suppose I'll cron a job to get these values and mail the output to our ticket system.. (Maybe Grep for a certain value) then mail to manage the exceptions. A better solution would be adding a new SNMP variable that goes from 0 to 100 that would represent either used or available space. I'll post that on SNMP too...as a reminder. You should make the "Keep CDR Duration" shorter. Then there are not so many files. Also, you can see the available file system space in the status interface. SNMP: It would be easy to add a OID for the number of CDR in the PBX. That value corresponds to the file system space. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.