MGC Web Server Manager User’s Guide
3.At this point, the participant that identified himself/herself as the conference chairperson can enter:
—His/her personal PIN Code, as defined in the Users table
—The chairperson password as defined for the conference. If Ad Hoc conferencing was used to initiate the conference, the Chairperson Password is either defined 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 input to the chairperson password request.
5.The WebCommander server searches its database for a User using the PIN code sent from the MCU.
—If a user with this PIN code is found, 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 (corresponding to the User Defined 1 field in the Participant Properties definition) are taken from the Users table and they overwrite these parameters in the Participant Properties in the MGC Manager application or the WebCommander Web site.
—If the participant has entered the correct conference Chairperson Password instead of his/her personal PIN Code, the participant cannot be found in the database but he/she is allowed to enter the conference as chairperson; the participant enters the conference as an undefined chairperson.
—If the participant enters the wrong Chairperson Password or the PIN code does not exist in the database, the participant is either moved to the Participants Queue for Operator’s assistance (MGC Manager application), or disconnected from the conference.
