Configuration And Implementation Changes - Polycom ReadiVoice Release Note

3.3 Configuration and Implementation Changes

Windows Operator
Windows Operator is now the default operator application. (PTR: 1-6143907) The "activate" configuration
parameter has been set to 1. The parameter is located in odprocrc.defaults configuration template file.
Configuration file change:
[modules]
[opupdater]
activate = 1
[]
[]
Conferencing API—Configurable Timeout Value
CAPI sessions now have a configurable timeout value. (PTR: 1-5953477) The parameter is located in
odprocrc.defaults configuration template file. The default timeout value is 120 seconds. Configuration file
change:
[modules]
[csc]
timeout = 120
[]
[]
Conferencing API—Check Script Change
In ReadiVoice v2.55.0, CAPI introduced a new Application user type. To further support this user type, ECR
1-5998401 in ReadiVoice v2.56.0 implements a change to the output of the ReadiVoice "check" script so that
the script more accurately reflects the Application sessions and Moderator sessions currently active on the
system.
The output of the "check" script identifies the sessions logged into the system, for example:
Operators logged in:
Moderators logged in:
Applications logged in:
Each application that is logged into the system increments the Applications session counter. However, when
an application registers for subscriber events, it also becomes a push_moderator. In this case, the application
increments both the Moderators session counter and Applications session counter.
So, for every subscriber for which an application registers, the Moderators session counter is incremented.
For example, if an application registers for three separate subscriber events, the "check" script shows:
Operators logged in:
Moderators logged in:
Applications logged in:
As the application unregisters for subscriber events, the Moderators session counter adjusts accordingly.
3725-70002-009G2
Confidential and Proprietary
0
0
1
0
3
1
Page 9
ReadiVoice v2.56.0 Release Notes
Polycom, Inc.