Config files not updating

Don't manually edit anything with a _additional.conf tagged on the file.
It will be overwritten by the FreePBX GUI.

Any changes that you make in any .conf file, won't reflect in the FreePBX gui either. System doesn't read those config files. FreePBX stores everything in a mySQL database, and all entries (for argument sake) must be done through the GUI. Once these entries are done, the FreePBX system generates those files and triggers Asterisk to load them into its configuration.

If you have a specific thing that needs to be entered into a standard asterisk .conf file, you should be able to place it in via the FreePBX gui. If you are unsure, post the information and we can tell you how to enter it (just change/hide any vital IP and/or password information first)

You didn't upgrade to Asterisk 1.4, did you?

Try an AMPORTAL Restart, or reboot of the machine?

Sounds like a permissions issue, but nothing i've seen before.

Ok, first of all I thought it was very clear. And as you said, I only asked one question, but did not get an answer to it even now. Your answer is the time of day stamp, that does not answer my question. Time of day stamp will let me know when it was last written, not if freepbx is writing to the correct files. What I'm looking for is a more advanced user to give me an answer of possibly where I might look in some configuration files or something to find out if freepbx is writing to the correct files in the correct directories. And if this is all internal in freepbx, which I suspect it is not and that there is some kind of config file, then there is a bug with freepbx itself. And as far as I know, freepbx is not an actual program, but just web pages or more likely to be called scripts. So somehow somewhere there must be a way to verify the path and files it is writing to. And for anybody that for some reason does not understand my first message, here is a more simple diagram.

Open freepbx GUI => Change Trunk Settings => Click Red Bar => Nothing is changed in sip_additional.conf
And yes, I even tried "amportal restart" and rebooting the server.
This is what works
Edit sip_additional.conf manually => change settings => save files => amportal restart

So far the only thing anyone has mentioned that I may not have understood was that freepbx does not read these files, so I'm assuming somehow it stores this information somewhere else. Can anyone tell me where this information is stored before writing to conf files? Perhaps it is a bug that is not writing these files when I click the red bar.

Thanks for any help.
Jeff

Well, I have the same probelm with trixbox 2.0 after updating all the modules. I eventually end up reinstalling trixbox2.2 and again updating the modules result the same thing.
None of the configuration files was updating, except voicemail.conf. When I tried using #retrieve_conf, i get the following output.
[root@asterisk1 asterisk]# /var/lib/asterisk/bin/retrieve_conf
Content-type: text/html
X-Powered-By: PHP/4.3.11

Checking for PEAR DB..OK
Checking for PEAR Console::Getopt..OK
Checking for /etc/amportal.conf..OK
Reading /etc/amportal.conf..OK
Reading /etc/asterisk/asterisk.conf..OK
Connecting to database..OK
Connecting to Asterisk manager interface..OK

Fatal error: Cannot instantiate non-existent class: ext_waitexten in /var/www/html/admin/modules/blacklist/functions.inc.php on line 66

It seems to me there is a problem with the new update of blacklist modules. So, I have to UNSTALL the blacklist modules and it works !!! Well, it seems to be bug for me. Anyway, hoping to be resolved soon.

Well, i guess, there is option to remove or uninstall the blacklist module. I tried disabling the blacklist module but it did not work, so I uninstalled the module.

By the way, have you changed your username and password at manager.conf, /etc/amportal.conf and crd_mysql.conf (??). ? If you have set the password don't put special character. I read somewhere in other post that special character on password barred freePBX from writing to the configuration file.

PS: I forget the configuration filename now crd_mysql.conf or something like that, as I am not in office, anyway, you can figure it out.

After finding on my own the 3 lines that had the problem, I reported it to freepbx bug tracker. http://www.freepbx.org/trac/ticket/2107 There is already an update to the blacklist module available fixing this problem.

Thanks to anybody that tried to help.

I also just recently updated all my modules and the problem exists. Removing Blacklist in its entirety fixed the problem. To be honest, the blacklist feature has never functioned very well. Many times I have added numbers to the "blacklist" but either they disappear or just are ignored. Its probably better not being active.

Thanks guys, I can stop banging my head against the wall now trying to fix this problem!
Alex

Thanks,

I was just browsing this treah. IT fixed a problem i didnt know i had.

I'd created a new extension and couldnt work out why the phone wouldnt register.

Thanks!