Release Notes for Avaya Scopia Management Suite

Transcription

1 Release Notes for Avaya Scopia Management Suite Version 8.3 FP1 For Solution 8.3 Dec 2014

2 Avaya Inc. All intellectual property rights in this publication are owned by Avaya Inc. and are protected by United States copyright laws, other applicable copyright laws and international treaty provisions. Avaya Inc. retains all rights not expressly granted. All product and company names herein may be trademarks of their registered owners. This publication is AVAYA Confidential & Proprietary. Use pursuant to your signed agreement or Avaya policy. No part of this publication may be reproduced in any form whatsoever or used to make any derivative work without prior written approval by Avaya Inc. No representation of warranties for fitness for any purpose other than what is specifically mentioned in this guide is made either by Avaya Inc. or its agents. Avaya Inc. reserves the right to revise this publication and make changes without obligation to notify any person of such revisions or changes. Avaya Inc may make improvements or changes in the product(s) and/or the program(s) described in this documentation at any time. If there is any software on removable media described in this publication, it is furnished under a license agreement included with the product as a separate document. If you are unable to locate a copy, please contact Avaya Inc and a copy will be provided to you. Unless otherwise indicated, Avaya registered trademarks are registered in the United States and other territories. All registered trademarks recognized. For further information contact Avaya or your local distributor or reseller. Release Notes for Avaya Scopia Management Version 8.3 FP1, December,

3 Table of Contents What s New... 3 New Features... 4 Integrating with Other Components... 4 Upgrading to this Release... 5 ECS Gatekeeper Security Considerations... 5 ECS Deployment Tips... 5 Resolved Issues Scopia Management... 6 Known Issues Scopia Management... 8 Known Issues ECS Gatekeeper...10 What s New This document contains late breaking or other information that supplements these components: Avaya Scopia Management for Enterprise Deployments Avaya Scopia Management for Service Provider Deployments Avaya Scopia ECS Gatekeeper

4 The components included in this release have the following software version: Component Version Scopia Management Scopia Gatekeeper SIP B2BUA New Features Supports VaaS 2.0 manual billing process. The virtual room peak usage data is sent monthly by to Avaya Business Operatiors on the 1 st day of every month. CSV reports about tenants VMR usage. Administrators can generate a CSV report that includes the tenant ID and the maximum number of provisioned VMRs during a given period. Integrating with Other Components Scopia Management version 8.3 FP1 is compatible with the following product versions: Component Version Scopia Elite Scopia Elite Scopia Desktop Server Scopia Mobile 8.3 Scopia XT5000/4200/XTE Scopia XT X Scopia VC240 2.X RADVISION SIP Gateway 7.7 Scopia TIP Gateway 8.0 Scopia Video Gateway Scopia MCU Release Notes for Avaya Scopia Management Suite Integrating with Other Components 4

5 Scopia Gateway Scopia Enhanced Communication Server (ECS) 8.3 Scopia PathFinder Not available in the Scopia for Aura Collaboration Suite Edition Upgrading to this Release The Scopia Management version 8.3 FP1 installer supports a fresh installation. It also supports upgrading from Scopia Management version or To upgrade from Scopia Management, follow these steps: Step 1: Back up Scopia Management as described in the Backup and Restore Procedures chapter of the Installation Guide for Avaya Scopia Management. Step 2: Step 3: Review the Known Issues section in this document. Run the executable installation files. Important For upgrading from Scopia Management version 8.3 or 8.3 SP1 with internal database (PostgreSQL) and redundancy case, upgrade the slave server first and then upgrade the master server. Do not upgrade the master server first or upgrade two servers at the same time. ECS Gatekeeper Security Considerations To ensure your ECS is secure from outside infiltration, we recommend modifying the following default settings: ECS username and password. SNMP Service Community parameters. To access these parameters in Windows Server 2003 or 2008, go to Start > Settings > Control Panel > Administrative Tools > Services > SNMP Service. Right click Properties and select the Security tab. Default port value of the web server. This can be modified at the webserverport line in the webs.ini file. For more information, see the Reference Guide for Port Security Version ECS Deployment Tips When using Alternate ECS, both the main and alternate ECS servers must be connected on the same physical network segment (on same leg of the router). When prefix stripping is disabled, endpoints can register with the ECS by using only a number that begins with the zone prefix. Release Notes for Avaya Scopia Management Suite Upgrading to this Release 5

