SCOPIA iVIEW Management Suite - Logitel€¦ · RADVISION | Administration Guide for SCOPIA iVIEW...

SCOPIA iVIEW Management Suite

Version 7.5

Administration Guide

© 2000-2010 RADVISION Ltd. All intellectual property rights in this publication are owned by RADVISION Ltd and are protected by United States copyright laws, other applicable copyright laws and international treaty provisions. RADVISION Ltd retains all rights not expressly granted.

This publication is RADVISION confidential. No part of this publication may be reproduced in any form whatsoever or used to make any derivative work without prior written approval by RADVISION Ltd.

No representation of warranties for fitness for any purpose other than what is specifically mentioned in this guide is made either by RADVISION Ltd or its agents.

RADVISION Ltd reserves the right to revise this publication and make changes without obligation to notify any person of such revisions or changes. RADVISION Ltd may make improvements or changes in the product(s) and/or the program(s) described in this documentation at any time.

If there is any software on removable media described in this publication, it is furnished under a license agreement included with the product as a separate document. If you are unable to locate a copy, please contact RADVISION Ltd and a copy will be provided to you.

Unless otherwise indicated, RADVISION registered trademarks are registered in the United States and other territories. All registered trademarks recognized.

For further information contact RADVISION or your local distributor or reseller.

Administration Guide for SCOPIA iVIEW Management Suite Version 7.5, September 2010

http://www.radvision.com

RADVISION | Administration Guide for SCOPIA iVIEW Management Suite Version 7.5

Table of Contents

1 About iVIEW Communications Manager

Understanding Video Conferencing .......................................................................1

About Network Devices ...............................................................................1

Cascading for Flexible Conferencing................................................................2

SCOPIA iVIEW Communications Manager User Types ...................................................2

Administrative Permissions ...........................................................................3

Login Screen Options ........................................................................................4

Service Provider Login.................................................................................4

Enabling Single Sign-on (SSO) ........................................................................4

Enabling Single Sign-on with Microsoft Vista and Microsoft 7.........................................5

Interface Orientation........................................................................................6

Configuration Workflow.....................................................................................6

2 Defining and Managing Organizational Profiles

Creating Organization Profiles.............................................................................8

Defining Organization Contact Details..............................................................9

Defining Concurrent Call Limits .....................................................................9

Defining a Billing Code .............................................................................. 10

Enabling Organization Meeting Types ............................................................. 10

Defining Organization System Administrator Credentials ..................................... 11

Viewing an Organization Profile ......................................................................... 11

Activating and Deactivating Organization Profiles ................................................... 11

Activating an Organization Profile ................................................................ 11

Deactivating an Organization Profile ............................................................. 12

Table of Contents| iRADVISION | Administration Guide for SCOPIA iVIEW Management Suite Version 7.5

Removing Inactive Organization Profiles ............................................................... 12

3 Setting-Up Your Video Communication Network

Managing Bandwidth of a Remote Network Location ................................................ 13

Connecting to the MCU.................................................................................... 14

Creating an MCU Profile............................................................................. 15

Cascading Multiple MCUs............................................................................ 16

Service Definitions in the MCU ..................................................................... 17

Viewing Available Meeting Types on Network MCUs ...................................... 18

Viewing Built-in Meeting Types............................................................... 19

Downloading a Meeting Type to iVIEW Communications Manager ...................... 19

Searching for a Meeting Type................................................................. 19

Removing a Meeting Type ..................................................................... 20

Viewing Meeting Type Details................................................................. 20

Modifying Meeting Type Details .............................................................. 20

Viewing a List of MCUs Containing a Specified Meeting Type ........................... 21

Creating or Modifying a Meeting Type Group .............................................. 21

Synchronizing MCU Information with iVIEW Management Suite .............................. 22

Searching for an MCU Profile ....................................................................... 22

Taking an MCU Offline ............................................................................... 23

Removing an MCU Profile ........................................................................... 23

Connecting to the Gatekeeper.......................................................................... 24

Selecting a Gatekeeper Type for Your Deployment............................................. 24

Using an Internal Gatekeeper ................................................................ 24

Using a Standalone RADVISION SCOPIA ECS Gatekeeper ................................. 24

Using an External Gatekeeper................................................................ 25

Creating a Gatekeeper Profile ..................................................................... 25

Defining the Gatekeeper Address............................................................ 25

Defining Dialing Plan Settings ................................................................ 26

Defining iVIEW Communications Manager as the Gatekeeper Authorization Server. 26

Removing a Gatekeeper Profile .................................................................... 27

Searching for a Gatekeeper Profile................................................................ 27

Accessing Meetings from an External Gatekeeper .............................................. 28

Connecting to the iVIEW Communications Manager.................................................. 29

Creating a Gateway Profile ......................................................................... 29

Table of Contents| iiRADVISION | Administration Guide for SCOPIA iVIEW Management Suite Version 7.5

Searching for a Gateway Profile ................................................................... 31

Taking a Gateway Offline ........................................................................... 32

Removing a Gateway Profile........................................................................ 32

Connecting to an SIP ServeriVIEW Communications Manager....................................... 33

Creating an SIP Server Profile ...................................................................... 33

Enabling the MCU to Work in SIP Mode ........................................................... 34

Removing a SIP Server Profile ...................................................................... 35

Searching for a SIP Server Profile.................................................................. 35

Disabling the SIP Back-to-Back User Agent....................................................... 36

Creating Meeting Rooms .................................................................................. 36

Enabling Meeting Room Support ................................................................... 36

Creating a Meeting Room Profile................................................................... 37

Sending Meeting Details by Email.................................................................. 37

Searching for a Meeting Room Profile............................................................. 37

Removing a Meeting Room Profile ................................................................. 38

Registering Endpoints with a Gatekeeper.............................................................. 38

Creating Terminal Profiles .......................................................................... 38

Defining H.323 IP Terminals................................................................... 39

Defining SIP IP Terminals ...................................................................... 40

Defining ISDN/PSTN H.320 Terminals........................................................ 41

Defining Mobile Terminals..................................................................... 42

Defining Dual H.320 and H.323 Terminals .................................................. 43

Removing a Terminal Profile ....................................................................... 44

Searching for a Terminal Profile ................................................................... 44

4 About Telepresence Support

About Supported Telepresence Systems................................................................ 45

Licensing for Telepresence ............................................................................... 45

About Telepresence Deployment Considerations ..................................................... 46

Configuring Telepresence Systems ...................................................................... 46

Telepresence Resource Calculation ..................................................................... 48

Scheduling Telepresence Systems ....................................................................... 48

Table of Contents| iiiRADVISION | Administration Guide for SCOPIA iVIEW Management Suite Version 7.5

5 Managing Your iVIEW Communications Manager User Profile

Viewing Your User Profile Settings....................................................................... 49

Modifying Your Password .................................................................................. 50

Modifying Your Email Address ............................................................................ 50

Modifying Your Time Zone ................................................................................ 51

Defining Your Meeting Display Preferences ............................................................ 51

Defining Your Virtual Room Preferences................................................................ 52

6 Managing Users Without an External Directory

Creating or Modifying a User Profile ................................................................... 54

Removing a User Profile................................................................................... 55

Searching for a User Profile .............................................................................. 56

Updating User Profiles..................................................................................... 56

Creating a User Group .................................................................................... 57

Modifying a User Group .................................................................................. 57

Removing a User Group ................................................................................... 58

Modifying a Service Provider Profile .................................................................... 58

Limiting Individual User Access to Meeting Types .................................................... 59

Limiting Group Access to Meeting Types ............................................................... 60

Configuring Multiple Settings for User Groups......................................................... 60

7 Creating SCOPIA Desktop Profiles

Creating or Modifying a SCOPIA Desktop Profile ..................................................... 61

Removing a SCOPIA Desktop Profile .................................................................... 62

Searching for a SCOPIA Desktop Profile ................................................................ 62

Streaming Meetings Using SCOPIA Desktop ............................................................ 62

Enabling Streaming on SCOPIA Desktop........................................................... 63

Enabling Streaming for a Virtual Room ........................................................... 63

Allowing Recording by Specified Roles............................................................ 63

Allowing Recording by Specified Users............................................................ 64

Enabling Recording for Specified Virtual Rooms................................................. 64

Table of Contents| ivRADVISION | Administration Guide for SCOPIA iVIEW Management Suite Version 7.5

8 Populating Corporate Address Books

Updating the Corporate Address Book.................................................................. 66

Configuring the LDAP Service ............................................................................ 66

Configuring the H.350 Directory Server in iVIEW ..................................................... 67

9 Setting the H.350 in Terminals for the Global Address Book

10 Viewing Network Device Performance and Availability

Viewing Device Usage and Failure by Time Interval.................................................. 73

Viewing Device Usage and Failure by Time Interval and Period.................................... 74

Viewing MCU Port Availability ........................................................................... 75

Generating a Report of Network Device Performance and Availability ........................... 76

11 Viewing Real-time Meeting Statistics

Viewing Port Utilization Information.................................................................... 77

Viewing Organization Meetings and Calls .............................................................. 77

Viewing the Creation Status of Meetings............................................................... 78

Searching for a Meeting................................................................................... 78

Monitoring a Meeting or Call ............................................................................. 79

Generating Reports of Upcoming Meetings ............................................................ 80

Modifying Upcoming Meetings............................................................................ 82

Viewing Host MCUs......................................................................................... 82

12 Creating Statistical Reports of Meetings and Calls

Creating a Call Information Report...................................................................... 83

Creating a Port Usage Report ............................................................................ 84

Creating a Resource Usage Report ...................................................................... 85

Generating Reports for Finished Meetings ............................................................. 85

Generating Bandwidth Utilization Reports............................................................. 87

Table of Contents| vRADVISION | Administration Guide for SCOPIA iVIEW Management Suite Version 7.5

13 TLS Configuration Guidelines

Configuring the MCU for TLS Support ................................................................... 88

Enabling SIP Protocol in the MCU with TLS....................................................... 89

Uploading Certificates............................................................................... 90

Configuring SIP Server for TLS ........................................................................... 94

Editing the SIP Server Configuration File......................................................... 94

Generating a B2BUA Certificate ................................................................... 95

Configuring IBM SameTime Media Server for TLS ..................................................... 98

Importing a B2BUA Certificate Into the SameTime Media Server ............................ 98

Downloading the Certificate for IBM SameTime................................................101

Configuring the SameTime Media Server to Use TLS ..........................................105

Advanced iVIEW Configuration ....................................................................105

Using TLS with SCOPIA Desktop Server and iVIEW Management Suite............................106

Configuring SCOPIA Desktop Server to use TLS.................................................106

Configuring iVIEW to Use TLS with SCOPIA Desktop Server...................................106

Generating a New Certificate...........................................................................106

Replacing the Default Certificate with a New Self-Signed Certificate ...........................108

Uploading the iVIEW Certificate to SCOPIA Desktop Server........................................109

14 Configuring iVIEW Management Suite Redundancy

About Redundancy Mode.................................................................................110

Configuring Redundancy Mode ..........................................................................110

Viewing Redundancy Status .............................................................................112

Disabling Redundancy Mode .............................................................................112

15 About the iVIEW Network Manager

Viewing Network Status..................................................................................114

Viewing Calls and Conferences .........................................................................114

Using Auto-Detect.........................................................................................114

Configuring Basic Elements..............................................................................115

Configuring an MCU and Updating its License Keys ............................................115

Configuring a Gatekeeper..........................................................................116

Configuring a Gateway .............................................................................116

Table of Contents| viRADVISION | Administration Guide for SCOPIA iVIEW Management Suite Version 7.5

Configuring Endpoints ..............................................................................117

Viewing Alarms and Events ..............................................................................117

Connecting to Element Managers.......................................................................117

Connecting to Terminal Managers ......................................................................118

Managing a Centralized Log .............................................................................118

Viewing Multiple Networks ..............................................................................118

Configuring Offline Elements............................................................................118

Defining Network Subsets and Restricting Users .....................................................119

Supporting ECS ............................................................................................119

16 Viewing Your Network in iVIEW Network Manager

How to View the Network as a Tree....................................................................120

Configuring Network Hierarchy ...................................................................120

Creating a Custom Network Tree View ..........................................................121

Viewing the Network as a Table ........................................................................122

Viewing the Network as a Map..........................................................................123

17 Managing Elements in iVIEW Network Manager

Displaying General Element Information..............................................................124

Management Status of Elements .......................................................................125

Viewing all Network Elements ..........................................................................125

Creating or Modifying an Element Profile ............................................................126

Removing an Element Profile............................................................................127

Searching for an Element Profile .......................................................................128

Defining Default Element or Endpoint Access Settings .............................................128

Defining Default SCOPIA PathFinder Access Settings................................................129

Overriding Default Element Access Settings..........................................................130

Upgrading Element Software............................................................................132

Adding a Software Upgrade File ..................................................................132

Modifying a Software Upgrade File...............................................................133

Removing a Software Upgrade File...............................................................134

Cancelling Pending Offline Configuration Settings ..................................................135

Detecting New Elements on the Network Automatically ...........................................135

Running the Auto-detect Mechanism Manually .................................................136

Table of Contents| viiRADVISION | Administration Guide for SCOPIA iVIEW Management Suite Version 7.5

Running the Auto-detect Mechanism Automatically...........................................136

Adding or Modifying Auto-detect Element Access Information ..............................136

Removing an Element Type from the Auto-detect Mechanism...............................137

Managing the Element Software Upgrade Upload Log ..............................................137

Viewing Your Software Upgrade Upload History................................................138

Uploading an Element Configuration File After a Failed Attempt...........................138

Removing Entries from the Element Upload Log ...............................................138

Accessing an Element Web User Interface ............................................................139

Accessing the Monitor Tab for a Specified Element .................................................139

18 Managing a Gateway in iVIEW Network Manager

Managing Gateway Services .............................................................................140

Viewing Gateway Supported Services............................................................140

Creating or Modifying a Gateway Service .......................................................140

Removing a Gateway Service......................................................................141

Configuring Gateway Addressing .......................................................................141

19 Managing the ECS in iVIEW Network Manager

Managing Services.........................................................................................142

Creating or Modifying a Service...................................................................142

Removing a Prefix ...................................................................................143

Bandwidth Tab (ECS version 3.5 or later) .......................................................144

Adding or Modifying Inter-subzone Rules ..................................................145

Viewing or Modifying the Default Inter-subzone Rule ...................................146

Configuring a Parent Gatekeeper.......................................................................147

Enabling the Parent Tab............................................................................147

Adding a Parent Manually ..........................................................................147

Adding a Parent Automatically....................................................................148

Managing Parent Filters ..................................................................................148

Creating or Modifying a Parent Filter ............................................................148

Removing a Parent Filter...........................................................................148

Configuring a Child Gatekeeper ........................................................................149

Enabling the Children Tab..........................................................................149

Viewing Child Gatekeepers ........................................................................149

Table of Contents| viiiRADVISION | Administration Guide for SCOPIA iVIEW Management Suite Version 7.5

Adding a Child Manually............................................................................150

Adding a Child Automatically......................................................................150

Managing Child Prefixes..................................................................................151

Creating or Modifying a Child Prefix .............................................................151

Removing a Child Prefix ............................................................................151

Adding a Neighbor Gatekeeper .........................................................................151

Viewing Neighbor Gatekeepers ...................................................................152

Adding or Modifying a Neighbor Gatekeeper....................................................152

Managing Zones ...........................................................................................153

Creating or Modifying a Local Zone ..............................................................153

Creating or Modifying a Remote Zone............................................................154

Removing a Zone ....................................................................................154

Managing Bandwidth Rules ..............................................................................154

Viewing Bandwidth Rules ..........................................................................155

Creating or Modifying a Bandwidth Rule.........................................................155

Removing a Bandwidth Rule .......................................................................156

20 Managing an MCU in iVIEW Network Manager

Setting Call Routing Devices.............................................................................157

Viewing Registered Multipoint Processors.............................................................158

Modifying MCU Configuration File Information.......................................................158

Backing Up MCU Configuration Settings ...............................................................159

Configuring MCU Location ...............................................................................159

Deleting a Configuration File............................................................................159

Restoring MCU Configuration Settings .................................................................160

21 Managing Traps and Alarms in iVIEW Network Manager

Sending Traps to iVIEW Network Manager.............................................................161

Creating or Modifying a Trap Forwarding Rule .......................................................162

Disabling a Trap Forwarding Rule.......................................................................163

Removing a Trap Forwarding Rule ......................................................................163

Creating or Modifying an Alert Recipient Profile ....................................................163

Removing an Alert Recipient Profile ..................................................................164

Viewing Generated Events...............................................................................165

Table of Contents| ixRADVISION | Administration Guide for SCOPIA iVIEW Management Suite Version 7.5

Filtering Generated Events ..............................................................................165

Viewing Events per Network Item......................................................................166

Viewing and Sorting Supported Alarms ................................................................166

Modifying Alarms..........................................................................................166

Viewing and Sorting Generated Alarms................................................................167

Viewing Generated Alarms per Network Item........................................................168

Table of Contents| xRADVISION | Administration Guide for SCOPIA iVIEW Management Suite Version 7.5

1 About iVIEW Communications Manager

SCOPIA iVIEW Communications Manager (iVIEW Communications Manager) is a simple-to-use, web-based application for managing visual communications in multi-site organization deployments. It provides resource management of network devices for video and audio meetings as well as scheduling, call-routing, and conference control functionalities.

iVIEW Communications Manager optionally includes an internal ITU-T H.323 version 4-compliant gatekeeper to provide call control for IP telephony and multimedia communication networks. This internal gatekeeper is a variation of the radvision SCOPIA ECS Gatekeeper.

iVIEW Communications Manager also contains an internal SIP Back-to-Back User Agent to provide call control for IP telephony and multimedia communication on the SIP network.

• Understanding Video Conferencing .......................................................... page 1

• SCOPIA iVIEW Communications Manager User Types ...................................... page 2

• Login Screen Options ........................................................................... page 4

• Enabling Single Sign-on with Microsoft Vista and Microsoft 7............................ page 5

• Interface Orientation........................................................................... page 6

• Configuration Workflow........................................................................ page 6

Understanding Video Conferencing

This section describes the main aspects of video conferencing.

• About Network Devices ........................................................................ page 1

• Cascading for Flexible Conferencing......................................................... page 2

About Network Devices

RADVISION network devices provide solutions for deploying high quality multipoint video meetings with video processing, audio transcoding and data-collaboration support over switched networks (ISDN) and packet-based networks (IP). RADVISION devices are modular and offer scalable solutions which can be deployed in large organizations in distributed environments. All devices

| 1RADVISION | Administration Guide for SCOPIA iVIEW Management Suite Version 7.5

provide easy to use and intuitive web-based interfaces for system management and configuration. RADVISION devices are fully compatible with third-party video network products, endpoints and terminals.

Entering complete information about each device attached to your network ensures that the iVIEW Communications Manager accurately predicts resource availability, reserves resource, and then schedules meetings accordingly.

Cascading for Flexible Conferencing

With MCU cascading, iVIEW Communications Manager can combine meetings hosted on multiple MCUs, resulting in larger meetings with many more participants than can be supported by a single MCU. Cascading is also used to save network bandwidth by distributing network load over multiple MCUs.

With dynamic cascading, participants can join a meeting on-the-fly (that is, ad hoc) and if originally scheduled resources are not available, iVIEW Communications Manager can automatically schedule and assign MCU resources to accommodate the new participants. This means that a large conference can increase to a size greater than that of the conference originally scheduled, providing that sufficient network resources are available.

Cascading, in general, creates a distributed environment that reduces potential drain on network resources. Processing resources required in order to host a meeting are distributed among participating MCUs.

SCOPIA iVIEW Communications Manager User Types

The following user types are used by the system. Each user type has its own set of permissions.

• Service Provider Administrator—This user type is only available with multi-tenant support.

• Organization Administrator

• Meeting Operator

• Meeting Organizer

• Regular User


Administrative Permissions

Each user type has a default set of permissions and a default view of the user interface. Table 1-1 outlines the different permissions for the user types.

Table 1-1 iVIEW Communications Manager User Types and Default

Permissions

Login Screen Options

The login screen offers the following options:

• Log in to the iVIEW Communications Manager user interface by providing the user ID and password.

• Select Enter a Meeting to open a new window from where you directly access the In-meeting Control interface of an ongoing meeting via meeting ID and PIN.

• Select Network Management to open a new window from where you can access the iVIEW Network Manager user interface.

Service Provider Administrator

Organization Administrator

Meeting Operator

Meeting Organizer

Regular User

View and manage multiple organizations Allowed

View and manage all network devices across multiple organizations

Allowed

View and manage all network devices, room terminals, and users and their virtual rooms within the organization

Allowed

View and manage all meetings across multiple organizations

Allowed

View and manage all meetings within the organization

Allowed Allowed

Create and manage meetings for others Allowed Allowed Allowed

Manage personal address book Allowed Allowed Allowed

Manage own virtual room Allowed Allowed Allowed

Create and manage own meetings Allowed Allowed Allowed Allowed

View scheduled meetings Allowed Allowed Allowed Allowed

Receive and respond to meeting notices Allowed Allowed Allowed Allowed

Attend meetings Allowed Allowed Allowed Allowed

Moderate meetings Allowed Allowed Allowed Allowed

Modify own profile Allowed Allowed Allowed Allowed


Service Provider Login

To log in to iVIEW Communications Manager with multi-tenant support as a service provider administrator, enter your user ID and password in the login screen. Leave the Organization field empty.

Note: For iVIEW Communications Manager with multi-tenant support, users except the Service Provider Administrator need to supply a user ID, password and organization.

Enabling Single Sign-on (SSO)

Single Sign-in (SSO) is only available for iVIEW Communications Manager without multi-tenant support. In other words, SSO only works in a single-enterprise setting. With SSO selected, users who log in to their Microsoft Windows account within their organization domain can log in to the iVIEW Communications Manager directly without having to enter their user names and passwords. iVIEW Communications Manager automatically authenticates the users using their Windows login ID, password, and domain name. For more information, refer to the Single Sign On (SSO) topic in the Installation Guide.

Enabling Single Sign-on with Microsoft Vista and Microsoft 7

By default, the Single Sign-on (SSO) feature does not work with Internet Explorer 8 under Microsoft Vista and Microsoft 7. Modify the Vista default security setting as described here to enable SSO.

Procedure

Step 1 Go to Administrative Tools > Local Security Policy > Security Options on your computer.

Step 2 For Windows Vista, perform these steps:

a. Double-Select Network security: LAN Manager or right-Select and select Properties.

b. Select Send LM & NTLM - use NTLMv2 session security if negotiated in the Local Security Setting tab.

Step 3 For Windows 7, perform these steps:

a. Double-Select Network security: LAN Manager authentication level or right-Select and select Properties.

b. Select Send LM & NTLM responses.

Step 4 Select Apply.


