Polycom MGC-25 Release Notes
  1. Manuals
  2. Brands
  3. Polycom Manuals
  4. Conference System
  5. MGC-25
  6. Release notes
Polycom MGC-25 Release Notes

Polycom MGC-25 Release Notes

Video conferencing bridge
Hide thumbs Also See for MGC-25:
Table of Contents

Advertisement

Quick Links

Download this manual
MGC-25/50/100
MGC+50/100
Release Notes
Version 7.0.4
March 2006
DOC2117E

Advertisement

Table of Contents
loading

Related Manuals for Polycom MGC-25

Summary of Contents for Polycom MGC-25

  • Page 1 MGC-25/50/100 MGC+50/100 Release Notes Version 7.0.4 March 2006 DOC2117E...
  • Page 2 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.

  • Page 3: Table Of Contents

    Dongle Upgrade ......................7 Dongle Information ....................7 Dongle Upgrade Instructions ................8 MGC-50/MGC-100 ..................8 MGC-25 ......................9 Downloading the Dongle File ................10 Installing the Dongle File ..................11 MGC Unit Software Upgrade Procedure ..............12 Upgrading from a Version using Password for Entry Queue Routing ....12 Upgrading from a Version using Numeric ID for Entry Queue Routing .....13...
  • Page 4 MGC Release Notes - Version 7.0.3...

  • Page 5: Version 7.0.4 Upgrade Package Contents

    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 II —...

  • Page 6: Prior To Installation And Sw Upgrade

    MGC Release Notes - Version 7.0.4 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.

  • Page 7: Control Unit Update Notice

    MGC Versions H.264 H.239 Version V4.42 V7.0 and later MUX+10 V4.42 V7.0 and later MUX+20 V4.42 V7.0 and later MUX+40 MGC-25 V1.24 V5.0 and later V1.41 V6.11, V7.0 and later V1.04 V5.0 and later AUDIO-A V1.21 V6.11, V7.0.1 and AUDIO-A later *1—These cards are not supported with the MGC+50/100.

  • Page 8: Version 7.0.4 Interoperability Table

    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 6.02.03 and 7.0 (tested in version 7.01)
  • Page 9 Prior to Installation and SW Upgrade Table 1: Version 7.0.4 Interoperability List (Continued) Device Version Polycom VSSP384 7.5.2 Polycom VS EX 6.04 Polycom VS FX 6.04 Polycom VS4000 6.04 Polycom V500 7.52 and 8.0 Polycom V500 Pal 7.52 and 8.0 Polycom VSX3000 7.52 and 8.0...

  • Page 10: Software Upgrade Procedure

    MGC Release Notes - Version 7.0.4 Software Upgrade Procedure Upgrade Checklist Prior to upgrading to Version 7.0.4 it is recommended you perform the following steps: Verify the amount of free disk space on the MCU. For details, see “MCU Disk Space Verification”...

  • Page 11: Dongle Upgrade

    Dongle Information The MGC-50/100, MGC+50 and MGC+100 are 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.

  • Page 12: Dongle Upgrade Instructions

    For a major version, such as upgrading from version 5.xx and 6.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 10) or contact your next level of support.

  • Page 13: Mgc-25

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

  • Page 14: Downloading The Dongle File

    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, the MGC+50 and MGC+100 have a Polycom label with a Serial •...

  • Page 15: Installing The Dongle File

    Software Upgrade Procedure Click Download. Save the new dongle file. If the following error message appears: “No Maintenance Agreement Found/ MGC Serial Number not Found”, please contact your next level of support. Click OK when Download is complete. Installing the Dongle File To Upgrade the Dongle file: Connect to the MCU.

  • Page 16: Mgc Unit Software Upgrade Procedure

    MGC Release Notes - Version 7.0.4 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: •...

  • Page 17: Upgrading From A Version Using Numeric Id For Entry Queue Routing

    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: On the File menu, click Download MCU Software.
  • Page 18 MGC Release Notes - Version 7.0.4 Click OK. The Software Installation dialog box opens. The MCU software will be installed on each listed MCU. Select the Install Default Services check box to download the default IVR Service and Entry Queue Service. The default IVR Service is in English and is named IVR70. The default Entry Queue Service is in English and is named EQ70.

  • Page 19: Installing The Mgc Manager Software

    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: Open Windows Explorer and open the folder that contains the MGC Manager diskettes.

  • Page 20: Updating The Entry Queue Services

    MGC Release Notes - Version 7.0.4 Updating the Entry Queue Services When upgrading from Version 5.x to Version 7.0.4 you need to update the Entry Queue Service to include the appropriate voice messages. To update the Entry Queue Service: Expand the IVR Message Services list (under the MCU Configuration list). 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.

  • Page 21: Corrections, Limitations And Pending Issues

    Corrections, Limitations and Pending Issues Corrections, Limitations and Pending Issues Corrections between Versions V.7.0.3 and V.7.0.4 Table 2: Corrections between Versions V.7.0.3 and V.7.04 Category Description Remarks Compilation error occurs when 20831 compiling 7.0 SDK with third party application. CDR retrieval generates two problems: 21471 •...
  • Page 22 MGC Release Notes - Version 7.0.4 Table 2: Corrections between Versions V.7.0.3 and V.7.04 Category Description Remarks General The MCU self-reboots with no activity 22097 on it, NVERCFG.CPP asserts appear. Connecting POTS to H.323 by the 21916 MGC Gateway fails in Version 7.x XPEK MGC The Stack Controller and RTP 21456...

  • Page 23: Corrections Between Versions V.7.0.2 And V.7.0.3

    Corrections, Limitations and Pending Issues Corrections between Versions V.7.0.2 and V.7.0.3 Table 3: Corrections between Versions V.7.0.2 and V.7.0.3 Category Description Remarks Audio+ Occasionally Audio disconnects, and 20999/ Audio+ cards crash. 21466 Auto Cascade In large auto cascaded conferences 21221 with a Master Meeting Room and 11 Slave Meeting Rooms, the IP+ card may crash.

  • Page 24: Corrections Between Versions V.7.0.1 And V.7.0.2

    MGC Release Notes - Version 7.0.4 Corrections between Versions V.7.0.1 and V.7.0.2 Table 4: Corrections between Versions V.7.0.1 and V.7.0.2 Category Description Remarks Audio When many participants are detected 19424 as having a Noisy Line, other participants cannot connect to the Audio+ card.
  • Page 25 20565 H.239 channel does not open. H.239 Slave conferences cannot receive 20649 content from the Master conference on the MGC-25. Alias names for IP participants 20481 increased to 100 characters. When connecting a defined dial-out 16625 participant to a Meet Me Per...
  • Page 26 Remarks MGC Manager When using MCU port 5001, 20294 conference names are not displayed in the IP card properties. MGC-25 When using the Fast Configuration 20584 Wizard, the MGC Manager crashes while configuring the ISDN Network Service. Synchronization improvements on the —...

  • Page 27: Corrections Between Versions V.7.0 And V.7.0.1

    Corrections, Limitations and Pending Issues Corrections between Versions V.7.0 and V.7.0.1 Table 5: Corrections between Versions V.7.0 and V.7.0.1 Category Description Remarks Ad Hoc During an Ad Hoc conference, when 14821 conferencing the chairperson presses DTMF code *3 to invite a PSTN invitee, an Assert occurs.
  • Page 28 MGC Release Notes - Version 7.0.4 Table 5: Corrections between Versions V.7.0 and V.7.0.1 Category Description Remarks When running conferences set to H.264 19535 and XGA Video Format, the video+ card may crash. H.323 An exception may occur when 19887 connecting more than 96 H.323 participants in a blast dial-out conference.

  • Page 29: Corrections Between Versions V.6.Xx And V.7.0.0

    Corrections, Limitations and Pending Issues Table 5: Corrections between Versions V.7.0 and V.7.0.1 Category Description Remarks In a IP conference with the Video 19632 Format set to XGA, errors could occur when sending content. XPEK In certain instances the MCU does not 19346 accept valid IP addresses.
  • Page 30 MGC Release Notes - Version 7.0.4 Corrections between Versions V.6.xx and V.7.0.0 Table 6: Corrections between Versions V.6.xx and V.7.0 Category Description Remarks Ad Hoc When the MCU status is Minor and 14619 conferencing the connection to an external DB is lost and then re-established, the MCU status is Normal instead of Minor.
  • Page 31 Corrections, Limitations and Pending Issues Table 6: Corrections between Versions V.6.xx and V.7.0 Category Description Remarks General The option to edit system files is not 14964 blocked for Operators. H.320 In Continuous Presence conferences 6650 set to 2x2 layout, the top left window display is empty after changing the participant name.

  • Page 32: Version 7.0.4 System Limitations

    MGC Release Notes - Version 7.0.4 Table 6: Corrections between Versions V.6.xx and V.7.0 Category Description Remarks MGC Manager The MGC Manager application 14789 closes when modifying participant templates while trying to exit the Database Manager without saving the changes (selecting Cancel when prompted to Save changes).
  • Page 33 Corrections, Limitations and Pending Issues Version 7.0.4 System Limitations Table 7: System Limitations Workaround/ Category Description Remarks Ad Hoc Assigning an Audio Only Profile to a 14591 conferencing video Ad Hoc-enabled Entry Queue causes faults. Audio+ In some conferences, the first participant hears a faint clicking sound when the second participant interacts with the IVR Service.
  • Page 34 MGC Release Notes - Version 7.0.4 Table 7: System Limitations (Continued) Workaround/ Category Description Remarks In COP conferences, when the 13200 Connect the chairperson enters the conference with chairperson prior to Click&View, all other participants see the other the Click&View slide instead of the participants.
  • Page 35 Corrections, Limitations and Pending Issues Table 7: System Limitations (Continued) Workaround/ Category Description Remarks Entry Queue During Entry Queue definition, 18382 Delete the Entry properties are taken from the IP Queue and redefine Service. Once an Entry Queue is it.‘1 defined, you cannot delete or add any IP Service related to that Entry Queue.
  • Page 36 MGC Release Notes - Version 7.0.4 Table 7: System Limitations (Continued) Workaround/ Category Description Remarks General Participants moved between 14424 conferences can be listed in both conferences. General When a defined dial-in participant is 14813 moved to the Operator conference with “Attend with details”, and disconnects, 14838 the Attended Participant window...
  • Page 37 Corrections, Limitations and Pending Issues Table 7: System Limitations (Continued) Workaround/ Category Description Remarks Interop When a Vcon ISDN endpoint connects 18027 Set the conference to a VideoSwitching (Auto or H.263) audio algorithm to conference the endpoint disconnects. G.711. Interop The Tandberg MXP endpoint connects 21430 Secondary during Video Switching...
  • Page 38 MGC Release Notes - Version 7.0.4 Table 7: System Limitations (Continued) Workaround/ Category Description Remarks 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”...
  • Page 39 MGC-25 Problems occur when connecting a — mouse to the MGC-25. MGC-25 After upgrading the MGC-25 card 12335 Functionality is OK. configuration file from IP12 to The limitation is the Unified24, the following major error appearance of the code appears in the Faults file: error message.
  • Page 40 MGC Release Notes - Version 7.0.4 Table 7: System Limitations (Continued) Workaround/ Category Description Remarks The maximum number of ISDN participants in an H.239 conference is People and When using Content, the number of — Resources should Content V0 supported participants per H.323 be manually network card may decrease as follows: allocated to the...
  • Page 41 DTMF codes from the remaining T1-CAS participants to the MCU. T1-CAS T1-CAS is not supported on the 15663 MGC-25. Video Participants who were forced to a — video window cannot be forced to another window in the layout without cancelling the first (choose “Auto...
  • Page 42 MGC Release Notes - Version 7.0.4 Table 7: System Limitations (Continued) Workaround/ Category Description Remarks Video An endpoint supports H.261, H.263 6947 Switching and H.264. When moving this endpoint from a Video Switching conference set 16869 to H.261 to a Video Switching conference set to H.263 or H.264, it connects as Secondary.

  • Page 43: Version 7.0.4 Pending Issues

    Encryption In a Video Switching encrypted 19552 conference with more than 75 participants and set to 768kbps line rate, the Audio+ card may crash. Falcon Long loop test may fail when running 20467 Diagnostic Tool diagnostics on the MGC-25...
  • Page 44 FX endpoints do not show Content. Gatekeeper Gatekeeper CON (Conference On 20477 Demand) does not work with the MGC-25. When deleting active conferences with two or more participants, asserts can occur. Gateway When the MGC unit is used as a 19297...
  • Page 45 Corrections, Limitations and Pending Issues Table 8: Pending Issues (Continued) Category Description Remarks H.239 Connecting 12 H.239 participants to an 20458 Connect only 11 MG323 board causes the card to fail. participants to one MG323 card. MGC Manager Endpoints appear as “faulty connected” 20382 during the first seconds of connection.
  • Page 46 MGC Release Notes - Version 7.0.4 Proprietary and Confidential The information contained herein is the sole intellectual property of Polycom, Inc. No distribution, reproduction or unauthorized use of these materials is permitted without the expressed written consent of Polycom, Inc. Information contained herein is subject to change without notice and does not represent commitment of any type on the part of Polycom, Inc.

This manual is also suitable for:

Mgc-50Mgc-100

Table of Contents