Avaya: CEBP Too Complex

Avaya upgraded its Communication Enabled Business Process (CEBP) under the brand Avaya Agile Communication Environment (ACE) release 2.3, in the process essentially admitting that its initial attempt to incorporate Web services into PBX design was too much for many of today's business users. With the new release, Avaya is pushing three themes: tighter integration with Avaya Aura; enhanced integration with systems such as Microsoft Office Communications Server (OCS), IBM Lotus Notes and Sametime

December 15, 2010

3 Min Read
NetworkComputing logo in a gray background | NetworkComputing

Avaya upgraded its Communication Enabled Business Process (CEBP) under the brand Avaya Agile Communication Environment (ACE) release 2.3, in the process essentially admitting that its initial attempt to incorporate Web services into PBX design was too much for many of today's business users. With the new release, Avaya is pushing three themes: tighter integration with Avaya Aura; enhanced integration with systems such as Microsoft Office Communications Server (OCS),  IBM Lotus Notes and Sametime environments; and greater control over communications sessions.
 
For years, telephony providers have sought ways to expose communication services to developers. Proprietary APIs have long existed, and early attempts at standards, such as TAPI from Microsoft, were noticeably voice-centric, requiring business developers to learn too much about the establishment, maintenance and tear-down of communication channels. Even the emergence of SIP was seen as being too low-level for most business developers.

Web services were expected to change all of that by providing a high-level interface to the communications platform. Avaya's initial introduction of CEBP was expected to enable developers to embed communications within business processes without understanding a lot about the underlying communications infrastructure. The technology met with strong reviews from the industry, but the technology failed to meet the needs of the heterogeneous environments of today's enterprise.

"In CEBP 1.0, CEBP was very complex," says Sajeel Hussain, director of Unified Communications for Avaya ACE. "Applications were tightly bound to the PBX domain limiting deployment in multiplatform, multivendor network communication system environments and limiting usage to devices connected to the PBX. The application would need to be re-written for each PBX integration, and significant maintenance work was needed to prevent the application from breaking with each new PBX release upgrade."

Typically, applications could not take control of the call or be introduced into the middle of a call set-up. CEBP 1.0 also required special telecom developer skills to contend with a vendor's proprietary and often platform-unique CTI protocols, thereby putting a barrier in front of the IT developer community.

Avaya says that it has addressed those issues with ACE. All packaged applications and Web Services ride on an Avaya Aura infrastructure, which is inherently designed for multi-PBX and multivendor deployments. What's more, applications are no-longer tied to the PBX domain, so applications can be rapidly introduced to all users across a multi-PBX, multivendor network.The applications can also be developed for users and sessions rather than endpoints and PBX calls, thereby supporting multiple endpoints and multimodal sessions, including presence, telephony, video and IM. Applications can take action on calls before they are delivered to the endpoint, using sequenced applications.

Other enhancements extend ACE's reach to non-Avaya environments. A new client-side add-in for Microsoft Communicator allows employees to click-to-call from online or premises-based Microsoft Communicator clients. This was possible in the past, but only from the more expensive enterprise CALs, not the standard CAL.

As for IBM environments, there's a packaged application to embed voice in the latest release of IBM Lotus Notes and Sametime. Employees can click-to-call and see telephony presence from within Lotus Release 8.5.1 while using desk phones from Avaya or other vendors.

Programmatically, Avaya has added the ability to support sequenced applications. Sequenced applications inject business applications and media services into call flows. Multiple actions can be triggered by specific criteria during the call setup, enabling all sorts of applications.

For example, a sequenced application for lawyers automatically enables recorded calls to be sent to a cloud-based speech-to-text transcription service and the recordings, transcriptions and call detail records for billing to be stored in the appropriate client databases.An e-mail out-of-office announcement could be played to a caller using text-to-speech media services and a list of options provided to the caller, including the ability to reach the next available, skilled person to help. Based on location proximity triggers, a pre-recorded message could be delivered to the recipient, alerting him or her of an impending arrival.

Avaya ACE 2.3 is currently available. The list price starts at $10,000 for the base software. There is a per-user fee ranging from $35 to $115, depending on the application. A per-user list price of $100 is available for the integrated suite of APIs, Web services and JAVA APIs.

SUBSCRIBE TO OUR NEWSLETTER
Stay informed! Sign up to get expert advice and insight delivered direct to your inbox

You May Also Like


More Insights