reinstalling and locking down trixbox – gotcha with extensions_additional.conf
I installed a new version of Trixbox over a > 1yo version a few days ago in an effort to clear up a set of minor but annoying problems. These included dropped calls, one way audio, no-response IVR, poor audio – but they were all intermittent and poorly documented problems. As the existing install was an RC-but-one release, and as there have been many nice improvements since then, I decided to take the risk and do a complete upgrade.
First I saved all the settings – literally by doing 20-30 screen captures. Then I copied off the custom .wav files for the ivr. I neglected to grab the voicemail prompts and should have.
Anyhow, I got everything going, including, amazingly, the sangoma card firing right up with no problems after a setup-sangoma, and then today I went back to sort out the security as everything was on the default settings. Not a big deal as its behind a m0n0wall firewall, but I like to follow the appropriate sureteq guide to lock down mysql and the various default passwords in trixbox and freepbx.
When I’d stepped through everything and went back to tweaking something else, I noticed that the IVR was no longer forwarding successfully. Quite a bit of head scratching later, and a power cycle (a bit tricky when you’re 300 miles away), I worked out that it was changing the amp password itself that was the problem. A little grep magic later, and I found a stray amp11 password in extensions_additional.conf and after I corrected it, everything was working again.
My guess is that if I’d changed the password before doing all the config I would have been ok, but I haven’t dug into things enough to work out if that is true or not. Similarly, I’m hoping that if I make more changes via FreePBX that it will do the right thing, but I’m guessing it will be ok.
