Polycom 3725-76302-001LI , Templates Linked to RMX Profiles

DMA OperationsGuide Conference Templates

196 Polycom, Inc.

•If a conference with encryption enabled is forced to land on an MCU that

doesn’t support encryption, that property is ignored.

To preferentially route conferences to certain MCUs, use MCU pool orders.

See “MCU Pools” on page 152 and “MCU Pool Orders” on page 156.

Templates Linked to RMX Profiles

Linking a template to an RMX profile lets you access profile properties that

aren’t currently available in a standalone template.

When you link a template to a profile, it’s up to you to ensure that the profile

exist s on t he MC Us yo u wa nt to use w ith that templa te 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 “MCU

Pools” on page152 and “MCU Pool Orders” on page 156). 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 RMX MCU, it falls back to its default

conference template (see “Conference Settings” on page193). 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.