Polycom video conference bridge hardware & installation guide (160 pages)
Summary of Contents for Polycom MGC-25
Page 1
MGC-25/50/100 MGC+50/100 Release Notes Version 9.0 August 2007 DOC2186A...
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.
Removal of Redundant Configuration Files ..............7 Dongle Upgrade ......................8 Verifying the Dongle Serial Number ..............8 MGC-50/MGC-100 ..................9 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 9.0 Detailed Description .................... 26 SilenceIT Additions ..................... 27 Detailed Description .................... 27 Version 9.0 Detailed Description - Partners ........30 Ad Hoc Conferencing in Avaya Environment ............30 Detailed Description .................... 30 Dial-plan and Dial-out Options for Microsoft’s Office Communicator ...... 31 Detailed Description ....................
Version 9.0 - New Features List Version 9.0 - New Features List The following table lists the new features in Version 9.0. Table 1: New Features List Category Feature Name Description Video Automatic Setting of During Continuous Presence (CP) Cascading Link to CP cascaded conferences, by default the 1x1 Layout video layout of the cascaded link is...
Downgrading to lower versions is not supported by some of the new cards. Some of the new features are only supported on the new hardware. Please consult with Table 2 "MGC Hardware" before downloading. AES encryption is not available in all countries. Please consult Polycom sales for AES encryption availability.
Gatekeepers/Proxies Polycom PathNavigator 7.00.03.0204 Cisco gatekeeper 12.3 Radvision ECS gatekeeper 3.5.2.5 (tested in version 7.5) Tandberg gatekeeper N2.0 (tested in version 7.01) Microsoft LCS SIP proxy 2005 ver. 2.0.5470.0 Iptel proxy 0.9.6 ReadiManager SE200 2.00.00.ER029 Recorder Polycom RSS 2000 1.0.1...
Page 9
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 10
MGC Release Notes - Version 9.0 Table 3: Version 9.0 Interoperability List (Continued) Device Version Polycom iPower 9000 6.5.0.51 Polycom iPower 600 6.1.0.51 Polycom iPower 900 6.1.0.51 Polycom VTX 1000 1.60.022 Aethra VegaStar Gold 6.0.49 Sony PCS1 03.30 Tandberg MXP Series F5.3...
Removal of Redundant Configuration Files In order to ensure smooth upgrades for MGC version, Reservations, Meeting Rooms and Card configurations for an MGC that underwent a downgrade, it might be necessary to manually remove specific configuration files. Please contact Polycom Support for further instructions.
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. If you are upgrading from a version that did not require a dongle, contact Polycom support for a new dongle.
To check the dongle serial number, 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. MGC-25 • To check the dongle serial number, right-click the MCU icon, and then click System Configuration.
Prior to accessing the Polycom Resource Center Web site, retrieve the system serial number from the MCU. • The MCU-25/50/100 have a Polycom label with a Serial No. fixed on the rear panel. • On the Dongle, a white label either on the face or the side lists the Serial No.
Software Upgrade Procedure e-mail). If the numbers do not match, do not proceed with the upgrade process and contact support. When 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.
MGC Release Notes - Version 9.0 MGC Unit Software Upgrade Procedure Before upgrading the MCU software version: • A new dongle file must be loaded to the MCU to upgrade from a previous version to version 9.X. • Backup your configuration, including all Message Services. •...
“You must have a valid Verify that the dongle is installed installed dongle attached to the on the MCU. MCU before Contact Polycom support team downloading MCU to have a dongle shipped. software version 5.02 and later.” Verifying the software “Software is not...
Page 18
MGC Release Notes - Version 9.0 To install a software update on the MCU: 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.
Open. The default system.cfg file is located in the appropriate MGC SW CD folder. To access a modified system.cfg file, contact Polycom Support. The name of the file appears in the Install field in the Install File dialog box.
MGC Release Notes - Version 9.0 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.
Software Upgrade Procedure Updating the Entry Queue Services When upgrading from Version 5.x directly to Version 9.0 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.
MGC Release Notes - Version 9.0 Version 9.0 Detailed Description - Video Automatic Setting of Cascading Link to CP 1x1 Layout During Continuous Presence (CP) cascaded conferences, by default the video layout of the cascaded link is automatically set to full screen (1x1), showing in each conference only the last/current speaker (in a full video window) from the other conference.
Version 9.0 Detailed Description - Video CP Full Screen (1x1) Layout setting of Cascading Link is supported in CP conferences for H.323, SIP and ISDN links in the following modes: Classic and Quad Views Video Sessions including Auto Layout setting •...
MGC Release Notes - Version 9.0 Video Invite Additions In version 8.0, Video Invite was available to H.323 participants only. In version 9.0, Video Invite is extended to include ISDN, MPI and SIP participants. Detailed Description By default, Invite options are automatically enabled in the IVR Service with the appropriate DTMF codes.
Version 9.0 Detailed Description - Video Table 5: Invite Dial String Format Endpoint DTMF Dial String Format Network Type Code ISDN endpoint The participant dials *36 followed by the ISDN number (i.e. 9925100) and pound key. For example: *36<dialtone->99251000# MPI endpoint The participant dials *37 followed by the service number (MPI number), astrisks (*), and pound key.
MGC Release Notes - Version 9.0 Version 9.0 Detailed Description - General External DB Modifications In version 9.0, additional modes are used for verifying with the external database application the participant’s right to start a new conference and the participant right to join an ongoing conference.
Page 27
Version 9.0 Detailed Description - General • In the system.cfg, in the GREET AND GUIDE/IVR section, manually add the flag USE_CLI_AS_PWD_FOR_EXT_DB=YES When the participant connects to a conference, the MCU uses the participant’s CLI to query the external database application. When the flag is set to YES, the system does not prompt for password and the request to the external database application includes a dummy password (999886) which is ignored by the external database application during authentication.
MGC Release Notes - Version 9.0 Permanent Conference The Auto Extension mechanism has been changed to enable the system to automatically extend an ongoing conference indefinitely, creating a permanent ongoing conference on the MCU. Detailed Description The automatic extension of the conference indefinitely is enabled by activating the Auto Extension mechanism and setting the conference duration to 99.59, making sure that it is the duration when the conference becomes ongoing.
Page 29
Version 9.0 Detailed Description - General • Each time the conference is extended, an event is added to the CDR file, until the file size reaches 1 MB. Once this limit is reached, no additional events are added to the CDR but they are written to the log file. When the conference ends, the appropriate event is added to the CDR file.
MGC Release Notes - Version 9.0 National ISDN NI1 & NI2 Switch Type National ISDN NI1 & NI2 is now supported in ISDN T1 Network Services. This option is available for ISDN T1 in North America. Detailed Description In the ISDN Network Service - Span Definition dialog box, in the Switch Type list, select NI-1 or NI-2.
Version 9.0 Detailed Description - General SilenceIT Additions A new mechanism is introduced, enabling fine tuning of the SilenceIT algorithm. Detailed Description In previous versions, in some cases, the SilenceIT algorithm was not sensitive enough to the noise level causing speech to be muted, or not muting music and noise. In version 9.0, the new mechanism enables the system to measure the audio energy, and based on this measurement, fine-tune the system usage of the SilenceIT algorithm.
Page 32
MGC Release Notes - Version 9.0 In the command line enter: AM<slot#><unit #>GETCSTRMSTAT and press <Enter>. The signal statistics are retrieved and are displayed in the Donkey-COM window. Look for these parameters in the following format: “Average Energy = <Energy> Total VADS = <Total Vads>Consecutive VADS = < Consecutive Vads>”.
Page 33
Version 9.0 Detailed Description - General Table 6: Noisy Line Tuning Table Noise Consecutive Parameter Energy Total VADs Environment VADs Value 76<E<91 Noisy V < 50 V < 50 152<E<182 67<E<76 Noisy V < 50 V < 50 134<E<152 0<E<67 Noisy V <...
MGC Release Notes - Version 9.0 Version 9.0 Detailed Description - Partners Ad Hoc Conferencing in Avaya Environment Ad Hoc conferencing is supported in Avaya environment. Detailed Description To enable Ad Hoc Conferencing for Avaya endpoints: The administrator must configure the ACM and MGC for Ad Hoc conferencing. In the MGC Manager, define one or several new Meeting Rooms.
The user can use the same dialout methods for ISDN, SIP, H.323 or PSTN endpoints. • For more information using the Call via Conferencing Service see, Microsoft-Polycom Integrated Deployment Guide Phase 5, Chapter 3 “Polycom Meeting Scenarios”, “An Office Communicator User Dials out to another Office Communicator User”.
Page 36
MGC Release Notes - Version 9.0 New MPI Flag In the system.cfg a new MPI flag SIP_REFER_MPI_PREFIX= <value> has been added to the SIP_REFER_PREFIX_AND_PHONES section. The dialout example shown on the previous page shows the prefix <value = 555> as it should be configured in the system.cfg. Figure 2: Sample system.cfg file The system.cfg flag DIGITS_IN_PHONE_NUMBER=<VALUE>...
Corrections, Pending Issues and Limitations Corrections, Pending Issues and Limitations Corrections between Versions V.8.0 and V.9.0 Table 7: Corrections between Versions V.8.0 and V.9.0 Category Description Remarks A memory leak occurs on API server in VNGM - the participant object, when updating 1780/ the private layout.
Page 38
MGC Release Notes - Version 9.0 Table 7: Corrections between Versions V.8.0 and V.9.0 Category Description Remarks An HD endpoint is connected as VNGM- Secondary (audio only) when 1578 connecting to a VSW conference whose line rate is 1920Kbps and the video parameters are fixed (disabling the Highest Common mechanism).
Page 39
Corrections, Pending Issues and Limitations Table 7: Corrections between Versions V.8.0 and V.9.0 Category Description Remarks Occasionally a stack controller failure VNGM - occurs on the IP+48 while the card is 1883/ used for conferencing. VNGFE -564 MGC that is not registered to the VNGM - gatekeeper cannot dial out to an H.323 1979/...
Page 40
MGC Release Notes - Version 9.0 Table 7: Corrections between Versions V.8.0 and V.9.0 Category Description Remarks NET-8 card The Net-8 card active LED (yellow) VNGM - remains lit after the conference ended 1778/ and not card ports are used for VNGFE conferencing.
Corrections, Pending Issues and Limitations Corrections between Versions V.7.5.0 and V.8.0 Table 8: Corrections between Versions V.7.5.0 and V.8.0 Category Description Remarks Compilation error occurs when 20831 compiling 7.0 SDK with third party application. CDR retrieval generates two problems: 21471 •...
Page 42
MGC Release Notes - Version 9.0 Table 8: Corrections between Versions V.7.5.0 and V.8.0 Category Description Remarks General The MCU occasionally disconnects 20880 Reconnect to the from MGC manager when using a MCU. secured port (port 443 - SSL). General The 'Auto_Redial' parameters in 20897 Require MCU...
Page 43
Corrections, Pending Issues and Limitations Table 8: Corrections between Versions V.7.5.0 and V.8.0 Category Description Remarks ISDN Sometimes ISDN endpoints fail to 20932 move from one Video Switching conference to another when the line rate of the destination conference is higher then the line rate at the initial conference.
Diagnostics Long loop test may fail when running 20467 the diagnostic on the MGC-25 Diagnostics Diagnostics sometimes cannot connect 21551 to the cards. Encryption In a Video Switching encrypted...
Page 45
Corrections, Pending Issues and Limitations Table 9: Pending Issues (Continued) Category Description Remarks FTP service on XPEK may stop 20433 In the IP working, which affects system Terminal, enter functions, such as prevent the Logger restore_ftp. If Diagnostic Files from opening, causing the system the MGC Manager application to close.
Page 46
MGC Release Notes - Version 9.0 Table 9: Pending Issues (Continued) Category Description Remarks General In a mixed system with ISDN and IP, — Set the when the clock is set to ISDN and you system.cfg set the source of the ISDN span to Null, CLOCKING the IP+ card may stop responding.
Corrections, Pending Issues and Limitations Version 9.0 System Limitations Table 10: System Limitations Workaround/ Category Description Remarks Ad Hoc Assigning an Audio Only Profile to a 14591 conferencing video Ad Hoc-enabled Entry Queue causes errors. ISDN participants can connect to VSW 20910 conferences that have the same Encryption settings (i.e.
Page 48
MGC Release Notes - Version 9.0 Table 10: System Limitations (Continued) Workaround/ Category Description Remarks With an endpoint set to Personal 19498 Layout, when a video parameter is altered, the video layout changes automatically to Conference Layout. FX cannot handle two H.264 calls 19635 simultaneously.
Page 49
Corrections, Pending Issues and Limitations Table 10: System Limitations (Continued) Workaround/ Category Description Remarks FECC Only the endpoint displayed in the 16503 layout’s upper left window can be controlled by the far end camera. FECC When trying to move a remote camera 17975 using FECC before the video is received may cause more than one...
Page 50
Refresh rate of the H.239 content is 21145 slow when using VSX7000 and VSX8000 endpoints. H.239 H.239 in cascaded conferences is VNGM supported only on MGC to MGC -1193 (Polycom to Polycom) cascaded links. H.264 In Quad View mode endpoints do not 21371 connect in H.264.
Page 51
Corrections, Pending Issues and Limitations Table 10: System Limitations (Continued) Workaround/ Category Description Remarks H.264 IP Participants are connected as 17198 Secondary when moved from a CP/ H.264 conference to a CP COP/H.264 conference, running at a different line rate. H.323 In H.323 Fixed Ports mode - although —...
Page 52
MGC Release Notes - Version 9.0 Table 10: System Limitations (Continued) Workaround/ Category Description Remarks The number of IVR Services defined 16455 for a single MGC unit may not exceed 30 Services. When this number is exceeded it causes high CPU usage. The DTMF Help file LdrHlp3 contains —...
Page 53
CARDS CONFIGURATION FILE cards. MGC-25 An exception occurs when performing 17469 update card while a conference is starting and the MGC-25 must be restarted. MGC-25 After changing the span of the Net card 18910 the MGC-25 must be restarted. MGC-25 Problems occur when connecting a —...
Page 54
MGC Release Notes - Version 9.0 Table 10: System Limitations (Continued) Workaround/ Category Description Remarks When four participants of a unit use 21622 Do not use FECC FECC and P+C, or FECC and with P+C or Siren, Siren 7/14, the MUX card can crash. or configure the units for two participants.
Page 55
Corrections, Pending Issues and Limitations Table 10: System Limitations (Continued) Workaround/ Category Description Remarks Roll Call When Roll Call is in use and a 13661 participant is disconnected, there is a delay until the MGC Manager indicates the disconnection. Roll Call Roll Call is not supported when moving —...
Page 56
MGC Release Notes - Version 9.0 Table 10: System Limitations (Continued) Workaround/ Category Description Remarks SIP endpoints connect as Secondary 21419 (audio only) in the following Video Session settings: • Software CP • CP COP (Conference on Port) • CP - Quad Views •...
Page 57
DTMF codes from the remaining T1-CAS participants to the MCU. T1-CAS T1-CAS is not supported on the 15663 MGC-25. VCON When an ISDN participant connects to 18027 Set the conference a Video Switching (Auto or H.263) to G.711.
Page 58
MGC Release Notes - Version 9.0 Table 10: System Limitations (Continued) Workaround/ Category Description Remarks 105. 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.
Page 59
Corrections, Pending Issues and Limitations 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.
Need help?
Do you have a question about the MGC-25 and is the answer not in the manual?
Questions and answers