Release Notes for Avaya Scopia Elite 6000 Series MCU

Transcription

1 Release Notes for Avaya Scopia Elite 6000 Series MCU Version 8.3 For Solution 8.3 March 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 Elite 6000 Series MCU Version 8.3, March

3 Table of Contents About Scopia Elite 6000 MCU... 3 What s new?... 4 Integrating with Other Components... 5 Upgrade and Downgrade procedures... 6 Resolved Issues and Enhancements... 6 Known Issues... 7 Auto-Attendant and IP Dialing... 7 MCU Web Interface... 7 General Interoperability... 7 H.243 Conference Control... 7 Encryption... 8 Content Sharing (H.239 and BFCP)... 8 Cascading... 8 SIP... 9 Far End Camera Control (FECC)... 9 Video...10 Telepresence Interoperability...10 Tips...11 This document contains the most updated information for Scopia Elite 6000 MCU version About Scopia Elite 6000 MCU The Scopia Elite MCU is Scopia Solution s flagship platform for high definition multi-party videoconferencing. The MCU harnesses revolutionary processing power for the most demanding videoconferencing applications using the latest DSP technologies. For an uncompromised videoconferencing experience, the MCU supports dual channels of Full HD 1080p at 60 frames per second for video and content, H.264 High Profile for bandwidth efficiency, H.264 Scalable Video Coding (SVC) for high network error resiliency, and full support for many telepresence systems. Release Notes for Avaya Scopia Elite 6000 Series MCU About Scopia Elite 6000 MCU 3

4 What s new? What s new in version 8.3 Scopia Elite MCU version 8.3 includes the following new features: Avaya branding - The MCU s hardware, web interface, and video slides now feature the Avaya logo. Gallery layouts A set of unique video layouts composed of both video and presentation, especially tailored for the following endpoints: o o o o Scopia XT Series with a single screen. Single-stream endpoints such as Avaya Flare, OneX, Microsoft Lync and others, which cannot receive standard dual H.239 / BFCP presentation.. Endpoints that can only receive H.239 / BFCP with a H.263 video codec. Any other endpoint that displays video and presentation on the same screen, as configured via Scopia Management. These layouts require the receiver to support H.264 Baseline or High-Profile, with a minimum bitrate of 384K or 256K, respectively. The minimum video resolution is 720p/15fps. Gallery layouts consume an additional 480p port per conference. In Scopia Management, administrators can configure which meeting types support gallery layouts. New and enhanced Voice Activity Detection (VAD) and Automatic Gain Control (AGC) algorithms, used to identify the active speaker, filter out participants producing background noise, and align the audio level for all participants. New look & feel for all video slides, including the Auto-Attendant, welcome slide, waiting room, moderator menu, and others. TLS/SRTP support for video, audio, and presentation when integrating with Avaya Aura. This includes Avaya phones, Flare and OneX, along with Scopia XT Series natively registered to Avaya Aura. This functionality requires Avaya Aura FP4. Integration with Avaya Sipera SBC Currently, it is supported for video and audio only. Presentation and encryption support is planned for a later time. Support for Acme-Packet SBC. What s new in version 8.2 Network redundancy the MCU has two Ethernet connections that can be used simultaneously. Use the second connection for redundancy, which allows the system to continue service in case the first connection fails. Recording indication for new participants a new audio indication notifies participants who join the meeting that a recording is already in progress. Scopia Elite MCU version 8.2 includes the following new features: Dynamic and flexible resource allocation a meeting can support a mix of SD and HD users, making most efficient use of available resources. Each user connects using unique, optimized audio and video settings to enjoy the best audio and video quality supported by their endpoint and network, without affecting the other participants in a meeting. Scopia Elite 6105 to 6110 license upgrade H.263 video processing is now an integral part of the MCU, allowing legacy video Release Notes for Avaya Scopia Elite 6000 Series MCU What s new? 4