Interface Orientation

The iVIEW Communications Manager toolbar is located in the upper-right corner of the window. The following table describes the graphic elements on the toolbar.

Table 1-2 Toolbar Details

Configuration Workflow

Element Name Icon Description

Help About Opens a window that contains license and version information about iVIEW Management Suite.

Customization The Customization Tool icon is enabled in Configuration Tool > System Configuration > UI Settings > Customization Tool. Select the icon to open a new window and follow the steps to customize any Web interface display label in SCOPIA iVIEW Communications Manager according to your needs.

Help Opens the online help window for iVIEW Communications Manager.

Show Log Opens a window that contains iVIEW Communications Manager log files.

Event List Opens a window that contains recent events.

Customer Support Information Capture

Creates a file of bundled logs and configurationfiles which you can send to RADVISION CustomerSupport for debugging purposes.

Restart Server Restarts the iVIEW Management Suite service from the web interface. Once the connection is re-established SCOPIA iVIEW Management Suite automatically synchronizes the resources of the MCU and the total service is resumed.

Login as a different user Logs out of iVIEW Communications Manager.


We recommend that administrators configure iVIEW Communications Manager according to the following workflow:

• Organization Management—Optional (required only if multi-tenant support is enabled)

• Network Configuration—Optional (required only for distributed deployment)

– IP topology

• Gatekeepers/SIP servers

• MCUs

– meeting types

• Gateways

• SCOPIA Desktop Server

• Meeting rooms—optional

• Terminals

• Users

• Schedule first meeting

Note: Some sections of the user-interface are hidden by default, according to settings in the Configuration Tool; however, these sections are included in the documentation.


2 Defining and Managing Organizational Profiles

This section is for Service Provider Administrators only and provides instruction for creating and managing organizational profiles.

• Creating Organization Profiles ................................................................ page 8

• Viewing an Organization Profile ............................................................. page 11

• Activating and Deactivating Organization Profiles........................................ page 11

• Removing Inactive Organization Profiles ................................................... page 12

Creating Organization Profiles

It is important to understand the distinction between the SCOPIA iVIEW Communications Manager organization and the SCOPIA iVIEW Communications Manager user.

An organization is a company, an enterprise or an individual that is registered with a Service Provider for video meeting services. An organization controls a discrete set of endpoints and a user group. An organization also controls privileges for its users.

A user sits at the base of the SCOPIA iVIEW Communications Manager user pyramid. Users use SCOPIA iVIEW Communications Manager on a day-to-day basis to schedule meetings and invite attendees.

• Defining Organization Contact Details....................................................... page 9

• Defining Concurrent Call Limits .............................................................. page 9

• Defining a Billing Code ........................................................................ page 10

• Enabling Organization Meeting Types....................................................... page 10

• Defining Organization System Administrator Credentials ............................... page 11


Defining Organization Contact Details

Procedure

Step 1 Select Organization Management in the sidebar menu.

Step 2 Select Active.

Step 3 Select Add.

Step 4 Enter the name of the organization in the Organization Name field.

Users in the organization use this name to access the SCOPIA iVIEW Communications Manager web user interface.

Step 5 Enter address information for the organization in the relevant fields.

Step 6 Enter contact information for the organization in the relevant fields.

The telephone number appears in the Active and Inactive tabs.

Step 7 Select OK to save your changes.

Defining Concurrent Call Limits

Procedure



Step 3 Select Add.

Step 4 Check Limit Gateway Use to n Concurrent Calls or Limit MCU Use to n Concurrent Calls to define the maximum number of concurrent gateway or MCU calls that can be scheduled for an organization.

During resource allocation, SCOPIA iVIEW Communications Manager checks if a newly scheduled meeting exceeds the defined limit.

Step 5 Check If Over Limit: Refuse to provide the user with a warning message if the meeting you are scheduling causes the allowed number of concurrent calls over the gateway/MCU to be exceeded, and to return the user to the scheduling interface.

If this option is not checked and the scheduled meeting causes the number of allowed concurrent calls over the gateway/MCU to be exceeded, the extra terminals in the meeting are recorded in the CDR.



Defining a Billing Code

Procedure



Step 3 Select Add.

Step 4 Enter a billing code for the organization in the Billing Code field.


Enabling Organization Meeting Types

Procedure



Step 3 Select Add.

Step 4 Locate the Meeting Type Groups field.

Step 5 Select Select Groups to select the meeting type groups for use by the organization.

Service Provider Administrators are advised to download and upload meeting types to/from SCOPIA iVIEW Communications Manager before creating organizations.

Step 6 Use the arrows in the Select Groups screen to select the required meeting types for the specified organization, and then select OK.

By default, all users in an organization have access to all meeting types of that organization.



Defining Organization System Administrator Credentials

This section is for Service Provider Administrators only for a multi-tenant.

Procedure



Step 3 Select Add.

Step 4 Locate the System Administrator Information section.

Step 5 Enter a login ID, password, and e-mail address for the system administrator of the organization in the relevant fields.

Step 6 Select a user provisioning option for synchronizing information about users defined in an external directory server.


Viewing an Organization Profile

Procedure


Step 2 Select the name of the organization whose details you want to display.

Activating and Deactivating Organization Profiles

• Activating an Organization Profile........................................................... page 11

• Deactivating an Organization Profile........................................................ page 12

Activating an Organization Profile

An active organization is an organization to which you provide a service. The organization profile determines organization-specific parameters.

Procedure


Step 2 On the Inactive tab, select the check box beside the name of the organization profile you want to activate.


Step 3 Select Activate.

The organization is removed from the Inactive tab and appears on the Active tab. All meeting types for the organization are restored.


Deactivating an Organization Profile

An active organization is an organization defined in the SCOPIA iVIEW Communications Manager but not currently receiving a service from you.

Procedure


Step 2 On the Active tab, select the check box beside the name of the organization profile you want to deactivate.

Step 3 Select Deactivate.

A warning message appears, confirming if you want to deactivate the organization.

Step 4 (Optional) Select OK if you do want to proceed.

The organization is deactivated and appears on the Inactive tab. The organization profile is maintained but the members of the organization cannot be used in the system unless they are reactivated.

Removing Inactive Organization Profiles

Procedure


Step 2 On the Inactive tab, select the check box beside the name of the organization profile you want to remove.

Step 3 Select Delete.

The organization profile is deleted from the scheduler and information about the organization is removed from the database.


3 Setting-Up Your Video Communication Network

• Managing Bandwidth of a Remote Network Location .................................... page 13

• Connecting to the MCU........................................................................ page 14

• Connecting to the Gatekeeper............................................................... page 24

• Connecting to the iVIEW Communications Manager...................................... page 29

• Connecting to an SIP ServeriVIEW Communications Manager........................... page 33

• Creating Meeting Rooms ...................................................................... page 36

• Registering Endpoints with a Gatekeeper.................................................. page 38

Managing Bandwidth of a Remote Network Location

You can define the maximum bandwidth for calls across zones to another location, or the bandwidth dedicated to calls within a location. When calling across zones, for example via an MPLS connection, you can define the maximum bandwidth usage and set alerts to be triggered if the maximum designated bandwidth is close to being exceeded.

The bandwidth threshold calculations include SCOPIA Desktop calls. When setting up a new location, use the Location Profile screen (Figure 3-1 on page 13) to define the bandwidth thresholds.

Figure 3-1 Defining bandwidth thresholds for a new location


Procedure

Step 1 Select the Network Management icon.

Step 2 In the Locations tab, select a location name or select the Add button.

The system displays the Location Profile window (Figure 3-1 on page 13).

Step 3 Define the Location Name.

Step 4 Define the maximum bandwidth for internal calls with Max allowed BW for In-zone calls (Kbps).

Step 5 Define the maximum bandwidth for calls between two defined locations with the Max allowed BW for Cross-zone calls (Kbps) field.

Step 6 You can define the system’s behavior when the maximum has been exceeded. Select Reject calls above limit to automatically disallow calls that exceed the defined maximum.

Use the check box next to the in-zone calls for internal calls, or the check box next to cross-zone calls for automatic rejections between zones.

If a call is rejected because of bandwidth limits, the system triggers a Call Rejected alert.

Step 7 You can set a system alert when the maximum bandwidth is close to being exceeded. Enter the percentage bandwidth usage that would trigger the with the Alarm threshold (%) field. The default value is 80%. The alert is called BW Utilization.

Step 8 In the Advanced pane (Figure 3-1 on page 13), select the Add button to define a location with rules to determine what is considered within a zone and what is considered a cross-zone call. There are three ways to define a location:

• Any device with an IP address within a range, for example between 192.168.1.1 and192.168.1.110.

• Any device within an IP subnet, for example to specify 192.168.x.x, enter a base IP of 192.168.1.1 and a subnet of 255.255.0.0.

• A dial prefix, for example any call dialled beginning with the prefix 85.

You can modify a rule by selecting the Modify button, or delete it by selecting Delete.

Connecting to the MCU

• Creating an MCU Profile....................................................................... page 15

• Cascading Multiple MCUs...................................................................... page 16

• Service Definitions in the MCU ............................................................... page 17

• Synchronizing MCU Information with iVIEW Management Suite ........................ page 22

• Searching for an MCU Profile ................................................................. page 22

• Taking an MCU Offline ......................................................................... page 23

• Removing an MCU Profile ..................................................................... page 23


Creating an MCU Profile

The MCU is where a multipoint video conference is hosted. iVIEW Communications Manager reserves MCU resources, schedules MCU conferences, and controls in-session MCU meetings. In order for iVIEW Communications Manager to correctly manage the MCU, it needs to retrieve configuration information from the MCU via the profiles defined under Admin > Resource Management.

During this procedure you specify the management IP of the gateway. The real-time IP is extracted automatically using either the device SNMP interface or its XML interface.

Procedure

Step 1 Select Resource Management in the sidebar menu, or for Multi-Tenant versions select Device Management.

Step 2 Select MCU.

Step 3 Select the link in the Name column for the MCU you require, or select Add to create a new MCU profile.

Step 4 Enter the name and the management IP address of the MCU in the relevant fields.

Figure 3-2 Create or Modify an MCU

Step 5 Select the MCU model.

Step 6 If you want to register the MCU to operate in SIP mode only (without registering to an H.323 gatekeeper), select MCU operates in SIP only mode.

The MCU is not required to register to a gatekeeper and the Registered To field is inactive.

Step 7 Select the device island from the Location list to which the MCU belongs.

The Location field is visible only when the IP Topology tab is activated in the iVIEW Management Suite Configuration Tool under System Configuration > UI Settings.


Step 8 Enter the login name and login password of the MCU in the relevant fields.

These must match the MCU web interface login name and password.

Step 9 Define SNMP communities, user name and password, communication port and signaling port MCU in the relevant fields.

SNMP community information must match the settings defined in the MCU to enable iVIEW Communications Manager to retrieve information from the MCU.


Step 11 The MCU is added to the MCU tab and brought online by default.

If iVIEW Communications Manager cannot connect to a newly configured MCU, the MCU is added but its status is shown as Offline in the MCU tab.

To try to reconnect to the MCU, select Online, and then select OK.

Cascading Multiple MCUs

iVIEW Communications Manager is able to manage multiple MCUs as a pool of resources. You can cascade MCUs to reduce potential drain on network resources, increase the efficiency of MCU usage, and allow large conferences to be held. The following points about cascading should be noted:

• The Meeting Type (MCU service) representing the required meeting must be available on all participating MCUs. For example, if the meeting uses MCU service 81, then 81 must exist on the master MCU and on the slave MCUs.

• A cascaded connection uses two ports—one on the master MCU conference, and one port on the slave MCU conference.

• Only one cascading stream exists between the master MCU and the slave MCU; therefore, only one participant from the slave MCU can send video for mixing and only one participant from the slave MCU can be seen by other participants in the meeting.

• Only one level of cascading is supported. All slave MCU conferences must cascade to the same master MCU conference.

• The administrator must define a default system level property that determines the cascading behavior.

To configure the MCU cascading behavior, use the following procedure:

Procedure

Step 1 Go to Admin > Advanced Settings from the sidebar menu.

Step 2 On the Default Meeting Settings tab you can enable or disable automatic cascading of MCU conferences by configuring the Allow Cascaded Meeting field.


Step 3 If Allow Cascaded Meeting is set to yes, select one of the following options from the Prioritize field:

• Bandwidth—iVIEW Communications Manager allocates resources to conserve bandwidth. For example, at a site with two users and one MCU, iVIEW Communications Manager creates a local meeting. In some cases, this may cause a meeting to cascade to conserve bandwidth, even though a single MCU is available to host the meeting.

Using this option, iVIEW Communications Manager cascades a maximum of two MCUs.

• Delay (default)—iVIEW Communications Manager allocates resources to ensure the best video quality. iVIEW Communications Manager invites all users directly to a main MCU, whatever their location. Since Delay can be costly in terms of bandwidth, it is recommended that you take topology into account before selecting the Delay option.

• Local MCU—Select this option if iVIEW Communications Manager has more than one MCU and there are at least two meeting participants. iVIEW Communications Manager invites all of the participating terminals to meetings hosted on their respective local MCUs (according to IP Topology settings), and then cascades these meetings together to form a single conference.

Step 4 Select OK to save the preferred behavior as the default.

Service Definitions in the MCU

A meeting type in iVIEW Communications Manager is the equivalent of the MCU service definition. Services should be defined in the MCU first and then synchronized to iVIEW Communications Manager. In the Meeting Types section, you retrieve services from MCUs configured in the system and then save them to iVIEW Communications Manager. iVIEW Communications Manager then distributes these services to other MCUs according to your specific deployment requirements.

Meeting types in iVIEW Communications Manager are used to schedule meetings on the MCU. There are also built-in meeting types that are not retrieved from the MCU in iVIEW Communications Manager.

• Viewing Available Meeting Types on Network MCUs ...................................... page 18

• Viewing Built-in Meeting Types............................................................... page 19

• Downloading a Meeting Type to iVIEW Communications Manager...................... page 19

• Searching for a Meeting Type................................................................. page 19

• Removing a Meeting Type ..................................................................... page 20

• Viewing Meeting Type Details ................................................................ page 20

• Modifying Meeting Type Details .............................................................. page 20

• Viewing a List of MCUs Containing a Specified Meeting Type ........................... page 21

• Creating or Modifying a Meeting Type Group .............................................. page 21


Viewing Available Meeting Types on Network MCUs

Procedure

Step 1 Select Meeting Types in the sidebar menu.

Step 2 Ensure that the Active Meeting Types tab is displayed.

All meeting types available for meeting scheduling are displayed with the parameters listed in Table 3-1.

If the name of a meeting type appears in red, the meeting type does not belong to any MCU and cannot currently be used for meeting scheduling.

Table 3-1 Meeting Type Parameters

Parameter Description

Name The name of a meeting type defined in iVIEW Communications Manager.

Prefix The service prefix downloaded from the MCU.

Description The service description downloaded from the MCU.

Media The service media type downloaded from the MCU.

BW (Kbps) The maximum service bandwidth (in kilobytes per second) for download from the MCU.

Lecture Mode For MCU services that support exactly two views with the first view being single sub-frame and the second view being multiple sub-frames, you can set this service to support the lecture mode feature in which a meeting participant is set to one view and can be seen by all other participants, and the other participants are set to the other view and can be seen by the first participant. For 7.x MCU, all the services, excluding audio only and switching services, support lecture mode.

In Use Indicates whether or not there are currently or upcoming meetings in iVIEW Communications Manager that use the specified meeting type. If so, the meeting type is considered in use and cannot be deleted from the system until the meeting type is no longer in use.

MCUs Select Details to display a list of all MCUs defined in iVIEW Management Suite containing the specified meeting type.

Maximum Available Ports

Displays the number of allowed ports for the specified meeting type.


Viewing Built-in Meeting Types

You cannot modify, upload or download built-in meeting types.

Procedure


Step 2 Ensure that the Active Meeting Types tab is displayed.

The built-in meeting types listed in Table 3-2 are available.

Table 3-2 Built-in Meeting Types

Downloading a Meeting Type to iVIEW Communications Manager

Procedure


Step 2 Select Download.

MCU services are downloaded from all network MCUs.

Because MCU services are downloaded via SNMP, the process might take some time if there are many MCUs to connect to.

Step 3 Enter a unique name for each meeting type.

Step 4 Select OK.

Searching for a Meeting Type

Procedure


Step 2 Enter the partial or complete name of the meeting type in the Name field.


Non Video Conference

This is a conference that involves only users and meeting rooms. There is no need for video conference devices. Use this meeting type to reserve users and room resources only.

Point to Point This is a conference that involves only two endpoints (terminals) and no MCU resources. It can only be created if one endpoint dials another endpoint directly.


Step 3 Select Search.

Search results are listed.

Step 4 To return to the complete list of meeting types, clear the Name field, and then select Search.

Removing a Meeting Type

You must deactivate an active meeting type before you can permanently remove it from the system. Once a meeting type is inactive, you can no longer used it to schedule a meeting; however, you must wait until all current or future meetings that use this meeting type are finished, or you must cancel them. When there are no longer any scheduled meetings that require this meeting type, the meeting type is marked not in use and you can remove it.

This process is irreversible. You can never reactivate a meeting type that you have deactivated. When you clear a deactivated meeting type from the iVIEW Communications Manager, the meeting type is also removed from all MCUs in the system which have a service with the same prefix as the deactivated meeting type.

Procedure


Step 2 Select the meeting type you want to delete.

Step 3 Select Deactivate and then OK.

The meeting type is removed from the Active Meeting Types tab and placed on the Inactive Meeting Types tab.

Viewing Meeting Type Details

Procedure


Step 2 Select the link in the Name column for the meeting type you require on the Active Meeting Types tab.

Modifying Meeting Type Details

Procedure


Step 2 Select the link in the Name column for the meeting type you require on the Active Meeting Types.

Step 3 (Optional) Enter a new name for the meeting type.


Step 4 (Optional) Specify a default connection rate value.

The default connection rate value must be less than the maximum bandwidth value.

Use the default connection rate for any non-predefined terminals that you invited without specifying a bandwidth for those terminals during meeting scheduling process or in-meeting control operations.

Step 5 (Optional) If the meeting type supports lecture mode, select Lecture Mode Support to enable this support.

Step 6 (Optional) Select Auto Attendant Support to specify this meeting type as the Auto Attendant meeting type.


Viewing a List of MCUs Containing a Specified Meeting Type

Procedure


Step 2 Select Detail in the MCU column to see a list of MCUs containing the specified meeting type.

Creating or Modifying a Meeting Type Group

This is function is only available with iVIEW Management Suite with Multi-tenant support. For iVIEW Management Suite that supports multi-tenant feature, the service provider administrator can define a Meeting Type Group on the Meeting Type Group tab. Each meeting type group is assigned multiple meeting types. A meeting type group can then in turn be assigned to an organization. This allows only a specific subset of all meeting types.The meeting types defined in the meeting type group assigned to the organization are available to that organization.

Procedure


Step 2 Select Meeting Type Groups.

Step 3 Select the link in the Group Name column for the group you require, or select Add to create a new meeting type group.

Step 4 Enter a name and, optionally, a description of the group in the appropriate fields.

Step 5 Use the arrows to select the meeting types included in this group.



Synchronizing MCU Information with iVIEW Management Suite

When a new MCU is initially configured, its internal information is downloaded to iVIEW Communications Manager. If you change the initial configuration, you must update the iVIEW Communications Manager.

Procedure

Step 1 Select Resource Management in the sidebar menu.

Step 2 Select MCU.

Step 3 Select the MCU entry you want to update in the Name column.

Step 4 Select Synchronize.

The information download includes the number of cards the MCU has and the resource capacity of each card.

Searching for an MCU Profile

Procedure


Step 2 Select MCU.

Step 3 Enter the partial or complete name of the MCU in the Name field.



Step 5 To return to the complete list of MCUs, clear the Name field, and then select Search.


Taking an MCU Offline

Procedure


Step 2 Select MCU.

Step 3 Select the link in the Name column for the MCU you require.

Step 4 To take the MCU offline temporarily, select Take this MCU offline and reschedule all meetings on this MCU up to this date and set the date to bring the MCU online again.

Step 5 To take the MCU offline permanently, select Take this MCU offline and reschedule all meetings currently on this MCU.


When you take the MCU offline, the following changes occur:

• iVIEW Communications Manager cannot schedule meetings for the offline MCU.

• All meetings currently in progress are terminated. iVIEW Communications Manager attempts to reschedule upcoming meetings for the offline MCU on other MCUs that use the same services and have sufficient, available resources. If no replacement MCUs are available when the MCU status is changed back to online, upcoming meetings are lost and not restored.

• If the MCU goes offline temporarily, iVIEW Communications Manager attempts to reschedule all meetings scheduled to this MCU from the time the MCU goes offline to the specified date for its return online.

• If the MCU goes offline permanently, iVIEW Communications Manager attempts to reschedule all future meetings scheduled to this MCU.

Removing an MCU Profile

You must take an MCU offline before you can remove it from the iVIEW Management Suite database.

Procedure


Step 2 Select MCU.

Step 3 Select the MCU entry you want to delete in the Name column.

Step 4 Select Delete and then OK.

The MCU profile is deleted from the scheduler and information about the MCU is removed from the database.


Connecting to the Gatekeeper

• Selecting a Gatekeeper Type for Your Deployment....................................... page 24

• Creating a Gatekeeper Profile ............................................................... page 25

• Removing a Gatekeeper Profile .............................................................. page 27

• Searching for a Gatekeeper Profile.......................................................... page 27

• Accessing Meetings from an External Gatekeeper ........................................ page 28

Selecting a Gatekeeper Type for Your Deployment

iVIEW Management Suite

• Using an Internal Gatekeeper ................................................................ page 24

• Using a Standalone RADVISION SCOPIA ECS Gatekeeper ................................. page 24

• Using an External Gatekeeper ............................................................... page 25

Using an Internal Gatekeeper

If the version of iVIEW Management Suite that you are using is shipped with an internal gatekeeper for the SCOPIA bundle, use the default gatekeeper configuration that is already configured after iVIEW Management Suite installation. The internal gatekeeper is a light version of the RADVISION ECS Gatekeeper. The internal gatekeeper is restricted to only work in authorization mode (whereas the standalone ECS Gatekeeper can work either in authorization mode or non-authorization mode).

iVIEW Communications Manager acts as the authorization server for any traffic going through the internal gatekeeper working in fully routed mode. In such cases, iVIEW Communications Manager can manage endpoint-initiated calls and point-to-point calls.

Register MCUs, gateways and endpoints (terminals) to the iVIEW Management Suite internal gatekeeper.

Using a Standalone RADVISION SCOPIA ECS Gatekeeper

