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

Meeting Exchange Avaya Conferencing Provider Interface (ACPI)


ACPI is an end-to-end conference management solution. It supports a complete set of conference management capabilities allowing developers to write applications that create, control and monitor active conferences on Avaya Aura® Conferencing (Release 6.0 only) and Meeting Exchange. ACPI is a Java programming interface that enables client applications to control conferences, callers and queues. ACPI can be used by any application that can make a Java call and supports Java version 5.0 or later to develop conferencing applications like Bridge Talk, Avaya Audio Console, etc.

ACPI comprises two components:

  • The Application Programming Interface (also known as ACP API), and
  • Implementations of the API.

Currently ACP-MODAPI-IMPL is the only implementation available and it can be used to interface with S700/780 Conferencing Servers, and with S6200 and S6800 Media Servers.

About the ACP API

The ACP API enables the development of client applications that:

  • provide moderators with real-time conference management capabilities for the automated and reservationless environment
  • provide participants with an alternative route for accessing the conference management capabilities
  • provide operators with the real-time conference management capabilities

The ACP API is the primary, preferred interface for all Meeting Exchange development.

This ACP API mainly provides Java classes, such as:

  • Connection represents the connection to the conferencing provider.
  • Conference represents a conference call on the conferencing provider.
  • EndPoint represents a media end-point (e.g. a phone) connected to the conferencing provider.
  • OperationFactory creates new operations which can be executed against the various conferencing objects.
  • ConferencingProviders is used to get the Connection (via the Java SPI mechanism).
  • Some other classes: Operator, RecordPlaybackServer, EndPointQueue, ConferenceQueue, Message, MessageSet, etc.

About the ACPI SDK

The ACPI SDK is bundled in the form of a ZIP file that includes the following JAR files and a detailed reference guide (Javadoc):

  • acp-api-versionnumber.jar
  • acp-modapi-impl-versionnumber.jar
  • modapi-versionnumber.jar
  • acpl-versionnumber.jar

plus logging JARs.

Note: versionnumber is the version number for each JAR file.

The above JAR files are required to be on the classpath for ACP API. The Javadoc fully defines the objects and interfaces supported in ACPI.

Release News

Latest Release