webcommander release notes 7.7

MGC WebCommanderRelease Notes

Version 7.5

January 2006DOC2135A

Copyright @ 2006 Polycom, Inc.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.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 [email protected].

Catalog No. DOC2135A Version 7.5

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

ContentsVersion 7.5 - New Features List............................................................1Version 7.5 Package Contents .............................................................2

MGC Web Server Requirements ............................................................................2

Installing the MGC WebCommander Software Package....................3Prior to Installation and Software Upgrade ...................................................................3

Backing Up the SQL/MSDE Database ..................................................................3Backing up the Access Database ............................................................................5

Software Installation ......................................................................................................6Installation Wizard ...........................................................................................6Product Upgrade Version 7.5 ...........................................................................8

Defining the MGC Web Server Security Properties ................................................... 10Selecting the User Account for Accessing the MGC Web Server ...............................10

Starting up the Server ....................................................................................12Selecting the User Account for Accessing the WAM Server ..................................... 13

Starting up the WAM Server ................................................................................13Optimizing E-mail Delivery on the Server ...........................................................13

Integrating Polycom PathNavigator ............................................................................ 13

Updating the Database........................................................................14Version 7.5 - WebCommander Features............................................17

Auto Cascade ...............................................................................................................17Detailed Description .............................................................................................17

Auto Cascade Configuration ..........................................................................17Auto Cascading Mechanisms .........................................................................20

Limitations ............................................................................................................21H.239/People+Content Star Cascading ........................................................................22

Detailed Description .............................................................................................22SSL (Secure Socket Layer) ..........................................................................................23

Detailed Description .............................................................................................23Same Layout Option in Video Switching Conferences ...............................................27

Detailed Description .............................................................................................27

Version 7.5 - Corrections, Limitations and Pending Issues ............28Corrections between Versions 7.0 and 7.5 ...................................................................28Corrections between Versions 6.01 and 7.0 .................................................................29Version 7.5 System Limitations ...................................................................................33Pending Issues Version 7.5 ..........................................................................................35

i

MGC WebCommander Release Notes - Version 7.5

ii

Version 7.5 - New Features List

Version 7.5 - New Features List

The following table lists the new features in version 7.5.

Category Feature Name Description

WebCommander - Specific Features

1. General Ad Hoc Auto Cascade Conferences can be automatically cascaded. When an identical Numeric ID is used for each conference, the WebCommander Professional automatically cascades each conference and creates the required links.

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

H.239/People+Content Star Cascading is available with H.320 & H.323 and Video Switching conferences.

3. General SSL (Secure Socket Layer)

SSL (Secure Socket Layer) enables secure HTTP connection to MCU’s with XPEK Operating Systems.

4. General Same Layout Option in Video Switching Conferences

Video Switching conferences support the Same Layout mode.

MGC Web Server and Personal Scheduler Features

5. General New languages New languages, Polish and Swedish have been added to the MGC WebCommander and Personal Scheduler applications.

1


Version 7.5 Package Contents

Version 7.5 software and documentation CD includes the following items:• MGC WebCommander software:

— MGC Web Server— MGC Web Server Manager— WebCommander Configuration application— MGC Personal Scheduler Client Installation

• Documentation PDF format:— MGC Web Server Manager Installation and Configuration Guide— MGC Web Server Manager User’s Guide— MGC WebCommander User’s Guide— MGC Personal Scheduler Quick Start Guide— Version 7.5 Release Notes

MGC Web Server RequirementsThe MGC Web Server requirements are as follows:• Pentium III, 400MHz (or higher) processor• 256 MB RAM• Windows NT Server, Windows 2000 Server, or Windows 2000 Advanced Server,

Windows 2003 Server (the last three are mandatory for Japanese and Chinese language support)

• Microsoft IIS version 4.0 with Service Pack 4.0. For Japanese and Chinese language support, Microsoft IIS version 5.0 with Service Pack 1.0 is required.

• Free hard disk space:— For MGC Web Server Manager application: 20 MB— For Database records: 30 MB— If SQL server is installed: 200 MB

• Database Software:— With the WebCommander and MGC Personal Scheduler it is recommended to use

Microsoft SQL Server database. Microsoft Access can be used for the MGC Manager application

— When integrating the Polycom PathNavigator database, use the Microsoft SQL Server version 7.0 or the SQL 2000 application. In this case, Windows NT Service Pack 4.0 or later is required.

