Please login or register to access secure site features.

Note: By continuing to use DevConnect Program Services you agree to our latest Registered Member Terms.

Sign in using DevConnect ID

Forgot password?

Trouble logging in?

Submit a ticket for Registration Support.

I have an SSO ID

sign in

Don't have a DevConnect or SSO ID ?

Create a DevConnect account or join the program.

register now

Device, Media, and Call Control (DMCC)

See All Content

Release 6.1

Avaya Aura® Application Enablement Services (AE Services) Release 6.1 was made generally available in February 2011. This is NOT the latest AE Services release; the latest release is recommended for new development.

New In This Release

AE Services release 6.1 includes the following new and enhanced features:

DMCC Service and SDKs

Unified DMCC Service: the DMCC API has been enhanced to support advanced third party call control, supplementing existing device, media and call control capabilities. The API has also been updated to support additional capability exchange, monitoring and logical device feature services, and new routing services. The enhancements are supported by all of the existing DMCC SDKs, but in particular enable .Net developers to use AE Services for their CTI-based applications. The DMCC Dashboard, included in the DMCC .Net SDK, has been updated to exercise and demonstrate the new capabilities. For details of enhancements to the DMCC Service, see:

  • .Net DMCC clients support the following operating systems:
    - Windows 7 Professional (32-bit and 64-bit in 32-bit compatibility mode)
    - Windows 7 Enterprise (32-bit and 64-bit in 32-bit compatibility mode)
    - Windows 7 Ultimate (32-bit and 64-bit in 32-bit compatibility mode)
    - Windows Server 2008 R2 (64-bit in 32-bit compatibility mode)
    - Windows XP Professional (32-bit)
    - Windows 2003 Server Standard Edition (32-bit)
  • IPv6 addressing supported: client and switch side interfaces can be configured for IPv4 only, IPv6 only, or both simultaneously.
  • Gatekeeper allocation: DMCC client applications no longer have to specify a gatekeeper for first-party call control devices at the time of the GetDeviceID requests: instead, an in-service gatekeeper is automatically assigned when each device is registered.
  • Avaya Aura Contact Center 6.1 support: DMCC, TSAPI and associated API and client enhancements have been made to support conference and transfer by deskphones and soft clients.

Compatibility Information

Compatibility with AE Services Release 4.2 and 5.2 Applications

All DMCC applications created with the AE Services Release 4.2.x or 5.2.x SDKs and client libraries will work seamlessly on AE Services Release 6.1 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.

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.