ExtensionExists
Description (v1.0.0)
This action checks if a given extension exists in a given context
In case the LARGE_INTERNAL_DIRECTORY flag is set, the lookup will be done in the database
If it is not set, the built-in asterisk command VALID_EXTEN will be used
Extension: [Extension]
Release notes
Version 1.0.0 - Early deployment
- Feature: Initial version
- Dependency:
Action parameters
- Extension: The extension that needs to be checked
- Context: The context in which the extension needs to be checked
Limitation
- only works starting from Communication server 2.X
- In case a large internal directory flag is set, the lookup will be done in the database instead of using the built-in asterisk function
- In case of database lookups, ranges are not supported (ex: 26860909 will not match on _2686090X)
- In case of database lookups, the exact configured route group or restriction group needs to be given (ex: When checking if an extension exists in the RestrictInternal restriction group (which contains the internal routeGroup) but the extension has been configured in the internal routeGroup, the result will be 'not found')