• 15” SVGA monitor, 600 x 800 pixels resolution. Recommended: 17” monitor

2

Installing the MGC WebCommander Software Package


Prior to Installation and Software Upgrade

If you are upgrading from a previous version, it is recommended to backup the SQLMSDE or Access database.

Backing Up the SQL/MSDE DatabaseTo backup the SQL/MSDE database:1. On the Start-Programs menu, click Microsoft SQL Server and then Enterprise

Manager.

The SQL Server Enterprise Manager window opens.2. Click the [+] icon next to Microsoft SQL Server to expand the list.

3. Click the [+] icon next to SQL Server Group to expand the list.

4. Click the [+] icon next to <PC Name> to expand the list.

3


5. Right-click the Databases folder icon. On the pop-up menu click All Tasks, and then select Backup Database.

The SQL Server Backup – General dialog box opens.6. On the General tab, select a database from the list and enter a name for the backup file,

select a backup destination folder and click OK.

When the backup process is completed, the SQL Server Enterprise Manager message is displayed, indicating the backup operation was completed successfully.

4


7. Click OK.

The new backup file is located in the destination folder selected in step 6.

Backing up the Access DatabaseTo backup the Access database:1. Open the folder where the database resides.

2. Select the database file by clicking it.

3. From the Edit menu, select Copy, and then select Paste.

4. The backup database file called Copy of <database_name>, appears in the same folder as the original database. This file can be moved to any folder.

5


Software Installation

The Installation Wizard guides you through the installation process for the MGC Web Server.

If installing from FTP:1. Download the software from the FTP site and unzip the files.

2. Open Windows Explorer and browse to the directory that contains the MGC WebCommander diskettes.

3. Expand the Disk 1 folder and double-click the Setup.exe file.

The Installation Wizard Welcome screen opens.

If installing from a CD:1. Insert the CD into the CD drive.

2. From the Start menu, select Run.

3. In the Run dialog box, enter D:Setup, where D is the CD drive name, and then click OK.

The Installation Wizard Welcome screen opens.

Installation Wizard

Follow the on-screen instructions to complete the installation procedure.1. From the “Polycom Resource Center’s Website” retrieve the KeyCode information by

accessing the Activate Your Product - Retrieve Software Key Code dialog box and select Software Upgrade Key Code.

2. In the Software License Agreement window, click Yes to accept and continue.The Question dialog box appears.

The installer must have administrator rights or domain administration rights to install software. It is also important that the password used to access the domain is permanent and does not expire after 90 days.

6


3. Double-click the WebCommander setup icon. The Enter License Information window opens.

a. Click Polycom Resource Center to register your product and retrieve the Key Code

b. In the License field enter the code located on the Product CD

c. In the Key Code field enter the product code retrieved from the Polycom website.

4. Click OK and continue the installation setup.The Software License Agreement window appears.

5. Click Yes, to accept and continue.

In certain instances the following dialog box appears.

Click Yes, to upgrade your MDAC version and continue the installation. Windows automatically reboots after the MDAC installation, and the WebCommander installation setup restarts automatically.

7


Product Upgrade Version 7.5

1. In the Software License Agreement window, click Yes to accept and continue.The Question dialog box appears.

2. Click Yes. The Enter License Information window opens.

— Click Polycom Resource Center to register your product on the Polycom Website and retrieve the Key Code

— In the License field enter the code located on the Product CD— In the Key Code field enter the product code retrieved from the Polycom website

3. Click Yes to use the existing product license and continue the installation setup.The Welcome window opens.

4. Click Next.The User Information window opens.

5. Enter the user Name and Company details and click Next.The Setup Type window opens, listing the products according to the purchased package.

6. Select the appropriate product type as follows:

• Client – Installs the MGC Web Server Manager application on a computer other than the server for remote access to the MGC Web Server.

• MGC Personal Scheduler – Installs the MGC Web Server and MGC Web Server Manager applications that enable users to define, modify, and start reservations via the Web or Microsoft Outlook.

• Meeting Director Server - Installs the MGC Web Server and MGC Web Server Manager applications that controls and manages On Going conferences via the Web. This module enables users to monitor the ongoing conference status, and perform various operations.

• Professional Server – Installs the MGC Personal Scheduler and the Meeting Director Server components to enable full functionality from the Web, and conference scheduling from Microsoft Outlook. This installation allows users to

8


schedule and start reservations, monitor, and control On Going conferences from the Web.

