Step 20. IVR (Interactive Voice Response)

The auto service is SIP-UA, respectively the nature of interaction with it is completely similar to the case of a call to the conference at step 19.

In order for an autoservice to run, the domain must exist:

The IVRScript role maintains the IVRScript instance of the IVR script. It is redundant and scalable in Active-Active mode. Similar to a conference, service is performed at the site closest to the call initiator, serving the domain in which routing is applied to the caller function code and the script itself. The IVRScript role uses its own media context, in which players and recorders are added in addition to the caller. IVRScript supports all kinds and directions of transfers.

As soon as the call reaches the IVRScript role, a script handler is immediately activated there and the specified script is loaded into it IVR.

Each scenario IVR is an algorithm created by the administrator in the visual editor. The administrator adds abstract scenario components to the script, parameterizes them, and links them in the execution sequence. The scenario is executed until the subscriber hangs up, until the scenario is terminated (STOP components, transferring the subscriber to a specified number, terminating the connection). There are also various error situations that also interrupt the script handler.

Each scenario component is responsible for abstract functionality that the administrator uses at his discretion. To transfer data between components, scenario variables are used, or other data areas located on disk in the database or other external resources.

Any call to the IVR auto service starts with the START component and requires a response from the IVR server - the SIP-response component. In addition to a successful response (code 200), which establishes a communication session, any unsuccessful response can be sent, effectively terminating the connection.

A special feature is the ability to configure a post-processing branch in the script that is activated by a particular scenario completion code.

Some components of scenarios:

The data for components are parameters that the administrator defines using arguments. The arguments can be constants (numeric, string and date/time), scenario variables, arbitrary expressions using standard syntax, a large list of scenario functions, and extended syntax Erlang.