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 3.5.1.2
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 4.0.1 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 2.0.1.8 (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 6.02.03 and 7.0 (tested in version 7.01) Endpoints
Prior to Installation and SW Upgrade
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
Polycom VSX7000 7.52 and 8.0
Polycom VSX8000 7.52 and 8.0
Polycom iPower 600 6.0.315
Polycom iPower 900 6.0.315
Polycom iPower 9000 6.0.315
Aethra VegaStar Gold 5.1.15 (tested in version 7.01)
Sony PCS1 2.30 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 MC8000 4.6 (tested in version 7.01)
Table 1: Version 7.5 Interoperability List (Continued)
Device Version
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 5.
3. Removing a redundant configuration file see “Removal of Redundant Configuration Files” on page 17
4. 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 12.
6. Install the new MCU version. For details see “MGC Unit Software Upgrade Procedure” on page 16.
7. 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 19.
9. 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.
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
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.
ALARMS COM2
COM1 KEYBOARD MOUSE VGA LAN
POLYCOMR
WARNING
Product warranty willbe void if seal label isremoved or damaged.
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.
e-mail). If the numbers do not match, do not proceed with the upgrade process and contact support.
Downloading the Dongle File
Prior to accessing the Polycom Resource Center Web site, retrieve from the MCU the system serial number.
• The MCU-25/50/100 have a Polycom label with a Serial No. fixed on the rear panel.
To retrieve the Dongle File from a Polycom Web Site:
Access the Polycom Resource Center web site http://extranet.polycom.com/csnprod/
signon.html.
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.
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.
Software Upgrade Procedure
6. Click Download.
Save the new dongle file.
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.
When the following error message appears: “No Maintenance Agreement Found/
MGC Serial Number not Found”, please contact your next level of support.
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.
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”.
2. To route participants from the Entry Queue to the destination conference using the conference or chairperson password, you must modify the system.cfg file included in the software kit:
a. 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 7.5.
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.
Entry Queue Password routing mode is required to run PCS version 7.0.0.
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.
2. Click OK.
The Software Installation dialog box opens.
The MCU software will be installed on each listed MCU.
3. Select the Install Default Services check box to download the default IVR Service, Entry Queue Service, and Gateway Service. The default IVR Service is in English and is named IVR70. The default Entry Queue Service is in English and is named EQ70.
You can manually install the default English IVR Service and Entry Queue Service or the English and Spanish IVR and Entry Queue Services. For more information, see
“Installing the MGC Manager Software” on page 19.
4. You can download software to all MCUs listed in the MCU List in one operation. If the list is not complete, you can add MCUs to the list by clicking the Add MCU button.
To avoid downloading the software to an MCU, remove the MCU from the list by selecting the MCU Name, and then clicking the Remove MCU button. For more details, see the MGC Administrator’s Guide, Chapter 2.
5. 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.
6. 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.
You need to select the folder containing the latest version number, and not the sub-folder labeled Disk 1.
• 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.
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.
Updating the Entry Queue Services
When upgrading from Version 5.x to Version 7.5 you need to update the Entry Queue Service to include the appropriate voice messages.
To update the Entry Queue Service:
1. Expand the IVR Message Services list (under the MCU Configuration list).
2. Right-click the icon of Entry Queue Service to update (an Entry Queue Service that was defined in version 5.x), and then click Properties.
The Entry Queue Message Service - General dialog box opens.
3. Click the Conference ID/Password tab.
4. In the Entry Queue Message Service - Conference ID/Password dialog box, assign the following voice messages:
— Using Conference Password for Entry Queue Routing (Version 5.x mode):
• Request Conference ID/Password: CONFPASS.ACA
• Join Failure Message: CONFRTRY.ACA
These files are located in the MGC software kit (as part of the default IVR Service for Version 7.5), in the following path:
MGC50-100 Version 7.5\MGC SW CD Ver 7.5\IVR\Default Services\English V7 IVR\msg\LANG70\NID\NUMID.
— Using Conference Numeric ID for Entry Queue Routing:
• Request Conference ID/Password: CNFIDRQS.ACA
• Join Failure Message: CNFIDFL.ACA
These voice messages are located in the MGC software kit (as part of the default IVR Service for Version 7.5).
5. Click OK to save the changes.
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.
Figure 3: Setting tab with Start conf Requires Chairperson checkbox SIP participants cannot view the Welcome slide.
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.
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.
The MCU GMT Time dialog box opens.
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.
You cannot set the MCU’s time or connect to the NTP server, when there are On Going conferences on the bridge.
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 Description
Country Enter any 2 letter code for the country name.
State or Province Enter the full name of the state or province.
Locality Enter the full name of the town/city/location.
Organization Enter the full name of your organization for which the certificate will be issued.
Organizational Unit Enter the full name of the unit (group or division)
4. Click Apply.
The new certificate request appears in the details box.
The new certificate request appears in the details box.