Send Yeastar archives to the right storage

Yeastar remote archiving sends call recording and PBX backup files out of the PBX. Couchdrop supplies the receiving FTP, SFTP, or S3-compatible endpoint and maps that endpoint to the storage system that should hold the files.

For FTP or SFTP, configure Yeastar with the Couchdrop host, path, and credentials. For S3-compatible archiving, configure Yeastar with the Couchdrop S3 endpoint, bucket, region, and access-key details.

After delivery, Couchdrop can route, rename, copy, or retain files across the connected storage and partner systems used by the business.

• Receive Yeastar call recording archives and PBX backup files over FTP or SFTP
• Receive Yeastar archives through a Couchdrop S3-compatible endpoint
• Write archived files through to SharePoint, Google Drive, Amazon S3, Azure Blob, or partner SFTP folders
• Use Couchdrop automations to organize, copy, retain, or forward recordings after arrival
• Combine file delivery with Yeastar API, webhook, or WebSocket events for richer workflow context

1. Create a Couchdrop FTP/SFTP user or S3-compatible endpoint for the Yeastar archive workflow.
2. Map the Couchdrop endpoint to the storage folder where recordings and backups should be written.
3. In Yeastar P-Series, add an external archive server and choose FTP, SFTP, or S3-compatible object storage.
4. Enter the Couchdrop endpoint, credentials, bucket or path details, and archive schedule.
5. Run a test archive, then add Couchdrop automations for routing, retention, and downstream delivery.