Polycom MGC+100 Release Note
  1. Manuals
  2. Brands
  3. Polycom Manuals
  4. Network Hardware
  5. MGC+100 ReadiConvene
  6. Release note

Polycom MGC+100 Release Note

Polycom mgc+100 network: release note
Hide thumbs Also See for MGC+100:
Table of Contents

Advertisement

Quick Links

Download this manual
MGC-25/50/100
MGC+50/100

Release Notes

Version 7.5
February 2006
DOC2134A

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the MGC+100 and is the answer not in the manual?

Questions and answers

Related Manuals for Polycom MGC+100

Summary of Contents for Polycom MGC+100

  • Page 1: Release Notes

    MGC-25/50/100 MGC+50/100 Release Notes Version 7.5 February 2006 DOC2134A...
  • 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

    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...
  • Page 4 Connecting to an MCU ... 74 Running Diagnostic Tests ... 75 Test Results ... 79 Disconnecting from the Falcon Diagnostic Tool ... 80 Appendix - Adding an MCU to the Network ... 81 Test Glossary ... 82 Log File Report Examples ... 83...

  • Page 5: Version 7.5 - New Features List

    Version 7.5 - New Features List The following table lists the new features in Version 7.5. Table 1: New Features List Category Video Video Video Video Video Feature Name Description H.264 SD/HD in Video H.264 Standard Definition (SD), High Switching conferences Definition (HD) and VSX 8000 (version 8.0) HRR resolutions are supported in Video Switching conferences.
  • Page 6 MGC Release Notes - Version 7.5 Table 1: New Features List (Continued) Category Feature Name Description 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.
  • Page 7 Conferences Version 7.5 - New Features List Description With MGC 7.5 (MS integrator phase 3) Polycom now supports the full set of OC Conferencing capabilities based on the MS SIP-CX protocol. For a detailed description of the Microsoft solution see the Microsoft Deployment Guide.
  • Page 8 MGC Release Notes - Version 7.5 Table 1: New Features List (Continued) Category General General General Feature Name Description Circular Resource When the MCU is set to circular mode, Mapping Audio+ and Video+ card resources are allocated onto the next sequential unit that is free on a plus (+) card.

  • Page 9: Version 7.5 Upgrade Package Contents

    — 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 Documentation describing how to work with an external database application...

  • Page 10: Prior To Installation And Sw Upgrade

    Hardware Update Notice Please make sure the hardware listed below is used with the listed MGC version and MGC Manager versions: Board Type MGC-50/MGC+50/MGC-100/MGC+100 Audio 12/24 Audio+12/24 Audio 24/48 Audio+24/48 Audio 48/96...

  • Page 11: Control Unit Update Notice

    Board Type MUX+20 MUX+40 MGC-25 AUDIO-A AUDIO-A *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).

  • Page 12: Version 7.5 Interoperability Table

    Tandberg MPS Radvision viaIP MCU Gateways Cisco IP gateway Radvision viaIP gateway Tandberg gateway Dilithium DTG2000 3G gateway Ericsson VIG 3G gateway Polycom Office Products Polycom PCS Polycom GMS Polycom WebOffice Endpoints Polycom ViaVideo1 Polycom ViaVideo 2 Polycom PVX Polycom VS512...
  • Page 13 Table 1: Version 7.5 Interoperability List (Continued) Device Polycom VSSP384 Polycom VS EX Polycom VS FX Polycom VS4000 Polycom V500 Polycom V500 Pal Polycom VSX3000 Polycom VSX7000 Polycom VSX8000 Polycom iPower 600 Polycom iPower 900 Polycom iPower 9000 Aethra VegaStar Gold...

  • Page 14: Software Upgrade Procedure

    Removing a redundant configuration file see “Removal of Redundant Configuration Files” on page 17 The system saves the network cards’ circuit ID assignment during the upgrade process. However it is recommended that you document the network cards’ circuit ID assignments and order.

  • Page 15: Dongle Upgrade

    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.

  • Page 16: 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.

  • Page 17: Mgc-25

    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.

  • Page 18: Downloading The Dongle File

    Prior to accessing the Polycom Resource Center Web site, retrieve from the MCU the system serial number. The MCU-25/50/100 have a Polycom label with a Serial No. fixed on the rear panel. • To retrieve the Dongle File from a Polycom Web Site: Access the Polycom Resource Center web site http://extranet.polycom.com/csnprod/...

  • Page 19: Installing The Dongle File

    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. Click OK when Download is complete. Installing the Dongle File To Upgrade the Dongle: Connect to the MCU.

  • Page 20: Mgc Unit Software Upgrade Procedure

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

  • Page 21: 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 22 MGC Release Notes - Version 7.5 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, Entry Queue Service, and Gateway Service. The default IVR Service is in English and is named IVR70.

  • Page 23: Installing The Mgc Manager Software

    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. Browse to Disk 1 and double-click the Setup.exe file. Follow the on-screen instructions to complete the installation procedure.

  • Page 24: Updating The Entry Queue Services

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

  • Page 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.
  • Page 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. In the MCU GMT Offset box, enter the time difference between the MCU Local Time and MCU GMT Time.

  • Page 29: Secure Socket Layer (Ssl)

    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.
  • Page 30 MGC Release Notes - Version 7.5 Click Apply. The new certificate request appears in the details box. Click Copy, then click Close. Alternatively, for a previously defined MCU for which SSL has been obtained before, click Get to get the latest certificate request from the MCU. In the browser, access your preferred certificate authority (for example, http:// www.thawte.com and select from the quick login box: Certificate Status), paste the certificate request from MCU and submit.
  • Page 31 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.
  • Page 32 MGC Release Notes - Version 7.5 To enable a Mandatory and Secure connection for the MCU: Before connecting the MCU, right-click the MCU icon and click MCU Utils, then click Edit “system.cfg”. The SysConfig dialog box opens. In the GENERAL section, set the following flags to: —...
  • Page 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.

  • Page 34: H.239/People+Content Star Cascading

    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.

  • Page 35: Ad Hoc Auto Cascade

    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.
  • Page 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. In the Entry Queue Properties dialog box, select the Cascade check box. Enter a value in the Numeric ID field.

  • Page 37: Monitoring Auto Cascaded Conference Links

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

  • Page 38: Faulty Participant In Red

    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.

  • Page 39: Http File Transfer Mode

    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.

  • Page 40: Same Layout Option In Video Switching Conferences

    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.

  • Page 41: Direct Ip Dial-In

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

  • Page 42: Sip Factory

    MGC Release Notes - Version 7.5 SIP Factory 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. Detailed Description When the Sip Factory is created, using SIP call control means, a globally routed Conference Factory URI can be allocated and published.
  • Page 43 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.

  • Page 44: Nortel Environment Flag Settings

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

  • Page 45: Mgc+ Predefined Ip Only Entry Queues And Meeting Rooms

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

  • Page 47: Corrections, Pending Issues And Limitations

    Corrections, Pending Issues and Limitations Corrections between Versions V.7.0.2 and V.7.5 Table 3: Corrections between Versions V.7.0.2 and V.7.5 Category Audio+ Cascade General H.239 H.239 Meeting Rooms MGC Manager Microsoft Corrections, Pending Issues and Limitations Description In an Encrypted VS conference with 96 Dial-out and 96 Dial-in participants, the Audio+ cards crashed.

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

    MGC Release Notes - Version 7.5 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 Audio Audio Cascade Cascade Cascade Cisco IP Phone endpoint Encryption External dB Falcon Description On an MCU with simultaneous conferences, audio can be heard from another conference.
  • Page 49 Table 4: Corrections between Versions V.7.0.1 and V.7.0.2 Category Description Falcon The Falcon application crashes after downloading diagnostic traces on the MGC-25. Falcon No Falcon diagnostics available on Video+ cards. General When the MCU is extremely loaded, conferences may terminate before their scheduled time (XPEK operating system only) General...
  • Page 50 When using MCU port 5001, conference names are not displayed in the IP card properties. When using the Fast Configuration Wizard, the MGC Manager crashes while configuring the ISDN Network Service. Synchronization improvements on the RTS signal. An MPI endpoint connected as Direct appear as dial-in the MGC Manager.

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

    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 Ad Hoc conferencing Audio+ Cascading Cascading Cascading Corrections, Pending Issues and Limitations Description During an Ad Hoc conference, when the chairperson presses DTMF code *3 to invite a PSTN invitee, an Assert occurs on the system.
  • Page 52 Lecture Mode, running on the Standard Video card, and the selected layout is other than full screen. When creating a new Network Service, after adding 10 different Spans, the In the MGC Manager monitoring pane refresh problems may cause wrong endpoint status.

  • Page 53: Version 7.5 Pending Issues

    Version 7.5 Pending Issues Table 6: Pending Issues Category Audio Cascade Cascade Content Database Encryption Falcon Diagnostic Tool Falcon Diagnostic Tool Corrections, Pending Issues and Limitations Description When using the G.729 audio algorithm, no audio available with VoIP or SIP phones.
  • Page 54 MGC Release Notes - Version 7.5 Table 6: Pending Issues (Continued) Category FECC Gatekeeper Gateway Gateway General General General General H.264 H.323 Description FECC does not work between an IP endpoint and an MPI (DTE) endpoint. FTP service on XPEK may stop working, which affects system functions, such as prevent the Logger Diagnostic Files from opening, causing...
  • Page 55 Table 6: Pending Issues (Continued) Category Description 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”. 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...
  • Page 56 MGC Release Notes - Version 7.5 Table 6: Pending Issues (Continued) Category On-line Help PSOS PSOS SNMP T1-CAS T-120 Video+ Description When the MCU connects to the NTP server for a time calibration, connection problems occur and 15 hour time deviations result on the MCU.
  • Page 57 Table 6: Pending Issues (Continued) Category Description Video In a Video Switching conference when Switching 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. Video During the start of Video Switching Switching...

  • Page 58: Version 7.5 System Limitations

    “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.
  • Page 59 Table 7: System Limitations (Continued) Category Description Audio+ 'The "Reserved" and "Active" columns of the Audio+ Resource Report show wrong port numbers. Audio+8 Audio+8 card does not support participants using T1-CAS lines and G.729 endpoints. Cascade The speaker is assigned a wrong site name when cascading Continuous Presence and Video Switching conferences.
  • Page 60 MGC Release Notes - Version 7.5 Table 7: System Limitations (Continued) Category Content DB Manager Double Gateway Entry Queue Entry Queue FECC Description FX cannot handle two H.264 calls simultaneously. H.264 calls to the FX endpoint may witness video blocking, disconnections and audio only connections.
  • Page 61 Table 7: System Limitations (Continued) Category Description FECC Only the endpoint displayed in the layout’s upper left window can be controlled by the far end camera. FECC When trying to move a remote camera using FECC before the video is received may cause more than one camera to move.
  • Page 62 Interop Description MCU software installation must be performed from a mapped location (X:\...) and not from a network location using Windows “My Network Places”. When a defined dial-in participant is moved to the Operator conference with “Attend with details”, and is...
  • Page 63 Category Description When entering an empty space in the Alias field in the Participant Properties call failure may occur. When you delete an IP Network Service on the MCU, the Card’s properties still appear as registered in PathNavigator. ISDN When two different ISDN Network Services are used for two “Meet Me”...
  • Page 64 MGC Release Notes - Version 7.5 Table 7: System Limitations (Continued) Category Lecture Mode Manager Description 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 65 H.239 conference is People and When using Content, the number of Content V0 supported participants per H.323 network card may decrease as follows: • MG323 board - 10 instead of 12 • IP24 board - 20 instead of 24 Pro-Motion An H.320 participant connecting to a...
  • Page 66 MGC Release Notes - Version 7.5 Table 7: System Limitations (Continued) Category Roll Call Roll Call Description When Roll Call is in use and a participant is disconnected, there is a delay until the MGC Manager indicates the disconnection. Roll Call is not supported when moving a participant from one conference to another or from the Operator conference to the Home Conference.
  • Page 67 Table 7: System Limitations (Continued) Category Description The following video settings are not supported with SIP connections: • FECC - video endpoints connect without FECC option • H.264 - SIP video endpoints connect as H.263 to CP conferences and as Secondary in VSW conferences •...
  • Page 68 MGC Release Notes - Version 7.5 Table 7: System Limitations (Continued) Category Video Video Video Video Switching Video Switching Video Switching Video+ Video+ Video+ 100. 101. VTX1000 Description When resetting the video units quickly (one after the other), the video card status changes to Major.

  • Page 69: Appendix A - Falcon Diagnostic Tool

    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.

  • Page 70: Test Description

    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”...
  • Page 71 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.
  • Page 72 MGC Release Notes - Version 7.5 Table 8: Diagnostic Tests Card MUX+ Audio+ Unit Test Description Local memory Checks buses’ data and addresses. Checks memory integrity and capacity. Checks the ping between the card and the Falcon host machine IP Address. Proc Local memory Checks buses’...
  • Page 73 Table 8: Diagnostic Tests Card Unit Video+ Proc 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.

  • Page 74: Starting The Falcon Diagnostic Tool

    Manager, see “Falcon Main Window” on page 1-70. 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.
  • Page 75 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 •...
  • Page 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 1-66.

  • Page 77: Setting The Log Files Path

    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.

  • Page 78: Connecting To An Mcu

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

  • Page 79: Running Diagnostic Tests

    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”...
  • Page 80 MGC Release Notes - Version 7.5 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. ISDN Loopback cable Figure 4: ISDN Loopback Cable Connected to PRI 1A and PRI 1B Ports on the Back of the MGC-25...
  • Page 81 You can set multiple tests to run at once, but they will run serially rather than simultaneously. Appendix A - Falcon Diagnostic Tool Slot A Main Control RS232 Network Module Cover Connectors MUSIC LINE IN COM 1...
  • Page 82 Summary pane, see “Test Results Pane” on page 1-72. 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.

  • Page 83: Test Results

    In the Test Selection window select the diagnostic tests to be performed. 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”...

  • Page 84: Disconnecting From The Falcon Diagnostic Tool

    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.

  • Page 85: Appendix - Adding An Mcu To The Network

    Enter the MCU password in the Password field. 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. Appendix A - Falcon Diagnostic Tool...

  • Page 86: Test Glossary

    MGC Release Notes - Version 7.5 Test Glossary The following Test Glossary describes the terms used in the diagnostic tests in the table: “Diagnostic Tests” on page 66. Table 12: Diagnostic Test Terms Test Term BCOD FPGA Proc QIFI Description An FPGA unit on the Video+ card.

  • Page 87: Log File Report Examples

    Log File Report Examples The following is an example of the Log File Report as it might appear after you run the Falcon diagnostic tool. Note log file lists initiation and end of tests that were run. Example Log Report 02/05/2005 15:30:00,937: *** Falcon Log File Created, version 1 02/05/2005 15:30:00,937: *** For MCU: 172.22.175.171 02/05/2005 15:30:00,937: **************************************...
  • Page 88 MGC Release Notes - Version 7.5 02/05/2005 15:31:31,338: MCU: startdiag.MuxPlus.4.END 02/05/2005 15:31:31,398: MCU: startdiag.MuxPlus.5.END 02/05/2005 15:31:31,398: MCU: settestlist.MuxPlus.4.CM.0.local_memory.23593045.lan.3932213.END 02/05/2005 15:31:31,398: MCU: settestlist.MuxPlus.5.CM.0.local_memory.23593045.lan.3932213.END 02/05/2005 15:31:31,408: MCU: settestlist.MuxPlus.4.proc4.4.clock.3932180.local_memory.7864412.neighbor.3932245.tdm.78643 42.full_memory.23593037.END 02/05/2005 15:31:32,39: MCU: settestlist.Audio+15.7.DSP.1.memory.39321692.clock.655444.END 02/05/2005 15:31:32,169: MCU: settestlist.MuxPlus.4.proc1.1.clock.3932180.local_memory.7864412.neighbor.3932245.tdm.78643 42.full_memory.39321677.END 02/05/2005 15:31:32,179: MCU: settestlist.MuxPlus.5.proc1.1.clock.3932180.local_memory.7864412.neighbor.3932245.tdm.78643 42.full_memory.39321677.END 02/05/2005 15:32:21,441: MCU: settestlist.IpPlus.2.CM.0.local_memory.19660885.END 02/05/2005 15:32:21,551: MCU: settestlist.IpPlus.3.CM.0.local_memory.19660885.END...
  • Page 89 02/05/2005 15:32:21,561: MCU: settestlist.IpPlus.9.proc1.1.clock.3932180.local_memory.7864412.neighbor.3932245.lan.393227 7.full_memory.39321677.END The IP+ card responds to the request from the Falcon diagnostic tool. Slot: 9 Unit: proc 1 Test Name: clock Test Flag: 3932180 Test Name: local memory Test Flag: 7864412 Test Name: neighbor Test Flag: 3932245 Test Name: lan Test Flag: 393277 Test Name: full memory Test Flag: 39321677 End of test for this car slot.
  • Page 90 MGC Release Notes - Version 7.5 02/05/2005 15:33:28,648: MCU: starttestind.39535.END 02/05/2005 15:33:44,501: MCU: keepalive.39535.END 02/05/2005 15:33:44,511: MCU: keepalive.39535.END 02/05/2005 15:33:44,511: MCU: keepalive.39535.END 02/05/2005 15:33:44,511: MCU: keepalive.39535.END 02/05/2005 15:34:27,814: Falcon: am 6 0 diag.gettestlist.service 02/05/2005 15:34:27,844: Falcon: am 10 0 diag.gettestlist.service 02/05/2005 15:35:21,792: Falcon: am 12 0 diag.starttestreq.pci.0.39536.1.0 02/05/2005 15:35:22,923: MCU: keepalive.39535.END 02/05/2005 15:35:22,923: MCU: keepalive.39535.END...
  • Page 91 02/05/2005 15:35:27,851: VIDEO+8 Deleted (Failed to receive card test list!) 02/05/2005 15:35:29,843: MCU: starttestind.39537.END 02/05/2005 15:35:29,853: MCU: finishtestind.39537.pass.END Falcon finishing neighbor (39537) test. 02/05/2005 15:35:29,853: MCU: starttestind.39536.END 02/05/2005 15:35:29,853: MCU: finishtestind.39536.pass.END 02/05/2005 15:35:29,853: MCU: starttestind.39536.END 02/05/2005 15:35:29,863: MCU: finishtestind.39536.pass.END 02/05/2005 15:35:29,863: MCU: starttestind.39536.END 02/05/2005 15:35:29,863: MCU: finishtestind.39536.pass.END 02/05/2005 15:35:29,873: MCU: starttestind.39536.END 02/05/2005 15:35:29,873: MCU: finishtestind.39536.pass.END...
  • Page 92 MGC Release Notes - Version 7.5 02/05/2005 15:37:02,37 : MCU: finishtestind.39536.pass.END 02/05/2005 15:37:02,568: Falcon: am 12 0 diag.stoptestreq.0.39536 02/05/2005 15:37:02,738: MCU: stoptestind.39536.END 02/05/2005 15:48:40,648: Falcon: mcpu_reset Falcon running pci (39536) test. Falcon stopping pci test. Falcon resets MCU.
  • Page 93 Appendix A - Falcon Diagnostic Tool 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.
  • Page 94 MGC Release Notes - Version 7.5...

This manual is also suitable for:

Mgc+50Mgc-25Mgc-50Mgc-100

Table of Contents