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

(1)

MGC-25/50/100

MGC+50/100

Release Notes

Version 7.5

(2)

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 e-mail to info@polycom.com.

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)

Version 7.5 - 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-100 ...12

MGC-25 ...13

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

Secure Socket Layer (SSL) ...25

H.239/People+Content Star Cascading ...30

(4)

HTTP File Transfer Mode ... 35

Detailed Description ... 35

Same Layout Option in Video Switching Conferences ... 36

Direct IP Dial-in ... 37

Direct End Point Dialing ... 37

IP to ISDN Gateway Call (without Gatekeeper) ... 37

SIP Factory ... 38

Nortel Environment Flag Settings ... 40

MGC+ Predefined IP only Entry Queues and Meeting Rooms ... 41

Corrections, Pending Issues and Limitations... 43

Corrections between Versions V.7.0.2 and V.7.5 ... 43

Corrections between Versions V.7.0.1 and V.7.0.2 ... 44

Corrections between Versions V.7.0 and V.7.0.1 ... 47

Version 7.5 Pending Issues ... 49

Version 7.5 System Limitations ... 54

Appendix A - Falcon Diagnostic Tool ... 65

Test Description ... 66

Starting the Falcon Diagnostic Tool ... 70

Falcon Main Window ... 70

Setting the Log Files Path ... 73

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

