Configuring features.conf options

This should be editable from the feature codes module

This should be editable from the feature codes module

Module to manage features.conf

I've attached the module I created to manage features.conf -- HOWEVER! It is not compatible with the new parking module (which also plays with features.conf). I will leave it as an exercise to the FreePBX gurus on how to resolve both. :)

here's my 2 cents. The main purpose of the parking module that I wrote was to generate a dialplan and provide and ability to trap orphaned parked calls and send them somewhere useful similar to the way destinations can be chosen for many other modules. Since I was writing that part, I threw in the rest of the parking configuration parameters to keep them all together.

I have not brought up this features module but I did take a quick scan and it basically does as advertised, sets variables for the features.conf file.

My 2 cents is that there is no reason why both can't co-exist separately with some minor changes. The parking module does not write out features.conf, it just includes a features_additional.conf file to bring in the parking lot settings. I would suggest that this module gets modified to generate a different file, rip out all the parking settings which can be handled by the parking module, and then make sure the includes can co-exist in the main features.conf file so that both work.

An alternative option would be to expand the parking module to include the other settings this handles, basically mergint this into the parking module. As mentioned, the pakring module generates dialplan code in extensions_additional.conf beyond the simple task of setting some parking variables. It is also structured in its database to accomodate a future version when there are multiple parkinglots (although the gui code will have to be modified for that).

Yeah, I wrote my module because there are some features.conf clashses with other FreePBX feature codes and I got irritated about changing it every time. :) Feel free to go nuts changing my module to suit, I'm happy with that.

Not really been following this, BUT isn't the answer to write a module that setup us, using the normal FeatureCode? stuff, the core Asterisk features and then write out the features.conf or features_additional.conf or whatever ?

Moved this to 2.3 - whilst it's a good idea, and I agree with wozto1s' suggestion, it'll be to hard to do 'soon'. Needs discussion.

Milestone 2.3 deleted

this has been achievable since 2.4 and specifically codes like transfer and blindtransfer are in the feature code panel.