5 endpoints that do not support H.264 to connect to any meeting on the MCU. H.263 capacity is similar to H.264 at 480p video resolution. Support for IP Separation the MCU enhances security within the enterprise by routing media and management traffic to two different subnets. IPv6 support Scopia Desktop participants connecting via the MCU waiting room now hear a new audio prompt. What s new in version SCOPIA Elite MCU version includes the following new features: Increased Desktop/Mobile Capacity the MCU can now accommodate quadruple capacity (x4) for all video resolutions up to 480p30. A new license option that doubles the MCU capacity for 720p30 video resolution. This license option should be purchased separately and can be installed on all Elite 6000 MCU models. Participants waiting to join a videoconference in a virtual room will now enjoy new music until the moderator joins and starts the meeting. Integrating with Other Components Scopia Elite 6000 MCU v8.3 is compatible with the following product versions: Component Version Scopia Management 8.3 Scopia Elite 5000 MCU Scopia Desktop Server 8.3 Scopia Mobile for ios 3.3 Scopia Mobile for Android 8.3 Scopia XT5000 / XT4200 / XTE Scopia Control 8.3 Scopia XT1000 / XT Scopia VC Scopia TIP Gateway 8.0 Scopia Video Gateway for Microsoft Lync 7.7 Scopia Gateway Scopia Enhanced Communication Server (ECS) 8.3 Scopia PathFinder 8.3 Release Notes for Avaya Scopia Elite 6000 Series MCU Integrating with Other Components 5

6 Upgrade and Downgrade procedures It is mandatory to perform upgrade and downgrade procedures from a computer located on the same network as your MCU, to ensure that there are no failures due to network connectivity issues. To upgrade your Scopia Elite 6000 MCU, see the Upgrading Scopia Elite 6000 Series MCU Software chapter in the Scopia Elite 6000 MCU Administrator Guide. Important When downgrading from version 8.3 to version 8.2, the MCU configuration may be restored to factory defaults. We recommend backing up the system configuration before downgrading. Resolved Issues and Enhancements This section details the list of issues that were resolved in version 8.3. Case Number Description When an endpoint is disconnected from the conference, the Active Speaker and Presenter icons may still be displayed Participants' names might disappear from the MCU Conference Control The video layout might suddenly change to a personal layout, even when the personal layout is disabled. The number of participants on the display increases when an invalid endpoint IP is invited and the invitation fails The participants Audio Gain cannot be controlled An endpoint camera blocked on the MCU Conference Control can be unblocked with a DTMF sent by the endpoint The icon for a blocked camera is not displayed Text overlay alignment cannot be selected Text Overlay Opacity (transparency) is not adjustable Presentation resolution cannot be configured to HD1080p Presentation problems when a Tandberg EX60 endpoint participates in a conference Elite 6105 MCU reboots occasionally when NTP is enabled Lecturer's video is not sent to some participants connected to a slave MCU Participants without active media may not be positioned properly in the video layout No audio in voice call when calling in via Auto-Attendant SIP OPTIONS message is sent over UDP when TLS mode is selected FQDN in the Gatekeeper field isn t accepted MCU Auto-Attendant language is incorrect when the MCU is registered with Scopia Management. Release Notes for Avaya Scopia Elite 6000 Series MCU Upgrade and Downgrade procedures 6

