Multi-Language Prompts - Polycom ReadiVoice Release Note

•
CAPI uses XML for all transport. Use of XML allows for better backward-compatibility between different
versions of ReadiVoice.
•
An ACM event set is provided to allow CAPI clients to interface with external applications.
•
Asynchronous and synchronous functionality is available. Asynchronous event notifications for
conference and participants allow for instant notification for any change in participant or conference
state. Notification that requires that some information be generated and returned is sent asynchronously
through a second connection.
At the event level:
•
CAPI allows third-party applications to register (APP_REGISTER_CONFS_ACTIVITY event) or
unregister (APP_UNREGISTER_CONFS_ACTIVITY event) for conference start and stop notifications.
When so registered, third-party applications receive a CONF_STARTED event when a conference has
started and CONF_ENDED event when a conference has ended.
•
CAPI allows third-party applications to retrieve a list of current conferences. In response to a request for
an active conference list, each media server sends a conference list that includes the start time of each
conference. The third-party application must be prepared to accept a conference list for each media server
in the system.
•
The BIG_CONF_INFO event now includes:
– Two subscriber user fields (User Field A, User Field B)
–
Two billing user fields (Billing User Field A, Billing User Field B)
– Two External ID fields (External ID and the new External ID B fields)
Compatibility
Existing MAPI clients are compatible with ReadiVoice v2.55.0 with CAPI. However, CAPI clients are not
compatible with pre-v2.55.0 versions of ReadiVoice. To implement CAPI, you must upgrade to RV v2.55.0.
Implementation
The CAPI Developer's Guide describes how to develop and implement a CAPI client and provides information
useful in migrating an existing MAPI or XML API client to CAPI.

4.2 Multi-language Prompts

Feature Description
In ReadiVoice releases previous to v2.55.x, the conferencing system could use the same audio (.wav) files any
number of times as required to support ReadiVoice call flows. This design supported system efficiency, but
somewhat hindered system flexibility—especially support for multi-language prompts.
In ReadiVoice v2.55.x, almost every unique call for a .wav file calls a unique .wav file. To support this
redesign, ReadiVoice engineering created a new prompt naming scheme and replicated those .wav files that
are used in multiple call flows into multiple .wav files. In addition, a small number of .wav files were
concatenated (joined together) and edited to create new .wav files.
Another issue—multi-digit numbers in different languages have different grammar syntax rules. ReadiVoice
v2.55.0 includes application-level changes necessary to meet these language-specific grammar rules.
ReadiVoice v2.56.0 Release Notes
Polycom, Inc. Page 12
3725-70002-009G2
Confidential and Proprietary