Overview
This article provides a description of the upload data management policy. A data retention policy configured with the upload action is used for specifying the final storage location of the recorded conversations. Recording Servers store the recorded conversations on their local disk temporarily while recording. After the recording is done, the files need to be moved to the designated storage location(s).
...
Direct Upload Policy | Upload Policy | |
|---|---|---|
| Place of execution | Recording Server | Recording Server |
| Suitable for Large Volumes | Yes, recommended | Yes |
| Data Types and Source Platforms | Any | Any |
| Database Query / File Based | File | File and Database Query |
| Filters | Conversation Type Source Platform 2N Source | Any |
| User Assignment | Yes (policy filter configuration) | Yes (user/extension configuration) |
| Audit Log | Yes | Yes |
| Configurable Schedule | No | No |
| Retention | Set only on the user level | Can be set on the policy level and on the user level |
What happens when there is a record with no matching policy?
After the recording service completes the recording process, the Storage Management Service will try to find a matching policy using database queries with the Conversation ID or the local configuration in the case of direct upload policies. If it does not find any matching policy, it will raise an alert and will immediately move the files related to the conversation to the media/nopolicy folder. Conversation-related files in the media/nopolicy folder are infinitely re-checked with a lower frequency (configurable, 10 minutes by default). The system does not give up the upload after the timeout and will continuously retry. If you receive an alert for upload failure due to no policy found, it is recommended to check the affected records and the policy filter configuration. After updating the policies, the system automatically tries to upload the files again.
Functionality in earlier versions (pre v9.6.6.6237):
After the recording service completes the recording process, the Storage Management Service tries to find a matching policy using database queries with the Conversation ID or the local configuration in the case of direct upload policies. If it does not find any matching policy, it will raise an alert and will try to find it again in the next cycle. The service tries to find a matching policy until a configurable timeout (120 hours by default). After the timeout expires, the Storage Management Service moves the files related to the call to the media/nopolicy folder, and will never try to upload it again. Files can be manually copied back to the standard media folder where the Storage Management Service will try the upload again. It will only try to upload it once since the timeout has already expired based on the call end date-time.
Enabling policy-based upload
...