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

Avaya Aura® Application Enablement Services

See All Content

Release 7.1.2


Effective October 14, 2019, Avaya Aura® Application Enablement Services (AE Services) Release 7.x will be End the Sale (EoS). Additional information about the EoS can be found here.

For all new development, Avaya recommends that developers use the latest AE Services release.

Avaya Aura® Application Enablement Services (AE Services) Release 7.1.2 was made generally available in December 2017 as part of Avaya Aura Platform Release 7.1.2. This is NOT the latest AE Services release; the latest release is recommended for new development.

New In This Release

AE Services 7.1.2 includes the following new and enhanced features:

  • AE Services Release 7.1.2 supports Application Specific Licensing (ASL) trusted applications: Officelinx, Avaya Cloud Application Link (ACAL), EP&T Breeze Snap-In, CRA Breeze Snap-In
  • Support for tracking pending agent work modes for Avaya Oceana® solution
  • From AE Services Release 7.1.1, the TSAPI Service supports a new private data version: Version 13.
  • TSAPI Client Windows 10 Support.

Compatibility Information

Compatibility with earlier AE Services releases

All DMCC, Web Services, JTAPI and TSAPI applications created with the AE Services 6.1, 6.2, 6.3 or 7.0 SDKs and client libraries will work seamlessly on AE Services 7.1.x without the need to recompile code and without the need to replace any third-party library components.

Note: AE Services 6.1, 6.2, 6.3 and 7.0 DMCC applications must specify the appropriate protocol version. If a protocol version is not specified, the server will default to 7.1 and the application may receive unexpected XML messages with added elements and/or receive new XML messages.

DMCC Java SDK and Documentation

DMCC XML SDK and Documentation

DMCC .Net SDK and Documentation

Selective Listening Hold/Multiple Registration Service

Important Note: This white paper provides guidance for application developers that use the Selective Listening Hold (SLH) service and/or Multiple Registration (MR) to utilize call media information from one or more parties in a call.

Media Stack Documentation

Important Note: This is a sample implementation of a client media stack designed to demonstrate the RTP processing capabilities of the DMCC SDK. Click here for important information about using the Media Stack in production environments.

Additional Resources

The DMCC APIs rely on the TSAPI service for Call Control, Logical Device, Snapshot and Routing services. The TSAPI Programmers Reference provides information that DMCC developers will find useful, such as details of parameters, error codes and limitations, as well as descriptions of how CTI applications may interact with other Communication Manager features:

JTAPI SDKs, Clients and Documentation

Additional Resources

The JTAPI API uses TSAPI to communicate with the AE Services. Therefore, JTAPI developers will find useful information in the TSAPI Programmers Reference. This includes details of parameters, error codes and limitations as well as descriptions of how CTI applications may interact with other Communication Manager features:

Note: The full Avaya Aura AE Services TSAPI SDK for use with AE Services is not available for download. DevConnect members can order the TSAPI SDK via the Procurement option.

Note: CallVisor LAN (CVLAN) is a legacy AE Services interface. CVLAN Client downloads are available via the portal for the purpose of maintaining existing applications only. CVLAN should not be used for new application development. DevConnect does not provide support nor compliance testing for any CVLAN-based solution and any technical support for an existing 3rd party CVLAN solution must be obtained via a formal customer SR.