- 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 5.2 was made generally available in November 2009. This is NOT the latest AE Services release; the latest release is recommended for new development.
New In This Release
AE Services release 5.2 includes the following new features:
DMCC Service and SDKs
- Set Device Id Format. It is now possible to set the Device Id Format to be used for an established session. Possible values are "DMCC" or "Tel URI". The Device ID Format session characteristic is set by an application in the new Set Session Characteristics message. "DMCC" corresponds to the currently used Communication Manager extension number-based Device Ids. "DMCC" is the default used if the Device Id Format is not explicitly set by the application. "Tel URI" Device Ids are based on the users' E.164 format telephone numbers. The "Tel URI" Device Id Format benefits applications that need to lookup telephone numbers for click-to-call, or need to perform number resolution on incoming calls, from an enterprise directory populated with E.164 format telephone numbers. Because the default behavior is as for previous releases, the DMCC Service interface changes do not break existing applications.
- Set Event Filtering Mode. It is now possible to set the Event Filtering Mode for an established session. Possible values are "None" or "Desktop Call Control". The Event Filtering Mode session characteristic is set by an application in the new Set Session Characteristics message. If set to "None", no events will be filtered out. "None" is the default used if the Event Filtering Mode is not explicitly set by the application. If set to "Desktop Call Control", AE Services filters out call control events that would allow users to detect silent participants on calls, such as DMCC recording devices and service observers. Because the default behavior is as for previous releases, the DMCC Service interface changes do not break existing applications.
- Unicode UTF-8 support. The ability to support Unicode display names on the DMCC interface provides increased support for global application deployment.
- Certificate Management. In previous releases, the AE Services Authentication and Authorization policies defaulted to "No Authentication" and "Enterprise Directory" respectively. An Administrator can now specify the Authentication and Authorization policies to be used for each host, via the AE Services Management Console.
- DMCC Service recovery allows DMCC to persist selected runtime state during normal operation. If the DMCC service is restarted abnormally, it will restore the working state for a client application to continue operating with minimal interruption.
- Support for Communication Manager TCP signalling socket.
Important Note: In addition to the new features of the DMCC Service release 5.2, the software and SDKs include a set of DMCC capabilities that are currently in an alpha status. These alpha status capabilities are not supported and must NOT be used in production environments. For full details and a list of the unsupported capabilities, download and read the statement below:
- Avaya Aura Application Enablement Services Release 5.2 - Unsupported DMCC Service Capabilities (65 KB .pdf)
System Management Service (SMS) Web Service and SDK
- XML Formatted Interface. A new XML formatted interface runs as a separate web service deployed under its own URL alias on the SMS server. The XML formatted interface provides access to the same models, operations and fields as the existing pipe-delimited string formatted interface. The string formatted interface is now deprecated, although existing applications will continue to work without update. Developers should use the new XML interface to develop new applications and are encouraged to update current applications before the next major release of SMS. To support the new XML formatted interface, the SMS SDK has been updated to include the XML WSDL specification, XML schemas referenced in the WSDL, an on-line reference of supported models, operations and fields, and an interactive SOAP client.
- Unicode UTF-8 Support. SMS supports UTF-8 encoding for the Native Names fields in the Station Model, Agent Model, TrunkGroup Model, HuntGroup Model, VDN Model and Vector Model.
JTAPI Service and SDK
- JTAPI SDK: The JTAPI SDK windows installer is no longer available: use ant to build and run sample applications and the JTAPI exerciser. The Programmer's Reference is bundled in the
javadocdirectory of the SDK. The SDK includes an Eclipse
.projectfile to create an Eclipse project for viewing and running sample code.
- Performance enhancements.
- Support for JTAPI 1.4 Listener mechanism. The Observer mechanism is now deprecated.
- Support for log4j logging.
- Client trace management. JTAPI support the creation of multiple trace files, where the number of files and the size of each file is configurable.
- Sample Applications: are now Swing applications rather than applets. An AutoAnswer sample application has been added. The sample applications demonstrate the use of the Listener interfaces rather than Observers.
TSAPI Service, SDKS and Clients
- Client trace management. TSAPI supports the creation of multiple trace files, where the number of files and the size of each file is configurable.
Other New Features
- Application Enablement Services on the Avaya Aura System Platform. The new System Platform offer is in addition to the Bundled and Software-Only offers available with earlier releases. The System Platform offer includes a hardware platform (S8800), AE Services software, and a maintenance contract with Avaya.
- Automatic failover of an AE Services server to a redundant AE Services server (High Availability). This optional feature is available on the System Platform offer only, and requires a high availability license.
- New look-and-feel for the AE Services administrative interface. The AE Services administrative interface, the AE Services Management Console, includes a revised menu for Release 5.2. In previous releases, the administrative interface was called AE Services Operations, Administration, and Maintenance (OAM).
- SNMP Interface and Support for Standard MIBs. AE Services supports the storage of system and performance measurement data in the SNMP manager. This data can be accessed programmatically and used for historical reporting. The Standard MIBs include traps for: Service failure of the ASAI link, transport, and TSAPI services; CTI Link failure; and Invalid Client Connection Attempt.
- Processor Ethernet connection to Communication Manager. AE Services transport is now able to connect to S87xx Communication Manager media servers via the Processor Ethernet connection.
- Increased throughput capacity on Communication Manager to 1000 messages per second on S85xx and S87xx/S8800 media servers running Communication Manager release 5.2.1 or later.
- 30-day grace period for all service licenses.
- Enhancements to the IBM Sametime integration. AE Services supports IBM Sametime 8.x and enterprise, or cluster, configurations.
- Enhancements to Microsoft Live Communications Server and Microsoft Office Communications Server implementations. AE Services supports configurations that use load balancers.
For more detailed information about what's new in the release see the Knowledge Transfer presentations (link under Educational Resources below) and the Release Notes:
- Avaya Aura Application Enablement Services Release 5.2 Server and Client Release Notes - October 2010 (559 KB .pdf)
Compatibility with AE Services Release 4.2 Applications
All DMCC, Web Services, JTAPI and TSAPI applications created with the AE Services Release 4.2.x SDKs and client libraries will work seamlessly on AE Services Release 5.2 without the need to recompile code and without the need to replace any third-party library components.
Note: AE Services 4.2 DMCC applications must specify the 4.2 or earlier protocol version. If a protocol version is not specified, the server will default to 5.2 and the application may receive unexpected XML messages with added elements and/or receive new XML messages.
Compatibility With Communication Manager Releases
AE Services release 5.2 is compatible with the following Communication Manger releases:
- Communication Manager 4.x
- Communication Manager 5.0.x
- Communication Manager 5.1.x
- Avaya Aura Communication Manager 5.2.x
- 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.
Note: The Avaya Aura AE Services 5.2 TSAPI SDK is not available for download. DevConnect members can order the TSAPI SDK via the Procurement option.
Note: DevConnect does NOT provide developer support for CVLAN.
End of Manufacturer Support
7.1.3 (May 2018)
7.1.2 (December 2017)
7.1.1 (August 2017)
7.1 (May 2017)
7.0.1 (May 2016)
7.0 (Aug 2015)
6.3.3 (Jun 2014)
6.3.1 (Oct 2013)
6.3 (May 2013)
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)
Release 5.2 Server and Client Release Notes - October 2010 (559 KB .pdf)