Polycom 1500/1800/2000/4000 manual Call Flow for TIP Endpoints from a Polycom ITP System

Entry Queues, Ad Hoc Conferences and SIP Factories

3The application server may request, through the MCCF channel - IVR package, to play an audio file and display a video slide. When the TIP endpoint uses multiple screens, the video slide is displayed on the main screen only. When the audio file has finished playing, the MCU notifies the application server that the audio file has been played for the call.

4The application server may request, through the MCCF channel - IVR package, to collect DTMF input such as a conference ID or password, from the caller. When the TIP endpoint uses multiple screens, the DTMF input is collected only once from the main screen. The DTMF input is transferred from the MCU to the application server. When the application server receives the DTMF input, it validates the input for the required conference ID or password. Because TIP uses DTLS, it can optionally enable re-keying of DTMF input and the calls to the Entry Queue and the conference can be encrypted.

5When the application server has completed the pre-conference IVR, the application server routes the call to a VMR with the collected password appended to the following dial string:

<conf-id>**<password>@mcu-sig-ip.

The call is disconnected from the application server. The MCU now has control of the call.

6The call is transferred to a conference, which can reside on another MCU.

Call Flow for TIP Endpoints from a Polycom ITP System

The following describes how a TIP call from Cisco TPS endpoints or TIP calls from a Polycom ITP system working as a TIP call is placed into the IVR-controlled Entry Queue and is then connected to a conference:

1A TIP call is routed through the application server to the IVR-controlled Entry Queue.

2The MCU answers the call and waits for the IVR media file requests from the application server. The MCU does not control the call while the call is in the Entry Queue.

3While the call is in the Entry Queue, video is only displayed on the main screen.

4DTMF input is collected only once from the main screen. Because TIP uses DTLS, it can optionally enable re-keying of DTMF input and the calls to the Entry Queue and the conference can be encrypted.

5When the application server has completed the pre-conference IVR, the application server routes the call to a VMR with the collected password appended to the following dial string:

<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 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

Polycom®, Inc. 284