EPOC   SDK Home Glossary Indexes Previous Next Up

ETel core client-side API


Contents


Overview

ETel’s core API defines a generic interface that supports the limited set of almost universally accepted telephony functionality. The interface is based on three fundamental abstractions, each represented by a class. Everything a telephone is, everything it can do, and all the services it either invokes or which invoke it, are captured by these basic types.

The fundamental abstractions are phones, lines, and calls. All requests to the ETel Server are made via a root ETel Server session, through a phone, line, call or data port. ETel also contains fax functionality, but this is not directly available to applications.

The following Booch diagram illustrates the class hierarchy used to implement the core client-side interface.

ETel class overview

The following sections define the root server session, and each of the fundamental ETel classes.


Root server session

Clients wishing to use the ETel Server must first open a connection to a root server session (see RTelServer class). The root session provides access to general information and functionality about the available telephony resources. The interface provides functions that allow clients to:

To access functionality associated with a specific phone, line, or call, the client must open a sub-session through an object of the associated class.


Phone sub-session

The phone sub-session provides access to functionality associated with a specific phone (see RPhone class). The API provides functions that allow clients to:


Line sub-session

The line sub-session provides access to functionality associated with a specific line (see RLine class). The API provides functions that allow clients to:


Call sub-session

The call sub-session provides access to functionality associated with a specific call (see RCall class). The API provides functions that allow clients to:

EPOC       SDK Home Glossary Indexes Previous Next Up