(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 Feature Name Description

1. Video H.264 SD/HD in Video Switching 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.

2. Video Increased Frame Rate in H.264 CP conferences

Higher Frame rates in H.264 CP conferences. The MCU now supports frame rates up to 30 FPS in CP conferences.

MAX_H264_CP_FR=30 (Default = 25)

3. Video H.264 up to 2 Mbps in VideoSwitching Conferences

In H.264 VideoSwitching Conferences, the maximum Line Rate capability is 1920 Kbps.

Supported in MGC version 7.03.

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

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.

6. IP H.323 dial-out automatic redial

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.

(6)

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, Table 1: New Features List (Continued)

(7)

Version 7.5 - New Features List

13. Microsoft LCS support

(con’t)

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.

14. IP IP Bridge Higher Capacity

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

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.

18. General Secure Socket Layer (SSL)

SSL (Secure Socket Layer) enables secure HTTP connection on MCU’s with XPEK Operating Systems. Available on the MGC Manager, WebCommander and API calls.

19. General H.239/People+Content Star Cascading

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

A “Faulty” participant connected to a conference has their background color marked red for improved visibility.

22. General HTTP File Transfer Transfer of files using HTTP mode can Table 1: New Features List (Continued)

(8)

24. General Circular Resource Mapping

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.

CIRCULAR_MAPPING_MODE_FOR_ AUDIO_VIDEO_PLUS=YES (default =YES).

25. General MGC+ Predefined IP Only Entry Queues and Meeting Rooms

The MGC+ unit is shipped with two Entry Queues and eight Meeting Rooms and the appropriate EQ and IVR Services.

26. General New Diagnostic tool (Falcon)

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. Table 1: New Features List (Continued)

(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

(10)

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+100

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

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

(11)

Prior to Installation and SW Upgrade

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

MGC-25

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

# Board Type H/W

(12)

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

(13)

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)

(14)

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.

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

(16)

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 P O L YCO M R WA R N IN G P rod uc t w a rra n ty w ill be v o id if s e a l la be l is re mo ved o r d a mag e d .

(17)

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

(18)

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.

(19)

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.

(20)

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.

(21)

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.

(22)

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.

(23)

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.

(24)

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

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

Figure 3: Setting tab with Start conf Requires Chairperson checkbox SIP participants cannot view the Welcome slide.

(26)

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.

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

(28)

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.

(29)

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.

(30)

4. 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, http:// www.thawte.com 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 E-mail. 7. When the E-mail 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

(31)

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.

(32)

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=443 3. Click OK and then reset the MCU.

4. Right-click the MCU icon and then click Properties.

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.

Do not connect to the MCU. When you right-click the MCU, the MCU should be disconnected and the icon appear grey.

(33)

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

(34)

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.

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.

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.

(35)

Ad Hoc Auto Cascade

The Auto Cascade feature enables automatic cascading of conferences. Both audio only and video conferences can be cascaded.

Detailed Description

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.

(36)

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

(37)

“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_11.11.11.11_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.

(38)

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.

(39)

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.

(40)

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.

(41)

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: 172.22.190.162##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: 172.22.190.162 as the call address and 1234 (conference NID) in the

Extension field, or 172.22.190.162 as destination IPaddress and 3116##1234 (i.e. ED

NID - 3116, Conf. NID - 1234) 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 (172.21.11.14##63*0141321800).

(42)

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

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.

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.

(43)

— 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

(44)

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

(45)

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

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

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

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.

(46)

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.

(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 Description ID# Remarks

1. Audio+ In an Encrypted VS conference with 96 Dial-out and 96 Dial-in participants, the Audio+ cards crashed.

20460

2. Cascade Video Switching, H.261 Fixed, 384Kbps and H239/P+C defined conferences may suffer from bad video quality.

20975

3. CP In a CP conference with a PSTN participant, the speaker indication disappears.

20375

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

20317

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.

20452

6. H.239 Connecting 12 H.239 participants to an MG323 board causes the card to crash.

20458

7. Meeting Rooms When a conference is defined as a Meeting Room, it takes over two minutes to receive any indication from MGC Manager.

21248

8. MGC Manager Endpoints appear as “faulty connected” during the first seconds of connection.

20382

9. Microsoft During an On Going conference participants from a previous conference are listed.

21472

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)

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

1. Audio On an MCU with simultaneous conferences, audio can be heard from another conference.

20071

2. Audio When many participants are detected as having a Noisy Line, other participants cannot connect to the Audio+ card.

19424

3. Cascade In Cascaded Video Switching conferences with a leased line link inconsistent switching between speaker and participants can occur.

20161

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.

17373 Connect first the Cascading link.

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.

17390

6. Cisco IP Phone endpoint

No Audio or Video when using Cisco IP phone.

20566 20557

7. CP In a H.264 conference, iPower set to a desktop mode causes video

fragmentation.

18483

8. CP During a CP conference participants with long names disconnect.

20515

9. CP In a CP conference with 2x2 layout, video forcing is not implemented.

20570

10. Encryption In Encrypted conferences no resources available for Encrypted participants allocated on IP+ cards with

(49)

13. Falcon The Falcon application crashes after downloading diagnostic traces on the MGC-25.

20469

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

19118

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.

19945 Set the system.cfg flag to YES.

17. General In the Participants Queue the operator cannot attend the next participant. The message "No Party in Participants Queue" appears.

20141

18. General Version default password and connectivity issues when upgrading: V.5 to V.6 & V.5 to V.7.

20283

19. General When an operator joins the conference, the conference terminates.

20511

20. H.239 In an IP conference Sony endpoints do not open the Content channel.

19673

21. H.239 After sending content in ISDN, the H.239 channel does not open.

20565

22. H.239 Slave conferences cannot receive content from the Master conference on the MGC-25.

20649

23. IP Alias names for IP participants increased to 100 characters.

20481

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

16625 Table 4: Corrections between Versions V.7.0.1 and V.7.0.2

(50)

25. MGC Manager When using MCU port 5001,

conference names are not displayed in the IP card properties.

20294

26. MGC-25 When using the Fast Configuration Wizard, the MGC Manager crashes while configuring the ISDN Network Service.

20584

27. MPI Synchronization improvements on the RTS signal.

—

28. MPI An MPI endpoint connected as Direct appear as dial-in the MGC Manager.

20371

29. MUX+ Connecting more than 15 ISDN H.239 VSX endpoints to a conference may cause the MUX+40 card to crash.

20427 20545 20528

30. SIP During an Invite session the Session Description Protocol mutes the audio of the participant.

20599

31. SIP When dialing-in to an On Going conference the IP+48 card crashes.

20561

32. T1-CAS An exception occurs after a T1-CAS participant dial-in (Audio Only).

20246

33. T1-CAS During Audio Only conferences T1-CAS dial-out participants cannot connect.

20257

34. Video When moving a video muted participant, the participant is

automatically unmuted after the move to the new conference

20327 Table 4: Corrections between Versions V.7.0.1 and V.7.0.2

(51)

Corrections between Versions V.7.0 and V.7.0.1

Table 5: Corrections between Versions V.7.0 and V.7.0.1

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.

14821

2. Audio+ After 40 cycles of starting and

terminating a conference that includes many participants, the Audio+96 card may crash.

19930

3. Cascading Error messages are displayed when cascading conferences run on MGC MCU and Tandberg MCU.

13345

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.

17326

5. Cascading Asserts may occur when connecting cascading conferences in H.323.

19802

6. COP In a conference set to H.264, when endpoints connect the frame rate decreases.

19602 This is an endpoint issue and not the MCU’s

7. COP In a CoP conference disconnecting a participant, video loss (Video Out 0) to all conference participants may occur.

19838

8. CP In a H.263 conference, after changing layouts of participants and speaker no outgoing video stream is sent.

19413

9. CP A H.263, FECC conference with a line rate set to 786Kb may have a

fragmentary video.

19452

10. CP With H.264 and XGA Video Format conference settings, the video+ card may crash.

19535

11. CP In an H.263 conference, after changing layouts of participants and speaker the Video card may crash.

(52)

13. H.323 An exception may occur when connecting more than 96 H.323 participants in a blast dial-out conference.

19887

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

17571

15. Lecture Mode - CP conference

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.

17571

16. MGC Manager When creating a new Network Service, after adding 10 different Spans, the

19939

17. MGC Manager In the MGC Manager monitoring pane refresh problems may cause wrong endpoint status.

19860

18. MGC Manager No 'Faulty connection' indication in the MGC Manager application.

20194

19. Video A blue screen is displayed for 1-1.5 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.

16032

20. Video Conferences with 4CIF or higher Video Formats may encountered brief video interruptions.

19462

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.

18991 This is an endpoint issue and not the MCU’s.

22. Video In a conference set to 256Kb line rate, 19680 Table 5: Corrections between Versions V.7.0 and V.7.0.1

(53)

Version 7.5 Pending Issues

Table 6: Pending Issues

1. Audio When using the G.729 audio algorithm, no audio available with VoIP or SIP phones.

20554

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

20299

4. Content All the participants Status becomes Faulty Connected when PVX endpoints send Content.

21569

5. COP When the first active participant is disconnected and the video of other participants is muted, participants view background colors.

19288

6. CP MCU status changes to Major for 30 seconds when connecting 32 endpoints at a line rate of E1 to a CP conference.

20331

7. CP In a CP Quad Views conference with more than 12 H.264 participants, the frame rate may decrease.

20553

8. CP Fragmented Video can occur during speaker changes in CP H.264 conferences.

21311

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.

21142 Save the participant under a new name, and then, if required, delete it from the database.

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.

(54)

13. FECC FECC does not work between an IP endpoint and an MPI (DTE) endpoint.

20401

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.

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

20477

16. Gateway When connecting conferences using the Gateway when you move a participant to and from a conference, no video is seen.

19469

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.

20232

18. General When moving a participant from one conference to another, the “First to join” IVR message is heard twice.

19515

19. General The 'Auto_Redial' parameters in 'confer.cfg' file are not updated.

20897 Require MCU restart in order for changes to take effect.

20. General Creating a conference with parameters "enable invite" and "encryption", the invitees are rejected.

21097

21. General SilenceIT algorithm does not

automatically mute participants placing their line on hold, hence background music is played to the conference.

21960

22. H.264 In Video Switching conference set to 21207 Table 6: Pending Issues (Continued)

(55)

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

20685 Reconfigure the ISDN clock.

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.

20932

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.

— Set the system.cfg (MCU_CLOCKING section) flag: INTERNAL_CLOCK = YES prior to setting the ISDN span to Null.

27. IP+ After participants disconnect from a conference, the LED on the card is still On (Active).

17890

28. IPower IPower fails to send content in a CP conference set to Auto, H.239 P+C and dial out.

21066

29. MGC Manager In the H.245 Properties dialog box, when H.239 is used, P+C is indicated instead.

20468

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.

20933

31. MGC Manager On an XPEK MCU, when extreme packet loss occurs, the MGC Manager can loose connection with the MCU.

21519

32. MGC-25 The Resource Report does not display IP capacities for line rates of 256 Kbps and 512 Kbps.

18307

33. MGC-25 Moving 3 IP participants from CP Quad View to a CP COP Quad View

conference fails on the MGC25.

20926 Move

participants one at a time. Table 6: Pending Issues (Continued)

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

MGC-25/50/100

MGC+50/100

Release Notes

Version 7.5

Table of Contents

Version 7.5 - New Features List... 1

Version 7.5 Upgrade Package Contents... 5

Prior to Installation and SW Upgrade ... 6

Software Upgrade Procedure ... 10

Detailed Description - Video ... 21

Detailed Description - General ... 23

Corrections, Pending Issues and Limitations... 43

Appendix A - Falcon Diagnostic Tool ... 65

Version 7.5 - New Features List

Version 7.5 Upgrade Package Contents

Prior to Installation and SW Upgrade

Hardware Update Notice

Control Unit Update Notice

Version 7.5 Interoperability Table

Software Upgrade Procedure

Upgrade Checklist

MCU Disk Space Verification

Dongle Upgrade

Dongle Information

Downloading the Dongle File

Installing the Dongle File

MGC Unit Software Upgrade Procedure

Upgrading from a Version using Password for Entry Queue Routing

Upgrading from a Version using Numeric ID for Entry Queue Routing

Removal of Redundant Configuration Files

Downloading the Software to the MCU

Installing the MGC Manager Software

Manual Installation of the Default Message Services

Updating the Entry Queue Services

Detailed Description - Video

Video Support for Start Conference requires Chairperson

Detailed Description

Detailed Description - General

Network Time Protocol (NTP) for XPEK Systems

Detailed Description

Secure Socket Layer (SSL)

Detailed Description

H.239/People+Content Star Cascading

Detailed Description

Ad Hoc Auto Cascade

Detailed Description

Limitations

Faulty Participant in Red

Detailed Description

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

Corrections between Versions V.7.0.2 and V.7.5

Corrections between Versions V.7.0.1 and V.7.0.2

Corrections between Versions V.7.0 and V.7.0.1

Version 7.5 Pending Issues