Filter
Top Products
Polycom RMX 2000 Administrator’s Guide
D-7
Conference Access Validation - All Participants (Always)
Once the conference is created either via an Ad Hoc Entry Queue, or a
standard ongoing conference, the right to join the conference is
authenticated with the external database application for all participants
connecting to the conference.
Figure D-3 Conference Access - Conference Password validation with External
Database Application
Joining the conference entails the following steps:
• When the conference is started (either in the Ad Hoc flow or in the
standard method), all participants connecting to the conference are
moved to the Conference IVR queue where they are prompted for the
conference password.
• When the participant enters the conference password or his/her
personal password, it is sent to the external database application for
validation.
• If there is a match, the participant is granted the right to join the
conference. In addition, the external database application sends to the
MCU the following parameters:
— Participant name (display name)
— Whether or not the participant is the conference chairperson
— Participant Information, such as the participant E-mail. These
fields correspond to Info 1, 2, 3 and 4 fields in the Participant
Properties - Information dialog box.
1
0
0
1
1
0
0
1
1
3
0
0
On Going
Conference
with this ID?
Network
Numeric ID: 1000
Name: DefaultEQ
9
2
5
1
0
0
0
9
2
5
1
0
0
0
MCU
IP Endpoint
IP Endpoint
MCU
Gatekeeper - 925
Prefix in
925DefaultEQ
IP Endpoint
New Conference
ID: 1300
Correct
Password?