Polycom 2000/4000 Manual De Usuario

Appendix D-Ad Hoc Conferencing and External Database Authentication

application it must be configured to access the external database for 

authentication. 

•

An Entry Queue IVR Service configured with the appropriate audio 

prompts requesting the Conference ID and configured to access the 

external database for authentication.

•

Create a Profile with the appropriate conference parameters and the 

appropriate Conference IVR Service assigned to it. 

•

An Ad Hoc-enabled Entry Queue with the appropriate Entry Queue 

IVR Service and Conference Profile assigned to it. 

•

An external database application with a database containing 

Conference IDs associated with participants and their relevant 

properties.

•

Define the flags required to access the external database in System 

Configuration. For more information, see "

The MCU can work with an external database application to validate the 

participant’s right to join an existing conference. The external database 

contains a list of participants, with their assigned parameters. The 

conference password or chairperson password entered by the participant 

is compared against the database. If the system finds a match, the 

participant is granted the permission to access the conference.
To work with an external database application to validate the 

participant’s right to join the conference, the Conference IVR Service must 

be configured to use the external database application for authentication. 
Conference access authentication can be performed as:
•

Part of the Ad Hoc conferencing flow where the participants must be 

authorized before they can enter the conference created in the Ad 

Hoc flow

•

Independent of Ad Hoc conferencing where conference access is 

validated for all conferences running on the MCU regardless of the 

method in which the conference was started. 

Conference access authentication can be implemented for all participants 

joining the conference or for chairpersons only.