7 Known Issues This section details the list of open issues in this version. Auto-Attendant and IP Dialing Auto-Attendant is not supported for the endpoints listed below. These endpoints do not support the Hold/Resume mechanism used to transfer endpoints from the Auto-Attendant session to the target Conference: Sony 1600, Polycom VS512, Innomedia SIP Phone, Leadtek SIP phone, TelePhoSee and old versions of Tandberg 1000 and Tandberg Connecting to the MCU Auto-Attendant using a Tandberg 1000 requires endpoint version B10.3 or higher. MCU Web Interface The user interface does not function correctly when the following setting is configured in Internet Explorer: Tools > Internet Options > General > Browsing History section > Temporary Internet files > Settings > Every visit to the page Solve this issue by modifying this setting to Automatically. IE-8/Vista: When selecting Manage Conferences from the MCU administrator web interface to open the Conference Control page, you are redirected to the login page. General Interoperability In a full HD 1080p conference, Polycom HDX8000 endpoints display a resolution of 1920x1072 and Tandberg C20 and C90 endpoints display a resolution of 1920x1088, even though the MCU is sending 1920x1080. In some cases, Mirial softphone doesn't send video to the MCU. When an IBM Sametime client connects to an MCU conference using audio only, it may not be possible to add video to the call. Reconnect with video. Tandberg MXP 95 and 990 endpoints connected to an Elite MCU conference may experience big video delay. To overcome this issue, configure the endpoint to use motion. (20575) bout Radvision H.243 Conference Control H.243 conference control might not function with some ISDN endpoints that are connected through a gateway. When H.243 is enabled, Far End Camera Control (FECC) to some TANDBERG endpoints might not function. Disable H.243 to solve this issue. If PIN protection is enabled, participants can only take moderator control via the MCU DTMF conference control menu. Release Notes for Avaya Scopia Elite 6000 Series MCU Known Issues 7

8 Encryption Tandberg 6000E might disconnect during encrypted calls. Configure the endpoint to use a call rate of 768 Kbps to solve this issue. Encryption does not function with Polycom HDX 9002 endpoints that are set to encryption required. Configure the endpoint to use encryption when available to solve this issue. Sony PCS-1 endpoints version 3.41 (or earlier) fail to connect to the MCU when the MCU is configured to use encryption. Use version 3.42 or later to solve this issue. In some cases where encryption is enabled, the bitrate of existing calls may be reduced automatically to maintain the MCU capacity and accommodate additional calls. Content Sharing (H.239 and BFCP) Cascading Sony PCS-1 endpoints do not always display the presentation when the presenter is an HD endpoint. In a full HD 1080p conference, TANDBERG C20 endpoints do not display the presentation when the presenter is any other participant. Configure the MCU to a maximum call rate of 1,500 Kbps or less to solve this issue. LifeSize Passport endpoints may not receive presentations that are sent from Sony PCS- XG80 endpoints. In a call between the MCU and Tandberg C20 v5.1, the endpoint may stop displaying the main video channel after H.239 presentation is stopped. (10262) Polycom HDX and Group series endpoints connecting to the MCU via SIP and through the Auto-Attendant do not display content shared by another endpoint. To avoid this issue, connect to the meeting by dialing the meeting ID. (25667, 12659) Endpoints that support only H.263 may fail to receive content shared by a Polycom HDX due to an HDX issue. Restart the presentation to solve this issue. (11830) If some of the endpoints only support H.263 for the presentation channel, it is recommended to configure the MCU to static presentation mode.(11831,17072,15551) Sony PCS-1 endpoints cannot receive content shared by other participants. (19237) Cisco EX90 endpoints connecting to the MCU via SIP cannot share content due to an endpoint issue. Configure the MCU to use static H.264 presentation to solve this issue. MCU SIP Presentation does not work with Tandberg MXP ver. F8.0 PAL and F9.0.2 PAL, since these endpoints only support BFCP over UDP. As a workaround, configure the MCU to a static presentation mode. (18035) LifeSize Team 220 endpoints connecting to the MCU via SIP cannot share content.(11382) When content slider is enabled (default configuration), endpoints that support only H.263 for the presentation channel cannot share/receive presentation. As a workaround, change the MCU meeting type (service) to H.263-presentation-only. Layout per participant and the shrink-to-fit feature are not supported on endpoints connected to the slave MCU. When a slave participant becomes the active speaker, the text overlay may be displayed with a slight delay after the video itself. Gallery layoutsare only supported on the Master MCU. Release Notes for Avaya Scopia Elite 6000 Series MCU Known Issues 8

