Avaya Aura AE Services Educational Resources

Latest Release: 10.1.3 (May 2023)

Getting Started with AE Services

AE Services provides a platform that support existing contact center application requirements along with new, emerging APIs. The "services" in AE Services refers to programs that perform specific functions and provide API's, protocols and web-based interfaces.

AE Services include the following services:

  • Device, Media and Call Control (DMCC) services enable first-party (device) call control, third-party call control and media control. DMCC provides Java, XML and .Net-based interfaces.
  • Telephony Services API (TSAPI), a C/C++ based API enables a full complement of third-party call control capabilities.
  • Java Telephony API (JTAPI), a client-side interface to the TSAPI service.
  • Web Services, providing convenient access to commonly used Telephony and System Management functionality through a published Web Services Definition Language (WSDL) file and Simple Object Access Protocol (SOAP) connectivity.
  • CallVisor LAN (CVLAN), a C/C++ based API that enables applications to exchange ASAI messages with the AE Server.
  • Definity LAN Gateway (DLG), which supports a set of TCP/IP connections for the communications channel between Avaya Communication Manager and AE Services.

Important Notice about Supported AE Services: DevConnect provides developer support for DMCC, TSAPI, JTAPI, System Management Service (SMS), and Telephony Web Service only when used in conjunction with AE Services Release 3.0 or later. DevConnect does not provide developer support for other interfaces.

API Selector

Use the table below to determine which APIs, protocol descriptions or web services to use to create your client application. Click on the links in the table to find out more about the selected API or web services, and to locate the corresponding SDK and technical resources.

Table 1 AE Services API Selector

Programming Language, Protocol or Web Services
Functionality Java .NET C and C++ Other /XML Web Services
Advanced third-party call control JTAPI 1,DMCC Java API 3 DMCC .NET API 2, 3 TSAPI 1,DMCC XML protocol 3 DMCC XML protocol 3
Basic third-partycall control DMCC Java API DMCC .NET API 2 DMCC XML protocol DMCC XML protocol
Simple callcreation andmaintenance Telephony
Physical devicecontrol DMCC Java API 1 DMCC .NET API 2 DMCC XML protocol 1 DMCC XML protocol
Media control DMCC Java API 1 DMCC .NET API 2 DMCC XML protocol 1 DMCC XML protocol
Communication Managersystem management System Management Service

Table 1 Notes:

  • Compatible AE Services APIs can be used in combination within a single application. For example:
    • DMCC Java API and JTAPI
  • DMCC .NET client applications may be written in C# .NET, Visual Basic .NET or Visual C++ .NET. The DMCC .NET SDK also supports thin client development through the use of activeX controls on a web page.
  • DMCC supports advanced call control capabilities in AE Services Release 6.1 and later.

The Benefits Of Using AE Services

AE Services delivers on key market trends for communication enabling of business processes by allowing the integration of telephony services into business and desktop applications. This improves employee productivity and contributes to a lowering Total Cost of Ownership by allowing for re-use of modular communications services constructs in a Service Oriented Architecture (SOA) model.

The enhanced set of API's, protocols and Web Services offered by AE Services makes the full capabilities of Avaya Communcation Solutions accessible to corporate application developers, Independent Software Vendors (ISVs), Systems Integrators and Avaya BusinessPartners.

AE Services SDKs, Clients and Servers

AE Services is implemented in several components. The AE Services server is the runtime platform that interfaces to Avaya Communication Manager and other Avaya applications. AE Server software is available as a software-only version (requiring the user to supply appropriately configured hardware and operating system software), or as virtual application in the Avaya Aura Virtualized Environment.

Certain interfaces such as the Telephony and System Management Service (SMS) Web Services can be directly invoked against the AE Server.

Other interfaces, such as JTAPI, TSAPI and DMCC Java require the use of a client-side library to invoke AE Server functionality.

Avaya provides a set of Software Development Kits (SDKs) for each of these interfaces for use by application developers. SDK contents vary, depending upon the interface model.


AE Services requires Avaya Communication Manager Release 3.0 or higher. Within the Avaya Aura architecture, Avaya Aura AE Services requires Avaya Aura Communication Manager Release 5.2 or higher.

Certain functions, however, may require specific Communication Manager releases. Please refer to AE Services documentation for each specific interface for more information on any release dependencies.

Understanding AE Services Licensing

AE Services requires a variety of runtime, and in some cases development licenses, depending upon the interface being used.