- 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
Avaya Aura® Application Enablement Services (AE Services) Release 6.3.3 was made generally available in June 2014 as part of Avaya Aura Platform 6.2 Feature Pack 4. The release includes a full set of reissued SDKs, Clients and server software, plus a number of updated product and developer guides. This is not the latest AE Services release. The latest release is recommended for new development.
New In This Release
With the introduction of 21-digit dial plan support and other enhanced features in Avaya Aura 6.2 Feature Pack 4, DevConnect members are encouraged to enhance and update their applications for AE Services 6.3.3 and other related Avaya Aura product releases. DevConnect Technology Partners are strongly encouraged to resubmit current solutions for formal Compliance Testing.
AE Services Release 6.3.3 includes the following new and enhanced features:
- CTI events support up to 21 digits
The number of digits in the address of the Calling Party Number and the Connected Number is increased to 21.
- Virtual IP for Geo Redundant High Availability (GRHA)
The GRHA feature extends to VMware offers, with virtual IP address support for System Platform and VMware offers.
- VMWare specific requirement
AE Services vApplication supports VMWare versions 5.0, 5.1 and 5.5.
- New CTI events elements
New optional event elements are included on Call Redirected, Busy/Unavailable and Reorder/Denial events, resulting in additional information on events notified via the TSAPI, JTAPI, DMCC and CVLAN interfaces.
- Security enhancements to support FIPS and JITC.
- TSAPI and CVLAN supported on MS Windows 2012.
For detailed information about what's new in this releases, see Chapter 3 of the Avaya Aura Application Enablement Services Overview and Specification, which is available under the Downloads - Product Overview tab.
Compatibility with AE Services Release 5.2, 6.1 and 6.2 Applications
All DMCC, Web Services, JTAPI and TSAPI applications created with the AE Services Release 5.2.x, 6.1.x or 6.2 SDKs and client libraries will work seamlessly on AE Services Release 6.3.3 without the need to recompile code and without the need to replace any third-party library components.
Note: AE Services 5.2, 6.1 and 6.2 DMCC applications must specify the appropriate protocol version. If a protocol version is not specified, the server will default to 6.3 and the application may receive unexpected XML messages with added elements and/or receive new XML messages.
Compatibility with Communication Manager Releases
AE Services 6.3.3 is compatible with the following Communication Manager Releases:
- Communication Manager 5.2.1
- Communication Manager 6.0.x
- Communication Manager 6.2
- Communication Manager 6.3
- Communication Manager 6.3.2
- Communication Manager 6.3.6
Compatibility with System Platform Releases
AE Services 6.3.3 on System Platform is compatible with the following versions of System Platform:
- System Platform R6.3.4.08007.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
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 Release 6.3.3 TSAPI SDK, for use with AE Services 6.3.3, 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 Support 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)