- Joined
- Sep 12, 2011
- Messages
- 10
- Reaction score
- 0
I've got a weird deal I need some help on. I just installed my first Elastix units (was a Trixbox and raw Asterisk shop before). I installed 3 systems and two of them are exhibiting this odd behavior where the Voicemail.conf file is spontaneously changed back to it's default form with no extensions listed.
The result is of course that voicemail goes away for all extensions. Since this happens about once a day I've made a backup of the voicemail.conf file and just copy the correct one back into place, but obviously that's not a good long-term solution.
For a few days I also set the file as read-only and that prevented the overwrite, but users can't change passwords, so that doesn't work.
Now I have a script running that checks the voicemail.conf file every minute and emails me when this happens so that I can try to change it back before anyone notices.
First, the easy question: Has anyone seen this happen and solved it?
Assuming the answer that question is no, what could possibly be executed that would be making changes to this file? I'm 99% sure it's not the UI that's doing it because the file modification times on the new file reflect that the overwrite happened when there was no one logged in. Is there something that fires at pre-defined intervals and checks config file syntax or something? I know that sounds bizarre, but that appears to be what's happening.
Also possibly important. I manually added a line to the voicemail.conf file "#include vm_custom.cfg" This file includes a bunch of voicemail only extensions. That line is the obvious place to look, but I have this line on all three systems and only two are exhibiting the problem, so the problem must be more complex.
The result is of course that voicemail goes away for all extensions. Since this happens about once a day I've made a backup of the voicemail.conf file and just copy the correct one back into place, but obviously that's not a good long-term solution.
For a few days I also set the file as read-only and that prevented the overwrite, but users can't change passwords, so that doesn't work.
Now I have a script running that checks the voicemail.conf file every minute and emails me when this happens so that I can try to change it back before anyone notices.
First, the easy question: Has anyone seen this happen and solved it?
Assuming the answer that question is no, what could possibly be executed that would be making changes to this file? I'm 99% sure it's not the UI that's doing it because the file modification times on the new file reflect that the overwrite happened when there was no one logged in. Is there something that fires at pre-defined intervals and checks config file syntax or something? I know that sounds bizarre, but that appears to be what's happening.
Also possibly important. I manually added a line to the voicemail.conf file "#include vm_custom.cfg" This file includes a bunch of voicemail only extensions. That line is the obvious place to look, but I have this line on all three systems and only two are exhibiting the problem, so the problem must be more complex.