User manual POLYCOM MGC-50 - RELEASE NOTE

MGC-25/50/100 MGC+50/100 Release Notes Version 7.5 February 2006 DOC2134A Copyright © 2006 Polycom, Inc. All Rights Reserved All text and figures included in this publication are the exclusive property of Polycom, Inc., and may not be copied, reproduced or used in any way without the express written permission of Polycom, Inc. Information in this document is subject to change without notice. This document also contains registered trademarks and service marks that are owned by their respective companies or organizations. If you have any comments or suggestions regarding this document, please send them via e-mail to info@polycom.com. Catalog No. DOC2134A Version 7.5 Notice While reasonable effort was made to ensure that the information in this document was complete and accurate at the time of printing, Polycom, Inc. cannot assure the accuracy of such information. Changes and/or corrections to the information contained in this document may be incorporated into future issues. Table of Contents Version 7.5 - New Features List............................................................ 1 Version 7.5 Upgrade Package Contents.............................................. 5 Prior to Installation and SW Upgrade .................................................. 6 Hardware Update Notice ................................................................................................6 Control Unit Update Notice ...................................................................................7 Version 7.5 Interoperability Table .................................................................................8 Software Upgrade Procedure ............................................................. 10 Upgrade Checklist ........................................................................................................10 MCU Disk Space Verification .....................................................................................10 Dongle Upgrade ...........................................................................................................11 Dongle Information ..............................................................................................11 Dongle Upgrade Instructions .........................................................................12 MGC-50/MGC-100 .......................................................................................12 MGC-25 .........................................................................................................13 Downloading the Dongle File ..............................................................................14 Installing the Dongle File .....................................................................................15 MGC Unit Software Upgrade Procedure .....................................................................16 Upgrading from a Version using Password for Entry Queue Routing .................16 Upgrading from a Version using Numeric ID for Entry Queue Routing .............17 Removal of Redundant Configuration Files ................................................................17 Downloading the Software to the MCU ......................................................................17 Installing the MGC Manager Software ........................................................................19 Manual Installation of the Default Message Services ..................................................19 Updating the Entry Queue Services .............................................................................20 Detailed Description - Video ............................................................... 21 Video Support for Start Conference requires Chairperson ..........................................21 Detailed Description .............................................................................................21 Detailed Description - General ........................................................... 23 Network Time Protocol (NTP) for XPEK Systems .....................................................23 Detailed Description .............................................................................................23 Secure Socket Layer (SSL) ..........................................................................................25 Detailed Description .............................................................................................25 H.239/People+Content Star Cascading ........................................................................30 Detailed Description .............................................................................................30 Ad Hoc Auto Cascade ..................................................................................................31 Detailed Description .............................................................................................31 Monitoring Auto Cascaded Conference Links ..............................................33 Limitations ............................................................................................................33 Faulty Participant in Red .............................................................................................34 Detailed Description .............................................................................................34 i MGC Release Notes - Version 7.5 HTTP File Transfer Mode ........................................................................................... 35 Detailed Description ............................................................................................ 35 Same Layout Option in Video Switching Conferences ............................................... 36 Direct IP Dial-in .......................................................................................................... 37 Detailed Description ............................................................................................ 37 Direct End Point Dialing ...................................................................................... 37 IP to ISDN Gateway Call (without Gatekeeper) .................................................. 37 SIP Factory .................................................................................................................. 38 Detailed Description ............................................................................................ 38 Nortel Environment Flag Settings ............................................................................... 40 MGC+ Predefined IP only Entry Queues and Meeting Rooms .................................. 41 Corrections, Pending Issues and Limitations................................... 43 Corrections between Versions V.7.0.2 and V.7.5 ....................................................... 43 Corrections between Versions V.7.0.1 and V.7.0.2 .................................................... 44 Corrections between Versions V.7.0 and V.7.0.1 ....................................................... 47 Version 7.5 Pending Issues .......................................................................................... 49 Version 7.5 System Limitations .................................................................................. 54 Appendix A - Falcon Diagnostic Tool ................................................ 65 Detailed Description ............................................................................................ 65 Test Description ........................................................................................................... 66 Starting the Falcon Diagnostic Tool ............................................................................ 70 Falcon Main Window .......................................................................................... 70 Setting the Log Files Path .................................................................................... 73 Connecting to an MCU ........................................................................................ 74 Running Diagnostic Tests ............................................................................................ 75 Test Results ................................................................................................................. 79 Disconnecting from the Falcon Diagnostic Tool ......................................................... 80 Appendix - Adding an MCU to the Network .............................................................. 81 Test Glossary ............................................................................................................... 82 Log File Report Examples ........................................................................................... 83 ii Version 7.5 - New Features List Version 7.5 - New Features List The following table lists the new features in Version 7.5. Table 1: New Features List Category Feature Name H.264 SD/HD in Video Switching conferences Description H.264 Standard Definition (SD), High Definition (HD) and VSX 8000 (version 8.0) HRR resolutions are supported in Video Switching conferences. Set the system.cfg flag: ENABLE_HD_SD_IN_FIXED_MODE= YES (default =NO). When YES, the Highest Common mode is enabled. Higher Frame rates in H.264 CP conferences. The MCU now supports frame rates up to 30 FPS in CP conferences. In H.264 VideoSwitching Conferences, the maximum Line Rate capability is 1920 Kbps. Supported in MGC version 7.03. H.264 Fixed mode can be used with cascaded conferences by setting the H.264_VSW_AUTO flag to YES. These flag settings forces all endpoints to use predefined conference resolution and frame rates. This feature is now available for video conferences. When the conference is set to Wait for Chairperson and participants connect to the conference before the chairperson, the conference is placed on hold. When an H.323 dial-out call fails to connect because the endpoint could not be reached (for example, the endpoint is busy), the system can be set to automatically redial the endpoint. Set the system.cfg flag: ENABLE_H323_REDIAL=YES. The MCU supports two new IP Dial-in methods: · Direct Endpoint Dialing (Without Gatekeeper) 1. Video 2. Video Increased Frame Rate in H.264 CP conferences 3. Video H.264 up to 2 Mbps in VideoSwitching Conferences 4. Video H.264 Fixed Mode 5. Video Video Support for Start Conference requires Chairperson 6. IP H.323 dial-out automatic redial 7. IP Direct IP Dial-in · IP to ISDN Gateway Call (without Gatekeeper) 1 MGC Release Notes - Version 7.5 Table 1: New Features List (Continued) Category Feature Name SIP REINVITE Description SIP protocol allows ways of changing one or more parameters in an existing session. It is performed by sending a REINVITE request with the desirable mode to the other SIP entities in the conference. Version 7.5 supports the SIP REINVITE request sent by the remote SIP endpoint to the MGC in the following instances: · Party Media - change in the participant's IP address. 8. IP · Conference Media - change in the participant status that is informed to the conference, such as mute and hold. Change Mode - changes that affect the conference media and may affect other participants as a result, such as change in the video protocol. Later Video - Upgrade the SIP connection from audio only to video. · · 9. IP SIP OPTIONS Support for SIP RFC-3261 (OPTIONS) that allows a UA (User Agent) to query another UA or a proxy server for its SIP and media capabilities. Support for SIP RFC-3265 (REFER) that instructs the recipient of the REFER request to contact a third party using the contact information included with the REFER request. This allows any SIP UA to send the URI of another UA to the conference and instructs the conference to create a new dial-out participant and dial to it. Allows SIP endpoints to create ad hoc conference and automatically connect to the conference. This version supports multipoint SIP conferencing in a Microsoft environment: · Microsoft LCS 2005, SP1, 10. IP SIP REFER 11. IP SIP Factory 12. IP Microsoft LCS support · · · Office Communicator version 1.0, Windows Messenger version 5.1, Installed desktop and group video conferencing systems PVX versions 8.0 & 8.0.1; VSX 8.0 & 8.0.3. · MGC Manager 7.5 Note: This product requires purchase of a license. 2 Version 7.5 - New Features List Table 1: New Features List (Continued) Category Feature Name Microsoft LCS support (con't) Description With MGC 7.5 (MS integrator phase 3) Polycom now supports the full set of OC Conferencing capabilities based on the MS SIP-CX protocol. For a detailed description of the Microsoft solution see the Microsoft Deployment Guide. The maximum bridge capacity in IP Video Switching conferences is increased. The system automatically detects the Nortel environment and changes the working mode accordingly (no need to set the Nortel flag in the system.cfg). However, if you do not see video with the Nortel endpoints, you may need to modify three flags in the system.cfg file. Note: This product requires purchase of a license. T.140 Closed Captioning is supported with H.323 FECC. The Network Time Protocol (NTP) allows the MCU to synchronize the internal MCU control unit's clock with an external NTP server to assure accurate time and synchronized controls. SSL (Secure Socket Layer) enables secure HTTP connection on MCU's with XPEK Operating Systems. Available on the MGC Manager, WebCommander and API calls. H.239/People+Content Star Cascading is available with H.320 (ISDN and MPI) & H.323 Video Switching conferences. Ad Hoc conferences can be automatically cascaded. When an identical Numeric ID is used for each conference, the WebCommander automatically cascades the conferences. A "Faulty" participant connected to a conference has their background color marked red for improved visibility. Transfer of files using HTTP mode can be used in addition to FTP mode of operation. Video Switching conferences support the Same Layout mode. 13. 14. IP IP Bridge Higher Capacity Nortel 15. IP 16. 17. IP General H.323 FECC Network Time Protocol (NTP) for XPEK Systems 18. General Secure Socket Layer (SSL) 19. General H.239/People+Content Star Cascading Ad Hoc Auto Cascade 20. General 21. General Faulty Participant Marked in Red HTTP File Transfer Mode Same Layout Option in Video Switching Conferences 22. General 23. General 3 MGC Release Notes - Version 7.5 Table 1: New Features List (Continued) Category Feature Name Circular Resource Mapping Description When the MCU is set to circular mode, Audio+ and Video+ card resources are allocated onto the next sequential unit that is free on a plus (+) card. Set the system.cfg flag: CIRCULAR_MAPPING_MODE_FOR_ AUDIO_VIDEO_PLUS=YES (default =YES). The MGC+ unit is shipped with two Entry Queues and eight Meeting Rooms and the appropriate EQ and IVR Services. The Falcon diagnostic tool is an add-on to the MGC Manager application that enables you to run diagnostic tests on the hardware of MGC. The Diagnostic Tool option is accessed from the Options menu in the MGC Manager application. 24. General 25. General MGC+ Predefined IP Only Entry Queues and Meeting Rooms New Diagnostic tool (Falcon) 26. General 4 Version 7.5 Upgrade Package Contents Version 7.5 Upgrade Package Contents Version 7.5 upgrade package includes the following items: · · MGC Software CD -- MGC Manager software -- MGC unit software -- External DB Tools · Documentation describing how to work with an external database application for Ad Hoc Conferencing and Conference Access Authentication · Sample Scripts for working with an external database application -- IVR · Default Message Services in English · Message Services in Spanish · Voice Messages in both *.wav and *.aca format -- File: system.cfg MGC Documentation -- Version 7.5 Release Notes -- MGC Manager User's Guide, Volume I -- MGC Manager User's Guide, Volume II -- MGC Manager User's Guide, VoicePlus Edition -- MGC Administrator's Guide -- MGC-50/MGC-100 Getting Started Guide -- MGC+50/MGC+100 Getting Started Guide -- MGC-25 Getting Started Guide -- MGC-50/MGC-100 Hardware and Installation Guide -- MGC+50/MGC+100 Hardware and Installation Guide -- Microsoft--Polycom Deployment Guide, Phase I -- Nortel--Polycom Deployment Guide, Phase I 5 MGC Release Notes - Version 7.5 Prior to Installation and SW Upgrade Reservations are automatically restored after software upgrade and you therefore do not need to Restore reservations. It is recommended that you backup reservations using the Reservations Backup utility. Reservation backups are not compatible between versions, therefore you should backup reservations before and after upgrade. Hardware Update Notice Please make sure the hardware listed below is used with the listed MGC version and MGC Manager versions: H/W Version # Board Type MGC Versions SIP H.264 H.239 AES MGC-50/MGC+50/MGC-100/MGC+100 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Audio 12/24*1 Audio+12/24 Audio 24/48*1 Audio+24/48 Audio 48/96*1 Audio+48/96 Video+8 Video+8 IP12 IP24 V1.04-7 V1.04-7 & V1.23 V1.04-7 V1.04-7, & V1.23 V1.04-7 V1.04-7, & V1.23 V1.23­ V1.31 V2.03 V1.45 V2.01-4 & V2.21-5 V4.22-5 V4.43 V4.43 V4.44 V1.01 & V1.21 V1.21 V4.42 V5.0 and later V5.17, V6.03 and later V5.0 and later V5.17, V6.03 and later V5.0 and later V5.17, V6.03 and later V5.0 and later V5.17, V6.03 and later V5.0 and later V5.0 and later n/a n/a n/a n/a n/a n/a n/a n/a NO NO n/a n/a n/a n/a n/a n/a n/a n/a YES YES n/a n/a n/a n/a n/a n/a n/a n/a YES YES n/a n/a n/a n/a n/a n/a n/a n/a NO NO 1 1. 12. 13. 14. 15. 16. 17. IP48 IP+12 IP+24 IP+48 IP48 I/O*2 IP+48 I/O*3 MUX+10 V5.0 and later V6.03 and later V6.03 and later V6.03 and later V5.0 and later V6.0 and later V7.0 and later YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES n/a n/a n/a 6 Prior to Installation and SW Upgrade # Board Type MUX+20 MUX+40 H/W Version V4.43 V4.44 MGC Versions V7.0 and later V7.0 and later SIP H.264 H.239 AES YES YES 18. 19. n/a n/a n/a n/a n/a n/a MGC-25 20. 21. 22. 23. IPN IPN AUDIO-A AUDIO-A V1.24 & V1.26 V1.41 V1.04 V1.21 V5.0 and later V6.11, V7.0 and later V5.0 and later V6.11, V7.0.1 and later YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES YES *1--These cards are not supported with the MGC+50/100. Only Audio+12/24, Audio+24/48 and Audio+48/96 are supported with the MGC+50/100. *2--Does not work with the new IP+ card V4.43 (IP+12/24/48) *3--Backward compatible; shipped with IP+ V4.43 (MGC 7.0.0) Please be aware that upgrading the MGC-100 hardware may require upgrading the power supplies (the MGC-50 has one 600W power supply). As a general guideline: · · · · · Each board consumes up to 40W apart from video boards. The Video+8 board consumes 75W, the Video6 board (older video board) consumes 55W and the Dual Video (2 Video6 boards tied together) consumes 110W. The Control Unit consumes 30W. Each older power supply unit (marked as PWR on its front panel) provides 300W (AC & DC). Each new power supply unit (marked as POWER on its front panel) provides 450W (AC & DC). Control Unit Update Notice The MCU Control unit must have at least 128 MB of memory to run MCU Version 7.5 and later. 7 MGC Release Notes - Version 7.5 Version 7.5 Interoperability Table The following table lists the devices with which Version 7.5 was tested. Table 1: Version 7.5 Interoperability List Device Gatekeepers/Proxies Polycom PathNavigator Cisco gatekeeper Radvision ECS gatekeeper Tandberg gatekeeper Microsoft LCS SIP proxy Nortel MCS Iptel proxy MCUs and Call Managers Cisco Call Manager Tandberg MCU Tandberg MPS Radvision viaIP MCU Gateways Cisco IP gateway Radvision viaIP gateway Tandberg gateway Dilithium DTG2000 3G gateway Ericsson VIG 3G gateway Polycom Office Products Polycom PCS Polycom GMS Polycom WebOffice Endpoints Polycom ViaVideo1 Polycom ViaVideo 2 Polycom PVX Polycom VS512 Polycom VSSP128 6.0.01288 6.0.01288 6.0.01288 and 8.0.0.0521 7.5.2 7.5.2 7.0 (tested in version 7.01) 6.0 and 7.0 (tested in version 7.01) 6.02.03 and 7.0 (tested in version 7.01) 12.3 (tested in version 7.01) 2.0.1.8 (tested in version 7.01) 2.1 (tested in version 7.01) (tested in version 7.01) 1.5 (tested in version 7.01) 4.0.1 and 5.0 (tested in version 7.01) D3.4 (tested in version 7.01) 1.1 (tested in version 7.01) 3.5 and 3.6 (tested in version 7.01) 5.20, 6.0 and 7.0 12.2 (tested in version 7.01) 3.5.1.2 N2.0 (tested in version 7.01) 2003 and 2005 5100 and 5200 Version 8 Prior to Installation and SW Upgrade Table 1: Version 7.5 Interoperability List (Continued) Device Polycom VSSP384 Polycom VS EX Polycom VS FX Polycom VS4000 Polycom V500 Polycom V500 Pal Polycom VSX3000 Polycom VSX7000 Polycom VSX8000 Polycom iPower 600 Polycom iPower 900 Polycom iPower 9000 Aethra VegaStar Gold Sony PCS1 Tandberg 1000 Tandberg 500 Tandberg 6000 B Tandberg 6000 E Tandberg 6000 F MXP Tandberg 800 Tandberg 880 B Tandberg 880 E Tandberg 880 F MXP VCON Cruiser VCON Escort VCON Falcon IP VCON MC8000 VCON Vigo VCON vPoint MS Windows messenger (SIP) Nortel SW client (SIP) Version 7.5.2 6.04 6.04 6.04 7.52 and 8.0 7.52 and 8.0 7.52 and 8.0 7.52 and 8.0 7.52 and 8.0 6.0.315 6.0.315 6.0.315 5.1.15 (tested in version 7.01) 2.30 and 2.41 B9.0 E4.0 (tested in version 7.01) B9.0 E4.1 (tested in version 7.01) and E4.2 & E5.0 F2.3,F2.5 (tested in version 7.01) and E4.2 & E5.0 B9.0 B9.0 E4.1, E4.2 (tested in version 7.01) and E4.2 & E5.0 F2.3, F2.5 (tested in version 7.01) and E4.2 & E5.0 4.6 (tested in version 7.01) 4.6 (tested in version 7.01) 0301.m01.d08.h10 (tested in version 7.01) 4.6 (tested in version 7.01) 5.10.0085 (tested in version 7.01) 6.0 (tested in version 7.01) 5.0.381 3.0 and 3.1 9 MGC Release Notes - Version 7.5 Software Upgrade Procedure Upgrade Checklist Prior to upgrading to Version 7.5 it is recommended you perform the following steps: 1. 2. 3. 4. Verify the amount of free disk space on the MCU, see "MCU Disk Space Verification" below. This step is required for older MCUs with PSOS operating systems only. Backup configuration and Reservations, see the MGC Administrator's Guide, Chapter 5. Removing a redundant configuration file see "Removal of Redundant Configuration Files" on page 17 The system saves the network cards' circuit ID assignment during the upgrade process. However it is recommended that you document the network cards' circuit ID assignments and order. Version 7.5 requires the installation of a hardware key (dongle) on the MCU. For details see "Dongle Upgrade Instructions" on page 12. Install the new MCU version. For details see "MGC Unit Software Upgrade Procedure" on page 16. Install the new system.cfg file, see MGC Administrator's Guide, Chapter 5, Send File section. Install the new MGC Manager version. For details, see "Installing the MGC Manager Software" on page 19. Back up the configuration (Backup Configuration) and database files (Backup Reservations) to create backups that are compatible to the new version. 5. 6. 7. 8. 9. MCU Disk Space Verification IP Terminal can be used to verify the disk space on the MCU. This verification is applicable to older systems running with PSOS operating system only. To verify the disk space on the MCU: 1. Right-click the MCU icon, and then click IP Terminal. The Donkey-COM window opens. 2. In the command line of the Donkey-COM window, type disk_stat and press Enter. 10 Software Upgrade Procedure The system displays information about the MCU disk. In case the number of Available Bytes is lower than 130,000, please contact support before installing the new version. Dongle Upgrade Dongle Information The MGC-50/100 is shipped with a dongle installed on COM1 of the rear panel. The MGC-25 is shipped with a dongle installed on parallel port of the rear panel. To verify if you have a dongle you are required to inspect the rear panel of the MCU as shown in Figure 1. The dongle label also includes the dongle serial number. Figure 1: MCU-100 & MCU-25 rear panels and their dongles 11 MGC Release Notes - Version 7.5 Product warranty will be void if seal label is removed or damaged. WAR NIN G POLYCOM LAN R VGA MOUSE KEYBOARD COM1 COM2 ALARMS Figure 2: MCU+ 50 rear panel and Dongle location The Dongle is backward compatible with current or previous MGC Manager versions. Dongle Upgrade Instructions For a major version, such as upgrading from version 5.xx, 6.xx and 7.xx, a new dongle file must be loaded onto the MCU. To acquire the new dongle file, access the Polycom Resource Center ("Downloading the Dongle File" on page 14) or contact your next level of support. Version 7.5 requires a new dongle file, and this file should be loaded prior to the upgrade. MGC-50/MGC-100 · Check the serial number of the dongle currently installed on the MCU (on the Dongle, a white label either on the face or side lists the Serial No.); right-click the MCU icon, and then click Dongle Information. The Dongle Information dialog box opens, displaying the dongle's serial number and the current MCU version. The serial number displayed in the Dongle Information dialog box should match the serial number of dongle as it appears in the name of the file sent to you (usually via e-mail). If the numbers do not match, do not proceed with the upgrade process and contact support. 12 Software Upgrade Procedure MGC-25 · Before you upgrade the dongle, please check and record the assignment between the ISDN Network Service and ISDN Network card. · Check the serial number of the dongle currently installed on the MCU; right-click the MCU icon, and then click System Configuration. The serial number displayed in the System Configuration dialog box should match the serial number of dongle as it appears in the name of the file sent to you (usually via 13 MGC Release Notes - Version 7.5 e-mail). If the numbers do not match, do not proceed with the upgrade process and contact support. Downloading the Dongle File Prior to accessing the Polycom Resource Center Web site, retrieve from the MCU the system serial number. · The MCU-25/50/100 have a Polycom label with a Serial No. fixed on the rear panel. To retrieve the Dongle File from a Polycom Web Site: Access the Polycom Resource Center web site http://extranet.polycom.com/csnprod/ signon.html. User ID and Password are required to access this site. If you do not have a User ID or Password, please refer to your next level of support. 3. 4. Enter your User ID and Password and click Sign In. The Welcome to the Polycom Resource Center window appears. Click MGC Product Activation. The MGC Dongle Upgrade File window opens. 5. Enter the System Serial Number and Dongle Serial Number. 14 Software Upgrade Procedure 6. Click Download. Save the new dongle file. When the following error message appears: "No Maintenance Agreement Found/ MGC Serial Number not Found", please contact your next level of support. 7. Click OK when Download is complete. Installing the Dongle File To Upgrade the Dongle: 1. Connect to the MCU. 2. Right-click the MCU icon, click MCU Utils, and then click Send Configuration File. The Open dialog box opens. 3. Select the file .don from its location on your PC's hard disk, and then click Open. The dongle is being upgraded. Reset the MCU. Connect to the MCU and verify that the dongle information was updated; right-click the MCU icon, and then click Dongle Information. The new version number should be listed in the MCU Version box. 4. 5. 15 MGC Release Notes - Version 7.5 MGC Unit Software Upgrade Procedure You can run the installation from the CD, or you can copy the files to your hard drive, and then select the hard drive/directory as the source files path. Before upgrading the MCU software version: · If you do not have a dongle installed on your MCU, you must install it before upgrading to version 7.X.X. For more information, please contact Support. · · · A new dongle file must be loaded to the MCU to upgrade from version 5.XX or 6.XX to version 7.X.X. Backup your configuration, including all Message Services. It is important to back up all reservations in the MCU. This is to safeguard against reservations being lost. However, reservations backups can only be used with the same version for which backups were created. Upgrading from a Version using Password for Entry Queue Routing Version 7.5 uses Numeric ID as the routing method from Entry Queues to destination conferences. If your current version uses conference or chairperson password for routing from Entry Queues to destination conferences, when upgrading to Version 7.5, you must modify the system.cfg file included in the software kit. To upgrade the MCU version: 1. Download the MCU software to the MCU. For more details, see "MGC Unit Software Upgrade Procedure". Entry Queue Password routing mode is required to run PCS version 7.0.0. 2. To route participants from the Entry Queue to the destination conference using the conference or chairperson password, you must modify the system.cfg file included in the software kit: a. b. c. Open the system.cfg file located in the MCU software folder. In the GREET AND GUIDE/IVR section, change the value of QUICK_LOG_IN_VIA_ENTRY_QUEUE flag to YES. Optional. To assign the same Numeric ID to different non concurrent conferences, in the GENERAL section change the value of RESERVATION_CONFERENCE_ID_UNIQUE to NO. Save the file. d. 3. 4. 5. 6. 7. Send the "system.cfg" file to the MCU (MCU Utils -> Send File). Reset the MCU. Install the MGC Manager application Version 7.5. In the MGC Manager application, list the IVR/Entry Queue Message Services. For each listed Entry Queue Service, assign the appropriate voice messages in the new Conference ID tab. 16 Software Upgrade Procedure Upgrading from a Version using Numeric ID for Entry Queue Routing Version 7.5 uses Numeric ID as the routing method from Entry Queues to destination conferences. If your current version uses Numeric ID for routing from Entry Queues to destination conferences (version 6.x and higher), no change in the system.cfg file is required. To upgrade the MCU version: 1. Download the MCU software to the MCU. For more details, see "MGC Unit Software Upgrade Procedure". 2. 3. Send the "system.cfg" file included in the software kit to the MCU (MCU Utils -> Send File). Reset the MCU. Removal of Redundant Configuration Files With initial MGC version installations, it is possible that the MCU was subject to version downgrades. In order to ensure smooth MGC version upgrade (if the MCU was subject to a downgrade), restore reservations, meeting rooms and card configurations prior to manually removing specific configuration files. Please contact Polycom Support for further instructions. Downloading the Software to the MCU To install a software update on the MCU: 1. On the File menu, click Download MCU Software. Alternatively, right-click the MCU icon, click MCU Utils, and then click Download MCU Software. The Logon dialog box opens. The Login Name and Password of the currently logged in operator are entered by default. If required, enter another login name and password. 17 MGC Release Notes - Version 7.5 2. Click OK. The Software Installation dialog box opens. The MCU software will be installed on each listed MCU. 3. Select the Install Default Services check box to download the default IVR Service, Entry Queue Service, and Gateway Service. The default IVR Service is in English and is named IVR70. The default Entry Queue Service is in English and is named EQ70. You can manually install the default English IVR Service and Entry Queue Service or the English and Spanish IVR and Entry Queue Services. For more information, see "Installing the MGC Manager Software" on page 19. You can download software to all MCUs listed in the MCU List in one operation. If the list is not complete, you can add MCUs to the list by clicking the Add MCU button. To avoid downloading the software to an MCU, remove the MCU from the list by selecting the MCU Name, and then clicking the Remove MCU button. For more details, see the MGC Administrator's Guide, Chapter 2. In the Enter path to source files box, type the full path to the folder containing the software version. Alternatively, click the Browse button and use standard Windows techniques to select the Folder containing the software. If the folder is named Vaaa.bbb, where aaa is the MGC Manager version number, and bbb is the MCU version number. 4. 5. You need to select the folder containing the latest version number, and not the sub-folder labeled Disk 1. 6. 7. · Click OK. The software version's path is displayed in the Enter path to source files box. Click the Install button to start the installation procedure. When you upgrade the new software, the existing reservation files are automatically restored and converted to the new version format. It is essential to back up reservations using the new version format. When you upgrade the MCU's software, the existing card configuration files are automatically restored. After the completion of the upgrade process, you need to manually update the existing Entry Queue Services by adding the voice message files prompting for the conference Numeric ID, otherwise the participants are placed on hold and cannot move to the target conferences. · · 8. Reset the MCU. Sometimes, an error message "No_Connection_With_Card" is displayed when the software download to the cards takes more than 420 seconds. In such a case, reset each of the cards manually. 18 Software Upgrade Procedure Installing the MGC Manager Software The MGC Manager software is Windows 95/98/NT/ME/2000/XP based software. After downloading the software from the FTP and unzipping the files: 1. Open Windows Explorer and open the folder that contains the MGC Manager diskettes. 2. 3. Browse to Disk 1 and double-click the Setup.exe file. Follow the on-screen instructions to complete the installation procedure. Manual Installation of the Default Message Services When upgrading from versions 5.x, 6.0 and 6.0x, the upgrade kit includes new Message Services that can be automatically installed on the MCU during the software installation. You can also manually install the default Message Services at the end of the installation process. The software CD contains two types of IVR Services: · · English English and Spanish The Automatic installation of Message services during MCU software update automatically installs the English only Message Services. The manual installation process enables you to install the English and Spanish Message Services as well as the English only. When you install the English and Spanish IVR Service, two separate IVR Services are created on the MCU and the English IVR Service is automatically set as the default IVR Service. To restore the Default IVR Service: The default Message Services are installed using the Restore Configuration utility. 1. 2. 3. Right-click the MCU icon, click MCU Utils, and then click Restore Configuration. Enter the path to the folder containing the configuration files to be installed, or click the Browse button to locate them. From the Version 7.5 software folder, select the English V7 IVR or the English and Spanish V7 IVR folder, according to the required Message Service, and click OK. The system returns to the Restore dialog box. Click OK to continue. Click the Select All button. Click OK to install the default Message Services on the MCU. At the end of the Restore process, a message is displayed indicating that the MCU must be reset to be able to use the new Message Services. Click OK and reset the MCU. 4. 5. 6. 7. 8. 19 MGC Release Notes - Version 7.5 Updating the Entry Queue Services When upgrading from Version 5.x to Version 7.5 you need to update the Entry Queue Service to include the appropriate voice messages. To update the Entry Queue Service: 1. Expand the IVR Message Services list (under the MCU Configuration list). 2. Right-click the icon of Entry Queue Service to update (an Entry Queue Service that was defined in version 5.x), and then click Properties. The Entry Queue Message Service - General dialog box opens. 3. Click the Conference ID/Password tab. 4. In the Entry Queue Message Service - Conference ID/Password dialog box, assign the following voice messages: -- Using Conference Password for Entry Queue Routing (Version 5.x mode): Request Conference ID/Password: CONFPASS.ACA · Join Failure Message: CONFRTRY.ACA These files are located in the MGC software kit (as part of the default IVR Service for Version 7.5), in the following path: · MGC50-100 Version 7.5\MGC SW CD Ver 7.5\IVR\Default Services\English V7 IVR\msg\LANG70\NID\NUMID. -- Using Conference Numeric ID for Entry Queue Routing: Request Conference ID/Password: CNFIDRQS.ACA · Join Failure Message: CNFIDFL.ACA These voice messages are located in the MGC software kit (as part of the default IVR Service for Version 7.5). · 5. Click OK to save the changes. 20 Detailed Description - Video Detailed Description - Video Video Support for Start Conference requires Chairperson Audio and Video conferences support the Start Conference requires Chairperson option. Detailed Description Versions 7.0 and previous, Audio Only conferences supported the Start Conference requires Chairperson option. Version 7.01 supported phase 1 of the feature for video conferences. In version 7.5, when the conference requires a chairperson, Audio or Video conference participants are placed on hold when they connect to the conference before the chairperson and hear background music. Set the system.cfg flag: WAIT_FOR_CHAIR_VIDEO_TYPE_NEW=YES (default = NO) Based on the Flags settings, two types of behavior are possible: · · NO; The participants can view each other and their audio is muted, till the chairperson joins the conference. YES; When placed on hold, connected participants view the Welcome slide and hear background music, till the chairperson joins the conference. SIP participants cannot view the Welcome slide. Figure 3: Setting tab with Start conf Requires Chairperson checkbox 21 MGC Release Notes - Version 7.5 Start Conference Requires Chairperson guidelines: · · · · · The conference must be defined with an IVR service. The IVR service must also include a video slide. An 'Entry Tone' is not played for the participants waiting for the chairperson to arrive. The `entry tone' is only heard when the chairperson is already in the conference. The conference time-out (20 minutes) activates if the chairperson fails to attend the conference. The operator cannot enable or cancel the Start Conference Requires Chairperson option while the conference is on-going. A participant accessing the conference by using the "attended" Entry Queue, is guided to the conference but hears music (audio conference) or views the welcome slide (video conference) when the chairperson has not yet entered the conference. 22 Detailed Description - General Detailed Description - General Network Time Protocol (NTP) for XPEK Systems The Network Time Protocol (NTP) on XPEK systems allows the MCU to synchronize the internal MCU control unit's clock with an external NTP server. Accurate time calculation is essential for cascaded or recurring conferences. Detailed Description The time synchronization protocol used in MGC version 7.5 is SNTP (Simple Network Time Protocol), a version of the NTP protocol used by Microsoft's W32Time Service. NTP servers use the time-zone independent Universal Time Coordinated (UTC) standard to synchronize networked computers. UTC is the current official standard that is based on an atomic clock and ensures uniform time calculation for networks. To synchronize MCU time with the NTP Server: 1. Right-click the MCU icon and click MCU Time. 23 MGC Release Notes - Version 7.5 The MCU GMT Time dialog box opens. You cannot set the MCU's time or connect to the NTP server, when there are On Going conferences on the bridge. 2. 3. 4. In the MCU GMT Offset box, enter the time difference between the MCU Local Time and MCU GMT Time. Select the Use NTP Server check box, and enter the IP address of the NTP server. Click OK. NTP Server synchronization may take up to an hour. All time-related settings, such as the scheduled Starting Time of Reservations, are adjusted. 24 Detailed Description - General Secure Socket Layer (SSL) SSL (Secure Socket Layer) enables secure HTTP connection on MCU's with XPEK Operating Systems with the MGC Manager, WebCommander and MGC API applications. Detailed Description SSL Certificate is required to enable SSL-level security for the MCU's connection to external applications. SSL uses a third party, that is the Certificate Authority, to identify HTTP transactions and secure them using the HTTPS protocol. The SSL certificate must be obtained on first connection to the MCU. To obtain the SSL certificate: 1. Connect to the MCU. 2. Right-click the unit's icon or name, and then click Create SSL Certificate Request. The dialog box opens where you can enter data for the request and apply. 3. Fill in the following information: Table 2: SSL Certificate Request - Required Information Field Country State or Province Locality Organization Organizational Unit Common Name (DNS/IP) Description Enter any 2 letter code for the country name. Enter the full name of the state or province. Enter the full name of the town/city/location. Enter the full name of your organization for which the certificate will be issued. Enter the full name of the unit (group or division) for which the certificate will be issued. Enter the DNS or the IP address of the MCU. Enter complete information, as all fields are mandatory for the request. 25 MGC Release Notes - Version 7.5 4. Click Apply. The new certificate request appears in the details box. 5. Click Copy, then click Close. Alternatively, for a previously defined MCU for which SSL has been obtained before, click Get to get the latest certificate request from the MCU. In the browser, access your preferred certificate authority (for example, http:// www.thawte.com and select from the quick login box: Certificate Status), paste the certificate request from MCU and submit. The authority issues the SSL certificate, and sends the certificate to you by E-mail. When the E-mail with the certificate arrives from the authority, select the text and click Copy. Back in the MGC Manager application, right-click the MCU's icon and click Send SSL Certificate. 6. 7. 8. The Send SSL Certificate dialog box opens. 26 Detailed Description - General 9. Paste the certificate's text in the Send SSL certificate window. 10. Click Send. The MCU validates the certificate. -- If the certificate is not valid, the following message appears: -- If the certificate matches the private key, and the task is completed, a message informs you that the certificate was created successfully. 11. Reset the MCU. The system has access to the SSL-secured port 443. 27 MGC Release Notes - Version 7.5 To enable a Mandatory and Secure connection for the MCU: 1. Before connecting the MCU, right-click the MCU icon and click MCU Utils, then click Edit "system.cfg". The SysConfig dialog box opens. 2. In the GENERAL section, set the following flags to: -- SECURED_PORT_MANDATORY_FOR_API=YES -- SECURED_PORT_MANDATORY_FOR_FILE=YES -- PREFERRED_SECURED_PORT=443 3. 4. Click OK and then reset the MCU. Right-click the MCU icon and then click Properties. Do not connect to the MCU. When you right-click the MCU, the MCU should be disconnected and the icon appear grey. The Properties dialog box opens. 5. 6. Click Advanced. Select the Secured check box to enable mandatory security. 7. 8. 9. Ensure that the Automatic Discovery option is deactivated (clear the check box). The Port Number box is enabled, enter port 443 as the Port Number. Click OK. 10. Connect to the MCU. When reconnected, the MCU uses the secured port. After reconnecting, it is recommended to change the login password. 28 Detailed Description - General -- The HTTPS protocol is indicated in the Connections list Protocol column under the MCU Configuration icon. Port 443 and the Secured (the lock) icon are indicated in the MGC Manager window's status bar. 29 MGC Release Notes - Version 7.5 H.239/People+Content Star Cascading H.239/People+Content Star Cascading is available with mixed H.320 and H.323 Video Switching conferences. Detailed Description In MGC version 7.0, H.239/People+Content Star Cascading was only available in an IP Video Switching environment. All the conferences in the Star Cascading topology must have the same settings for the conference: line rate, audio algorithm, Video Parameters (Video Protocol, Video Format, Video Frame Rate, Annexes, and ProMotion) and other conferencing features such as Encryption. Highlights: · One central MCU is required in a conference. A slave MCU can only be cascaded to the main MCU. A Slave MCU cannot be cascaded with other slave MCUs. · Only two cascade options - "Master" and "Slave" - is available in H.320 H.239/ P+C cascade. There will be no "Auto" cascade mode like in regular H.320 cascade. · IVR is supported. However, if Node Type in the Participant Properties - Advanced is set to MCU, no IVR service is available. · Encryption is supported. · H.243 site names for H.320 are supported H.320 cascade links use the H.239 protocol and not Polycom P+C protocol, as in IP cascaded conferences. H.239 can only be implemented when in the system.cfg: H.239=YES. 30 Detailed Description - General Ad Hoc Auto Cascade The Auto Cascade feature enables automatic cascading of conferences. Both audio only and video conferences can be cascaded. Detailed Description The automatic cascading of conferences is beneficial in distributed MCU environment, when MCUs are installed in different locations. A maximum of six conferences can be Auto Cascaded into one conference. The MCU network can support multiple Auto Cascaded conferences simultaneously. The cascading is performed by an Ad Hoc Cascade component in the WebCommander Professional which monitors the MCUs. When the Ad Hoc Cascade component finds that two or more MCUs are running a conference with the same Conference Numeric ID, it checks if the conferences are already cascaded by looking for a cascading link between the conferences. If there are no cascading links, conferences are automatically connected using pre-defined cascading links. If at a later stage the Ad Hoc Cascade component finds an additional MCU running a conference with the same Numeric ID, it adds the conference to the cascaded conferences. Set up identical Ad Hoc Entry Queues and Profiles on each MCU, so that the cascaded conferences will have the same properties. To use the Auto Cascade feature, the system.cfg flag QUICK_LOGIN_VIA_ENTRY_QUEUE must be set to NO on all MCUs, that is, the Conference Numeric ID routing mode must be used. This flag is located in the GREET AND GUIDE/IVR section of the system.cfg file. 31 MGC Release Notes - Version 7.5 Defining Auto Cascading Entry Queues To eliminate IVR prompts when Auto Cascade links are created, you must set up Auto Cascade Entry Queues on each MCU. 1. In the Entry Queue Properties dialog box, select the Cascade check box. 2. 3. 4. Enter a value in the Numeric ID field. The Numeric ID must be identical in the Auto Cascading Entry Queues of all the MCUs. Leave the Ad Hoc check box cleared. Proceed to configure the Entry Queue as for any other Entry Queue. Implementation of Chairperson DTMF features The following chairperson DTMF actions are implemented across the MCUs: · · · · · · Mute all but me and unmute Terminate the conference Place the conference on hold and release the conference from being placed on hold Lock and unlock the conference Secure the conference and release a secured conference Wait for the Chairperson Chairperson Conference Activation If chairperson activation is enabled in the Auto Cascade configuration in the MGC WebCommander Server Manager, then the cascaded conference may implement the "Start only when the chairperson connects", and "Terminate conference after the chairperson exits" features, provided these options are selected in the individual conferences. If the 32 Detailed Description - General