The IP Office interfaces below are supported by DevConnect.

Microsoft Telephony API (TAPI)

IP Office provides Computer Telephony Integration (CTI) capabilities via the Telephony API. TAPI is a Microsoft interface that enables third party solutions deployed on Windows machines to apply first- and third-party control to calls.


The DevLink3 API was introduced in IP Office Release 10.0. DevLink3 supersedes the Delta2 record reporting used by the existing DevLink DLL. DevLink3 provides an enhanced, real-time stream of all call events. The stream can be consumed by client applications and used to track calls throughout their lifecycle.


DevLink provides a real-time event stream that can be consumed by client applications. The event stream incorporates Call records, which include call and party/target information. DevLink is superseded by DevLink3 in IP Office Release 10 and higher, and is not recommended for new development. DevLink remains available in Release 10.0 to give developers time to transition their existing solutions. Avaya cannot guaranteed that future releases of IP Office will continue to support DevLink. Developers are advised to upgrade their integration to DevLink3 as soon as possible.

Centralized CTI Web Services

The IP Office Centralized CTI Web Services API introduced in IP Office Release 10.1 offers an open platform for use in creating applications that employ telephony features and other functionalities provided by IP Office such as Call Log, Directory, Instant Messaging, Presence and Voicemail services. The API has a dependency on Avaya one-X Portal and is supported for use in a distributed IP Office environment.

Location API

The Location API was introduced in IP Office Release 10.0. The API enables developers to build custom emergency services solutions that can update the dynamic location of an extension that does not have a fixed location, such as a WiFi Cordless phone. In addition, the API supports On-site Notification functionality, enabling solutions to receive notification of emergency services calls and to get information about each call, including the caller's location, from the associated Emergency Services Call Alarm.

Emergency Services Call Alarm

IP Office Release 9.0 introduced the Emergency Services Call Alarm. Developers of emergency services solutions are strongly advised to get emergency call information from the alarm, rather than use other methods. The Alarm was updated in Release 10 to include additional device type detail and to support longer names. In addition, Release 10 introduced the Location API, which enables solutions to receive Emergency Call Notification events whenever an emergency call is initiated on IP Office, regardless of whether it is successful or not. Each of these events includes the content of the corresponding Emergency Services Call Alarm. A guide to the format of the alarm is available for download under Releases - Downloads - Emergency Services Call Alarm for the latest release of IP Office.

SIP Endpoints

IP Office's integrated SIP Server supports third party SIP endpoints such as deskphones, softphones and conferencing speakerphones.

SIP Trunks

Used by third party entities that interface with IP Office via a SIP trunk. For more information see the Administering Avaya IP Office Platform with Manager available under Releases - Downloads - SIP Trunks for the latest release of IP Office.

H.323 Endpoints

Used by third-party H.323 deskphones and other endpoints that can register with Communication Manager.

H.323 Trunks

Used by third party entities that interface with IP Office via an H.323 trunk.

Non-IP Trunks and Stations

Used by TDM type solutions, such as PRI trunks and analog stations, that interface with IP Office.

Avaya Client SDK

Avaya Client SDK Release 4.1 introduced initial support, including basic voice and video calling only, for IP Office Platform Release 11.0 / Powered by Avaya Release 3.0 and later. IP Office Release 11.1 supports Avaya Client SDK 4.5 which includes IP Office On Premise Messaging support. Note that Avaya Client SDK does not currently support VP8 video codec.


WebRTC capabilities were introduced in IP Office Release 10.0. The WebRTC SDK includes a JavaScript API that makes it easy for Web developers to build WebRTC clients that can be registered as SIP endpoint devices at IP Office extensions. Users can initiate, receive and control audio and video calls from a Web page displayed in a WebRTC-compliant browser, without having to install a plug-in. The WebRTC SDK supports Chrome and Firefox browsers. Note that Apple requires use of Safari browser for WebRTC support on iOS; the WebRTC SDK does not yet include Safari support - so there is no support for iOS with the WebRTC SDK at this time.

Management API

Introduced in IP Office Release 10.1, the IP Office Management API consists of a set of REST-based services which enables developers to consume IP Office configuration objects and incorporate configuration changes to an expanded set of IP Office entities into applications. Requests and responses utilize XML and JSON formats.

Configuration Service

The Configuration Service enables IP Office configuration changes to be incorporated in client solutions via a Web service interface, expressing configuration changes via an XML document. The API is supported for use with IP Office Essential Edition, Preferred Edition, Advanced Edition and Server Edition only. Using the API, developers can build custom, Web-based front-ends for administering users and local groups.

Service Monitoring Web Services API and SDK

The Service Monitoring Web Services introduced in IP Office Release 10.1 is a REST Web Services interface that provides read-only access to IP Office system status data in XML format. The data can be used by developer solutions for applications such as proactive resource monitoring or monitoring of the general health and inventory of a fleet of IP Office systems.

MTCTI-3 Web Services API

The MTCTI-3 Web Services introduced in IP Office Platform Release 11.1 provide an alternative to 3rd Party TAPI on Avaya IP Office. The protocol enables an application to observe call activity on users and queues, and acquire presence activity. A number of additional features beyond those available through TAPI are also supported by MTCTI-3.

Station Message Details Recording (SMDR)

IP Office provides an interface that enables client solutions to obtain SMDR events. A comma-separated SMDR event record is issued whenever a call is completed. The SMDR interface enables the development of call accounting and call billing applications. The IP Office SMDR can be output directly from the IP Office control unit to a designated IP address and port. SMDR information is included in the Administering Avaya IP Office Platform with Manager manual available under Releases - Downloads - SMDR for the latest release of IP Office.

VoiceMail Pro

VoiceMail Pro provides message handling for individuals or groups, audio information to callers and links to business applications through services such as Text-to-speech. VoiceMail Pro includes a full telephony application environment where call flows can be set up and interact in real time with business workflows.

SSL VPN Onboarding and Onboarding Express APIs and SDKs

The Onboarding APIs and SDKs were introduced in IP Office Release 9.1. They enable Business Partners to use their own Avaya VPN Gateways to perform remote customer support over IP Office SSL VPN technology. The SSL VPN Onboarding APIs facilitate the creation of Onboarding XML files that are installed in IP Office for SSL VPN remote support and monitoring. The SSL VPN Onboarding Express API facilitates offline onboarding of IP Office systems. The SDKs, developer documentation and a KT presentation are available for download under Releases - Downloads - SSL VPN Onboarding APIs for the latest release of IP Office.



Used by third party infrastructure solutions that are IP based in nature, such as SNMP collectors, to interface with IP Office.


IP Office interoperates with third party SIP entities based on the IETF SIP standards.


Used by third party infrastructure VPN solutions, such as VPN appliances, to interoperate with IP Office.


Used by third party Wireless infrastructure solutions that interoperate with IP Office.