Avaya Aura Application Enablement Services (AE Services) Release 10.1 was made generally available in December 2021. This is the latest release of AE Services and is recommended for new development.
Avaya Aura Application Enablement Services (AE Services) Release 10.1 was made generally available in December 2021. This is the latest release of AE Services and is recommended for new development.
AE Services 10.1 includes the following new and enhanced features:
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.
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.
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.
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:
Note: Effective with Avaya Aura AE Services release 8.1.3.2, the Telephony Web Service SDK is discontinued. Release 8.1.3.2 and above will continue to support applications developed using prior Telephony Web Service SDKs (8.1.3 and older).
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 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.