Bugfix: Warnings were logged when using unlimited mode (M9061)
Version 1.6.0 - General deployment
Improvement: Remember source and destination extensions (M7540)
Version 1.5.0 - General deployment
Improvement: possibility to limit redirect to maximum 1, 2 or 3 iterations.
Version 1.4.0 - General deployment
Bugfix: Redirect limit was not working on CS2 (M6805)
Version 1.3 - General deployment
Improvement: Compatibility with the Communication Server module
Version 1.02 - General deployment
Feature: Added possibility to limit the number of times a call can go through a redirect action (M0004416)
Version 1.01 - General deployment
Feature: Potential update impact level 3 : in the event this update contains a bug, it might have critical impact. Given the complexity of the update, it is advised to contact ESCAUX support before applying this update. Added possibility to set the next context. The default context is 'default'
Version 1.00 - General deploymentVersion 0.0 - Deprecated
Action parameters
number: Number where to redirect the call
context: Context (Restriction Group or Route Group) where to redirect the call. If not specified, the call will be sent to the 'default' context.
For security reason, the default context is set to 'default'. This is suitable for most cases, except when redirecting to an outside contact not located on the SOP, such as a mobile phone. In that case, a specific context must be selected, such as 'NoRestrict'.
Limit: The maximum number of times a call can go through the branch on which this action is located. This option provides a way to prevent loops in callflows. By default there isn't any limit.