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 as for applications?
Or all of them are supported from gooey?
If not then i have to read the manual(which i already started with) in order to know where i should configure
and would not interfere with freepbx âapply changesâ then reload, right?
Same thing for modules, functions, applications, channel drivers, language used for AGI, everything in fact.
FPBX uses a subset of asteriskâs abilities that you can manage with a bunch of provided php and javascript code which run within a webserver but also provides plenty of âhooksâ to add your own function.
â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
Pretty well, fwconsole reload applies any pending changes to âadditionalâ files then applies a dialplan reload` so changes you made will also be applied.
Just to make things straight:
1-I should add my dialplan in the right place which is in one of the extensions.conf additional files
2-fwconsole reload
3-dialplan reload
I hope this is right
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.