Polycom 3725-76302-001O manual Conference Templates, Two Types of Templates, Standalone Templates

Conference Manager Configuration

See also:

Conference Settings on page 185

Microsoft Lync 2013 Integration on page 167

Conference Templates

Conference templates are used to create users’ conference rooms, which define a user’s conference experience. A conference template specifies a set of conference properties, such as the line (bit) rate and video display mode.

Note: Cisco Codian Template Settings

The Polycom RealPresence DMA system supports the use of some Cisco Codian MCUs, and conference templates can include Codian-specific settings.

Two Types of Templates

You can create a conference template in two ways:

●Specify the individual conference properties directly in the Polycom RealPresence DMA system, creating a “standalone” (free-standing) template independent of the profiles available on the system’s RealPresence Collaboration Server or RMX MCUs.

●Link the template to a RealPresence Collaboration Server or RMX profile that exists on some or all of the MCUs.

Either kind of template can also include settings specific to Cisco Codian MCUs so that it can be used in deployments containing both kinds of MCUs.

Standalone Templates

Standalone templates defined in the Polycom RealPresence DMA system free you from having to ensure that the exact same RealPresence Collaboration Server or RMX profiles exist on all the MCUs. You specify the desired conference properties directly in the template.

When it uses a standalone template for a conference, the system sends the specific properties to the MCU instead of pointing to one of its profiles.

When using a template not linked to a profile, the system doesn’t use the template’s properties to limit its choice of MCU. It selects the least used MCU in the selected MCU pool (see MCU Pools on page 142 and MCU Pool Orders on page 145). Unsupported properties are ignored or degrade gracefully if necessary. For instance:

●If a conference set to a 4096 kbps line rate is forced to land on an MCU that doesn’t support that value, the line rate falls back to 1920 kbps.

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

Templates Linked to RealPresence Collaboration Server or RMX Profiles

Linking a template to a RealPresence Collaboration Server or RMX profile lets you access profile properties that aren’t currently available in a standalone template, as the MCU may offer more profile properties than

Polycom, Inc. 190