Release Notes for Avaya Scopia Management Suite

Transcription

1 Release Notes for Avaya Scopia Management Suite Version July, 2017 Issue 2

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.9, July

3 Table of Contents General... 3 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... 6 Known Issues ECS Gatekeeper... 8 General 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 Management for Aura Collaboration Suite Avaya Scopia ECS Gatekeeper

4 The components included in this release have the following software version: Component Version Scopia Management Scopia Gatekeeper Integrating with Other Components Scopia Management version is part of Scopia Solution and compatible with the following product versions: Component Version Scopia Elite Scopia Elite Scopia Desktop Server Scopia Mobile Scopia XT7100/5000/4200/4300/XTE Scopia XT1000 / XT Scopia VC Scopia TIP Gateway 8.0 Scopia Video Gateway 7.7 Scopia MCU Scopia Gateway Scopia Enhanced Communication Server (ECS) Scopia PathFinder Scopia Streaming & Recording Web Collaboration Server Release Notes for Avaya Scopia Management Suite Integrating with Other Components 4

5 Upgrading to this Release The Scopia Management version installer supports a fresh installation. It also supports upgrading from Scopia Management version and To upgrade from Scopia Management, follow these steps: Step 1: Backup 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 To upgrade from previous versions of Scopia Management with internal database (PostgreSQL) and redundancy case, upgrade the slave server first. After upgrading the slave server, login to Scopia Management Dashboard to check the database replication status (in the redundancy popup window). If the replication status is not replicating (for example, Waiting or Syncing ), it means that the database is not ready, then wait for a few minutes until the replication status is replicating, and finally 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 2008/2012, 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. 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. 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 Release Notes for Avaya Scopia Management Suite Upgrading to this Release 5

6 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: List of resolved issues in this version Case Number Description of issue Upload Branding Image failure Presentation Frame Rate Issues Two extra black frame (extra participant) gets shown when cascading three Elite5110 RVSM8158 Wrong WCS server allocated for new SIP calls or when meeting extended RVSM8398 Scopia P3S3 Cascading User on Master MCU cannot see the video of user on Slave MCU and vice versa. 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 PC (Memory is 4 G or higher and the CPU pass mark should be higher than 6000) to operate the conference 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 & Mobile clients Lync clients Scopia Management version 8.3.x Outlook Addin has the following limitations: The Addin does not support Outlook The Outlook Addin has dependencies on the following components: Windows installer 3.1 or higher. Microsoft.Net framework 4.0 or higher. Microsoft Visual Studio 2010 Tools for Office Runtime. Note: The Microsoft.Net framework and Microsoft office 2010 runtime tool can be Release Notes for Avaya Scopia Management Suite Resolved Issues Scopia Management 6

7 downloaded and installed automatically when install outlook addin. If the outlook addin couldn t work after install, it usually caused by security restriction or antivirus software on your system that prevented the setup program from downloading the required programs from the Microsoft website. The workaround is to download and install them manually. Windows Installer 3.1: Framework 4.5: Virtual studio 2010 tools: Installing a redundant deployment on the Microsoft 2008 operating system requires WinPcap. You can download WinPcap from 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. The administrator portal supports the following languages: English, French, Simplified Chinese and Japanese. But some event/alarm messages, coming from other devices/endpoints, remain in English. After adding a new virtual room, the user needs to relogin to use it to schedule a new meeting. For recurrent meetings scheduled from the Microsoft Exchange server Addin, the start time of a single occurrence cannot be modified from Outlook. 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) (Rollup 9) Exchange Server 2013 Service Pack 1 (SP1) (CU8) 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. The Scopia Classic MCU is not supported if Scopia Management works in VaaS license mode. For Dual NIC case only, if there are two or more IP addresses configured on the Scopia Management server, please configure which IP address is working for the SIP server. C:\Program Files (x86)\radvision\sipserverapp\conf\updatedsipconfig.xml change <Network> as below <Network> <LocalTcpAddressList>Correct iview server IP:5060</LocalTcpAddressList> <LocalUdpAddressList> Correct iview server IP:5060</LocalUdpAddressList> <LocalTlsAddressList> Correct iview server IP:5061</LocalTlsAddressList> <B2bFQDN> iview server IP or fqdn </B2bFQDN> </Network> then restart Avaya SIP server service. Release Notes for Avaya Scopia Management Suite Known Issues Scopia Management 7

8 After install Scopia Management, the Scopia Management installer changes the dynamic port range as below to avoid the dynamic ports conflict for Scopia components. If the following dynamic ports range setting does not fit for your network or firewall setting, you can use the command Netsh int ipv4 set dynamicport tcp start=1052 num=3974 (the 1052 and 3974 are just example) to change the dynamic port range setting after install Scopia Management. Protocol TCP Dynamic Port Range Start Port : Number of Ports : If Windows security group policy is configured on the server, it might cause Scopia Management install process stuck because the Windows security group policy might block the install process to configure PostgreSQL database service. The following workaround is available to complete the install process: If Scopia Management install process gets stuck for more than 5 minutes when installing PostgreSQL, open the windows Task manager, find the process installpolicy.exe, kill it, and then Scopia Management install process will continue. When a room system is trying to virtually knock on a locked meeting, the room system appears in Scopia Desktop client roster list before the meeting moderator allows the room system joining. For Aura Collaboration edition only, if Scopia Management is upgraded from the previous version, by default no users have permission to start recording via Scopia Desktop clients as previous Scopia Management Aura Collaboration editions do not support recording functionality at all. If ASSR is purchased and added to the deployment, the workaround is to login the Scopia Desktop server administration portal to trigger a user synchronization. Maximum Length of Meeting Extension in Settings > Meetings > Policies is applicable to all meetings including P2P meeting. Knock on the Door feature is not supported on Elite 5K, but there is one exceptional case: Scopia Desktop and Mobile clients can join locked meetings on Elite 5K when Knock on the Door feature is enabled. Local redundancy may not work in nonenglish windows platform. Known Issues ECS Gatekeeper Table 3: This section details the list of limitations and issues that remain unresolved in this version. 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 Release Notes for Avaya Scopia Management Suite Known Issues ECS Gatekeeper 8

9 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, follow these steps: 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 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. If you select only predefined endpoints can register ECS then you need to predefine each Conference Point of the Avaya Streaming & Recording Server registers in ECS's GUI, Release Notes for Avaya Scopia Management Suite Known Issues ECS Gatekeeper 9

10 otherwise the streaming & recording cannot work. Release Notes for Avaya Scopia Management Suite Known Issues ECS Gatekeeper 10