Guidelines For Using External Ivr Services Via The Mccf-Ivr Package; Configuring The Mcu To Support External Ivr Services Via The Mccf-Ivr; Sip Factories - Polycom RealPresence 1800 Administration Manual

Collaboration server
Hide thumbs Also See for RealPresence 1800:
Table of Contents

Advertisement

<conf-id>**<password>@mcu-sig-ip. The MCU now has control of the call.
The call is transferred to a conference, which can reside on another MCU.
Guidelines for Using External IVR Services via the MCCF-IVR
Package
● Only AVC SIP and TIP protocols are supported.
● MCCF channels support both IPV4 and IPV6.
● When the MCCF channel is disconnected, an alarm is displayed and all external IVR files are deleted.
When the MCCF channel is reconnected, the external IVR files are sent to the MCU.
● When the Collaboration Server (MCU) is restarted, all existing external IVR files are deleted. When
the MCCF channel connects to the Collaboration Server, the external IVR file are sent to the
Collaboration Server.
● H.323 and ISDN-video protocols are not supported.
● Video Switching conferences do not support the TIP protocol
● TIP-based conferencing does not support the following features during conferences:
 Gathering phase
 Skin display
 Text messaging using Message Overlay
 Site Name display
 PCM
 Click&View
● To play audio messages and display the welcome slide during the participant connection to the
conference via the Virtual Entry Queue, the Media files have to meet the following requirements (as
defined in the Entry Queue IVR Service):
 Audio messages: WAV files - PCM, 16 KHz, 16 bit, Mono
 Video slides: JPG files - 1920 x 1088 resolution
Configuring the MCU to Support External IVR Services via the
MCCF-IVR
The support of External IVR Services via the MCCF-IVR package is enabled by default in the Collaboration
Server (RMX) systems, by the flag ENABLE_MCCF which is set to YES.
However, in Ultra Secure Mode and in secured environments where the External IVR Services via the
MCCF-IVR package is not required and unused ports should be closed, this flag should be set to NO.
To change this flag value from YES to NO, you must first add it to the System Configuration.

SIP Factories

A SIP Factory is a conferencing entity that enables SIP endpoints to create Ad Hoc conferences. The system
is shipped with a default SIP Factory, named DefaultFactory.
Polycom, Inc.
Entry Queues, Ad Hoc Conferences and SIP Factories
169

Advertisement

Table of Contents
loading

This manual is also suitable for:

Realpresence 2000Realpresence 4000

Table of Contents