- Educational Resources
- Development Tools & Configurations
- Compliance Testing
IP Office Release 10.1 was made generally available in June 2017. Service Pack 1 (Release 10.1.0.1) was issued in December 2017; Service Pack 2 (Release 10.1.0.2) was issued in April 2018; and Service Pack 3 (Release 10.1.0.3) was issued in July 2018. This is NOT the latest IP Office release; the latest release is recommended for new development.
New APIs and SDKs
- Centralized CTI Web Services API:
The IP Office Centralized CTI Web Services API offers an open platform for use by developers 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 is supported for use in a distributed IP Office environment and is not limited to use on a nodal basis, as is the current TAPI SDK. This new API has a dependency on Avaya one-X Portal, thus users will require access to the one-X Portal application. The existing license for CTI Pro is used to enable the capability on IP Office Release 10.1.
- Management API:
The IP Office Management API enables developers to consume IP Office configuration objects using a REST-based interface. Requests and responses via the interface use XML and JSON format. The API provides read/write access to privileged service users only. The older Configuration Web Services SDK remains available in Release 10.1 to give developers time to transition their existing solutions. Avaya cannot guarantee that future releases of IP Office will continue to support the Configuration Web Services SDK. Developers are advised to upgrade their integration to the new IP Office Management API as soon as possible to take advantage of the additional capabilities it exposes. There is no separate license required to access the Management API.
- Service Monitoring Web Services API and SDK:
The Service Monitoring Web Services API 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 in applications such as proactive resource monitoring or monitoring of the general health and inventory of a fleet of IP Office systems. It is not intended to poll the IP Office system more frequently than needed for the 15 minute trunk utilization statistics, nor does it provide call data. There is no separate license required to access the Service Monitoring API.
Other new features and enhancements
- Integrated Contact Center Reporter: IP Office deployments now include a basic, voice-only reporting solution for use with 5 to 25 active agents and up to 5 active supervisors. ICR Agent and ICR Supervisor licenses are available at no charge in IP Office Release 10.1. (Customers using this feature require a number of Power Users on the system equal to or greater than the number of active ICR users, however those Power User licenses are not restricted to the ICR users.)
- Media Manager: IP Office now includes a native application for archiving, storage, search, playback and download of IP Office call recordings, with administration and maintenance integrated within IP Office Web Manager.
- WebManager Role-based Access: Role-based access with specific permissions is available for IP Office WebManager.
- Multiple Appearance DN: IP Office now supports configuration of multiple appearance DNs on IP Phone lamp keys for use in either a single call or multiple call arrangement.
- VoiceMail Pro 3rd Party Database Access on Server Edition: Lookups in third party PostgreSQL and mySQL databases in order to retrieve data for use in a VoiceMail Pro workflow are supported in an IP Office Server Edition environment .
- Security enhancements include a configurable length for PINs used to access "privileged" services or a device and the removal of the hot-desking capability for SIP phones.
For information about these and other new features and enhancements, see Chapter 2 of the IP Office Platform Feature Description, Release 10.1.
- Release & Product Overview Documentation
- TAPI, DevLink3 and DevLink
- Configuration Service
- SIP Trunks
- SSL VPN Onboarding APIs
- Location API & Emergency Services Call Alarm
- WebRTC SDK API
- Centralized CTI Web Services
- Management API
- Service Monitoring Web Services
TAPI and DevLink
DevLink remains available in Release 10.1 to give developers time to transition their existing solutions. Avaya cannot guarantee that future releases of IP Office will continue to support DevLink. Developers are advised to upgrade their integration to DevLink3 as soon as possible.
TAPI and DevLink Drivers
The TAPI and DevLink installers to be used with IP Office 10.1.0.0 are available for download below. Note that the DevLink driver is 32-bit only, and there are no plans to add support for 64-bit.
- TAPI 2 Release 184.108.40.206, TAPI 3 Release 220.127.116.11 and DevLink Release 18.104.22.168 driver installers (29.1 MB .zip)
Members who are registered for PLDS can also download the IP Office User CD 4.2.88 which includes the drivers from Avaya Support.
Software Development Kits
The Configuration Service remains supported in IP Office Release 10.1, however it does not support new functionalities introduced in Release 10.1 such as Media Manager or Integrated Contact Center Reporter. Avaya cannot guarantee that future releases of IP Office will continue to support the Configuration Service, and therefore recommends that developers begin migrating their applications to the new RESTful-based Management API delivered in 10.1 as soon as possible. The new interface exposes additional capabilities and will be the supported interface for such applications over the coming releases.
The SMDR interface is described in Chapter 24 of the document below:
- SSL VPN Onboarding SDK, Release 9.1 (1.22 MB .zip)
- SSL VPN Onboarding Developer’s Guide, Release 9.1 (1.11 MB .pdf)
- SSL VPN Onboarding Express SDK, Release 9.1 (826 KB .zip)
- SSL VPN Onboarding Express Developer’s Guide, Release 9.1 (681 KB .pdf)
Software Development Kit
Emergency Services Call Alarm
The white paper below offers guidelines on best practices in supporting Emergency Services requirements and how specific IP Office features can be used to satisfy those requirements.: