Retention and Storage
CDR Search Tool stores received CDR data locally. Retention and storage controls prevent the application from consuming unlimited disk capacity.
Public edition retention
The public edition is limited to 30 days of searchable record retention.
The limit is designed for ongoing operational troubleshooting rather than long-term enterprise call-record archiving.
Full Licence activation
The Full Licence costs A$100 once for one organisation and one installation. It has no expiry and includes all future updates to Call Records. It unlocks configurable retention beyond 30 days, up to the application's supported setting of 36,500 days. Available disk space and your storage policy still limit retained data.
- Open Administration, then the Licensing card.
- Copy the installation Instance ID before purchasing.
- Enter that exact ID and your organisation name at checkout.
- Paste the licence key from the confirmation page or purchase email into the Licensing card.
- Select Activate full licence.
- Set your preferred retention period in CDR storage and save the policy.
Activation does not run cleanup or change your current retention setting. A key for another installation or another app is rejected. Pasting a bad key does not replace an existing valid licence.
Keep the complete data folder backed up: it contains your installation identity and activated licence as well as records and settings. Preserve it during updates. Contact support before replacing an installation identity. If an installed key becomes invalid, cleanup is paused while the licence needs attention so a licence problem alone does not delete existing records.
Storage policy
The application storage policy considers both received CDR files and indexed application data.
When planning capacity, allow for:
- Incoming CDR source files.
- Database growth.
- Report/export files where applicable.
- Application logs.
- Update and rollback files.
- Temporary working space during upgrades.
Retention changes
Reducing a retention value may result in older data becoming eligible for removal.
Before making a significant retention or storage-policy change, confirm the organisation does not rely on the application as its only copy of required historical records.
Backups
Application backups should be included in the organisation's normal backup plan if the retained data or configuration is operationally important.
The managed updater creates a pre-update backup for rollback purposes. That mechanism is not a substitute for a broader backup strategy.