7. Click Next.The Choose Destination Location window opens.

8. Select the target path for the installation (it is recommended to accept the suggested path and directory name) and click Next.The Select Programs Folder window opens.

9. Click Next to accept the suggested group folder and name and start downloading the software files. When the download is complete, a dialog box appears, prompting you whether to configure the PathNavigator gatekeeper. For more information see the Software Installation section in the MGC Web Manager Installation and Configuration Guide.

10. Select:

— Yes, to automatically configure the link to the PathNavigator Gatekeeper. Proceed with step 12.

— No, if no PathNavigator gatekeeper is installed in your environment, or to manually define the link to the PathNavigator. Proceed with step 13.

11. If you have selected Yes, the Select Components window opens.The following options are available:

— Specify is the default setting. It enables you to manually define the link to the PathNavigator gatekeeper.

— Automatically lets the WebCommander search for a PathNavigator database on all the SQL servers installed in the local domain and automatically create the link between them.

a. To manually select the PathNavigator gatekeeper server, click Next.The Enter Information window opens.

• Enter the name of the PathNavigator gatekeeper server, and click Next.• A confirmation dialog box (Server found) opens. Click OK.

b. Select Automatically to let the system to detect automatically select the PathNavigator gatekeeper, and click Next.A confirmation dialog box opens.

12. Click Yes, then choose the Select a PathNavigator Database dialog box, listing the SQL Servers found in the local domain.

13. Select the required PathNavigator Server, and then click Next.

14. The Site alias name window opens.The site Alias name automatically redirects participants to the correct Web site in the event that the address changes (for instance, when upgrading to a higher version). For example, the alias entered to go to the Web site can be abcABC, where abcABC is the IP address of the WebCommander server.

15. Enter the site Alias name and then click Next.

The Setup Complete window opens.16. At the end of the installation, click Finish to complete the installation procedure and

exit the Setup Wizard.

Sometimes the error message “Cannot Create Application” appears at the end of the installation. This error message may appear when there are two Web sites installed in the system. In this case, you need to manually create and configure the ConfSiteV7_5 and ConfPollerSiteV7_5 in the IIS application.

9


Defining the MGC Web Server Security PropertiesThe security properties of the MGC Web Server must be defined to allow access to the Server. For more information see, Defining the MGC Web Server Security Properties in the MGC Web Manager Installation and Configuration Guide.

Selecting the User Account for Accessing the MGC Web Server

The Web Server application is installed during the WebCommander installation process. When using a local database, there is no need to define the Web Server security properties. All other definitions require setting the properties of the Web Server.

To select the user account in Windows 2000/2003 Server:1. On the Start - Programs menu, click Administrative Tools, and then click Services.

The Services window opens.2. Right-click OperSrvV7_5, and then click Properties.

The OperSrvV7_5 Properties (Local Computer) dialog box opens.3. Click the Log On tab.

4. Select This account to select the user with access to the MGC WebCommander Server.

10


5. Click the Browse button to select the user name.

The Select User dialog box opens.6. Select the user name from the list, and then click OK.

The system returns to the OperSrvV7_5 Properties (Local Computer) dialog box.7. Enter the user password in the Password field.

8. Enter the user password again in the Confirm Password field.

9. Click OK.A confirmation box opens.

10. Click OK to confirm and complete this procedure.

11


Starting up the Server

When the application is installed, the server is started automatically. Manual start of the server is only required when the password is changed or for troubleshooting.

To start up the Server in Windows 2000/2003 Server:1. On the Start - Programs menu, click Administrative Tools, and then click Services.

The Services window opens.2. Right-click OperSrvV7_5, and then click Start on the pop-up menu.

The Service Control box opens, indicating that Windows is attempting to start the OperSrvV7_5 service.

12


3. In the Services dialog box, the status of the service changes to “Started”.

Selecting the User Account for Accessing the WAM Server

By default, the WAM Server is installed during the WebCommander installation process. When using a local database, there is no need to define the WAM Server security properties. All other definitions require setting the properties of the WAM Server. For more information see, Selecting the User Account for Accessing the WAM Server in the MGC Web Manager Installation and Configuration Guide.

Starting up the WAM ServerWhen the application is installed, the server is started automatically. When a PathNavigator gatekeeper is present on the network, there is no need to define the WAM Server security properties. With SQL Authentication however, configuration of the WAM server is required when no PathNavigator is present on the network. A manual start of the server is also required when the password is changed or when troubleshooting the server. For more information see, Starting up the WAM Server in the MGC Web Manager Installation and Configuration Guide.

