Not all modiles are supported by FPBX directly (examples would be radius or pgsql or corosync ), but asterisk is asterisk so if the modules are compiled, configured and loaded , they will work as advertised even if you cant get to do that from the gooey
Same thing for modules, functions, applications, channel drivers, language used for AGI, everything in fact.
‘apply changes’ will effectively rebuild all *additional.conf files in astetcdir and then ‘reload asterisk’ , if you work within that behavior , then evey-body is happy
If i understood exactly what i said, you mean apply changes will affect additional.conf files thus i must add anything i need in a file where apply changes must not affect! Then i restart asterisk, then everybody is happy
There are files in the configuration directory that have “custom” and “override” in their names. For example, 'extensions_custom.com" would be where you put elements that do not replace or compete with FreePBX and Asterisk pre-defined contexts.
Let’s say you needed to add a context called “call-dtmf-from-cat”. Well, there’s nothing that looks anything like that in ‘extensions.conf’ (the Asterisk config) or ‘extensions_additional.conf’ (the FreePBX config), so you can add it to ‘extensions_custom.conf’.
If there is a point of competition, then you’ll need to use the ‘extensions_override_freepbx.conf’ (SIC, check in /etc/asterisk) file. This loads first, so the stuff supplants the stuff from both the extensions.conf and extensions_additional.conf.
Now, your documentation may say something like "Add the following line to the context ‘from-pstn’ or ‘default’. You can use the ‘override’ context to actually change the standard ‘from-pstn’ context or you can add a new context in the custom file and change the name.
In FreePBX, the ‘default’ context is ‘from-pstn’ (we don’t use ‘default’) so your choices may seem to get overwhelming. When you get to the point you need specific advice, we’ll be here for you.