Disconnecting a Call

After Web telephony or an application answers a call, the call continues until one of the following disconnection events occurs:

• The caller hangs up the phone.
• The caller navigates to an application page that causes the call to disconnect. The page either contains a script that calls the Disconnect method on the ITBasicCallControl object, or the engine reaches the end of the HTML content and there is nothing more for the engine to render.
• The call is transferred either by a script that calls a method on the ITBasicCallControl object, or by the caller pressing the operator key.
• An error occurs that causes Web telephony to disconnect. For example, the application tries to navigate to a file that does not exist.

Processing the Post-Call Page

When the call is disconnected for whatever reason, Web telephony navigates to the post-call page of the application. At this point, the phone line and other telephony resources allocated for the call are freed and made available for new incoming calls. However, the resources that Web telephony allocated for the application, including the Session object, remain available.

The WTE application should use its post-call page to perform any necessary post-call processing on the information gathered from the caller or stored in the Session object. For example, your post-call page can use the LastVisitedPage and LastVisitedTagID properties of the Session object to identify the last HTML page and element that the caller visited before the call was disconnected. You can use this information in a program that processes the post-call page according to the caller's location in the WTE application when the disconnection occurred.

An application should use its post-call page to perform any lengthy processing operations that would otherwise tie up the line or keep the caller waiting.

When no post-call page is specified, a default post-call page is rendered. This page calls the Abandon method and nothing more.

Abandoning the Session

When the post-call-page processing is finished, the application must call the Abandon method. Calling Abandon causes Web telephony to end the session, destroy the Session object, and free all other resources that it allocated for the call. The following example shows how to call the Abandon method:

<script language=vbscript>
external.abandon
</script>