|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Brief description that will be published in the Extension Registry about this extension
|
Medium |
|
|
|
|
|
|
Choose un-identified destinations on your system to add to the Custom Destination Registry. This will insert the chosen entry into the Custom Destination box above.
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Custom Destinations allows you to register your custom destinations that point to custom dialplans and will also 'publish' these destinations as available destinations to other modules. This is an advanced feature and should only be used by knowledgeable users. If you are getting warnings or errors in the notification panel about CUSTOM destinations that are correct, you should include them here. The 'Unknown Destinations' chooser will allow you to choose and insert any such destinations that the registry is not aware of into the Custom Destination field.
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Custom Extensions provides you with a facility to register any custom extensions or feature codes that you have created in a custom file and FreePBX doesn't otherwise know about them. This allows the Extension Registry to be aware of your own extensions so that it can detect conflicts or report back information about your custom extensions to other modules that may make use of the information. You should not put extensions that you create in the Misc Apps Module as those are not custom.
|
Medium |
|
|
|
|
|
|
DUPLICATE Extension: This extension already in use
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Does this destination end with 'Return'? If so, you can then select a subsequent destination after this call flow is complete.
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Invalid Destination, must not be blank, must be formatted as: context,exten,pri
|
Medium |
|
|
|
|
|
|
Invalid Extension, must not be blank
|
Medium |
|
|
|
|
|
|
Invalid description specified, must not be blank
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
More detailed notes about this destination to help document it. This field is not used elsewhere.
|
Medium |
|
|
|
|
|
|
More detailed notes about this extension to help document it. This field is not used elsewhere.
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Registry to add custom extensions and destinations that may be created and used so that the Extensions and Destinations Registry can include these.
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
Set the Destination after return
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|
|
|
The entered extension conflicts with another extension on the system
|
Medium |
|
|
|
|
|
|
This is the Custom Destination to be published. It should be formatted exactly as you would put it in a goto statement, with context, exten, priority all included. An example might look like:<br />mycustom-app,s,1
|
Medium |
|
|
|
|
|
|
This is the Extension or Feature Code you are using in your dialplan that you want the FreePBX Extension Registry to be aware of.
|
Medium |
|
|
|
|
|
|
WARNING: This destination is being used by other module objects. Changing this destination may cause unexpected issue.
|
Medium |
|
|
|
|
|
|
|
Medium |
|
|
|
|