SCOPIA iVIEW Communications Manager can act as the authorization server for any traffic going through standalone SCOPIA ECS Gatekeepers working in a fully routed mode. With this mechanism, SCOPIA iVIEW Communications Manager can manage endpoint-initiated calls and point-to-point calls, and present a group of distributed, deployed MCUs as a single pool of video and audio resources. This feature is known as Virtual MCU.

Register MCUs, gateways, and endpoints (terminals) to SCOPIA ECS Gatekeeper Gatekeepers


Using an External Gatekeeper

SCOPIA iVIEW Communications Manager supports external H.323 gatekeepers (such as the Cisco IOS H.323 Gatekeeper) when the external gatekeeper is configured as a neighbor to the iVIEW Management Suite internal gatekeeper or ECS.

Register only endpoints (terminals) to an external. Register gateways and MCUs to the internal gatekeeper or ECS.

Creating a Gatekeeper Profile

Only an Organization Administrator (or Service Provider Administrator when Multi-tenant support is enabled) has permission to configure an H.323 gatekeeper in the system for video conferences using the H.323 protocol.

• Defining the Gatekeeper Address............................................................ page 25

• Defining Dialing Plan Settings ................................................................ page 26

• Defining iVIEW Communications Manager as the Gatekeeper Authorization Server page 26

Defining the Gatekeeper Address

During this procedure you define the management IP address of the gatekeeper. The real-time IP address is extracted automatically using either the device SNMP interface or the XML interface. The real-time IP address is used for zone matching. Each time a new element is added to the network iVIEW Network Manager uses the real-time IP address to check whether the new element is registered to this gatekeeper or not.

If the added element management IP does not match the real-time IP address of the gatekeeper, you need to add a new zone on the gatekeeper, creating an inferred gatekeeper. Once a user tries to connect to this new element iVIEW Network Manager tries to use the management IP address for connection and if it does not exist it tries to connect using a signaling IP address.

When configuring a redundant gatekeeper, use the same settings used for the main gatekeeper.

Procedure


Step 2 Select Gatekeeper/SIP server.

Step 3 Select the link in the Name column for the gatekeeper you require, or select Add to create a new gatekeeper profile.

Step 4 Locate the General section.

Step 5 Enter the name and the management IP address of the gatekeeper in the relevant fields.

Step 6 Select the gatekeeper model.

If you select Other in the Model field, select H.323 in the Protocol field.


Step 7 Select the device island to which the gatekeeper belongs from the Location list.

Each device island can have only one gatekeeper.

The Location field is visible only when the IP Topology tab is activated in the iVIEW Communications Manager Configuration Tool under System Configuration > UI Settings.


Defining Dialing Plan Settings

Procedure



Step 3 Select the link in the Name column for the gatekeeper you require, or select Add to create a new gatekeeper profile.

Step 4 Locate the Dialing Plan Information section.

Step 5 (Optional) Select Hierarchical if the gatekeeper has a parent-child relationship with its neighbor in the dialing plan, rather than a flat peer relationship.

If you select Hierarchical, the Parent Gatekeeper list becomes active. Select a parent zone for the gatekeeper from the list. None is automatically selected in the list if the gatekeeper is a parent at the top of the hierarchy.

Do not select Hierarchical for a root gatekeeper. The root gatekeeper in a hierarchical tree structure has no parent but may have peer neighbors.

Step 6 (Optional) Select Stripping for a gatekeeper that is configured to strip (remove) zone prefixes.

Step 7 Select Add Zone Prefix to add a zone prefix that matches the configuration of the gatekeeper.


Defining iVIEW Communications Manager as the Gatekeeper Authorization Server

Procedure



Step 3 Select the link in the Name column for the gatekeeper you require.

Step 4 Locate the Advanced section.

The Advanced section appears if you are using the internal gatekeeper or ECS.


Step 5 Select Enable Gatekeeper advanced features (authorization and point-to-point) to set iVIEW Communications Manager as the authorization server of the internal gatekeeper or ECS.

This option is checked by default if you are using the internal gatekeeper or ECS.

iVIEW Communications Manager will initiate a connection to the ECS for authorization and call control.

Step 6 If you are using the internal gatekeeper—You do not need to modify the internal gatekeeper default values for the Port, SNMP Get Community and SNMP Set Community fields.

Step 7 If you are using the ECS—Ensure the SNMP community names are correct.

iVIEW Communications Manager requires this to properly initiate the authorization connection with the ECS.

You can view the SNMP Get Community and SNMP Set Community fields on the ECS host server under Control Panel > Administrative Tools > Services > SNMP Service > Security.

Step 8 Ensure the following configuration options are set on the ECS or internal gatekeeper:

• Under ECS > Settings > Calls, set the Routing Mode field to Call Setup (Q.931) and Call Control (H.245).

• Under ECS > Settings > External API:

• Select Allow Authorization servers to connect.


Removing a Gatekeeper Profile

Procedure



Step 3 Select the gatekeeper entry you want to delete in the Name column.


The gatekeeper profile is deleted from the scheduler and information about the gatekeeper is removed from the database.

Searching for a Gatekeeper Profile

Procedure



Step 3 Enter all or part of the name of the gatekeeper you want to find in the Name field.



Search results are listed. If you are using the internal gatekeeper or ECS, the following information about connection status is available in the list of search results:

• Authorization Connection indicates whether or not iVIEW Communications Manager acts as the authorization server for the internal gatekeeper or ECS. This connection needs to appear as connected for advanced iVIEW Communications Manager features such as Virtual MCU and point-to-point call control to function correctly.

• Call Control Connection indicates whether or not a Call Control API connection is established between the gatekeeper and iVIEW Communications Manager. This corresponds to the Settings > Calls > Enable XML call control field in the ECS user interface.

• SNMP Connection indicates whether or not the SNMP connection between the iVIEW Communications Manager and the gatekeeper is established.

Step 5 To return to the complete list of gatekeepers, clear the Name field, and then select Search.

Accessing Meetings from an External Gatekeeper

If iVIEW Communications Manager ECS is neighbored to an external gatekeeper (for example, a Cisco IOS Gatekeeper), perform the following configuration steps in the ECS web user interface to enable dial-in and dial-out to work properly between the ECS and the external gatekeeper:

Procedure

Step 1 Add the external gatekeeper as a neighbor to this ECS at Hierarchy > Neighbors, and define the appropriate zone prefix according to the dial plan.

When iVIEW Communications Manager works in authorization mode with the ECS, meeting IDs start with the iVIEW Communications Manager meeting ID prefix (configured via the Meeting ID Prefix field at Configuration Tool > System Configuration > Scheduling Settings screen).

Step 2 Add a new service to the Services tab and select Conference Hunting.

The service prefix should be the same as the Meeting ID Prefix field in the iVIEW Management Suite Configuration Tool.

Step 3 On the Endpoints tab, select Add Predefined to add a new dummy endpoint for routing purposes.

Step 4 Enter dummy values in the Registration IP and Call Signaling IP fields.


Step 5 Add the following two aliases:

• Value = Fake Terminal, Type = Name

• Value = Meeting ID Prefix value, Type = Phone number

Step 6 Select Upload to save your changes.

Note: iVIEW Communications Manager automatically performs the above steps on the internal gatekeeper, so no extra internal gatekeeper configuration is necessary.

Step 7 In the external gatekeeper interface, add the ECS (or internal gatekeeper) as a neighbor to this external gatekeeper, and define the zone prefix for the ECS according to the dial plan.

Step 8 Define the following forwarding rules in the external gatekeeper interface:

• Forward any dial strings that begin with iVIEW Communications Manager Meeting ID Prefix to the ECS.

• Forward any dial strings that begin with MCU service prefix or Gateway service prefix to the ECS.

Since terminals are registered to the external gatekeeper, these two forwarding rules allow these terminals to dial into the iVIEW Communications Manager meetings from the external gatekeeper.

Connecting to the iVIEW Communications Manager

• Creating a Gateway Profile ................................................................... page 29

• Searching for a Gateway Profile ............................................................. page 31

• Taking a Gateway Offline ..................................................................... page 32

• Removing a Gateway Profile.................................................................. page 32

Creating a Gateway Profile

Configure gateways in your network to enable PSTN/ISDN/mobile terminals to join a meeting. iVIEW Communications Manager uses the gateway information to provide proper dialing information for meeting participants, and to dial out to terminals to invite them to meetings. iVIEW Communications Manager also manages gateway resources to allow successful call scheduling using network gateways.

During this procedure you specify the management IP of the gateway. The real-time IP is extracted automatically using either the device SNMP interface or its XML interface.

When you add a gateway, settings in iVIEW Communications Manager must be consistent with the actual gateway configuration. We recommend the following:

• If you make changes to the gateway, maintain the IVR and DID numbers in iVIEW Communications Manager.

• To ensure that there are no gateway ports available for scheduled and ad hoc calls, maintain capacity information.


Procedure


Step 2 Select Gateway.

Step 3 Select the link in the Name column for the gateway you require, or select Add to create a new gateway profile.

Step 4 Enter the name of the gateway in the Name field.

Step 5 Select a gateway model and enter the management IP address in the relevant fields.

Note: If multiple gateways are pooled together in a local network with the same access phone number, you can enter multiple IP addresses in the IP Address field to indicate the gateways in the gateway pool. IP addresses are separated by a colon (:).

Step 6 Select the gatekeeper from the Registered To list to which the gateway is registered.

Step 7 Select the device island from the Location list to which the gateway belongs.


Step 8 Select Add Service and select the bandwidth for the gateway or gateway pool. For example, for an E1 line, the bandwidth should be 30 B-channels (3940 Kbps).

Step 9 Enter a gateway phone number.

a. Enter a description of the phone number for the gateway in the Description field.

b. Enter the numeric prefix required to make an international long distance call in the International Access Code field.

c. Enter the numeric prefix required to make a long distance call within the same country in the Domestic Long Distance Prefix field.

d. Enter the country code for the gateway phone number in the Country Code field. iVIEW Communications Manager adds this prefix when dial-out is performed from this gateway to a terminal located in a different country than the country in which the gateway is located.

e. If Allow Out of Area Calls is not selected, only endpoints with the same area code as the gateway are allowed to reach iVIEW Communications Manager via the gateway.

f. If you select Allow Out of Area Calls, the gateway accepts incoming calls to iVIEW Communications Manager from terminals with a different area code than that of the gateway.

g. Enter the domestic area code of the gateway number in the Area Code field.

h. Specify a local telephone number in the Telephone Number field that you want to assign to the specific port.

i. Enter a number in the To access an outside line for local calls, dial field for a gateway with no direct access to an outside line for local calls.

j. Enter a number in the To access an outside line for long distance calls, dial field, for a gateway with no direct access to an outside line for long distance calls.


k. Assign the ISDN device island that the gateway or gateway pool belongs to. If ISDN Topology is hidden, then this field is also hidden.

Step 10 Select Add Service to add or modify the gateway service.

Note: If you select Restricted Mode in the Bandwidth section, 56 appears in the Kbps list. Multiples of 56 Kbps are used instead of multiples of 64. iVIEW Communications Manager does not support gateway services whose bandwidth is set to “auto” since iVIEW Communications Manager needs the specific bandwidth to perform resource reservation. If there is a gateway service with “auto” bandwidth, when you configure this service in iVIEW Communications Manager, select a bandwidth value to best approximate the average bandwidth endpoints use when dialing that service.

Step 11 Set the Advanced Settings.

• Set the gateway port used for signaling in the Signaling Port field. By default, it is left blank and signaling port will be negotiated dynamically on the fly.

• Set the SNMP community name required by iVIEW Communications Manager to communicate with the gateway in the SNMP Get/Set Community fields.

• Select Dial-in Only to mark the gateway for use only with terminals that users dial into. iVIEW Communications Manager does not schedule dial-out calls on this gateway.


Searching for a Gateway Profile

Procedure



Step 3 Enter the partial or complete name of the gateway in the Name field.



The Status column indicates whether the gateway is online or not. iVIEW Communications Manager only uses an online gateway for meeting scheduling and creation.

The SNMP Connection column indicates whether or not iVIEW Communications Manager established an SNMP connection with the gateway.

Step 5 To return to the complete list of gateways, clear the Name field, and then select Search.


Taking a Gateway Offline

Once a gateway is configured, it is automatically brought online so that iVIEW Communications Manager can schedule resources.

Procedure



Step 3 Select the link in the Name column for the gateway you require.

Step 4 To take the gateway offline temporarily, select Take this gateway offline and reschedule all meetings on this gateway up to this date and set the date to bring the gateway online again.

Step 5 To take the gateway offline permanently, select Take this gateway offline and reschedule all meetings currently on this gateway.


When you take the gateway offline, the following changes occur:

• iVIEW Communications Manager cannot schedule meetings for the offline gateway.

• All meetings currently in progress are terminated. iVIEW Communications Manager attempts to reschedule upcoming meetings for the offline gateway on other gateways that use the same services and have sufficient, available resources. If no replacement gateways are available when the gateway status is changed back to online, upcoming meetings are lost and not restored.

• If the gateway goes offline temporarily, iVIEW Communications Manager attempts to reschedule all meetings scheduled to this gateway from the time the gateway goes offline to the specified date for its return online.

• If the gateway goes offline permanently, iVIEW Communications Manager attempts to reschedule all future meetings scheduled to this gateway.

Removing a Gateway Profile

You must take a gateway offline before you can remove it from the iVIEW Management Suite database.

Procedure



Step 3 Select the gateway entry you want to delete in the Name column.


The gateway profile is deleted from the scheduler and information about the gateway is removed from the database.


Connecting to an SIP Server

• Creating an SIP Server Profile ................................................................ page 33

• Enabling the MCU to Work in SIP Mode ..................................................... page 34

• Removing a SIP Server Profile ................................................................ page 35

• Searching for a SIP Server Profile............................................................ page 35

• Disabling the SIP Back-to-Back User Agent................................................. page 36

Creating an SIP Server Profile

iVIEW Communications Manager includes an embedded SIP Back-to-Back User Agent (B2BUA) component for managing SIP traffic to network devices (such as to MCUs) which are managed by iVIEW Communications Manager.

To enable iVIEW Communications Manager to operate with SIP endpoints, configure iVIEW Communications Manager with an external SIP server to which SIP endpoints are registered.

Procedure



Step 3 Select the link in the Name column for the SIP server you require, or select Add to create a new SIP server profile.

Step 4 Enter the name and IP address or Fully Qualified Domain Name (FQDN) of the SIP server in the relevant fields.

Step 5 Select the SIP server model.

You can select Microsoft LCS 2005/OCS 2007 or other third-party SIP servers. iVIEW Communications Manager is interoperable with the following external SIP servers:

• Cisco Unified Communications Manager Release 5.0 or later

• Microsoft Live Communications Server 2005 with Service Pack 1

• Microsoft Office Communications Server 2007

• Microsoft Office Communications Server 2007 R2

• Broadsoft IPCentrix

Step 6 (Optional) If you select Other in the Model field, select SIP in the Protocol field.

Step 7 Select the device island to which the SIP server belongs from the Location list.

Each device island can have only one SIP server.


Step 8 Enter the name of the SIP server in the SIP Domain field.

Step 9 (Optional) Enter the name of a preferred and an alternative DNS server in the relevant fields.



Enabling the MCU to Work in SIP Mode

Perform the following configuration steps in the MCU web user interface.

Procedure

Step 1 Select Configuration.

Step 2 Select Protocols.

Step 3 Locate the SIP section.

Step 4 Select SIP to enable MCU communication with the SIP proxy.

Step 5 Enter the SIP domain of the MCU in the Default SIP domain field as defined in the SIP server.

An example of a SIP domain is company.com.

Step 6 Select Locate automatically to instruct the MCU to automatically locate one of the SIP proxy servers that are present in the domain,

or

Select Specify and enter the following:

• An IP address or host name of the SIP p roxy, f or e xample proxy.company.com.

• The communication port number of the SIP proxy address. The default port is 5060.

• The transport connection type for sending messages to the SIP proxy according to the type supported by the SIP proxy—UDP or TCP.

This field is mandatory. The default is UDP.

Note: The Locate automatically option works only if you have configured a valid IP address at Configuration > Setup > Network > DNS server1 or DNS server2.

Step 7 Select Use registrar to instruct the MCU to register with a SIP registrar and to send service information to the registrar.

Step 8 Enter the following information:

• The IP address or the host name of the SIP registrar in the IP address field.

This field is mandatory.

• The communication port number of the SIP registrar address.

• The transport connection type for sending registration requests to the registrar according to the type supported by the SIP registrar—UDP or TCP.

This field is mandatory. The default is UDP.

Step 9 Select More.

Step 10 Enter the number of the signaling port on which the MCU communicates with the SIP proxy.

The default is 5060.


Step 11 Select Use proxy digest authentication to enable MCU authentication with a SIP proxy server using user name and password.

Authentication is performed as defined in RFC 2617. This field is disabled by default.

Step 12 Enter the MCU user name and password.

The user name and password must match the name and password defined on the SIP proxy server.

Step 13 Select Use registrar digest authentication to enable MCU authentication with a SIP registrar using user name and password.

Authentication is performed as defined in RFC 2617. This field is disabled by default.

Step 14 Select Use ‘Empty Invite’ when sending Invite messages to endpoints to enable the remote endpoint to indicate preferred audio and video channels.

Step 15 Select Using Microsoft OCS to enable the MCU to work with Microsoft Office Communications Server (OCS).


Removing a SIP Server Profile

Procedure



Step 3 Select the SIP server entry you want to delete in the Name column.


The SIP server profile is deleted from the scheduler and information about the SIP server is removed from the database.

Searching for a SIP Server Profile

Procedure



Step 3 Enter all or part of the name of the SIP server you want to find in the Name field.



Step 5 To return to the complete list of SIP servers, clear the Name field, and then select Search.


Disabling the SIP Back-to-Back User Agent

You can disable the B2BUA if iVIEW Communications Manager is currently not operating with an external SIP server to which SIP endpoints are registered.

Procedure

Step 1 Go to Control Panel > Administrative Tools > Services on the iVIEW Management Suite server.

Step 2 Locate the service named “SIP Server” and stop it.

Step 3 Use a text editor to open the vcs-core.properties file located at JBOSS_HOME\bin on the iVIEW Management Suite server where JBOSS_HOME is the home directory of the JBOSS application server used in iVIEW Management Suite.

By default, JBOSS_HOME is C:\Program Files\RADVISION\iVIEW Suite\iCM\jboss\bin

Step 4 Set the following line as shown:

vnex.vcms.core.sip.serverAddress=

Step 5 Save and close the vcs-core.properties file.

Step 6 Restart the SIP Server service for the change to take affect.

Creating Meeting Rooms

A meeting room is the physical location of one or more terminals. Meeting rooms are also used for non-video conference meetings in which no terminals are involved.

• Enabling Meeting Room Support ............................................................. page 36

• Creating a Meeting Room Profile ............................................................ page 37

• Sending Meeting Details by Email ........................................................... page 37

• Searching for a Meeting Room Profile....................................................... page 37

• Removing a Meeting Room Profile ........................................................... page 38

Enabling Meeting Room Support

By default, the Meeting Rooms tab is hidden in iVIEW Communications Manager. Enable support for meeting rooms as follows:

Procedure

Step 1 Select Advanced Settings in the sidebar menu.

Step 2 Select Look and Feel.

Step 3 Deselect Hide Meeting Rooms.



Creating a Meeting Room Profile

Procedure


Step 2 Select Meeting Rooms.

Step 3 Select the link in the Name column for the meeting room you require, or select Add to create a new meeting room profile.

Step 4 Enter the name and location of the meeting room in the relevant fields.


Sending Meeting Details by Email

You can define an email address to enable an endpoint that participates in a meeting to receive notification email messages.

By default, this option is hidden.

Procedure



Step 3 Deselect Hide Meeting Notification E-mail for meeting rooms and terminals.




Step 7 Select the link in the Name column for the meeting room you require.

Step 8 Select Meeting e-mail notification address and enter the email address for the meeting room.

Step 9 Select a time zone for the meeting room.

The default value is set at Advanced Settings > Default User Settings > Default Time Zone.


Searching for a Meeting Room Profile

Procedure



Step 3 Enter the partial or complete name of the meeting room in the Name field.




Step 5 To return to the complete list of meeting rooms, clear the Name field, and then select Search.

Removing a Meeting Room Profile

Procedure



Step 3 Select the meeting room entry you want to delete in the Name column.


The meeting room profile is deleted from the scheduler and information about the meeting room is removed from the database.

Registering Endpoints with a Gatekeeper

• Creating Terminal Profiles .................................................................... page 38

• Removing a Terminal Profile.................................................................. page 44

• Searching for a Terminal Profile ............................................................. page 44

Creating Terminal Profiles

The term “terminal” refers to any kind of endpoint (H.323, SIP, ISDN, or mobile) used for video conferencing.

• Defining H.323 IP Terminals .................................................................. page 39

• Defining SIP IP Terminals...................................................................... page 40

• Defining ISDN/PSTN H.320 Terminals ....................................................... page 41

• Defining Mobile Terminals .................................................................... page 42

• Defining Dual H.320 and H.323 Terminals.................................................. page 43

Note: To avoid conflicts between endpoint-initiated point-to-point meetings and endpoint-initiated multipoint meetings, the names of endpoints and terminals registered to gatekeepers in iVIEW Communications Manager cannot start with the same prefix as the MCU service or as a meeting type ID in iVIEW Communications Manager.


Defining H.323 IP Terminals

Define all H.323 terminals registered to gatekeepers that are configured in iVIEW Communications Manager.

Procedure


Step 2 Select Terminals.

Step 3 Select the link in the Name column for the terminal you require, or select Add to create a new terminal profile.

Step 4 (Optional) Select Default Users to associate this terminal as the default terminal for selected users defined in iVIEW Communications Manager.

Step 5 Select OK to apply your selections and to close the Select Users window.

Step 6 (Optional) Enter any description text that you may have for this terminal in the Description field.

Step 7 Select IP(H.323) from the Terminal Type list.

Step 8 Enter the E.164 IP phone number of the terminal registered on the gatekeeper in the IP Phone Number field as specified in the Registered to field.

If the terminal is not registered to a gatekeeper, enter the IP address of the terminal in the IP Phone Number field.

Step 9 Select a topology setting from the Location drop-down list.


Step 10 Define the default bandwidth for the terminal by selecting bandwidth settings in the Video Profile dropdown list. iVIEW Communications Manager uses the bandwidth number to reserve resources for this terminal.

Step 11 (Optional) Select an entry from the Meeting Room field to associate this terminal with a meeting room defined in iVIEW Management Suite.

Step 12 (Optional) Select Display in global address book (Enterprise edition only).

Step 13 (Optional) Select VIP to provide enhanced quality video to this terminal.



Defining SIP IP Terminals

Define all SIP terminals registered to gatekeepers that are configured in iVIEW Communications Manager.

Procedure







Step 7 Select IP(SIP) from the Terminal Type list.

