Procedure 8-Defining Additional Conferencing Components In The Mgc Environment - Polycom ReadiConvene Deployment Manual

Procedure 8—Defining Additional Conferencing
Components in the MGC Environment
There are several scenarios in which a conference can start and Windows
Messenger, Office Communicator and Polycom video endpoints (VSX,
PVX) users can connect to these conferences. The main conferencing
scenarios detailed in this guide are:
• Meeting Rooms
• Dial-out Meeting Rooms/Scheduled conference
• Single-dial Entry Queues
• Ad-hoc Entry Queues
Meeting Room is a conference without resource allocation or starting
date and time that is defined once but can be activated many times. A
Meeting Room remains in a passive state between activations until the
first participant connects to it and activates the conference. A Meeting
Room can contain predefine dial-out participants, which are called by the
MCU when the Meeting Room is activated.
Single-dial Entry Queues are used as a single dial lobby to route
participants to their target conferences. The participant enters the target
conference ID using DTMF codes using the Office Communicator keypad.
Entry Queues can also be defined as ad-hoc, enabling the creation of new
conferences immediately. In standard ad-hoc conferencing, the new
conference is created once the participant enters the conference ID using
DTMF codes and no other conference with this ID is already running.
When connecting to the Entry Queue from Windows Messenger that does
not support DTMF codes, the conference ID must be communicated
differently. This is done by adding the conference ID to the target URI
provided by the participant. This addition to the URI is not recognized by
the LCS, and it is based on LCS provisioned static routes. Static Routes are
also used for ad-hoc conferencing, where the provided URI is not
registered with LCS since the conference does not exist yet, and it is the
the only way for the request to be routed to the Entry Queue/MCUs.
Single-dial Entry Queues or ad-hoc Entry Queues are the recommended
conferencing scenarios with Office Communicator. In these scenarios only
a limited number of accounts have to be defined in the LCS (for each
defined Entry Queue), that can be used for all conference access. Office
Communicator users will have to add only one or two "conferencing
buddies" to their list. With Meeting Rooms, a separate LCS account must
Polycom-Microsoft Deployment Guide
2-27