- Educational Resources
- Development Tools & Configurations
- Compliance Testing
IP Office Release 10.0 was made generally available in August 2016; Service Pack 3 was issued in March 2017; Service Pack 4 (Release 10.0.0.4) was issued in June 2017; Service Pack 5 (Release 10.0.0.5) was issued in September 2017 and updated in November 2017. This is NOT the latest IP Office release; the latest release is recommended for new development.
New APIs and SDKs
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. DevLink3 supersedes the Delta2 record reporting used by the existing DevLink DLL. 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.
- Location API:
The Location 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.
- Web RTC SDK API:
Other new features and enhancements
- Avaya one-X® Portal resiliency: Server Edition Select deployments support a backup Avaya one-X Portal server, providing resiliency for Unified Communication (UC) features.
- SIP endpoint resiliency: IP office now uses the same mechanism as is used for H.323 endpoints to provide resiliency for SIP endpoints.
- Centralized licensing: IP Office now supports fully centralized WebLM licensing for Server Edition and Server Edition Select deployments.
- ADI licensing: ADI licensing is not supported as of IP Office Release 10.0.
- Basic user licenses are no longer provisioned. Basic user licenses are required only in the Cloud environment.
- T.38 Fax on Server Edition: T.38 Fax is now supported with Server Edition and Server Edition Select Linux platforms.
- Server Edition performance enhancements including up to 32 different music on hold (MOH) sources, improved packet capture logging, reduced RAM footprint, etc.
For detailed information about these new features and enhancements, see Chapter 2 of the IP Office Platform Feature Description, Release 10.0.
- 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
TAPI and DevLink
TAPI and DevLink Drivers
Releases 10.0.0.2, 10.0.0.3 and 10.0.0.4
The TAPI, DevLink and TAPI Wave drivers to be used with IP Office 10.0.0.2, 10.0.0.3 and 10.0.0.4 are included on the IP Office User CD 4.2.88. Alternatively, you can download the installers below:
- TAPI 2 Release 18.104.22.168, TAPI 3 Release 22.214.171.124 and DevLink Release 126.96.36.199 driver installers (29.1 MB .zip)
Releases 10.0.0.0 and 10.0.0.1
The TAPI, DevLink and TAPI Wave drivers to be used with IP Office 10.0.0.0 and 10.0.0.1 are included on the IP Office User CD 4.2(64). Alternatively, you can download the installers below:
- TAPI 2 Release 188.8.131.52, TAPI 3 Release 184.108.40.206 and DevLink Release 220.127.116.11 driver installers (23.0 MB .zip)
Members who are registered for PLDS can download User CDs from Avaya Support.
Software Development Kits
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.: