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
X

Release 6.3

Release 6.3 was made generally available in May 2013, and superceded by Releases 6.3.1 in October 2013. Releases 6.3.1 is currently the latest release of AE Services and is recommeded for new development.

New In This Release

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

DMCC Service

AE Services Release 6.3 provides the following enhancements for DMCC XML, Java and .NET clients:

  • Endpoint registration events enable clients to monitor H.323 endpoints registration activity, and to retrieve information on H.323 endpoints registered to an extension, on Communication Manager for up to three endpoints at a given extension. These events consume a basic TSAPI license for each extension and require Communication Manager Release 6.3 or later.
  • Warning tone generation: DMCC recording clients can request that AE Services plays a warning tone into calls where the Single Step Conference, Multiple Registration or Service Observing call recording method is being used.
  • The new GetTimeOfDay method provides time information for a specified Communication Manager.
  • Support for the Private Direct Number (DN) feature in Communication Manager 6.3 including the following new feature access codes:
    - AACC No Conference Activation feature access code
    - AACC One Conference Activation feature access code

Compatibility Information

Compatibility with AE Services Release 5.2, 6.1 and 6.2 Applications
All DMCC applications created with the AE Services Release 5.2.x, 6.1.x or 6.2 SDKs and client libraries will work seamlessly on AE Services Release 6.3 without the need to recompile code and without the need to replace any third-party library components.

Note: AE Services 5.2, 6.1 and 6.2 DMCC applications must specify the appropriate protocol version. If a protocol version is not specified, the server will default to 6.3 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.