Entry Queue Access - Polycom 1500 Getting Started Manual

RealPresence Collaboration Server (RMX) 1500/1800/2000/4000 Getting Started Guide
Example:
Assigned dial-in number: 4631111
» The participant dials: 4631111
When adding a defined dial-out participant to the conference, and that participant dials in as an
undefined participant before she or he is called by the system, the Collaboration Server is unable to
identify that it is the same participant and will have two separate participant entries in the conference
for the same participant. In such a case, since the dial-in participant is already connected, the
dial-out participant will be displayed as disconnected (line is busy).
For MCUs registered to a gatekeeper, the RMX can be configured to dial and receive calls to and
from H.323 endpoints using the IP address in the event that the Gatekeeper is not functioning. Direct
IP dialing is enabled or disabled by the GK_MANDATORY_FOR_CALLS_OUT and
GK_MANDATORY_FOR_CALLS_IN System Flags. For more information, see the Polycom®
RealPresence Collaboration Server (RMX) 1500/1800/2000/4000 Administrator's
Dialing.

Entry Queue Access

Access via an Entry Queue allows all participants to dial the same entry point that acts as a routing lobby.
Once in the Entry Queue, participants are guided to the conference according to the conference ID they
enter.
Move between the Entry Queue and the destination conference is enabled when both conferencing entities
have the same conferencing parameters (it is recommended that the same Profile is used for both entities).
For example, participants connected to a mixed CP and SVC conference can only be moved to a mixed CP
and SVC conference.
Polycom®, Inc.
Guide, Direct IP
123