Outgoing call component
:icons:font :hardbreaks: :imagesdir: ../../../assets/images :toc-title: Contents :toc:
Description
Calls a subscriber by number and transfers trunk control to the IVR script.
Index |
|
Short name |
|
Script types |
|
Start module |
|
Mode |
Asynchronous |
Icon |
|
Branching type |
Branching, closing |
Properties
| Specification | Description |
|---|---|
Name: Mode Code: Visibility condition: no Default: Asynchronous |
The operating mode of the component after sending a request for an outgoing call to the selected IVR server. Possible options:
|
Name: Number Code: Visibility condition: no Default: — |
Subscriber number. The standard routing call process applies. |
Name: Outgoing number Code: Visibility condition: no Default: — |
Initiator number, inserted as username in the |
Name: Outgoing name Code: Visibility condition: no Default: — |
Initiator name, substituted as displayname in the If no value is specified, then the URI does not contain a displayname. |
Name: Additional headers Code: Visibility condition: no Default: — |
Additional headers inserted into the SIP request. The argument contains a multi-line value, the format of each line is Used to add new custom headers, the default header values cannot be changed in most cases. |
Name: Script Source
Code: Default: From the list |
Possible options:
|
Name: Script body Code: Visibility condition: yes Default: — |
An argument containing a JSON structure with the body of the IVR script (a JSON array packed into a string). The structure format is similar to the section `scriptdata.objects`" in the entity IVR script. |
Name: Script Code
Code: Default: — |
Argument with the IVR script code in the current domain. |
Name: Script Code: Visibility condition: no Default: — |
Drop-down list with script codes. Contains all available (unhidden) IVR scripts contained in the current domain. |
Name: Script Variables Code: Visibility condition: yes Default: — |
An argument containing a JSON structure with script variables (a JSON array packed into a string). The structure format is similar to the “scriptdata.variables” section in the IVR script entity. Used when specifying the script body as JSON. |
Name: Variable values Code: Visibility condition: no Default: — |
Table of initial values for local variables of the IVR script launched to service the initiated call. Keys are the names of IVR script variables. Matching occurs by variable names, values are assigned only to those variables that are defined in the script. If the launched IVR script transfers control to a nested script, then the assignment of values to each of the specified variables is carried out no more than once, but can be delayed until the nested script that has a variable with the corresponding name is loaded. Values set this way take precedence over default values within the IVR script. |
Name: Parameter 1 Code: Visibility condition: yes Default: — |
First parameter for the triggered IVR script. The value is accessed through the |
Name: Parameter 2 Code: Visibility condition: yes Default: — |
Second parameter for the triggered IVR script. The value is accessed through the expression function |
Name: Parameter 3 Code: Visibility condition: yes Default: — |
Third parameter for the triggered IVR script. The value is accessed through the expression function |
Name: Parameter 4 Code: Visibility condition: yes Default: — |
The fourth parameter for the triggered IVR script. The value is accessed through the expression function |
Name: Parameter 5
Code: Default: — |
Fifth parameter for the triggered IVR script. The value is accessed through the expression function |
Name: Other parameters Code: Visibility condition: yes Default: — |
JSON array containing parameters 6, 7, 8, etc. for a triggered IVR scenario. The value is accessed through the expression function |
Name: Time, s Code: Visibility condition: yes Default: — |
Time limit for waiting for the subscriber’s final response, in seconds. |
Name: SIP response code to variable Code: Visibility condition: yes Default: — |
Variable for storing the last received SIP response code (1xx-6xx). When waiting for a preliminary SIP response, there will be either a preliminary response (1xx) or a final response (2xx-6xx) |
Name: Transition Code: Visibility condition: no Default: — |
The component to which control is transferred if the operation completes successfully. |
Name: Transition, failure Code: Visibility condition: no Default: — |
Component to which control is transferred in case of unsuccessful final SIP response (4xx-6xx). If not filled in, the transition is carried out along the standard branch. |
Name: Transition, no response
Code: Default: — |
The component to which control is transferred if the waiting time for receiving the final SIP response expires in the final and script completion waiting modes, or the preliminary response in the preliminary response waiting mode. If not filled in, the transition is carried out along the standard branch. |
Name: Transition, error Code: Visibility condition: no Default: — |
The component to which control is transferred if any error occurs during the call initiation process. If not filled in, the transition is carried out along the standard branch. |