Step 8 Define the terminal name or terminal number in the SIP URI field, followed by the SIP server domain name and a suffix derived from the domain name of the SIP server.

For example, <terminal name>@<SIP server domain name> or “user@domain_name.com”.

Step 9 Define the default bandwidth for the terminal by selecting bandwidth settings in the Video Profile dropdown list. iVIEW Communications Manager uses the bandwidth number to reserve resources for this terminal.







Defining ISDN/PSTN H.320 Terminals

Define all H.320 terminals that you want iVIEW Communications Manager to automatically invite to a meeting and manage their availability.

Procedure







Step 7 Select ISDN/PSDN(H.320) from the Terminal Type list.

Step 8 Define the default bandwidth for the terminal in the Bandwidth field. iVIEW Communications Manager uses the bandwidth number to reserve resources for this terminal.



Step 10 Select Restricted Mode for a PSTN/ISDN network working in restricted mode.

Step 11 Enter the phone number of the terminal in the Country Code, Area Code and Number fields.

If you do not specify this information, iVIEW Communications Manager cannot find the optimal gateway for the terminal when scheduling a conference.




Defining Mobile Terminals

Define all mobile terminals that you want iVIEW Communications Manager to automatically invite to a meeting and manage their availability.

Procedure







Step 7 Select Mobile from the Terminal Type list.

Step 8 Define the default bandwidth for the terminal in the Bandwidth field. iVIEW Communications Manager uses the bandwidth number to reserve resources for this terminal.



Step 10 Enter the phone number of the terminal in the Country Code, Area Code and Number fields.


Step 11 Select 3G for 3G terminals.




Defining Dual H.320 and H.323 Terminals

Procedure







Step 7 Select Dual(H.320 and H.323) from the Terminal Type list.

Step 8 Enter the E.164 IP phone number of the terminal registered on the gatekeeper in the IP Phone Number field as specified in the Registered to field.

If the terminal is not registered to a gatekeeper, enter the IP address of the terminal in the IP Phone Number field.

Step 9 Define the default bandwidth for the terminal in the IP Bandwidth and ISDN Bandwidth fields. iVIEW Communications Manager uses the bandwidth number to reserve resources for this terminal.



Step 11 Select Restricted Mode for a PSTN/ISDN network working in restricted mode.

Step 12 Enter the phone number of the ISDN terminal in the Country Code, Area Code and Number fields.






Removing a Terminal Profile

Procedure



Step 3 Select the terminal entry you want to delete in the Name column.


The terminal profile is deleted from the scheduler and information about the terminal is removed from the database.

Searching for a Terminal Profile

Procedure



Step 3 Enter the partial or complete name of the terminal in the Name field, or enter the partial or complete IP or ISDN phone number of the meeting room in the Dialing Info field.

The ISDN phone number of the terminal should not include dashes or spaces.

The ISDN phone number can only be used when you select ISDN/PSTN(H.320) or Dual(H.320 and H.323) in the Terminal Type field.

Both IP and ISDN numbers are displayed if the terminal is configured as a dual terminal.

Step 4 (Optional) Select Display All to include in the terminals displayed in the list all the terminals that are currently in the global address book.

Terminals in the global address book are indicted by a book icon after the terminal name.

Step 5 (Optional) Select Conceal All to remove from the terminals displayed in the list all the terminals that are currently in the global address book.

Terminals in the global address book are indicted by a book icon after the terminal name.



Step 7 To return to the complete list of meeting rooms, clear the Name and Dialing Info fields, and then select Search.


4 About Telepresence Support

The concepts described in the following sections relate to the different telepresence endpoints as a single unified end point.

• About Supported Telepresence Systems.................................................... page 45

• Licensing for Telepresence ................................................................... page 45

• About Telepresence Deployment Considerations ......................................... page 46

• Configuring Telepresence Systems .......................................................... page 46

• Telepresence Resource Calculation ......................................................... page 48

• Scheduling Telepresence Systems ........................................................... page 48

About Supported Telepresence Systems

The Elite MCU supports the following telepresence (TP) systems when using iVIEW Management Suite:

• Polycom RPX 200 (2 screens)

• Polycom RPX 400 (4 screens)

• Polycom Telepresence X 200 (2 screens)

• Polycom Telepresence X 300 (3 screens)

• Tandberg T3 (3 screens)

• LifeSize Conference (3 screens)

• Cisco Telepresence

Licensing for Telepresence

Although the SCOPIA MCU does not manage the telepresence logic as a standalone component, telepresence support requires specific license on the SCOPIA MCU.

iVIEW Communications Manager does not require any specific license for supporting telepresence. iVIEW Communications Manager needs to be aware of the SCOPIA MCU licensing in order to deliver warning messages to administrators and for display purposes.


The MCU Resource Tab displays a small telepresence icon near the MCU which are licensed for support.

About Telepresence Deployment Considerations

Special considerations should be made for deploying telepresence systems based on your deployment type:

• In mixed deployments with both telepresence enabled MCUs and telepresence disabled MCUs, iVIEW Management Suite chooses the MCU host according to the end point specifications.

• In centralized deployments with telepresence Meetings, iVIEW Management Suite will chose a telepresence enabled MCU. For centralized deployments with Non telepresence Meetings, iVIEW Management Suite gives preference to a MCU with no telepresence support. If there are no resources on the non telepresence MCU, it will use a telepresence enabled MCU.

• In distributed deployments with telepresence Meetings, iVIEW Management Suite chooses a telepresence enabled MCU according to the best location. For distributed deployments in non telepresence Meetings, iVIEW Management Suite chooses the best MCU according to location even if the MCU is telepresence enabled; Location has higher priority than telepresence preference.

Configuring Telepresence Systems

The administrator defines a telepresence system as an end point resource in iVIEW Management Suite.

There will no way to dynamically define a telepresence system as an external end point from the scheduling interface - including the iVIEW Communications Manager user interface, Outlook plug-in, or Lotus Notes Plug-in.

When configuring telepresence, note the following restrictions and guidelines:

• Telepresence will be supported only for IP end points.

• Telepresence will be supported only for a bandwidth which is higher than 768Kbps.

• Video profiles will be grayed out and set to auto.

• Personal Terminal support – The telepresence terminal will not be associated with any specific user. The Choose Participant option will be hidden.

• The administrator will not be able to associate the telepresence terminal with a specific user.

• Administrators will not be able to change a defined end point into a telepresence end point, and vice versa. To do so, you must delete and redefine the end points again.

• The VIP option will unchecked and grayed out for any telepresence end points.

• If there is a collision with another defined end point, the system will pop up the appropriate error message.

• The telepresence will always be connected to the Master conference since we can only send a single video steam from the master to the slave.


Procedure



Step 3 Select Add.

Figure 4-1 Telepresence Configuration Screen

Step 4 Insert a Terminal Name and Description (optional).

Step 5 Select the Telepresence System check box.

Step 6 Select a System Type from the dropdown list.

Step 7 Input 2 to 4 IP phone numbers according to the system type.

Step 8 Select the Primary check box to define a primary terminal.


Step 9 (Optional) Select the Display in global address book check box. The telepresence end point will be represented in the address book as a single end point. The number which the system displays will be the number assigned tot the primary terminal. This relates to all the interfaces including:

• iVIEW Management Suite

• SCOPIA Desktop

• Lotus Notes Plug-in

• Outlook Plug-in

• Room Systems via H.350

Step 10 Select OK.

Once configured, the Terminal Resource tab displays a small icon near the end point name, dialing info numbers with relevant prefixes, and a tooltip indicating that the end point is a telepresence system.

Figure 4-2 Telepresence Terminal Icon

Telepresence Resource Calculation

Resources are calculated according to the number of supported screens.

For example: For scheduled telepresence end points which have two screens, iVIEW Management Suite calculates 2 HD ports. For scheduled telepresence end points which have four screens, iVIEW Management Suite calculates 4 HD ports.

If a telepresence system is dialing into the system (which can be done from each one of the pre-configured numbers), iVIEW Management Suite attempts to allocate the total number of ports on the master conference, and if managed to do so, it will authorize to connect the call.

Scheduling Telepresence Systems

When scheduling a telepresence system, the following restrictions apply:

• Enabled telepresence MCU must be selected.

• Telepresence must be scheduled to the master conference.

• Pre-positioning the telepresence end point in a specific sub frame will not be supported for the telepresence end point.


5 Managing Your iVIEW Communications Manager User Profile

Based on your user type, the iVIEW Management Suite interface displays a different user interface. This section provides profile management information for Operators, Organizers, and Regular Users.

• Viewing Your User Profile Settings .......................................................... page 49

• Modifying Your Password ...................................................................... page 50

• Modifying Your Email Address ................................................................ page 50

• Modifying Your Time Zone .................................................................... page 51

• Defining Your Meeting Display Preferences ................................................ page 51

• Defining Your Virtual Room Preferences.................................................... page 52

Viewing Your User Profile Settings

Procedure

Step 1 For Select the My Profile icon in the sidebar menu.

Figure 5-1 My Profile Icon

Step 2 View or edit your profile details as needed.

-or-

For Organizers and Regular Users, select My Preferences and edit your profile details as needed.

Step 3 Select OK to close the profile view.


Modifying Your Password

If your profile settings are stored on an external directory server, you cannot modify your password.

Procedure

Step 1 For Operators, select the My Profile icon in the sidebar menu.

-or-

For Organizers and Regular Users, select the My Profile then select My Info.

Step 2 Select Modify Password.

Figure 5-2 Modify Password

Step 3 Complete the information as required and Select OK to save your changes.

Modifying Your Email Address

Your email address is a required field. If your profile settings are stored on an external directory server, you cannot modify your e-mail address.

Procedure

Step 1 For Operators, select the My Profile icon in the sidebar menu.

-or-

For Organizers and Regular Users, select My Profile then select My Info.

Step 2 Modify your email address as required.


Note: Depending on your user type, you can follow the procedures above to modify other details of your profile, including your name, telephone contact, company, company branch, time zone, date display format, name display format, time zone, or to enable full-screen display.


Modifying Your Time Zone

Procedure

Step 1 Select My Profile in the sidebar menu.

Step 2 Select My Info.

Step 3 Select Advanced.

Step 4 Select the required time zone.


Defining Your Meeting Display Preferences

Procedure


Step 2 Select My Preferences.

Step 3 Select a default virtual room from the drop-down list.

The default virtual room is automatically selected when you schedule a meeting from the SCOPIA iVIEW Management Suite Web interface.

For LDAP users, the virtual rooms created during LDAP synchronization are automatically set as the default virtual room.

Step 4 Select Don’t include me in the meeting if you do not want to be automatically included in the Selected Participants list on the Invite tab when you schedule a new meeting.

Step 5 Enter a value in Delete meeting history items older than n days to delete meetings from My Meetings > History after the specified number of days.

Step 6 Select Use Full Screen Display to display meetings without a menu or title bar in your browser.

Deselect to display meetings using default browser settings.

Step 7 Select an option from the Name Display Format list to change the way your name is displayed in meeting-related information and in the meeting video display.

Step 8 Select Last name or First name from the Sort by list to change the sort order for participant name columns in the User interface.

Step 9 Select an option from the Date Display Format list to change the way dates are displayed in the user interface.



Defining Your Virtual Room Preferences

Procedure


Step 2 Select My Info.

Step 3 Select Virtual Room Setting.

Meeting Operators can define multiple virtual rooms.

Meeting Organizers can define only one virtual room and can configure only basic information such as meeting type and conference PIN.

Step 4 Enter a virtual room number and name in the relevant fields.

The virtual room should be unique in the system.

The virtual room number is generated automatically and is not editable if the administrator has downloaded user profile information from the LDAP server.

Step 5 Select a meeting type.

A meeting type is required to schedule a meeting.

• Non Video Conference—Only users and meeting rooms are scheduled for a meeting. No terminals are involved.

• Point to Point meeting type—Only two terminals are scheduled for a meeting and there is no use of MCU ports for the meeting.

This feature is only available if advanced call control is enabled on the Enhanced Communication Server profile.

• Audio Only—Only an audio bridge is scheduled for the meeting. There is no meeting room or video scheduled.

• HD/SD Continuous Presence—Supports high definition continuous presence. Supports image size of up to 720p. Default when adding a new service.

• HD Switched Video—Supports switched high definition video at rates of up to 4096 Kbps.

Note: Continuous Presence or Voice Activated meeting types are available only if your system administrator has configured a Sony endpoint with an embedded MCU. To host the meeting on the embedded MCU, you must be one of the meeting attendees and select a Sony endpoint with an embedded MCU.

Step 6 (Optional) Define the meeting access PIN in the Meeting PIN field.

Only integers are allowed. This PIN allows you to join a PIN-protected meeting.

Step 7 (Optional) Define the PIN that allows a user to perform moderation operations on a meeting in the Moderator PIN field.

Only integers are allowed. This PIN allows you to take control of a meeting from the In-meeting Control interface or from the endpoint using DTMF. Administrators and Meeting Operators can access the In-meeting Control screen without using the Moderator PIN.


Step 8 If you entered a moderator PIN, you can turn on the waiting room functionality by selecting Place participants in a 'waiting room' until the moderator joins the meeting.

Before the host joins the meeting, all connected participants are put into waiting room mode where they cannot hear or see one another. When the host terminal joins the meeting, the waiting room mode is removed and all participants can see and hear each other.

You can unlock the waiting room mode by taking control of the In-meeting Control screen after entering the moderator PIN and clicking Unlock waiting room.

Step 9 (Optional) If you entered a moderator PIN, you can automatically record a meeting when it starts by selecting Record meeting when starts (available only when a SCOPIA Desktop Server is configured in SCOPIA iVIEW Management Suite).

Step 10 For meetings enabled for SCOPIA Desktop attendance, you can specify whether the meeting will allow streaming by selecting the default streaming mode.

The default streaming mode determines the initial streaming state. Streaming can be disabled or enabled during the meeting by any SCOPIA Desktop Client that has meeting moderation rights.

By default, the Default Streaming Mode field is disabled and hidden from the user interface. If you need this field enabled, contact your system administrator.

Step 11 (Optional) Enter a description of the scheduled meeting for future reference.

The Description field is hidden by default. If you need this field displayed, contact your system administrator.


6 Managing Users Without an External Directory

• Creating or Modifying a User Profile ........................................................ page 54

• Removing a User Profile....................................................................... page 55

• Searching for a User Profile .................................................................. page 56

• Updating User Profiles......................................................................... page 56

• Creating a User Group......................................................................... page 57

• Modifying a User Group ....................................................................... page 57

• Removing a User Group ....................................................................... page 58

• Modifying a Service Provider Profile ........................................................ page 58

• Limiting Individual User Access to Meeting Types ........................................ page 59

• Limiting Group Access to Meeting Types ................................................... page 60

• Configuring Multiple Settings for User Groups ............................................ page 60

Creating or Modifying a User Profile

You can add or modify a user profile if iVIEW Communications Manager uses its own database for storing user profiles.

If your organization is synchronized with an external directory server to provision users, you can only modify the settings stored in iVIEW Communications Manager, such as virtual room, default terminals, allowed meeting types, groups, and time zone.

You can modify user passwords, email, telephone and time zone settings at Users > My Profile if those settings are not stored in the external directory server.

Note: Before configuring user profiles, set default settings for each user type at Advanced Settings > Default User Settings.


Procedure

Step 1 Select User Management in the sidebar menu.

Step 2 Select Users.

Step 3 Select the link in the Name column for the user you require, or select Add to create a new user profile.

Step 4 Enter the user ID and last name in the relevant fields.

Step 5 (Optional) Enter the first name, email address and password for the user in the relevant fields, and confirm the password.

Step 6 (Optional) Select Virtual Room Setting to add or modify virtual room settings for the user.


Step 8 Select a user type and enter telephone numbers in the relevant fields.

Step 9 Select Select Terminal to assign a default terminal to this user.

Step 10 Select Select next to the Allowed Meeting Types field to restrict this user to a subset of all available meeting types.

By default, all active meeting types are allowed.

Step 11 Select the group to which this user belongs from the Groups list.

Step 12 Select a default time zone.

Local time zones are used by default at User > My Meetings and User > All Meetings.

Step 13 Select Enabled in the Account Status field to activate the user account and allow the user to log in to iVIEW Communications Manager.

Step 14 Select a recording policy option for this user from the Recording Policy list.

Step 15 Select a location preference for this user.

Step 16 Enable the user to log in to SCOPIA Desktop, if required.

Step 17 Select an allowed bandwidth for SCOPIA Desktop calls.


The user profile is saved and iVIEW Communications Manager sends the user a notification e-mail containing login access information.

Removing a User Profile

You cannot remove a user profile if:

• You are provisioning users via an external directory server—The Delete button is disabled.

• The user is participating in an active meeting—You must wait for the user to leave the meeting.

• The user is the last user configured in the system with Organization Administrator privileges.


Procedure



Step 3 Select the user profile you want to delete in the Name column.


The user profile is deleted from the scheduler and information about the user is removed from the database.

Searching for a User Profile

Procedure



Step 3 Enter the partial or complete name of the user in the Name field, or enter the partial or complete virtual room for the user in the Virtual Room field.

Step 4 Select the group in which you want to perform the search.

The default is All Groups.



Step 6 To return to the complete list of users, clear the Name or Virtual Room field, and then select Search.

Updating User Profiles

If your organization uses an external directory server to provision users, you must update the list of iVIEW Communications Manager user profiles if users are removed from that directory server.

Meeting creation and meeting scheduling issues may arise if you do not update as required.


Procedure



Step 3 Go to Advanced Settings->LDAP Configurations and select Synchronize to import an up-to-date list of users from the external directory server.

The import process runs in the background enabling administrators to continue working with the system.

Once the new updated user database is created, users log in to iVIEW Communications Manager using a directory server login ID and password.

Creating a User Group

Procedure


Step 2 Select Groups.

Step 3 Select Add.

Step 4 Enter a name for the group in the Name field.

Step 5 Select participants and terminals from the Available Contacts list and select the right-arrow button to move them to the Selected Contacts list.

Step 6 Enter a cost code for group in the Cost Code field.

Note: A cost code is required when an administrator includes catering services for a group.


The group appears in the Groups tab list.

Modifying a User Group

Procedure



Step 3 Select the link in the Name column for the user group you require.

Step 4 Modify the name of the user group.



Removing a User Group

Procedure



Step 3 Select the group you want to delete.


The user group is deleted from the scheduler.

Modifying a Service Provider Profile

The Service Provider Administrator is a special kind of user. You can access and modify the profile of the service provider administrator of SCOPIA iVIEW Management Suite with multi-tenant support.

Procedure

Step 1 Log in as the service provider administrator, and then go to My Profile.

Step 2 Modify the login ID in the User ID field.

Step 3 Select Modify Password to modify the service provider administrator password.


Step 4 You can configure the following information:

• First name

• Last name

• Company

• Department

• Email

• Branch

• Telephone (Office)

• Telephone (Mobile)

• Time zone—Of the service provider administrator

Step 5 Set preferences for the service provider administrator:

• Select a format from the Date Display Format list (for example, DD/MM/YY) to determine the date display in the user interface.

• Select User Full Screen Display to display a window frame without a menu or title bar in the browser.

By default this option is selected. If the option is not selected, the standard browser display appears.

• Select a name format from the Name Display Format list.

Depending on the default browser settings, the options are first name first or last name first.

• Select a sort order (by last name or first name) in the Sort field.

• Select the order in which the day, month, and year are displayed in the Date Display field.

Step 6 Select OK to save and apply changes.

Limiting Individual User Access to Meeting Types

Meeting types listed on the Active Meeting Types tab are automatically listed in the Meeting Type field at User > Meeting Scheduling > Meeting. You can limit which meeting types are accessible by users.

Procedure





Step 5 Select Select next to the Allowed Meeting Types field.

Step 6 Select the required meeting types and select OK.



Limiting Group Access to Meeting Types

Procedure


Step 2 Select Provisioning.

Step 3 Select one or any of the groups listed in the Available Groups list and select the right-pointing arrow.

Step 4 Select Allowed Meeting Types and select Select.

Step 5 Select the required meeting types and select OK.


Configuring Multiple Settings for User Groups

The Provisioning tab offers a convenient way to set multiple parameters for large groups of users.

Procedure


Step 2 Select Provisioning.

Step 3 Select a group in the Available Groups list and select the right-pointing arrow to move the group to the Selected Groups list.

The following default groups are listed as well as any other groups that you have manually defined or imported from your directory server:

• All Users

• Organization Administrators

• Meeting Operators

• Meeting Organizers

• Regular Users

You can select more than one group at a time using the Crtl button on your keyboard.

Step 4 Select and configure the parameters you want to apply to the groups you have selected.

Step 5 Select Update.


7 Creating SCOPIA Desktop Profiles

• Creating or Modifying a SCOPIA Desktop Profile .......................................... page 61

• Removing a SCOPIA Desktop Profile......................................................... page 62

• Searching for a SCOPIA Desktop Profile .................................................... page 62

• Streaming Meetings Using SCOPIA Desktop ................................................ page 62

Creating or Modifying a SCOPIA Desktop Profile

Once a SCOPIA Desktop is configured, it is automatically brought online so that iVIEW Communications Manager can schedule resources.

Procedure


Step 2 Select SCOPIA Desktop.

Step 3 Select the link in the Name column for the SCOPIA Desktop you require, or select Add to create a new SCOPIA Desktop profile.

Step 4 Enter the name and IP address of the SCOPIA Desktop in the relevant fields.

Step 5 Enter the URL used by participants to join a meeting via SCOPIA Desktop in the Web Access URL field.

The URL must be in the format http://<web URL>:<port number>/scopia.

Step 6 Enter an H.323 ID used to identify connections from SCOPIA Desktop in MCU conferences in the H.323 ID field.

Ensure that the same H.323 ID is configured in the SCOPIA Desktop administrator web interface.

Configuring this field allows iVIEW Communications Manager to route calls from this SCOPIA Desktop Server based on the predefined IP topology.

Step 7 Select a topology setting from the Location drop-down list. The default value is Home.



Step 8 Enter any text you want to associate with the web access URL in the Description Text field.

The description text is embedded in email invitations sent to meeting participants.

Step 9 Enter the maximum capacity allowed by your SCOPIA Desktop license in the Maximum Capacity field.

Step 10 (Optional) Select Secure XML interface (SSL) to use the Secure Sockets Layer (SSL) protocol to secure the transport link between iVIEW Management Suite and SCOPIA Desktop.


Removing a SCOPIA Desktop Profile

Procedure



Step 3 Select the SCOPIA Desktop entry you want to delete in the Name column.


The SCOPIA Desktop profile is deleted from the scheduler and information about the SCOPIA Desktop is removed from the database.

Searching for a SCOPIA Desktop Profile

Procedure



Step 3 Enter the partial or complete name of the SCOPIA Desktop in the Name field.



Step 5 To return to the complete list of SCOPIA Desktops, clear the Name field, and then select Search.

