You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

Introduction

Group Parameters can be configured, giving the ability to trigger REST functions at certain points in the call flow. Functions can range from seding a GET request when a call transfer is made to an agent, to opening a crm url when a call is accepted by an agent.

Creating and editing parameters

To create a new parameter click on "Add"

To modify an existing parameter click on "Edit"

To duplicate an existing parameter click "Copy"


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:

<UseCase>Description
INBOUND.ACD.DIRECTA direct inbound call
INBOUND.ACD.BLENDEDA direct inbound call which has gone through call blending
OUTBOUND.CLICKTOCALLAn outbound call done via the click to dial function in Agent Home
OUTBOUND.DIALLERAn outbound call made via the dialler
TRANSFER.AGENT

A call transfer to an agent

TRANSFER.GROUPA call transfer to an ACD-Group
TRANSFER.SYNONYMA call transfer to a synonym
TRANSFER.NUMBERA call transfer to a number
TRANSFER.NUMBER_ANNOUNCEMENTA call transfer to a number with a configured announcement


<Event>

The following event types can be configured in the parameter name and will affect when the configured REST function is triggered:

<Event>Description
RINGINGsent when the call is in the ringing state
CONNECTEDsent when the call is connected
CONNRES.1sent when the call was successful and is ended
CONNRES.2sent when the call was not answered
CONNRES.4sent when the caller hungup during the transfer
CONNRES.6sent when the called agent refused the call or hungup during a whisper transfer announcement


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:

ValueDescription
URL=<url>Specifies a URL to be called
METHOD=GET/POSTSpecifies the http method to use
TIMEOUT=<ms>Specifies a timeout in ms before the function is aborted.
HEADER=<http_header>Specifies an http header to be used. May be specified multiple times.
QUERYPARAM=<param=value>Specifies a query parameter which will be added to the URL in URL encoded format
DATA=<value>Specifies POST data which will be sent with the request

Variables

The following variables may be used in the parameter value:

VariableDescription
$date_timethe current date and time
$service_numberthe ServiceNumbers.Name field
$service_namethe ServiceNumbers.Name2 field
$callerthe caller ID
$agent_nameThe surname of the agent
$agent_firstnameThe firstname of the agent
$agent_numberThe number of the agent
$agent_id The ID of the agent
$agent_tel The telephone number of the agent
$agent_uidThe UID of the agent
$agent_nicknameThe NickName of the agent
$group_nameThe name of the ACD group
$group_number The number of the ACD group
$diallercampaign_nameThe name of the dialler campaign
$diallercontact_nameThe surname of the dialler contact
$diallercontact_firstnameThe firstname of the dialler contact
$diallercontact_externalsystemlinkThe external system link for the dialler contact
$diallercontact_userdataThe UserData field for the dialler contact


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.






  • No labels