Call recording on Yeastar: where it's stored, how long it lasts and how to use it
Where Yeastar P-Series stores recordings, which format to download (.wav or .mp3), how auto cleanup works and how BRIGGS fetches each recording via API.
Short answer
The Yeastar P-Series PBX records calls and keeps the files in the PBX's own storage. When downloading, you can choose .wav or .mp3. When storage reaches the configured limit, or when the retention period set by the administrator runs out, auto cleanup deletes the oldest recordings.
That covers the basics, but leaves three questions open:
- How do you find the right call when a customer complains?
- How do you keep recordings without depending on PBX storage space?
- How do you use recordings to improve service, and not just as evidence?
With BRIGGS connected to Yeastar, each recording is fetched through the API, transcribed, evaluated and stored outside the PBX. Overview in Yeastar + BRIGGS.
Where recordings are stored on Yeastar
According to Yeastar's official call recording documentation, the PBX stores recordings on the storage attached to it, chosen by the administrator. On the Cloud Edition, recordings are kept in the local storage of the cloud PBX.
A few points from the documentation that matter day to day:
- Format: when downloading, the administrator chooses between .wav and .mp3.
- Digital signature: Yeastar saves the file with a digital signature, to show the recording hasn't been altered.
- Separate channels: on calls between two people, each side can be recorded on its own stereo channel (left and right).
- Who has access: by default, only the super administrator manages recording files, and each user sees their own recordings. These permissions can be adjusted.
- Recording notice: by default, Yeastar doesn't play any announcement that the call is being recorded. The administrator can set up a notice for inbound, outbound and internal calls.
That last point deserves attention. Telling customers the call is recorded is the company's obligation, and it doesn't depend on BRIGGS. If your IVR doesn't have that notice yet, it's worth setting up.
How long recordings stay on the PBX
Yeastar's retention exists so the PBX doesn't run out of space. It wasn't designed to meet the retention period your industry requires.
On the Appliance Edition, auto cleanup of recording files is under System → Storage → Auto Cleanup → Recording Auto Cleanup → Recording Files and uses two settings:
- Max Usage of Device (%), 80% by default: when the storage reaches it, the oldest recordings are deleted;
- Recordings Preservation Days: after that many days, the recording is deleted. The default is 0, which means no day limit.
With the Auto Cleanup Reminder turned on, the PBX sends an email when recordings reach 90% of the limit, so there's time to make a copy.
On the Cloud Edition, auto cleanup is tied to the recording capacity you've subscribed to: when it runs out, the PBX deletes the oldest recordings. The same Recordings Preservation Days setting, under the same menu, adds a time limit on top of that.
Regulated sectors, such as customer service under Brazil's SAC rules (the federal regulation for customer service channels), private health plans and financial services, often have their own retention periods. We cover this topic in our post on how much it costs to store 5 years of recordings.
How BRIGGS fetches recordings
The integration uses the official Yeastar P-Series API:
- The PBX administrator creates a Client ID and a Client Secret under Integrations → API, as described in the API authorization rules.
- With those credentials, BRIGGS requests an access token from the PBX, following the OAuth 2.0 standard.
- Every few minutes, BRIGGS queries new recordings and the call record (CDR).
- BRIGGS downloads the audio, transcribes it and evaluates the call against the company's scorecard.
The CDR carries the information that gives the recording context: the extension that answered, the queue, the inbound number (DID), the duration. The extension identifies the employee being evaluated, and the queue, DID or extension determines which scorecard applies to that call.
Nothing is installed on the PBX. On your side, the only thing to allow is access to the API.
In the settings, the company picks the cutoff date from which recordings are included, and can skip short and internal calls, which don't help the evaluation.
Once the recording reaches BRIGGS
Find calls by what was said
In the PBX recordings list, you search by extension, number and time. Someone looking for a call after a complaint usually knows something else: the customer's name, the topic, a phrase the customer says they heard. In BRIGGS, calls are transcribed and you can search by content, with the summary and evaluation next to the audio.
Keep recordings without depending on PBX storage
Because BRIGGS downloads the audio, the recording is also kept in BRIGGS storage, with role-based access control. Yeastar's auto cleanup keeps working as it does today to free up space, but the evaluated copy doesn't depend on it.
Use recordings in management
A recording that's stored and never heard changes nothing in the operation. Once analyzed, the same recordings show:
- the score for each employee against the company's scorecard (quality monitoring with Yeastar);
- the contact reasons and what drives the most complaints (speech analytics with Yeastar);
- the at-risk customers, who talked about canceling, complaining or going to Procon (Brazil's consumer protection agency).
Frequently asked questions
Do I need to change the recording format in Yeastar? No. BRIGGS works with the audio the PBX already records.
Does BRIGGS need access to the recordings folder? No. Recordings are fetched through the Yeastar API, using the credentials the administrator created. There's no need to share a folder or open another port.
What about calls that weren't recorded? They aren't included in the evaluation, because BRIGGS needs the audio. The rule for which calls get recorded stays in Yeastar.
Do I need to tell customers the call is recorded? Yes, and that's independent of BRIGGS. In Yeastar, the administrator configures the recording notice, since it's off by default.
Want to actually put your Yeastar recordings to use? Talk to us.