|
||||||||||
PREV NEXT | FRAMES NO FRAMES |
See:
Description
Packages | |
com.avaya.jtapi.tsapi | This package is the Avaya implementation of JTAPI . |
javax.telephony | The Java Telephony API (JTAPI) is a portable, object-oriented application programming interface for Java-based computer-telephony applications. |
javax.telephony.callcenter | The JTAPI Call Center package extends the core JTAPI package with additional interfaces supporting call routing, automatic call distribution, predictive dialing and application data. |
javax.telephony.callcenter.capabilities | The JTAPI Call Center Capabilities package provides the interfaces for applications to query which features are included in the current JTAPI implementation and are available. |
javax.telephony.callcenter.events | The JTAPI Call Center Events package defines the call center specific event transitions. |
javax.telephony.callcontrol | The JTAPI advanced Call Control package provides more detailed information about the core call model and supplies an extended set of states for the Connection and TerminalConnection objects. |
javax.telephony.callcontrol.capabilities | The JTAPI Call Control Capabilities package provides the interfaces that inform the an application about which features were included in the current JTAPI implementation and which features are currently valid throughout a call transaction. |
javax.telephony.callcontrol.events | The JTAPI Call Control Events package defines the specific Call Control state transition events. |
javax.telephony.capabilities | The JTAPI Core Capabilities package provides an interface to query the current JTAPI implementation to see which features are currently accessible. |
javax.telephony.events | The JTAPI Core Events package defines the core call model state transistions in setting up and monitoring call progress. |
javax.telephony.media | |
javax.telephony.media.capabilities | |
javax.telephony.media.events | |
javax.telephony.mobile | The JTAPI Mobile package extends the core capabilities of a JTAPI implementation with capabilities specific to mobile networks. |
javax.telephony.phone | The JTAPI Phone package provides objects that model the physical characteristics of the terminal, such as, speakerphone,microphone, display, buttons, ringer, handset, and lamp. |
javax.telephony.phone.capabilities | The JTAPI Phone Capabilities package defines the optional features that may be present as part of the JTAPI implementation. |
javax.telephony.phone.events | The JTAPI Phone Events package defines the specific event transitions associtaed with the physical terminal characteristics. |
javax.telephony.privatedata | The JTAPI Private Data package provides an extension mechanism for vendor specific telephony objects. |
javax.telephony.privatedata.capabilities | The JTAPI Private Data Capabilities package provides the extension mechanism for vendor specific private data. |
javax.telephony.privatedata.events | The JTAPI Private Data Events package defines the vendor specific private data event transitions. |
These packages constitute Avaya JTAPI, release 3.1.0.
Avaya has long been a leader in the JTAPI API. From its participation in the initial inception of JTAPI in the 80's, through our participation in the Sun and ECTF standards process and in our leadership in the definition of JTAPI 1.4 (JSR 43), Avaya has been heavily involved in the definition of this Java API.
With this release of JTAPI (Avaya JTAPI 3.1.0) Avaya brings its long-standing JTAPI 1.2 API into conformance with the latest revision of the specification (JTAPI 1.4).
Since there are minor incompatibilities (see the com.avaya.jtapi.tsapi Package description
for details) between the JTAPI 1.2 and JTAPI 1.4 specifications (driven by an incompatible change in Sun JDK 1.4, and a bug in the JTAPI 1.4 specification), application developers should rebuild their applications to work with this release of Avaya's JTAPI implementation.
The packages described in this document are the latest revision of JTAPI (the JTAPI 1.4 specification), and Avaya's implementation of that specification. Since the JTAPI 1.4 specification can be viewed as a superset of the JTAPI 1.2 spec (by design), the vast majority of code written against Avaya's prior JTAPI implementation (Avaya JTAPI 1.3.05) will compile and run against this release of Avaya's JTAPI implementation.
Bringing Avaya's implementation into conformance with the latest JTAPI specification but preserving its JTAPI 1.2 API support, gives Avaya customers the best of both worlds: it allows them to easily adapt to the new standard, and positions Avaya to invest further to introduce, in future releases, the Listener enhancements added with the JTAPI 1.4 specification.
For details about the new features available with this release, such as single Jar packaging, trace file redirection and a features which support the TSAPI Private Data Version 7 features, see the com.avaya.jtapi.tsapi Package description
.
|
||||||||||
PREV NEXT | FRAMES NO FRAMES |