Polycom RMX 1800 Administrator’s Guide
D-2 Polycom, Inc.
Figure D-1 Ad Hoc Conference Initiation without Authentication
To enable this workflow, the following components must be defined in the system:
• An Entry Queue IVR Service with the appropriate audio file requesting the Conference
ID
• An Ad Hoc-enabled Entry Queue with an assigned Profile
System Settings for Ad Hoc Conferencing

Ad Hoc Settings

Before a participant can initiate an Ad Hoc conference, the following components must be
defined:
•Profiles
Defines the conference parameters for the conferences that will be initiated from the Ad
Hoc-enabled Entry Queue. For more details, see "Conference Profiles” on page2-1.
•Entry Queue IVR Service with Conference ID Request Enabled
The Entry Queue Service is used to route participants to their destination conferences,
or create a new conference with this ID. For details, see "IVR Services” on page15-1.
In Ad Hoc conferencing, the Conference ID is used to check whether the destination
conference is already running on the MCU and if not, to start a new conference using
this ID.
•Ad Hoc - enabled Entry Queue
Ad Hoc conferencing must be enabled in the Entry Queue and a Profile must be
assigned to the Entry Queue. In addition, an Entry Queue IVR Service supporting
conference ID request. For details, see "Entry Queues” on page7-1..
1
0
0
1
1
0
0
1
3
0
0
On Going
Conference
with this ID?
Maple_Room
Conference ID: 1001
New Conference
ID: 1300
Network
Numeric ID: 1000
Name: DefaultEQ
9251000
9251000
MCU
IP Endpoint
IP Endpoint
MCU
Gatekeeper - 925
Prefix in
925DefaultEQ
IP Endpoint