MGC-25/50/100 MGC+50/100

Transcription

1 MGC-25/50/100 MGC+50/100 Release Notes Version 7.5 February 2006 DOC2134A

2 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 to 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.

3 Table of Contents Version 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 MGC 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

4 MGC Release Notes - Version 7.5 HTTP File Transfer Mode Detailed Description Same Layout Option in Video Switching Conferences Direct IP Dial-in Detailed Description Direct End Point Dialing IP to ISDN Gateway Call (without Gatekeeper) SIP Factory Detailed Description Nortel Environment Flag Settings MGC+ Predefined IP only Entry Queues and Meeting Rooms Corrections, Pending Issues and Limitations...43 Corrections between Versions V and V Corrections between Versions V and V Corrections between Versions V.7.0 and V Version 7.5 Pending Issues Version 7.5 System Limitations Appendix A - Falcon Diagnostic Tool...65 Detailed Description Test Description Starting the Falcon Diagnostic Tool Falcon Main Window Setting the Log Files Path Connecting to an MCU Running Diagnostic Tests Test Results Disconnecting from the Falcon Diagnostic Tool Appendix - Adding an MCU to the Network Test Glossary Log File Report Examples ii

5 Version New Features List Version New Features List The following table lists the new features in Version 7.5. Table 1: New Features List Category Feature Name Description 1. Video H.264 SD/HD in Video Switching conferences 2. Video Increased Frame Rate in H.264 CP conferences 3. Video H.264 up to 2 Mbps in VideoSwitching Conferences 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. Set the system.cfg flag: MAX_H264_CP_FR=30 (Default = 25) In H.264 VideoSwitching Conferences, the maximum Line Rate capability is 1920 Kbps. Supported in MGC version Video H.264 Fixed Mode 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. 5. Video Video Support for Start Conference requires Chairperson 6. IP H.323 dial-out automatic redial 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. 7. IP Direct IP Dial-in The MCU supports two new IP Dial-in methods: Direct Endpoint Dialing (Without Gatekeeper) IP to ISDN Gateway Call (without Gatekeeper) 1

6 MGC Release Notes - Version 7.5 Table 1: New Features List (Continued) Category Feature Name Description 8. IP SIP REINVITE 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. 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. 10. IP SIP REFER 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. 11. IP SIP Factory Allows SIP endpoints to create ad hoc conference and automatically connect to the conference. 12. IP Microsoft LCS support This version supports multipoint SIP conferencing in a Microsoft environment: Microsoft LCS 2005, SP1, 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 & MGC Manager 7.5 Note: This product requires purchase of a license. 2

7 Version New Features List Table 1: New Features List (Continued) Category Feature Name Description 13. Microsoft LCS support (con t) 14. IP IP Bridge Higher Capacity 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. 15. IP Nortel 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. 16. IP H.323 FECC T.140 Closed Captioning is supported with H.323 FECC. 17. General Network Time Protocol (NTP) for XPEK Systems 18. General Secure Socket Layer (SSL) 19. General H.239/People+Content Star Cascading 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. 20. General Ad Hoc Auto Cascade Ad Hoc conferences can be automatically cascaded. When an identical Numeric ID is used for each conference, the WebCommander automatically cascades the conferences. 21. General Faulty Participant Marked in Red 22. General HTTP File Transfer Mode 23. General Same Layout Option in Video Switching 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. 3

8 MGC Release Notes - Version 7.5 Table 1: New Features List (Continued) Category Feature Name Description 24. General Circular Resource Mapping 25. General MGC+ Predefined IP Only Entry Queues and Meeting Rooms 26. General New Diagnostic tool (Falcon) 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. 4

9 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

10 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: # Board Type H/W Version MGC Versions SIP H.264 H.239 AES MGC-50/MGC+50/MGC-100/MGC Audio 12/24* 1 V1.07 V5.0 and later n/a n/a n/a n/a 2. Audio+12/24 V1.23 V5.17, V6.03 and later n/a n/a n/a n/a 3. Audio 24/48* 1 V1.07 V5.0 and later n/a n/a n/a n/a 4. Audio+24/48 V1.23 V5.17, V6.03 and later n/a n/a n/a n/a 5. Audio 48/96* 1 V1.07 V5.0 and later n/a n/a n/a n/a 6. Audio+48/96 V1.23 V5.17, V6.03 and later n/a n/a n/a n/a 7. Video+8 V1.31 V5.0 and later n/a n/a n/a n/a 8. Video+8 V2.03 V5.17, V6.03 and later n/a n/a n/a n/a 9. IP12 V1.45 V5.0 and later NO YES YES NO 10. IP24 V2.25 V5.0 and later NO YES YES NO 11. IP48 V4.25 V5.0 and later YES YES YES YES 12. IP+12 V4.43 V6.03 and later YES YES YES YES 13. IP+24 V4.43 V6.03 and later YES YES YES YES 14. IP+48 V4.43 V6.03 and later YES YES YES YES 15. IP48 I/O* 2 V1.01 V5.0 and later YES YES YES YES 16. IP+48 I/O* 3 V1.21 V6.0 and later YES YES YES YES 17. MUX+10 V4.42 V7.0 and later n/a n/a n/a YES 18. MUX+20 V4.42 V7.0 and later n/a n/a n/a YES 19. MUX+40 V4.42 V7.0 and later n/a n/a n/a YES 6

11 Prior to Installation and SW Upgrade # Board Type MGC-25 H/W Version MGC Versions SIP H.264 H.239 AES 20. IPN V1.24 V5.0 and later YES YES YES YES 21. IPN V1.41 V6.11, V7.0 and later YES YES YES YES 22. AUDIO-A V1.04 V5.0 and later YES YES YES YES 23. AUDIO-A V1.21 V6.11, V7.0.1 and later 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

12 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 Version Gatekeepers/Proxies Polycom PathNavigator 5.20, 6.0 and 7.0 Cisco gatekeeper 12.2 (tested in version 7.01) Radvision ECS gatekeeper Tandberg gatekeeper N2.0 (tested in version 7.01) Microsoft LCS SIP proxy 2003 and 2005 Nortel MCS 5100 and 5200 Iptel proxy MCUs and Call Managers Cisco Call Manager and 5.0 (tested in version 7.01) Tandberg MCU D3.4 (tested in version 7.01) Tandberg MPS 1.1 (tested in version 7.01) Radvision viaip MCU 3.5 and 3.6 (tested in version 7.01) Gateways Cisco IP gateway 12.3 (tested in version 7.01) Radvision viaip gateway (tested in version 7.01) Tandberg gateway 2.1 (tested in version 7.01) Dilithium DTG2000 3G gateway (tested in version 7.01) Ericsson VIG 3G gateway 1.5 (tested in version 7.01) Polycom Office Products Polycom PCS 7.0 (tested in version 7.01) Polycom GMS 6.0 and 7.0 (tested in version 7.01) Polycom WebOffice and 7.0 (tested in version 7.01) Endpoints Polycom ViaVideo Polycom ViaVideo Polycom PVX and Polycom VS Polycom VSSP

13 Prior to Installation and SW Upgrade Table 1: Version 7.5 Interoperability List (Continued) Device Version Polycom VSSP Polycom VS EX 6.04 Polycom VS FX 6.04 Polycom VS Polycom V and 8.0 Polycom V500 Pal 7.52 and 8.0 Polycom VSX and 8.0 Polycom VSX and 8.0 Polycom VSX and 8.0 Polycom ipower Polycom ipower Polycom ipower Aethra VegaStar Gold (tested in version 7.01) Sony PCS and 2.41 Tandberg 1000 B9.0 Tandberg 500 E4.0 (tested in version 7.01) Tandberg 6000 B B9.0 Tandberg 6000 E E4.1 (tested in version 7.01) and E4.2 & E5.0 Tandberg 6000 F MXP F2.3,F2.5 (tested in version 7.01) and E4.2 & E5.0 Tandberg 800 B9.0 Tandberg 880 B B9.0 Tandberg 880 E E4.1, E4.2 (tested in version 7.01) and E4.2 & E5.0 Tandberg 880 F MXP F2.3, F2.5 (tested in version 7.01) and E4.2 & E5.0 VCON Cruiser 4.6 (tested in version 7.01) VCON Escort 4.6 (tested in version 7.01) VCON Falcon IP 0301.m01.d08.h10 (tested in version 7.01) VCON MC (tested in version 7.01) VCON Vigo (tested in version 7.01) VCON vpoint 6.0 (tested in version 7.01) MS Windows messenger (SIP) Nortel SW client (SIP) 3.0 and 3.1 9

14 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. 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. 2. Backup configuration and Reservations, see the MGC Administrator s Guide, Chapter Removing a redundant configuration file see Removal of Redundant Configuration Files on page 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. 5. Version 7.5 requires the installation of a hardware key (dongle) on the MCU. For details see Dongle Upgrade Instructions on page Install the new MCU version. For details see MGC Unit Software Upgrade Procedure on page Install the new system.cfg file, see MGC Administrator s Guide, Chapter 5, Send File section. 8. Install the new MGC Manager version. For details, see Installing the MGC Manager Software on page Back up the configuration (Backup Configuration) and database files (Backup Reservations) to create backups that are compatible to the new version. 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

