Filter
Top Products
Chapter 4-Entry Queues, Ad Hoc Conferences and SIP Factories
4-10
Ad Hoc Conferencing
The Entry Queue can also be used for Ad Hoc conferencing. If the Ad Hoc
option is enabled for the Entry Queue, when the participant enters the
target conference ID the system checks whether a conference with that ID
is already running on the MCU. If not, the system automatically creates a
new ongoing conference with that ID. The conference parameters are
based on the Profile linked to the Entry Queue. As opposed to Meeting
Rooms, that are predefined conferences saved on the MCU, Ad Hoc
conferences are not stored on the MCU. Once an Ad Hoc conference is
started it becomes an ongoing conference, and it is monitored and
controlled as any standard ongoing conference.
An external database application can be used for authentication with Ad
Hoc conferences. The authentication can be done at the Entry Queue level
and at the conference level. At the Entry Queue level, the MCU queries
the external database server whether the participant has the right to create
a new conference. At the conference level the MCU verifies whether the
participant can join the conference and if the participant is the conference
chairperson. The external database can populate certain conference
parameters.
For more information about Ad Hoc conferencing, see Appendix D: "Ad
Hoc Conferencing and External Database Authentication” on page D-1.