Polycom MGC WebCommander Version 9.0 Home Theater Server User Manual


 
Chapter 5 - Administrator’s Tasks
5-40
Conference Access Authentication Request using WebCommander
as the External Database Application
An additional security measure of verifying the conference entry password
can be added to the Ad Hoc conference initiation. Which mean participants
with valid passwords can connect to the conference.
1. If the conference is started using the Ad Hoc conferencing mechanism,
follow steps 1 to 7 of the Ad Hoc Conferencing using WebCommander
Server as the External Database Application for Conference Initiation
Authentication flow.
2. The On Going conference is assigned an IVR Service, which is
configured to access an External database application for conference
Entry Password authentication with the appropriate Entry Password
request messages. When the participant is moved from the Entry Queue
to the conference IVR queue, the participant is prompted for the
conference Entry Password.
3. At this point, the participant can enter:
His/her personal PIN Code, as defined in the Users table
The conference password as defined for the conference either in the
Profile, or by the parameters sent from the external database
application to the MCU at the conference start time
4. The MCU sends the WebCommander server the conference numeric ID
and the participant’s request for the conference entry password.
5. The WebCommander searches its database for a User matching the PIN
code sent from the MCU.
If a user matching the PIN code is found, the WebCommander
checks whether the Conference Numeric ID sent from the MCU is
identical to the Numeric ID defined for the User in the database. If
yes, the participant is connected to the conference as the
chairperson, replacing the participant temporary name with the
name defined for the User in the database. In addition, the
participant VIP state and Participant Information parameters are
taken from the Users table and they overwrite these parameters in
Conference access authentication can be independent of Ad Hoc conferencing
(conference initiation authentication). In this case each participant’s connection
to a conference is validated by the WebCommander server.