Browse Prior Art Database

Method for Converting the CallPath Architecture to the JTAPI Architecture

IP.com Disclosure Number: IPCOM000123180D
Original Publication Date: 1998-Jun-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 6 page(s) / 301K

Publishing Venue

IBM

Related People

Fath, M: AUTHOR [+6]

Abstract

Disclosed is a method for converting IBM's CallPath Architecture to the Java Telephony Architecture (JTAPI). Utilizing the CallPath Architecture allows IBM's JTAPI implementation to immediately support connectivity to many different telephony switches.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 21% of the total text.

Method for Converting the CallPath Architecture to the JTAPI Architecture

   Disclosed is a method for converting IBM's CallPath
Architecture to the Java Telephony Architecture (JTAPI).  Utilizing
the CallPath Architecture allows IBM's JTAPI implementation to
immediately support connectivity to many different telephony
switches.

   This document explains how IBM's JTAPI implementation
utilized the CallPath Architecture.  The IBM JTAPI implementation is
a Client/Server design whereby both the Client and the Server took
advantage of the CallPath Enterprise product.  The Server was
implemented as a CallPath Enterprise Daemon (JTAPI Daemon) with the
primary responsibility of converting JTAPI requests to CallPath
Enterprise requests and CallPath Enterprise events/responses to JTAPI
events and class exceptions respectively.  The IBM JTAPI Client is a
Java based toolkit which implements the JTAPI interfaces.  During
this conversion process, continual effort was placed on adhering to
the behavior specified in the JTAPI Architecture document.  Since one
of the most important design points was to make the JTAPI Daemon the
work horse and the JTAPI Client thin with respect to code
implementation, the the scope of this document focuses primarily on
the JTAPI Daemon.

   The components of the JTAPI Daemon consist primarily of
the Toolkit, Request Handler, Event Processor, Fanout and Transport
Protocol used to communicate between the JTAPI Daemon and the JTAPI
Client.

   This document assumes the reader is familiar with the JTAPI
and CallPath Architectures and their associated terminology.

      JTAPI Toolkit

   The JTAPI Toolkit (Toolkit) was designed to model a
telephone call according to the JTAPI Architecture.  The main
internal control blocks consist of Calls, Addresses, ACD Addresses
and Terminals.  Refer to the JTAPI architecture to define these
terms.  The JTAPI Toolkit is mainly manipulated by the Event
component upon receipt of a CallPath Enterprise Event.  For example,
when an unsolicited event is received indicating a new call, an
internal Call control block is created.  This control block contains
regular elements and indexes into tables modeling any ACD Addresses,
Addresses or Terminals, associated with the switch, in the call.
Some Call elements describe its state, the calling address ID, the
called address ID, the last redirected ID, the list of connection
control blocks associated with the call, and the dynamic Ids involved
in the call.  The Call indexes associate the Address Ids, ACD
Address Ids, and Terminal Ids involved in this call with their
respective control blocks.

   The Toolkit models all switch resources configured in
the Server via the JTAPI Configurator.  Switch resources are
subdivided among different users of these resources according to
guidelines established outside the Server by the administrator.  This
division allows users to request telephony action for the specific
resources that are assig...