Dialplan Injection module added to trixbox

I added the Dialplan Injection module to PBXconfig today. You can download it using Module Admin in PBXconfig. This is an advanced module that lets you add pieces of dial plan into your call routing. This will let you do just about anything.

Here is a quick description of the Dialplan Injection from it’s creators at http://aussievoip.com.au

This module allows you to create short custom dial plan fragments. While such fragments can also be added to extensions-custom.conf, the advantage of creating them in this module is that the resulting dial plan fragment can be directly selected as a destination in modules that use destinations. Optionally, the dial plan fragment can also be accessed directly by calling an extension number. Just about anything that could be put into extensions_custom.conf can be placed in a Dialplan Injection.

WARNING: This module bypasses many of the safety checks of PBXconfig. It is very easy to screw up your system using this module. If you add a Dialplan Injection to your system and anything strange happens please remove and test again. Even if the problem doesn't seem to be related.

This can be an replacement

This can be an replacement for CustomContext?

Does Not apear in my PBX Modules???

Have just tired to add it and it does not apper when I do a Module Admin from the from the Admin Tools section. Any ideas?

Dialplan injection is a nice

Dialplan injection is a nice module that naftali wrote for FreePBX quite some time ago (same author as the custom context module). In adding it to trixbox, I hope you will take it upon yourself to update it so that it properly inter-operates with the current version of FreePBX that you are using.
To clarify, any module that provides destinations that can be used by other modules, or that provides extensions that can be dialed, must supply the proper API calls that allow FreePBX to do integrity checks for broken links, and avoid duplicating extension numbers. (This is how the extension and destination registries are implemented). In its current state these are not present and you can easily end up with broken IVRs and other call flows, or replicated extensions that result in un-predictable and un-stable behavior of your PBX.
Genuine FreePBX installations do not include this module in the repository (Module Admin), partially because of this limitation, since FreePBX is very committed to maintain extremely solid and stable functionality within the offerings that are supported on its online repository.
We look forward to seeing these updates to this module to assure that users of FreePBX (well in this case PBConfig) continue to experience the level of reliability that they have come to expect out of the functionality automatically loadable inside of FreePBX.

Thanks for point this out

Thanks for point this out philippel. I added dial plan injection for advanced users. These users would normally be adding this stuff to extensions_custom. I warn people that it could break their systems. I think it would be hard to make a module like this safe enough for the average user. Even if it checked for extensions use using the FreePBX API it would still be very easy to screw something up using this module. I'll add more warnings to it when I get the change. Thanks again.

you are correct, clearly for

you are correct, clearly for advanced. You may want to have a look none-the-less about adding the API calls. You can look at modules like ring groups which provide both type (extension registry and destination registry) to see where they go, and then there is typically a little bit of ugly code in the page.xxx.php file to check for the duplicate extensions before allowing them to be added.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.