Streaming Meetings Using SCOPIA Desktop

• Enabling Streaming on SCOPIA Desktop .................................................... page 63

• Enabling Streaming for a Virtual Room ..................................................... page 63

• Allowing Recording by Specified Roles...................................................... page 63


• Allowing Recording by Specified Users...................................................... page 64

• Enabling Recording for Specified Virtual Rooms........................................... page 64

Enabling Streaming on SCOPIA Desktop

Procedure



Step 3 Set Streaming to Visible.


Enabling Streaming for a Virtual Room

Procedure




Step 4 Set Streaming to Enabled.


Allowing Recording by Specified Roles

Procedure


Step 2 Select Default User Settings.

Step 3 Select the user types that you want to allow to record meetings from the list in the Default Recording Permissions section.



Allowing Recording by Specified Users

Procedure



Step 3 Select the link in the Name column for the user you require.


Step 5 (Optional) Select Allow user to record meetings to enable this user to record meeting regardless of the global policy.


Enabling Recording for Specified Virtual Rooms

Procedure



Step 3 Select the link in the Name column for the user you require.


Step 5 Select Record the meeting when meeting starts.

This option is available if

• Recording is allowed for the current user according to the recording policy.

• The Record Meeting field is set to Enabled under Admin > Advanced Settings > Look and Feel.

The meeting will not be recorded if there are not enough available recording ports on the SCOPIA Desktop when the meeting is scheduled.



8 Populating Corporate Address Books

The Corporate Address Book feature provide a standard corporate address book for room systems. The iVIEW Management Suite server will act as H.350 standard LDAP server so endpoints which support the H.350 protocol will be able to configure the iVIEW Management Suite server as it’s corporate address book host.

Corporate Address Books are automatically generated for Room Systems where endpoints are preconfigured in iVIEW Management Suite and allowed to be displayed in the global address book. The endpoints can be of any of the following types:

• IP H323

• IP SIP

• ISDN

• Dual

• Mobile

The following endpoints are supported to use this feature:

• Life-Size: Passport, Express, Team, Room, Conference

• Polycom: HDX Series, VSX Series

• Radvision XT1000

• Tandberg v ia TMS: All

Note: To secure the LDAP connection and avoid sending the password in clear text over the network, iVIEW Management Suite supports LDAP over TLS/SSL.

This section includes the following topics for configuring corporate address books.

• Populating Corporate Address Books........................................................ page 65

• Configuring the LDAP Service ................................................................ page 66

• Configuring the H.350 Directory Server in iVIEW ......................................... page 67


Updating the Corporate Address Book

The Room System endpoints and SCOPIA Desktop Pro clients will get updated with any change in the address book content. The following events will cause general update:

• Adding a new Room System

• Removing a Room System

• Updating a Room System

Configuring the LDAP Service

By default, the service is disabled. You must enable it before using.

Before You Begin

Log into iVIEW Management Suite Enterprise edition as an Administrator; multi-tenant users should access these settings in the Administration section.

Procedure

Step 1 Select Corporate Address Book icon in the sidebar.

Step 2 Select General Settings.

Figure 8-1 Corporate Address Book Configuration

Step 3 Select Enable Corporate Phone Book for remote systems.

Step 4 If required - insert the Listening Port: the port that the service receives the LDAP request.


Step 5 (Optional) Select the LDAP Distinguished Name (DN) Suffix.

The data input in one of the fields will be the suffix of the distinguished name of an entry supplied by the LDAP service. If the Organization Name field is filled with, for example, “Westco”, the DN suffix will be “o=westco”; if the domain name field is filled with, for example, “westco.com”, the DN suffix will be “dc=westco,dc=com”.

When configuring the search base of the LDAP configuration on the endpoints, you should append the suffix accordingly:

• If the suffix is not filled, the search base for users will be "ou=users", o=westco” if the organization name field is filled, or “ou=users,dc=westco,dc=com” if the domain name field is filled.

• The search base for terminals will be "ou=terminals" if no suffix is filled.The search base for terminals will be “ou=terminals,o=westco” if the organization name is filled, or “ou=terminals,dc=westco,dc=com” if the domain name is filled.

Step 6 (Optional) Select the Allow Anonymous Login box. If this box is checked, the end point can search the data in the LDAP service without the needs of an account.

Step 7 (Optional) Select Secure the Connection. If this box is checked, only SSL connections are allowed.

Configuring the H.350 Directory Server in iVIEW

Procedure

Step 1 On the LDAP Configuration page, select Add.

Figure 8-2

Step 2 To download terminals from a H.350 directory server, configure the server from this page. Set the search base for terminals and configure an Organizational Unit containing the terminals by H.350.


Figure 8-3 Terminal Search Base


9 Setting the H.350 in Terminals for the Global Address Book

Use the procedures below to configure the H.350 protocol for the respective terminal types.

For LifeSize terminals apply these settings (Figure 9-1 on page 70):

• LDAP Enable: This must be enabled.

• LDAP Host name: The iVIEW Management Suite address.

• LDAP Username and password: The user name must same as the entry in the Corporate Address Book of iVIEW Management Suite called “LifeSize Endpoint logon name”.

• LDAP Base: The data input in one of the fields is the suffix of the LDAP Distinguished Name of an entry supplied by the LDAP service. LifeSize searches the terminals by ou=terminals.

For example:

– If iVIEW Management Suite configured the LDAP Distinguished Name (DN) Suffix as None, in LifeSize the Base DN should be ou=terminals.

– If iVIEW Management Suite configures the LDAP Distinguished Name (DN) Suffix as mycompany for the Organization Name, in LifeSize the Base DN would be: ou=terminals,o=mycompany.

– If iVIEW Management Suite configured the LDAP Distinguished Name (DN) Suffix as: mycompany.com, in LifeSize the Base DN would be: ou=terminals,dc=radvision,dc=com.

• LDAP Filter: Set its value to (objectClass=*).


Figure 9-1 LifeSize Terminal Settings

For Polycom terminals, apply these settings (Figure 9-2 on page 71):

• Server Address: set to the iVIEW Management Suite server address.

• Server Port: It must be the same as the settings of iVIEW Management Suite. For example: 389.

• Group Name: Define a group name.

• Base DN (Distinguished Name): The data input in one of the fields is the suffix of the LDAP Distinguished Name of an entry supplied by the LDAP service. Polycom must use the ou=users because Polycom terminals access via the users to reach the endpoints.

For example:

– If iVIEW Management Suite configured the LDAP Distinguished Name (DN) Suffix as None, in Polycom the Base DN should be: ou=users.

– If iVIEW Management Suite configured the LDAP Distinguished Name (DN) Suffix as mycompany for the Organization Name, in Polycom the Base DN should be ou=users,o=mycompany.

– If iVIEW Management Suite configured the LDAP Distinguished Name (DN) Suffix as mycompany.com for the Domain Name, in Polycom the Base DN should be: ou=users,dc=mycompany,dc=com.

• Authentication Type: Define it as Basic.

• Bind DN (Distinguished Name): Set it to iVIEW Management Suite’s username.

• Change Password: set to your user’s password.


Figure 9-2 Polycom Terminal Settings

For Tandberg terminals, apply these settings (Figure 9-3 on page 72):

• IP address/DNS: Set this field to the iVIEW Management Suite’s address.

• Username: Set this field to the iVIEW Management Suite’s user.

• Password: Set to the user’s password.

• LDAP Port Number: This must be the same as the settings for iVIEW Management Suite. For example, 389.

• LDAP Base: The data input in one of the field will be the suffix of the LDAP Distinguished Name of an entry supplied by the LDAP service. Tandberg’s TMS searches terminals by ou=terminals.

For example:

– If iVIEW Management Suite configured the LDAP Distinguished Name (DN) Suffix as None, in TMS the Base DN would be ou=terminals.

– If iVIEW Management Suite configured the LDAP Distinguished Name (DN) Suffix as mycompany for the Organization Name, on the TMS side the Base DN would be ou=terminals,o=mycompany.

– If iVIEW Management Suite configured the LDAP Distinguished Name (DN) Suffix as: mycompany.com, in the TMS the Base DN would be: ou=terminals,dc=mycompany,dc=com.

• Custom LDAP Filter: Enter the value (commUniqueId=*).

• Field to use for Display Name in TMS: Enter the value cn.


Figure 9-3 Tandberg Terminal Settings


10 Viewing Network Device Performance and Availability

• Viewing Device Usage and Failure by Time Interval...................................... page 73

• Viewing Device Usage and Failure by Time Interval and Period........................ page 74

• Viewing MCU Port Availability................................................................ page 75

• Generating a Report of Network Device Performance and Availability ............... page 76

Viewing Device Usage and Failure by Time Interval

You can view historical usage and failure information for all MCUs and gatekeepers configured in iVIEW Communications Manager during a designated time period (the default time interval is one hour).

Procedure

Step 1 Select Device Monitoring in the sidebar menu.

Step 2 Select Performance Monitor.

Table 10-1 describes the information displayed on the Performance Monitor tab.


Table 10-1 Performance Monitor Tab Parameters

Viewing Device Usage and Failure by Time Interval and Period

You can view historical usage and failure information by time interval for all MCUs and gatekeepers configured in iVIEW Communications Manager during a designated time period. For example, usage per hour over a 15-day period.

Procedure


Step 2 Select Statistics.

Table 10-2 describes the information displayed on the Statistics tab.


Device Name Displays the alias name of the MCU or gatekeeper.

Model Displays the device model.

Total Meetings Displays the total number of meetings hosted on the MCU during the designated time interval. These totals only include ad hoc and scheduled meetings created via iVIEW Communications Manager.

Failed Meetings

Displays the total number of meetings that were unable to start on the MCU during the designated time interval. These totals only include ad hoc and scheduled meetings created via iVIEW Communications Manager.

% Failed Meetings

Displays the number of failed meetings divided by the total number of meetings.

Total Connections

Displays the total number endpoints involved in meetings hosted on the MCU during the designated time interval. These totals only include ad hoc and scheduled meetings created via iVIEW Communications Manager.

Failed Connections

Displays the total number of endpoints involved in meetings on the MCU that were unable to start during the designated time interval. These totals only include ad hoc and scheduled meetings created via the iVIEW Communications Manager.

% Failed Connections

Displays the number of failed connections divided by the total number of connections.


Table 10-2 Statistics Tab Parameters

Viewing MCU Port Availability

You can view MCU resource availability information during a designated time period.

Procedure


Step 2 Select Resource Availability.

Step 3 Select a meeting type and a starting date.

Step 4 Select Previous or Next to move between start times.

Step 5 Select the time interval at which you want to view resource availability information.

Information about reserved MCU ports for a designated time interval is displayed in the Reserved MCU Ports section.


Device Name Displays the name of the MCU or gatekeeper.

Model Displays the device model.

Start Time Displays the beginning of the time interval.

End Time Displays the end of the time interval.

Meetings Displays the total number of multipoint meetings hosted on the MCU during the designated time interval. Totals include only ad hoc and scheduled meetings created via iVIEW Communications Manager. Gatekeeper information is not displayed.

Peak Connections

Displays the peak number of endpoint connections for MCU or gatekeeper during the designated time interval. Figures include only ad hoc and scheduled meetings created via iVIEW Communications Manager. Gatekeeper information is not displayed.

Failed Meetings

Displays the total number of meetings unable to start on the MCU during the designated time interval. Totals include only ad hoc and scheduled meetings created via iVIEW Communications Manager. Gatekeeper information is not displayed.

Failed Connections

Displays the number of endpoints involved in meetings that were unable to connect with the MCU during the designated time interval. Totals include only ad hoc and scheduled meetings created via iVIEW Communications Manager. Gatekeeper information is not displayed.


Generating a Report of Network Device Performance and Availability

You can generate a report in .xls format, showing statistics about device usage between selected dates. Once you have saved the report, you can view it using Microsoft Excel.

Procedure


Step 2 Select Resource Availability or Statistics.

Step 3 Select the calendar icons by the From and To fields to select a start and end period within which to generate the report.

Step 4 Select Generate Report.

Information about each device is included in the report.

Step 5 Select Save to save the report.

Step 6 Browse to the location in which you want to save the file, enter the file name and type, and then select Save.


11 Viewing Real-time Meeting Statistics

• Viewing Port Utilization Information........................................................ page 77

• Viewing Organization Meetings and Calls .................................................. page 77

• Viewing the Creation Status of Meetings................................................... page 78

• Searching for a Meeting....................................................................... page 78

• Searching for a Meeting....................................................................... page 78

• Generating Reports of Upcoming Meetings ................................................ page 80

• Modifying Upcoming Meetings................................................................ page 82

• Viewing Host MCUs............................................................................. page 82

Viewing Port Utilization Information

You can view port and bandwidth utilization information for MCUs, Gateways and SCOPIA Desktops configured in the system.

Procedure

Step 1 Select Meeting Monitoring in the sidebar menu.

Step 2 Select Overall Status.

Step 3 Locate the System Utilization Status section.

Viewing Organization Meetings and Calls

Procedure


Step 2 Select Ongoing Meetings to see all meetings that are currently in progress.

Step 3 Select Ongoing Point-to-Point Calls to see all point-to-point calls that are currently in progress.

Step 4 Select Upcoming to see all meetings that have not yet started.


Viewing the Creation Status of Meetings

Procedure


Step 2 Select Ongoing Meetings to see all meetings that are currently in progress.

Step 3 Select Ongoing Point-to-Point Calls to see all point-to-point calls that are currently in progress.

Step 4 Select Upcoming to see all meetings that have not yet started.

The creation status of each of the displayed meetings is shown in the Status column.

• Green—Successful status

• Orange—Alert status

• Red—Failure status

There are three status indicators in each row.

• First (left) status icon—Indicates meeting creation status.

If meeting creation fails due to device failure, iVIEW Communications Manager attempts to recreate the meeting whenever it receives a dial-in call from a meeting participant. This allows the system multiple attempts at creating the meeting after the initial failure.

• Second (middle) status icon—Indicates participant/terminal status.

If the second status indicator is red, a participant/terminal is not connected.

If the second status indicator is orange, a participant/terminal is disconnecting from the meeting.

• Third (right) status icon—Indicates meeting termination status.

Step 5 To view the Reason Failed error message, select the red status indicator, and then select Retry to resend the meeting information to the MCU.

Note: If a terminal is disconnected correctly via the In-meeting Control interface, there is no red status indicator.

Searching for a Meeting

Procedure


Step 2 Select Ongoing Meetings, Ongoing Point-to-Point Calls or Upcoming, as required.


Step 3 Perform any of the following:

• Enter the partial or complete subject of the meeting in the Subject field.

If any part of the meeting subject matches the search string, the meeting record is displayed in the search results.

• Enter the E.164 number of an attending terminal in the E164 field.

If any part of the meeting subject matches the search string, the meeting record is displayed in the search results.

• Select the calendar icon in the From field, and select a date and time in the window that opens.

Meetings scheduled after the selected time are listed.

• Select the calendar icon in the To field, and select a date and time in the window that opens.

Meetings scheduled before the selected time are listed.

• Enter the partial or complete meeting ID in the Meeting ID field.

If any part of the meeting ID matches the search string, the meeting record is displayed in the search results.



Step 5 To return to the complete list of meetings, clear each of the fields.


Monitoring a Meeting or Call

Procedure


Step 2 Select Ongoing Meetings or Ongoing Point-to-Point Calls.

Step 3 Select the link in the Subject field for the meeting or call you want to monitor.

Step 4 Enter the moderator PIN if one is used for this meeting or call.

Step 5 Select the Become Moderator icon.

The In-meeting Control interface is not available for meetings or calls in which you are not a participant or the organizer.


Generating Reports of Upcoming Meetings

On the Upcoming tab, you can generate a report in .xls format which shows all meetings scheduled between selected dates (as specified in the To and From fields). Once you have saved a report, you can view it with Microsoft Excel.

Procedure


Step 2 Select Upcoming.

Step 3 Select the calendar icon in the From and To fields to choose a start and end date for information in the generated report.

Step 4 Select Report.

Table 11-1 describes the information categories that are included in a generated report.


Table 11-1 Generated Report Information Categories

Step 5 Select Save to save the report to a location of your choice.

Category Description

Virtual Meeting ID A meeting ID that can be dialed, used to access a specific meeting.

Master Meeting ID Corresponds to a physical meeting ID on the master MCU.

Slave Meeting ID Corresponds to a physical meeting ID on the slave MCU.

SCOPIA iVIEW Management Suite Meeting ID

Internal database ID for the meeting.

Meeting Subject/Party Name Corresponds to Subject field in Meeting Scheduling.

Meeting Description this is new

Description provided by a meeting initiator?

Location this is new Description provided by a meeting initiator?

Meeting Type Corresponds to the Meeting Type field in Meeting Scheduling. The name of the meeting type is displayed.

Reference Code Corresponds to the Reference Code field in Meeting Scheduling.

Start Time Corresponds to the Start Time field in Meeting Scheduling.

Duration Corresponds to the Duration field in the Meeting Scheduling.

Meeting Room Meeting room used for scheduling a meeting.

Organizer Name Corresponds to the Organizer field in Meeting Scheduling.

Service Prefix MCU service prefix used for the meeting.

Services MCU service used for the meeting.

MCU Name(s) MCU(s) used for the meeting. For cascaded meetings, “(master)” appears after the MCU name.

Terminals Number of terminals used for the meeting.

Number of Extra IP Ports Reserved

Corresponds to the Reserve additional ports field in Meeting Scheduling.

Dial-in IP Terminals Number of dial-in IP terminals.

Dial-out IP Terminals Number of dial-out IP terminals.

Dial-in ISDN Terminals Number of dial-in PSTN/ISDN terminals.

Dial-out ISDN Terminals Number of dial-out PSTN/ISDN terminals.

Gateway List Gateways used for the meeting.

Device Failure Cause (Device Name, IP Failure, Cause)

Any failure on a network device such as an MCU or gateway.

Attendee Failure Cause (Name, Number, ISDN, Dial-in, Total Time, Failing Attempts, Last Failure Cause)

Any failures on attending terminals.


Modifying Upcoming Meetings

You can reschedule the meeting to another time, change the meeting parameters, or delete the meeting request.

Procedure


Step 2 Select Upcoming.

Step 3 Select the subject of the meeting you want to modify.

Step 4 Enter the required information in the Meeting Detail page.

Viewing Host MCUs

Procedure


Step 2 Select Ongoing Meetings or Upcoming, as required.

All host MCUs are listed in the MCU column with an indication of whether the meeting is cascaded.


12 Creating Statistical Reports of Meetings and Calls

• Creating a Call Information Report.......................................................... page 83

• Creating a Port Usage Report ................................................................ page 84

• Creating a Resource Usage Report .......................................................... page 85

• Generating Reports for Finished Meetings ................................................. page 85

• Generating Bandwidth Utilization Reports................................................. page 87

Creating a Call Information Report

Organization Administrators can create a report for calls based on any one of these criteria:

• Multipoint calls

• Point-to-point calls

• Gateway calls

• Calls per terminal

• Calls per virtual room

Service Provider Administrators can create a report for calls based on any one of these criteria:

• Multipoint calls

• Point-to-point calls

• Gateway calls


Procedure

Step 1 Select Reports and Statistics in the sidebar menu.

Step 2 Select Create New Report.

Step 3 Select an option from the Report Type field.

Step 4 Select the time period to be covered by the report in the Graph X-Axis field.

Step 5 Select a start and end time for the report in the relevant fields.

Step 6 Select Total Number or Total Duration (Minutes) in the Graph Y-Axis field.

Step 7 Select a week range and hour range where relevant.

Step 8 (Optional) Select Recent Report to see the last call report generated.

Step 9 Select Generate.

The report appears on the in the Usage tab.

Step 10 (Optional) Select Generate PDF Report to print your report to a PDF file.

Creating a Port Usage Report

You can create a report of the ports used by these network elements:

• MCU

• Gateway

• SCOPIA Desktop

The reports provide this information:

• System utilization peaks

• Terminal utilization

• Virtual room utilization

Procedure


Step 2 Select Utilization.


Step 4 Select an option from the Report Type field.




Step 8 (Optional) Select Recent Report to see the last port utilization report generated.


The report appears on the in the Utilization tab.



Creating a Resource Usage Report

This section is for Organization Administrators only.

You can create a report of how terminals and virtual rooms are being used on your network.

Procedure




Step 4 Select Terminals Utilization or Virtual Room Utilization from the Report Type field.

Step 5 Select up to 3 terminals or virtual rooms from the pop-up list and select OK.


Step 7 Select the start and end points for the report in the relevant fields.





Step 11 (Optional) Select Generate Excel Report to print your report to an Excel file.

Generating Reports for Finished Meetings

You can generate a report in .xls format which shows all meetings scheduled between selected dates (as specified in the To and From fields). Once you have saved a report, you can view it with Microsoft Excel.

If the generated report contains more than 10,000 records including meetings and calls, iVIEW Management Suite asks whether you want the report to contain only the last 10,000 entries, or whether you prefer to abandon the current generating operation.

Procedure


Step 2 Select History.

Step 3 Select the calendar icon in the From and To fields to choose a start and end date for information in the generated report.

Step 4 Select Report.

Table 12-1 describes the information categories that are included in a generated report.


Table 12-1 Generated Report Information Categories

Step 5 Select Save to save the report to a location of your choice.

Category Description

Meeting ID/Party Number A meeting ID which can be dialed to access a specific meeting.

Master Meeting ID Corresponds to a physical meeting ID on the master MCU.

Slave Meeting ID Corresponds to a physical meeting ID on the slave MCU.

SCOPIA iVIEW Management Suite Meeting ID

Internal database ID for the meeting.

Meeting Subject/Party Name Corresponds to Subject field in Meeting Scheduling.

Meeting Description Description provided by a meeting initiator?

Location Des cription provided by a meeting initiator?

Meeting Type Corresponds to the Meeting Type field in Meeting Scheduling. The name of the meeting type is displayed.

Reference Code Corresponds to the Reference Code field in Meeting Scheduling.

Start Time Corresponds to the Start Time field in Meeting Scheduling.

Duration Corresponds to the Duration field in the Meeting Scheduling.

Meeting Room Meeting room used for scheduling a meeting.

Organizer Name Corresponds to the Organizer field in Meeting Scheduling.

Service Prefix MCU service prefix used for the meeting.

Services MCU service used for the meeting.

MCU Name(s) MCU(s) used for the meeting. For cascaded meetings, “(master)” appears after the MCU name.

Terminals Number of terminals used for the meeting.

Number of Extra IP Ports Reserved

Corresponds to the Reserve additional ports field in Meeting Scheduling.

Dial-in IP Terminals Number of dial-in IP terminals.

Dial-out IP Terminals Number of dial-out IP terminals.

Dial-in ISDN Terminals Number of dial-in PSTN/ISDN terminals.

