Skip to content
Call Interactive

Interactive Request Parameters

This page describes the request parameters used by Call Interactive.

Custom Request Parameters

The system can add to the HTTP request extra parameters that pre-configured an IVR or are specific to that IVR only.

Static Parameters

The parameters will not be changed by the service as they are pre-configured with a static value. To use them, your URL must have the following structure:

http(s)://<host>.foo.com?custom_variable1=1&custom_variable2=2

In the above example, custom_variable1 and custom_variable2 are called static parameters.

Interactive Parameters

The values of these parameters will be set up by the service with the variables previously assigned on the IVR using actions like Record digits to variable or Set variable. The variables can also be added to the IVR using Call Interactive with the SetVar verb (for more details, please see the Response Structure section). For example, the following request contains only interactive parameters:

http(s)://<host>.foo.com?custom_variable1=$variable1&custom_variable2=$variable2

Where $variable1 will be replaced by the service with the value of the custom_variable1 variable and $variable2 with the value of the custom_variable2 variable. If one of the variables has not been previously set up in the IVR, then these variables will be null.

Example

STEP 1: Add the Record digits to variable action to the IVR and configure it.

Record 6 digits to the variable subscription.

STEP 2: Add the Call Interactive and set up its parameters.

Call Interactive with the method GET and the URL:

http
http://<host>/check_subscription.php?subscription_code=$subscription

STEP 3: Check that the Record action is executed in the call flow BEFORE the Call Interactive action.

Suppose that a user enters 934924, the request URL sent to the remote application will be the following:

http://<host>/check_subscription.php?subscription_code=934924

Default Request Parameters

By default, some extra request parameters are always added to the request by the service.

NameOccurrenceTypeDescription
CallID1StringUnique identifier of the call.
CallerIDNum1StringThe caller's CallerID number.
CallerIDName1StringThe caller's CallerID name.
CalledDID1StringThe called public number (if available).
CalledExtension1StringThe number of IVR in extended format (e.g. yyyy*zzz).
CallStatus1StringThe call status. This parameter is set to the following values, depending on the event type:

For Dial-In and Dial-Out event types: CALLING

For Hangup event type:
- ANSWER - Call answered, successful call
- BUSY - Busy signal, number is busy
- NOANSWER - Not answered, timed out
- CANCEL - Caller hung up before callee picked up
- CONGESTION - Dialed number not recognized
- CHANUNAVAIL - Channel unavailable, peer may not be registered
CallFlow1StringThe call flow. Always set to IN.
CallerExtension1StringThe number of the extension that called the IVR. Only if the call was inside the server.
CalledNumber1StringThe number that was dialed by the caller (can be an external number: 003258422544, the extended IVR number: 0003*001 or the short IVR number: 001).
CallAPIID1StringThe call ID that is auto-generated and maintained for the entire duration of the call, no matter how many transfers are performed. This variable can be used to identify in the Call Events the calls started using a UnifiedAPI request.
Last updated: Dec 4, 2025