Polycom ReadiManager SE200 Release note

Brand: Polycom

Model: ReadiManager SE200

Type: Release note

This manual is also suitable for

ReadiManagerSE200

Polycom ReadiManager SE200 is a powerful and versatile video conferencing management solution that enables organizations to easily manage and monitor their video conferencing endpoints and conferences. With centralized control over scheduling, provisioning, and device management, ReadiManager SE200 helps streamline operations and improve collaboration efficiency.

registered trademarks, V

IU, ReadiManager SE200, PathNavigator, Global Management System, and iPower are

trademarks of Polycom, Inc. in the United States and various other countries. All other trademarks are the property of

respective owners

ViewStation are registered trademarks, PathNavigator, Global Management System, and iPower are trademarks of

Polycom, Inc. in the United States and various other countries. All other trademarks are the property of respective owners

ReadiManager SE200 ™ 1.0.0 Release Notes

November 18, 2005

This document provides complementary or late-breaking information to supplement

the ReadiManager SE200 User Guide documentation. Check the Polycom web site

(http://www.polycom.com) for the latest information.

Check the User Guide or the Read Me First for more information on system

requirements, installation, and licensing.

INSTALLATION AND FIRST TIME SETUP

1. When doing the initial IP configuration during first time setup, the appliance

operating system does not report the current IP settings unless a live network

cable is connected to the proper network interface on the back of the system.

2. Doing the first time setup on the Integrated Application Module (IAM) blade in

the ReadiConvene platform must be done via the Serial Console to set the

initial IP address. The instructions for web-based first time setup operations

will not work until the IP address has been set up via the Serial Console.

NETWORK SETUP

1. The Site Topology and Dial Rule configuration can take up to fifteen minutes

to propagate fully within the system. Until then, though the user interface

will reflect the new settings the gatekeeper and global address book services

may reflect the previous configuration. When testing site topology and dial

rules changes, be sure to allow sufficient time for the changes to fully

propagate before conducting tests.

2. Not all devices will send their ISDN configuration when registering with the

gatekeeper. This can be corrected by manually configuring the ISDN settings

on the endpoint after it is registered.

3. While an SBC such as the Polycom V

IU can be configured for a site in the

Site Topology configuration, the gatekeeper will not currently send call setup

to the SBC for Internet/VPN bound calls to unregistered endpoints.

4. When creating dial rules, a service cannot be changed from gateway to MCU

or the reverse. If the service type needs to be changed it should be removed

and then re-entered into the system.

5. To set up prefix dialing of neighbor gatekeepers the dial rules section of the

configuration must be used. While there is a location to set a gatekeeper

preference when configuring an alternate region gatekeeper address, only the

dial rules engine will apply during address resolution.

USER ADMINISTRATION

1. When looking up group membership in an ActiveDirectory only simple group

membership is returned. Users who are members of groups that are in turn

registered trademarks, V

IU, ReadiManager SE200, PathNavigator, Global Management System, and iPower are

trademarks of Polycom, Inc. in the United States and various other countries. All other trademarks are the property of

respective owners

ViewStation are registered trademarks, PathNavigator, Global Management System, and iPower are trademarks of

Polycom, Inc. in the United States and various other countries. All other trademarks are the property of respective owners

members of other groups will not be returned as members of the secondary

groups. Hierarchical group membership is not tracked.

DEVICE ADMINISTRATION

1. Adding a device with ISDN capabilities will assume that the device has a

quad-BRI interface.

2. If an endpoint registers through the gatekeeper, though it will appear in the

global address book, it will not automatically receive the global address book

entries. To receive the global address book the endpoint must be provisioned

with the appropriate global address book configuration.

3. If an endpoint registers with the global address book server it will not

automatically be registered with the gatekeeper. Though it can be reached by

registered endpoints it cannot call other registered endpoints by alias without

registering with the gatekeeper.

4. An endpoint entered manually through the user interface must still be

provisioned to register with the gatekeeper or global address book services.

5. An endpoint which registers through either the gatekeeper or global address

book services may not automatically be claimed for device management if the

device has an administrative password until that password is entered through

the user interface.

6. In the Device Wizard you must clear the fields for Country Code, Area Code,

and number in order to uncheck the ISDN capability.

SCHEDULING

1. When creating a scheduled conference a higher bit rate can be selected for an

IP call than either the device policy or network topology would allow. When

the scheduled call launches the gatekeeper policies will apply by either

downgrading or rejecting the call.

2. The Outlook plugin and Web Scheduling control does not currently accept 8-

bit characters. Only characters in the 7-bit character set are currently valid.

3. When creating a recurring conference where only a portion of the future

scheduled conferences have conflicts will result in the non-conflicting

conferences being scheduled and the conflicting conferences not being

scheduled. No error message is returned to the user.

4. Users with iPower and VCON endpoints will need to download a plugin from

the Polycom Resource Center (PRC) to install on those endpoints. This will

enable the scheduling engine to auto-launch calls on those endpoints.

5. If endpoints are scheduled which are not part of a defined site, the conference

will not auto-launch the call with those endpoints. However, none of the

scheduling interfaces will indicate an error when those endpoints are

scheduled. All endpoints in an auto-launched call must be part of a defined

network to successfully start the conference.

6. Clients using the Jerusalem time zone on their local system must download a

patch from Microsoft to correctly compute daylight savings time for

scheduling calls.

7. When scheduling calls using the web-based scheduling control, emails will be

sent to all users who are associated to devices scheduled as well as guests

where the user details include a valid email address. Emails will not be sent

to resource owners which are part of the scheduled call. This functionality

registered trademarks, V

IU, ReadiManager SE200, PathNavigator, Global Management System, and iPower are

trademarks of Polycom, Inc. in the United States and various other countries. All other trademarks are the property of

respective owners

ViewStation are registered trademarks, PathNavigator, Global Management System, and iPower are trademarks of

Polycom, Inc. in the United States and various other countries. All other trademarks are the property of respective owners

requires that a valid SMTP server configuration is present in the

administration view.

CONFERENCE MONITORING/MANAGEMENT

1. The scheduled conference ID may differ in conference monitoring when calls

become active. The conference ID for active IP calls will be the H.323

conference ID assigned by the gatekeeper. This value may differ from the

scheduled conference ID when the future scheduled conference was created.

The CDR will report the gatekeeper assigned conference ID.

2. Point-to-point scheduled conferences that do not use the MGC will always

show as “FUTURE” conferences in the conference monitoring control in the

operator interface. Even when the conference launches it will remain in a

“FUTURE” state rather than converting to “ACTIVE.” In addition, the

participants will be shown as disconnected. However, in the device

monitoring control the correct status information for the endpoints is shown.

3. Conferences running on Polycom MGC’s with versions prior to version 7 may

not fully display all details in the conference monitoring control in the

Operator view. With version 7 and higher MGC’s all conference details and

full ad-hoc conference management capabilities are present.

4. The level of conference management depends on the version of MGC

installed. Version 6 allows for basic conference management functionality.

Version 7 or higher allows for advanced functionality.

5. Muting participants from the conference monitoring control of the Operator

view will not work. However, participants can be connected and disconnected

from conferences running on MGC’s with version 7 or higher by clicking on the

green connection ball.

6. Using the Send Message function on a MGC call from the conference

monitoring control will not send a message to the participant. To send

messages to endpoints in a multi-point call the device monitoring control

should be used.

7. When monitoring active conferences not all parameters will be populated in all

cases. However, the data that is presented accurately represents the ongoing

conference.

PROVISIONING

1. Only one scheduled provisioning profile can be scheduled for a device type at

any one time. If a second profile is scheduled for a device type its schedule

will replace any other profile which is scheduled but not yet active.

POLYCOM MGC CONFIGURATION

1. When adding an MGC version 7 or higher all of the configuration details will

be auto-populated based on the current MGC configuration. These details can

be edited from their defaults.

2. If entry queues are not defined on an MGC running version 7 or higher then

the auto-populated details on the MGC will have IVR unchecked. If entry

queues do exist on the MGC when it is added to the ReadiManager then the

IVR option will be checked and the entry queue number will be entered

registered trademarks, V

IU, ReadiManager SE200, PathNavigator, Global Management System, and iPower are

trademarks of Polycom, Inc. in the United States and various other countries. All other trademarks are the property of

respective owners

ViewStation are registered trademarks, PathNavigator, Global Management System, and iPower are trademarks of

Polycom, Inc. in the United States and various other countries. All other trademarks are the property of respective owners

automatically. If more than one entry queue exists, this number should be

set to the number of the entry queue to be used by the ReadiManager.

3. When entry queues are in use, audio-only dial-in calls will be prompted to dial

into the conference and enter the PIN generated by the conference

configuration.

4. If entry queues are defined then all scheduled video calls will use IVR. The

IVR behavior will depend on how the MGC has the IVR service configured.

5. If it is desirable to use IVR without using entry queues, then the MGC

configuration on the ReadiManager can have the IVR option checked and

leave the entry queue number configuration empty. The behavior of IVR for

scheduled calls will then be based on the IVR configuration on the MGC.

6. After the MGC has been configured, if the IVR is unchecked and the entry

queue number removed, the ReadiManager will continue to use IVR for all

scheduled calls on that MGC. The work around is to remove the MGC

configuration and enter it again. However, existing future scheduled calls will

need to be validated if they were scheduled to use that MGC.

LOCAL MSDE DATABASE

1. The backup process for the local database will store backups directly on the

hard drive of system. These images can be restored through the Serial

Console. If backups are required to be offloaded from the system then an

external Microsoft SQL Server should be configured for use with the

ReadiManager.

2. Users with more than 100 endpoints are recommended to use an external

SQL server. The resources used by the internal MSDE server can limit the

number of endpoints and other resources that can be served effectively by

the ReadiManager.

REMOTE MS SQL SERVER DATABASE

1. To use an external MS SQL server with the ReadiManager it must be running

at least SQL Server 2000 Standard Edition or Enterprise Edition with Service

Pack 3 or higher. Newer versions of SQL Server have not been tested.

2. An external SQL Server system must have at least 1GB of RAM and 30GB of

free hard disk space. It is recommended that a single processor system be at

least 2.5GHz and a dual processor system be at least 2.0GHz.

3. When an external SQL server is used, the database backup and restore

facilities available through the Serial Console are not useful. These utilities

only apply when using the internal MSDE database server.

BROWSER SETTINGS

1. Client systems which have the 2.0 beta version of the Microsoft .NET

Framework may not function correctly when accessing the Operator pages of

the ReadiManager. The only work around is to uninstall the 2.0 .NET

Framework and use the released .Net version of 1.1.1322.573.

2. Setting “Prompt” as the choice for executing .NET controls in Internet

Explorer may cause some functionality to be disabled on the ReadiManager

Operator view.

registered trademarks, V

IU, ReadiManager SE200, PathNavigator, Global Management System, and iPower are

trademarks of Polycom, Inc. in the United States and various other countries. All other trademarks are the property of

respective owners

ViewStation are registered trademarks, PathNavigator, Global Management System, and iPower are trademarks of

Polycom, Inc. in the United States and various other countries. All other trademarks are the property of respective owners

3. Users should verify that the full version of their .NET framework on their local

client is at least 1.1.4322.573. Microsoft had an earlier release of this version

(numbered 1.1.4322.510) that is known to cause periodic crashes of the

browser. Users should, if they have an older version of the .NET framework,

install at least version 1.1.4322.573 on their local system. The mechanism

built into the ReadiManager cannot detect the differences between these two

versions so users must verify this manually.

DISASTER RECOVERY

1. When choosing the “Restore OS” option in the Serial Console the system will

over-write the normally running operating system and software with that

which shipped from the factory. This process can take up to twenty minutes

to complete. During this time the system will be unavailable for other

operations. The only indication of activity on the system will be the hard

drive activity LED on the front of the unit. Powering down the unit during this

process can render the system unusable. Once the process is complete the

unit will start automatically. This process does not change any settings in the

database.

Polycom ReadiManager SE200 Release note

Brand: Polycom

Model: ReadiManager SE200

Type: Release note

This manual is also suitable for

ReadiManagerSE200

Download PDF

report

Polycom ReadiManager SE200 Release note

This manual is also suitable for

Polycom ReadiManager SE200 Release note

Related papers

Other documents