The DMCC APIs provided by Avaya Aura Application Enablement Services (AE Services) enable applications to access the physical device, media and basic third-party call control capabilities provided by Avaya Communication Manager as an evolution server:
- Device control enables applications to manipulate and monitor the physical aspects of devices, such as buttons, lamps, the display and the ringer. Applications can simulate manual actions on devices and obtain the status of their physical elements.
- Media control allows applications to access voice stream RTP data for the purposes of recording or analysis, and to send RTP data as outgoing voice streams. The AE Services server can record and playback WAV format files when it is managing the media stream for a device.
- Call control makes use of the Telephony Services API (TSAPI) service to provide basic (Release 5.2 and earlier) and advanced (Release 6.1 and later) third-party call control capabilities, such as the ability to place calls, create conferences, transfer calls, reconnect calls, and monitor call control events.
Application Enablement Services provides DMCC access methods for client applications developed using the following programming languages and protocols:
- DMCC Java API
- DMCC .NET API (release 4.1 and above)
- DMCC XML protocol description
Each of the access methods provides access to the same functionality on Communication Manager.