Moderator Api Changes - Polycom ReadiVoice Release Note

5.2 Moderator API Changes

Note: ReadiVoice v2.55.0 and v2.56.0 are transition releases that supported the Conferencing API (CAPI), the Java Moderator
API (MAPI), the XML-API, and Application Control Modules (ACM). ReadiVoice v2.60.0 will support only CAPI.
MAPI EVENT
SET_CONF_SECURITY_NUM.java
ReadiVoice v2.56.0 Release Notes
Polycom, Inc.
In previous versions of ReadiVoice, each dial-out to subscriber
required sending of SET_SECURITY_NUM. There were different
problems with this approach; especially with timing and the fact that
SET_SECURITY_NUM sending was required otherwise the
conference could end up crippled.
To resolve this, a new SET_CONF_SECURITY_NUM event was
introduced. It can be sent at any time a conference is running and
it's not required.
Guidelines for applications regarding SET_SECURITY_NUM and
SET_CONF_SECURITY_NUM:
•
New applications that don't need to set up any conference
security code: No sending of either event is necessary.
•
New applications that need to set up a conference security
code: use SET_CONF_SECURITY_NUM. It can be sent at any
time even when no subscriber is in conference.
•
Legacy applications that don't need to set up any conference
security code: Remove all the code sending
SET_SECURITY_NUM. Neither SET_SECURITY_NUM nor
SET_CONF_SECURITY_NUM need to be sent during dial-outs
or at any other time.
•
Legacy applications that need to set up a conference security
code: Replace SET_SECURITY_NUM with
SET_CONF_SECURITY_NUM. But make sure that
SET_CONF_SECURITY_NUM is sent before the subscriber
joins conference otherwise some participants may join
conference without entering the conference security code.
•
Legacy applications that need to set up a conference security
code and their source code has not been changed: They will
work as before but conferences may run with no conference
security code even when a code is specified in
SET_SECURITY_NUM. SET_SECURITY_NUM processing
usually ignores the sent-in CSC.
A good time to send SET_CONF_SECURITY_NUM is as soon as
the conference starts (or before a dial-out to the subscriber is
initiated). Otherwise there is no guarantee for blast dial-outs to the
subscriber that every single caller entered the conference security
code during his call flow. For non-blast dialouts to the subscriber it is
enough to send SET_CONF_SECURITY_NUM before JOIN_CONF
is sent.
Page 16
Description
Confidential and Proprietary
3725-70002-009G2