Optimizing E-mail Delivery on the ServerYou can Optimize e-mail Delivery on your Server. For more information see, Optimizing E-mail Delivery on the Server in the MGC Web Manager Installation and Configuration Guide.

Integrating Polycom PathNavigatorWhen the Polycom PathNavigator is installed in your enterprise you can access the endpoints registered with the PathNavigator via the WebCommander. For more information see, Integrating Polycom PathNavigator in the MGC Web Manager Installation and Configuration Guide.

13


Updating the Database

When upgrading from a previous version of the MGC Web Server Manager, the old database is saved during the installation procedure.

At the end of the installation procedure, you must access the MGC Web Server Manager application to automatically update the database.

To update the database:1. On the Start – Programs menu, click MGC Web Manager Ver7.5, and then click

MGC Web Server Manager.

The Database Login dialog box opens.

2. Enter your Login Name and Password as defined in the database and click Login.

3. If there are discrepancies in the number of fields between the old and the new databases, the system prompts whether to update the existing database to the new format.

4. Click Yes to automatically update the database (recommended), or No to leave the database unchanged.

If you select No, new entries added to the database via the MGC Web Server Manager will not be saved.

However, it is recommended that you back-up the database before updating the database.

• The procedure for updating the database is the same for Windows 2000, Window 2003 and Windows NT.

The default Login Name is admin1. The default Password is 123. The system automatically starts the update process.

14

Updating the Database

If you select Yes, the UpdateDB dialog box opens, indicating which databases require updating.

Updating all the databases you intend to use is recommended.To cancel the update of a database, clear the check mark next to the database.

5. Click Apply to update the selected databases.The updating process may take time, depending on the size of the database. At the end of the process, an Update Database Results dialog box may open, listing the fields that were updated.

6. Click OK to return to the UpdateDB dialog box.

Click Cancel to close the dialog box and exit the update process.

On computers that support Unicode, this dialog box does not appear.

15


• When upgrading from a previous version which did not support Groups, the Update Database process - automatically performed by the Server Manager - creates a group for each listed user, and retains the access rights defined for a user as the access rights to that group.

• Participant templates and Conference templates are automatically assigned to the Root directory; therefore, only users who have access rights to the root directory (usually administrators) are able to view these conferences. The templates can be moved to the appropriate group in the Groups tree in the MGC Manager – Database Manager segment, using Copy and Paste (drag & drop is not available).

• When you open the MGC Web Server Manager for the first time after an upgrade, and you have not yet updated the database, you can do it later using the dB’s to Update from the Options menu.

16

Version 7.5 - WebCommander Features


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 which monitors the MCUs. The Ad Hoc Cascade is installed as part of the MGC WebCommander Professional installation. 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. If there are no cascading links, it will automatically connect the conferences 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 will add this conference to the cascaded conferences.The links between the MCUs and other configuration parameters are defined using the MGC Web Server Manager. A primary link is defined between each pair of MCUs to be included in the Auto Cascade. A secondary link can optionally be defined for use as a backup configuration if the primary link fails.

Auto Cascade Configuration

The configuration of the Auto Cascading environment involves configuration in both the MGC Web Server Manager and in the MGC Manager application.• In the MGC Web Server Manager you define the Cascading Links in the Auto Cascade

configuration table. You define the type of link to be set up between the conferences on the different MCUs, such as IP or ISDN, the direction of the link, and the connection string to be used to set up the link.

• In the MGC Manager application you define an Auto Cascade Entry Queue on each MCU. You can create one Entry Queue for both ISDN and IP, or two separate Entry Queues. To set up the links, the external application will dial the Entry Queue dial-in number (for ISDN connection) or the Network Service Prefix and Entry Queue Numeric ID (for IP connection) followed by the Conference Numeric ID. Calls to Auto Cascade Entry Queues will be considered as MCU calls and no IVR will be played.

MGC WebCommander Professional installation is required. You are required to install and configure the WebCommander and Web Server Manager application. On the MGC Manager you are required to configure the Entry Queue for Ad Hoc Cascading.

It is recommended to set up identical Ad Hoc Entry Queues and Profiles on each MCU, so that the cascaded conferences will have the same properties.

17