15 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

16 R MGC Release Notes - Version 7.5 LAN WARNING Product warranty will be void if seal label is removed or damaged. POLYCOM 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 ). If the numbers do not match, do not proceed with the upgrade process and contact support. 12

17 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

18 MGC Release Notes - Version 7.5 ). 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 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. Enter your User ID and Password and click Sign In. The Welcome to the Polycom Resource Center window appears. 4. Click MGC Product Activation. The MGC Dongle Upgrade File window opens. 5. Enter the System Serial Number and Dongle Serial Number. 14

19 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 <nnnn>.don from its location on your PC s hard disk, and then click Open. The dongle is being upgraded. 4. Reset the MCU. 5. 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. 15

20 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 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. Open the system.cfg file located in the MCU software folder. b. In the GREET AND GUIDE/IVR section, change the value of QUICK_LOG_IN_VIA_ENTRY_QUEUE flag to YES. c. 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. d. Save the file. 3. Send the system.cfg file to the MCU (MCU Utils -> Send File). 4. Reset the MCU. 5. Install the MGC Manager application Version In the MGC Manager application, list the IVR/Entry Queue Message Services. 7. For each listed Entry Queue Service, assign the appropriate voice messages in the new Conference ID tab. 16

21 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. Send the system.cfg file included in the software kit to the MCU (MCU Utils -> Send File). 3. 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

22 MGC Release Notes - Version 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 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 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. You need to select the folder containing the latest version number, and not the sub-folder labeled Disk Click OK. The software version s path is displayed in the Enter path to source files box. 7. 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

23 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. Browse to Disk 1 and double-click the Setup.exe file. 3. 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. Right-click the MCU icon, click MCU Utils, and then click Restore Configuration. 2. Enter the path to the folder containing the configuration files to be installed, or click the Browse button to locate them. 3. 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. 4. Click OK to continue. 5. Click the Select All button. 6. Click OK to install the default Message Services on the MCU. 7. 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. 8. Click OK and reset the MCU. 19

24 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: MGC 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

25 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

26 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

27 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

28 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. Set the MCU s time. 3. Ensure that the Use NTP Server check box is selected, and enter the IP address of the NTP server. 4. Set the time difference between the MCU Local Time and MCU GMT Time in the MCU GMT Offset box. 5. 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

29 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