Dial-out ISDN Terminals Number of dial-out PSTN/ISDN terminals.

Gateway List Gateways used for the meeting.

Device Failure Cause (Device Name, IP Failure, Cause)

Any failure on a network device such as an MCU or gateway.

Attendee Failure Cause (Name, Number, ISDN, Dial-in, Total Time, Failing Attempts, Last Failure Cause)

Any failures on attending terminals.


Generating Bandwidth Utilization Reports

In order to improve Administrator visibility, real time information about bandwidth usage is available by generating a Bandwidth Usage report.

The guidelines and restrictions for generating the Bandwidth Utilization report include:

• The Utilization Tab will only be displayed if there is one or more zones and at least one of them has a configured bandwidth limit.

• If there is no limit for the bandwidth, the utilization will always be set to zero.

• Once a report is created, a Summary link is available to present data in a text format.

Procedure

Step 1 Select Reports and Statistics icon in the sidebar menu.



Step 4 Select Bandwidth Utilization from the Report Type field.







Figure 12-1 Bandwidth Usage Report



13 TLS Configuration Guidelines

In order to secure SIP signaling, the iVIEW Management Suite supports Transport Layer Security (TLS) for the SIP Signaling protocol. The purpose of this section is to provide a configuration guidelines for using TLS between iVIEW Management Suite and the SCOPIA Elite MCU, iVIEW Management Suite and IBM Sametime Media Server, iVIEW Management Suite and SCOPIA Desktop Server.

• Configuring the MCU for TLS Support....................................................... page 88

• Configuring SIP Server for TLS ............................................................... page 94

• Configuring IBM SameTime Media Server for TLS ......................................... page 98

• Advanced iVIEW Configuration............................................................. page 105

• Using TLS with SCOPIA Desktop Server and iVIEW Management Suite............... page 106

• Replacing the Default Certificate with a New Self-Signed Certificate .............. page 108

• Generating a New Certificate.............................................................. page 106

• Uploading the iVIEW Certificate to SCOPIA Desktop Server........................... page 109

Configuring the MCU for TLS Support

These topics will assist you in configuring an MCU for TLS support.

• Enabling SIP Protocol in the MCU with TLS ................................................ page 89

• Uploading Certificates ........................................................................ page 90


Enabling SIP Protocol in the MCU with TLS

Before You Begin

Access the MCU administrative user interface.

Procedure

Step 1 Select Enable SIP Protocol.

Step 2 Select Specify.

Step 3 Set IP address as iVIEW server IP.

Step 4 Set Port to the same port defined in iVIEW Management Suite. The default value is 5061.

Step 5 Set Type as TLS.

Figure 13-1 Enabling the SIP Protocol on the MCU

Step 6 Restart the MCU.


Uploading Certificates

Before You Begin

Log into the MCU Management as an administrator.

Procedure

Step 1 Select Configuration.

Step 2 Select Manage in the Security section.

Figure 13-2 Security Section

Step 3 Select Create a new certificate request.

Figure 13-3 Create New Certificate Request

Step 4 Select Next.


Step 5 Enter the Organization, Organizational Unit, Email and Common name.

Figure 13-4 Organization Details

Step 6 Select Next.

Step 7 Enter the geographical information as required.

Step 8 Select Next.

The Certificate Request Summary appears.

Figure 13-5 Certificate Request Summary


Step 9 To generate a certificate request, select Next. Copy certificate request text in text area and paste it to a file. For example, mcu_ca_request.txt.

Figure 13-6 Save Certificate Request

Step 10 Submit this file to your Certification Authority (CA) by e-mail or any other method supported by your organization for your Enterprise CA.

You will receive a signed certificate from the CA, for example and the root certificate, for example ca_root.cert.

To install the signed certificate:

Step 11 Select Manage.

Step 12 Select Process the pending request and install the certificate.

Figure 13-7 Certificate Status

Step 13 Select Next.


Step 14 Open the signed certificate, and copy-paste the content of the signed certificate.

Figure 13-8 Process a Pending Request

Step 15 Select Next.

Step 16 If data is correct, select Finish and the MCU certificate is uploaded successfully. If the data is not correct, select Back to enter the correct data.

Figure 13-9 Successful Certificate Upload

Step 17 Upload the CA root certificate by selecting Upload from the Security section.


Step 18 Select Browse to select the CA root certificate.

Figure 13-10 Browse for the CA Root Certificate

Step 19 Select OK.

Step 20 Copy the certificates to the B2BUA’s CA directory, for example: mcu_ca.cert and ca_root.cert.

Configuring SIP Server for TLS

These topics will assist you in configuring the SIP Server for TLS.

• Editing the SIP Server Configuration File................................................... page 94

• Generating a B2BUA Certificate ............................................................. page 95

Editing the SIP Server Configuration File

To configure an SIP server for use with TLS, the SIP server’s configuration file needs to be edited to set the TLSEnableFIPS tag to False:

<SIPServerApp>

<TLSEnableFIPS>False</TLSEnableFIPS>

</SIPServerApp>


Generating a B2BUA Certificate

Procedure

Step 1 Navigate to Start>Programs>Radvsion iVIEW Suite> Certificates Management

Step 2 Select 3rd-Party Certificate from Type.

Figure 13-11 Certificate Management Tool


Step 3 Select Generate Certificate Signing Request (CSR) and enter details as required.

Figure 13-12 Certificate Signing Request

Step 4 Select Save to save the CSR and send it to the certificate authority.

Figure 13-13 Saving the Certificate

Step 5 Select Save Certificate. Choose an appropriate folder and file name when saving the certificate.


Step 6 Upload the CA Root Certificate by selecting the Browse button and navigating to the appropriate folder, then select Upload.

Figure 13-14 Uploading the CA Root Certificate

Step 7 Upload the CA Signed Certificate by selecting the Browse button and navigating to the appropriate folder, then select Upload.

Figure 13-15 Uploading the CA Signed Certificate

Step 8 Copy files to the SIP server. Copy the uas_key_cert.pem file from \certificatemanagement\ca. Navigate to the ca directory at \iVIEW Management Suite\icm\sipserver\ca and replace the existing file.

Step 9 Restart the SIP Server Service.


Configuring IBM SameTime Media Server for TLS

These topics will assist you in configuring an IBM ST Media Server for TLS.

• Importing a B2BUA Certificate Into the SameTime Media Server ...................... page 98

• Downloading the Certificate for IBM SameTime......................................... page 101

• Configuring the SameTime Media Server to Use TLS ................................... page 105

Importing a B2BUA Certificate Into the SameTime Media Server

Follow these procedures to import a B2BUA certificate into an IBM SameTime (ST) media server as a trust certificate:

Procedure

Step 1 Go to IBM ST media server web.

Step 2 Select Security > SSL certificate and key management.

Step 3 Select Manage endpoint security configurations.

Figure 13-16 Endpoint Security Configuration


Step 4 Open the Outbound tree, and select rvcn-7205STMSCell1(CellDefaultSSLSettings).

Figure 13-17 Outbound SSL

Step 5 Select Key stores and certificates on the right hand side.

Figure 13-18 Key Stores and Certificates


Step 6 Select CallDefaultTrustStore.

Figure 13-19 Default Trust Store

Step 7 Select the Signer certificates link on the right.

Figure 13-20 Signer Certificates


Step 8 Select the Add button to import a B2BUA certificate into the SameTime media server.

Figure 13-21 Adding the B2BUA Certificate

Step 9 Enter an Alias and File name. The file name is the local path of the SameTime media server.

Step 10 Select the Apply button.

Downloading the Certificate for IBM SameTime

Follow these procedures to import a B2BUA certificate into an IBM SameTime (ST) media server as a trust certificate:

Procedure

Step 1 Open the IBM SameTime media web server.

Step 2 Select Security > SSL certificate and key management.

Step 3 Select Manage endpoint security configurations.

Figure 13-22 Endpoint Security Configuration


Step 4 Open the Outbound tree and select rvcn-7205STMSCell1(CellDefaultSSLSettings).

Figure 13-23 Outbound SSL

Step 5 Select Key Stores and Certificates on the right hand side.

Figure 13-24 Cell Default Key Store

Step 6 Select CellDefaultKeyStore.


Step 7 Select the Personal certificates link on the right.

Figure 13-25 Personal Certificates

Step 8 Select the default check box, and then select the Extract button.

Figure 13-26 Extract Button


Step 9 Enter the pathname to the local IBM SameTime media server.

Figure 13-27 Inserting the File Name


Step 11 Copy the certificate into B2BUA CA directory.

Step 12 Back in the Personal Certificates window (Figure 13-25 on page 103) select the Signer certificates link on the right hand side.

Step 13 Select the root check box, then select the Extract button.

Figure 13-28 Root Check Box

Step 14 Enter the pathname of the local IBM SameTime media server.

Step 15 Select the Apply button.

Step 16 Copy this root certificate into B2BUA CA directory.

Step 17 Restart the IBM SameTime media service.

Step 18 Restart the B2BUA service.


Configuring the SameTime Media Server to Use TLS

Procedure

Step 1 Navigate to the Integrated Solutions Console.

Step 2 Select SameTime System Console > SameTime Servers > SameTime Media Manager.

Step 3 Select STMM.

Step 4 Ensure the Transport Protocol field is set to TLS.

Figure 13-29 TLS Protocol Settings

Step 5 To use TLS between the SameTime server and the iVIEW Management Suite, set values for these two properties in C:\Program Files\RADVISION\iVIEW Suite\iCM\jboss\bin\vcs-core.properties and restart iVIEW services:

com.radvision.tcspi.server.sip.useTls = true com.radvision.tcspi.server.sip.port=5061

Advanced iVIEW Configuration

These advanced configuration properties should be taken into consideration when configuring iVIEW Management Suite with TLS:

• vnex.vcms.core.conference.sipTransportWithMCU

For calls from an MCU if this property is TLS. If a call from the MCU is not TLS, this call will be rejected by iVIEW Management Suite.

For calls to an MCU, if this property is TLS, iVIEW Management Suite will connect MCU with TLS. If this property is TCP, iVIEW Management Suite will connect MCU with TCP. Others, iVIEW Management Suite will use UDP.

• vnex.vcms.core.conference.sipTransportWithSipServers

For call from SIP server, if this property is TLS, and the call is not TLS, this call will be rejected.


Using TLS with SCOPIA Desktop Server and iVIEW Management Suite

These topics will assist you in using TLS in deployments that include both iVIEW Management Suite and SCOPIA Desktop Server.

• Configuring SCOPIA Desktop Server to use TLS.......................................... page 106

• Configuring iVIEW to Use TLS with SCOPIA Desktop Server............................ page 106

Configuring SCOPIA Desktop Server to use TLS

Procedure

Step 1 Select Start>Programs > SCOPIA Desktop > SCOPIA Desktop Administration.

Step 2 Select Deployment.

Step 3 Select the Secure connection using TLS check box.

Figure 13-30 TLS Secure Connection

Step 4 Restart the SCOPIA Desktop Server.

Configuring iVIEW to Use TLS with SCOPIA Desktop Server

To add or modify SCOPIA Desktop Server, check Secure Connection using TLS.

Figure 13-31 Secure Check Box

Generating a New Certificate

A default certificate is predefined in iVIEW Management Suite and SCOPIA Desktop Server.

To generate a new certificate:


Procedure

Step 1 Select Start > Programs > RADVISION iVIEW Management Suite > Certificate Management.

Figure 13-32 Generating a New Certificate


Replacing the Default Certificate with a New Self-Signed Certificate

Follow these procedures to replace the default certificate with a new, self-signed certificate.

Procedure


Step 2 Input Common Name, Organization unit, Organization, City, State, Country code.

Figure 13-33 Generating a New iVIEW Management Suite Certificate

Step 3 Select Generate New iVIEW Certificate.

Step 4 (Optional) To view the certificate, select the View button.


Figure 13-34 Viewing the Certificate

Uploading the iVIEW Certificate to SCOPIA Desktop Server

When SCOPIA Desktop Server is re-installed, follow this procedure to upload the iVIEW certificate to SCOPIA Desktop Server.

Procedure

Step 1 Copy the iVIEW certificate from this iVIEW server location: C:\Program Files\RADVISION\iVIEW Management Suite\iCM\jboss\server\default\conf\ca\sds.keystore to this SCOPIA Desktop Server location C:\Program Files\RADVISION\SCOPIA Desktop\data\sds.keystore.

Step 2 Restart the SCOPIA Desktop Server by selecting Start > Programs > SCOPIA Desktop > Stop Conference Server.

Step 3 Restart the Conference Server.

Note: Always restart the SCOPIA Desktop Server after creating new certificates.


14 Configuring iVIEW Management Suite Redundancy

• About Redundancy Mode.................................................................... page 110

• Configuring Redundancy Mode ............................................................. page 110

• Viewing Redundancy Status ................................................................ page 112

• Disabling Redundancy Mode ................................................................ page 112

About Redundancy Mode

The iVIEW Management Suite redundant solution is based on two iVIEW Management Suite servers which act as a master/slave hot swap mechanism. The redundant solution supports an internal gatekeeper and an internal database.

Configuring Redundancy Mode

The iVIEW Management Suite redundant solution is based on two iVIEW Management Suite servers which act as a master/slave hot swap mechanism. The redundant solution supports an internal gatekeeper and an internal database.

Before You Begin

• For an existing redundant deployment, verify that iVIEW Management Suite is installed on an additional server.

• Verify that two Microsoft SQL databases are installed and configured to work in the Mirror failover mode.

• For a new redundant deployment, verify that iVIEW Management Suite products are installed on two separate servers.

• Decide which iVIEW Management Suite server will act as a master in the deployment.


Procedure

Step 1 On the iVIEW Management Suite server which you want to be a master select Start > Programs > iVIEW Management Suite > Redundant iVIEW Management Suite Configuration.

The redundancy tool starts.

Step 2 Select Master, and then select Next.

Step 3 In the next screen enter settings for this server and the remote server. If the MS SQL Database is used, specify the database-related settings. Select Next.

Step 4 Select Next to start the configuration. At this stage the iVIEW service is stopped.

The configuration process on this service is paused until you run the redundancy tool on the other iVIEW Management Suite server.

Step 5 On the other iVIEW Management Suite server select Start > Programs > iVIEW Management Suite > Redundant iVIEW Management Suite Configuration.


Step 6 Select Slave, and then select Next.

Step 7 Select Next to start the configuration. At this stage the iVIEW service is stopped.

The redundancy tool on the master server communicates with the redundancy tool on the slave server and configures redundancy.

When the configuration is completed successfully the success message is displayed.

Step 8 In the redundancy tool window on the master iVIEW Management Suite server, select Finish.

Step 9 In the redundancy tool window on the slave iVIEW Management Suite server, select Finish.

Note: In the case where a standalone iVIEW deployment is being converted to a redundant deployment, the recommended approach is use the old IP address of the standalone iVIEW as public IP address.

The redundant iVIEW deployment needs three IP addresses. Two are private IP address for master and slave, and the third is a public IP address. For instance, for a standalone iVIEW deployment with an IP address of 192.168.1.1, the iVIEW has run for a few days and has some data. When you want to upgrade it to a redundant deployment, you need to get two additional IP addresses, e.g. 192.168.1.2 and 192.168.1.3.

The recommended solution is to configure the old iVIEW as master, assign one new IP address to it as private IP (for example 192.168.1.2). Then, install another new iVIEW server as a slave with IP 192.168.1.3, and configure the 192.168.1.1 as a public IP. The advantage is that the IP address is not changed from the point of view of other components, which would otherwise need to be re-configured.


Viewing Redundancy Status

Once the redundancy mode is configured you can view the redundancy real-time status at any time by clicking the redundant deployment status on the toolbar .

You can view the following information:

• Virtual IP

• Probe IP

• Master Server Native IP

• Slave Server Native IP

• Last Hot Swap

• Slave Server Status

Disabling Redundancy Mode

Procedure

Step 1 On the master iVIEW Management Suite server select Start > Programs > iVIEW Management Suite > Redundant iVIEW Management Suite Configuration.


Step 2 Select Yes, and then select Next.

The configuration process starts. The system informs you when the redundancy mode has been disabled.

Step 3 Select Finish.

Step 4 Repeat this procedure on the slave iVIEW Management Suite server.


15 About the iVIEW Network Manager

The iVIEW Network Manager is a simple-to-use network management system for radvision IP video conferencing network deployments. Designed with the network administrator in mind, the iVIEW Network Manager provides a unified interface for managing all the devices (elements) in your video conferencing network, including:

• RADVISION Gateways

• RADVISION MCUs

• RADVISION Enhanced Communication Server

• RADVISION DCS

• RADVISION SCOPIA PathFinder Server

• Cisco Unified Videoconferencing MCUs

• Cisco Unified Videoconferencing Gateways

• Cisco IOS Gatekeeper

• Third-party elements and endpoints: Polycom, Tandberg, Sony, SCOPIA XT1000 and SCOPIA VC240.

The iVIEW Network Manager is a fully compliant network management system that provides network-wide functionality for RADVISION devices.

• Viewing Network Status..................................................................... page 114

• Viewing Calls and Conferences ............................................................ page 114

• Using Auto-Detect............................................................................ page 114

• Configuring Basic Elements................................................................. page 115

• Viewing Alarms and Events ................................................................. page 117

• Connecting to Element Managers.......................................................... page 117

• Connecting to Terminal Managers ......................................................... page 118

• Managing a Centralized Log ................................................................ page 118

• Viewing Multiple Networks ................................................................. page 118

• Configuring Offline Elements .............................................................. page 118

• Defining Network Subsets and Restricting Users ........................................ page 119

• Supporting ECS ............................................................................... page 119


Viewing Network Status

The iVIEW Network Manager provides network administrators with the most critical network status information at a glance, including:

• Element information—Total number of elements, the number of faulty elements and the number of elements that are offline.

• Call information—Total number of calls in the network, the number of point-to-point calls and the number of conferences.

• Endpoint information.

• Bandwidth information—Inter-zone bandwidth usage.

• B-channel usage information.

All network status information is updated in real time by the iVIEW Network Manager database.

Viewing Calls and Conferences

The iVIEW Network Manager provides network administrators with a view of all calls and conferences currently taking place over the network.

One-select control allows the network administrator to view call details or to access the source or destination gatekeeper element manager per call, and to link to the MCU Conference Control interface to assume full control of any conference in the list.

With these views, administrators can quickly determine:

• Call source and destination alias

• Call source and destination gatekeeper

• Call allocated resources

• The MCU controlling the conference

• Conference type.

• Conference video and bandwidth settings.

• Number of participants—including the current number, the number reserved and the number of local participants.

Using Auto-Detect

The iVIEW Network Manager uses an automatic detection mechanism for discovering the RADVISION elements present on the network. This information is saved to the iVIEW Network Manager database and is used to create the various network views available via the iVIEW Network Manager interface. Auto-detect can be run at regular intervals and whenever the server is restarted. Auto-detect can also be manually initiated at any time.

SCOPIA PathFinder does not yet support auto-detect.


Note: The access field definitions for SNMP communities and Telnet must correspond with the settings configured in the selected element in order to retrieve the information from the element. If these fields are not configured correctly, the required information cannot be displayed.

Configuring Basic Elements

The iVIEW Network Manager provides network administrators with the ability to view and edit the most commonly used configuration parameters of various elements in the network, such as MCUs, gatekeepers, gateways, and TANDBERG, Polycom, Sony, and Samsung SCOPIA VC240 and XT1000 endpoints.

Configuring an MCU and Updating its License Keys

Network administrators can configure the following MCU parameters, using the iVIEW Network Manager:

• The Gatekeeper’s IP address

• The SIP server working with the MCU (SCOPIA Elite MCU only)

• Updating license keys (SCOPIA Elite MCU only)

To update an MCU license key from the iVIEW Network Manager:

Procedure

Step 1 Login to the iVIEW Network Manager.

Step 2 Select the Network Tree icon on the left and explore the tree by expanding network zones to find an MCU.

Alternatively, select the Network Table icon on the left, and search the Element Type column for one of the SCOPIA Elite MCU models. Double-click on that element.

Note: Ensure it is a SCOPIA Elite MCU. The remote license update functionality is only available for the SCOPIA Elite MCU.

Step 3 Select the Licensing tab (Figure 15-1 on page 116). This tab is only visible for a SCOPIA Elite MCU.

If the license is temporary, the Remaining Days field will display the number of days before the license expires.


Figure 15-1 Remote update of the SCOPIA Elite MCU license

Step 4 Enter the new license key in the Update License Key field.

Step 5 Select the Upload button.

The system confirms the license has been updated. If there are any problems with this process, verify the license key is accurate and that the system can properly access the MCU.

Configuring a Gatekeeper

Using the iVIEW Network Manager, network administrators can configure the following Gatekeeper parameters:

• Dial plan version

• ECS ID registration and routing modes

• Dial plan version

• Strip prefixes and Strip Gateway prefixes

• Services and Hierarchy (Parent/Child/Neighbors)

• Sub-zones

• Bandwidth

• GKTMP port

• LRQ hop count

Configuring a Gateway

Using the iVIEW Network Manager, network administrators can configure the following Gateway parameters:

• Gatekeeper IP Address and Services

• Location


Configuring Endpoints

Using the iVIEW Network Manager, network administrators can configure different parameters for different type of endpoints. The three editable parameters common to all endpoints include:

• Gatekeeper IP address

• Endpoint alias name

• E.164 number

Viewing Alarms and Events

The iVIEW Network Manager provides network administrators with a list of the alarms currently active in any of the elements in the network. The list is constantly updated by the system, ensuring that any problems are located without delay. One-select access from any alarm directly to the administration interface of the device ensures that problems can be investigated and dealt with immediately.

In addition, the iVIEW Network Manager provides a list of all events that have taken place in the network. This list can be filtered by the network administrator, as required.

Connecting to Element Managers

The iVIEW Network Manager provides one-select access to the administration interfaces (element managers) of all the elements in the network, regardless of type, without the need to log in individually to each element. This gives network administrators the ability to perform a full range


of management and configuration procedures on individual elements. Links to element managers can be found throughout the iVIEW Network Manager interface, including the Alarm and Event views, the Conferences view and the various network views.

Connecting to Terminal Managers

In addition to providing one-select access to element managers, the Network Tree view of the iVIEW Network Manager also provides one-select access to the Web-based management systems of some common endpoints registered to the network.

Managing a Centralized Log

The iVIEW Network Manager provides centralized log management at both the network and element type levels. Using the Settings View, network administrators can define the size of the network log file, as well as the number of backups to maintain and the level of activity detail to include in the log. In addition, the iVIEW Network Manager can be used to keep logs for those elements types, such as MCU elements and Gateways, that do not maintain log files of their own.

Viewing Multiple Networks

The iVIEW Network Manager provides network administrators with multiple options for viewing the elements in the network, including a Network Tree view with elements arranged in a tree structure according to zone, a Network Table view that displays a single, unified list of all network elements, as well as a Network Map view that displays elements and network status information in a graphic, multi-layered format.