9 SIP Scopia XT series endpoints connecting to the MCU Auto-Attendant through an Acme- Packet session border controller (SBC) may disconnect when transferred to the conference. As a workaround, disable presentation support in the endpoint configuration and disable BFCP-UDP fallback in the MCU configuration. (23664) Tandberg MXP150 versions 4.2 and earlier may not display video. To solve this issue, upgrade to a later software version (such as 5.1). Tandberg MXP1700 endpoints connecting to the MCU Auto-Attendant may not display video after transferring to the MCU conference. To avoid this issue, connect to the meeting by dialing the meeting ID. (25968) When dialing out via SIP, LifeSize version endpoints display CIF resolution instead of 720p. Upgrade to version 4.0 or later to solve this issue. When muting and unmuting a LifeSize Room 200 version endpoint connected via SIP, the endpoint stays muted. Upgrade to a later endpoint version to solve this problem. LifeSize-Room100 v3.5 connecting to the MCU through the Auto-Attendant and using SIP may experience poor audio quality. When the MCU dials a LifeSize Passport v4.3, the endpoint displays the welcome screen after 6 seconds, instead of while the video is starting. (15040) Polycom Group series (v4.0 and later) connecting to the MCU through the Auto-Attendant and using SIP might transmit poor video quality. To avoid this issue, connect to the meeting by dialing the meeting ID. (25959, 25550) When the MCU dials Polycom version endpoints via SIP, the audio channel fails to open. Remove the G.722.1C audio codec to solve this issue. When the MCU dials Sony PCS-XG80 endpoints, they display 288p resolution instead of 720p. Use the Empty Invite option to solve this issue. Sony PCS-XG80 endpoints do not send video after transfer even though video channel remains open. (18081) Sony PCS-1 and PCS-XG80 endpoints may not see the video properly, if connecting to the MCU through the Auto-Attendant and using SIP, or if invited from the MCU. As a workaround, disable H.264 High-profile and 240p resolution in the MCU configuration. (25878, 25888) Far End Camera Control (FECC) LifeSize Room 200 endpoints using versions and earlier cannot control the camera of other endpoints. FECC does not function during encrypted meetings with LifeSize and Polycom HDX endpoints. (18655) FECC does not function with Tandberg C20 and C90 endpoints. Release Notes for Avaya Scopia Elite 6000 Series MCU Known Issues 9

10 Video When setting the Elite auto-switch interval, the actual switching interval may be longer if the unit is overloaded or cascaded. Interoperability issue with Scotty EOS may result in decreased video quality. Manual drag & drop of a participant in the Scopia Management Conference Control UI may disable the active speaker video indication. Text message sent to the conference participants from Scopia Management is limited to 255 bytes. Telepresence Interoperability When Polycom RPX is connected to the MCU, the different video segments may be crossed and shown in a wrong order on the video layout. When dialing from a Polycom Telepresence to an MCU conference, you may experience connectivity issues and may need to redial. Starting a Presentation from Tandberg T3 v1 endpoints using DTMFs might fail. In Tandberg T3 v2 this issue is resolved. Release Notes for Avaya Scopia Elite 6000 Series MCU Known Issues 10

11 Tips It is strongly recommended to export the customer support package only when the MCU is in an idle state. Exporting the package when the system is loaded may force the system to restart. When the Windows Start Navigation sound is enabled, a continuous clicking sound is heard when the Conference Control interface automatically refreshes. Disable this sound in the Sounds and Multimedia configuration of the Control Panel. The Conference Control and Login screens are best viewed in full screen mode (1024x768). The MCU allows you to open multiple Conference Control browser screens at the same time. We recommend that you close screens in which you are not currently working to avoid confusion and performing operations on a wrong conference. We recommend that you set the Ethernet port speed and duplex parameters of both the MCU and the switch to Auto Negotiation. Set these parameters to 1Gbps full duplex only if your switch supports this configuration and if you experience port speed negotiation problems. Ensure that the Ethernet port speed and duplex parameter values on the MCU and the switch are identical. It is recommended to adjust the MTU size value according to the other network devices that are part of your deployment. Release Notes for Avaya Scopia Elite 6000 Series MCU Tips 11