Polycom 3725-76302-001O Manual De Usuario
Conference Manager Configuration
Polycom, Inc.
191
standalone templates. When you link a template with an MCU profile, the MCU’s profile settings take priority
over values set in the RealPresence DMA system template.
over values set in the RealPresence DMA system template.
When you link a template to a profile, it’s up to you to ensure that the profile exists on the MCUs you want
to use with that template and that its settings are the same on all of them.
to use with that template and that its settings are the same on all of them.
When it uses a profile-based template, the system first tries to find an MCU that has that profile (but it does
so within the MCU pool order rules; see
so within the MCU pool order rules; see
selects the least used MCU in the pool that has that profile.
If none of the MCUs in the pool have that profile, the system selects the least used MCU in the pool and
does one of the following:
does one of the following:
● If the system selected a Cisco Codian MCU, it uses the Codian-specific settings of the specified
template.
● If the system selected a Polycom RealPresence Collaboration Server or RMX MCU, it falls back to
on page 185). If the default template
happens to be linked to a profile that this MCU doesn’t have, the system falls back to its built-in
conference properties settings.
See also:
Template Priority
A user (local or enterprise) has one or more conference rooms. Each room may either use the system’s
default template (specified on the
default template (specified on the
page) or use a specifically assigned template.
(Typically, most conference rooms use the default template.)
Note: MCU Pools vs. Profiles
You can also use a template linked to a RealPresence Collaboration Server or RMX profile to
preferentially route conferences to MCUs that have the profile. But we recommend that you create
MCU pools and pool orders for this purpose instead of using profiles. See
You can also use a template linked to a RealPresence Collaboration Server or RMX profile to
preferentially route conferences to MCUs that have the profile. But we recommend that you create
MCU pools and pool orders for this purpose instead of using profiles. See
and
Note: Templates and API Recording Events
When you link to a RealPresence Collaboration Server or RMX profile that has recording enabled, the
RealPresence DMA system isn’t aware that recording is enabled and rejects attempts to start
recording via the API. To enable recording control via the API, use a standalone conference template
with recording enabled, not a template linked to a RealPresence Collaboration Server or RMX profile.
When you link to a RealPresence Collaboration Server or RMX profile that has recording enabled, the
RealPresence DMA system isn’t aware that recording is enabled and rejects attempts to start
recording via the API. To enable recording control via the API, use a standalone conference template
with recording enabled, not a template linked to a RealPresence Collaboration Server or RMX profile.
Note: Profile-Based Templates and Passcodes
When you link to a RealPresence Collaboration Server or RMX profile that uses an IVR service which
doesn’t prompt for passcodes, callers aren’t prompted even if the conference has a conference or
chairperson passcode.
When you link to a RealPresence Collaboration Server or RMX profile that uses an IVR service which
doesn’t prompt for passcodes, callers aren’t prompted even if the conference has a conference or
chairperson passcode.