Hi Sardar,
As an alternative solution, you can just create batch jobs to export them through your S3 integration.
- /api/v2/recording/jobs to create the job
- /api/v2/recording/jobs/{jobId} execute the job
- /api/v2/recording/jobs watch the job
When you create the job, it will take some time for it to be ready to execute, so make sure you GET the status until you see state: READY. I also found that exporting more than a few hundred thousand caused issues. I would suggest staying under 200K.
------------------------------
Caleb Smith
Interstate Gas Supply, Inc.
------------------------------
Original Message:
Sent: 01-31-2024 12:40
From: Sardar Mohammed
Subject: Recording policy - not working
Hello Everyone,
we have multiple recording policies and everything working fine. recently one of our vendor requested for backdated recordings so i created a policy and set up the date range. I dont see the files are moving into our s3 bucket. we have AWS s3 bucket interagtion set up. all the configuration looks good. any suggestions?
Thanks
Sardar Mohammed
#QualityManagement
------------------------------
Sardar Mohammed
Elevate Credit Service LLC
------------------------------