Extended Object Model Overview

The WTE provides an extension to the Internet Explorer Object Model called the extended object model (ExOM). The Web Telephony ExOM allows the application author to change the configuration parameters of an application dynamically, store and retrieve variables between pages, and access the current TAPI Call object. In addition, the author can use the ExOM to control the operation of the Web telephony session handling the call. The ExOM is accessible from VBScript, Microsoft JScript® or ActiveX controls. Note that any changes made through scripting affect only the current instance of an application.

An application accesses the ExOM by means of the ExOM object. The WTE includes a predefined reference to the ExOM object called External, which applications can use to access the object directly. For example, the following code retrieves the name of the current application:

AppName =  External.Configuration.Name

The ExOM is actually a collection of objects that are exposed to applications through properties on the External (ExOM) object. For a general overview of these objects, see the following topics:

• Web Telephony Configuration Object
• The Session Object
• The TAPI Call Object
• The WTE Event Object
• The TTSMode Object
• The SRMode Object
• The LogCustomField Object

In addition to the preceding objects, the External object exposes the following properties and methods:

• The AlternativePhrases Property
• The hostName Property
• The Log Method

The Objects section contains detailed descriptions of the objects, methods, and properties exposed by the WTE through the ExOM object.

To access the External objects and methods from a scriptlet, use the window.parent.External property. In addition, some External objects such as Session, Configuration, and ITBasicCallControl can be passed into a scriptlet as parameters of public methods. Within the scriptlets, the External object behaves according to the Internet Explorer Object Model (OM) specification.