Release 3.1

The Avaya Breeze Platform (fka Avaya Engagement Development Platform) Release 3.1 was made generaly available in August 2015; Service Pack 1 (Release 3.1.0.1) was issued in September 2015 and includes an updated version of the SDK. This is NOT the latest release of the Avaya Breeze Platform and is out of support. The latest release is recommended for new development.

IMPORTANT The following end of sale and end of support dates have been announced:
  • End of sale: December 21, 2015
  • End of sale: December 21, 2015
Additional information about the end of sale and end of support dates can be found here. For all new development, Avaya recommends that developers use the latest release of Avaya Breeze platform.

New in Release 3.1

The Avaya Breeze Platform 3.1 supports the following new features:

  • Engagement Call Control solution:
    The release incorporates the new Engagement Call Control snap-in, which provides REST APIs for call control operations such as Make Call, Get Call, Drop Call, Answer Call, Hold Call, Retrieve Call, Redirect Call, Single Step Transfer, Complete Transfer and Complete Conference. See the Engagement Call Control Snap-in pages for more detailed information and programming resources.
  • Flexible Call Leg Control:
    Flexible Call Leg Control facilitates serial calling and serial forking of calls by providing the ability to drop one participant and replace them with a different participant on the same call.
  • Send DTMF:
    Send DTMF enables an application to generate and send DTMF digits.
  • Installation using the Solution Deployment Manager:
    Solution Deployment Manager is a centralized software management solution in System Manager that provides deployments, upgrades, migrations, and updates to the Avaya Breeze Platform.
  • Attribute Scoping:
    Snap-in developers can define whether a snap-in's attributes can be specified at the Global, Global and Cluster, or Global, Cluster and Service Profile level.
  • Avaya Aura Media Server shuffling:
    It is now be possible to add an Avaya Aura Media Server to a call only when needed for a media operation.
  • Avaya Aura Media Server is now licensed separately.
  • Implicit User support for Service Profiles.
  • Persistence database.
  • Call Preserving Failover.
  • Element Manager improvements.

For more detailed information, see the section What's new in this release included in Chapter 2 of the Avaya Engagement Development Platform Overview and Specification.

Release history

End of Support Sept. 2020 (view notice)