Telephony Application Using Tapi 2.1
Tutorial Pages > Telephony Application Using Tapi 2.1 |
Overview
This document describes the processes needed to interact with a telephony system that uses Tapi 2.1.
The aim is to be able to make calls from a users phone via a click on a form.
We also need to be able to monitor the call length, drop the call and record it's status.
In the case of a system using Tapi 3.0 we can uses the JTAPI solution that is built into Presence.
For Tapi 2.1, we need to call programs written in c++ to make and query calls, Namely Caller.exe and Status.exe.
In this solution we have 2 servers.
One server that runs the main Presence installation and makes socket requests via the socket node to the Tapi Server.
The Tapi Server is in this case an NT machine, that is running a telephony service along with Presence.
Tasks running on the Tapi Server have socket nodes listening for requests that then make calls to the two exes via the Call Native Program Node.
Importing
You can download the tasks for this example from:- http://www.international-presence.com/wikidocs/samples/On_Demand_Windows_Login.xml
Once imported they should look like:-
http://www.international-presence.com/images/docs/userlogin/tasks.png
To embed the task, we just place the Check Login Sub Task before our normal OnDemand task page as you can see below in Simple Task To Confirm Action.
It might be that all OnDemand pages start from one single task, in which case we would place the Check Login Sub Task at the start of that task.
http://www.international-presence.com/images/docs/userlogin/embedded.png
If the username and password are valid, or if the httpsession already exists in the table, then the Check Login Sub Task task will return null, and so the calling task will continue.
We can see here (in the yellow box), the embedded Check Login Sub Task and a switch to continue if the ${response} variable is null.
Description of Tasks
Simple Task To Confirm Action is the example task that shows you how to use Check Login Sub Task in your OnDemand tasks.
This task is our OnDemand task, that contains the Check Login Sub Task. As such it must be added to the OnDemand Queue:-
http://www.international-presence.com/images/docs/userlogin/ondemand.png
Instructions task explains how to configure the tasks.
The instructions task must be run once to create the DEMO.UserLogin table:-
http://www.international-presence.com/images/docs/userlogin/userlogin.png
It is this table that the other tasks use to store and retrieve data about who is logged in.
Session Expiry is a queued task that querys the Demo.UserLogin table effectively expiring sessions unused for 20 minutes.
This task must be added to the Task Queue.
http://www.international-presence.com/images/docs/userlogin/queued.png
Check Login Sub Task calls Login and updates the users details in the Demo.USerLogin table.
Login querys the username and password against the system and either returns a null response or a login panel.
Check User Exists in LDAP performs an LDAP Query against your active directory to Query if the username exists.
In Use
Start the httpserver and go to http://localhost/task/newconfirmtask
The first time you should see the following:-
http://www.international-presence.com/images/docs/userlogin/pleaseenterausername.png
This will require a valid windows username and password combination:-
http://www.international-presence.com/images/docs/userlogin/pleaseenterapassword.png
If the password is incorrect then you will get the following:-
http://www.international-presence.com/images/docs/userlogin/usernamepasswordincorrect.png
The username is looked up via an LDAP Query, so if it does not exist you will see:-
http://www.international-presence.com/images/docs/userlogin/usernamenotfound.png
As the task validates that the http session is logged in, Once the user is logged in they will stay logged in.
This means that once the username and password have been successfully entered, subsequent visits to http://localhost/task/newconfirmtask will pass straight through to the rest of the OnDemand page.