Call Recordings - some advice and maintenance tips

[Voipy]

Currently we record in .wav and run a script nightly to convert this to mp3 and change the filename in the db to reflect this, to save space. We decided on this years ago for fear of putting load on the server by recording in mp3 format right away. Seeing that we are looking to start from scratch with FS PBX we want to simplify things where we can. What are people's thoughts on recording as mp3? Does it really increase the load significantly, or is it not something to really worry about?

On maintenance - we have always just run a script to delete recordings that are older than X, and excluded some domains of customers who have longer retention periods. That's prone to mistakes and more importantly cannot be set by just a support agent. Our version of Fusion is a bit older - I see that there are some options now to set "days to keep recording" on a global level. There is also some maintenance module I came across but haven't looked at at this point.

Is there currently a way to set this in the GUI on a per domain level? And if not, is it something that is on the roadmap? Alternatively - are there easy ways to deal with this currently?

 

[pbxgeek]

I have some great news. FS PBX includes a module that automatically runs overnight to upload call recordings to AWS. As part of the process, recordings are converted to MP3 format to help reduce storage costs.

Once uploaded, recordings can still be played and downloaded directly from the Call History page, so there’s no change to the user experience.

Most FS PBX customers have had very few storage concerns because this works so effectively. In many cases, they retain recordings in AWS for one to two years (depending on their requirements) while keeping costs relatively low.

FS PBX also supports AWS storage settings at both the global and per-domain level. This means if one of your clients prefers to store their own recordings for compliance or internal policy reasons, that can be configured as well. In that case, recordings will still play directly from the Call History page, but they will be served from that client’s own S3 storage.