Defining Auto Cascading Entry QueuesTo eliminate IVR prompts when Auto Cascade links are being created, you must set up Auto Cascade Entry Queues on each MCU.

To define an Auto Cascade Entry Queue: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 on all the MCUs.

3. Leave the Ad Hoc check box cleared.

4. Proceed to configure the Entry Queue as for any other Entry Queue.

Configuring the Cascading Links using the Web Server Manager

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

Before configuring Cascading Links, you must define all the MCUs included in the Auto Cascading environment in the Web Server Manager. For details see the MGC Web Server Manager User’s Guide.

18


To Configure the MCU Cascade Links:1. In the main Web Server Manager window, select the database assigned as the Global

Default.

2. On the Options menu, click Auto Cascade Configuration.

The Cascade Links List dialog box opens. 3. Select the Enable Cascade Links check box.

The dialog box is automatically filled with a list of primary and secondary links between each two MCUs defined in the MCUs table of the Web Server Manager.

4. To enable the links, you must define the link direction and network type to be used for the connection, and the connection string. You must complete the definition for the primary links, and can optionally complete the definition for the secondary links.

Each row in the Cascade Links List contains the following columns.

The Auto Cascade feature can only be implemented for the database assigned as the Global Default in the Web Server Manager. To assign a database as the Global Default, right-click on the database and select the Set as Global default option.

Table 1-1: Cascade Links List Parameters

Column Description

Link Priority Indicates whether this row contains a primary or secondary link definition.

Source MCU The name and IP address of the first MCU.

Direction Contains an icon indicating the direction of the link between the MCUs, as follows:

The destination MCU dials to the source MCU.

The source MCU dials to the destination MCU.

Click the icon to reverse the link direction.

Destination MCU The name and IP address of the second MCU.

19


5. In the Redial Attempts field, specify the number of redial attempts to be made when an Auto Cascade link fails.

6. To enable implementation of the “start only when the chairperson connects” and “terminate conference after the chairperson exits” features over Auto Cascaded conferences, select the Chairperson Activation check box.

7. Click OK.

Auto Cascading Mechanisms

Selection of the Master ConferenceThe conferences are cascaded in a star configuration - one master and up to five slaves. The master conference is selected when cascading first takes place between two or more conferences. If chairperson activation is enabled in the Auto Cascade configuration in the MGC Web Server Manager, then the master conference is determined as follows:• If one of the conferences has a participant who is defined as a chairperson, and none of

the other conferences has a chairperson, the conference with the chairperson will be assigned as the master conference.

• If none of the conferences has a chairperson, then the conference that is running on the MCU which is highest in the MCUs table in the Web Server Manager will be assigned as the master conference.

• If there is more than one conference with a chairperson, then the conference with a chairperson that is running on the MCU which is highest in the MCUs table in the Web Server Manager will be assigned as the master conference.

If chairperson activation is disabled, then the conference that is running on the MCU which is highest in the MCUs table in the Web Server Manager will be assigned as the master conference.

Implementation of Chairperson DTMF featuresThe following chairperson DTMF actions are implemented across the MCUs: • Mute all but me• Terminate the conference• Place the conference on hold• Lock and unlock the conference• Secure the conference and release a secured conference

Network Type The type of connection to be set up between the MCUS.Select the network type from the drop down list. The possible values are: ISDN, IP (H.323), MPI, SIP or T1-CAS.

Connection String The connection string to the Auto Cascade Entry Queue.Enter the connection string as follows:• For ISDN and MPI, specify the Entry Queue dial-in

number.• For H.323 and SIP specify the Network Service

Prefix followed by the Entry Queue Numeric ID.

Table 1-1: Cascade Links List Parameters

Column Description

20


Chairperson Conference ActivationIf chairperson activation is enabled in the Auto Cascade configuration in the MGC Web Server Manager, then the cascaded conference may implement the “Start only when the chairperson connects”, and “Terminate conference after the chairperson exits” features, provided these options are selected in the individual conferences. If the “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 ConferenceIf the conferences are set to terminate when the chairperson leaves, and the Auto Cascade configuration includes enabling of chairperson activation, then all conferences will terminate when the chairperson leaves, as described in the section “Chairperson Conference Activation” on page 21. In addition, 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.

Limitations• In Continuous Presence conferences, the layout must be set to full screen.• 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 is required.• The MGC Manager and WebCommander monitoring is per MCU. There is no GUI to

