Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now

Java Telephony API (JTAPI)

See All Content

Release 5.2

Avaya Aura® Application Enablement Services (AE Services) Release 5.2 was made generally available in November 2009. This is NOT the latest AE Services release; the latest release is recommended for new development.

New In This Release

AE Services release 5.2 includes the following new features:

JTAPI Service and SDK

  • JTAPI SDK: The JTAPI SDK windows installer is no longer available: use ant to build and run sample applications and the JTAPI exerciser. The Programmer's Reference is bundled in the javadoc directory of the SDK. The SDK includes an Eclipse .project file to create an Eclipse project for viewing and running sample code.
  • Performance enhancements.
  • Support for JTAPI 1.4 Listener mechanism. The Observer mechanism is now deprecated.
  • Support for log4j logging.
  • Client trace management. JTAPI support the creation of multiple trace files, where the number of files and the size of each file is configurable.
  • Sample Applications: are now Swing applications rather than applets. An AutoAnswer sample application has been added. The sample applications demonstrate the use of the Listener interfaces rather than Observers.

For more detailed information about what's new in the release see the Knowledge Transfer presentations (link under Educational Resources below) and the Release Notes:

Compatibility Information

Compatibility with AE Services Release 4.2 Applications

All JTAPI applications created with the AE Services Release 4.2.x SDKs and client libraries will work seamlessly on AE Services Release 5.2 without the need to recompile code and without the need to replace any third-party library components.