Data store integration

This section provides you with instructions to how to configure Desktop Connect Express to retrieve data from the Call Data Web Service.

In most case application need to send data with the CTI call, as default the UUI field of the

CTI call was used for this purpose, but the problem with the UUI is that it can only carry up to

96 characters Call Data Web Service allows 3rd party applications to send call attached data to Desktop Connect Express.

Desktop Connect Express version 5.3 support the following data store servers:

Legacy GeoCCI Data Store, communication is performed over SOAP messages

Geo DataStore, a high available data store that can be installed on multiple servers and data is synchronized between the instances, communication is performed using JSON protocol.

Settings

To enable Call Data Web Service integration the following parameters need to be specified in the [GeoPDI] secion

Name	Description	Value
GduPlugin	This field controls if the Call Detail Web service interaction is enabled	Y or N
GduUrl	This field specifies the URL of the Call Detail Web service	Valid URL
GduId	The id based on which the name value couples can be identified, this can be a static field e.g. 1234 or CTI data such as UUI or UCID	<UCID> <UUI> other unique values
GduWidth	Controls the width of the call attached data section if omitted the default of 302 pixels is used	e.g. 400
UseDataStore	Controls whether to use the high available GeoDataStore over JSON protocol or the legacy GeoCCI storage	Y or N

The fields retrieved from the Call Detail Web Service can be used just as the fields retrieved from the outbound screen, or the information carried in the inbound CTI call. Where the reference is made based on the name field of the name-value pair.

e.g. Voice Portal script add the following to the Call Detail Web Service

           Balance - 1223

Account – 8231552

           Name - John Smith

The in the rule we are able to reference this values based on their name field. <Balance>,

[Rule1]

'Fieldx is the name of the field that is required

'Valuex is the required value, if empty the field must contain a value

* *

Field1=CAMPAIGN_TYPE

Value1=Collections

Field2=APPLICATION

Value2=LB

* *

InfoMessage=Collections,Account: <Account>, Name: <Name> Balance: <Balance>

* *

Threshold1=240

Threshold2=300

Threshold3=360

ResetAfter=yes

* *

Call data translation

In certain scenarios the data attached to the call needs to be mapped to a value, for example if a message needs to be displayed based on the VP script nodes on which the call is routed.

In such scenarios a mapping can be configured within Desktop Connect Express where the different name and value field can be mapped to a final value. The map has to be specified under the

[GduTranslation] section.

The section contains the name value pair in the following format

[GduTranslation]

trans1:<name1>,<name2>,<name3>=value1,value2,value3=>mapped value

trans2:<name1>,<name2>,<name3>=value1,value2,value4=>mapped value

……

Note that the name field is preceded by a “transX:” which uniquely identifies each translation, the name fields are separated with a comma, and the matching value has to be administered in the same order after the “=” mark, the mapped value is indicated after the “=>” sign.

The mapped value can be referenced in rule field under the <GduTranslation> parameter.