display cascaded conferences across multiple MCUs as one conference.• Operator assistance is per MCU.• The following chairperson actions are not implemented across MCUs: Voting,

Question and Answers, Replay Roll Call, Change password.• All the MCUs must have IVR/DTMF licenses.• For H.263 4CIF and H.264 Continuous Presence conferences, the link will be defined

as H.263 CIF.• The Auto Cascade feature does not work with H.239/People + Content.• The Auto Cascade feature can only be implemented for the database assigned as the

Global Default in the Web Server Manager.

21


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

H.239 can only be implemented when in the system.cfg: H.239=YES.

22


SSL (Secure Socket Layer)

SSL (Secure Socket Layer) enables secure HTTP connection to MCU’s with XPEK Operating Systems.

Detailed DescriptionSSL 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 in the Web Server Manager.

To obtain the SSL certificate in the Web Server Manager:1. Connect to the MCU.

2. Right-click the MCU’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:

Enter complete information, as all fields are mandatory for the request.

Table 1-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) for which the certificate will be issued.

Common Name (DNS/IP)

Enter the DNS or the IP address of the MCU.

23


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 by text 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 SSL Certificate.

The Send SSL Certificate dialog box opens.9. Paste (Ctrl +V) the certificate’s text in the Send SSL certificate window.

10. Click Send.The MCU validates the certificate.

24


— 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.The system has access to the SSL-secured port 443.

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 Automatic Discovery.Make sure the Automatic Discovery option is deactivated (clear the check box).

7. The Port Number box is enabled, enter port 443 as the Port Number.When mandatory security is enabled, on first connection after the reset, MCU will automatically use only the preferred SSL-secured port 443, and the HTTPS protocol.

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

25


8. Select the Secured check box to enable mandatory security.

9. Click OK.

10. Connect to the MCU.When reconnected, the MCU uses the secured port.

— The HTTPS protocol is indicated in the Server list, in the Security column. Port 443 and the Secured (the lock) icon are indicated in the MGC Web Server Manager window’s status bar.

After reconnecting, it is highly recommended to change the login password.

26


Same Layout Option in Video Switching Conferences

Video Switching conferences support the Same Layout mode.

Detailed DescriptionIn version 7.5, when the Same Layout option is checked, the speaker views himself instead of the previous speaker. All other participants view this layout.

27


Version 7.5 - Corrections, Limitations and Pending Issues

Corrections between Versions 7.0 and 7.5

Table 1-3: Corrections between 7.0 and 7.5

#. Subject Description ID# Remarks

1. Personal Scheduler Client

When sending an e-mail from Personal Scheduler without including a subject heading in the email, conference details and the ViaVideo icon are missing.

19829

2. External Database

If the Windows service pack is older than version 4.0, the WebCommander cannot be used with an external database for Ad Hoc conferencing.

13530

3. Windows NT When using Windows NT authentication, the second user to login fails and is rejected.

21712

28


Corrections between Versions 6.01 and 7.0



1. Calendar When you make a reservation for the next day and you go to the calendar and change the reservation to the present day, the message “Phone is Occupied” appears. When you click OK the application crashes.

Create the reservation from scratch on the correct (present) day.

2. Conference monitoring

A participant with a long name causes the Video Layout pane to stretch across the WebCommander screen.

14423


If the conference is terminated with DTMF, a Java Script error appears.

11464


In conferences running on the standard Video card, the Personal Layout option is enabled, even though this option is unavailable.

7259

5. Conference Properties

The Conference On Port option is missing from the conference properties when using WebCommander in a language other than English.

12452

6. Double Booking If a conference is starting and the Double Booking window appears indicating a conflict, you can not send out a conference notification via e-mail (even if the e-mail is not being sent to the participant(s) in conflict).

12452 .

7. Double Booking When defining a new Meeting Room with a participant that is present in an On Going conference, the Double Booking window does not appear.

14703

8. Entry Queue Access

An Entry Queue Access conference started from a Reservation Template cannot start if the conference properties do not match those defined for the first Entry Queue listed in the Meeting Rooms list as the system searches only for the first Entry Queue and ignores the other listed Entry Queues.

14784

9. Reservation templates

If you define a Continuous Presence - Classic conference along with its layout, and then you change the conference to Continuous Presence - Quad View, you must start the conference from the Video Layout tab or you get an error message.

Start the conference from the Video Layout tab.

29



When selecting Presentation Mode during conference definition, COP and Same Layout are disabled.

14740