6 When predefining an endpoint in ECS, new services are allowed by default. To decline an endpoint to use a service, you must decline the service in the Predefined Endpoint Properties dialog box in the Endpoints tab. The search function in the Endpoints tab is casesensitive. To hide the Product Family Entry Point interface when accessing ECS, modify the homepage line in the webs.ini file from admin/net/default.asp to admin/gk/default.asp. forwarding/fallback rules are casesensitive. Verify that the latest Java applet version is installed in the client accessing the ECS. Resolved Issues Scopia Management Table 1: Case Number RVSM3040 List of resolved issues in this version Description of issue Fixed an issue where the system did not add the IVR Number record to the internal ECS when the auto attendant number was greater than Added "Extend Meeting" and "Reconnect Call" for ongoing p2p meetings Shows "start failed" meeting in the ongoing meeting list. Added a property to show a meeting PIN as clear text in Scopia management meeting information. By default, the meeting PIN displays as asterisks. To see it as clear text, set the following advanced parameter property: context.inmeetingctrl.displaymeeingpin=true Supports UsertoUser information transportation via SIP in VTM projects. Fixed an issue where the calls were incorrectly disconnected by Scopia Management due to a timing issue. Fixed an issue where the user information page incorrectly displayed a message that the user has full administrator access permission even when the user s user profile has "read only" admin portal rights. Fixed an issue where the no selfsee feature did not work if the MCU service was set to static layout. Fixed an issue that the current meeting list did not display all meetings where there were multiple pages in the admin portal meeting list. Fixed an issue that when making an IP call to an endpoint, Scopia Management confirmed the call to the endpoint IP with port number 0 (xxx.xxx.xxx.xxx:0), rather than the original destination CSIP. Fixed an issue where an ISDN endpoint s name is displayed as "Gateway CallId #xxxx", instead of displaying the preset name. Fixed an issue where the Scopia Management multitenant version updated the Scopia Pro license, but the Mobile license failed due to the license s version type mismatch (the licenses generated from PLDS are only for enterprise). Fixed an issue where Scopia Management incorrectly played the audio prompt as first participant when Scopia Desktop client joined the slave meeting. Fixed an issue that the meeting size always displayed as 0 in Scopia Management meeting reports. Changed the windows service display name from RADVISION Scopia Management to AVAYA Scopia Management ; Changed the SIP server windows service display name from RADVISION SipServer to AVAYA SipServer. Fixed an issue that endpoints which are imported from gatekeepers are not Release Notes for Avaya Scopia Management Suite Resolved Issues Scopia Management 6

7 Case Number Description of issue visible in the schedule meeting endpoints list. RVSM3006 Fixed an issue that duplicated participants display in the Scopia Desktop client roster Fixed a few incorrect Korean translations in meeting control. Fixed the following issues in Scopia management Outlook addin: The new message that warns users about Save & close/red cross: «If you save the meeting without sending, the parameters of the video meeting will be lost» was only in English. The warning message incorrectly appeared when updating your meeting (for example, doubleclicking it in the calendar, changing the schedule or participants and then clicking update). Some files were not translated correctly in certain languages, such as French and German: the text chains were too long (for example Code du moderator ); some question marks were displayed instead of text. RVSM3164 Fixed an issue where Scopia Management sent duplicate mail notifications when meetings were scheduled from the Microsoft Exchange Server addin. Release Notes for Avaya Scopia Management Suite Resolved Issues Scopia Management 7

8 Known Issues Scopia Management Table 2: Case Number This section details the list of limitations and issues that remain unresolved in this version. List of known issues for this version. Description of issue Users with Japanese & Korean characters in their login IDs cannot login to Scopia Management. When working with Internet Explorer 10 or 11, we recommend adding the Scopia Management URL as well as the Google Maps URLs as trusted sites. Refer to topic#trusted for detailed instructions. When a meeting has more than 300 participants, we recommend using a PC with a strong CPU and extra memory to operate the inmeeting control. The Scopia TIP Gateway or Scopia Gateway for Microsoft Lync services prefix must not conflict with the MCU service prefix. Scopia Management does not detect this conflict. For a deployment with an external database, Scopia Management does not automatically backup the database, so the administrator must backup the database manually when creating a backup point. You cannot move a participant from one meeting to another for the following endpoints: Telepresence endpoints Scopia Desktop clients Lync clients Scopia Management version 8.3 Outlook Addin has the following limitations: The user must have administrator privileges on the local machine to install the Addin. The Addin does not support Outlook The new Outlook plugin needs to connect to the Scopia Management server to work, so users outside of the office must be on a VPN. The Outlook Addin has dependencies on the following components: Windows installer 3.1 or higher. Microsoft.Net framework 4.0 or higher. (It is downloaded and installed automatically). Microsoft office 2010 runtime tool. (It is downloaded and installed automatically). The iview 7.7 Outlook Addin is disabled automatically when you install the version 8.3 Addin. Installing a redundant deployment on the Microsoft 2008 operating system requires WinPcap. You can download WinPcap from For upgrading from Scopia Management version 8.3 and internal database (PostgreSQL) and the redundancy case, follow this procedure: Step 1 Back up Scopia Management as described in the Backup and Restore Procedures chapter of the Installation Guide. Step 2 Upgrade the slave Scopia Management server first. Step 3 After the slave Scopia Management upgrade is completed, upgrade the Master Scopia Management server. Follow this backup/restore procedure for redundancy with internal database (PostgreSQL) deployment: Step 1 Make sure that the Backup or restore is only on the Master Scopia Management server. Step 2 Before starting the restore procedure, stop the standby Scopia Management service. Step 3 After the restore procedure is completed on the Master server, the Master server restarts automatically. Step 4 After the Master server restarts completely, start the standby server. The restored configuration files and database are automatically synchronized to the standby server. Release Notes for Avaya Scopia Management Suite Known Issues Scopia Management 8

