Polycom 1500/1800/2000/4000 manual Ad Hoc Settings

Appendix D - Ad Hoc Conferencing and External Database Authentication

●If the Conference IVR Service is configured to prompt for the Conference password, the participant is requested to enter the conference password. In this flow, the conference password is not validated with the external database application, only with the MCU.

If the wrong password is entered, he/she is disconnected from the conference.

●If the correct conference password is entered, the participant is prompted to enter the chairperson identifier key.

If no identifier is entered, the participant is connected to the conference as a standard participant.

●If the chairperson identifier is entered, the participant is prompted to enter the chairperson password.

●When the participant enters the chairperson password or his/her personal password, it is sent to the external database application for validation.

If the password is incorrect the participant is disconnected from the MCU.

●If there is a match, the participant is granted the right to join the conference as chairperson. In addition, the external database application sends to the MCU the following parameters:

Participant name (display name)

Participant Information, such as the participant E-mail. These fields correspond to Info 1, 2, 3 and 4 fields in the Participant Properties - Information dialog box.

To enable conference access validation for all participants, the following conferencing components are required:

●The external database must hold the Chairperson Password or the participant’s Alias.

●The Conference IVR Service assigned to the conference (defined in the Profile) must be configured to check the external database for the Chairperson password only when the participant enters the chairperson identifier key (either pound or star). In addition, it must be configured to prompt for the chairperson identifier key and password.

System Settings for Ad Hoc Conferencing and External Database Authentication

Ad Hoc Settings

Before a participant can initiate an Ad Hoc conference (with or without authentication), the following components must be defined:

●Profiles

Defines the conference parameters for the conferences that will be initiated from the Ad Hoc-enabled Entry Queue. For more details, see Defining AVC-Based Conference Profiles and Defining SVC and Mixed CP and SVC Conference Profiles.

●Entry Queue IVR Service with Conference ID Request Enabled

The Entry Queue Service is used to route participants to their destination conferences, or create a new conference with this ID. For details, see IVR Services.

In Ad Hoc conferencing, the Conference ID is used to check whether the destination conference is already running on the MCU and if not, to start a new conference using this ID.

Polycom®, Inc. 957