Filter
Top Products
Appendix D-Ad Hoc Conferencing and External Database Authentication
D-8
If there is no match (i.e. the conference or personal password are not
defined in the database), the request to access the conference is
rejected and the participant is disconnected from the MCU.
• If the Conference IVR Service is configured to prompt for the
chairperson identifier and password, the participant is requested to
enter the chairperson identifier.
— If no identifier is entered, the participant connects as a standard,
undefined participant.
• If the chairperson identifier is entered, the participant is requested to
enter the chairperson password. In this flow, the chairperson
password is not validated with the external database application,
only with the MCU.
— If the correct chairperson password is entered, the participant is
connected to the conference as its chairperson.
— If the wrong password is entered, he/she is disconnected from
the conference.
To enable conference access validation for all participants the following
conferencing components are required:
• The external database must hold the conference password or the
participant personal password/PIN code or the participant’s Alias.
• The Conference IVR Service assigned to the conference (defined in
the Profile) must be configured to authenticate the participant’s right
to access the conference with the external database application for all
requests. In addition it must be configured to prompt for the
Conference Password.