The directory is default, but I have separetely installed Fop2 and the directory is mounted by cifs. In my case nfs is no option for us. But its no problem to remove files from it by console.
If your voicemail path is not standard, you will find to set it correctly in /usr/local/fop2/fop2.cfg. If that is already done, then you might have issues with file creation on your CIF share, in order to manipulate voicemails a lock file is created on the same voicemail directory, that is unavoidable, and it is safe.. If your system gives you that error, it means it is not allowed to write the lock file (lack of write permissions on file or execute permission on path).
Its strange. I thinked you use something like flock().. Yes, I already did this. I see voicemail, can play it and download. But cannot move or remove.
I set all (777) permissions on the directory and files in this directory. If my file is
My problem was in permission to create link from .lock-xxxx to .lock
Now after deleting voice messages the lock files is not removed and used by fop2 (I cant remove them manually by rm unless restart fop2). What fop2 waiting for?
As I see in log, it was twice opened and ones closed. I cant remove .lock-xxxx bacause its opened for 'write only' by fop2.
This was solved by remove 'cache=no' from fstab.
Now all works fine.
Comments
Best regards,
I set all (777) permissions on the directory and files in this directory. If my file is
/var/spool/asterisk/voicemail/sip_viocemail/100/INBOX/msg0000.wav
Where and what lock file will be created? From /var/spool/asterisk/voicemail/sip_viocemail/100 und up all 777 permissions, as I sad before.
Now after deleting voice messages the lock files is not removed and used by fop2 (I cant remove them manually by rm unless restart fop2). What fop2 waiting for?
As I see in log, it was twice opened and ones closed. I cant remove .lock-xxxx bacause its opened for 'write only' by fop2.
This was solved by remove 'cache=no' from fstab.
Now all works fine.