I’m trying to set up without resorting to disabling SELinux. It refused to write voicemail files for a while but a relabel fixed it, although I don’t quite understand why. Now it refuses to run agi scripts. I tried the audit2allow method against the log file without any luck. The agi directory and script have the following protections:
[code]drwxr-xr-x. root root system_u:object_r:asterisk_var_lib_t:s0 agi-bin
-rwxr-xr-x. root root unconfined_u:object_r:asterisk_var_lib_t:s0 astermail.agi
and here is the audit log message
So it seems that the asterisk process is using asterisk_t while the file and directory are asterisk_var_lib_t. I could go and study SELinux for another week and perhaps come up with a solution, but the worry is that I’ll go down some very non-optimal path. Surely whoever set up the SELinux rules for Asterisk and Centos 6 thought about agi.
I went down this path because the System() application doesn’t like really long command lines.
Any help is, of course, greatly appreciated.
An update of sorts. Talking to a colleague it might be a disconnect between asterisk from source and the Centos asterisk policy module.