Browser based application

 

The integration in a Browser based application is easy to do.

Outgoing calls

There are several options:

 

•Dial with a Hyperlink  (preferred option)
•Dial within the Browser
•Dial with a Hotkey
•Dial using an XML file (see developer SDK) and Configuration for Remote Applications

 

Incoming calls - database is within the local network

To implement incoming calls, a direct access via ODBC etc. to the database is required. CTI Data Connector Enterprise Edition can do the caller identification.

 

Details how to implement caller identification

Step 1 - define SQL Statements

 

•Define SQL statements (see developer SDK)

 

Step 2 - configure the Browser Pop-up
CTI Data Connector Enterprise Edition can open a URL to display the caller data.

 

•Unzip the files to the installation folder of CTI Data Connector Enterprise Edition
•Edit the file: browser-popup.ini to configure the URL

 

3 different URLs can be configured:

 

UrlAccount = URL if an account / main address was identified

UrlContact = URL if a contact was identified

UrlNOTFOUND = URL in case no caller could be identified - e.g. to create a new record  (in case CTI Data Connector Enterprise Edition does not do the caller identification this URL is always used)

 

[WEBREQUESTER]

UrlACCOUNT="http://AccountID=$ACCOUNTKEY$_and_CustomerId=$CUSTOMERID$"

UrlCONTACT="http://ContactId=$CONTACTKEY$_and_CustomerId=$CUSTOMERID$"

UrlNOTFOUND="http://NotFound/ft=$ForeignTel$&it=$CallerIDInternational$&ot=$OwnerTel$"  

 

The URL can contain variables. The values are retrieved depending on the defined SQL statements (see developer SDK)

 

$ACCOUNTKEY$ = primary key index of the account or unique identifier of the account

$CUSTOMERID$" = customer number

$CONTACTKEY$ = primary key index of the contact person or unique identifier of the contact person

$CallerIDInternational$  = this phone number is in international format and should be used for caller identification

$ForeignTel$ = phone number of the caller in the format the TAPI driver sends it

$OwnerTel$ = phone number which was caller (your own phone number)

 

 

Step 3 - configure the cdc.xml file

Edit the file cdc.xml and change

 

     <Description>Enterprise Application</Description>

     <Executable>popup.exe</Executable>

 

to

 

     <Description>Enterprise Application</Description>

     <Executable>popup-browser.exe</Executable>

 

Step 4 - test your application

Make an incoming call. Click on the desktop notification. The URL should open.

 

Incoming calls - database is hosted or CTI Data Connector Enterprise Edition should only pass the phone number

If the database is hosted, CTI Data Connector Enterprise Edition cannot make the caller identification but can pass the phone number to the browser application.

 

Details how to pass the phone number

Step 1 - change configuration settings

CTI Data Connector Enterprise Edition has to be configured in the way, that the phone number is directly passed to the URL without displaying a desktop notification. Start the Configuration Wizard and change

 

 

•Signaling call with Desktop Notification - uncheck both options (incoming / outgoing)
•Signaling call with call details - uncheck both options (incoming / outgoing)
•Development API - check Always write XML file
•Development API - check Create calls.xml  only once per call
•Delete the default database as you do not need it (button Delete)
•Disable search in Internet phone book - set search option to inactive

 

Step 2 - configure the Browser Pop-up
CTI Data Connector Enterprise Edition can open a URL to display the caller data.

 

•Unzip the files to the installation folder of CTI Data Connector Enterprise Edition
•Edit the file: browser-popup.ini to configure the URL

 

3 different URLs can be configured:

 

UrlAccount = URL if an account / main address was identified

UrlContact = URL if a contact was identified

UrlNOTFOUND = URL in case no caller could be identified - e.g. to create a new record  (in case CTI Data Connector Enterprise Edition does not do the caller identification this URL is always used)

 

[WEBREQUESTER]

UrlACCOUNT="http://AccountID=$ACCOUNTKEY$_and_CustomerId=$CUSTOMERID$"

UrlCONTACT="http://ContactId=$CONTACTKEY$_and_CustomerId=$CUSTOMERID$"

UrlNOTFOUND="http://NotFound/ft=$ForeignTel$&it=$CallerIDInternational$&ot=$OwnerTel$"  

 

The URL can contain variables. The values are retrieved depending on the defined SQL statements (see developer SDK)

 

$ACCOUNTKEY$ = primary key index of the account or unique identifier of the account

$CUSTOMERID$" = customer number

$CONTACTKEY$ = primary key index of the contact person or unique identifier of the contact person

$CallerIDInternational$  = this phone number is in international format and should be used for caller identification

$ForeignTel$ = phone number of the caller in the format the TAPI driver sends it

$OwnerTel$ = phone number which was caller (your own phone number)

 

 

 

Step 3 - configure the cdx.xml file

Edit the file cdc.xml and change

 

  <DEFAULTS>

   <Executable></Executable>

 

to

 

    <DEFAULTS>

   <Executable>browser-popup.exe</Executable>

 

Step 4 - test your application

Make an incoming call. The URL, configured with UrlNOTFOUND in the browser-popup.ini file, should open instantly.