Asterisk and FreePBX configuration boundaries
FreePBX manages an Asterisk system through its own settings, modules and generated configuration. Before applying a raw Asterisk example, identify which component owns the setting and how the managed system expects it to change.
Source-reviewed, 20 October 2026. Prepared from the cited documentation. No FreePBX deployment has been independently tested by Phone Guides. Scope: configuration ownership and review method; supported customisation depends on the exact FreePBX, module and Asterisk versions.
Record the installed system
Record the FreePBX release, Asterisk release, relevant module versions and installation/distribution. Keep the administrative interface's saved values separate from generated files and the running Asterisk state. A difference between them may explain why an apparently correct edit disappears or is not loaded.
The official Sangoma FreePBX documentation is a starting point for product-specific instructions. Verify the version and module scope of a page; a community contribution hosted in the same documentation system is not automatically a present vendor support guarantee.
Find the owner before editing
| Desired change | First decision |
|---|---|
| Extension, trunk or route | Which supported GUI/module setting owns it? |
| Custom application context | Which documented customisation point calls it? |
| PJSIP endpoint option | Is there a managed field or supported custom include? |
| Module-generated behaviour | Will a module update regenerate the relevant output? |
| Direct Asterisk CLI change | Is it temporary state or persisted through its owner? |
Do not replace a generated pjsip.conf or extensions.conf with a standalone Phone Guides example. Our examples explain Asterisk objects and routes; they are not whole-system FreePBX replacement files.
Verify the extension point
Sangoma's dialplan customisation presentation includes custom-context examples. It is a dated community reference. Confirm the supported entry context and file/include for your installed version before using its pattern.
For module-level generation, Sangoma's BMO dialplan-hook and Extensions class documentation describes callbacks that add entries to the generated dialplan during configuration application. The FreePBX 17 Core module definition declares a get_config callback; that source is evidence for the named module branch only. These are module-author mechanisms, not a promise that a custom module is supported on every managed installation. They also do not define a long-running ARI application's start, supervision, call ownership or cleanup. Treat generated dialplan and a live call-control service as separate responsibilities, and establish the exact supported module/version path before relying on either.
A filename containing custom does not by itself prove that every setting belongs there. Record who includes the file, which context calls the code, what arguments are passed and how returning control works. Keep access to the custom context as narrow as the task needs.
Apply through the configuration owner
Preserve the prior managed settings and custom source. Use the product's supported apply procedure, then inspect both persisted settings and running Asterisk objects/dialplan. Check warnings and rejected objects. A successful GUI save is not the same observation as a working call route.
If a module or system upgrade is planned, review its compatibility and migration instructions before changing the underlying Asterisk packages independently. Preserve a recovery set that includes the managed configuration and database, not just a selection of generated text files.
Reader checks
On the exact installation, check the intended feature, a denied route and normal call termination. Reapply the managed configuration and confirm that the custom behaviour persists. Include the relevant module versions in any published result.
Use backup and restore for recovery inventory and legacy dialplan review for version-specific application checks. Keep raw Asterisk and managed-product instructions visibly scoped so readers know which owner to use.
Return to Asterisk documentation.