Debian Linux Voicemail Second partition

[Mark Jones]

I have 2.5 TB unused and 3cx is on 300GB is ther any way in 3cx to point the recording to the unused storage?

 

[craigreilly]

Use with Caution.
If I were in your shoes - I'd move the installation to another larger drive entirely.

Settings - Parameter:
Recording Parameter: CALLRECORDSROOT
VM: VOICEMAILBOX_PATH and VOICEMAILBOX_WEBACCESS_URL

 

[JohnS_3CX]

Hi @Mark Jones

What version is your PBX ?

 

[Mark Jones]

Hi @Mark Jones

What version is your PBX ?

16

 

[Mark Jones]

Use with Caution.
If I were in your shoes - I'd move the installation to another larger drive entirely.

Settings - Parameter:
Recording Parameter: CALLRECORDSROOT
VM: VOICEMAILBOX_PATH and VOICEMAILBOX_WEBACCESS_URL

so just re install on the bigger drive?

 

[JohnS_3CX]

The correct way to do this in V16 will include copying your existing recordings to the new location. Best done at a time when no calls are taking place to avoid losing any recordings being written.

1.) Create a new Recordings folder on your 2.5 TB volume (I assume this to be a local volume with block-level access, as NFS is not supported).

2.) Go to Recordings, click Location and make the location point to the new folder you wish to use on your 2.5TB drive.

3.) You should now manually copy the contents of your old Recordings folder into the new destination folder so the system will find them in the same directory layout and naming scheme as before.

The system has now dynamically updated the path and you should be able to download recordings off the new location from the MC just like before the move took place.

Note: Once done, keep in mind that any past-generated call reports will no longer point to the recordings, but future generated reports will correctly point to the new location (referring to the download-recording links embedded in call reports as hard links).

 

[Mark Jones]

The correct way to do this in V16 will include copying your existing recordings to the new location. Best done at a time when no calls are taking place to avoid losing any recordings being written.

1.) Create a new Recordings folder on your 2.5 TB volume (I assume this to be a local volume with block-level access, as NFS is not supported).

2.) Go to Recordings, click Location and make the location point to the new folder you wish to use on your 2.5TB drive.

3.) You should now manually copy the contents of your old Recordings folder into the new destination folder so the system will find them in the same directory layout and naming scheme as before.

The system has now dynamically updated the path and you should be able to download recordings off the new location from the MC just like before the move took place.

Note: Once done, keep in mind that any past-generated call reports will no longer point to the recordings, but future generated reports will correctly point to the new location (referring to the download-recording links embedded in call reports as hard links).

how to do this in linux?

 

[usti]

how to do this in linux?

Mark,

It sounds like you may not be super familiar with Linux systems administration. If this is the case, I would recommend having an experienced Linux systems administrator handle steps 1 and 3 for you as they will understand how to determine where the additional storage is located, where to mount it, how to make it remount after a system reboot, and copy the files from the old location to the new location.

I prefer not to offer details on how to perform these steps yourself in this forum as it would require making some assumptions that could lead down a rabbit hole and undesired outcomes (not to mention potential liability).

 

[ucme4now]

I agree with USTI on posting the steps here. The concept is the same in linux as it is in the Windows world. Expand the volumes, mount the drive format it. etc. I just went through this a few weeks ago because the initial VM I setup for the customer did not take into consideration call recording. It was not part of the initial services. Now they want call recording and the issues revolving around storage, the number of users being recorded and the amount of time they want to save the recordings are the primary issues. A week is not a problem a month or more become very problematic in terms of the amount of storage.

For example, I have a single user client blowing through 2GB of storage every 21-days. He records all calls for order verification. He only needs access to the calls for 21-days so I set the Quota up to accommodate that and the flush the old recordings to keep the VM disk space in check. So before you add more disk space make sure you have a through discussion about what the actual storage needs are or you will be scrambling again to add more space or you'll be deleting the old stuff.

The PBX permits you to point to the folder (directory path) where you want to store the calls. You can add the storage to accommodate this relatively easily. If you are not familiar with linux, spin up a test server and Google "adding disk space debian" and read through each link one before you do anything. The terms are unfamiliar but as I said earlier if you are familiar with Windows, the concept is pretty much the same. I'm running VMWare on the host so the steps are different as compared to Hyper-V again the concept is the same. The good news is the PBX is Debian so you aren't having to deal any variances in the linux distros from a command line perspective.