Filter
Top Products
Conference Manager Configuration
Polycom, Inc. 193
See also:
Conference Templates on page 190
Two Types of Templates on page 190
Template Priority on page 191
Conference Templates Procedures on page 216
About Cascading
One of the conference features you can optionally enable in a template is cascading, which makes it
possible for a conference to span RealPresence Collaboration Server or RMX MCUs. One of two mutually
exclusive forms of cascading can be enabled:
● Cascading for Bandwidth
● Cascading for Size
Cascading for Bandwidth
Cascading a conference across multiple MCUs to conserve bandwidth is especially useful when using WAN
links. Participants can connect to MCUs that are geographically near them, reducing network traffic between
sites to a single link to each MCU.
Cascading does, however, impact the quality of the conference experience.
If you have a Polycom RealPresence Resource Manager or CMA system in your network, you can enable
cascaded-for-bandwidth conferences with the following steps:
1 On the Polycom RealPresence Resource Manager or CMA system, create site topology data
defining the territories, sites, site links, and MPLS clouds in your network, and the subnets in each
site.
2 On the Polycom RealPresence DMA system, integrate with the Polycom RealPresence Resource
Manager or CMA system to obtain its site topology data. See Resource Management System
Integration on page 178.
3 On the Polycom RealPresence DMA system, enable cascading for bandwidth in some or all of your
conference templates.
If you don’t have a Polycom RealPresence Resource Manager or CMA system, you must define your site
topology in the Polycom RealPresence DMA system instead of importing it. See Site Topology on page 278.
Note: Bypass IVR Service Passcode Prompt
Callers to conferences with passcodes (PINs) can bypass the IVR service’s passcode prompting by
appending their passcode to the dial string, following the protocol-appropriate delimiter:
• H.323: <vmr number>#<passcode>
• SIP: <vmr number>**<passcode>
Note: SIP vs. H.323 Cascade Links
The cascade links between MCUs use H.323 signaling for any conferences containing at least one
AVC endpoint.
SIP cascade links are used when:
• There are only SVC endpoints in the conference
• One of the MCUs in the cascade does not support H.323