The Network Tree view features a default view based on the zones in the IP conferencing network. However, the iVIEW Network Manager also enables network administrators to create custom views. By creating folders and placing elements into them, administrators can view the network in whatever arrangement works best, such as dividing the network according to location. The views created in the Network Tree view can also be displayed in graphic format in the Network Map view.

Configuring Offline Elements

The iVIEW Network Manager can hold configuration details for offline elements and apply settings as each element goes online. Both added elements and existing elements can be configured to allow offline configuration.

Note: This option is not available for MCU or endpoints.


Defining Network Subsets and Restricting Users

The iVIEW Network Manager enables administrators to define subsets of the network and restrict users with specific profiles to control certain network areas. Administrators can configure the network subsets using criteria to include or exclude certain zones and element types.

Supporting ECS

The iVIEW Network Manager provides extensive monitoring, configuration and management capabilities of the ECS including local and remote zone setup, bandwidth policies, prefixes, logs, debugging and Telnet commands.


16 Viewing Your Network in iVIEW Network Manager

• How to View the Network as a Tree....................................................... page 120

• Viewing the Network as a Table ........................................................... page 122

• Viewing the Network as a Map............................................................. page 123

How to View the Network as a Tree

The Network Tree view organizes the information about the IP conferencing network into one or more tabbed views, each of which lists the elements in the network in a tree structure. By default, the tree divides the elements by zones.

• Configuring Network Hierarchy ............................................................ page 120

• Creating a Custom Network Tree View ................................................... page 121

Configuring Network Hierarchy

The drag and drop feature enables quick configuration of the network hierarchy and reconfigures element relationships by automatically assigning and updating the appropriate details of the elements with which the managed element registers.

The following element relationships can be configured using the drag and drop feature:

• Gatekeeper Parent - Child

• Gatekeeper - MCU/Gateway

• MCU - DCS

iVIEW Network Manager automatically updates element tables for Gatekeeper parent and child elements in the relationship. iVIEW Network Manager updates MCU, Gateway and elements with the appropriate gatekeeper IP address. iVIEW Network Manager updates MVP and DCS elements with the relevant IP address and configuration details for registering with the MCU.


Procedure

Step 1 Select Network Tree in the sidebar menu.

Step 2 Select an element in the network tree.

Step 3 Drag and drop the element to the required location in the hierarchy.

Step 4 Deselect the element.

Creating a Custom Network Tree View

You can create your own tree structures according to criteria you define, such as the physical location or other customer-specific criteria. You can add folders and elements to the custom views and organize them as needed.

Procedure


Step 2 Do one of the following:

• Right-click a tab in the Network Tree view (above the tree) and select Add tree view

• Select Edit > New > New tree view.

Step 3 Enter a name for the new tree view and select OK.

The new tree view is added to the Network Tree view.

By default, the new tree view includes a Network root directory and an Unassigned folder. The Unassigned folder contains all the elements in the network organized by type.

Step 4 Create folders for organizing the elements in the tree view by right-clicking the location in the tree where each folder should be located, and selecting Add folder.

Step 5 Drag and drop elements from the Unassigned folder to the folders that you created.

Note: To rename or remove tree views, either use the Edit menu or right-select the tree view. To rename or remove folders, right-select the folder and select the relevant option.


Viewing the Network as a Table

The Network Table view displays information about all the elements in the IP conferencing network in a single table and provides element editing, search and auto-detect capabilities.

Procedure

Step 1 Click Network Table in the sidebar menu.

The Network Table view includes the following information about each element:

• Element status

• Element type

• Element name

• IP address

• Version number

• Location

• Resource usage versus capacity

Step 2 Click the column headers to sort the information displayed.

Step 3 Double-select any element in the table to display the relevant element manager for that element.

There is a filter next to the Find Element icon named Show. You can further filter the same type of elements using this filter.


Viewing the Network as a Map

The Network Map view displays information about the IP conferencing network in the form of graphic maps created for each node in the network hierarchy.

Procedure

Step 1 Click Network Map in the sidebar menu.

The top level of the Network Map view displays the network root and the zones into which the network is divided.

Each square represents either the network root, a zone (or user-defined folder) or a single element. Each square includes the following information:

• Current status

• Number of calls

• Number of conferences

• Number of registered participants versus capacity

• Number of B-channels handled by gateways versus capacity

• Total bandwidth handled by gatekeepers versus capacity

Inter-zone bandwidth information appears above the zones when relevant.

Note: Call and conference statistics for OnLan Gateways and OnLan MCUs are not included in summary details for selected elements.

Step 2 Use the Up and Down buttons to navigate between map levels.

The Network Map view enables you to navigate from the zone level (or folder) to the element level by double-clicking a square.

Step 3 Use the list to select which view to display.


17 Managing Elements in iVIEW Network Manager

• Displaying General Element Information................................................. page 124

• Management Status of Elements .......................................................... page 125

• Viewing all Network Elements ............................................................. page 125

• Creating or Modifying an Element Profile ................................................ page 126

• Removing an Element Profile .............................................................. page 127

• Searching for an Element Profile .......................................................... page 128

• Defining Default Element or Endpoint Access Settings ................................ page 128

• Defining Default SCOPIA PathFinder Access Settings................................... page 129

• Overriding Default Element Access Settings............................................. page 130

• Upgrading Element Software............................................................... page 132

• Cancelling Pending Offline Configuration Settings ..................................... page 135

• Detecting New Elements on the Network Automatically .............................. page 135

• Managing the Element Software Upgrade Upload Log ................................. page 137

• Accessing an Element Web User Interface ............................................... page 139

• Accessing the Monitor Tab for a Specified Element .................................... page 139

Displaying General Element Information

The Monitor tab, which is the default tab displayed when an item is selected in the Network Tree view, displays general information about the item.

When the gatekeeper in a zone is unmanaged or inferred, the calls, bandwidth and registration information appears as zero.

The information displayed on the Monitor tab is dependent on the item selected in the tree.


Procedure


Step 2 Select the element you require in the tree.

Step 3 Select Monitor.

Step 4 (Optional) Select the link to display the element manager for the selected element.

Management Status of Elements

Table 17-1Describes the different types of element management status.

Table 17-1 Element Management Status

Viewing all Network Elements

The Elements tab displays a table of all elements related to the network, zone or folder selected in the tree.

Any element listed in the tree with a question mark (?) is considered to be an inferred element by the system. This means that the element is not listed in the database, but is presumed to exist because another known element refers to the element. Inferred elements cannot be managed, therefore we recommend that you either initiate auto-detect to discover an element, add an element manually or manually connect an inferred element.

Element Status Description

Managed The element exists in the iVIEW Network Manager database and provides monitoring information and access to configuration settings.

Inferred The element does not exist in the iVIEW Network Manager database, but it might appear as an inferred element because a managed element refers to that element.

For example, a gatekeeper is inferred when a managed element is registered to that gatekeeper zone, but the gatekeeper is not managed by the iVIEW Network Manager.

Unmanaged The element exists in the iVIEW Network Manager database but has no open communication channels with the iVIEW Network Manager and provides no monitoring information or access to configuration settings.

An element might be unmanaged when the iVIEW Network Manager license limitations have been exceeded or when the user manually sets the element as unmanaged.


Procedure


Step 2 Select Network root element.

Step 3 Select Elements.

The table in the Elements tab includes the following information about each element:

• Element status, indicated by an icon, as follows:

Online

Unmanaged

Offline

Faulty

• Element type (MCU, gatekeeper and so on)

• Element name (acts as a link to its element manager)

• IP address

• Version number

• Location (as defined on the Configure tab of each element)

• Traffic usage versus capacity

Creating or Modifying an Element Profile

Procedure

Step 1 Select one of the network views (Network Tree, Network Table or Network Map) in the sidebar menu.

Step 2 Do one of the following to modify an existing element profile:

• Right-click the element you require and select Edit element.

• Select the element you require and select Edit > Modify > Modify element.

• Select the element you require and select Edit element .

Step 3 Select the location in the network view at which you want to add the new element, and do one of the following to create a new element profile:

• Select Add > New > New element.

• Select Add element .

Step 4 Enter the element name and IP address in the relevant fields.

Step 5 Select the required element type.

The element type cannot be modified.

Step 6 (Optional) Select Managed element to enable iVIEW Network Manager to manage the element.

This option is not available for endpoint elements.


Step 7 (Optional) Select Allow offline configuration to allow offline configuration of the element.

This option is not available for MCU, SCOPIA PathFinder or endpoint elements.

The iVIEW Network Manager can hold configuration details for offline elements and apply settings as each element goes online. Both added elements and existing elements can be configured to allow offline configuration.

Step 8 (For endpoints only) Select an option from the Gatekeeper IP field.

You can select the IP address of a gatekeeper already configured in the system, or you can select No Gatekeeper or Upon endpoint configuration.

Step 9 (Optional for endpoints only) Select Set iVIEW NMS as the default trap server to use iVIEW Network Manager as the SNMP trap server for endpoint elements.


Removing an Element Profile

Deleted elements are not added to the iVIEW Network Manager database in any subsequent auto-detect operations. You can only add a deleted element manually either by using the New element option in the Edit menu, selecting the Add element button in the network views (Network Tree, Network Table or Network Map), or by connecting to a deleted element that is inferred.

Procedure


Step 2 Do one of the following to remove an existing element profile:

• Right-select the element you require and select Delete element.

• Select the element you require and select Edit > Delete > Delete element.

• Select the element you require and select Delete element .

Step 3 Select Yes.

The element profile is deleted from the scheduler and information about the element is removed from the database.


Searching for an Element Profile

Procedure


Step 2 Do one of the following to search for an element profile:

• Select Edit > Find > Find element.

• Select Find element .

Step 3 Enter the IP address of the element or select the element type.

Step 4 Select Find.

The required element is highlighted in the Network Tree, Network Table or Network Map view.

Defining Default Element or Endpoint Access Settings

Default access settings allow access to a network element (or a network endpoint) for monitoring and configuration without having to first go through the login window for that element or endpoint.

Note: You can override default access settings for a specified element at Network Tree > Access.

Procedure

Step 1 Select Settings in the sidebar menu.

Step 2 Select Element Management (for managing elements) or Endpoint Management (for managing endpoints).

Figure 17-1 Element Management


Figure 17-2 Endpoint Management

Step 3 For element management, select the Access tab.

-or-

For endpoint management select Endpoint Type.

Step 4 For element management, select an Element Type.

-or-

For endpoint management, select the Access tab.

Step 5 Define SNMP read and write communities, user name and password, HTTP communication port and Telnet password in the relevant fields.

The SNMP option is not available for endpoint or SCOPIA PathFinder Server elements.

The HTTP option is not available for endpoint elements.

SNMP community and Telnet information must match the settings defined in the selected element to enable iVIEW Network Manager to retrieve information from the element.

Step 6 Select Upload to save the information to the iVIEW Network Manager database.

Defining Default SCOPIA PathFinder Access Settings

Default access settings allow access to a SCOPIA PathFinder Server network element for monitoring and configuration without having to first go through the login window.

Procedure


Step 2 Select the required SCOPIA PathFinder Server element.

Step 3 Select Access.

Step 4 Enter a collaborator user name and password in the relevant fields.

This is the user account with which iVIEW Network Manager connects to the SCOPIA PathFinder Server. It should match the account details of a user defined on the SCOPIA PathFinder Server with the collaborator user type.

Default values are Collab and balloC respectively.


Step 5 Enter an SFTP user name and password in the relevant fields.

This is the user account with which iVIEW Network Manager connects to the SCOPIA PathFinder Server to download logs.

Default values are uadmin and admin respectively.

Step 6 Enter the SFTP port number.

The default value is 22.

Step 7 Enter an HTTP user name and password in the relevant fields.

This is the user account with which iVIEW Network Manager accesses the SCOPIA PathFinder Server web user interface.

Default values are admin and admin respectively.

Step 8 Enter the web server service port number of the SCOPIA PathFinder Server in the HTTP Port field.

The default value is 8080.

Step 9 Enter an SSH user name and password in the relevant fields.

This is the user account with which iVIEW Network Manager connects to the SCOPIA PathFinder Server platform.

Default values are admin and admin respectively.

Step 10 Select Upload to save the information to the iVIEW Network Manager database.

Overriding Default Element Access Settings

Procedure


Step 2 Select the required network element in the network tree.


Step 3 Select Access.

Figure 17-3 Element Access Tab

Step 4 Select Use default to use the default access settings for the element type.

When deselected, all other tab options are enabled.

Availability of the following access configuration parameters depends on the element type selected.

Step 5 Select a tab to display the appropriate access configuration parameters for the inferred gatekeeper.


Step 6 Select Connect to add an inferred element to the iVIEW Network Manager database.

SNMP community and Telnet information must match the settings defined in the selected element to enable iVIEW Network Manager to retrieve information from the element.

Step 7 Configure the following parameters:

• SNMP read community

• SNMP write community

• User name

• Password

• HTTP port

• Telnet password (Gateway, MCU, DCS, ECS)

• Telnet user name (ECS only)

• Enable Telnet (ECS only)

Upgrading Element Software

iVIEW Network Manager enables you to manage software upgrade files for MCUs, Gateways, and Polycom and Sony endpoints on your network.

• Adding a Software Upgrade File ........................................................... page 132

• Modifying a Software Upgrade File........................................................ page 133

• Removing a Software Upgrade File........................................................ page 134

Adding a Software Upgrade File

Procedure


Step 2 Select Endpoint Management or Element Management.

Step 3 For element management, select Software Upgrade Files. For endpoint management, select a specific endpoint type.

Figure 17-4 Element Software Upgrade


Figure 17-5 Endpoint Software Upgrade

Step 4 For element management, select the type of endpoint you require in the Show field. For endpoint management, select Software Upgrade Files.

Step 5 Select Add.

Step 6 Enter the full path of the software upgrade file to be added to the iVIEW Network Manager database, or browse to the file.

For a SCOPIA VC240 endpoint, iVIEW Network Manager starts package file validation during which the following items are validated:

• Package file format is zip.

• The upgrade-info xml file exists.

• The xml file format is correct and contains the following information: product type, version number, upgrade file list.

• The xml file contains the correct SCOPIA VC240-related information:

The product type is VC240.

The number and the name of the actual file match the xml file information.

The file name prefixes are correctness.

If the validation process fails, select another package file to upload.

Step 7 Enter a name and description for the upgrade file in the relevant fields.

Step 8 (Polycom endpoints only) Enter a related version number for the upgrade file.


Modifying a Software Upgrade File

This section applies to TANDBERG, SCOPIA VC240, Polycom and Sony endpoints only.

You can change the description of a software upgrade file that you have already added to iVIEW Network Manager.


Procedure


Step 2 For endpoint management, select Endpoint Management, or for element management, select Element Management.

Step 3 For endpoint management, select the Endpoint type from the list, or for element management, select an element from the Show list.

Step 4 Select Software Upgrade Files.


• Double-select the software upgrade file you require.

• Select the software upgrade file you require and select Edit.

• Right-select the software upgrade file you require and select Edit.

Step 6 Enter a new description for the upgrade file in the relevant fields.


Removing a Software Upgrade File

This section applies to TANDBERG, SCOPIA VC240, Polycom and Sony endpoints only.

Procedure


Step 2 Select Endpoint Management or Element Management.

Step 3 For element management, select Software Upgrade Files. For endpoint management, select a specific endpoint type.

Step 4 For element management, select the type of endpoint you require in the Show field. For endpoint management, select Software Upgrade Files.


• Select the software upgrade file you require and select Delete.

• Right-select the software upgrade file you require and select Delete.


The software upgrade file is removed from the database.


Cancelling Pending Offline Configuration Settings

Procedure


Step 2 Right-click an offline element.

Step 3 Select Clear offline updates.

The element configuration settings which existed before the offline modifications are restored.

Detecting New Elements on the Network Automatically

Auto-detect enables you to search the network for elements and add them to the iVIEW Network Manager database.

Auto-detect is performed by broadcasting requests to all SNMP communities defined in the iVIEW Network Manager for RADVISION elements. The access field definitions for SNMP communities and Telnet must correspond with the settings configured in the selected element.

Once these elements respond to the requests, the iVIEW Network Manager can query the elements directly for full configuration and status details.

The auto-detect method of discovery might not find all the elements located behind equipment such as routers. Therefore, the iVIEW Network Manager interface enables you to complete the database by adding elements manually.

Note: Elements manually deleted from the iVIEW Network Manager database are not detected in subsequent auto-detect procedures. These elements must be manually added to the iVIEWNetwork Manager database. For more information, see the “Creating or Modifying an Element Profile” section on page 17-126.

• Running the Auto-detect Mechanism Manually .......................................... page 136

• Running the Auto-detect Mechanism Automatically.................................... page 136

• Adding or Modifying Auto-detect Element Access Information ....................... page 136

• Removing an Element Type from the Auto-detect Mechanism........................ page 137


Running the Auto-detect Mechanism Manually

Procedure


Step 2 Select Tools > Auto-detect elements

Step 3 Select Yes.

The iVIEW Network Manager interface is updated accordingly.

The auto-detect procedure may take some time, depending on the size of the network.

Running the Auto-detect Mechanism Automatically

Procedure


Step 2 Select Auto-detect.

Step 3 (Optional) Select Run auto-detect on server startup to instruct iVIEW Network Manager to look for new elements on the network whenever the iVIEW Management Suite server is restarted.

Step 4 (Optional) Select Run auto-detect every (hrs) and set an hourly interval to instruct iVIEW Network Manager to look for new elements periodically.

Step 5 (Optional) Select Use default access information in auto-detect routine to instruct iVIEW Network Manager to use the default element access settings defined at Settings > Element Management > Access or Settings > Endpoint Management > Access.


Adding or Modifying Auto-detect Element Access Information

Procedure




Step 3 Do one of the following to modify existing access settings for a network element:

• Double-click the type you require in the Type column.

• Select the type you require and select Edit.

• Right-click the type you require in the Type column and select Edit.

Step 4 Do one of the following to create new access settings for a network element:

• Select Add.

• Right-click any link in the Recipient Name column and select Add.

Step 5 Select the unit type you require.

Step 6 Define an SNMP read community in the relevant field.

SNMP community information must match the settings defined in the selected element to enable iVIEW Network Manager to retrieve information from the element.

Step 7 (Optional) Define a description, SNMP write community, and user name and password in the relevant fields.

Step 8 Select Enabled to activate the new access settings.

Step 9 Select OK to save the information to the iVIEW Network Manager database.

Removing an Element Type from the Auto-detect Mechanism

Procedure




• Select the element type you require and select Delete.

• Right-select the element type you require and select Delete.


Managing the Element Software Upgrade Upload Log

• Viewing Your Software Upgrade Upload History......................................... page 138

• Uploading an Element Configuration File After a Failed Attempt.................... page 138

• Removing Entries from the Element Upload Log........................................ page 138


Viewing Your Software Upgrade Upload History

Procedure


Step 2 Select Element Management.

Step 3 Select Upload Log.

Step 4 Select the type of element you require in the Show field.

The Upload Log tab displays the history of all your attempts to upload a software upgrade file, and shows all scheduled future upload attempts.

Uploading an Element Configuration File After a Failed Attempt

Procedure





Step 5 Do one of the following to attempt to upload a software upgrade file after a previous upload attempt has failed:

• Select the log entry you require and select Retry.

• Right-click the log entry you require and select Retry.


Removing Entries from the Element Upload Log

This section applies to elements only.

Procedure






Step 5 Do one of the following to remove a single log entry:

• Select the log entry you require and select Delete.

• Right-click the log entry you require and select Delete.


Step 7 Select Delete All to remove all entries from the log.


Note: In progress entries cannot be deleted.

Accessing an Element Web User Interface

Procedure


Step 2 Right-click the element you require and select Open element manager

–or–

Select the link to the name or IP address of the element.

Accessing the Monitor Tab for a Specified Element

Procedure

Step 1 Select Network Table in the sidebar menu.

Step 2 Double-click the element you require in the table.


18 Managing a Gateway in iVIEW Network Manager

• Managing Gateway Services ................................................................ page 140

• Configuring Gateway Addressing .......................................................... page 141

Managing Gateway Services

• Viewing Gateway Supported Services..................................................... page 140

• Creating or Modifying a Gateway Service ................................................ page 140

• Removing a Gateway Service............................................................... page 141

Viewing Gateway Supported Services

Procedure


Step 2 Select the gateway you require in the tree.

Step 3 Select Services.

Note: The services tab of the P25/M Gateway is disabled.

Creating or Modifying a Gateway Service

Procedure





Step 4 Do one of the following to modify an existing service:

• Double-click the service you require.

• Select the service you require and select Edit.

• Right-click the service you require and select Edit.

Step 5 Do one of the following to create a new service:

• Select Add.

• Right-click any existing service and select Add.

Step 6 Enter the service prefix description.

Step 7 Select the call type and bit rate.

Step 8 Select OK.

Removing a Gateway Service

Procedure





• Select the service you require and select Delete.

• Right-click the service you require and select Delete.


The service is removed from the database.

Configuring Gateway Addressing

Procedure



Step 3 Select Configure.

Step 4 Enter the IP address of the gatekeeper with which the gateway registers.

Step 5 (Optional) Enter a string identifying the physical location of the gateway.


19 Managing the ECS in iVIEW Network Manager

• Managing Services............................................................................ page 142

• Configuring a Parent Gatekeeper.......................................................... page 147

• Managing Parent Filters ..................................................................... page 148

• Configuring a Child Gatekeeper ........................................................... page 149

• Managing Child Prefixes..................................................................... page 151

• Adding a Neighbor Gatekeeper ............................................................ page 151

• Managing Zones............................................................................... page 153

• Managing Bandwidth Rules ................................................................. page 154

Managing Services

The Services tab enables you to assign prefixes to local and remote ECS zones, configure the method for sending LRQ messages to each destination for address resolution and assign Gateway priorities.

• Creating or Modifying a Service............................................................ page 142

• Removing a Prefix............................................................................ page 143

Creating or Modifying a Service

Procedure


Step 2 Select the ECS you require in the tree.


Step 3 Select Services

Figure 19-1 ECS Services Settings

Step 4 Select the prefix you require and select Edit to modify an existing prefix.

Step 5 Select Add to create a new service.

Step 6 Configure prefixes with which the ECS performs address resolution, sends LRQ messages simultaneously and configures Gateway priorities per zone.

Step 7 (Optional) Select a zone, enter a prefix number and select Blast to send LRQ messages simultaneously.

Step 8 Select Upload to save your changes to the ECS database.

Removing a Prefix

Procedure



Step 3 Select Prefixes.

Step 4 Select the prefix you require and select Delete.

Step 5 Select Yes to remove the prefix from the ECS database.


Bandwidth Tab (ECS version 3.5 or later)