Some NT operating systems do not have an Atl.dll that is required for add-in clients. Personal Scheduler Client installations fail to install when installed on new installations of WindowsNT or Windows98 that were not updated with the latest updates and service packs due to missing dlls.

14943 Install the. dll in the correct location.This is provided by Support personnel. In most installations, installing the latest WindowsNT Service pack and updates or Windows98 updates may resolve the problem.

12. Personal Scheduler Client Update

After uninstalling and re-installing a new version of the MGC Personal Scheduler Client, the Polycom Office icon does not appear in the Outlook.

14777 Close and re-open Outlook.


After installing the Personal Scheduler Client, after scheduling the first meeting, an error message occurs.

18316


The IP Dial-in number is missing or is incorrect when sending an e-mail invitation during recurrent meetings.

18423

15. Personal Scheduler - Client Meeting Form

If “MCU Selection” and “Enable Dial-out” are not enabled in the configuration of the server, these two options are not available, however they appear in meetings listed in the Calender.



30


16. Personal Scheduler - Meeting

The minimum number of participants cannot be selected for Entry Queue Access conference templates.

14831 When creating a new template, select Meet Me Per Conf instead of Entry Queue Access. Set the minimum number of participants and then select the Entry Queue Access (cancelling the Meet Me per Conf). The correct Min Number of Participants is saved.

17. Personal Scheduler - Update Recurrence / Multiple MCU

When using multiple MCUs, if you update a reservation and make it recurring, the reservations are created on another MCU.

Make the reservation from scratch. To be corrected in the next version.

18. Personal Scheduler - Installation

In case that the ATL.dll is missing from windows 95/98/ME the installation of the Personal Scheduler Client may not start.

14943 To be corrected in the next version.

19. Personal Scheduler

When displaying the properties of a meeting in the calendar that occurred in the past, the Invite dial-out button is enabled (should be disabled).

11480


In Personal Scheduler Client you cannot reload the Language database, therefore changes in the strings will not be displayed in the Personal Scheduler.

14977 Install WebCommander Meeting Scheduler or restart WAM.


When reinstalling the Personal Scheduler Client while a few E-mail messages and meeting windows are open, the Personal Scheduler button in the Outlook is not responding.

15045 Close and re-open the Outlook application.


The billing code is not taken from the User definition - Conference Creation parameters in the database.

14880 Add the billing code to the conference template.



31


23. Personal Scheduler Tab Name

If you modify the tab name and install the client server, and then you modify the tab name again, the old tab name will remain.

To change the tab name you must go to the Tools menu in Outlook and select Options. Click the Other tab and then click the Advanced Options button. Click the Custom Forms button and then click the Manage Forms button. You must then select the Form name and delete it. Start a new meeting and the new changes will take effect.

24. Reservation recurrence

When you make a recurrence reservation using the Monthly option ‘day X of the month’, the last recurrence is missing.

Add the last recurrence manually. To be corrected in the next version.

25. Server When your local time in Start -> Settings -> Control Panel -> Local Settings -> Regional Options is not set to the United States, the date and month are reversed in the reservation.

11896 To be corrected in the next version.



32


Version 7.5 System Limitations

Table 1-5: System Limitations

No. Subject Description ID# Workaround/Remarks

1. Conference On Going

When the system cannot support the Exclusive Speaker mode due to the incorrect card type, a status message does not appear.

14650

2. E-mail notification

When the From field in an e-mail is not filled in, the system does not produce a warning message.

3. Participants Polycom DataStore participants in Bonding mode cannot be added to a conference.

Change the participant’s aggregation mode.

4. Permissions If the conference organizer does not have permission to change user settings, any passwords the organizer configures will be ignored and the conference will start with passwords defined by the MCU.

5. Recurrent reservation

After changing the scheduling of a single recurrent meeting, when using the Drag & Drop method, if you try to update the entire series, you get a message "Operation failed".

18007 Open the appointment and change it.


When setting up an Entry Queue conference, the Continuous Presence - Quad View option is enabled. This should be disabled.


If you change the layout colors of the conference and start the conference, the colors will revert to the default colors after the conference is over, even if you save the template.

You must change the layout colors before the start of each conference.

8. Reservation Calendar

When the name of MCU contains an apostrophe (‘), you get a Java script error.

The name of the MCU may not contain an apostrophe (‘).


After an updating an recurring reservation and sending an update by e-mail, in Outlook 2003, the invitee gets an email with a “Polycom Office” tab.

