...
When the Called Number is processed against this single transformation, the Called Number must match the regex value in the Input Field Value. If the Input Field Value does not match the Called Number, this transformation will fail, and so will the route entry that called this transformation talbetable.
...
Note |
---|
In the example above, there is only one transformational entry for Calling Extension and Calling Address/Number Input Field Types. If there is only one transformation for a particular Input Field Type, then the Match Type setting for that entry is irrelevant. Each Input Field Type must have at least one successful transformation. If there is only one transformation entry for a particular Input Field Type, like the Calling Extension above, then that transformation must be successful. In this case of a sole Input Field Type, the configuration of the Match Type, either Mandatory or Optional, has no bearing: that tranformation must succeed or the tranformation table will be false (failed). |
...
There are several transformation entries for Called Address/Number Input Field Type and those all have a Match Type set to Optional. In addtion to the outcome evaluation of the Redirecting Number, at least one of the Called Number transformations must be successful for the translation table to be true (passed)..
The table below is the same as the table above, with an additional Called Number transformation entry at the bottom of the table.
Panel | |||||||
---|---|---|---|---|---|---|---|
| |||||||
|
The addtional additional Mandatory Called Address/Number means only the Mandatory translation must match the transformation table to possibly be true, with respect to the other Called Number Optional translation entries. Of course, the Redirecting Number transformation entry must also be evaluated in order to determine whether the transformation table will be ultimately true (pass) or false (fail).