Avaya Aura Application Enablement Services

Latest Release: 10.1.3 (May 2023)

Release 8.1.2

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

Important The following end of sale and end of support dates have been announced:
  • End of sale: December 13, 2021
  • End of support: March 6, 2023
Additional information about the end of sale and end of support dates can be found here. For all new development, Avaya recommends that developers use the latest release of Avaya Aura Application Enablement Services.

Features in the new release

AE Services 8.1.2 includes the following new and enhanced features:

  • Data Encryption: Enable or disable data encryption for Avaya Aura applications at the time of deployment
  • 12-Party Conference: 8.1.2 supports 12 participants for ad-hoc and meet-me conferences
  • With Release 8.1.2, a new version of TSAPI has been released with new content specific to AE Services release 8.1.2. All other toolkits and interfaces remain unchanged.

Compatibility Information

Compatibility with earlier AE Services releases

Developers are advised to utilize the SDK version that corresponds to the deployed Avaya Aura release to address enhancements, features and changes in Avaya Aura and/or the developer solution. Should any questions or issues arise, use the Technical Support request option to request application development support.

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 application may receive unexpected XML messages with added elements and/or receive new XML messages.

Release history

SPECIAL NOTE:Avaya Aura Application Enablement Services (AE Services) software is no longer downloadable from this page. DevConnect Technology Partners and Testing-enabled Members may purchase the needed Communication Manager and AE Services lab systems to be used for development purposes as a DevConnect Procurement package. Non-members should contact an authorized Avaya reseller or their Avaya Account Executive to obtain the necessary software and licenses.

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.
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.

DMCC Java SDK and Documentation

DMCC XML SDK and Documentation

DMCC .NET SDK and Documentation

Selective Listening Hold/Multiple Registration Service

Media Stack Documentation

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:

TSAPI SDK and Clients

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.

TSAPI Developer Documentation

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 nor new customer deployment. DevConnect does not provide support nor compliance testing for any CVLAN-based solution and any technical support for an existing third-party CVLAN solution must be obtained via a formal customer SR.