...
Currently, REST calls and REST functionality during the call flow is provided. See ACD Group Parameters - REST Calls.
Creating and editing parameters
...
The "Add" and "Edit" options will bring you to the following page
Syntax
The syntax of the parameter is as follows:
CallTransfer.Client.<UseCase>.<Event>
<UseCase>
The following examplary use cases can be included in the parameter name and will decide at which point in the call-flow an action is triggered:
...
A call transfer to an agent
...
<Event>
The following event types can be configured in the parameter name and will affect when the configured REST function is triggered:
...
| Note |
|---|
Note, the use cases CONNRES.3 (Busy) and CONNRES.5 (SIP Reason) and CONNRES.7 (Error) are not necessary, since a RINGING event must always be received before any REST calls are made. |
Parameter Values
Values
The value of the parameter is specified as a multi-line value instructing the server what to do. The following lines are allowed:
...
Variables
The following variables may be used in the parameter value:
...
Example parameters:
The following parameter will send a GET request when a direct inbound ACD call is ringing:
And this parameter will send a POST request when a direct inbound ACD call is not answered:
The following parameters can be added to an ACD Group which causes the server to send http GET requests (REST calls) to a configured URL when events occur in the call flow to agents.