Administrator Guide for SCOPIA Desktop Server Version 772

Administrator GuideVersion 7.7for Solutions 7.7, 8.0

SCOPIA Desktop Server

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

All product and company names herein may be trademarks of their registered owners.

This publication is RADVISION confidential. No part of this publication may be reproduced in any form whatsoever orused 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 ismade either by RADVISION Ltd or its agents.

RADVISION Ltd reserves the right to revise this publication and make changes without obligation to notify any personof such revisions or changes. RADVISION Ltd may make improvements or changes in the product(s) and/or theprogram(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 agreementincluded with the product as a separate document. If you are unable to locate a copy, please contact RADVISION Ltdand a copy will be provided to you.

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

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

Administrator Guide for SCOPIA Desktop Server Version 7.7, December 2, 2012

http://www.radvision.com

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7

1 About SCOPIA Desktop Server

About SCOPIA Desktop Client.......................................................................... 2

Components of the SCOPIA Desktop Server.......................................................... 3

2 Configuring SCOPIA Desktop Client

Defining Client Video Quality and Connection Parameters.........................................5

Defining Meeting Features..............................................................................8

3 Rolling-Out SCOPIA Desktop to End Users

Adding and Modifying SCOPIA Desktop in SCOPIA Management.................................. 11

Verifying SCOPIA Desktop Client Requirements.................................................... 14

Installing SCOPIA Desktop Client..................................................................... 15

Testing Desktop Connectivity.........................................................................17

Sending Meeting Invitations to End Users........................................................... 18

Sending Administrator Messages to End Users...................................................... 20

Configuring Dial String Rules..........................................................................21

Planning Rules to Modify Dial Strings...........................................................21

Adding or Editing a Dial String Rule............................................................ 24

Deleting a Dial String Rule.......................................................................27

Table of Contents

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7 Table of Contents | i

4 Maintaining the SCOPIA Desktop Deployment

Upgrading the SCOPIA Desktop Server License..................................................... 29

Backing Up Configuration Settings................................................................... 30

Restoring Configuration Settings..................................................................... 31

Enabling Integrated Windows Authentication...................................................... 31

Enabling Microsoft Internet Explorer for Integrated Windows Authentication................. 32

Integrating SCOPIA Desktop with Sametime........................................................ 34

Working with the Content Slider..................................................................... 34

Accessing Log Files..................................................................................... 36

5 Configuring SCOPIA Desktop to Manage Recording Features

Adding a Recording Server............................................................................ 37

Calculating Space Needed for Recording............................................................38

Defining SCOPIA Desktop Recording Settings....................................................... 39

6 Managing Recordings

Viewing Recording Information.......................................................................42

Editing Recording Attributes.......................................................................... 45

Managing Categories................................................................................... 46

Creating Categories for Multiple Recordings........................................................47

Selecting Recording Owners.......................................................................... 48

Recording Meetings.................................................................................... 49

Stopping a Recording in Progress.....................................................................51

Deleting a Recording...................................................................................51

7 Configuring SCOPIA Desktop Server to Manage Streaming Features

Defining the Streaming Server Settings..............................................................54

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7 Table of Contents | ii

8 Customizing the SCOPIA Desktop User Interface

Replacing Images....................................................................................... 57

Modifying Strings....................................................................................... 58

Saving or Restoring Branding- Related Changes.................................................... 59

Restoring Default Images and Strings................................................................ 60

9 Configuring Multiple SCOPIA Desktop Servers

Configuring SCOPIA Desktop Servers for Load Balancing.......................................... 62

Implementing Scalability with the Radware AppDirector......................................... 63

Implementing Scalability with a Third-party Load Balancer...................................... 65

Configuring Multiple SCOPIA Desktop Servers as Tomcat Clusters............................... 67

Configuring Server Redirection....................................................................... 69

Configuring Streaming and Recording for Scalability.............................................. 70

10 Securing Your SCOPIA Desktop Deployment

Securing Web Connections and Media Traffic to SCOPIA Desktop Server....................... 72

Securing SCOPIA Desktop Server’s Connection to other Components........................... 74

11 Troubleshooting Common Issues

Preserving SCOPIA Desktop Presence Server Configuration.......................................76

Viewing Status of Servers and Directory.............................................................77

Viewing Server Status and Port Resource Usage.............................................. 77

Viewing Directory Status.........................................................................80

Viewing Recording Server Status............................................................... 82

Viewing Content Slider Status...................................................................83

Recording Does not Start Automatically.............................................................84

Synchronizing SCOPIA Desktop Server with SCOPIA Management................................ 84

Updating the IP Address on the Recording or Streaming Server..................................85

Changing the IP Address of the SCOPIA Desktop Server........................................... 85

Client -734 Error and other Certificate Problems.................................................. 86

Upgrading SCOPIA Desktop Server Recordings...................................................... 87

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7 Table of Contents | iii

Enabling a User to Sign In............................................................................. 87

Troubleshooting SCOPIA Mobile...................................................................... 88

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7 Table of Contents | iv

The SCOPIA Desktop Server brings together meetings with SCOPIA Desktop Clients and SCOPIAMobile devices, passing their media connections to the SCOPIA Elite MCU.

SCOPIA Desktop Server is easy to use and includes built-in presence, invitation and firewalltraversal features to ensure call connectivity and quality videoconferencing. Additionally,SCOPIA Desktop Server supports advanced videoconferencing features such as ContinuousPresence video, H.239 data collaboration, PIN protected meetings, conference moderation,full authentication and authorization, and SIP point-to-point communication between SCOPIADesktop Clients.

SCOPIA Desktop offers the following additional features:

• Streaming and recording

You can enhance SCOPIA Desktop Server by deploying additional components forstreaming, recording, and presence features.

• Chat messages to meeting participants

The user can now send public or private chat messages to meeting participants, includingroom systems, via SCOPIA Desktop.

• Service provider (multi-tenant) support

SCOPIA Management, SCOPIA Desktop, and SCOPIA Desktop Pro support service providerdeployments that include multiple organizations (tenants). In a multi-tenant deployment,each SCOPIA Desktop meeting is associated with only one tenant. Multi-tenant featuresinclude:

– All SCOPIA Desktop Clients only see contacts (users or endpoints) belonging to theirown organization.

– When browsing or searching a recording, SCOPIA Desktop Clients only see recordingsbelonging to their own organization.

• Microsoft Lync support

If you have a SCOPIA Video Gateway in your deployment, SCOPIA Desktop Pro Clients areable to call Microsoft Lync users from the contact list, and invite them to a meeting.

• Internet Explorer 9.0 support

SCOPIA Desktop is now compatible with Internet Explorer 9.0, thus answering therequirements of Windows Vista and Windows 7 users.

1 About SCOPIA Desktop Server

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7 About SCOPIA Desktop Server | 1

• Scalability with an external load balancer

SCOPIA Desktop works with an external load balancer providing unlimited scalability anduncompromised redundancy for large deployments.

• About SCOPIA Desktop Client ............................................................... page 2

• Components of the SCOPIA Desktop Server ............................................... page 3

About SCOPIA Desktop Client

The SCOPIA Desktop Client is a simple web browser plug-in for interactive videoconferencingusing high definition or standard definition with superb quality. It is part of SCOPIA Desktop,the desktop videoconferencing solution which provides the client/server application thatextends videoconferencing to remote and desktop users for voice, video and datacommunications.

Clients can be centrally managed and deployed without complex licensing fees or installationissues. Users receive a web link in their invitation to join a videoconference, and in momentsthey are connected and participating. The standard SCOPIA Desktop Client includes the mainvideoconference client with a built-in chat window and presentation viewing abilities (Figure1-1 on page 2).

Figure 1-1 The SCOPIA Desktop Client user interface

SCOPIA Desktop Pro extends the functionality of SCOPIA Desktop Clients by providing userswith their own login, enabling each user to have their own virtual room to invite people tomeetings, point-to-point calling. It also includes a list of contacts with a corporate directoryof users, and indication of their availability for videoconferencing. An SCOPIA Add-in forMicrosoft Outlook enables easy scheduling of meetings, so you can chat one-to-one or withmultiple participants anywhere.


Components of the SCOPIA Desktop Server

Depending on the features you require, SCOPIA Desktop may include a variety of differentservers, each of which fulfills its own function (Figure 1-2 on page 3).

Figure 1-2 Components of the SCOPIA Desktop Server

• SCOPIA Desktop Conference Server

This is the main gateway responsible for creating conferences with SCOPIA DesktopClients, and connects to the MCU to enable transparent connectivity with H.323endpoints.

• SCOPIA Desktop Streaming Server

Responsible for streaming webcasts. This server functionality is available for alldeployment types, and in SCOPIA Desktop this service is offered by a server known asDarwin.

• Tomcat Application Server

The underlying web server and application server is implemented by Tomcat in SCOPIADesktop deployments. It also provides the following functionality:

– Automatic downloads and updates of the SCOPIA Desktop Client

– The SCOPIA Desktop Recording Server

– The SCOPIA Desktop portal web page from which users can sign in and launch theSCOPIA Desktop Client.

– User authentication

• SCOPIA Desktop Recording Server

Part of the Tomcat Application Server, this service is responsible for recording meetings,storing recordings and providing HTTP access to the recordings.


This server functionality is available for all deployment types except point-to-pointdeployments.

It is also responsible for the SCOPIA Desktop Content Slider content.

• SCOPIA Desktop Presence (XMPP) Server

Maintains a live list of contacts which are available or unavailable for video chat orvideoconference. This information is presented in the Contact List of SCOPIA Desktop Pro.In SCOPIA Desktop deployments, this is implemented with Jabber. The XMPP server is alsoresponsible for user authentication, and it is used for attendee registration andinvitations.

The presence server must be configured separately after the initial SCOPIA Desktopinstallation. This server functionality is only available for point-to-point and advanceddeployments.

• STUN Server

Enables you to directly dial a SCOPIA Desktop Client or Server behind a NAT or firewall inpoint-to-point implementations by giving that computer’s public internet address. Third-party STUN Servers are supported.

Deployments where a STUN Server is used has these restrictions:

– You cannot use a NAT address on the STUN Server and expose it via a static ordynamic public IP address. Instead you must configure the STUN Server with a publicIP address.

– You must place the STUN Server at a location which is accessible by both SCOPIADesktop Clients participating in a call.

– SCOPIA Desktop Clients can use different STUN Servers provided that the STUN Serversare situated on the Internet outside the Clients’ NAT.


You configure SCOPIA Desktop Clients in order to define the parameters related to the videoquality, connection addresses, and meeting functionality. SCOPIA Mobile is also considered asSCOPIA Desktop Client for configuration purposes.

Perform these procedures:

• Defining Client Video Quality and Connection Parameters ............................. page 5

• Defining Meeting Features .................................................................. page 8

Defining Client Video Quality and Connection Parameters

During this procedure you define the maximum bandwidth used between the SCOPIA DesktopClient and the SCOPIA Desktop Server. The video quality options include:

• Standard Definition

This option limits the client to standard definition video connection at the maximum callrate you specify. If you define a service on the MCU that enables H.323 endpoints to use ahigher bandwidth rate or high definition without enabling high definition on SCOPIADesktop, calls using this service are transcoded down to the lower rate at standarddefinition (CIF resolution). If you select a MCU service with a bandwidth rate lower thanthe value set in the Maximum Call Rate list, then the latter is used for the standarddefinition call to the SCOPIA Desktop client. The default value is 384K.

• High Definition

This option allows SCOPIA Desktop Clients to connect to a conference in high definitionmode. If you select this option, select a maximum call rate of at least 1024 Kbps orgreater to enable the conference to continue in 720p high definition video resolution forall clients. For deployments using SCOPIA MCU, you may want to allow SCOPIA Desktop toreduce the video resolution from 720p to 480p if you set the call rate to 1024 Kbps andthere is a bandwidth congestion during a conference.

The SCOPIA Desktop Client sends up to 512 Kbps of 480p video resolution and receives themaximum call rate or rate of the service selected (the lower value of the two) of 720pvideo resolution. If you select a lower maximum call rate, you force the high definitionservice to send 480p to all clients at the lower bandwidth.

2 Configuring SCOPIA Desktop Client

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7 Configuring SCOPIA Desktop Client | 5

When SCOPIA Desktop is set to high definition mode and connected to a high definitionservice in deployments using SCOPIA Elite MCU. SCOPIA Desktop limits fast updaterequests to avoid degradation of video quality or frame rate to all the connectedendpoints.

If SCOPIA Desktop connects to a standard definition service, or if there are no highdefinition ports available for the high definition service, the standard definition maximumcall rate is used during a SCOPIA Desktop conference.

Procedure

Step 1 Navigate to the SCOPIA Desktop Server Administration web interface.

Step 2 Select the Client icon in the sidebar.

Step 3 Select the Settings tab.

Step 4 Select the maximum call rate in the Maximum Video Quality section.

Step 5 To configure settings for standard definition, select a bandwidth rate from the Maximum CallRate list. To configure settings for high definition:

Figure 2-1 Maximum Call Rate Section

a. Select the High Definition check box.

b. Select a bandwidth rate from the Maximum Call Rate list.

c. If necessary, select the Allow SCOPIA MCU version 5.x to negotiate high definition callsdown to 480p check box.

Step 6 Enter a value in the MTU Size field if your network routers and the MCU are configured toaccept network packets of a different size. The default value is 1360.


Figure 2-2 Setting the MTU size for SCOPIA Desktop Client

Note This value must remain the same across all network components to guard against

packet fragmentation.

Step 7 Configure a more limited port range opened on the firewall by entering values for the lowest

multimedia port and the highest multimedia port.

Figure 2-3 Limiting the port range used by SCOPIA Desktop media

Use these fields if you need to limit UDP ports that are opened on the firewall to allowSCOPIA Desktop Clients to send RTP to SCOPIA Desktop. We recommend that you use alimited range between 2326 and 65535. If this option is used, each client connection useseleven ports; to define the range, multiply the number of connections allowed by yourlicense by eleven.

For the full range of ports required by the SCOPIA Desktop Server and SCOPIA Desktop Client,see the Installation Guide for SCOPIA Desktop.

Step 8 Insert the public address of the SCOPIA Desktop Server to be accessed by the client. Use aFQDN which the SCOPIA Desktop Clients can resolve from their location, to arrive at thecorrect IP address of the server.

In deployments using SCOPIA Management, if clients cannot send messages to the PresenceServer directly because no ports are open, the SCOPIA Desktop Server tunnels the XMPPmessages using this public address.

Figure 2-4 The address for the SCOPIA Desktop Client to connect to theserver


If the Streaming Server resides behind a NAT, the clients might not resolve the StreamingServer IP address. In this case the clients use this SCOPIA Desktop Server public address toconnect to the Streaming Server.

Step 9 Enter a value in the Call Limit field to limit the resources used by the system. Use this whenthe computer on which the SCOPIA Desktop Server is installed is not powerful enough tosupport two hundred calls.

Figure 2-5 Call Limit Section

Step 10 Select OK or Apply.

Defining Meeting Features

This section describes how to enable various in-meeting features, including desktop sharing,additional conference panes, and whether or not the mic is enabled by default when joining ameeting.

Procedure

Step 1 Navigate to the SCOPIA Desktop Server Administration web user interface.

Step 2 Select the Client icon in the sidebar.

Step 3 Select the Meeting Features tab.

Step 4 Select Enable Desktop Sharing in the Meeting Room section to allow participants to sharetheir PC desktop content with others in the videoconference.

If desktop sharing disabled, the Present button does not appear in the meeting window.


Figure 2-6 Meeting Room Settings

Step 5 Select Enable Content Slider feature in SCOPIA Desktop meetings to enable participants toreview content which has already been shared in the meeting by scrolling back and forth.

Select Allow only moderators to share applications from their desktop to restrict thisfeature only to moderators of videoconferences.

Step 6 Select Enable Chat to display the chat window pane in the videoconference window.

For deployments with multiple SCOPIA Desktop Servers, it is recommended that you do notenable the Chat option. A participant using one SCOPIA Desktop Server cannot join the chatstarted by a participant using another SCOPIA Desktop Server.

Step 7 Select Enable Raise Hand feature in SCOPIA Desktop meetings to allow a muted user torequest permission to speak.

Step 8 Select Display an additional panel in the conference room to add your own custom contentfrom another web location to be displayed directly in the meeting room.

Step 9 Define the additional custom panel option as desired:

a. Select the Display an additional panel in the conference room check box to enable theoption.

b. Enter the URL in the field.

The system automatically appends two parameters to the external URL: the ongoingmeeting ID and the participant's nickname, so your external web content can relate tothe meeting and participant if required. The parameters addedare: ?meetingid=NNN&nickname=XXX. If your external web content already takesdifferent parameters in its URL, these parameters are appended to the URL string.

Use standard URL-encoding in this field, for example '&' is %26, '=' is %3D and so on.

Step 10 Configure the Push to Talk section to define how participants use the microphone button inthe SCOPIA Desktop Live Meeting Console:

• Allow users to join a meeting with their microphone on enables the microphone bydefault, so participants must select the microphone button to mute themselves.

• Force users to join a meeting with their microphone off disables the microphone bydefault, so participants must select the microphone button to unmute themselves. This isoften helpful to eliminate background noise from a videoconference until the participantis ready to contribute.


• Force users to hold down their microphone button while speaking requiresparticipants to select and hold down the microphone button to activate theirmicrophones and send their audio.

Figure 2-7 Push to Talk Settings

Step 11 Select Encrypt Media in the Security section to secure the audio, video and presentationusing sRTP between the SCOPIA Desktop Server and SCOPIA Desktop Client.

Note Using encryption is subject to local regulation. In some countries it is restricted or

limited for usage. Consult your local reseller for further details.

This does not encrypt the web portal, only the media content of a video call.

Figure 2-8 Security Settings

Step 12 Select Allow Users to have SCOPIA Desktop call them back for users who have an H.323endpoint but also want to connect a dedicated PC to share presentations.

On the SCOPIA Desktop portal page, before connecting to a meeting, participants can selectMore Options > Use my computer for presentation only > Callback my video devicenumber for the server to call back the H.323 device when the users connect, so they canautomatically connect their H.323 devices at the same time.

Note When a computer connects as a dedicated data-only device, it cannot view or send

video or audio, but it can display the participant list, and you can moderate, chat,and show or view presentations from the computer.



This section provides the recommended procedures for rolling-out your deployment to endusers.

• The Contact List is configured, on installation, with organization-specific URL.

• The Contact List supports Lync users who have the Lync icon next to their names todifferentiate them among the Contacts.

• Point-to-point calls escalated to multi-point calls are associated with the user making thecall.

• URLs in the invitation sent from the SCOPIA Add-in for Microsoft Outlook are organization-specific. This feature is displayed when the SCOPIA Desktop is part of a multi-tenantdeployment.

• Users can send meeting invitations to Lync Clients.

The section includes these topics:

• Adding and Modifying SCOPIA Desktop in SCOPIA Management ....................... page 11

• Verifying SCOPIA Desktop Client Requirements ........................................ page 14

• Installing SCOPIA Desktop Client ......................................................... page 15

• Testing Desktop Connectivity ............................................................. page 17

• Sending Meeting Invitations to End Users ............................................... page 18

• Sending Administrator Messages to End Users .......................................... page 20

• Configuring Dial String Rules .............................................................. page 21

Adding and Modifying SCOPIA Desktop in SCOPIA Management

SCOPIA Desktop profiles are manually added to the SCOPIA Management. Once a SCOPIADesktop server is configured, it is automatically brought online. SCOPIA Management canrecord meetings using SCOPIA Desktop's recording server, and SCOPIA Desktop can retrieveinformation from SCOPIA Management, including:

• SCOPIA Management's user directory

3 Rolling-Out SCOPIA Desktop to End Users

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7 Rolling-Out SCOPIA Desktop to End Users | 11

• Information about current and scheduled meetings, such as meeting participants

When configuring the SCOPIA Desktop server IP address in SCOPIA Management, the SCOPIAManagement IP address must also be configured in the SCOPIA Desktop server to allowconnection and communication between them. .

Procedure

Step 1 Access the SCOPIA Management administrator portal.

Step 2 In the Devices tab, select Desktop Servers.

Step 3 Select the link in the Name column for the SCOPIA Desktop Server you require, or select Addto create a new SCOPIA Desktop Server profile. The Add SCOPIA Desktop Server pageappears (Figure 3-1 on page 12).

Figure 3-1 Adding a SCOPIA Desktop profile

Step 4 Enter the required information (Table 3-1 on page 13).


Table 3-1 Configuring SCOPIA Desktop Server

Field Name Description

Name Enter a name to identify this SCOPIA Desktop Server. Thisname is displayed in the list of SCOPIA Desktop Servers.

IP address Enter the management IP address of SCOPIA DesktopServer.

URL Enter the URL used to access the SCOPIA Desktop Server.The URL must be in the format http://<web URL>:<portnumber>/scopia.

H.323 ID Enter the H.323 ID used to identify connections fromSCOPIA Desktop Server in MCU conferences.

This must match the H.323 ID that is configured in theSCOPIA Desktop administrator web interface.

Configuring this field allows SCOPIA Management to routecalls from this SCOPIA Desktop Server based on thepredefined IP topology.

Location This is only relevant for service providers or deploymentswith multiple locations.

Select the SCOPIA Desktop Server's location.

Invitation You can modify the text that is displayed in emailinvitations sent to meeting participants. You can insertplaceholders for the following links, which are generatedby SCOPIA Management for each meeting:

• Direct Access URL: Link for participants toautomatically join the meeting.

• Access URL: Link for participants to watch themeeting's webcast or recording.

• Installer URL: Link for participants to install theSCOPIA Desktop Client.

Maximum Capacity Enter the maximum number of ports allowed by yourSCOPIA Desktop license in the Maximum Capacity field.

Secure the connectionbetween this server andSCOPIA Management

To use the Transport Layer Security (TLS) protocol tosecure the transport link between SCOPIA Management andSCOPIA Desktop, select this checkbox. For moreinformation, see Securing Your Video Network Using TLS.

This SCOPIA Desktop Serverhas a recording server

Select this checkbox to configure this SCOPIA DesktopServer with a recording server.

Step 5 Select OK to save your changes.


Verifying SCOPIA Desktop Client Requirements

This section details the software and hardware requirements of the SCOPIA Desktop Client.

Note The system undergoes thorough testing using the latest browser versions available at the time

of release.

The minimum software requirements of the SCOPIA Desktop Client are:

• Operating systems:

Note We recommend using the latest service pack of the Windows operating systems

listed in this section

– Windows XP (SP2 and higher, 32 and 64-bit)

– Windows Vista (SP2 or higher, 32 and 64-bit)

– Windows 7 (32 and 64-bit).

– Macintosh OS X version 10.5 (Leopard) or higher, Intel CPU only

• Web browsers (for the web interface)

– Internet Explorer 6, 7, 8 and 9 (Windows)

– Firefox 3.5 or later (Mac and Windows)

– Safari 4 or later (Mac and Windows)

– Google Chrome 5.0 or later (Mac and Windows)

• Viewing live webcasts or recorded meetings

– Mac: QuickTime 7.4.5 or later (version 10 recommended)

– PC: QuickTime 7.4.5 minimum (version 7.7 recommended)

Note Internet Explorer must be installed on your Windows PC when using the SCOPIA Desktop

Client, even if you choose to access the meeting with an alternate web browser like Firefox,Safari or Chrome.

The minimum hardware requirements for the SCOPIA Desktop Client depend on the videoresolution.

• Standard definition hardware specification:

– PC Intel Pentium 4, 3.0 GHz or faster

– PC AMD Athlon 3.0 GHz or faster

– PC Intel Centrino Mobile Processor 1.8 GHz or faster

– Mac with Intel Core Duo 1.8 GHz or faster

– Netbook Intel Atom Processor 1.6 GHz or faster

– 1 GB of RAM or more


• Enhanced definition hardware specification:

– PC Intel true dual core processors - Core 2 Duo 1.8 GHz or faster

– PC AMD true dual core processors - e.g. Phenom IIx4 91- 2.X GHz or faster

– Minimum 2 GB of RAM

• High definition hardware specification:

– PC Intel quad core or better processors

– PC Intel Core i5 or i7 are recommended for an ultimate experience

– PC AMD Quad-Core Opteron

– Mac with Intel Core 2 Duo 2.7 GHz or faster

– Minimum 2 GB of RAM, 3 GB of RAM or more recommended

Installing SCOPIA Desktop Client

The SCOPIA Desktop Client installation portal provides an automatic download and updatemanager. When you select the Updates link, the Updates Manager allows you to view anycurrently installed components and versions, and to install optional components, including theOutlook Add-On and the Contact List.

Note You must be logged in to the portal to install all components at once. If you are not logged in,

you can only install the client, not the Contact List or the Outlook plugin. These componentsare reserved for users who are authenticated to access corporate systems for scheduling andmaking calls.

In a multi-tenant deployment the Contact List and the Outlook Add-On are configured oninstallation with organization-specific URLs.

Before you begin

• Obtain login credentials. You may need to ask your SCOPIA Desktop administrator for auser name and password if SCOPIA Desktop is configured so that only authenticated userscan participate in meetings, access webcasts, or watch recordings.

• Connect a headset or speaker and microphone to your computer, and ensure it isconfigured in the control panel or system settings.

• Connect a video camera or webcam to your computer.

Procedure

Step 1 To activate SCOPIA Desktop for the first time, go to the SCOPIA Desktop portal page at:

• http://sd.company.com/scopia for a single tenant deployment

• http://sd.company.com/<tenant> or http://sd.company.com/scopia/mt/<tenant> for amulti-tenant deployment


Step 2 Select Updates.

Figure 3-2 Locating the Client Download and Update Link

Step 3 Select the check box next to any optional components to install or update.

Figure 3-3 Updating SCOPIA Desktop Client

Step 4 Select Install. When the SCOPIA Desktop Client installation is complete, you should see thefollowing icon in the task tray at the lower right corner of the screen:

Step 5 To verify that any optional components were installed, select the View Installed Updateslink. A list of installed components appears.


Figure 3-4 Installed Updates and Components

Testing Desktop Connectivity

As best practice, after configuring your SCOPIA Desktop deployment, you should install aSCOPIA Desktop Client on a local computer and attempt to enter a meeting room to verifyconnectivity.

In a multi-tenant deployment the Contact List and the SCOPIA Add-in for Microsoft Outlook areconfigured with organization-specific URLs.

This section describes how to check whether or not a client is connected to SCOPIA DesktopServer.

Procedure

Step 1 Verify that your video and audio peripheral equipment is connected to your desktop PC andconfigured correctly.

Step 2 From a client machine (with Windows XP Service Pack 2 or higher), connect to SCOPIADesktop Server via the following URL:

http://<FQDN>/scopia

Step 3 You are prompted to install SCOPIA Desktop Client.

Note If you have not yet installed SCOPIA Desktop Client or if you need to update it, a

yellow message displays on SCOPIA Desktop Server entry page. Select the link toaccess the page from which you can install SCOPIA Desktop Client.


Step 4 After installing SCOPIA Desktop Client, enter a meeting ID in SCOPIA Desktop Server thatstarts with one of the following:

• The prefix configured on your MCU for the SCOPIA Desktop service.

• A valid SCOPIA Management virtual room ID.

The SCOPIA Desktop Client loads and your own video stream is displayed.

Note Ensure there is no firewall enabled on your machine that might block the SCOPIA

Desktop Client.

Sending Meeting Invitations to End Users

This section describes how to view and edit the default instructions for joining a meeting thatthe SCOPIA Desktop Server Outlook add-on sends to invitees, and how to modify the contentsof these e-mail invitations.

While modifying the contents of e-mail invitations, you can define these links:

• Meeting URL—For connecting to a SCOPIA Desktop meeting.

• Portal URL—For watching a webcast or a recorded meeting.

If you have multiple SCOPIA Desktop Servers and want participants to know about them, insertlink information for each of them into each SCOPIA Desktop e-mail configuration.

For example, if you have one SCOPIA Desktop Server in Europe, one in Asia, and another in theUS, you could place the following information in your e-mail:

“From Europe, connect to http://europe.server.com/scopia?ID=1234

From Asia, connect to http://asia.server.com/scopia?ID=1234

From the US, connect to http://us.server.com/scopia?ID=1234.”

Note In a multi-tenant deployment the Contact List and the Outlook Add-On are configured, on

installation, with organization-specific URLs. URLs in invitations sent for the meetings areorganization-specific.

Before you begin

Navigate to the SCOPIA Desktop Administration web user interface.

Procedure

Step 1 Select Messages and Invitations in the sidebar.

Step 2 Select the Invitations tab.

The default instructions for accessing the meeting from a desktop, phone or videoconferencing device appear in the screen.


Figure 3-5 Invitation Message for Desktop Access

Step 3 In the Desktop Access section:

• Select Meeting URL to insert a link to the meeting.

• Select Portal URL to insert a link to the SCOPIA Desktop portal entry page.

• Select Client Installation to insert a link used to ensure that the SCOPIA Desktop client isinstalled and up-to-date.

Note The automatically inserted server address is the SCOPIA Desktop Server Fully

Qualified Domain Name specified during installation.

Step 4 In the Phone Access area, select E.164 to insert the required E.164 alias. If your deploymentdoes not include a gateway, leave the checkbox unchecked and the gateway information willnot be included in Outlook.

Figure 3-6 Invitation Message for Phone Access

Step 5 In the Video-Conference Device Access area, select E.164 to insert the required E.164 alias.

Figure 3-7 Invitations for Video Communication Devices



Sending Administrator Messages to End Users

You can use the Administrative message appearing on the SCOPIA Desktop Server portal entrypage to post important information such as: system status, scheduled shutdown, orconfiguration tips. This section describes how to edit the Administrator and Dial Planmessages.

The Dial Plan message appears in the Invitation dialog box. You can use this message toprovide users with dialing tips, for example, explain what prefixes they should use forgateways of different types.

These tags and attributes are supported in the administrator messages text editor:

<a href="http*" target="_blank"></a><img src=”http*”><iframe src=”http*”></iframe><font color=#123456|red|green|blue|”></font><u>underlined text</u><i>italic text</i><b>bold text</b><br> to break a line<ol><li>Ordered list items</li></ol><ul><li>Unordered list items</li></ul><p></p><div></div>

You must fix a width and height of the <iframe> tag according to the style sheet of thecorresponding page. For example, for the portal entry page, the style sheet looks like this:

<style> .motd iframe { width: 100% height: 150px }</style>

The administrator message text editor replaces single ‘&’ characters with ‘&amp’; it alsoreplaces ‘<‘ and ‘>’ of invalid tags with ‘&It’ and ‘&gt’ respectively.

Before you begin

Navigate to the SCOPIA Desktop Server Administration web user interface.

Procedure

Step 1 Select the Messages and Invitations icon in the sidebar.

Figure 3-8 Messages and Invitations Icon


Step 2 Select the Messages tab.

Step 3 Select the Administrative Message check box.

Figure 3-9 Administrative Messages Section

Step 4 Modify the text of the entry page message as required.

Step 5 Select the Invitation Dial Plan Assistance check box.

Figure 3-10 Invitation Dial Plan Assistance Section

Step 6 Modify the text of the invitation message as required.


Configuring Dial String Rules

This section describes how to configure dial string rules in SCOPIA Desktop. Dial string ruleslook for prefixes in the dial string, alter the string according to your organization’s policy, androute the call to the correct gateway or gatekeeper.

• Planning Rules to Modify Dial Strings .................................................... page 21

• Adding or Editing a Dial String Rule ...................................................... page 24

• Deleting a Dial String Rule ................................................................. page 27

Planning Rules to Modify Dial Strings

Depending on the phone system of your organization, you may already have a prefix of ‘9’ (orsome other number) to call outside the organization. More specifically, a gateway reads andinterprets the dial string, sees the ‘9’, and routes the call to a gateway to reach an external


phone line. It then alters the dial string by removing the ‘9’, and sends the remainder of thenumber to the external phone exchange.

Similarly, you may also have a prefix of ‘1’ or ‘0’ to dial outside your city or state (longdistance calls), and ‘00’ or ‘011’ for international calls. If you have branches in otherlocations, your gateways/gatekeepers may have dedicated prefixes to reach that branch’sexchange. For example, all dial strings beginning with ‘5’ may be routed to the Hong Kongoffice. In each case, your call system routes to different gateways or gatekeepers by readingand interpreting your dial prefixes.

In SCOPIA Solution deployments, dial prefixes are interpreted and altered when:

• When a call is routed to a local H.323 PSTN or ISDN gateway. SCOPIA Desktop modifies theprefix to add routing information.

• When there is a SIP PBX either on-site or at a remote location, SCOPIA Desktop detectsphone numbers in the directory and appends the SIP URL to forward it to the rightgateway.

There are several methods SCOPIA Desktop uses to alter dial strings:

• string normalization

• prefix or suffix substitution

• prefix or suffix addition

• prefix stripping

When you create the rules for SCOPIA Desktop to alter dial strings, consider that the rules areapplied in the specific order they are listed.

In addition, note that every dial string alteration always starts with normalization. Duringnormalization any non-numeric characters except “+” are removed. For example:

• 1 (603) 407-5956 becomes 16034075956

• +1 (603) 407-5956 becomes +16034075956

Thereafter, you should list your rules so that the more specific rules are applied first,followed by the more general. For example, a rule which replaces all +1603 prefixes is morespecific than a rule which replaces all +1 prefixes. Therefore the more specific +1603 ruleshould be executed first.

Note If during the rule configuration you leave the replacement string blank, SCOPIA Desktop strips

the prefix from the address.

Table 3-2 on page 23 shows the rules required to edit the dial strings so that:

• Any phone number starting with an area code of +1603, 1603, or 603 and followed byexactly seven digits should be routed to a gatekeeper/gateway which is accessed with theprefix 1370. The seven digits following the prefix remain intact.

• Any other long distance (national) number indicated by +1 and followed by 10-digit phonenumber should be routed to a gatekeeper/gateway by substituting 11701 for the +1 andkeeping the subsequent 10 digits.

• Any calls starting with the international country code prefix of +44 for the UK followed byany random number of digits is re-routed to the 10700 gateway.


Table 3-2 Simplified example for local, national and international dial string rules

Match Prefix Replacement OptionalSuffix

Example InputString

Example ResultString

Comments

603xxxxxxx 1370 6035555555 13705555555 A call to area code 603 with sevendigits following is routed to a localcall gateway, accessed with thenumber 1370. The remainder of thenumbers remain intact.

1603xxxxxxx 1370 16035555555 13705555555 A call to area code 603, also whenprefaced by a ‘1’, is also routed toa local call gateway, accessed withthe number 1370. The remainder ofthe numbers remain intact.

+1603xxxxxxx 1370 +16035555555 13705555555 A call to area code 603, even whenprefaced by a ‘+1’, is also routed toa local call gateway, accessed withthe number 1370. The remainder ofthe numbers remain intact.

+1xxxxxxxxxx 11701 +15085555555 117015085555555 All other long distance calls routedto another gateway, accessed withthe number 11701.

+44 10700 +445556666666 107005556666666 International calls to England go tothe London local call gateway,accessed by the number 10700.

Table 3-3 on page 24 shows the rules required to edit the dial strings so that:

• Any phone number starting with the area code +1603, 1603 or 603 and then followed byexactly seven digits is routed to the ‘aa’ SIP gateway by adding the “@sip_aa.acme.com”suffix to the remaining seven digits.

• Any long distance (national) number indicated by +1 and followed by 10-digit phonenumber is routed to the ‘bb’ SIP gateway by adding the “@sip_bb.acme.com” suffix to the10 digits.

• Any calls starting with the international country code prefix of +44 for the UK followed byany random number of digits is re-routed to the 10700 London gateway by replacing theprefix with 0 and adding the “@sipg+_cc.acme.com” suffix.


Table 3-3 Example dial rules to add a suffix to route to a SIP gateway

Match Prefix Replace Optional Suffix Example InputString

Example Result String Comments

603xxxxxxx @sip_aa.acme.com 6035555555 5555555@sip_aa.acme.com A call to area code603 with sevendigits following isrouted to the ‘aa’SIP gateway withthe area coderemoved.

1603xxxxxxx @sip_aa.acme.com 16035555555 5555555@sip_aa.acme.com A call to area code603 with a ‘1’ infront is also routedto the ‘aa’ SIPgateway with thearea code removed.

+1603xxxxxxx @sip_aa.acme.com +16035555555 5555555@sip_aa.acme.com A call to area code603 with a ‘+1’ infront is also routedto the ‘aa’ SIPgateway with thearea code removed.

+1xxxxxxxxxx 1 @sip_bb.acme.com +15085555555 15085555555@sip_bb.acme.com All other longdistance (national)calls routed to the‘bb’ SIP gateway.The ‘+1’ is replacedwith ‘1’.

+44 0 @sip_cc.acme.com +445556666666 05556666666@sip_cc.acme.com International callsto the UK go to the‘cc’ SIP gateway.The ‘+44’ isreplaced by ‘0’.

Adding or Editing a Dial String Rule

A dial string rule is the method used to alter dial strings to reflect the routing policy of yourorganization. For example, a dial string that starts with ‘9’ can be defined to be routed to anoutside line. The rule usually specifies a dial prefix, which the rule then replaces, or adds asuffix to the end of the dial string, so that it can be sent to the appropriategateway/gatekeeper.

To correctly represent the number of digits in a string, use the “x” character to denote ‘anynumber’.

For example, a rule that looks for ‘603’ matches any dial string that begins with ‘603’, while arule looking for ‘603xxxxxxx’ matches only a dial string which begins with ‘603’ and is


followed by another seven digits. You cannot use any other characters, such as a space, a dashor parentheses.

This section details how to create or edit a dial string rule.

Before you begin


Procedure

Step 1 Select the Messages and Invitations icon in the sidebar.


Step 2 Select the Dial Strings tab.

Figure 3-12 List of Dial string rules

Step 3 To add a new rule, select Add.

To edit an existing rule, select the edit icon on the right hand side of the row.


Figure 3-13 New Dial String rule

Step 4 Enter the prefix in the Match Prefix field.

Step 5 Select one of these options:

• Replace—A string matching the prefix is replaced with another string.

• Remove—A string matching the prefix is stripped from the dial string.

• Leave As Is—A string matching the prefix is left as is.

Step 6 If you selected the Replace option, enter the replacing prefix in the field.

Step 7 To add a suffix, select the Append Suffix check box, and then enter the suffix in the field.

Step 8 Enter a comment.

Step 9 Select OK.

Step 10 To test the new dial string rule:

a. Enter a string in the Test a Dial String field.

Figure 3-14 Dial String Test

b. Select the check box for the rule you want to apply to this string.

c. Select Test.

The Dial String Test window appears displaying the dial string after the rule is applied.


Figure 3-15 Dial String Test Results

Deleting a Dial String Rule

A dial string rule is the method used to alter dial strings to reflect the routing policy of yourorganization. For example, a dial string that starts with ‘9’ can be defined to be routed to anoutside line. The rule usually specifies a dial prefix, which the rule then replaces, or adds asuffix to the end of the dial string, so that it can be sent to the appropriategateway/gatekeeper.

This section details how to remove an existing dial string rule.

Before you begin


Procedure

Step 1 Select Messages and Invitations in the sidebar.


Step 2 Select the Dial Strings tab.


Figure 3-17 List of Dial string rules

Step 3 Locate the rule you need to remove and select the check box next to it.

The Add button changes to a Delete button.

Step 4 Select Delete.

Step 5 Select OK to confirm.


Occassional system upgrades and infrastructure changes in your network may requireadditional system maintenance activities to maintain your SCOPIA Desktop deployment. Thissection includes the following topic to assist you in maintaining your deployment:

• Upgrading the SCOPIA Desktop Server License ......................................... page 29

• Backing Up Configuration Settings ....................................................... page 30

• Restoring Configuration Settings ......................................................... page 31

• Enabling Integrated Windows Authentication ........................................... page 31

• Enabling Microsoft Internet Explorer for Integrated Windows Authentication ...... page 32

• Integrating SCOPIA Desktop with Sametime ............................................ page 34

• Working with the Content Slider ......................................................... page 34

• Accessing Log Files ......................................................................... page 36

Upgrading the SCOPIA Desktop Server License

You need to update the SCOPIA Desktop Server license in these cases:

• If you upgrade the SCOPIA Desktop Server by adding the recording feature or increasingthe number of simultaneous recordings which requires a new or updated recording serialkey.

• If you upgrade SCOPIA Solution components by adding SCOPIA MCUs and additional portson the SCOPIA Desktop Server.

Before you begin

Obtain an SCOPIA Desktop Server license key and an optional recording serial key.

Procedure

Step 1 Select Start > Settings > Control Panel.

4 Maintaining the SCOPIA Desktop Deployment

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7 Maintaining the SCOPIA Desktop Deployment | 29

Step 2 Double-click Add or Remove Programs.

Step 3 From the list of programs, choose SCOPIA Desktop, and then Change.

The Setup Wizard opens.

Step 4 In the Welcome screen select Next.

Step 5 In the Program Maintenance screen, choose Modify, and select Next.

Step 6 In the Custom Setup screen, select Next.

Step 7 In the SCOPIA Desktop Serial Key window, enter updated keys, and then select Next.

Step 8 Follow on-screen instructions to complete installation configuration.

Backing Up Configuration Settings

Certain configuration files used by SCOPIA Desktop should be backed up regularly to allowrecovery from catastrophic system failure or instances of corrupted files. During this backupprocedure you copy the xml files which contain these settings:

• Dial string rules

• Administrative message

• Invitation message

• Presence Server database

• Local database

• Local configuration

Procedure

Step 1 Navigate to the following directory: <installdir>\data.

Step 2 Copy the relevant files into a location outside the installation directory:

• ctmx.ini—for local configuration

• motd.html—for administrator message

• dialplanhelp.html—for invitation message

• members.xml—for local database

• dial_string_manipulators.xml—for dial string rules

Note The members.xml is created only if you use SCOPIA Desktop without SCOPIA

Management and add terminals to a local directory. As a result, the directory statusin the system web interface shows a synchronization error with SCOPIA Managementas explained in “Viewing Directory Status” on page 80.


Restoring Configuration Settings

You may need to restore some of the configuration files used by SCOPIA Desktop to allowrecovery from catastrophic system failure or instances of corrupted files.

Procedure

Step 1 Stop the service "SCOPIA Desktop - Apache Tomcat".

Step 2 Navigate to the following directory: <installdir>\data.

Step 3 Replace the relevant file with the backup file:

• motd.html—for administrator message

• dialplanhelp.html—for invitation message

• members.xml—for local database

• dial_string_manipulators.xml—for dial string rules

Step 4 Start the service "SCOPIA Desktop - Apache Tomcat".

Note The members.xml is created only if you use SCOPIA Desktop without SCOPIA

Management and add terminals to a local directory. As a result, the directory statusin the system web interface shows a synchronization error with SCOPIA Managementas explained in “Viewing Directory Status” on page 80.

Enabling Integrated Windows Authentication

When SCOPIA Desktop Server is enabled to use Integrated Windows Authentication (IWA), theuser name and password are verified before being sent across the network. The client browserproves its knowledge of the password through a cryptographic exchange with your Web server.By default, the current Windows user information on the client is used for authentication.

Note SCOPIA Desktop provides IWA only for sign-on to a single Windows domain. You cannot

configure IWA for a multi-tenant deployment.

Before you begin

Ensure that authentication settings are configured for SCOPIA Management.


Procedure

Step 1 Select the Directory and Authentication icon in the sidebar.


The Settings tab is displayed.

Step 2 Select the Integrated Windows Authentication check box.

Figure 4-1 Configurating Integrated Windows Authentication settings for asingle Windows domain

Step 3 Enter the windows domain to which users belong.

Step 4 Enter the NetBIOS short domain name.

Note The NetBIOS short domain name field is case sensitive.

Step 5 Enter the Proxy account user name.

Step 6 Enter the Proxy account password.

Step 7 If a WINS server is not defined, enter the domain controller address.

Enabling Microsoft Internet Explorer for Integrated Windows Authentication

For SCOPIA Desktop to work properly with Integrated Windows Authentication, the SCOPIADesktop Server must be either located in the Intranet zone or be in the list of trusted sites.

You must perform this procedure on SCOPIA Desktop client computers to enable IntegratedWindows Authentication.

Procedure

Step 1 Verify whether Integrated Windows Authentication is enabled for your Internet Explorer:

a. In the Internet Explorer window, from Tools menu select Internet Options.

b. Select the Advanced tab.

c. Under Security section, verify that Enable Integrated Windows Authentication checkboxis selected.


Step 2 To add SCOPIA Desktop Server to the list of Internet Explorer trusted sites:


b. Select the Security tab.

c. Select Trusted Sites, and then select Sites.

Figure 4-2 Internet Explorer Trusted Sites Configuration

d. Enter the SCOPIA Desktop Server site address, for example “sd.server.com”., and thenselect Add.

e. Select Custom level.

f. Under User Authentication section, select the Automatic logon with current user nameand password option.

g. Select OK.

Step 3 To add SCOPIA Desktop Server to the Internet Explorer Intranet zone:


b. Select the Security tab.

c. Select Local Intranet.

d. Select Sites.

e. Select Advanced.


Figure 4-3 Internet Explorer Advanced Security Settings

f. Enter the SCOPIA Desktop Server site address, for example “sd.server.com”., and thenselect Add.

g. Select Custom level.

h. Under User Authentication section, select the Automatic logon only in Intranet zoneoption.

i. Select OK.

Integrating SCOPIA Desktop with Sametime

For SCOPIA Desktop deployments working with Lotus Sametime Web Conferencing plug-in, youmust configure Sametime-related administrative settings. For information about configuringSametime settings, refer to the SCOPIA Connector for IBM Lotus Sametime Installation Guide.

Working with the Content Slider

The Content Slider allows SCOPIA Desktop users to browse presentations and is compatiblewith both SCOPIA Desktop and Mobile users.

The Content Slider is a part of the recorder component, from both an installation andadministration management perspective. Slider functionality is tied to your recording license,and shares the same base configuration (such as network address, gatekeeper/MCU, etc.).They also re-use the same TCP connection for control channel and share the ACL/TLSconfiguration.

Note The Content Slider (Advanced Data Collaboration) service is only available when

communication is set to H.239 over H.264 in the MCU. MCU services configured to H.263 willnot enable Advanced Data Collaboration.


Make note of these considerations when using the Content Slider:

• Generated slides are stored as files in a folder on a local or network mounted drive.

• For every slider session, SCOPIA Desktop specifies a slide folder, a slide set name, slidesize and compression rate.

• SCOPIA Desktop saves slides using a base slide set name and incremental indexing.

For deployments with a single SCOPIA Desktop Server, these scenarios are supported:

• All-in-one. All components are installed on the same box. Recorder/slider share SCOPIADesktop resources with live calls and webcasts.

• Separate box install. The recorder/slider is installed on a separate box and has adedicated SCOPIA Desktop Server.

Note The recorder and slider always shares SCOPIA Desktop resources and disk space for generated

recordings/slides.

For deployments with multiple SCOPIA Desktop Servers, these options are available:

• Centralized recorder/slider. Owners of a single recording license install one recorderserver. All SCOPIA Desktop Servers point to that recorder. Recordings are served forplayback from the central site, while slides are downloaded to and served from a localSCOPIA Desktop.

• Distributed recorders/sliders. Owners of separate recording licenses for each recorderserver install a recorder on each site. This provides distribution where licenses are notcounted as a pool (separate number for each recorder); recordings are only available fromthe SCOPIA Desktop Server they are made from.

Figure 4-4 on page 35 displays the Content Slider tab and all slider sessions currently inprogress, and provides details about the server(s) where there are non-active sessions.

Figure 4-4 Content Slider Tab

If there are errors with a slider session, notices appear as links (per server) in theProblems column. Details are available by selecting the problem link.


Accessing Log Files

SCOPIA Desktop automatically maintains extensive logs to help maintain your deployment andtroubleshoot problems. By accessing the Logging tab, you can enable enhanced logging, whichprovides a network trace on the server (with or without media, depending on your selection)as well as extended middleware logging.

Note Enabling enhanced logging for extended periods of time adds large log files to the system.

Procedure

Step 1 Navigate to the SCOPIA Desktop Server Administration web interface.

Step 2 Select the Status icon in the sidebar.

Step 3 Select the Logging tab.

Figure 4-5 Enabling enhanced logs

Step 4 To download a zipped version of current log files, select Download.

Step 5 (Optional) To enable enhanced logging, select Enable.

The Logging Summary pane displays the current status of enhanced logging - enabled ordisabled.


SCOPIA Desktop allows users to record meetings and to view recorded meetings. A recordingincludes all media types: audio, video and presentation.

Servers used for recording meetings must have a recording license installed on them. SCOPIADesktop supports up to 10 simultaneous recordings. If you did not provide the RecordingServer license key during SCOPIA Desktop Server installation, a default evaluation licenseallows you to record one five-minute meeting at a time.

In deployments where authentication is enabled on SCOPIA Management, recordings may bedesignated as public or private. Public recordings are available for all users, includingauthenticated and guest users. Authenticated users can record private recordings,automatically becoming the recording’s owner. Only recording owners can watch privaterecordings. By default all recordings are public. Recordings made by guest users are alwayspublic.

Note Recordings made using SCOPIA Desktop version 5.x appear as public from SCOPIA Desktop

version 7.5 onwards.

This section describes how to define the recording settings on a SCOPIA Desktop Server.

• Adding a Recording Server ................................................................ page 37

• Calculating Space Needed for Recording ................................................ page 38

• Defining SCOPIA Desktop Recording Settings ............................................ page 39

Adding a Recording Server

If the Recording Server was not installed during the SCOPIA Desktop Server installation, andusers recorded meetings using the evaluation license, you can add the Recording Server to thedeployment afterwards.

5 Configuring SCOPIA Desktop to Manage RecordingFeatures

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7 Configuring SCOPIA Desktop to Manage Recording Features | 37

Before you begin

Prior to modifying the SCOPIA Desktop installation, acquire the recording license and makesure you have the license key for the Recording Server.

Procedure

Step 1 Open the Windows Control Panel > Add or Remove Programs.

Step 2 Select the SCOPIA Desktop Server and select Change.

The SCOPIA Desktop Server Installation Wizard opens.

Step 3 Select a language and select OK.

The Welcome screen is displayed.

Step 4 Select Next.

Step 5 Select Modify to change the existing installation, and then select Next.

The Custom Setup screen opens.

Step 6 Select the Recording Server icon and select the This feature will be installed on local harddrive option.

Step 7 Select Next.

The SCOPIA Desktop License Key screen opens.

Step 8 Enter the license key for the Recording Server, and then select Next.

The Network Configuration screen opens.

Step 9 Select Next in the rest of the configuration screens.

Step 10 In the Ready to Modify the Program screen, select Install.

Calculating Space Needed for Recording

Use the following formula to calculate the space required for recordings:

Recording Bandwidth (in megabytes) × Time (in seconds) + 20% Overhead

For example, for a call of 1 hour at 384 Kbps, calculate as follows:

384 Kbps × (60 minutes × 60 seconds) = 1382400 kilobits

1382400 ÷ 1024 = 1350 megabits

1350 ÷ 8 = 168.75 megabytes

168.75 × 20% = 33.75 megabytes (overhead)

Total is 168.75 + 33.75 = 202.5 megabytes (including overhead)


Defining SCOPIA Desktop Recording Settings

You can define the recording policies of the SCOPIA Desktop Server with SCOPIA Management,to determine whether users are allowed to record meetings. In deployments without SCOPIAManagement, you can define the recording policy on SCOPIA Desktop Server by enabling therecording option for SCOPIA Desktop users.

Note In deployments where the Recording Server is installed on the same server as the SCOPIA

Desktop Server, users watching recorded meetings take up SCOPIA Desktop bandwidth whichcan be used for other purposes, such as videoconferences.

When you enable high definition recordings in the MCU, SCOPIA Desktop Server startsrecording in high definition. If the attempt to record in high definition fails, the SCOPIADesktop Server automatically switches to standard definition and continues recording.

Before you begin

Verify the recording server is defined in the SCOPIA Desktop Server, by checking the following:

• Navigate to the SCOPIA Desktop Server Administration web user interface.

• Select Deployment in the sidebar, and verify that the Recording check box is selected.

• Select Status in the sidebar, and verify that the IP address in the Recording ServerAddress field is correct.

Procedure

Step 1 Select Recording in the sidebar.

Figure 5-1 SCOPIA Desktop Recording Icon

The Settings tab is displayed.

Step 2 To configure standard definition recording, in the Limits section select a value from theMaximum Bit Rate list under Standard Definition.

Setting the recording bit rate to a value lower than 256 Kbps can affect the quality and framerate of the presentation data in the videoconferencing and streaming modes.

Step 3 To configure the quality of high definition recording, in the Limits section:


b. Select a value from the Maximum Bit Rate list under High Definition.

Setting the recording bit rate to a value lower than 256 Kbps can affect the quality andframe rate of the presentation data in the videoconferencing and streaming modes.


Figure 5-2 Recording Video and Bitrate Settings

Step 4 Enter a value in the Maximum Recording Duration field.

This value controls maximum allowed duration for any recording.

Step 5 In the Playback Bandwidth section, enter a value in the Total Bandwidth Allowed field.

This is the total bandwidth to be shared by all users who are watching a recording.

Figure 5-3 Recording Playback Bandwidth Settings

Step 6 Enter a value in the Minimum Bandwidth required for download field.

For example, if you set the Total Bandwidth Allowed value to 100 Mb/s, then SCOPIADesktop allows 100 Mb/s bandwidth if one user watches a recording and 50 Mb/s bandwidthfor each user if two users watch recordings. You need to set the Minimum Bandwidthrequired for download to prevent too many users from watching recordings at the sametime.

Step 7 In the Policies section, choose an option from the Send tone periodically during recordinglist.

This defines the frequency of the sound signal played during a recording which reminds userstheir meeting is being recorded.

Step 8 To disable the automatic recording feature, clear the Allow virtual rooms and scheduledmeetings to be recorded automatically check box.

If automatic recording is enabled on multiple SCOPIA Desktop Servers, a recording is made oneach server, creating several identical recordings. In this case, enable automatic recording onjust one of the SCOPIA Desktop Servers, while disabling the automatic recording feature onthe others.

Step 9 Select the Allow meeting participants to record check box to enable recording for SCOPIADesktop users.

This only applies to deployments without SCOPIA Management. If you have SCOPIAManagement, this setting cannot be modified since SCOPIA Management controls therecording policies.


Step 10 In the Connection Information section, enter the full name of the recording server (FQDN) inthe Public Address field.

This is an IP address accessible from outside the NAT, in cases where the regular IP address ofthe SCOPIA Desktop Recording Server may not be directly accessible by clients.

Figure 5-4 Connection Information Settings

Step 11 Enter the HTTP Port of the publicly accessible IP address.

This port is used by clients to access the recording. You must configure the HTTP port on theRecording Server and open this port on the firewall



This section provides instruction for creating and managing recordings within SCOPIA Desktop.The topic included are:

• Viewing Recording Information ........................................................... page 42

• Editing Recording Attributes .............................................................. page 45

• Managing Categories ....................................................................... page 46

• Creating Categories for Multiple Recordings ............................................ page 47

• Selecting Recording Owners ............................................................... page 48

• Recording Meetings ......................................................................... page 49

• Stopping a Recording in Progress ......................................................... page 51

• Deleting a Recording ....................................................................... page 51

Viewing Recording Information

You can review the list of recordings made on this SCOPIA Desktop using the Recordings tab.The following information is displayed:

• Meeting ID

• Name

• Start Time

• Duration

Note For meetings that are currently being recorded, the “In progress” indication is

displayed.

• PIN-protected indicator

• Owner (only in advanced deployments where authentication is enabled on SCOPIAManagement)

6 Managing Recordings

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7 Managing Recordings | 42

• Private recording indicator (only in advanced deployments where authentication isenabled on SCOPIA Management)

You can also access for the following additional information for a specific recording:

• Description

• Categories—Keywords associated with recordings

• Recording URL

Figure 6-1 on page 43 shows recording information for an organization pertaining to a singletenant deployment.

Figure 6-1 Viewing recording information for an organization pertaining to asingle tenant deployment

Figure 6-2 on page 43 shows recording information for an organization pertaining to a multi-tenant deployment. Scroll the dropbox list in the Organization field to select the organizationwhose recording information you need to check.

Figure 6-2 Viewing recording information for a company pertaining to amulti-tenant deployment

Note Select the (none) setting in the dropbox list to bring up recordings that do not belong to an

organization. This could happen if you moved from a single-tenant deployment to a multi-tenant one.

Before you begin



Procedure

Step 1 Select Recording icon in the sidebar.

Step 2 Select the Recordings tab.

The Recordings tab is displayed showing a list of recordings. By default all recordings aredisplayed.

Step 3 To filter recordings, select a category from the Show list.

Figure 6-3 Scopia Desktop Administration - Show List

Step 4 To sort recordings, select the column according to which you want to sort.

Step 5 To search for a specific recording by an attribute:

• Meeting ID—Select the Meeting ID column, enter the meeting ID in the Search field, andthen select the Search button.

• Owner—Select the Owner column, enter the owner name in the Search field, and thenselect the Search button.

• Meeting Name—Select any column except the Meeting ID and Owner columns, enter themeeting name in the Search field, and then select the Search button.

Figure 6-4 Recording Tab Search Box

Step 6 To display additional information for a specific recording, select the Information icon: TheMeeting Information window opens.


Figure 6-5 Recording Information Dialogue Box

Editing Recording Attributes

You can assign either an owner or an access PIN for recording security. The access PIN isoptional and is used for viewing recordings. In the list of recorded meetings, recordingsprotected by an access PIN are marked by a key icon. If you assign an owner to a recording,only the owner can edit it. There are no PINs for recordings assigned to owners.

Before you begin


Procedure

Step 1 Select Recording icon the sidebar.


Step 3 Select the Manage Recording button for the required recording in the list:

The Edit Recording window is displayed.


Figure 6-6 Edit Recording Window

Step 4 To modify the recording name and description, enter new text in relevant fields.

Step 5 If necessary, select the check box to make the recording public.

Step 6 If you enabled user authentication, you can select or remove a recording owner.

Step 7 To modify categories for the recording, select a category in the relevant pane and select theTransfer button.

Step 8 To set the owner PIN for the recording, enter the owner PIN.

Step 9 To set the access PIN, enter the access PIN.

Step 10 Select OK.

Managing Categories

Apart from standard attributes like an ID, name, and duration, SCOPIA Desktop provides acategory—a special attribute that can help organizing and searching recordings. Both users andadministrators can assign categories to recordings. Administrators manage categories bymodifying a list of existing categories, while users can only select categories from this list toassociated them with recordings.

If you rename an existing category, SCOPIA Desktop automatically updates attributes for allrecordings belonging to the modified category. Deleting a category does not cause SCOPIADesktop to delete recordings belonging to the deleted category.

Before you begin



Procedure

Step 1 Select the Recording icon in the sidebar.

Step 2 Select the Categories tab.

Step 3 To create a new category:

a. In the Create a new category field, enter the name.

b. Select Create.

The new category appears in the list.

Step 4 To edit an existing category:

a. Select the Edit icon:

b. Enter the new name for the category.

c. Select OK.

Step 5 To delete an existing category:

a. Select the Delete icon.

b. Select Yes.

Creating Categories for Multiple Recordings

You can create categories for multiple recordings at once. For example, you may want togroup a specific presenter’s recordings and save them separately from recordings of otherpresenters.

Before you begin


Procedure



Step 3 In the recording list, select check boxes for required recordings.

Step 4 Select the Categorize button.

The Categorize Recordings window opens.


Figure 6-7 Categorize Recordings Dialogue Window

Step 5 To assign a category, which is not currently assigned to selected recordings:

a. In the left pane, select the check box for this category.

b. Select Assign.

Step 6 To remove a category, which is currently assigned to selected recordings:

a. In the right pane, select the check box for this category.

b. Select Remove.

Selecting Recording Owners

You can assign ownership to recordings when you want to grant administrative control for arecording to a specific user.

Before you begin


Procedure



Step 3 In the recording list, select check boxes for each recording you want to assign to an owner.

Step 4 Select Select Owner.

The Select Recording Owner window opens.


Figure 6-8 Select Recording Owner Window

Step 5 Select the owner name from the Search field.

Step 6 Select Submit.

Step 7 To remove an owner which is currently assigned to selected recordings:

a. Select the check box for the recording in the list.

b. Select Remove.

Recording Meetings

There are several ways of recording meetings:

• You can configure SCOPIA Management to automatically record a user virtual room or ascheduled meeting when the meeting begins. For detailed information, see theAdministrator Guide for SCOPIA Management.

• SCOPIA Desktop users can connect to a meeting and start recording from a conferenceroom depending on their configuration in SCOPIA Management. SCOPIA Desktop guests canconnect to a meeting and start recording from a conference room if guest policies inSCOPIA Management allow to do s

• You can record meetings using the SCOPIA Desktop Server Administration web userinterface as explained in this procedure.

Note In a multi-tenant deployment, each recording is associated with only one organization. A

recording is always listed under the organization in which the meeting was recorded, even ifthe recording was started by a user belonging to a different organization than the meetingowner.

Before you begin

• Verify that you have the ID of a meeting you wish to record.



Procedure

Step 1 Select the Recording icon in the sidebar.


Step 3 In the Start recording meeting ID field, enter ID.

Figure 6-9 Start Recording Button

Step 4 Select Record.

The Start Recording window is displayed.

Figure 6-10 Start Recording Window

Step 5 Enter recording name and description.

Step 6 Assign categories as necessary.

Step 7 To set the owner PIN for the recording:

a. Choose either the Use the moderator PIN as the Owner PIN or Specify an Owner PINoption.

b. Enter the owner PIN.

c. Enter the owner PIN in the Confirm field.

Step 8 To set the meeting PIN:

a. Choose the Use the meeting PIN as the Access PIN or Specify an Owner PIN option.

b. Enter the access PIN.

c. Enter the access PIN in the Confirm field.

Step 9 To set an owner for the meeting, select Select Owner.


Step 10 If you set an owner for the meeting, select the Make this recording private check box.

Step 11 Select Start Recording.

The meeting appears in the list, and its duration is indicated as “In Progress”.

Stopping a Recording in Progress

You can stop any recording which is in progress. When you do so, meeting participants arenotified that the recording is stopped. The meeting moderator receives a notification that therecording is stopped by the administrator.

Before you begin


Procedure

Step 1 Select Recording in the sidebar


Step 3 In the recording list, select the check box for recordings you wish to stop.

Figure 6-11 Stop Recording Button

Step 4 Select Stop.

Step 5 Select Yes in the confirmation message.

Deleting a Recording

You can permanently remove a recording from SCOPIA Desktop by deleting it from therecording list.

When you delete a recording which is in progress, the meeting participants are notified thatthe recording is stopped. Also, the meeting moderator receives a notification that therecording was deleted by the administrator.


Before you begin


Procedure



Step 3 In the recording list, select the check box for recordings you wish to delete.

Step 4 Select Delete.

Step 5 Select Yes in the confirmation message.


This section describes how to configure SCOPIA Desktop streaming settings. Streaming can bemanaged either by a single SCOPIA Desktop Server or by multiple SCOPIA Desktop Servers. If asingle SCOPIA Desktop Server is set to manage streaming, all other participants are directed tothis server. If multiple SCOPIA Desktop Server are configured to manage streaming, eachmanages streaming independently.

To designate a single SCOPIA Desktop Server to manage streaming, enable streaming on thisSCOPIA Desktop Server. In this case you must disable streaming on other SCOPIA DesktopServers in the same deployment. However, you can configure those servers to allow theviewing of webcasts from the SCOPIA Desktop Server on which streaming is enabled.To enablemultiple SCOPIA Desktop Servers for managing streaming, enable streaming on each SCOPIADesktop Server in this deployment.

The SCOPIA Management Streaming feature requires an additional license.

Table 7-1 on page 53 compares deployments using a single SCOPIA Desktop Server todeployments using multiple SCOPIA Desktop Server for streaming.

Table 7-1 Comparison of Streaming Server Deployment Types

Characteristic Single SCOPIA Desktop Serverenabled for streaming

Multiple SCOPIA DesktopServers enabled forstreaming

HTTP performance Slower HTTP performanceover the Internet betweendispersed sites and thedesignated SCOPIA DesktopServer.

Faster HTTP performancewithin local sites.

Load on Streaming Server Many streaming clients atdifferent sites sharing theresources of a singlestreaming server.

Streaming clients at individualsites share a local streamingserver.

7 Configuring SCOPIA Desktop Server to ManageStreaming Features

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7 Configuring SCOPIA Desktop Server to Manage Streaming Features | 53

Characteristic Single SCOPIA Desktop Serverenabled for streaming

Multiple SCOPIA DesktopServers enabled forstreaming

SCOPIA Desktop Servermanagement

Single location for managingstreaming.

Streaming must be enabled ordisabled on each individualSCOPIA Desktop Server.

Participant count All participants connected tothe central SCOPIA DesktopServer are shown in themeeting display.

Only participants connectedto a specific local SCOPIADesktop Server are shown.

Defining the Streaming Server Settings

You need to perform the procedure described in this section only if you enabled streamingduring deployment configuration.

The public address you define during this procedure performs a similar role to the publicaddress defined for the SCOPIA Desktop Server. If the Streaming Server resides behind a NAT,the clients might not resolve the Streaming Server IP address. In this case, the clients use thepublic address to connect to the Streaming Server.

You can enable and configure multicast streaming to allow an unlimited number ofsimultaneous streaming connections. Multicast streaming in SCOPIA Desktop is performedwithout Streaming Server support. If the IP address of a client computer is not within themulticast IP address range you configured, this client will use a unicast streaming connection.

During multicast configuration you also need to define the Time to Live value—the number oftransmissions of a multicast packet that SCOPIA Desktop propagates throughout the network.Setting this value to 1 means that a multicast packet stays within a local network. The changein the multicast streaming configuration applies only to meetings created after the changetakes place; the change does not effect meetings in progress.

By default, the maximum number of ports used for streaming is 600. However, we recommendthat you adjust the number of ports value to match the supported number of streaming portsbased on the CPU and Memory system requirements.

Before you begin


• Select Deployment in the sidebar and verify that streaming is enabled on the Serverspage.

Procedure

Step 1 Select the Streaming icon in the sidebar.


Figure 7-1 Scopia Desktop Administration Streaming Icon

Step 2 Select the Settings tab.

Step 3 To configure standard definition recording, select a value from the Maximum Bit Rate listunder Standard Definition.

Figure 7-2 Video Settings Section

Step 4 To configure high definition recording, perform the following:


b. Select a value from the Maximum Bit Rate list under High Definition.

Step 5 If necessary, configure multicast settings:

Figure 7-3 Multicast Settings Section

a. Check the Enable Multicast option.

b. Enter the multicast IP address.

The valid multicast IP address is in the range of 224.0.0.1 and 239.255.255.255.

c. Enter the Time to Live value.

d. Define clients that will be able to watch multicasts by entering IP range in the fields andselecting the Arrow button.

Step 6 Enter a public address.

We recommend to use a public address that clients can resolve.

Step 7 Enter a TCP streaming port.

The default port is 7070.


Note If you use a TCP port different from the default value of 7070, you must open this

port on the firewall. For more information about configuring a UDP connection, referto the “Configuring Streaming or Playback using the UDP connection” section of theSCOPIA Solution Deployment Guide.

Step 8 Enter a value for the maximum number of ports you want to use for unicast streaming clients.

Figure 7-4 Port Settings Section



Customers can change logos and strings which contain the default RADVISION or SCOPIADesktop branding to brand the user interface with their own logos and strings. You can changeimages and strings using the SCOPIA Desktop Branding application.

• Replacing Images ........................................................................... page 57

• Modifying Strings ........................................................................... page 58

• Saving or Restoring Branding- Related Changes ........................................ page 59

• Restoring Default Images and Strings .................................................... page 60

Replacing Images

You can replace images appearing in the SCOPIA Desktop user interface by using the Brandingapplication on SCOPIA Desktop Server. Replacement takes affect immediately, therefore werecommend that you should not replace images on a server that is currently in service.Replacement does not affect the proper function of the SCOPIA Desktop user interface.Mostweb browsers store local copies of images to accelerate future views of the same image. Thispractice is called caching. Any browser that has previously loaded an image that you replacemay display its local copy of the old image rather than your replacement image. If an image inthe SCOPIA Desktop user interface does not appear to be the same as the one displayed as thecurrently installed image, then you must clear your browser's cache. SCOPIA Desktop Server isreleased with a set of default images which you can restore at any time.

Procedure

Step 1 Select Start.

Step 2 Choose Programs > SCOPIA Desktop > Branding Application.

The branding application starts.

Step 3 Select the Images tab.

The images that can be replaced are displayed together with the recommended size and abrief description of each image.

8 Customizing the SCOPIA Desktop User Interface

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7 Customizing the SCOPIA Desktop User Interface | 57

Note If an image has a transparent background, it appears with a gray and white

“checkerboard” background in the preview fields.

Step 4 From the list, choose the image you want to replace.

A brief description of the image is displayed along with the recommended image size. TheDefault image area shows the image that was originally distributed with the product. TheCurrently installed image shows the image that appears in the user interface.

Step 5 Select Select File, and then choose the replacement image.

A preview of the image is displayed. If you use an image that the application indicates as notproperly sized, a warning appears below the image description. Using an image that does notmatch the original image size might result in incorrect image display.

Step 6 If you use an image that is not properly sized, verify that the image is displayed correctly:

a. Verify that the SCOPIA Desktop Server is running.

b. Review the SCOPIA Desktop user interface after replacement in order to verify that theimage appears correctly.

Step 7 Select Install Image to use the replacement image.This image is replaced.

Note If an old image still appears, see your browser's documentation for information

about removing temporary internet files.

Step 8 To restore a default image, select Restore Original Image.

Step 9 Repeat Step 4 through Step 7 for other images.

Modifying Strings

You can modify some strings appearing in the SCOPIA Desktop user interface. New stringvalues you set using the Branding application appear in the user interface only after SCOPIADesktop Server starts and reads these values. Therefore, you can see modified strings onlyafter the changes are applied and after the server is restarted if it was running when youmade the changes.

Procedure



Step 3 Select the Strings tab.

The strings that can be replaced are displayed along with the their values:

• The Rebranded Value column displays values that are currently saved. When the SCOPIADesktop Server is restarted, these are the values that appear in the user interface.


• The Default Value column displays values that are the original strings that weredistributed with SCOPIA Desktop.

Step 4 Select the relevant cell in the New Value column and type in the new string you want to use.

Or

Double-click a value in the Rebranded Value column or the Default column to copy it into theNew Value column.

Step 5 Repeat Step 4 for other strings if necessary.

Step 6 Select Apply.

The new values are saved. The modified values appear in the Rebranded Value column.

Step 7 Restart the “SCOPIA Desktop - Apache Tomcat” service for the changes to take affect.

Step 8 To restore default strings:

a. Select Restore All Default Strings.

b. Select Apply.

c. Restart the “SCOPIA Desktop - Apache Tomcat” service for the changes to take affect.

Saving or Restoring Branding- Related Changes

You can save modified images and strings by exporting them to a file. You can later use thisfile to import values from it, thus restoring them.

Procedure



Step 3 To save modified images and strings:

a. From the File menu, choose Export.

b. Specify the location in which you want to save the file.

c. Select Save.

Step 4 To restore the modified images and strings from the file:

a. From the File menu, choose Import.

b. Navigate to the export file.

c. Select Import.



Restoring Default Images and Strings

SCOPIA Desktop Server is released with a set of default images and string values. You canrestore both default images and default string values at once. Restoring default images andstrings overwrites currently used images and string values with the default settings.

Procedure



Step 3 From the File menu, choose Restore all.



SCOPIA Desktop can be deployed as multiple servers to increase the number of calls availableto the organization (scalability) and for redundancy when one server fails (high availability).

SCOPIA Desktop Servers can be made scalable using a load balancer configured for scalabilityand high availability in several ways, depending on the available hardware and network. Thepreferred method to achieve this goal is to use a load balancer device such as the RadwareAppDirector. Similar configuration should be possible with other third-party load balancers.

Figure 9-1 on page 61 shows a typical load balancing deployment.

Figure 9-1 Typical SCOPIA Desktop Deployment

9 Configuring Multiple SCOPIA Desktop Servers

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7 Configuring Multiple SCOPIA Desktop Servers | 61

SCOPIA Desktop Servers are clustered behind a load balancing system for scalability and highavailability.

External SCOPIA Desktop Clients access the IP address of the cluster, like SD.company.com,which points directly to the load balancer via the firewall. The load balancer resolves therequest to one of the servers in the cluster (as opposed to offering several IPs and leaving it tothe client browser to cycle through them).

Internal SCOPIA Desktop Clients type the same address, SD.company.com, which is alsoresolved directly to the load balancer, this time with its internal address.

Note • The firewall must be configured with a static IP mapping.

• Scalability cannot be currently extended to streaming servers.

We recommend using the health checks of ICMP echo request and HTTP Web (TCP port 80) tomonitor the cluster in your deployment.

If users login with a username and password to their SCOPIA Desktop Client,the underlyingTomcat Application Server of each SCOPIA Desktop Server should be configured to form acluster. This prevents users from re-entering their credentials when the load balancer routescalls to other servers in the cluster.

The load balancer might send calls to a server that cannot handle them due to a lack ofresources. To avoid call failure or call redial by a SCOPIA Desktop Client, we recommend toenable the server redirection feature which allows clients that are routed to busy servers totry connecting to another server.

These topics explain the different configurations load balancing configurations supported bythe SCOPIA Desktop.

• Configuring SCOPIA Desktop Servers for Load Balancing .............................. page 62

• Implementing Scalability with the Radware AppDirector ............................. page 63

• Implementing Scalability with a Third-party Load Balancer .......................... page 65

• Configuring Multiple SCOPIA Desktop Servers as Tomcat Clusters ................... page 67

• Configuring Server Redirection ........................................................... page 69

• Configuring Streaming and Recording for Scalability .................................. page 70

Configuring SCOPIA Desktop Servers for Load Balancing

You can deploy multiple SCOPIA Desktop Servers for dialing to and from your organization.More servers translates to higher capacity. Deploying multiple servers in a load balancedenvironment offers several advantages:

• If one server fails, the remaining servers can continue working, offering even higherreliability in video services

• Load balancers can even-out the workload across several servers and thus allow for betterutilization of the resources.


This configuration is required when the Radware AppDirector or other third-party loadbalancers are used in the SCOPIA Desktop deployment. For more information, see “ConfiguringMultiple SCOPIA Desktop Servers” on page 61.

Perform this procedure on each SCOPIA Desktop Server in the deployment.

Note The procedure also enables the HTTP persistency cookie in the SCOPIA Desktop Server.

Procedure

Step 1 Locate the ctmx.ini file in <install directory>\data\

Note For backup purposes, we recommend to save a copy of the original ctmx.ini file

before editing it.

Step 2 Open the ctmx.ini file in a text editor.

Step 3 Edit the file as follows:

a. Locate the [redundancy] section of the file.

b. Set loadbalancerenabled to true.

Step 4 Restart the SCOPIA Desktop – Apache Tomcat service.

Implementing Scalability with the Radware AppDirector

For scalability and high availability several SCOPIA Desktop Servers can be clustered behind aload balancing system such as Radware's AppDirector.

Radware AppDirector is an application which can be configured to track the meeting ID,enabling it to route users in the same meeting to a single SCOPIA Desktop Server. TheAppDirector routes all the clients belonging to the same meeting to the same server.Simultaneously, in order to balance the load on the servers, the AppDirector routes differentmeetings to different servers.

When a request arrives to the main virtual IP address, the AppDirector inspects the cookieembedded within the HTTP request to determine whether it is a part of an existing sessionwith a server. If it is, the AppDirector redirects the HTTP request to that server.

When a new session is requested, the AppDirector can be configured to route requests to theserver with the least amount of traffic.

For information on SCOPIA Desktop functionalities which are supported with the AppDirector,see “Configuring Multiple SCOPIA Desktop Servers” on page 61.

This procedure describes the initial settings required for allowing the load balancer tofunction with the SCOPIA Desktop deployment. For the detailed configuration of the loadbalancer, see the Radware's AppDirector documentation.


Note This procedure should only be performed by system integrators familiar with AppDirector.

Before you begin

• Make sure you have the IP addresses of the SCOPIA Desktop Servers you need to configurein the load balancer.

• Perform the procedure in “Configuring SCOPIA Desktop Servers for Load Balancing” onpage 62.

Procedure

Step 1 Login to the AppDirector.

Step 2 Create a farm by selecting AppDirector > Farms > Farm Table > Create.The farm is a virtual entity that combines one or more physical servers into a single entity.Calls arriving to the farm's virtual IP are distributed among the physical servers.

a. Enter the server farm name in the Farm Name field (for example, Server_Farm).

b. Enter the preferred value in seconds in the Aging Time field (for example, 90000). Itindicates the interval of time that elapses from the moment the source IP addressbecomes inactive until its removal from the Client Table of the load balancer. The sourceIP address is active in that table as long as there is an exchange of requests with theserver.

c. Select the Dispatch Method the load balancer uses for distributing client requestsbetween servers in this farm. For example, select Cyclic if you want the load balancer todirect traffic to each server in a round robin mode.

d. Set the Sessions Mode field to EntryPerSession to ensure the load balancer continuesdispatching packets from the same client to the same server throughout the session.

e. Select TCP Port in the Connectivity Check Method field.

f. Use the default values for the remaining fields.

g. Select Set.

Step 3 Configure a virtual IP address for the farm by selecting AppDirector > Layer 4 TrafficRedirection > Layer 4 Policies > Create.This is the address the load balancer uses to forward requests to the servers grouped in a thefarm. AppDirector uses the Layer 4 protocol and the request’s destination port to select therequired farm. TCP (Transmission Control protocol) and UDP (User Datagram Protocol) arepart of the Layer 4 protocol. AppDirector manages the virtual IP addresses using Layer 4policies.

Note Add the farm's virtual IP address to the organization's firewalls to ensure

communication is possible with the farm.

a. Enter the IP address of the server farm in the Virtual IP field.


b. Select Any in the L4 Protocol field, meaning that the Layer 4 traffic policy supports anyIP protocol.

c. Enter a policy name in the L4 Policy Name field (for example, Main_Policy).

d. Enter the name of the server farm in the Farm Name field (for example, Server_Farm).

e. Use the default values for the remaining fields.

f. Select Set.

Step 4 Add the servers to the farm by selecting AppDirector > Application Servers > Table >Create.

a. Select the name of the newly created farm in the Farm Name field (for example,Server_Farm).

b. Enter the IP address of the server in the Server Address field.

c. Enter the name of that server in the Server Name field.

d. Enter the server description in the Server Description field.

e. In the Client NAT Address Range field, select the IP address the AppDirector uses toreach the physical server.

f. Use the default values for the remaining fields.

g. Repeat these steps for each of the physical servers that compose the farm.

Step 5 Configure cookie persistency by selecting AppDirector > Layer 7 Server Persistency > TextMatch > Create.This configures the persistency rule in the load balancer so that all the clients belonging tothe same meeting are routed to the same server. The rule examine the HTTP persistentcookie sent by SCOPIA Desktop Clients. The cookie has the format CONFSESSIONID =<meeting number>.

a. Enter the name of the farm in the Farm Name field. For example, Server_Farm.

b. Select Cookie in the Lookup Mode field.

c. Enter CONFSESSIONID in the Persistency Identifier field.

d. Enter 90000 in the Inactivity Timeout [sec] field.

e. Select Client Request in the Learning Direction field.

f. Select Enabled in the Ignore Source IP field.

g. Use the default values for the remaining fields.

h. Select Set.

Implementing Scalability with a Third-party Load Balancer

For scalability and high availability several SCOPIA Desktop Servers can be clustered behind athird-party load balancer with the added advantage of continued service even when one ormore of the servers fails.

For information on this type of load balancing, see “Configuring Multiple SCOPIA DesktopServers” on page 61.


Perform this procedure to confirm that the load balancer includes the settings required forrouting calls to the SCOPIA Desktop Servers.

Before you begin

• Make sure you have a detailed understanding of this load balancing tool and the HTTPprotocol to setup this deployment.

Note This procedure does not give instructions since it applies to generic third party load

balancing systems. Therefore this section is only for experts familiar with thedeployed load balancer.

• Perform the procedure in “Configuring SCOPIA Desktop Servers for Load Balancing” on

page 62.

Procedure

Step 1 Make sure to configure a virtual IP (VIP) on the load balancer for the SCOPIA Desktop Serverfarm.

The SCOPIA Desktop Clients use the VIP to reach the cluster of SCOPIA Desktop Servers.

Step 2 Select a routing policy for the load balancer.

Most load balancers offer a selection of policies regarding the VIP. We recommend to choosea policy that cycles through the servers to ensure good load balancing (for example, RoundRobin).

Step 3 Configure a persistency rule in the load balancer so that all the clients belonging to the samemeeting are routed to the same server.

The rule must examine the HTTP persistent cookie sent by SCOPIA Desktop Clients. Thecookie has the format CONFSESSIONID = <meeting number>.

If an HTTP request arrives from the client and contains an HTTP cookie with a CONFSESSIONIDkey, this rule must route as follows:

• If the load balancer has previously routed an HTTP request with this cookie to a specificserver, it must route the new request to the same server.

• If the load balancer did not yet encounter a cookie with this value, it must route therequest to the next available server and learn this cookie.

Note Failure to correctly set the rule does not result in obvious problems. Calls connect

even if the load balancer fails to route the requests to the same server, but itreduces the efficiency of port usage. In addition, some moderation actions (such asmuting participants) may fail. We strongly recommend to verify correct routing usinga network tracing tool such as Wireshark.

Step 4 Set the aging time of the persistency rule to a high value to ensure that the load balancer

correctly routes requests during long meetings.


Configuring Multiple SCOPIA Desktop Servers as Tomcat Clusters

To implement any kind of redundancy or load balancing on SCOPIA Desktop Servers thatrequire user authentication, the underlying Tomcat Application Server of each SCOPIA DesktopServer should be configured to form a cluster. The cluster allows authenticated users to entertheir username and password only once upon joining a videoconference. Without Tomcatclusters users might have to re-enter their credentials when the load balancer routes calls toother servers in the cluster.

Note Clusters are not required in setups where all the users connect as guests.

Tomcat clustering supports the following load balancing techniques implemented by theSCOPIA Solution:

• Radware AppDirector

• Other third-party load balancers

For information on these devices, see “Configuring Multiple SCOPIA Desktop Servers” on page61.

Perform this procedure on the configuration files of each SCOPIA Desktop Server pertaining tothe cluster.

Note For backup purposes, we recommend to save a copy of the original configuration file before

editing it.

Procedure

Step 1 Enable Tomcat clustering in the SCOPIA Desktop Server.

a. Using a text editor, open the ctmx.ini file located in <install directory>\data\

b. Locate the [redundancy] section of the file.

c. Set clusteringenabled to true.

Step 2 Configure the Tomcat cluster as a simple TCP cluster with full memory replication ofsessions.

a. Using a text editor, open the server.xml file located in <install directory>\tomcat\conf\

b. Locate the line:

<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster" channelSendOptions="8">

c. Replace that line with the following code:

<Cluster className="org.apache.catalina.ha.tcp.SimpleTcpCluster" channelSendOptions="8"> <Manager className="org.apache.catalina.ha.session.DeltaManager" expireSessionsOnShutdown="false" notifyListenersOnReplication="true"/> <Channel className="org.apache.catalina.tribes.group.GroupChannel"> <Membership className="org.apache.catalina.tribes.membership.McastService" address="228.0.0.4"


port="45564" frequency="500" dropTime="3000"/> <Receiver className="org.apache.catalina.tribes.transport.nio.NioReceiver" address="auto" port="4000" autoBind="100" selectorTimeout="5000" maxThreads="6"/>

<Sender className="org.apache.catalina.tribes.transport.ReplicationTransmitter"> <Transport className="org.apache.catalina.tribes.transport.nio.PooledParallelSender"/> </Sender> <Interceptor className="org.apache.catalina.tribes.group.interceptors.TcpFailureDetector"/> <Interceptor className="org.apache.catalina.tribes.group.interceptors.MessageDispatch15Interceptor"/> </Channel> <Valve className="org.apache.catalina.ha.tcp.ReplicationValve" filter=""/> <Valve className="org.apache.catalina.ha.session.JvmRouteBinderValve"/> <Deployer className="org.apache.catalina.ha.deploy.FarmWarDeployer" tempDir="/tmp/war-temp/" deployDir="/tmp/war-deploy/" watchDir="/tmp/war-listen/" watchEnabled="false"/>

<ClusterListener className="org.apache.catalina.ha.session.JvmRouteSessionIDBinderListener"/> <ClusterListener className="org.apache.catalina.ha.session.ClusterSessionListener"/></Cluster>

d. Save and close the file.

e. Using a text editor, open the web.xml file located in \tomcat\webapps\scopia\WEB-INF\

f. Add a new line before the </webapp> line.

g. Enter <distributable/> in the line.

h. Save and close the file.

i. Open the context.xml file in \tomcat\conf\

j. Locate the line containing <Manager pathname="" />.

k. Verify that the line is commented, or delete it.

l. Save and close the file.


Step 4 (Optional) To verify whether the cluster is correctly configured on all the servers, you cancapture network traces using the Wireshark filter ip.dst filter==228.0.0.4 whichpresents the cluster's synchronization traffic (or "heartbeat").

For example, enter the filter to verify that each server in the cluster broadcasts a messageevery 0.5 seconds to the specified IP address.

Figure 9-2 Capturing network traces


Configuring Server Redirection

The load balancer might send calls to a server that cannot handle them due to a lack ofresources. To avoid call failure or call redial by a SCOPIA Desktop Client, we recommend toenable the server redirection feature which allows clients that are routed to busy servers totry connecting to another server.

The server redirection feature is commonly used in load balancer environments to maximizeresource utilization of SCOPIA Desktop Servers.

With this feature, the administrator can design any kind of redirection algorithm. Werecommend using either a daisy chain topology or a dedicated server topology, as describedbelow:

• In daisy chain topologies, each server points to the next one in line, thus forming a cycle.For example, consider a three-server deployment (servers A, B and C) where:

1. A redirects to B.

2. B redirects to C.

3. C redirects to A.

Clients attempting to connect to server A would be redirected to server B if there are noavailable resources on server A. These clients would be redirected again to C if there areno available resources on server B and so on. To prevent an infinite loop, the total numberof redirections should be limited to the total number of servers in the deployment.

• In dedicated server topologies, one server is used as the designated redirectiondestination for all the other servers. For example, consider a three-server deploymentwhere:

1. A redirects to C.

2. B redirects to C.

Clients attempting to connect to server A would be redirected to server C if there are noavailable resources on server A. Similarly, clients connecting to server B would beredirected to server C if there are no available ports on server B.

With this topology, server C is used exclusively for calls that are redirected. This maycause under-utilization on the dedicated server.

To enable the server redirection feature, perform this procedure on each SCOPIA DesktopServer in the deployment:

Before you begin

• Load balancing is done through the Radware AppDirector or another third-party loadbalancer.

• All the servers in the deployment are configured to the same security mode (http/https).

Note Server redirection fails when used in mixed security modes.


Procedure

Step 1 Locate the ctmx.ini file in <install directory>\data\

Note For backup purposes, RADVISION recommends to save a copy of the original ctmx.ini

file before editing it.

Step 2 Open the ctmx.ini file in a text editor.

Step 3 Edit the file as follows:

a. Locate the [redundancy] section of the file.

b. Set redirectenabled to true.

c. Set the redirection server’s destination by entering an address (either IP or FQDN) in theaddress line. You can specify only one redirection server. For example:

192.168.241.99

or

scopiaserver1.com

Note If you changed the default port for the SCOPIA Desktop Server, make sure to add the

new port number to the address. For example:

172.16.88.93:8080

d. Enter the maximum number of redirections in maxattempts. This number should be

consistent in all the servers across the deployment to ensure a predictable redirectionbehavior.

e. Save and close the file.


Configuring Streaming and Recording for Scalability

Currently there is no solution for recording when the SCOPIA Desktop Server is configured forscalability. Therefore recording functionality must be disabled on each SCOPIA Desktop Serverused for interactive users.

To support streaming functionality in the cluster, you can install dedicated SCOPIA DesktopServers as streaming servers, and enable streaming as a policy on all scheduled meetings andVirtual rooms. The maximum number of streaming servers is the number of SCOPIA DesktopServers deployed for interactive users.

To configure a dedicated streaming server, you can either point all interactive SCOPIA DesktopServers to the same alternate streaming server, or assign one streaming server to eachinteractive SCOPIA Desktop Server as the alternate streaming server.


Procedure

Step 1 Open the SCOPIA Desktop Server Administration Web User Interface.

Step 2 Select the Deployment section.

Step 3 Select the Streaming check box.

Step 4 Select the check box Allow watching of webcasts from an alternate SCOPIA Desktop Server

Step 5 Enter the IP address of the dedicated streaming server.

Step 6 Configure the SCOPIA Management to enable streaming for virtual rooms and scheduledmeetings. See the Administrator Guide for SCOPIA Management for further details.


This section describes how you can enhance the security of your SCOPIA Desktop deploymentby encrypting communications using the encryption keys held in certificates which areuploaded to the various deployment components.

Note Using encryption is subject to local regulation. In some countries it is restricted or limited for

usage. For more information, consult your local reseller.

There are two types of certificates which can be installed.

• Install certificates on the Conference Server to encrypt the media travelling betweenSCOPIA Desktop Clients and the SCOPIA Desktop Server. These certificates also secure allweb traffic to the SCOPIA Desktop Server, for example, when you access the server’s webadministration user interface or when a user accesses their meeting portal.

• Install certificates in the server’s keystore file, part of the Java installation, to securecommunications with SCOPIA Management and other components. Mutual authenticationrequires a certificate stored on each side of the communication line.

The details of each certificate type and their configuration are detailed in the sections below:

• Securing Web Connections and Media Traffic to SCOPIA Desktop Server ............ page 72

• Securing SCOPIA Desktop Server’s Connection to other Components ................ page 74

Securing Web Connections and Media Traffic to SCOPIA Desktop Server

This procedure explains how to secure all web traffic to the SCOPIA Desktop Server withHTTPS, including the administrator interface and user portals. This also secures the actualmedia (audio and video) of any videoconferences which take place.

The certificate which secures web traffic and videoconference media is installed in theSCOPIA Desktop Conference Server.

10 Securing Your SCOPIA Desktop Deployment

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7 Securing Your SCOPIA Desktop Deployment | 72

Note This procedure requires a signed certificate ready for the SCOPIA Desktop Server. You can

either use the certificate shipped with the server, or create your own unique certificate.

Procedure

Step 1 Select Start > All Programs > SCOPIA Desktop > Config Tool.

Step 2 Select the Enable HTTPS check box in the HTTPS tab.


Step 4 Select Add Certificate to upload an existing signed certificate.

Step 5 Stop the service SCOPIA Desktop Conference Server.

Step 6 Navigate to this location:

<SD_installation_dir>\Confsrv

where <SD_installation_dir> is the installation directory of the SCOPIA Desktop Server.

Step 7 Run the Certificate Configuration Utility by launching CertificateConfiguration.exe file.

Step 8 If the certificate is installed in the local machine's certificate store:

a. Select the Configure Certificate via Certificate Store

b. Select Select Certificate.

c. Select the certificate from the list.

Step 9 If the certificate is in PKCS12 format:

a. Select Configure Certificate via File Name.

b. Browse to the PKCS12 certificate and select it.

c. Enter the private key password for the certificate.

Step 10 Select OK.

Step 11 Verify that the certificate information is listed in the Selected Certificate pane.


Step 13 Select OK.

Step 14 Select OK.

Step 15 Start the service SCOPIA Desktop Conference Server.

Step 16 Select Restart Services.

Step 17 Change the URL in the Invitations section of the SCOPIA Desktop Administration webinterface to use the secure HTTPS protocol:

a. Log into the SCOPIA Desktop Administration web interface.

b. Select Messages and Invitations on the sidebar.

c. Select the Invitations tab.

d. In the Desktop Access section, verify all URLs have the prefix of https.


Note By default, there are two URLs present in this section.

Securing SCOPIA Desktop Server’s Connection to other Components

You can secure the management communication sent between SCOPIA Desktop Server andother components like SCOPIA Management with TLS encryption. This method also checks thedata integrity of messages.

Mutual authentication would require a certificate on each side of the connection. On SCOPIADesktop Server, use the keytool utility, which is part of the Java installation. For moreinformation about securing SCOPIA Management’s connections with other components, see theAdministration Guide for SCOPIA Management.

To open a mutually authenticated TLS connection, each server authenticates the other byexchanging certificates.

Note SCOPIA Desktop Server is shipped with a pre-created and pre-installed certificate, but its

encryption keys are non-unique.

To create certificates with unique keys for true authentication (Step 3 onwards), you mustfirst remove the pre-installed certificates held in keytool’s .keystore file, then generateand install new unique certificates.

The password on the .keystore file is radvision.

This section does not explain each of the parameters of the keytool command. For a fulldescription of this Java utility, see http://java.sun.com/j2se/1.4.2/search.html.

Procedure

Step 1 Enable the management encryption on the SCOPIA Desktop Server side:

a. Access the SCOPIA Desktop Server Administrator web user interface.

b. Select the Deployment icon on the sidebar.

c. Select the Secure connection using TLS check box in the SCOPIA Management section.

Figure 10-1 Secure Connection Check Box

d. Select OK.


Step 2 On the side of SCOPIA Management, enable the management encryption connection:

a. Login to the SCOPIA Management.

b. Select Resource Management in the sidebar.

c. Select the SCOPIA Desktop tab.

d. Select the SCOPIA Desktop Server whose communications you want to encrypt.

e. Select the check box Secure XML connection using TLS.

f. Select OK.

Step 3 Stop the SCOPIA Desktop - Apache Tomcat service.

Step 4 Copy the .keystore file located in <SD_install_dir>\data\sds.keystore to a temporaryworking folder, for example C:\cert. The keystore file holds the certificates on each server.Currently they hold the default non-unique certificates.

Step 5 Open a command line window. The keytool utility is located in <SD_install_dir>\JRE\bin.

Step 6 Use the keytool utility to remove the pre-installed certificate from the .keystore filewith the -delete parameter. The default certificate has an alias of default:

keytool -delete -alias default -keystore sds.keystore -storepassradvision

Step 7 Generate a unique key pair using an appropriate DN with the -genkeypair parameter:

keytool -genkeypair -keyalg RSA -alias sds -dname "CN=<FQDN ofserver>" -keystore sds.keystore -storepass radvision -validity 365 -keysize 1024

Step 8 Create a certificate signing request file (CSR) for the newly generated key pair using the -certreq parameter:

keytool -certreq -alias sds -keystore sds.keystore -storepassradvision -file C:\cert\certreq.csr

Step 9 Send the certificate request to a Certificate Authority.

Step 10 The CA returns the certificate signed in form of .crt file, for example signed_cert.crt. Italso returns a root certificate, root_cert.crt.

Step 11 Import the root certificate of the CA into the keystore file using the -import parameter:

keytool -import -trustcacerts -alias root -file root_cert.crt -keystore sds.keystore -storepass radvisionwhere root_cert.crt is the trusted root certificate.

The trustcacerts parameter instructs keytool to check both the specific and thesystem.keystore file for the root certificate.

Step 12 Import the signed certificate into the keystore file. Use the same alias you used in Step 8 .

keytool -import -trustcacerts -alias sds -file signed_cert.crt -keystore sds.keystore -storepass radvisionKeytool issues a confirmation message if the certificate was uploaded successfully.

Step 13 Copy the .keystore file back to its original location (see Step 4 ).

Step 14 Restart the service on each side (see Step 3 ).


Each of the following sections presents the symptoms of common problems that may occurduring the use of the SCOPIA Desktop. Recommended actions for each symptom are alsoprovided. For more information related to known issues, see the SCOPIA Desktop ReleaseNotes.

When SCOPIA Desktop is part of a multi-tenant deployment, you can view the componentconnection and communication status in a page that enables you to verify any issues perorganization located in the deployment. Once you accessed the page, select the Directorytab, enter the cursor into the dropdown list and select the organization whose policies youwant to check.

These topics include:

• Preserving SCOPIA Desktop Presence Server Configuration ........................... page 76

• Viewing Status of Servers and Directory ................................................. page 77

• Recording Does not Start Automatically ................................................. page 84

• Synchronizing SCOPIA Desktop Server with SCOPIA Management .................... page 84

• Updating the IP Address on the Recording or Streaming Server ...................... page 85

• Changing the IP Address of the SCOPIA Desktop Server ............................... page 85

• Client -734 Error and other Certificate Problems ...................................... page 86

• Upgrading SCOPIA Desktop Server Recordings .......................................... page 87

• Enabling a User to Sign In ................................................................. page 87

• Troubleshooting SCOPIA Mobile ........................................................... page 88

Preserving SCOPIA Desktop Presence Server Configuration

Perform the procedure described in this section to preserve the SCOPIA Desktop PresenceServer configuration to solve the issue.

11 Troubleshooting Common Issues

RADVISION | Administrator Guide for SCOPIA Desktop Server Version 7.7 Troubleshooting Common Issues | 76

Procedure

Step 1 Backup the current Presence Server configuration:

a. Save the ejabberd.cfg file at the ...\Jabber\conf location into a different location.

b. Save any folders under the ...\Jabber\database folder into a different location.

Step 2 Navigate to the ...\Jabber\install location and double-click the ejabberd-2.0.3-windows-installer.exe file.

The Installation wizard opens.

Step 3 Modify the installation directory in the Installation Directory window to be C:\Program Files\Radvision\SCOPIA Desktop\Jabber, and then select Next.

Step 4 Leave the default domain in the ejabberd server domain window, and then select Next.

The default domain is changed either via the Jabber Config tool or by replacing theejabberd.cfg file after installation, and then select Next.

Step 5 Leave the default admin name in the Administrator user name window, and then select Next.

Step 6 Enter the administrator password and re-enter it for confirmation in the Administratorpassword window, and then select Next.

Step 7 Select the required option in the Cluster window, and then select Next.

Step 8 After the installation is complete, perform this:

• Restore the database and ejabberd.cfg file.

• Set the service to automatic.

Viewing Status of Servers and Directory

Viewing the status of your SCOPIA Desktop deployment is a helpful way to assess resourceavailability and troubleshoot connectivity problems. The following sections provide usefulinformation for utilizing the View Status functionality of SCOPIA Desktop.

• Viewing Server Status and Port Resource Usage ........................................ page 77

• Viewing Directory Status .................................................................. page 80

• Viewing Recording Server Status ......................................................... page 82

• Viewing Content Slider Status ............................................................ page 83

Viewing Server Status and Port Resource Usage

The SCOPIA Desktop Status tab displays status information about the SCOPIA Desktop Serverand other servers with which it interacts:

• Gatekeeper—RADVISION ECS Server.

• Streaming—SCOPIA Desktop Server. This information appears only if the SCOPIA DesktopServer is configured to manage streaming.

• SCOPIA MCU—MCU. This information is displayed only for basic deployments.


• SCOPIA Management—SCOPIA Management. This information is displayed only for point-to-point and advanced deployments.

• Sametime Server—Sametime Community Server. This information appears if the SCOPIADesktop Server is configured to work with IBM Lotus Sametime Web.

Figure 11-1 Component Status

The indicator next to each link shows whether or not the connection to the target server orregistration with the Gatekeeper is successful. When the indicator is red, a tooltip containingerror details is available. Click the red indicator to view further error information.

The SCOPIA Desktop Status tab also shows port usage statistics and presents port usagegraphically.

Figure 11-2 Port Status Graph

Depending on your needs you may choose one of the graph reports described in Table 11-1 onpage 79.

Note We recommend that you wait five minutes after you run the SCOPIA Desktop Server before

you refresh the SCOPIA Desktop Status tab to acquire the updated port information.


Table 11-1 Graph Views Content

Graph Report Data CollectionFrequency

Number of DataPoints Collected

Source

one hour one minute 60 SCOPIA Desktop

6 hours four minutes 90 Four data points fromone hour report

24 hours 20 minutes 72 Five data points from6 hour report

7 days 120 minutes 84 Six data points from24 hour report

30 days 12 hours 60 Six data points from 7day report

Depending on the deployment the SCOPIA Desktop Status tab also displays additionalstatistics:

• For deployment without SCOPIA Management

– Number of participants in group calls

– Number of streaming ports

• For deployments with enabled point-to-point-only functionality

– Number of relayed point-to-point calls

• For advanced deployments

– Number of total live ports

– Number of relayed point-to-point calls

– Number of participants in group calls

– Number of streaming ports


Sometimes point-to-point and group calls may exceed the allowed port limit because the limitis enforced at connecting time. If this happens, number of connected ports appears in red andthe “Usage has exceeded the maximum allocated resources” warning is displayed.

If you set the call limit to a number lower than defined by the license, an error message isdisplayed next to the number of participants in group calls.

Viewing Directory Status

In deployments where SCOPIA Desktop is configured to work with SCOPIA Management, SCOPIADesktop Server must synchronize with SCOPIA Management to download information aboutusers, virtual rooms, and global policy. SCOPIA Desktop Server synchronizes with SCOPIAManagement when it connects to it for the first time; then SCOPIA Management updatesSCOPIA Desktop Server each time there is new or modified information. These are thefollowing synchronization states:

• Synchronized—SCOPIA Desktop Server is synchronized with SCOPIA Management.

• Synchronizing—SCOPIA Desktop Server is caching information from SCOPIA Management.Users cannot search for users and terminals in the contact list or in the Invite dialog box.

• Not Synchronized—SCOPIA Desktop Server functions using locally cached information.TheSCOPIA Desktop functionality is not influenced except one feature: standard login is notavailable. In deployments where the Integrated Windows Authentication is enabled, userscan still log in using Single Sign-On.

• Synchronization error—SCOPIA Desktop Server is not synchronized with SCOPIAManagement, no information is cached. The SCOPIA Desktop functionality is reduced.

Select Status > Directory Status to display an organization’s directory information. All thesettings in this screen are configured in SCOPIA Management.


Figure 11-3 on page 81 illustrates the directory status of a company pertaining to a singletenant deployment.

Figure 11-3 Viewing the directory status of an organization pertaining to asingle tenant deployment

Figure 11-4 on page 81 shows the directory status of an organization pertaining to a multi-tenant deployment. Scroll the dropdown list in the Organization field to select theorganization whose directory you need to check.

Figure 11-4 Viewing the directory status of a company pertaining to multi-tenant deployment

You can also view the maximum call rate value. This setting is configured in SCOPIAManagement.

Figure 11-5 Viewing the maximum call rate policy


Viewing Recording Server Status

You can view the Recording Server Status information only if recording is enabled in yourdeployment.

The Recording Status tab displays this information:

• Recording Components:

Figure 11-6 Recording Components Status

– Recording Server—Displays the address of the SCOPIA Desktop Recording Server.

– Recorder—Displays the connection status between the SCOPIA Desktop RecordingServer and the SCOPIA Desktop Conference Server.

– Gatekeeper—Displays the address of the gatekeeper to which the Conference Server isregistered. In the special case that the SCOPIA Desktop Recording Server is installedseparately from the SCOPIA Desktop Server and has its own Conference Server, theConference Server must be registered to the same gatekeeper as the SCOPIA DesktopServer.

– NIC Address—Displays the NIC address used by the SCOPIA Desktop Recording Server tocommunicate with MCU.

• Recording Server Information:

Figure 11-7 Recording Server Information

– Recordings Folder—Displays the location of the folder on the SCOPIA DesktopRecording Server used for storing recordings.

– Remaining Disk Space—Shows how much space is remaining on the disk on whichrecordings are stored.

If the remaining disk space is less than the disk space allocated for recordings, awarning icon is displayed. Click the icon for details.

• Storage Capacity—Shows the amount of disk space used by all recordings.


Figure 11-8 Storage Capacity Status

The maximum value is configured during installation.To change the maximum disk space,run the installer on the SCOPIA Desktop Recording Server in the modification mode.

• Recording Ports:

Figure 11-9 Port Usage Status

– In Use—Shows the number of recordings being recorded at the present moment. Themaximum value appears as specified in the recording license installed for this SCOPIADesktop.

– Licensed—Shows the number of recording ports defined by the license.

• Available Recordings:

Figure 11-10 Available Recordings Status

– Completed—Shows the total number of completed recordings available for watching.

– Reconstructed—Shows the number of reconstructed recordings.

SCOPIA Desktop saves actual recordings and recording attributes in different folders. Ifa user restores only a recording without restoring its attributes, the recording appearsas reconstructed. In this case you need to manually define recording attributes, suchas the name and the owner PIN, to finalize reconstruction of a recording. After thereconstruction is completed, the recording appears on Watch Recording page of theSCOPIA Desktop portal. If recording attributes are not reconstructed, the yellowattention icon is displayed. Click the icon for more information.

Select Status > Recording Status to access Recording Server information.

Viewing Content Slider Status

You can view the Content Server status information only if recording is enabled in yourdeployment.


The Content Slider Status tab displays this information:

Figure 11-11 Content Slider Status

• Recording Server Status:

– Recording Server—Displays the address of the SCOPIA Desktop Recording Server.

– Sessions—All slider sessions currently in progress, with details on the server(s) thathave sessions.

Problems—If there are problems with slider sessions, they appear (per server) in theproblems column. To view details, select the link in the Problems column: Resultsshow the date/time of the problem and a brief summary of the problem details.

Recording Does not Start Automatically

Problem SCOPIA Management configured to work with the SCOPIA Desktop Server does not recordvirtual room meetings or scheduled meetings automatically, even though SCOPIAManagement is configured to do so.

Solution Verify that one of these problems does not interfere with recording:

• There are not enough available recording ports on the SCOPIA Desktop at the time whenthe meeting is scheduled.

• There are not enough available recording ports on the SCOPIA Desktop at the time whenthe meeting is scheduled.

• The maximum number of simultaneous recordings is reached.

Synchronizing SCOPIA Desktop Server with SCOPIA Management

Problem The Directory Status - SCOPIA Management tab displays the synchronization error.

Solution Perform the procedure.

Procedure

Step 1 Select the link on the Directory Status - SCOPIA Management tab.

The Directory tab opens.

Step 2 Select the Synchronize button.


Figure 11-12 SCOPIA Management Synchronization

Updating the IP Address on the Recording or Streaming Server

Problem The SCOPIA Desktop Status tab indicates that the Streaming or Recording Server is notconnected. If you select the Streaming Server indicator, this error is displayed: “5003 Accessdenied error from proxy”.

Solution When the Streaming or Recording components of SCOPIA Desktop are installed on their ownserver, separately from the SCOPIA Desktop Server, they are configured with the IP address ofthe SCOPIA Desktop Server which is allowed to connect to them. If the IP address of theSCOPIA Desktop Server changes, you need to update it on the Streaming and RecordingServers.

Procedure

Step 1 From the Start menu, select Programs > SCOPIA Desktop > ConfigTool.

Step 2 Select the Content Center tab.

Step 3 Click the Add button and enter the new IP address of the SCOPIA Desktop Server.

Step 4 Select the old IP address of SCOPIA Desktop Server, and click the Remove button to remove itfrom the list.

Changing the IP Address of the SCOPIA Desktop Server

Problem The SCOPIA Desktop Status tab indicates that the SCOPIA Desktop Server is not connected.

Solution If the IP address of the server on which the SCOPIA Desktop Server is installed changes, youneed to update SCOPIA Desktop Server components with its new IP address.

Procedure

Step 1 Select Start > Settings > Control Panel.

Step 2 Double-click Add or Remove Programs.

Step 3 From the list of programs, choose SCOPIA Desktop, and then Change.

The Setup Wizard opens.

Step 4 In the Welcome screen select Next.

Step 5 In the Program Maintenance screen, choose Modify, and select Next.

Step 6 In the Custom Setup screen, select Next.


Step 7 In the SCOPIA Desktop Serial Key screen, select Next.

Step 8 In the SCOPIA Desktop Network Configuration screen, select Next.

Step 9 In the SCOPIA Desktop Hostname Configuration screen, select Next.

Step 10 In the SCOPIA Desktop Recording Configuration screen, select Next.

Step 11 Select Install.

Client -734 Error and other Certificate Problems

Problem The client issues a -734 error, and the client call log states:

get_verify_result error = 19, the peer certificate is invalid.

In cases of an incorrect SCOPIA Desktop Server certificate setting, the SCOPIA Desktop Clientreturns errors 21 or 26.

Possible Causes The SCOPIA Desktop Client is attempting to connect to the SCOPIA Desktop Server when theconnection is encrypted but the server’s certificate is signed by an unknown (untrusted) CA.

Solution Install the root CA certificate on the SCOPIA Desktop Client computer using the standardMicrosoft Management Console.

Procedure

Step 1 Obtain the root certificate of the CA used to sign the certificate on the Conference Server.

Step 2 Launch the Microsoft Management Console.

Step 3 Select File > Add/Remove Snap-in.

Step 4 Select Add.

Step 5 Select Certificates, and then select Add.

Step 6 Select Computer Account in the Certificates snap-in window, and then select Next.

Step 7 Select Local computer (the computer this console is running on), and then select Finish.

Step 8 Select Close and OK.

Step 9 Verify that the console shows the Certificates (Local Computer) in the main consolewindow’s left hand pane.

Step 10 Expand the entry Certificates (Local Computer) and navigate to Certificates (LocalComputer) > Trusted Root Certification Authorities > Certificates.

Step 11 Right-click Certificates and select All Tasks > Import.

Step 12 Select Next.

Step 13 Select Browse, and select the signed certificate file you want to upload.

By default the file type in the browse window is set to show only X.509 Certificates. Changethis to Personal Information Exchange (*.pfx;*.p12) or All Files (*.*), and select Next.

Step 14 Select Place all certificates in the following store, and then verify that the Certificatestore: Trusted Root Certification Authorities option is selected.

Step 15 Select Next.


Step 16 Verify the information and select Finish.

Step 17 Verify that the Certificate Chain is located in the Trust Root Certification Authorities store.

Upgrading SCOPIA Desktop Server Recordings

If there are recordings created using SCOPIA Desktop Server version 5.x, upgrade them byperforming these steps:

Note You can upgrade recordings at any time.

Procedure

Step 1 Install QuickTime version 7.6.2 or higher. You can download QuickTime athttp://www.apple.com/quicktime/download/.

Step 2 On the SCOPIA Desktop Server, navigate to the <INSTALLDIR>\config location.

Step 3 Double-click the recording_converter.exe file.

Step 4 Follow the on-screen instructions. Depending of the size and amount of recordings, theupgrade may take time.

Step 5 The recordings are converted and the log files are created in this folder.

Step 6 Verify that the recordings are converted correctly.

Step 7 Delete backed up recordings.

Enabling a User to Sign In

Problem A user cannot sign in.

Solution Verify that the following problems do not interfere with user signing in:

• Authentication is turned off on SCOPIA Management. In the SCOPIA Desktop Administratorweb user interface, select Status in the sidebar, and then select the Directory Statustab. Verify that authentication is enabled.


Figure 11-13 General User Policies

• This particular user does not have a SCOPIA Desktop Pro license.

• If SCOPIA Desktop is enabled for Integrated Windows Authentication and the user doesnot use a valid proxy account. In the SCOPIA Desktop Administrator web user interface,select Directory and Authentication in the sidebar, check the proxy account configuredin the Integrated Windows Authentication area.

Figure 11-14 Proxy Account Settings

• If SCOPIA Desktop is not enabled for Integrated Windows Authentication and uses SCOPIAManagement to authenticate, select Status in the sidebar and verify that SCOPIA DesktopServer is connected to SCOPIA Management.

Figure 11-15 SCOPIA Desktop and SCOPIA Management Connectivity

Troubleshooting SCOPIA Mobile

If SCOPIA Mobile stops running (or crashes), a crash report is generated and copied to thecomputer the next time the device is synchronized with iTunes.

Two files are generated for each crash: .crash and .plist. You can find them in these locations,depending on the computer you are using:

• In a MAC device, look for the files in~/Library/Logs/CrashReporter/MobileDevice/<DEVICE_NAME>\SCOPIAMobile*


• In a PC using Windows Vista/Windows 7, look for the files in C:\Users\<USERNAME>\AppData\Roaming\Apple Computer\Logs\CrashReporter\MobileDevice\<DEVICE_NAME>\SCOPIAMobile*

• In a PC using Windows XP, look for the files in C:\Documents and Settings\<USERNAME>\Application Data\Apple Computer\Logs\CrashReporter\MobileDevice\<DEVICE_NAME>\SCOPIAMobile*


www.radvision.com

About RADVISIONRADVISION (NASDAQ: RVSN) is the industry’s leading provider of market-proven products and technologies for unifiedvisual communications over IP and 3G networks. With its complete set of standards based video networkinginfrastructure and developer toolkits for voice, video, data and wireless communications, RADVISION is driving theunified communications evolution by combining the power of video, voice, data and wireless – for high definition videoconferencing systems, innovative converged mobile services, and highly scalable video-enabled desktop platforms onIP, 3G and emerging next generation networks. For more information about RADVISION, visit www.radvision.com

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]

This document is not part of a contract or license as may be expressly agreed. RADVISION is a registeredtrademark of RADVISION, Ltd. All product and company names herein may be trademarks of their registeredowners. All rights reserved © 2012 RADVISION, Ltd.

Date post:	01-Dec-2015
Category:	Documents
Upload:	hai-ninh-van
View:	235 times
Download:	7 times