Readivoice V2.55.0; Conferencing Api (Capi) - Polycom ReadiVoice Release Note

4 ReadiVoice v2.55.0

ReadiVoice v2.55.0 was a feature release. The following table identifies its new features.
Conferencing API
Multi-language Prompts
Blast Dial with Recorded Subscriber Name
New External ID B filed
HP OpenView MIB Access
Notes:
– ReadiVoice v2.55.0 is only available for ReadiVoice PSTN systems. ReadiVoice IP on InnoVox 4000 media
servers is supported with ReadiVoice v2.53.x.
–
In ReadiVoice v2.55.0, the Windows Operator was a beta release for development and testing purposes only.
For that release, the Java Operator was the only operator interface supported for production systems.
This section describes each new feature in detail. Section 3 describes the enhancements to existing features.
Section 4 describes other enhancements and changes.

4.1 Conferencing API (CAPI)

Feature Description
As a transition, ReadiVoice v2.55.0 (and v2.56.0) supports a new Conferencing API (CAPI) along with the
current Java MAPI, XML API, and Application Control Mode (ACM) programming interfaces. CAPI extends
the functionality of MAPI, XML-API, and ACM interfaces by adding new commands and responses such as
CONF_START and CONF_END. ReadiVoice v2.60.0 will support only CAPI.
Notes: We recommend that you first certify and implement your current MAPI or XML-API clients or ACM applications. Then you
can migrate them to CAPI and roll them out in a subsequent release. The ReadiVoice v2.55.0 CAPI user documentation
includes detailed CAPI migration and implementation documentation, as well as transition examples.
The Conferencing API was developed so that in the future you can access new functionality without having
to support a new API. To extend functionality, CAPI supports a new user type—Application—which is like a
super-moderator that can monitor several conferences at once. The CAPI architecture and how it
encompasses both the Java MAPI and the XML-API are described in detail in the CAPI Developer's Guide. In
these release notes, we describe just the important new functionality that CAPI enables.
At a high-level:
•
CAPI encapsulates the server components from the conferencing application, making it easier to write
and maintain CAPI clients
•
CAPI is XML-based, allowing developers to write clients in a variety of programming languages. Java
utility files and event files are provided, as well.
•
A conference can have multiple subscriber and participant logins.
•
Log4j and Apache Common Logging have been used to provide logging functionality.
3725-70002-009G2
Confidential and Proprietary
Feature/Enhancement
Page 11
ReadiVoice v2.56.0 Release Notes
Polycom, Inc.