- Telephony Web Service
- SMS Web Service
- Getting Started with AE Services
- Training Course: Developing with AE Services
Sample Applications & Tutorials
- Application Event Monitoring using the DMCC Java SDK
- Application Initialization using the DMCC Java SDK
- C# Telecommuter
- Call Control using the DMCC Java SDK
- Call Detection using the DMCC Java SDK
- Record, Playback, Transfer & Conference (RPTC)
- Setting up a Development Environment for the DMCC Java SDK
- Setting up a Development Environment for the DMCC XML SDK
- Telephony Web Service
- SMS Web Service
- DMCC APIs
- Development Tools & Configurations
- Compliance Testing
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.0 was made generally available in August 2015 as part of Avaya Aura Platform Release 7.0. The release includes a full set of reissued SDKs, Clients and server software. Most of the documentation has also been updated and reissued, although a number of the Programmers' Guides originally issued with Release 6.3.3 should continue to be used with this release. This is not the latest AE Services release - the latest release is recommended for new development.
New In This Release
AE Services 7.0 includes the following new and enhanced features:
- Default certificate change: The AE Services server comes pre-installed with a set of default server certificates for lab use only. In AE Services 7.0, the Certificate Authority (CA) used to sign the server default certificates has changed. To allow client applications to connect to the AE Services 7.0 server using a TLS socket connection in the lab, the new AE Services CA certificate must be exported from the server, and imported into your client trust store. See Release 7.0 - Default Certificate Change for more information about this change and recommendations for replacing the default certificates in production environments.
- RTP media and RTCP encryption updates: see Release 7.0 - RTP Media and RTCP Encryption Changes for detailed information and recommended actions.
- Support for up to 8000 DMCC instances.
- Support for Java 8 by the DMCC SDK.
- AE Services Virtualized Appliance support: AE Services 7.0 is not available as part of System Platform or Bundled offers. The AE Services 6.3.3 or earlier servers based on the System Platform or Bundled offers can only be migrated to AE Services 7.0 by reconfiguring the servers for the Avaya Virtualized Appliance model based on Appliance Virtualization Platform.
- ANAV entitled to Application Specific Licensing (ASL): ANAV now qualifies as an Avaya application and is entitled to the benefits of ASL. ANAV can acquire DMCC and TSAPI licenses from AE Services as required without charge, and agent event information without polling.
- Support for use of up to 8 domain controllers per station.
- Support for Geographic Redundancy High Availability (GRHA) on servers deployed in the Virtualized Environment; Fast Reboot High Availability (FRHA) is no longer supported.
- Support for Internet Explorer 11.
- RHEL updated to release 6.5.
- Support for the 9601 SIP-only deskphone.
- Detection of unreachable SIP endpoints and logging out of unreachable SIP agents.
- Out of Band Management provides the ability to move the AE Services Management Console Web-based management and configuration traffic of the server to a dedicated subnetwork.
Compatibility with earlier AE Services releases
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 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.
Compatibility with Communication Manager releases
AE Services 7.0 is compatible with the following Communication Manager Releases:
- Communication Manager 6.0.x
- Communication Manager 6.2
- Communication Manager 6.3
- Communication Manager 6.3.x
- Communication Manager 7.0
- Release Information
- Product Overview
- Product Documentation
- Server Downloads
- MIB Files
- DMCC APIs
- Web Services
- CVLAN API
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.
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
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, 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.
End of Sale Notified
6.2 (Jul 2012)
6.1.2 (Mar 2012)
6.1.1 (Jun 2011)
6.1 (Feb 2011)
5.2.4 (Oct 2012)
5.2.3 (Mar 2011)
5.2.2 (Jun 2010)
5.2.1 (Jan 2010)
5.2 (Nov 2009)
4.2.4 (Aug 2010)
4.2.3 (Sep 2009)
4.2.2 (Jun 2009)
4.2.1 (Aug 2008)