Avaya Aura Application Enablement Services

Latest Release: 10.1 (December 2021)

Release 7.0.1

Avaya Aura® Application Enablement Services (AE Services) Release 7.0 Feature Pack 1 (Release 7.0.1) was made generally available in May 2016 as part of Avaya Aura Platform Release 7.0.1. 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: October 14, 2019
  • End of support: December 14, 2020
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 AE Services.

Features in the new release

AE Services 7.0.1 includes the following new and enhanced features:

  • Support for SNMP version 3.
  • WebLM is embedded in AE Services, enabling Enterprise Wide Licensing (EWL) to be deployed in allocation mode on a VMWare platform.
  • Support for ESXSi 6.0.
  • Logging enhancements: All AE Service configuration changes are logged via Syslog. The logs can be automatically exported for backup.
  • Support for Common Server Release 3 (CSR3) hardware
  • OAM Web pages are correctly displayed in Internet Explorer 9, 10, and 11.

Compatibility Information

Compatibility with earlier AE Services release

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

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

Release history

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:

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

Note: DevConnect does NOT provide technical support for CVLAN or compliance testing for CVLAN-based solutions.

Loading...