Ad-Hoc Entry Queue And Conference Creation - Polycom ReadiConvene Deployment Manual

Microsoft—Polycom Meeting Scenarios

Ad-hoc Entry Queue and Conference Creation

3-34
This procedure is similar to the Single Dial Entry Queue procedure, with
the exception that the Meeting Room is not defined in the MGC Manager
in advance and the ongoing conference is created on-the-fly.
In addition, the Entry Queue must be set as Ad-hoc, and the conference
Profile must be assigned to it.
When the user enters the target conference ID, the MCU checks for an
ongoing conference with this ID. If such a conference does not exist, a new
conference is created using the parameters defined in the conference
Profile. The conference ID sent by the user (using DTMF codes) is
assigned to the new conference.
This scenario is supported only with Office Communicator and is the
recommended scenario for Office Communicator users as no Meeting Rooms
have to be defined in advance and stored in the MCU memory. This scenario is
not supported with Windows Messenger as it does not support DTMF codes.
For a detailed description of Ad-hoc conferencing and External database
Authentication, see Chapter 4.