Conference Manager Configuration

Note: MCU IVR service vs. shared number dialing

The RealPresence Collaboration Server or RMX conference IVR service is separate and distinct from the RealPresence DMA system’s SIP-only shared number dialing feature (see Shared Number Dialing).

If you do choose to override the default and specify an IVR service, it’s up to you to make sure that the IVR service you select is appropriate for the users whose conferences will use this template, and that it’s available on the MCUs on which those conference may take place. See your Polycom RealPresence Collaboration Server or RMX documentation for information about conference IVR services. This feature is not supported on Cisco Codian MCUs.

On the Conference IVR tab of the Add Conference Template and Edit Conference Template dialogs, the list contains the names of all the conference IVR services available on the currently connected MCUs. If an IVR service is only available on some of the connected MCUs, its entry shows how many of the MCUs have that IVR service (for instance, 2 of 3).

If a template specifies a conference IVR service, the system will put conferences using that template on the least used MCU that has that conference IVR service. If there are none, it falls back to the default conference IVR service.

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>

See also:

Conference Templates

Two Types of Templates

Template Priority

Conference Templates Procedures

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

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 one of the MCUs in the cascade does not support H.323.

Polycom, Inc.

191

Page 191
Image 191
Polycom 7000 manual About Cascading, Cascading for Bandwidth Cascading for Size