Polycom 7000 manual Conference Templates, Two Types of Templates

Conference Manager Configuration

Keep in mind that if you choose to remove all contacts across all SIP domains, the conference contacts associated with other RealPresence DMA system superclusters that were removed by this action will be automatically recreated daily, when the systems sync with Active Directory. You can also manually recreate these contact resources by performing the following steps.

To manually recreate Lync 2013 contact resources associated with other superclusters

1Log in to a system on one of the affected superclusters.

2Go to Admin > Conference Manager > Conference Settings.

3Deselect Publish presence for Polycom conference contacts.

4Click Update.

5Select Publish presence for Polycom conference contacts.

6Click Update.

A caution dialog may appear regarding contact SIP domains for multiple superclusters.

7Click OK.

8Repeat steps 1 through 7 for any other affected superclusters.

See also:

Conference Settings

Microsoft® Lync® 2013 Integration

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.

Polycom, Inc. 188