As your VOS3000 softswitch processes thousands of calls daily, the MySQL database grows continuously. Without proper VOS3000 data maintenance, old CDRs, logs, and reports consume disk space, slow down queries, and can eventually cause system instability. This guide covers everything you need to know about managing VOS3000 data – from manual cleanup to fully automated maintenance routines.
By the end of this article, you’ll know how to keep your database lean, fast, and reliable for years of operation.
VOS3000 stores data in multiple MySQL tables that grow daily:
Without cleanup, you risk:
VOS3000 organizes data into separate tables by type and date. This design makes maintenance easier – you can drop or archive entire tables without affecting current operations.
Located under “System Management > Data Maintenance > CDR Tables”. Each table name ends with a date suffix, e.g., cdr_20250309. The “Data volume” column shows the number of records. Double‑click any table to view its contents.
Found under “System Management > Data Maintenance > System Log Tables”. These record all user activities – logins, configuration changes, etc. They’re essential for audits but can be purged after a retention period.
Under “System Management > Data Maintenance > History Alarm Tables”. Stores past alarms. Once resolved, alarms move here from current alarm list.
Under “System Management > Data Maintenance > Payment Record Tables”. All financial transactions are stored here permanently or until purged.
Under “System Management > Data Maintenance > Data Report Tables”. Pre‑generated reports (daily summaries) – can be safely deleted if you regenerate reports on demand.
Under “System Management > Data Maintenance > Other Income Report Tables”. Contains package rent, monthly fees, and other non‑call income records.
For one‑time or occasional cleanup, you can manually delete old data through the web interface:
⚠️ Warning: Deleted data cannot be recovered. Ensure you have verified backups before deleting anything.
Manual cleanup is error‑prone. VOS3000 includes a powerful auto‑cleanup feature that automatically removes old data based on your rules.
Go to System Management > Data Maintenance > Automatically Cleanup. Here you can configure retention periods for each data type:
You can also enable automatic cleanup of:
Once enabled, a background process runs daily (typically at low‑traffic hours) and:
⚠️ Important: Auto‑cleanup deletes entire tables, not individual rows. This is extremely fast and efficient but means you cannot keep partial months – it’s all or nothing per table.
Based on typical VoIP operations, here are sensible starting points:
| Data Type | Retention Period | Reason |
|---|---|---|
| CDRs | 90 days | Enough for customer disputes and traffic analysis; older data can be archived externally. |
| System logs | 30 days | Security audits rarely need older logs; export if longer retention required. |
| History alarms | 60 days | Alarm patterns over two months help identify recurring issues. |
| Payment records | 365 days (or longer for compliance) | Financial records may need 1‑7 years depending on local laws – adjust accordingly. |
| Data reports | 30 days | Reports can be regenerated from CDRs if needed. |
Before enabling auto‑cleanup or running manual deletes, ensure you have reliable backups:
Test your backups regularly by restoring to a test environment.
Even with auto‑cleanup, monitor disk usage:
du -sh /var/lib/mysqlIf you need to keep CDRs longer than auto‑cleanup allows, consider archiving:
VOS3000 does not include built‑in archival tools, but you can script this using mysqldump and cron.
No. Auto‑cleanup only deletes accounts that have been expired and have no associated active phones, gateways, or bind numbers. It checks dependencies before deleting.
Not from the live system. You must restore from backups if you need deleted data. This is why testing your backup restoration process is critical before enabling auto‑cleanup.
No. VOS3000 writes CDRs to a temporary table and moves them to the daily table after the call ends. Deleting old tables has no impact on ongoing calls.
Check that the retention period is set correctly and that the cleanup process is running (system logs will show cleanup actions). Also ensure that the tables are indeed older than the retention period – auto‑cleanup runs daily, so tables become eligible only after the configured number of days have passed since their creation.
Yes. Each data type has independent retention settings. Set payment records to a high value (e.g., 3650 days) and CDRs to a lower value (e.g., 90 days).
Proper VOS3000 data maintenance ensures your softswitch runs smoothly, queries stay fast, and disk space never becomes a crisis. Whether you prefer manual control or fully automated cleanup, VOS3000 provides the tools you need. Start with conservative retention periods, monitor the results, and adjust as you gain confidence.
Need help setting up data maintenance or recovering from a disk space emergency? Contact us on WhatsApp: +8801911119966
VOS3000 Caller Number Pool: Powerful CLI Rotation for Outbound Traffic The VOS3000 caller number pool feature solves a critical problem… Read More
VOS3000 Protect Route: Smart Backup Gateway Activation with Timer The VOS3000 protect route feature is one of the most misunderstood… Read More
VOS3000 outbound registration setup guide for carrier SIP trunk connections. Configure VOS3000 to register outbound to carriers, IMS, and ITSP… Read More
This website uses cookies.