Polycom 3725-76302-001O manual Template Priority

Conference Manager Configuration

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.

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 MCU Pools on page 142 and MCU Pool Orders on page 145.

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.

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.

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 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 MCU Pools on page 142 and MCU Pool Orders on page 145). It 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:

●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 its default conference template (see Conference Settings 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:

Conference Settings on page 185

About Conference IVR Services on page 192

About Cascading on page 193

Conference Templates Procedures on page 216

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 Conference Settings page) or use a specifically assigned template. (Typically, most conference rooms use the default template.)

Polycom, Inc. 191