18390


When creating an recurrent reservation “on behalf” of a colleague, the conference ID for the recurring reservations are incorrect.

15264

33


11. Personal Scheduler - Server

When configuring the Personal Scheduler server (after installation), the Language drop-down list appears blank.

14676 Click the arrow to display the list of languages and select the appropriate language.


In the MGC Manager, when printing the parameters of a Continuous Presence conference scheduled from the Personal Scheduler, the layout of 1x1 appears as “unknown” in the printed data.

11812

Table 1-5: System Limitations

No. Subject Description ID# Workaround/Remarks

34


Pending Issues Version 7.5

Table 1-6: Pending Issues


1. Double Booking

When making a conference reservation for today (Monday) and selecting a future date for the recurrent reservation (for example next Wednesday), the Double Booking window appears for today’s booking.

14742


Personal Scheduler Clients version 5.6 cannot connect to Personal Scheduler server version 6.0.

13607 Version 7.0 enables backward compatibility.


In the "Polycom office" tab, the field "Dial-in Endpoints/Phones" field That appears in all types of conferences. This field should appear only in "Entry Queue" or "Meet-Me per" conferences.

17887


When a viaVideo auto connection is not supported when the system.cfg flag 'Quick login Via EQ' is set to YES.

18713 Create a regular conference and check the 'Enable numeric conference name' checkbox in the 'MGC Personal Scheduler Configuration'. For reservation recurrences, use EQ Access or Entry Queues to solve the problem.

5. Personal Scheduler Client Installation

Personal Scheduler version 5.6 and Personal Scheduler version 6.0 should not be installed on the same server as version 6.0 is not backward compatible with previous Personal Scheduler versions.

13640

6. Personal Scheduler Reservation

When creating a recurring reservation when you click Edit and then change the subject name, the name does not change.

18374

35


7. Recurrent Reservation

The recurrent reservation's name field is limited to 73 characters. The WebCommander automatically adds the user-name and numbers to each reserved conference, resulting in missing Therefore, it is recommended (Workaround) to give the reservations names that are shorter than 50-60 characters.

17829 Reservation names should be shorter than 50-60 characters.

8. Recurrent Reservation

When user A creates a single recurring meeting on behalf of user B, when user B updates the meeting, user A cannot re-open the meeting on behalf of user B.

19268


After an update of recurrence fails, it is impossible to access any recurring reservation.

18010


When editing a recurrent meeting, no changes are implemented. The reservations are deleted and recreated without the changes. If the number of recurrent reservations consist of a large number, it takes a long period of time to generate and process.

18373

11. Reservations Japanese and Chinese languages

When using WebCommander in Japanese and Chinese languages, the confirmation button to schedule new conferences is missing in the New Meeting page.

You must schedule the reservation from the Reservations Templates window.

12. Screen Resolution

You are unable to view the WebCommander GUI if your screen resolution exceeds 600x800.

13733

13. Version Upgrade

WebCommander version 6.0x installed with PathNavigator database and NT Authentication, after upgrading to version 7.0 using the PathNavigator database with SQL Authentication, the PathNavigator database is not added or connected to the database list.

18999 Update the database list using NT Authentication.



36


14. Reservation default

When you copy and paste the Reservation Default template from one database to another, not everything copies correct.

The fields that did not copy correctly must be changed manually. The fields are: Interlaced Video Mode, Dual Stream Mode, Conference on Port, Entry Queue Access, Meet Me Per Conference, Meeting Room, Start Conference Requires Chairperson, Terminate After Chairperson Exits, On Hold, Invite Party, Background, Layout Border, Speaker Notation.

To be corrected in the next version.

15. Web Commander and Personal Scheduler - Server Manager

In the Server Manager, when modifying the name of an existing Default Reservation set from lower case to upper case, the system indicates that the default reservation set already exists.

14860

16. WebOffice Inter- operability

When WebOffice is configured with WebCommander using Windows Authentication, WebOffice will not be able to start audio or video links.

13847 In WebOffice Server configuration use MGC Direct Management and not Web Commander. The links from WebOffice will then work independently, and the monitoring of the conference can be done by Web Commander.

17. Web Commander

When customizing the format of the Email (In any language), there is no default format.

16014



37


Proprietary and ConfidentialThe 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. Polycom and Accord are registered trademarks of Polycom, Inc.

38


39

webcommander release notes 7.7

Documents