Filter
Top Products
MGC Web Server Manager User’s Guide
5-37
Conference access authentication can be part of the Ad Hoc conferencing
flow (conference initiation authentication), or independent of Ad Hoc
conferencing. In this case each participant’s connection to a conference is
validated by the external database application (such as the WebCommander
server).
When Ad Hoc conferencing for conference creation is the first stage in the
flow, the Entry Queue is configured to Ad Hoc conferencing with the
conference parameters defined in a Profile assigned to it. The Entry Queue
Service assigned to the Ad Hoc-enabled Entry Queue is usually configured to
access the External Database application for conference creation
authentication.
In the WebCommander - Web Server Manager application, in the Users
Properties table, you must define all users with rights to start a new
conference using Ad Hoc conferencing. For each user defined in the Web
Server database, you enter the PIN Code, conference Numeric ID, Conference
Entry Password and Chairperson Password (when applicable), billing code
and Conference general information (corresponding to the User Defined 1
field in the Profile properties). In addition each user is assigned a PIN code,
and his/her VIP status may be defined.
The user definitions are used for authentication: who can start an On Going
conference from an Ad Hoc-enabled Entry Queue, and in some configurations
who can join the conference as a participant and who as a chairperson.
Ad Hoc Conferencing using WebCommander Server as the External
Database Application for Conference Initiation Authentication
To increase the system security and ensure that only authorized users/callers
can start a new conference, the WebCommander application is used for
authentication.
The procedure to initiate an On Going conference is as follows:
1. The participant dials into an Ad Hoc-enabled Entry Queue.
2. The participant is requested to enter the target conference Numeric ID.
3. The participant inputs the conference Numeric ID using the endpoint
remote control or telephone using DTMF codes. If there is currently an
Conference access authentication can be independent of Ad Hoc conferencing
(conference initiation authentication). In this case, each participant connection to
a conference is validated with the WebCommander server.