Avaya Enterprise Cloud


DevConnect supports application development using the Avaya Enterprise Cloud interfaces below.

These are applicable for premises to Avaya Cloud-based integrations and also Cloud-to-Cloud integrations with the Avaya Enterprise Cloud solution.

Note that while Avaya Enterprise Cloud is based upon the Avaya Aura platform, certain additional requirements may have to be met as part of testing for Avaya Enterprise Cloud certification, such as ability to failover to the Geo site and adherence to security standards such as those required for HIPAA and PCI. Latency requirements between elements may need to be identified as part of the testing.

Additional interfaces will be added to Avaya Enterprise Cloud as they become available.

Telephony Services API (TSAPI)

TSAPI enables the development of C and C++ clients that can access the advanced third-party call control capabilities provided by Avaya Aura Communication Manager.

Web Telephony Interface

The Web Telephony Interface (WTI) service enables cloud services and on-premises CTI applications to access CTI capabilities through these REST APIs. These APIs allow easy integration with enterprise applications and aggregation of services to implement compound operations. The initial set of WTI capabilities allows migration of depreciated TWS API applications; subsequent iterations will expand the set of CTI capabilities until the majority of AES APIs are available. Click here to see the capabilities currently available.

Admin Portal Web Service

The Admin Portal Web Services API enables administrative provisioning through user-centric and device-centric methods. User-centric methods relate to communication resources that are associated with users and identified implicitly by the user ID. Device-centric methods relate to devices regardless of association with users. When using device-centric methods, the devices must be explicitly identified.

Download the Admin Portal Web Services Reference Guide.

SIP (Infrastructure)

The Avaya Aura platform interoperates with third-party equipment based on the IETF SIP standards.

SIP Endpoints

Used by third-party SIP endpoints that can register with Session Manager geo setup via Avaya SBCE that are compliant with Enhanced 911 station tracking.

SIP Trunks

Used by third-party entities that communicate with Session Manager via Avaya SBCE SIP trunk.