Chapter 5 - Administrator’s Tasks
conference is created via Ad
•The WebCommander Server
Conference Access - Chairperson Password Authentication Request using WebCommander as the External Database Application
An additional security measure may be added to the Ad Hoc conference initiation by verifying the chairperson password. In this case, standard participants connect to the conference without entering the conference Entry Password. Only a participant that wants to join the conference as a chairperson is verified with the WebCommander server.
Chairperson access to the conference can be validated independent of the Ad Hoc conferencing. In such a case, each participant that identifies himself/herself as the conference chairperson upon connection to a conference is validated with the WebCommander server.
Initiating a conference using this method:
1.If the conference is started using Ad Hoc conferencing mechanism, follow steps 1 to 7 of the Ad Hoc Conferencing using the WebCommander Server as the External Database Application for Conference Initiation Authentication flow.
2.The On Going conference is assigned an IVR Service that is configured to access an External database application for Chairperson Password authentication and with the appropriate Chairperson Password request messages. In this case, the IVR Service does not include prompts for conference Entry Password. When the participant is moved from the Entry Queue to the conference IVR queue, the participant is prompted for the Chairperson identifier key and if one is entered, the participant is prompted for the Chairperson Password.
—If no Chairperson identifier key is entered, the participant enters the conference as a standard, undefined participant.
