D-1
Appendix D

Ad Hoc Conferencing and

External Database

Authentication

The RMX Ad Hoc conferencing feature enables participants to start
ongoing conferences on-the-fly, without prior definition when dialing an
Ad Hoc-enabled Entry Queue. The created conference parameters are
taken from the Profile assigned to the Ad Hoc-enabled Entry Queue.
Ad Hoc conferencing is available in two modes:
Ad Hoc Conferencing without Authentication
Any participant can dial into an Entry Queue and initiate a new
conference if the conference does not exist. This mode is usually used
for the organization’s internal Ad Hoc conferencing.
Ad Hoc conferencing with external database authentication
In this mode, the participant’s right to start a new conference is
validated against a database.
The external database application can also be used to validate the
participant’s right to join an ongoing conference. Conference access
authentication can be:
Part of the Ad Hoc conferencing flow where the participants must be
authorized before they can enter the conference created in the Ad
Hoc flow.
Independent of Ad Hoc conferencing where conference access is
validated for all conferences running on the MCU regardless of the
method in which the conference was started.