The Bandwidth tab enables you to define subzones and subzone rules, and to determine bandwidth policy between zones and subzones for ECS version 3.5 or later.

Figure 19-2 Network Tree—Bandwidth Tab (ECS version 3.5 or later)

The Bandwidth tab displays the following information.

Note: Details are displayed for both inter-subzone rules and for inter-zone rules.

• Name—Displays the name of the specified rule.

• Description—Displays the description of the specified rule.

• Allowed—Displays the total bandwidth (in Kbps) allowed by the specified rule.

• Used—Displays the bandwidth (in Kbps) currently used by calls governed by the specified rule.

• Available—Displays the free bandwidth (in Kbps) currently available to calls governed by the specified rule.

Note: Displays 0 when available minus used bandwidth < 0.

• Dedicated—Indicates whether or not the rule applies to a specific dedicated connection only.


Adding or Modifying Inter-subzone Rules

Procedure

Step 1 To create an inter-subzone bandwidth rule, select Add.

The Add Bandwidth Rules window appears.

-or-

To modify an existing inter-subzone rule, double-click the required inter-subzone rule, or select the required inter-subzone rule and select Edit.

The Edit Bandwidth Rules window appears.

Note: If you select the Subzone Default entry, the Edit Bandwidth Rule window displays default settings only. For more information, see XREF.

Figure 19-3 Add Bandwidth Rules Window (Inter-subzone)


Step 2 Configure the following in the Add Bandwidth Rules window:

• Name—Enter the required name of the inter-subzone rule.

• Description—Enter the required description of the inter-subzone rule.

• Connecting—Select to apply the specified inter-subzone rule to specific subzones only. Select the required subzones from the lists displayed.

• Any non-dedicated subzones—Check to apply the specified inter-subzone rule to all subzones within the zone.

• Allowed—Enter the bandwidth (in Kbps) allowed by the specified inter-subzone rule.

• Dedicated—When checked, the call is not included in the used bandwidth calculation. A dedicated rule applies to a specific dedicated connection only.

Step 3 To save the file in the iVIEW Network Manager database, select OK or to cancel the operation, select Cancel.

Viewing or Modifying the Default Inter-subzone Rule

The default inter-subzone rule applies to any intra-zone call that does not match any of the configured inter-subzone bandwidth rules.

Procedure

Step 1 Double-select the subzone default inter-subzone rule, or select the subzone default inter-subzone rule and select Edit.

The Edit Bandwidth Rules window appears showing the default settings.

Figure 19-4 Edit Bandwidth Rules Window—Default


Step 2 Configure the following in the Edit Bandwidth Rules window:

• Name—Displays the name of the default inter-subzone rule.

• Description—Displays the description of the default inter-subzone rule.

• Allowed bandwidth—Enter the bandwidth (in Kbps) allowed by the default inter-subzone rule.

• Dedicated—A default rule cannot be dedicated. Disabled for the default inter-subzone rule.

Step 3 To save the file in the iVIEW Network Manager database, select OK or to cancel the operation, select Cancel.

Configuring a Parent Gatekeeper

The ECS sends an LRQ to the parent gatekeeper when the zone prefix of the call matches one of the defined parent filters. If the ECS fails to match the zone prefix of the call with any of the defined parent filters, the ECS either rejects the call or forwards the call according to the Call Fallback settings configured in the ECS element manager. Where no filters are defined, the ECS passes the call to the parent gatekeeper. The ECS allows a maximum of ten parent filters.

• Enabling the Parent Tab..................................................................... page 147

• Adding a Parent Manually ................................................................... page 147

• Adding a Parent Automatically............................................................. page 148

Enabling the Parent Tab

The Parent tab is not available in ECS version 1.0 and INVISION ECS.

Procedure




Step 4 Select Version 2 in the Dial plan version field.

Step 5 Ensure that Use Central Database is deselected.



Adding a Parent Manually

Procedure



Step 3 Select Parent.

Step 4 Select Enabled.

Step 5 Enter the IP address, port number and description of the parent gatekeeper in the relevant fields.

Step 6 (Optional) Add a parent filter.


Adding a Parent Automatically

Procedure


Step 2 Drag and drop the ECS element into the zone of the gatekeeper you want to configure as the parent gatekeeper.

The ECS Parent tab is automatically updated with the parent gatekeeper details.

Managing Parent Filters

• Creating or Modifying a Parent Filter ..................................................... page 148

• Removing a Parent Filter.................................................................... page 148

Creating or Modifying a Parent Filter

Procedure




Step 4 Locate the Parent Filters section.

Step 5 Select the parent filter you require and select Edit to modify an existing parent filter.

Step 6 Select Add to create a new parent filter.

Step 7 Enter a name for the parent filter and select OK.

Step 8 Select Upload to save the filter to the ECS database.


Removing a Parent Filter

Procedure




Step 4 Locate the Parent Filters section.

Step 5 Select the parent filter you require and select Delete.

Step 6 Select Yes to remove the filter from the ECS database.

Configuring a Child Gatekeeper

• Enabling the Children Tab................................................................... page 149

• Viewing Child Gatekeepers ................................................................. page 149

• Adding a Child Manually..................................................................... page 150

• Adding a Child Automatically .............................................................. page 150

Enabling the Children Tab

The Parent tab is not available in ECS version 1.0 and INVISION ECS.

Procedure




Step 4 Select Version 2 in the Dial plan version field.

Step 5 Ensure that Use Central Database is deselected.



Viewing Child Gatekeepers

Procedure



Step 3 Select Children.

Table 19-1 describes the information displayed on the Children tab.

Table 19-1 Children Tab Parameters

Adding a Child Manually

Procedure




Step 4 Select Add.

Step 5 Enter the IP address, port number and description of the parent gatekeeper in the relevant fields.

Step 6 (Optional) Select Use Cisco Proxy to route calls from this zone to the neighbor gatekeeper via the Cisco Proxy.

Step 7 Add required prefixes from the list of defined child prefixes.

The ECS sends an LRQ to the child gatekeeper when the zone prefix of the call matches one of the defined child prefixes. If the ECS fails to match the zone prefix of the call with any of the defined child gatekeeper prefixes, the ECS passes the call to a neighbor gatekeeper.



Description Displays the child gatekeeper description in free text.

Prefixes Displays the zone prefix.

IP Address Displays the IP address of the child gatekeeper.

Port Displays the port number of the child gatekeeper.

Proxy Indicates whether or not the ECS routes calls from this zone to the neighbor gatekeeper through the Cisco Proxy.

Central Database Indicates whether or not the child gatekeeper was retrieved from the central database.


Adding a Child Automatically

Procedure


Step 2 Drag and drop the ECS element you want to configure as the child gatekeeper into the zone of the current ECS.

The Children tab of the parent ECS is automatically updated with the child gatekeeper details.

Managing Child Prefixes

• Creating or Modifying a Child Prefix ...................................................... page 151

• Removing a Child Prefix ..................................................................... page 151

Creating or Modifying a Child Prefix

Procedure




Step 4 Open the required child gatekeeper profile.

Step 5 Select the prefix you require and select Edit to modify an existing prefix.

Step 6 Select Add to create a new prefix.

Step 7 Enter a name for the prefix and select OK.

Step 8 Select Upload to save the prefix to the ECS database.

Removing a Child Prefix

Procedure




Step 4 Open the required child gatekeeper profile.

Step 5 Select the prefix you require and select Delete.

Step 6 Select Yes to remove the prefix from the ECS database.


Adding a Neighbor Gatekeeper

• Viewing Neighbor Gatekeepers ............................................................ page 152

• Adding or Modifying a Neighbor Gatekeeper ............................................ page 152

Viewing Neighbor Gatekeepers

Procedure

Step 1 Click Network Tree in the sidebar menu.


Step 3 Click Neighbors.

Table 19-1 describes the information displayed on the Neighbors tab.

Table 19-2 Neighbors Tab Parameters

Adding or Modifying a Neighbor Gatekeeper

Procedure



Step 3 Select Neighbors.


Description Displays the neighbor gatekeeper description in free text.

Prefix Displays the zone prefix.

IP Address Displays the IP address of the neighbor gatekeeper.

Port Displays the port number of the neighbor gatekeeper.

Proxy Indicates whether or not the ECS routes calls from this zone to the neighbor gatekeeper through the Cisco Proxy.

GK ID Displays the neighbor gatekeeper identifier.

Central Database Indicates whether or not the child gatekeeper was retrieved from the central database.

LDAP Indicates whether or not the child gatekeeper was retrieved from the LDAP server.


Step 4 Do one of the following to modify an existing neighbor gatekeeper:

• Double-click the ECS you require.

• Select the ECS you require and select Edit.

• Right-click the ECS you require and select Edit.

Step 5 Do one of the following to create a new service:

• Select Add.

• Right-click any existing ECS and select Add.

Step 6 Enter the neighbor gatekeeper zone prefix.

Step 7 Enter the description, IP address and port number of the neighbor gatekeeper in the relevant fields.

Step 8 (Optional) Select Use Cisco Proxy to route calls from this zone to the neighbor gatekeeper via the Cisco Proxy.


Managing Zones

• Creating or Modifying a Local Zone ....................................................... page 153

• Creating or Modifying a Remote Zone .................................................... page 154

• Removing a Zone ............................................................................. page 154

Creating or Modifying a Local Zone

Procedure



Step 3 Select Local Zones.

Step 4 Select the zone you require and select Edit to modify an existing local zone.

Step 5 Select Add to create a new local zone.

Step 6 Enter a zone name and the zone domain.



Creating or Modifying a Remote Zone

Procedure



Step 3 Select Remote Zones.

Step 4 Select the zone you require and select Edit to modify an existing remote zone.

Step 5 Select Add to create a new remote zone.

Step 6 Enter a zone name, zone domain, IP address and port.


Removing a Zone

Procedure



Step 3 Select Local Zones or Remote Zones.

Step 4 Select the zone you require and select Delete.

Step 5 Select Yes to remove the zone from the ECS database.

Managing Bandwidth Rules

The BW Rules tab enables you control the bandwidth of H.323 traffic both in the ECS zone and between the ECS and other zones. Bandwidth rules per session or specific zones can also be specified. A default setting specifies a bandwidth rule for all zones with which the ECS operates.

• Viewing Bandwidth Rules ................................................................... page 155

• Creating or Modifying a Bandwidth Rule.................................................. page 155

• Removing a Bandwidth Rule ................................................................ page 156


Viewing Bandwidth Rules

Procedure



Step 3 Select the Bandwidth tab.

Table 19-1 describes the information displayed on the BW Rules tab.

Table 19-3 Bandwidth Rules Tab Parameters

Creating or Modifying a Bandwidth Rule

Procedure



Step 3 Select Bandwidth tab.

Step 4 Select the rule you require and select Edit to modify an existing bandwidth rule.

Step 5 Select Add to create a new bandwidth rule.

Step 6 Select the scope of the bandwidth rule, indicate whether the rule is the default for all zones, select a zone and maximum bandwidth rate.



Name Indicates the rule name.

Description Describes the rule.

Allowed Indicates the maximum bandwidth allowed for a session in the zone.

Used Indicates the amount of bandwidth being used for a session in the zone.

Available Indicates the amount of bandwidth available for a session in the zone.

Dedicated Indicates whether or not the bandwidth is dedicated.


Removing a Bandwidth Rule

Procedure



Step 3 Select the Bandwidth tab.

Step 4 Select the bandwidth rule you require and select Delete.

Step 5 Select Yes to remove the bandwidth rule from the ECS database.


20 Managing an MCU in iVIEW Network Manager

MCU configuration and management options vary according to the MCU version you are using.

• Setting Call Routing Devices................................................................ page 157

• Viewing Registered Multipoint Processors................................................ page 158

• Modifying MCU Configuration File Information.......................................... page 158

• Backing Up MCU Configuration Settings .................................................. page 159

• Configuring MCU Location .................................................................. page 159

• Deleting a Configuration File............................................................... page 159

• Restoring MCU Configuration Settings .................................................... page 160

Setting Call Routing Devices

Procedure


Step 2 Select the MCU you require in the tree.

Step 3 Select Protocols.

Step 4 Select Use H.323 Gatekeeper or Use SIP Server to determine the MCU call routing device.

Step 5 Enter an IP address port value in the relevant fields.



Viewing Registered Multipoint Processors

The term Multipoint Processors (MPs) refers to MCUs and MVPs. This section applies to SCOPIA MCUs only.

Procedure


Step 2 Select the SCOPIA MCU you require in the tree.

Step 3 Select Registered MPs to view the list of MPs currently registered with the SCOPIA MCU.

Table 20-1 describes the information displayed on the Registered MPs tab.

Table 20-1 Registered MPs Tab Parameters

Modifying MCU Configuration File Information

This section applies to the SCOPIA Elite MCU only.

Procedure


Step 2 Select the SCOPIA Elite MCU you require in the tree.

Step 3 Select Backup & Restore.

Step 4 Select a configuration file from the list.

Step 5 Select Edit.

Step 6 Modify the name and description of the configuration file, as required.

Step 7 Select OK.


Type Displays the type of MP unit registered with the current MCU. MP unit types supported include:

MP The local MP component of the current MCU or MCU operating in MP Only mode. Performs basic media processing such as audio transcoding, video processing and video switching.

MVP Unit performing advanced media processing such as video processing and video switching.

DCS Providing T.120 data collaboration services.

Address Address of the MP unit. This may be the same as the current MCU if the MP is the media processing component of the current unit.

Description Version number and type.


Backing Up MCU Configuration Settings

Procedure




Step 4 Select Backup.

Step 5 Enter a description of the MCU configuration file in the Retrieve Configuration File window and select OK.

Step 6 Select OK in the Configuration file backup successful message window to complete the backup procedure.

Configuring MCU Location

Procedure




Step 4 Enter a string identifying the physical location of the MCU device in the Location field.

Step 5 Select Upload.

Deleting a Configuration File

Procedure





Step 5 Select Delete.

Step 6 Select OK.


Restoring MCU Configuration Settings

Procedure





Step 5 Select Restore.

Step 6 Select Yes when prompted by the “Are you sure you want to restore...?” message.


21 Managing Traps and Alarms in iVIEW Network Manager

• Sending Traps to iVIEW Network Manager................................................ page 161

• Creating or Modifying a Trap Forwarding Rule .......................................... page 162

• Disabling a Trap Forwarding Rule.......................................................... page 163

• Removing a Trap Forwarding Rule ......................................................... page 163

• Creating or Modifying an Alert Recipient Profile........................................ page 163

• Removing an Alert Recipient Profile ...................................................... page 164

• Viewing Generated Events.................................................................. page 165

• Filtering Generated Events................................................................. page 165

• Viewing Events per Network Item......................................................... page 166

• Viewing and Sorting Supported Alarms ................................................... page 166

• Modifying Alarms............................................................................. page 166

• Viewing and Sorting Generated Alarms................................................... page 167

• Viewing Generated Alarms per Network Item........................................... page 168

Sending Traps to iVIEW Network Manager

You can configure the managed elements in the network to send SNMP traps to the iVIEW Network Manager.

Procedure


Step 2 Select Traps.

Step 3 Select Receive traps from elements.



Creating or Modifying a Trap Forwarding Rule

You can instruct iVIEWNetwork Manager to forward traps received from managed elements to an address specified by a trap forwarding rule.

You can also enable SNMP version 3 support to add privacy, authentication and access control to SNMP traps before forwarding them to the trap server.

Procedure



Step 3 Do one of the following to modify an existing trap forwarding rule:

• Double-click the trap rule you require.

• Select the trap rule you require and select Edit.

• Right-click the trap rule you require and select Edit.

Step 4 Do one of the following to create a new trap forwarding rule:

• Select Add.

• Right-click any trap rule and select Add.

Step 5 Enter a description in the Description field.

Step 6 Specify the IP address and port number for iVIEWNetwork Manager to forward traps received from managed elements.

Step 7 Select Enable trap forwarding.

Step 8 (Optional) Select Enable SNMP v3 to add security attributes to SNMP traps, and select a security level.

Note: You can select this option only after selecting the Enable trap forwarding option.

• Low—No Authentication or Privacy

• Medium—Authentication without Privacy

• High—Authentication with Privacy

Step 9 (For Medium or High security only) Enter a user name and password for authentication of SNMP trap messages.

Step 10 (For Medium or High security only) Select a protocol for authentication of SNMP trap messages.

The default protocol is MD5.

Step 11 (For High security only) Enter a privacy password for encryption of SNMP trap messages.

Step 12 (For High security only) Select a privacy protocol for encryption of SNMP trap messages.

The default protocol is DES (56-bit).



Disabling a Trap Forwarding Rule

Procedure



Step 3 Do one of the following to modify an existing trap forwarding rule:

• Double-click the trap rule you require.

• Select the trap rule you require and select Edit.

• Right-click the trap rule you require and select Edit.

Step 4 Deselect Enable trap forwarding.


The trap forwarding rule is disabled but remains in the database.

Removing a Trap Forwarding Rule

Procedure




• Select the trap rule you require and select Delete.

• Right-select the trap rule you require and select Delete.


The trap forwarding rule is removed from the database.

Creating or Modifying an Alert Recipient Profile

Procedure


Step 2 Select Alert Recipients.


Step 3 Do one of the following to modify an existing alert recipient profile:

• Double-click the alert recipient you require in the Recipient Name column.

• Select the alert recipient you require and select Edit.

• Right-click the alert recipient you require in the Recipient Name column and select Edit.

Step 4 Do one of the following to create a new alert recipient profile:

• Select Add.

• Right-click any link in the Recipient Name column and select Add.

Step 5 Enter the name and email of the alert recipient in the relevant fields.

Step 6 Select a user profile.

The options in the Select user profile field reflect the user details defined at Settings > Users.

If you select a user profile with Local user access level, the alert recipient receives notifications only for alarms that belong to elements that are part of the network subset defined for the user at Settings > Users.

If you select a user profile with Administrator or Read only access level, the alert recipient receives notification of all alarms.

Step 7 Select the minimum severity level of the alerts to be sent to the alert recipient.

The severity level of alerts is defined by the profile selected in the Select user profile field.

Step 8 (Optional) Select Notify on alarms clearing to enable the alarm recipient to receive an error report via email when the alarms have been cleared.

Step 9 (Optional) Select Use custom subject line to include a custom subject line in the email and enter a string for the custom subject line.

Step 10 (Optional) Select Include element info to include details of the elements reported in the alerts in the custom subject line.

Step 11 Select Enable alert to activate the recipient.


Removing an Alert Recipient Profile

Procedure


Step 2 Select Alert Recipients.


• Select the alert recipient you require and select Delete.

• Right-select the alert recipient you require in the Recipient Name column and select Delete.


The alert recipient profile is removed from the database.


Viewing Generated Events

The Events tab enables you to sort the events reported by the system according to event severity, event time, event message and element.

Procedure

Step 1 Select Alarms in the sidebar menu.

Step 2 Select Events.

The Events tab displays the following information:

• Event severity level (Minor, Cleared, Information, Warning, Minor, Major, Critical).

• Date and time of the event.

• Text message describing the event.

Step 3 Select the column headings in the alarms table to sort the information displayed.

Step 4 Select the element in the table to display the relevant element manager for that element.

Filtering Generated Events

Procedure

Step 1 Select Alarms in the sidebar menu.



• Select View > Filter events.

• Select the Current filter link above the table.

Step 4 Define the time period and minimum severity levels of the events to display.

Step 5 Enter filter criteria and select OK.

The events that correspond to your selection are displayed in the table.


Viewing Events per Network Item

You an view a table of the events that have occurred in the system related to a specific item in your network.

Procedure


Step 2 Select Network or a relevant custom view.

Step 3 Select the network item you require.


The Events tab includes the event severity level, the date and time of the event and the event message.

Step 5 (Optional) Select the link in the Element column to display the element manager for that element.

Step 6 (Optional) Do one of the following to filter the events displayed by date and severity level:

• Select View > Filter events.

• Select the Current filter link above the table.

Viewing and Sorting Supported Alarms

Procedure


Step 2 Select Alarms.

Step 3 Select the Alarm heading in the alarms table to view alarms generated by the managed elements in the network in alphabetical order.

Step 4 Select the Severity heading in the alarms table to sort the alarms by increasing or decreasing order of severity.

Modifying Alarms

Procedure




Step 3 Do one of the following to modify an alarm generated by the managed elements in the network:

• Double-select the alarm you require.

• Select the alarm you require and select Edit.

• Right-select the alarm you require and select Edit.

Step 4 Modify the severity level, and enable or disable the alarm in the relevant fields.

Step 5 Select Create event for this alarm to instruct iVIEW Network Manager to create a report at Alarms > Events every time this alarm occurs.

Step 6 Use the Apply to all users option to indicate whether the alarm properties apply only to the current user or to all users.


Viewing and Sorting Generated Alarms

The Alarms tab enables you to view and sort the alarms generated by the elements in the network according to alarm status, alarm message, date and time or element.

Procedure

Step 1 Click Alarms in the sidebar menu.

Step 2 Click Alarms.

The Alarms tab includes the severity of each alarm, the time the event occurred and the alarm message that is related to the selected element. Alarm severity levels include the following:

Major/Minor/Critical

Information

Warning

Step 3 Double-select any element in the table to display the relevant element manager for that element.


Viewing Generated Alarms per Network Item

You can view a table of all current alarms related to a specific item in your network. Alarms can be viewed per element, network zone or the entire network in one view.

Procedure


Step 2 Select Network or a relevant custom view.

Step 3 Select the network item you require.


The Alarms tab includes the severity of each alarm, the time the event occurred and the alarm message that is related to the selected element. Alarm severity levels include the following:

Major/Minor/Critical

Information

Warning


www.radvision.com

About RADVISIONRADVISION (NASDAQ: RVSN) is the industry’s leading provider of market-proven products and technologies for unified visual communications over IP and 3G networks. With its complete set of standards based video networking infrastructure and developer toolkits for voice, video, data and wireless communications, RADVISION is driving the unified communications evolution by combining the power of video, voice, data and wireless – for high definition video conferencing systems, innovative converged mobile services, and highly scalable video-enabled desktop platforms on IP, 3G and emerging next generation networks. For more information about RADVISION, visit www.radvision.com

This document is not part of a contract of license as may be expressly agreed RADVISION is registered trademarks of RADVISION, Ltd. All trademarks recognized. All rights reserved © 2010 RADVISION, Ltd.

USA/AmericasT +1 201 689 6300F +1 201 689 [email protected]

EMEAT +44 20 3178 8685F +44 20 3178 [email protected]

APACT +852 3472 4388F +852 2801 [email protected]

http://www.radvision.com

Date post:	21-May-2020
Category:	Documents
Upload:	others
View:	13 times
Download:	0 times

SCOPIA iVIEW Management Suite - Logitel€¦ · RADVISION | Administration Guide for SCOPIA iVIEW...

Documents