9 Auto backup limitation If Scopia Management is installed on Windows 2008 or 2012, Scopia Management can save backup files on the local machine or network path. But if Scopia Management is installed on Windows 2003, Scopia Management can only save the backup files on the local machine. The administrator portal supports the following languages: English, French, Simplified Chinese and Japanese. But some events/alarms messages remain in English because they come from other devices / endpoints. In certain cases the displayed number of registered endpoints in the system menu is inaccurate. Click on the Refresh button to display the right number. After adding a new virtual room, the user needs to relogin to use it to schedule a new meeting. Recurrent meetings scheduled from the Microsoft Exchange server Addin, cannot be modified from Outlook Web This is a Microsoft Web Outlook 2013 bug. For the Microsoft Exchange Server plugin installation, we have different installers for the different major released versions of the Exchange Server. The following Exchange Server versions are supported: Exchange Server 2010 Service Pack 3 (SP3) (UR5, UR6) Exchange Server 2013 Service Pack 1 (SP1) (CU4) Exchange upgrade: For minor Exchange Server version upgrades, if, for example, you already installed the plugin on Exchange Server 2013 (SP1, CU3) and then upgraded to a minor version like 2013 (SP1, CU4), the server plugin continues to work. For a major Exchange version upgrade, for example, from Exchange Server 2010 to Exchange Server 2013, you need to reinstall the server plugin after the upgrade. For Scopia Classic MCU manually cascading with Scopia Elite MCU, the Scopia solution version 8.3 only supports the simple cascading mode. The Scopia Classic MCU is not supported if Scopia Management works in VaaS license mode. Release Notes for Avaya Scopia Management Suite Known Issues Scopia Management 9

10 Known Issues ECS Gatekeeper This section details the list of limitations and issues that remain unresolved in this version. Table 3: List of known issues for this version Case Number Description of issue If you get a java is out of date error message after logging in to the ECS standalone administrative interface, we recommend following the steps below: 1. Update to the latest version of Java from 2. After updating, open the Java Control Panel, Security tab and add the ECS URL as an exception. Interoperability issues with ECS: H.245 channels are not connected when a Cisco (Tandberg) Codian MCU calls via ECS. Video IVR does not function properly with LifeSize endpoints running version 4.0 and below. Upgrading the LifeSize endpoints to a later version resolves the issue. Video may not display correctly when calling a SCOPIA MCU from an external Cisco Endpoint. On rare occasions the ECS service might fail to start (Error 1053). To recover, execute the following actions: Stop the SNMP service Start the ECS service Start the SNMP service On rare occasions the ECS service is stopped when retrieving the ECS CsPackage. This situation occurs only in Windows Line hunting fails when two or more gateways are registered to the ECS, and one of the gateways returns a destinationrejection reason in the Release Complete message. In such cases, the ECS attempts to connect calls only via the gateway which returns the Release Complete message and ignores other registered gateways. The gkalternoredundancy SNMP trap is cleared and resent approximately every 30 seconds if the master and slave gatekeeper licenses allow different capacities. You must reboot your computer after performing these settings: Adding or modifying an IP address Binding to a specific IP address Modifying the NIC definition in the ECS Note: The operating system does not provide a prompt before rebooting in this case You cannot view log files via the FTP server when working with Windows Solve this problem by enabling an anonymous user in the IIS settings. When using predefined endpoints: After changing the DHCP mode setting, you must redefine the endpoints. If you change the setting of the DHCP environment in the zone checkbox in the Basics section of the Settings tab after defining the endpoints, the endpoints do not register successfully. Predefined endpoints fail to register when the ECS working mode changes from Release Notes for Avaya Scopia Management Suite Known Issues ECS Gatekeeper 10

11 DHCP to nondhcp mode and vice versa. Note: DHCP mode in the ECS is different from the TCP/IP DHCP mode. ECS DHCP is a mode of operation in which the ECS can accept more than one registration from the same IP address. To enable this mode, select the DHCP checkbox. Changing the default ECS installation port (port 80) causes incorrect operation of the web interface for the Product Family Entry Point. Forwarding fails when working with endpoints that support encryption in H.245 routed mode. Forwarding fails when fast start is used. When a neighbor gatekeeper has two zone prefixes, the gatekeeper check boxes appear unchecked when you reedit interzone rules. Release Notes for Avaya Scopia Management Suite Known Issues ECS Gatekeeper 11