Unable to add /var/lib/asterisk/sounds/custom/filename.wav - Can not read file!

I have tried everything on the forums with no luck . after i installed freepbx 2.3.0 beta everything is fine exept the system recordings. when i try to record an incomming msg using an extention and the *77 it does not work after i enter the filename and hit save this is what appears "Unable to add /var/lib/asterisk/sounds/custom/filename.wav - Can not read file!" Does anyone know the fix for this or are they working on it?

Please someone help !

I am also having this issue. The recorded .wav file is being saved into /tmp, and I can copy it across as '/var/lib/asterisk/sounds/custom/filename.wav' to get the recording going, but for some reason, the system is not doing this for me. I am running Asterisk 1.4.6 and freepbx 2.3beta2.1 with version 3.3.4 of the recordings module.

this happened to me also with 2.3beta2.

It seems that it's a visual interface presentation issue.

Step1 and Step2 are presented on the screen. If you enter your extension in step 1 and don't press GO, but instead add the recording name, do the recording with *77 and press save, you immediately get the error.

The file is there, and *99 plays back the audio file, but they aren't correctly associated if you didn't enter your extension and press GO first.

You can get this error if you simply forget to record.

Workaround is to press GO after entering the extension number.

This is not the case for me. I enter my extension and click 'GO'. I dial *77 and record my message and press #. I hang up and go back to the system recordings screen and enter a name for my recording and click save and I get the 'Unable to add /var/lib/asterisk/sounds/custom/testing123.wav - Can not read file!' error. If I dial *99, I can listen to my recording, I just cannot save it using system recordings.

I have been able to reproduce this error in one way only. When running Asterisk as root. The file gets saves with an owner of root. Then FreePBX tries to move the file running as Asterisk which results in an error. A similar situation could happen if you were running apache as something other than Asterisk.

I have changed the 'mv' command to a 'cp' followed by an 'rm' command with error reporting at each stage. So if running Asterisk as root (highly discouraged), the recordings should still work but you will see errors when trying to remove the old tmp file.

If the error persists, then reopen with more infomration and hopefully more useful message now.

r4574 (2.3)
r4576