Polycom 2000/4000 manual Ad Hoc Settings, Authentication Settings

Polycom RMX 2000/4000 Administrator’s Guide

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 information, see "$paratext>” on page 1-1.

•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.

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. For more information, see "$paratext>” on page 13-27.

•Ad Hoc - enabled Entry Queue

Ad Hoc conferencing must be enabled in the Entry Queue and a Profile must be assigned to the Entry Queue. In addition, an Entry Queue IVR Service supporting conference ID request. For more information, see "$paratext>” on page 4-11.

Authentication Settings

•MCU Configuration

Usage of an external database application for authentication (for starting new conferences or joining ongoing conferences) is configured for the MCU in the System Configuration.

•Entry Queue IVR Service with Conference Initiation Authentication Enabled

Set the Entry Queue IVR Service to send authentication requests to the external database application to verify the participant’s right to start a new conference according to the Conference ID entered by the participant.

D-11