Version 9.0 Detailed Description - General; External Db Modifications; Detailed Description; Validation Of The Participant's Right To Start A New Conference With An External Database Application - Polycom MGC-25 Release Notes

MGC Release Notes - Version 9.0

Version 9.0 Detailed Description - General

External DB Modifications

In version 9.0, additional modes are used for verifying with the external database
application the participant's right to start a new conference and the participant right to join
an ongoing conference. These modes are cotrolled by flags added to the system.cfg.

Detailed Description

Validation of the participant's right to start a new conference with an external
database application
In previous versions, when the MCU was configured to verify the participant's right to start
a new conference based on the conference ID, the system always queried the external
database application without first checking if a conference with that ID is already running.
In Version 9.0, you select whether the MCU sends the validation query to the external
database application without checking if the conference is already running, or only after
checking if the conference is already running. The system behavior is controlled by a
system.cfg flag.
To set the system validation mode for starting a new conference:
By default, the system is configured to maintain the current behavior and validate the
participant's right to start a new on going conference without checking if the conference is
already running (flag is set to NO).
To modify the system behavior and validate the participant's right to start a new on going
conference only after checking if the conference is already running:
•
•
•
Validation of the participant's right to join an On Going Conference with an
external database application
In previous versions, participant's right to join a conference with an external database was
authenticated using a password or PIN code.
In version 9, the authentication can also be done using the participant's CLI (Caller ID). In
such a case, the system does not prompt for conference password and the query to the
external database application is automatically sent using the participant's CLI. The
authentication mode is controlled by a system.cfg flag.
To set the authentication mode for joining an on going conference:
By default, the system is configured to maintain the current behavior and use a Password or
PIN code for authentication with the external database application (flag is set to NO).
To modify the system behavior and enable CLI authentication with the external database
application:
22
In the system.cfg, in the GREET AND GUIDE/IVR section, manually add the flag
AD_HOC_EQ_DIRECT_ONGOING_CONF=YES.
Ad Hoc conferences require the use of an Audio+ board, combined with the Entry
Queue and IVR
Ad Hoc conferences are initiated via an Entry Queue. SIP endpoints can initiate Ad
Hoc conferences using SIP Factories.