Avaya Aura Application Enablement Services (AE Services) Release 6.1.2 was made generally available in March 2012. This is NOT the latest AE Services release and is out of support. The latest release is recommended for new development.
Avaya Aura Application Enablement Services (AE Services) Release 6.1.2 was made generally available in March 2012. This is NOT the latest AE Services release and is out of support. The latest release is recommended for new development.
Note: AE Service SDKs, Clients and MIB files have not been reissued with the 6.1.2 release; Release 6.1.1 developer resources should continue to be used with AE Services Release 6.1.2. For details of known issues, workarounds and issues resolved in this service pack, see: Avaya Aura Application Enablement Services Release 6.1.2 Server and Client Service Pack Release Notes, Issue 1.0 - March 2012 (174 KB .pdf)
All DMCC, Web Services, JTAPI and TSAPI applications created with the AE Services Release 4.2.x, 5.2.x or 6.1 SDKs and client libraries will work seamlessly on AE Services Release 6.1.2 without the need to recompile code and without the need to replace any third-party library components. Note: AE Services 4.2 and 5.2 DMCC applications must specify the appropriate protocol version. If a protocol version is not specified, the server will default to 6.1 and the application may receive unexpected XML messages with added elements and/or receive new XML messages.
AE Services Release 6.1.2 is compatible with the following Communication Manger releases:
AE Services Release 6.1.2 is compatible with the following System Platform release:
Note: The Avaya Aura AE Services Release 6.1.1 TSAPI SDK, for use with AE Services 6.1.2, 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.
Originally issued with AE Services Release 6.1.1 or earlier, but still to be used with AE Services Release 6.1.2.