Solved No recording files for some extensions

[Carrosserie Forthomme]

Our extensions record all calls. The problem is that the sound files do not exist for some extensions.

For these problematic extensions, the record line does exist in the record list, in the web interface. If we try to download this recording, we get a "404 Requested resource not found" message. If we look in the recording directory of this extension, we see that the sound file is not present.
What is very strange is that this exists for some extensions and not others which have the exact same configuration in 3cx.
Extension 02 works and extension 07 does not work, with identical parameters:

• Phone brand, model and firmware (Yealink T46)
• Network
• Codecs
• Options (including Call recording with Record all calls checked.

Activity log confirm recording but no file : "05/20/2021 11:36:46 AM - [CM503023]: Call(C:786): Call recording is stopped, audio file: /var/lib/3cxpbx/Instance1/Data/Recordings/07/[Pupitre]_07-0475535290_20210520093632(786).wav"

I reprovisioned, rebooted the phones and the entire system. This recording problem persists ...

My licence is Professional Perpetual 16.0.8.9.

Someone can help me ?

 

[ChrisC_3CX]

Do these affected extensions have no recording files in their recording folder at all? Since the host is a Linux machine, first thing I would recommend checking is the file permissions for the folders of the affected extensions. SSH to the machine, navigate to /var/lib/3cxpbx/Instance1/Data/Recordings/ and make sure that all extension folders permissions are as follows:
drwxr-xr-x 3 phonesystem phonesystem

If this is already the case, please let me know if newly created recordings for these extensions do not get created either.

 

[Carrosserie Forthomme]

My solution...

Change the name of the 07 directory to 07old, then make a call with the 07 extension. The 07 directory is automatically recreated with the sound file of the recording in it. YES! Transfer all old files from 07old to 07. Delete the 07old directory. Make this for all problematic extensions.

Regenerate the database by setting the RECS_SYNC_REQUIRED parameter to 1. Click on "Click to convert recordings!" in the dashboard.

In my case, I used FileZilla on the IP of 3cx (port 22). Use the user and password of the 3cx system installation!

 

[Carrosserie Forthomme]

This problem is certainly due to an importation of the recordings. 3cx windows to 3cx linux.
This problem should be self controlled by 3cx...

 

[ChrisC_3CX]

This problem is certainly due to an importation of the recordings. 3cx windows to 3cx linux.
This problem should be self controlled by 3cx...

The correct way of importing recordings is making sure that the backup file used to migrate the 3CX PBX also contains the recordings.

That said, even if you do manually move the recordings to the recordings directory and then make sure that the file permissions are in order, using the recordings sync method should work without issues.

 

[Carrosserie Forthomme]

I confirm that during the new installation, we obviously imported a complete backup file (zip from 3cx).

And I think you're right, it was definitely a directory access right issue. Thanks for your help.

 

[ChrisC_3CX]

You're very welcome, glad the issue has been resolved! Please feel free to post a new thread should you need additional info or assistance!