30 MGC Release Notes - Version 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. 6. In the browser, access your preferred certificate authority (for example, 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 When the with the certificate arrives from the authority, select the text and click Copy. 8. Back in the MGC Manager application, right-click the MCU s icon and click Send SSL Certificate. The Send SSL Certificate dialog box opens. 26

31 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

32 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= Click OK and then reset the MCU. 4. 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. Click Advanced. 6. Select the Secured check box to enable mandatory security. 7. Ensure that the Automatic Discovery option is deactivated (clear the check box). 8. The Port Number box is enabled, enter port 443 as the Port Number. 9. 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

33 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

34 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

35 Detailed Description - General Ad Hoc Auto Cascade Detailed Description The Auto Cascade feature enables automatic cascading of conferences. Both audio only and video conferences can be cascaded. 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

36 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. Enter a value in the Numeric ID field. The Numeric ID must be identical in the Auto Cascading Entry Queues of all the MCUs. 3. Leave the Ad Hoc check box cleared. 4. 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

37 Detailed Description - General Start only when the chairperson connects option is implemented, participants in all conferences will be placed on hold until a chairperson joins one of the conferences. If the Terminate conference after the chairperson exits option is implemented, all conferences will be terminated when there is no longer a chairperson connected to a conference. Terminating a Cascading Conference The system will terminate a slave conference when it no longer has any live participants, and will terminate the master conference when it no longer has any live participants itself and has no slave conferences with live participants. Monitoring Auto Cascaded Conference Links The links between Auto Cascaded conferences can be monitored in both the MGC Manager and the MGC WebCommander. The important links to monitor are the dial-out link participants. Figure 1-1 shows an example of monitoring an Auto Cascaded conference in the MGC Manager. Figure 1-1: Monitoring an Auto Cascade conference The Link Participant Names The dial-out link participant name will be as follows: LinkTo[ConferenceType(Master/Slave)]_[Target MCU IP]_ [Primary or Secondary connection (0/1)_[Link Number (01..99)] For example, the master conference link to slave3 may be called: LinkToSlave_ _0_03 Dial-in link participants will have a visual name of the following format after they are moved from the Entry Queue to the conference: LinkTo[ConferenceType(Master/Slave)]_[Link Number (01..99)] For example, the dial-in link from a slave conference may have the visual name: LinkToMaster_01 Limitations In Continuous Presence conferences, the layout must be set to full screen. The MGC Manager and WebCommander monitoring is per MCU. There is no GUI to display cascaded conferences across multiple MCUs as one conference. The following chairperson actions are implemented per MCU: Voting, Question and Answers, Replay Roll Call, Change password and Operator assistance. For H.263 4CIF and H.264 Continuous Presence conferences, the link will be defined as H.263 CIF. The Auto Cascade feature does not work with H.239/People + Content. 33

38 MGC Release Notes - Version 7.5 Faulty Participant in Red A Faulty participant connected to a conference has their background color marked red for greater visibility in the MGC Manager monitoring pane. Detailed Description All participants that have a problem with their connection and require operator assistance are marked and highlighted in a red background color. The cause of the problem is marked in the Connection column. To mark faulty participants in red in the MGC Manager: 1. From the Options menu, select Mark Faulty Participants in Red. A check mark appears before Mark Faulty Participants in Red. 2. In the MGC Manager all participants requiring operator assistance are highlighted in red, as shown in the Monitor pane. 34

39 Detailed Description - General HTTP File Transfer Mode Transfer of files using HTTP can be performed by the MGC Manager. Detailed Description HTTP can replace FTP, to solve Firewall issues, PSOS limitations in the FTP mode and address security issues occurring in FTP. The user can select either the HTTP or FTP mode of operation from the Options menu. When selecting FTP mode either an Active or Passive FTP connection can be enabled. To enable HTTP Connection mode from the Options menu: 1. In the Options menu, select FTP Configurations. The FTP Configurations dialog box opens. 2. Click Use HTTP Connection. Select Use FTP Connection and click Enable Passive FTP Connection to enable the Passive FTP mode. When the Passive FTP connection is enabled, the client opens the primary connection to the server. The server acknowledges a connection request, and informs the client on which port to connect to the secondary connection. The client opens the secondary connection according to the port supplied by the server. 35

40 MGC Release Notes - Version 7.5 Same Layout Option in Video Switching Conferences In version 7.5, when the Same Layout option is checked, the speaker in his monitor views himself instead of the previous speaker. 36

41 Detailed Description - General Direct IP Dial-in Direct IP MCU Dial-in modes: IP address & extension string. Enables internet IP calls to a MCU that functions as a Firewall Gateway (MCU is inside the Firewall zone). Detailed Description The MCU supports two new MCU Dial-in strings: Direct End Point Dialing IP to ISDN Gateway Call Direct End Point Dialing The Direct End Point Dialing method enables undefined dial-in participants to connect to conferences without a gatekeeper being used for address resolution. The Direct End Point Dialing method can be implemented with or without a Gatekeeper. When a Gatekeeper is present it should be set to a Direct Call Policy configuration. Conference dial-in can be achieved using one of the following methods: FX endpoints support the delimiter "," and not "##" H.323 card s IP address##conf NID (for example: ##1234) When the endpoint has extension capabilities available, list the H.323 card s IP address in the destination field and conference NID in the extension field. For example: as the call address and 1234 (conference NID) in the Extension field, or as destination IPaddress and 3116##1234 (i.e. ED NID , Conf. NID ) in the endpoint s Extension field. In case the endpoint has the extension capabilities use H.323 card s IP address as the destination address and EQ NID##conf NID in the extension field. For example: Test result summary for Meeting Rooms and On-Going conferences: IP + Extension is supported on VSX3000/7000/8000, V500, FX, and VS endpoints. IP##NID is supported on VSX3000/7000/8000, V500, FX, VS, Sony, and PVX endpoints. Test result summary for Entry Queues: IP + Extension is supported on VSX3000/7000/8000, V500, and FX endpoints. IP## EQNID##NID is supported on VSX3000/7000/8000, V500, FX, and PVX endpoints. IP to ISDN Gateway Call (without Gatekeeper) On a network without a Gatekeeper, you can use the following IP to ISDN sting to dial-in to the MCU: IP address of H.323 card##gateway prefix*isdn number of remote ISDN endpoint. For example ( ##63* ). 37

42 MGC Release Notes - Version 7.5 SIP Factory Detailed Description SIP Factory is a new conferencing entity that enables SIP endpoints to create an arbitrary number of ad hoc conferences and automatically connect to the new conferences. When the Sip Factory is created, using SIP call control means, a globally routed Conference Factory URI can be allocated and published. When a SIP endpoint calls this URI, and the call is established successfully, a new conference is automatically created and the endpoint joins the conference. The conference automatically ends when the conference creator leaves the conference. All other participants are invited to the conference using the SIP REFER method. To create a SIP Factory: A conference Profile must be defined in the MCU before creating a SIP Factory. The Profile should be set to Auto Terminate when the Chairperson exits the conference. 1. Expand the MCU tree. 2. Right-click the Meeting Rooms, Entry Queues & SIP Factories icon and then click New SIP Factory. The SIP Factory dialog box opens. 3. Define the following parameters: Name - Enter the SIP Factory Name. This is the name that will be used as part of the URI (together with the domain name) dialed by the SIP endpoint to initiate the conference. 38

43 Detailed Description - General Profile - select the conference Profile from the list of Profiles defined in the MCU. The new conference will be created using the parameters defined in the Profile. Automatic Connection - Select this check box to immediately accept the conference creator endpoint to the conference. If cleared, the endpoint will be redirected to the conference and then connected. 4. Click OK. The New SIP Factory is added to the list. Enabling the Registration of the SIP Factories with the SIP Proxy: The SIP Factory URI must be registered with the SIP server to enable routing of calls to the SIP Factory. To register the SIP Factory, the registration option must be enabled in the IP Network Service - SIP dialog box. In the Register section, select Entry Queues & SIP Factories. Connecting to the SIP Factory The conference initiator dials the SIP Factory URI and connects to an Ad-hoc conference. 39

44 MGC Release Notes - Version 7.5 Nortel Environment Flag Settings 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, the following system.cfg flags may be set: IGNORE_STREAM_VIOLATION in the IP MISC FLAGS section Set this flag to YES, to connect the video channel of Nortel endpoints that send video at a line rate higher than the rate declared in the capabilities exchange. When set to NO, these endpoints will connect as Secondary. SIP_USER_AGENT_FLOW_CONTROL_RATE in the SIP section. Set this flag to the following values: 8,64,128,256,384,512,768. This flag indicates the line rates that should be requested from the Nortel endpoints to prevent video overflow (default values are: 64,128,192,256,384,512,768). If you have set the flow control rate to Nortel mode but your environment includes also Polycom endpoints that do not exceed the declared line rate and therefore should not be requested to send lower video rates, define the following flag to exclude them from the flow control mode: In the SIP section set the flag SIP_USER_AGENT_FLOW_CONTROL to POLYCOM. 40

45 Detailed Description - General MGC+ Predefined IP only Entry Queues and Meeting Rooms The MGC+ unit is shipped with two pre-defined IP Only Entry Queues and eight predefined Meeting Rooms as follows: Entry Queue CP whose Numeric ID is 1111, and Video Session type is Continuous Presence, is used to access Meeting Rooms 1000, 2000, 3000 and Entry Queue VSW whose Numeric ID is 2222, and Video Session type is Video Switching, is used to access Meeting Rooms 5000, 6000, 7000 and The Entry Queues and Meeting Rooms are set to line rate of 384 Kbps. Meeting Rooms 1000, 2000, 3000 and 4000 are set to Continuos Presence mode. Meeting Rooms 5000, 6000, 7000 and 8000 are set to Video Switching mode. Meeting Room names and Numeric IDs are identical. For example, Meeting Room 3000 has the Numeric ID The Network Configuration wizard, which is activated when the MCU is installed in the site for the first time, enables you to reconfigure the IP Address of the IP cards, the IP address of the network entities and the default IP Network Service Prefix. To use the default Entry Queues and Meeting Rooms without modifying them, define the prefix as 789. Two Entry Queue Services (one per Entry Queue) and one default IVR Service are also shipped with the system. When accessing an Entry Queue, the system displays a video slide indicating the numeric IDs of the predefined Meeting Rooms that can be accessed from this Entry Queue. Figure 2: Entry Queue Video Slide 41

46 MGC Release Notes - Version 7.5 When joining a Meeting Room, the system displays a video slide indicating the operations that can be performed from the participant s endpoint and the DTMF code that must be used to activate each operation. Figure 3: Meeting Room Video Slide 42

47 Corrections, Pending Issues and Limitations Corrections, Pending Issues and Limitations Corrections between Versions V and V.7.5 Table 3: Corrections between Versions V and V.7.5 #. Category Description ID# Remarks 1. Audio+ In an Encrypted VS conference with 96 Dial-out and 96 Dial-in participants, the Audio+ cards crashed. 2. Cascade Video Switching, H.261 Fixed, 384Kbps and H239/P+C defined conferences may suffer from bad video quality. 3. CP In a CP conference with a PSTN participant, the speaker indication disappears. 4. General When the MGC Manager uses port 80 to connect to the MGC unit, the MGC Manager may disconnect from the MGC unit (Bad connection status). 5. H.239 When sending Content from two endpoints at the same time (within the same second), one endpoint will not be able to send Content again. 6. H.239 Connecting 12 H.239 participants to an MG323 board causes the card to crash. 7. Meeting Rooms When a conference is defined as a Meeting Room, it takes over two minutes to receive any indication from MGC Manager. 8. MGC Manager Endpoints appear as faulty connected during the first seconds of connection. 9. Microsoft During an On Going conference participants from a previous conference are listed. 10. MPI When upgrading the MCU software from version 6.xx to version 7.0.X, on an MCU with two MPI cards, an exception may occur

48 MGC Release Notes - Version 7.5 Corrections between Versions V and V Table 4: Corrections between Versions V and V #. Category Description ID# Remarks 1. Audio On an MCU with simultaneous conferences, audio can be heard from another conference. 2. Audio When many participants are detected as having a Noisy Line, other participants cannot connect to the Audio+ card. 3. Cascade In Cascaded Video Switching conferences with a leased line link inconsistent switching between speaker and participants can occur. 4. Cascade In an ISDN Master-Slave cascading conference, if participants are connected to the conference before connecting the links between the conferences, the site names disappear after the speaker changes. 5. Cascade In an ISDN Master-Slave cascading conference, if participants are connected to the conference before connecting the links between the conferences, it takes about a minute for a Tandberg endpoint to become the speaker Connect first the Cascading link Cisco IP Phone endpoint No Audio or Video when using Cisco IP phone CP In a H.264 conference, ipower set to a desktop mode causes video fragmentation. 8. CP During a CP conference participants with long names disconnect. 9. CP In a CP conference with 2x2 layout, video forcing is not implemented. 10. Encryption In Encrypted conferences no resources available for Encrypted participants allocated on IP+ cards with HW version External db After resetting the server, the MCU stays in Major when there is an external Database connection. 12. Falcon Falcon diagnostics cannot be used to test Audio+ cards

49 Corrections, Pending Issues and Limitations Table 4: Corrections between Versions V and V #. Category Description ID# Remarks 13. Falcon The Falcon application crashes after downloading diagnostic traces on the MGC Falcon No Falcon diagnostics available on Video+ cards. 15. General When the MCU is extremely loaded, conferences may terminate before their scheduled time (XPEK operating system only) 16. General PictureTel Legacy endpoint cannot connect to On Going conferences. In the system.cfg, General section a new flag: TRADITIONAL_END_POINTS_MODE =NO has been added (default). Set this flag to YES, when using older PictureTel endpoints. 17. General In the Participants Queue the operator cannot attend the next participant. The message "No Party in Participants Queue" appears. 18. General Version default password and connectivity issues when upgrading: V.5 to V.6 & V.5 to V General When an operator joins the conference, the conference terminates. 20. H.239 In an IP conference Sony endpoints do not open the Content channel. 21. H.239 After sending content in ISDN, the H.239 channel does not open. 22. H.239 Slave conferences cannot receive content from the Master conference on the MGC IP Alias names for IP participants increased to 100 characters. 24. IVR When connecting a defined dial-out participant to a Meet Me Per conference with IVR that all its options are enabled, and the participant is first to connect, the participant hears the voice message (you are the first participant to connect), but does not hear the music that should follow the message Set the system.cfg flag to YES

50 MGC Release Notes - Version 7.5 Table 4: Corrections between Versions V and V #. Category Description ID# Remarks 25. MGC Manager When using MCU port 5001, conference names are not displayed in the IP card properties. 26. MGC-25 When using the Fast Configuration Wizard, the MGC Manager crashes while configuring the ISDN Network Service. 27. MPI Synchronization improvements on the RTS signal. 28. MPI An MPI endpoint connected as Direct appear as dial-in the MGC Manager. 29. MUX+ Connecting more than 15 ISDN H.239 VSX endpoints to a conference may cause the MUX+40 card to crash. 30. SIP During an Invite session the Session Description Protocol mutes the audio of the participant. 31. SIP When dialing-in to an On Going conference the IP+48 card crashes. 32. T1-CAS An exception occurs after a T1-CAS participant dial-in (Audio Only). 33. T1-CAS During Audio Only conferences T1-CAS dial-out participants cannot connect. 34. Video When moving a video muted participant, the participant is automatically unmuted after the move to the new conference

51 Corrections, Pending Issues and Limitations Corrections between Versions V.7.0 and V Table 5: Corrections between Versions V.7.0 and V #. Category Description ID# Remarks 1. Ad Hoc conferencing During an Ad Hoc conference, when the chairperson presses DTMF code *3 to invite a PSTN invitee, an Assert occurs on the system Audio+ After 40 cycles of starting and terminating a conference that includes many participants, the Audio+96 card may crash. 3. Cascading Error messages are displayed when cascading conferences run on MGC MCU and Tandberg MCU. 4. Cascading Occasionally, the IP+12 card crashes when IP participants connect to a cascading P+C/H.239 conference for longer than two hours. 5. Cascading Asserts may occur when connecting cascading conferences in H COP In a conference set to H.264, when endpoints connect the frame rate decreases. 7. COP In a CoP conference disconnecting a participant, video loss (Video Out 0) to all conference participants may occur. 8. CP In a H.263 conference, after changing layouts of participants and speaker no outgoing video stream is sent. 9. CP A H.263, FECC conference with a line rate set to 786Kb may have a fragmentary video. 10. CP With H.264 and XGA Video Format conference settings, the video+ card may crash. 11. CP In an H.263 conference, after changing layouts of participants and speaker the Video card may crash. 12. CP In a large Continuous Presence conference where the participants reside on more than one video card, the video layout background screen flashes (blue screen effect) when there is an exchange of speakers between the two video cards This is an endpoint issue and not the MCU s

52 MGC Release Notes - Version 7.5 Table 5: Corrections between Versions V.7.0 and V #. Category Description ID# Remarks 13. H.323 An exception may occur when connecting more than 96 H.323 participants in a blast dial-out conference Lecture Mode - CP conference 15. Lecture Mode - CP conference Incorrect speaker is displayed when the first participant that connects to the CP conference set to Lecture Mode, running on the Standard Video card, is muted and the second participant is unmuted. The first participant remains the speaker although second participant should have been selected as the speaker. No video when connecting a single participant to a CP conference set to Lecture Mode, running on the Standard Video card, and the selected layout is other than full screen MGC Manager When creating a new Network Service, after adding 10 different Spans, the 17. MGC Manager In the MGC Manager monitoring pane refresh problems may cause wrong endpoint status. 18. MGC Manager No 'Faulty connection' indication in the MGC Manager application. 19. Video A blue screen is displayed for seconds when the speaker changes in a conference with more than 10 participants in Classic or Quad Views CP conference running on the Video+ card. 20. Video Conferences with 4CIF or higher Video Formats may encountered brief video interruptions. 21. Video VSX endpoint connect as Secondary (audio only) when connecting via ISDN to a VSW conference set to Auto mode, as the endpoint uses encryption for the connection This is an endpoint issue and not the MCU s. 22. Video Switching In a conference set to 256Kb line rate, connecting and disconnecting ISDN endpoints cause the MUX+ card to crash XGA In a IP conference with the Video Format set to XGA, errors could occur when sending content. 24. XPEK In certain instances the MCU does not accept valid IP addresses

53 Corrections, Pending Issues and Limitations Version 7.5 Pending Issues Table 6: Pending Issues #. Category Description ID# Remarks 1. Audio When using the G.729 audio algorithm, no audio available with VoIP or SIP phones Cascade In an ISDN Master-Slave cascading conferences, if participants are connected to the conference before connecting the links between the conferences using blast dial-out, morphing occurs on some endpoints during the connection process. 3. Cascade In Cascaded Video Switching conferences with an ISDN link, FECC occasionally does not work. 4. Content All the participants Status becomes Faulty Connected when PVX endpoints send Content. 5. COP When the first active participant is disconnected and the video of other participants is muted, participants view background colors. 6. CP MCU status changes to Major for 30 seconds when connecting 32 endpoints at a line rate of E1 to a CP conference. 7. CP In a CP Quad Views conference with more than 12 H.264 participants, the frame rate may decrease. 8. CP Fragmented Video can occur during speaker changes in CP H.264 conferences. 9. Database In the Participants database, when you Copy As a participant template and then modify this template without prior pasting the copied template, the system forces you to save the original template under a different name. 10. Encryption In a Video Switching encrypted conference with more than 75 participants and set to a 768KB line rate, the Audio+ card may crash Save the participant under a new name, and then, if required, delete it from the database Falcon Diagnostic Tool 12. Falcon Diagnostic Tool Long loop test may fail when running the diagnostic on the MGC-25 Falcon diagnostics sometimes cannot connect to the cards

54 MGC Release Notes - Version 7.5 Table 6: Pending Issues (Continued) #. Category Description ID# Remarks 13. FECC FECC does not work between an IP endpoint and an MPI (DTE) endpoint. 14. FTP FTP service on XPEK may stop working, which affects system functions, such as prevent the Logger Diagnostic Files from opening, causing the MGC Manager application to close In the IP Terminal, enter restore_ftp. If the system displays an indication that the ftp cannot be restored, reset the MCU. If MCU reset is not applicable, call support. 15. Gatekeeper CON Gatekeeper CON (Conference On Demand) does not work with the MGC-25. With the MGC-50/MGC-100/ MGC+ it works with asserts Gateway When connecting conferences using the Gateway when you move a participant to and from a conference, no video is seen. 17. Gateway When calling from H323 endpoint to an EQ placed on MGC V6 (used as an MCU) through MGC V7 (used as GW H323->H320), the call will fail. 18. General When moving a participant from one conference to another, the First to join IVR message is heard twice. 19. General The 'Auto_Redial' parameters in 'confer.cfg' file are not updated. 20. General Creating a conference with parameters "enable invite" and "encryption", the invitees are rejected. 21. General SilenceIT algorithm does not automatically mute participants placing their line on hold, hence background music is played to the conference. 22. H.264 In Video Switching conference set to H.264 and a line rate of 384Kbps, Sony endpoints connect as secondary. 23. H.323 Connecting a service to a card during card download card results in card failure Require MCU restart in order for changes to take effect Connect the service after software download is completed. 50

55 Corrections, Pending Issues and Limitations Table 6: Pending Issues (Continued) #. Category Description ID# Remarks 24. ISDN After upgrade to version 7.5, the MCU loses the ISDN clock source configuration. In Faults file there is no message about NO CLOCK SOURCE. 25. ISDN ISDN endpoints fail to move to Video Switching conference when the line rate of the destination conference is higher then the line rate at the initial conference. 26. IP+ In a mixed system with ISDN and IP, when the clock is set to ISDN and you set the source of the ISDN span to Null, the IP+ card may stop responding. 27. IP+ After participants disconnect from a conference, the LED on the card is still On (Active). 28. IPower IPower fails to send content in a CP conference set to Auto, H.239 P+C and dial out. 29. MGC Manager In the H.245 Properties dialog box, when H.239 is used, P+C is indicated instead. 30. MGC Manager Wrong indication in the MGC Manager when Moving IP endpoints from one Video Switching 384 Kbps to a Video Switching 512 Kbps conference, the participant appears connected when they should say secondary. 31. MGC Manager On an XPEK MCU, when extreme packet loss occurs, the MGC Manager can loose connection with the MCU. 32. MGC-25 The Resource Report does not display IP capacities for line rates of 256 Kbps and 512 Kbps. 33. MGC-25 Moving 3 IP participants from CP Quad View to a CP COP Quad View conference fails on the MGC MUX When an undefined ISDN participant connects to a CP conference using a lower rate than the conference, the call is rejected. Other endpoints are unable to connect Reconfigure the ISDN clock Set the system.cfg (MCU_CLOCKING section) flag: INTERNAL_CLOCK = YES prior to setting the ISDN span to Null Move participants one at a time

56 MGC Release Notes - Version 7.5 Table 6: Pending Issues (Continued) #. Category Description ID# Remarks 35. NTP When the MCU connects to the NTP server for a time calibration, connection problems occur and 15 hour time deviations result on the MCU. 36. On-line Help On-line help is not updated in version 7.0.X. 37. PSOS When sending files to the MCU, the MCU displays a Bad Connection status indication. When the download is completed the status indication reverts to Normal. 38. PSOS The Backup and Restore processes take more than 20 minutes to complete. 39. PVX During MCU dialout, the PVX endpoint connects as Secondary when the dial out call is set to H.263 and the endpoint VGA Encoding is enabled. 40. SIP An IP Video Switching conference set to 256Kb with many SIP participants may crash the IP+ card. 41. SIP After a SIP connection failure, deleting SIP participants from the conference fails. 42. SIP When changing the Refresh SIP registration in the IP Service to 10 seconds, the LCS proxy rejects the MGC and registration fails. 43. SIP LCS proxy does not work with Automatic SIP-Factory settings. 44. SSL The MCU occasionally disconnects from MGC manager when using a secured port (port SSL). 45. SNMP SNMP MIB2 sections: interfaces, at, ip, icmp, tcp, udp, egp transmission are not supported in XPEK. 46. T1-CAS T1-CAS is not supported on the MGC T-120 During the creation of a T-120 conference an error may occur. 48. Video+ When changing the video protocol of a conference from H.264 to H.263 long delays in the video occur Set the Refresh SIP Registration to more than 10 seconds In the LCS proxy, define static-route rules using IP board (format: *@IPAddress) Reconnect to the MCU

57 Corrections, Pending Issues and Limitations Table 6: Pending Issues (Continued) #. Category Description ID# Remarks 49. Video Switching 50. Video Switching In a Video Switching conference when the speaker changes, all ISDN parties accumulate R-Synch Video Loss and are indicated as Faulty in MGC Manager. On average Video is impaired for 1 second. During the start of Video Switching conference, poor video can appear for several seconds VoIP In a CP conference with VoIP phones, the Audio+ card can crash when using the G.729 Audio Algorithm VTX1000 For future use. 53. XP In XP installations, the Setup is halted when the Logger file is full. 54. XP After upgrading the MGC Manager to version 7.5, the MCU s re-start takes longer (up to 2 additional minutes). This is due to the Microsoft new service pack synchronizing with the MCU s software Clean the logger file before installation

58 MGC Release Notes - Version 7.5 Version 7.5 System Limitations Table 7: System Limitations No. Category Description ID# Workaround/ Remarks 1. Ad Hoc conferencing Assigning an Audio Only Profile to a video Ad Hoc-enabled Entry Queue causes errors AES In encrypted Video Switching conference, ISDN parties cannot be encrypted. 3. API When changing of the maximum number of participants during a conference, sudden shutdowns can occur in the MCU (MCMS) when working with incompatible MCU - MGC Manager software versions. The problem is caused because memory allocation is done according to the maximum number of parties. Specifically for voice participants: Version Version Version 4.6x Version 5.0x For example, when working with MGC Manager version 5.0x which allows up to 100 video switching participants in a conference with MCU version 4.0x which can only run 30 participants in a conference Use the appropriate MGC Manager version to manage the MCU. 4. Audio Only conferences When you copy an audio only participant, terminate the conference and then Paste as" to another audio only conference which includes a participant with an assigned dial-in number, instead of using the next dial-in number from the network service's configured range, a message is displayed indicating that the number is occupied Assign the dial-in numbers manually. 5. Audio+ In some conferences, the first participant hears a faint clicking sound when the second participant interacts with the IVR Service. 6. Audio+ After swapping an Audio+ card (removing an existing one and inserting another in the same slot) the IVR prompts are not loaded to the new Audio+ card Insert the Audio+ card into another slot or remove and restore the card. 54

59 Corrections, Pending Issues and Limitations Table 7: System Limitations (Continued) No. Category Description ID# Workaround/ Remarks 7. Audio+ 'The "Reserved" and "Active" columns of the Audio+ Resource Report show wrong port numbers. 8. Audio+8 Audio+8 card does not support participants using T1-CAS lines and G.729 endpoints. 9. Cascade The speaker is assigned a wrong site name when cascading Continuous Presence and Video Switching conferences The columns "Non reserved" and "Total" show the right number of ports Cascade No Cascade in CP Quad conferences Cascade Cascading is not available for Software CP conferences. 12. CDR Low Memory alert may appear on screen when retrieving large (megabyte and larger) CDR files Circular mode 14. Circular mode 15. Circular mode After the conference start, different resources are used than those allocated during the conference reservation. Creating a new ISDN service while a conference is running will disable the option to add another participant to the existing conference. Moving participants from one conference to another and terminating the original conference result in resources reallocation Create a new conference CP In a Continuous Presence conference set to Same Layout, in the Click&View application the Personal Layout option is enabled although this option is not applicable to the Same Layout mode. 17. CP In a CP conference, the speaker position in the CP layout window is not maintained when the layout is changed back and forth. 18. CP In a conference set to H.264 CIF, when the Exclusive Speaker is changed the Video Protocol also changes to H CP With an endpoint set to Personal Layout, when a Video parameter is altered, the video layout changes automatically to Conference Layout

60 MGC Release Notes - Version 7.5 Table 7: System Limitations (Continued) No. Category Description ID# Workaround/ Remarks 20. CP FX cannot handle two H.264 calls simultaneously. H.264 calls to the FX endpoint may witness video blocking, disconnections and audio only connections. 21. Content Refresh rate of the content is slow when using VSX7000 and VSX8000 endpoints. 22. COP In Conference on Port, Lecture Show is disabled. 23. COP In COP conferences, when the chairperson enters the conference with Click&View, all other participants see the Click&View slide instead of the conference video. 24. COP When moving participants back and forth between two COP conferences the video may need to be manually refreshed due to bad video synchronization. 25. COP Occasionally, when using the option of Noisy Line Detection, the speaker indication does not indicate the current speaker. 26. DB Manager When two operators are saving modifications in the Access DB with the same reservation, the second (slower) operator will get an error message when reading from DB Connect the chairperson prior to the other participants Caused by MS Access limitations. Use SQL Server. 27. Double Gateway A local Gateway Session in the Remote GW Link window always uses the default profile. 28. Entry Queue If no IVR Service is assigned to an Audio Only conference, participants connecting to the conference via Entry Queue can access a locked On Going conference. 29. Entry Queue During Entry Queue definition, properties are taken from the IP Service. Once defined, you cannot delete or add an IP Service to the Entry Queue. 30. FECC FECC functionality problems in a Continuous Presence conference when Exclusive Speaker mode is active Delete the Entry Queue and redefine it DevTrack

61 Corrections, Pending Issues and Limitations Table 7: System Limitations (Continued) No. Category Description ID# Workaround/ Remarks 31. FECC Only the endpoint displayed in the layout s upper left window can be controlled by the far end camera. 32. FECC When trying to move a remote camera using FECC before the video is received may cause more than one camera to move. 33. Gateway When the MGC unit is used as a gateway and one endpoint is used as an MCU for multipoint connection, if the connection has started with video protocol H.264, other participants using video protocol other than H.264 cannot connect to the endpoint-mcu. 34. Gateway When the MGC unit is used as a gateway and one endpoint is used as an MCU for multipoint connection, using FECC or H.239, may cause the MCU endpoint to display only one participant (as in a standard gateway session). 35. General When removing cards from the MCU while on-going conferences with dial-in participants are running, asserts and ports deficiencies may occur. 36. General When a cellular phone disconnects from a conference, the disconnection is not immediately known to the conference and a busy tone may be heard by all of the remaining participants. 37. General A dial-out "auto detect" telephone cannot be connected to the conference (the option is blocked). 38. General Maximum number of participants in a single conference template is General Cannot move participants between Reservations using drag & drop. 40. General When the properties of an On Going conference are changed, and the MCU is reset, the initial conference properties are restored on the MCU. 41. General Participants moved between conferences may be listed in both conferences Set the gateway call to H.263 or set the system.cfg flag GW_H264 to NO (default) Disable the FECC and H.239 options for the gateway call or set the system.cfg flags: GW_EPC_H239 and FECC_GW to NO The MGC does not receive a disconnection signal form the handset In an Audio Only conference, create a pre-defined participant

62 MGC Release Notes - Version 7.5 Table 7: System Limitations (Continued) No. Category Description ID# Workaround/ Remarks 42. General MCU software installation must be performed from a mapped location (X:\...) and not from a network location using Windows My Network Places. 43. General When a defined dial-in participant is moved to the Operator conference with Attend with details, and is disconnected, the Attended Participant window cannot be closed and the participant disappears from the conference (as an undefined participant). 44. General Long backup time (more than 15 minutes) for reservations (in XPEK only). 45. General When the participant name has been changed and you add a new participant using the first participant s former name a message STATUS PARTY NAME EXISTS appears. 46. General When definiting Network Services, the Apply button is disabled. 47. General When an Entry Queue accessed Meeting Room is active you cannot change the password. 48. General When you open the LAN.cfg with Notepad application, the file s content is listed in a single string. Editing the file may result in an MCMS crash. 49. H.264 In the H.264 Quad View mode endpoints do not connect in H H.264 IP Participants are connected as Secondary when moved from a CP/ H.264 conference to a CP COP/H.264 conference, running at a different line rate. 51. H.323 In H.323 Fixed Ports mode - although only two ports are allocated to audio and two ports to video, defining a range of two consecutive ports for each will result in an error message indicating ports overlap. 52. Interop After moving a participant with a Tandberg endpoint to a conference without H.263 annexes the endpoint remains secondary and Use the OK button Open the LAN.cfg file with WordPad and only change the MCU s IP address Define the range leaving a 2-port gap

63 Corrections, Pending Issues and Limitations Table 7: System Limitations (Continued) No. Category Description ID# Workaround/ Remarks 53. IP When entering an empty space in the Alias field in the Participant Properties call failure may occur. 54. IP When you delete an IP Network Service on the MCU, the Card s properties still appear as registered in PathNavigator. 55. ISDN When two different ISDN Network Services are used for two Meet Me or Meeting Room conferences, and one dial-in number is contained in the other, dial-in undefined participants may be connected to the wrong conference. For example, if one Network Service allocates the dial-in number 397, and the second allocates the number 8397, participants dialing 8397 will be connected to the conference assigned the number IVR Faint clicks may be heard when participants are using DTMF codes. 57. IVR The number of IVR Services defined for a single MGC unit may not exceed 30 Services. When this number is exceeded it causes high CPU usage Dial-in numbers allocated to all ISDN Services of a MCU should be of the same length

64 MGC Release Notes - Version 7.5 Table 7: System Limitations (Continued) No. Category Description ID# Workaround/ Remarks 58. IVR The DTMF Help file LdrHlp3 contains prompts that are not played by the Help file menu. These prompts are: To mute dial-in participants when connecting to the conference, press star, eight, six To cancel the automatic muting of dial-in participants, press pound eight, six To ask a question, press star, two, two To cancel your question, press pound, two, two To let the next participant in line to ask the question, press star, two, three To end the current question, press pound, two, three To cancel all questions press star, two, four To enable the roll call, press star, three, two To disable the roll call, press pound, three, two To start dialing to predefined dial-out participants, press star, two, five To end the conference, press star, eight, seven" 59. IVR Passwords are automatically allocated by the system only if the flag QUICK LOGIN = YES and the conference is defined as Entry Queue Access. 60. IVR When selecting the Roll Call check box in the conference Properties - Settings dialog box, the selection is revoked when displaying another Properties tab. 61. Lecture Mode In a Lecture Mode conference, when the lecturer connects while all the conference participants are muted, the conference acquires the attributes of a regular conference Select the Roll Call check box at the end of the conference definition process MGC Manager After an operator logs onto the MGC Manager to an MCU not using the Create Log-in mechanism and then logs out, another person can use his computer to log-on and save a new password

65 Corrections, Pending Issues and Limitations Table 7: System Limitations (Continued) No. Category Description ID# Workaround/ Remarks 63. MGC Manager 64. MGC Manager When defining a new Operator, the MCU must be reset before the new operator can perform any FTP operation (such as sending a file to the MCU). Cards may change to "Major" status when MCU software is downloaded untill the download process is complete MGC-25 After upgrading the MGC-25 card configuration file from IP12 to Unified24, the following major error code appears in the Faults file: INCONSISTENT_INFORMATION_IN_FILE File Type: CARDS CONFIGURATION FILE: cards. 66. MGC-25 An exception occurs when performing update card while a conference is starting and the MGC-25 must be restarted. 67. MGC-25 After changing the span of the Net card the MGC-25 must be restarted. 68. MGC-25 Problems occur when connecting a mouse to the MGC MUX At the end of unit reset, after one minute, the MUX card status changes to Major and the card must be reset. 70. MUX / ISDN The maximum number of ISDN participants in an H.239 conference is Functionality is OK. The limitation is the appearance of the error message Reset the card to continue working People and Content V0 When using Content, the number of supported participants per H.323 network card may decrease as follows: MG323 board - 10 instead of 12 IP24 board - 20 instead of 24 Resources should be manually allocated to the additional participants (11-12 and 21 to 24) using the IP address of the appropriate card. 72. Pro-Motion An H.320 participant connecting to a conference defined as Pro-Motion (NTSC) and line rate of 384 Kbps may connect as Secondary. 73. PSOS The starting time of the first reservation after winter daylight saving time change, is shifted by one hour Disconnecting and reconnecting this participant can solve the problem

66 MGC Release Notes - Version 7.5 Table 7: System Limitations (Continued) No. Category Description ID# Workaround/ Remarks 74. Roll Call When Roll Call is in use and a participant is disconnected, there is a delay until the MGC Manager indicates the disconnection. 75. Roll Call Roll Call is not supported when moving a participant from one conference to another or from the Operator conference to the Home Conference. Roll Call is also not supported in an Invite session SIP Cascaded SIP links cannot be allocated to the same IP+ card. 77. SIP If the VSX endpoint is registered to the SIP Proxy,you cannot dial-out from the endpoint to conference on the MCU. This scenario fails even when the conference is registered to the proxy. 78. SIP In a SIP environment asymmetric Payload Type is not supported. (Incoming and outgoing channels use different payload type numbers in the header of the RTP packets). By setting the flag VIDEO_DRAFT=4 MGC uses static Payload Type and forces the end point to symmetric mode. (When flag is VIDEO_DRAFT=5 MGC uses Dynamic Payload Type) 79. SIP Windows Messenger cannot get TCP call from IPTEL proxy. 80. SIP SIP endpoints connect as Secondary (audio only) in the following Video Session settings: Software CP CP COP (Conference on Port) CP - Quad Views Video Switching - Highest Common mechanism (video parameters must be set to fixed mode) Cascade on two different cards Dialout using the SIP proxy

67 Corrections, Pending Issues and Limitations Table 7: System Limitations (Continued) No. Category Description ID# Workaround/ Remarks 81. SIP The following video settings are not supported with SIP connections: FECC - video endpoints connect without FECC option H SIP video endpoints connect as H.263 to CP conferences and as Secondary in VSW conferences H.239/People+Content - SIP video endpoints can only see the video channel and not the Content channel H.263+ Annexes 82. SIP Encryption is not supported with SIP endpoints, therefore cannot connect to an encrypted conference. 83. SIP T.120 is not supported with SIP endpoints, hence, the video endpoints connect without T SIP Participant RTP/RTCP monitoring is unavailable for SIP endpoints. 85. SIP Gateway calls are not supported with SIP endpoints. 86. Software CP The Welcome Slide does not appear when a participant connects to a Software CP conference. 87. T-120 The H.323 card causes an assert when deleting a participant or terminating a T-120 conference. 88. T1-CAS Incorrect CLI s are assigned to undefined T1-CAS participants. 89. T1-CAS Connecting and disconnecting T1-CAS participants can prevent the transfer of DTMF codes from the remaining T1-CAS participants to the MCU. 90. VCON When an ISDN participant connects to a Video Switching (Auto or H.263) conference the endpoint disconnects. 91. Video Video card units may fail when terminating large CP conferences before all the participants have disconnected from the conference & Set the conference to G First disconnect the endpoints and then terminate the conference. 63

68 MGC Release Notes - Version 7.5 Table 7: System Limitations (Continued) No. Category Description ID# Workaround/ Remarks 92. Video When resetting the video units quickly (one after the other), the video card status changes to Major. 93. Video Video force settings are not saved after interactively (Drag & Drop) moving a participant from an Operator conference to the Home conference. 94. Video On QCIF endpoints the supported layouts are up to 3x3 only (not 4x4 for instance). Wait a few seconds for the board to change to Normal, and then reset the next unit Video Switching 96. Video Switching 97. Video Switching When moving an endpoint that supports H.261, H.263 and H.264 from a Video Switching conference set to H.261 to a Video Switching conference set to H.263 or H.264 it connects as Secondary. When disconnecting and reconnecting the endpoint it still connects as Secondary. When an FX endpoint connects to a conference set to 4CIF & 15 fps and if the conference video format changes to CIF or QCIF, the MCU connects the endpoint at 15 fps, although it should have connected the endpoint at 30 fps. A Video Switching conference reservation with 4CIF Video Format and 15 fps Frame rate settings, the conference starts with CIF - 30 fps settings and Video+ When changing the default layouts for Auto Layout in the confer.cfg file, the Auto Layout is activated only after the fourth participant connects to the conference. 99. Video+ Up to 128 participants can be connected to a single Video+ card Video+ During a video conference with XGA Content, when there is a speaker switch, a delay of 6-10 seconds occurs before the video feed changes to the new speaker VTX1000 The VTX1000 check box function included with MGC Manager version 7.5, will only be available in later versions. 64

69 Appendix A - Falcon Diagnostic Tool Appendix A - Falcon Diagnostic Tool The Falcon diagnostic tool is an add-on to the MGC application that enables you to run diagnostic tests on the hardware and software of the MGC-25, MGC-50 and the MGC-100 units. Detailed Description The Falcon diagnostic tool is used by used by Polycom support personnel or the customer's System Administrator to provide data for checking the hardware performance. When running the Falcon Diagnostic tool, it is best to run all the available tests on each applicable card to locate any problem in the hardware. If a fault is discovered, it should be reported to Polycom support personnel. More specific diagnostic tests can then be run on the units. The Falcon diagnostic tool runs diagnostic tests on the following cards on: MGC+50/MGC+100/MGC-50/MGC-100: The Audio+ cards The Video+ cards The IP+ cards MUX+ cards MGC-25: The Audio+ card The Video+ cards The IPN card On the MGC-25 unit, the IPN card can be configured as a virtual NET-2, IP+ and MUX+ cards. The Falcon diagnostic tool displays the NET-2 and the two processors (IP+ and MUX+) as IPN card units. The Audio+ and Video+ cards are displayed in the diagnostic tool as they are actually installed. These parameters can be viewed in the card Properties - Card Settings dialog box. 65

70 MGC Release Notes - Version 7.5 Test Description The following table lists the diagnostic tests performed, by card and unit. The tests differ depending on the selected card and unit. For a description of the terms that appear in the table, see Test Glossary on page Table 8: Diagnostic Tests Card Unit Test Description IP+ (MGC-50, MGC-100) CM Local memory Checks buses data and addresses. Checks memory integrity and capacity. Proc Clock Checks the frequency of the processor. Local memory Neighbor Clock LAN TDM Full memory Checks buses data and addresses. Checks memory integrity and capacity. Checks the PCI access between processors. Checks the frequency of the processor. This test requires that a LAN cable be connected to the I/O of the card. See Connecting the ISDN Loopback and LAN cables on page 75. Checks the ping between the card and the Falcon host machine IP Address. Creates a loop between the DSP through the backplane and back to the DSP to check data transfer through the loop. Checks all the processing memory of the card manager. 66

71 Appendix A - Falcon Diagnostic Tool Table 8: Diagnostic Tests Card Unit Test Description IPN (MGC-25 only) NET-2 ISDN-Loopbac k The Falcon diagnostic tool displays the NET-2 card as a unit in the IPN card. This test checks the ISDN hardware. To run this test, an ISDN Loopback cable must be connected to the Network I/O card. For more details, see Connecting the ISDN Loopback and LAN cables on page 75. Proc Clock Checks the frequency of the processor Local memory Neighbor LAN TDM Full memory Checks buses data and addresses. Checks memory integrity and capacity. Checks the PCI access between processors. This test requires that a LAN cable be connected to the I/O of the card. See Connecting the ISDN Loopback and LAN cables on page 75. Checks the ping between the card and the Falcon host machine IP Address. Creates a loop between the DSP through the backplane and back to the DSP to check data transfer through the loop. Checks all the processing memory of the card manager. 67

72 MGC Release Notes - Version 7.5 Table 8: Diagnostic Tests Card Unit Test Description MUX+ CM Local memory Checks buses data and addresses. Checks memory integrity and capacity. LAN Checks the ping between the card and the Falcon host machine IP Address. Proc Local memory Checks buses data and addresses. Checks memory integrity and capacity. Full memory Neighbor Clock TDM Checks all the processing memory from the card manager. Checks the PCI access between processors. Checks the frequency rate of the processor. Creates a loop between the DSP through the backplane and back to the DSP to check data transfer through the loop. Audio+ CM PCI Scans the PCI to ensure that its components are working properly. TDM QIFI Memory Creates a loop between the DSP through the backplane and the QIFI then back to the DSP via the time slot switch to check data transfer through the loop. Checks the H-sync and F-sync clocks. Checks buses data and addresses. Checks memory integrity and capacity. Proc Clock Checks the frequency of the processor. Memory Checks buses data and addresses. Checks memory integrity and capacity. Checks burst and data bus energy changes. 68

73 Appendix A - Falcon Diagnostic Tool Table 8: Diagnostic Tests Card Unit Test Description Video+ CM PCI Scans the PCI to ensure that its components are working properly. Memory TDM BCOD Checks buses data and addresses. Checks memory integrity and capacity. Creates a loop between the DSP through the backplane and the BCOD then back to the DSP via the time slot switch to check data transfer through the loop. Checks the H-sync and F-sync clocks and BCOD memory. Proc Memory Checks buses data and addresses. Checks free memory. Clock Checks the frequency rate of the processor. MCU Level Tests When the Falcon diagnostic tool is run at the MCU level, all available tests are run on all the recognized cards installed on that MCU and their units. Several MCUs can be tested simultaneously, and their tests run serially. Card Level Tests When the Falcon diagnostic tool runs tests on an installed recognized card, it performs all the available tests on all the card s component units. You can test all cards of a certain type, for example, all the Video+ cards. All tests run on the Falcon diagnostics tool are run serially rather than simultaneously. Unit Level Tests At the unit level, tests can be selected individually. A specific test, for example, the TDM test, can be run on all cards installed on the MCU as long as each test is initiated individually. The tests run serially. 69

74 MGC Release Notes - Version 7.5 Starting the Falcon Diagnostic Tool The Falcon tool is part of the MGC Manager Options menu. To Start the Diagnostics Tool: 1. Terminate all On Going Conferences and cancel any soon to open Reservations on the MCUs to be tested. 2. In the Options menu, select Diagnostics tool. Falcon Main Window The Falcon diagnostics tool opens. The Falcon diagnostics tool displays all the MCUs currently defined in the MGC Manager, see Falcon Main Window on page You can define other MCUs so they can be displayed in the MGC Manager and in the Falcon tool. The MCU network is displayed in a Browser pane on the left side of the Falcon window. Test Modes available for running tests IP Test window. It is enabled when running the LAN test on an IP+ or IPN card. Main menu Browser pane Tests available for the selected element Displays the Test Results. Test columns change if test is run on an MCU unit or on a card. Detailed explanation of selected test results 70

75 Appendix A - Falcon Diagnostic Tool Browser Pane Displays the MCUs defined in the MGC Manager application. Each MCU tree can be expanded to display the cards supported for diagnostic tests. Main Menu The Main Menu includes the MCU, Log and Help menus. Table 9: Falcon Main Menu Description Field Description MCU Add MCU - To define a new MCU and add it to the MCU list. This option is required only for MCUs that are not currently defined in the MGC Manager application. Connect - Connects an MCU to the application. Disconnect - To disconnect an MCU from the Falcon diagnostic tool, and resets the MCU to normal mode. Reset MCU - To reset the MCU while remaining in the diagnostic mode. Remove MCU - This option removes the MCU from the MCU list. Properties - Lists the MCU properties: MCU Name, IP Address, Product Type (MGC-25/50/ 100), MCU Version, and the MCSM version. Log Help Contains the following options: Set Log File Path - Enables you to select the folder where the log file will be saved. Only Faults - Click this option to save only Faults in the Log file. Lists the following options: About Falcon - Lists the Falcon diagnostic tool version. Falcon Help - Provides On Line Help for the application. Test Options Box The Test Options box displays the modes for running tests. Table 10: Test Options Description Field Loop Test Stop on Failure Description Sets tests to repeat continuously in a loop mode. This provides continuous testing for these diagnostics. In this mode tests are run continuously until a failure is detected. The diagnostic testing then stops. Quick Test Enables running tests that do not run longer than 5 minutes. On the MGC-25, all tests run as they all take less than 5 minutes to run. 71

76 MGC Release Notes - Version 7.5 If no selection is made in the Test Options box, the tests will run one time. Test Selection The Test Selection box displays the tests that are available for the selected element. All - Selects all the diagnostic tests to run. Tests vary depending on the selected MCU component, for details, see Table 8 on page When the MCU icon or card icon is selected, all tests are run by default. When a card unit is selected, tests can be selected individually. Run button - Initiates the diagnostic tests that are selected. Stop button - Terminates on going diagnostic tests. IP Test Box The IP Test box is active during the LAN test. The IP Address, Subnet Mask and Default Gateway information must be entered. If these parameters are not entered, a pop-up box appears when the diagnostics run the LAN test, and these fields must be entered at that time. You can cancel the LAN test instead of entering the IP Test values. IP Address - This is the address of the card and should be provided by the System Administrator. Subnet Mask - This is provided by the System Administrator. Default Gateway - This is necessary to test the LAN Controller. Test Results Pane As the tests are run, the results are displayed in the Test Results table. A log report is written containing these results. The test categories depend on what tests are run. When the MCU icon is selected in the Browser pane, two terms are displayed: Card and Status. When the cards or units are selected, there are five terms displayed in this window: Table 11: Test Selection Categories and Descriptions Field Card Unit Test Description Displays the name of the card and its serial number. Identifies the unit on the card. Identifies the test. Status Describes whether or not the test was completed, if it timed out, whether the test passed or failed. Time Left Lists the time left to run on the test. When you click on a test result (a row) in the summary table, the test details re displayed in the Details box. The two buttons below the Details box determine how the test results are saved in the log report. Save Details - Saves the details as they appear in the Details box. Save Summary - Saves the table in the Tests Results pane to the Falcon Logs folder. The log is named using the MCU name, Slot ID, Card name, Unit, Processor and Word summary. 72

77 Appendix A - Falcon Diagnostic Tool Setting the Log Files Path Whenever you connect to an MCU, a new log file is started. All Falcon functions are saved to a log file. The Log option in the main menu enables you to define the location of the folder where the log files are sent. You can restrict the logs to record only detected faults discovered during a diagnostic test. These log files can be sent by the system administrator to Polycom support to help resolve any problems that might occur. In addition, any Test Results or Test Summaries are sent to the folder in which the log files are stored. If you save Only Faults in the Log menu, files with just the faults discovered in the test results will be available in the log file folder. Otherwise, all the results are recorded. To set the Log file path: 1. In the Log menu, click Set Log File Path. A browser opens to set the log file path. 2. Select the Folder to store the log files and click OK. To filter the log file to list only the test faults: In the Log menu, click Only Faults. 73

78 MGC Release Notes - Version 7.5 Connecting to an MCU Before running the diagnostic tests on an MCU, you must connect the MCU to the Falcon diagnostic tool. To connect the Falcon diagnostic tool to a specific MCU: 1. Double-click on the selected MCU icon or right-click on the MCU icon and click Connect from the right mouse menu or the Main menu options. A message appears indicating that the MCU must be reset in the Falcon mode. 2. Click OK. You must close all On Going Conferences before opening the Falcon diagnostic tool. If a conference is running when you try to connect to an MCU, an error message is displayed indicating that you must first close the On Going Conference. When the Falcon diagnostic tool resets the MCU, it identifies the MCU cards that can be tested. Cards that cannot be tested are displayed in the MGC Manager but not in the Falcon tool. 74

79 Appendix A - Falcon Diagnostic Tool Running Diagnostic Tests After you connect to an MCU, you can run the diagnostic tests. The Falcon tool reads the available cards in the MCU, and a list of tests relevant to the selected element is displayed in the Test Selection box. For a list of the specific tests run on each element, see Diagnostic Tests on page Connecting the ISDN Loopback and LAN cables If you run a LAN test on an IP+ or IPN card, or an ISDN Loop test on an IPN card, you must connect the ISDN Loopback or LAN cables to the MCU before you run the diagnostic tests PPP (Point to Point Protocol) support enables the operator to establish TCP/IP communication with the MCU over a telephone line with a modem, or directly by means of a serial connection. If a modem connection is used, the modem must be connected to one of the MCU's serial connectors. If a direct line connection is used, the remote station must be connected to the MCU by means of a Null Modem cable. When the PPP is used, there is no need to run the LAN test. If you do not fill in the IP Test box, a pop-up box appears when the LAN test is about to run. You can cancel the LAN test at that time. To connect the LAN cable and the ISDN Loopback cable to the MGC-25 unit: 1. On the MGC-25 unit, ensure that the Control LAN cable is connected to the Control LAN port. 2. Ensure that a second LAN cable is connected to the LAN 1A port. These two cables are necessary to run the LAN diagnostic tests on the installed IPN cards. 75

80 LAN MGC Release Notes - Version Replace the standard ISDN cable with the ISDN Loopback cable that comes with the unit to the PRI 1A and PRI 1B ports on the MGC-25 unit. This is necessary to run the ISDN Loop Test on the IPN card. PRI 1A port LAN 1A port PRI 1B port LAN cable ISDN Loopback cable Figure 4: ISDN Loopback Cable Connected to PRI 1A and PRI 1B Ports on the Back of the MGC-25 To connect the LAN cable to an MGC-50 unit: 1. Ensure that the Control LAN cable is connected to the RJ 45 Connector port. 2. Connect a LAN cable to the I/O port of any installed IP+ card. This is necessary to run the diagnostic tests on the installed IP+ cards. There is no ISDN Loop test on an MGC-50 or MGC-100. Insert LAN cable to I/O port Slot A IO Card Main Control Module Cover COM 1 Fuse Main Switch AC Inlet RJ45 Connector Fan 76

81 MUSIC LINE IN COM COM 1 ALARMS LAN 10/100 Mbits Appendix A - Falcon Diagnostic Tool To connect the LAN cable to an MGC-100 unit: 1. Ensure that the Control LAN cable is connected to the RJ 45 Connector port. 2. Connect a LAN cable to the I/O port on the back of any IP+ card to be tested. Insert LAN cable to I/O port Slot A RS232 Connectors Network Connectors Main Control Module Cover Main Switch and Circuit Breaker AC Inlet Dry Contacts RJ45 Connector Fan To run the diagnostic tests at the MCU level: The LAN test and the ISDN Loop test are automatically run at the MCU level testing, so connect the ISDN Loopback and LAN cables to the MCU before running the tests. For more details, see Connecting the ISDN Loopback and LAN cables on page Connect to all the MCUs that must be tested. 2. In the Test Options box, select the test mode. For a detailed description of the three modes, see Test Options Box on page For a description of how to connect the ISDN Loopback or LAN cables, see Connecting the ISDN Loopback and LAN cables on page At the MCU level, the LAN test is automatically run and therefore, the IP Test fields must be filled in. For a detailed description of the IP Test fields, see IP Test Box on page Select a test mode in the Test Options box. For a description of the test selection options, see Test Selection on page Click the Run button. The test results appear in the Test Results pane as the tests occur. For a detailed description of the Test Results pane, see Test Results Pane on page To run diagnostic tests at the card level: Once you are connected to an MCU, you can expand the MCU tree to display its cards. This enables you to run the diagnostic tests on individual cards without having to run the test series on all the cards that are installed. You can set multiple tests to run at once, but they will run serially rather than simultaneously. 77

82 MGC Release Notes - Version 7.5 When you run the diagnostic tests on a specific card, all available tests are performed on that card. If you run a LAN test on an IP+ or IPN card, or an ISDN Loop test on an IPN card, you must connect the ISDN Loopback or LAN cables to the MCU before you run the diagnostic tests. For a description of how to connect the LAN or ISDN Loopback cables, see Connecting the ISDN Loopback and LAN cables on page In the Browser pane, expand the selected MCU tree. 2. Select the cards to test. 3. In the Test Options box, select the test mode. For a detailed description of the three modes, see To run the diagnostic tests at the MCU level: on page If you have an IP or IPN card installed on your MCU, one of the tests that is run is the LAN test. To complete the LAN test, you must fill-in the IP Test fields. For a description of completing the IP Test fields, see IP Test Box on page Click the Run button The test results appear in the Test Results pane. For a detailed description of the Test Summary pane, see Test Results Pane on page To run tests at the unit level: The card unit tests are usually run by Polycom personnel. If you run a LAN test on an IP+ or IPN card units, or an ISDN Loop test on an IPN card, you must connect the ISDN Loopback or LAN cables to the MCU before you run the diagnostic tests. For a description of how to connect the LAN or ISDN Loopback cables, see Connecting the ISDN Loopback and LAN cables on page In the Browser pane, expand the selected MCU tree. 2. In the Test Options box, select the test mode. For a detailed description of the three modes, see To run the diagnostic tests at the MCU level: on page Expand the Card tree to display its units. 4. Select the card unit on which the diagnostic tests are to be performed. The Test Selection window displays the available tests for that card. 78

83 Appendix A - Falcon Diagnostic Tool 5. In the Test Selection window select the diagnostic tests to be performed. 6. If you have an IP or IPN card installed on your MCU, one of the tests that is run is the LAN test. To complete the LAN test, you must fill-in the IP Test fields. For a description of completing the IP Test fields, see IP Test Box on page Click Run. The test results appear in the Test Results pane. For a detailed description of the Test Summary pane, see Test Results Pane on page Post Testing Procedure for MGC-25 Units After all the tests have been completed on an MGC-25 unit, replace the ISDN Loopback cable with the standard ISDN cable. Test Results The test results appear dynamically in the Test Results pane as the tests run. To save the table that is displayed in the Tests Results window to the Falcon Logs folder: In the Test Results pane, click the Save Summary button. The log is named using the MCU name, Slot ID, Card name, Unit, Processor and Word summary. To save the faults details as they appear in the Details box: After the tests are completed, click the Save Details button in the Test Results pane. The Test Results, Faults and Summaries are saved together with the Log files in the folder designated for that purpose when the Log file path was set. These files can be sent to support personnel to help them understand any problems with the hardware that may appear after the diagnostics are run. 79

84 MGC Release Notes - Version 7.5 Disconnecting from the Falcon Diagnostic Tool Disconnecting from the Falcon diagnostic tool resets the MCU and puts it back into Normal mode. If the MCU is not connecting properly in the MGC Manager Application, this option is a good way to restore the connection. This is also the recommended way to close the Falcon tool. To disconnect from the Falcon diagnostic tool: 1. Right-click the MCU icon and then select Disconnect. Alternatively, on the MCU menu, click Disconnect. A pop-up window appears prompting you to confirm the selection. 2. Click OK. The MCU disconnects from the Falcon diagnostic tool and is reset. At the end of the reset, the MCU status is restored to Normal mode. 80

85 Appendix A - Falcon Diagnostic Tool Appendix - Adding an MCU to the Network To add an MCU to the MCU Network: 1. Right-click the MCU Network icon, and then click Add MCU. 2. Alternatively, on the MCU menu, click Add MCU. 3. The Add MCU dialog box opens. 4. In the Name box, enter the name of the MCU. Specify a name that clearly identifies the MCU. 5. In the IP Address box, enter the IP Address of the MCU. The correct IP address should be obtained from your network administrator. 6. The correct Port Number appears in the dialog box. 7. Enter the user name of the MCU in the User Name field. 8. Enter the MCU password in the Password field. 9. Click the Add button. The Add MCU dialog box closes. A new icon with the specified MCU name appears in the Browser pane below the MCUs Network icon. 81