Avaya Equinox Conferencing Media Server for Equinox Solution FP ( ) Release Notes

Transcription

1 Avaya Equinox Conferencing Media Server for Equinox Solution FP ( ) Release Notes August 13 th 2017 Avaya Equinox Conferencing Media Server Version Equinox Solution FP August 2017 Rev.2 October

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 Equinox Conferencing Media Server Equinox Solution Version FP, August

3 Contents Avaya Equinox Conferencing Media Server for Equinox Solution FP ( )... 1 Release Notes... 1 Contents... 3 Document changes... 5 Introduction... 5 Installation... 5 Product compatibility... 5 Required patches... 6 Backing up the software... 6 Installing the release... 7 Troubleshooting the installation... 8 Restoring software to previous version... 8 What s new... 8 Equinox Solution FP... 8 Equinox Solution SP Equinox Solution Avaya Equinox Conferencing Media Server... 9 WebRTC only Gateway License Resolved Issues Equinox Solution FP Avaya Equinox Conferencing Media Server v Equinox Solution FP Equinox Solution Known Issues and Workarounds Avaya Equinox Conferencing Media Server v Equinox Solution FP Avaya Equinox Conferencing Media Server v Equinox Solution 9.0 SP Documentation Note Supported Languages Contacting support Contact Support Checklist Contact Support Tasks Appendix A Installing Avaya Common Servers (CSR) with Avaya Appliance Virtualization Platform (AVP) Downloading documentation About this task Procedure Initial AVP host configuration

4 About this task Procedure Deploying the Solution Deployment Manager client

5 Document changes Date Description 11/08/2017 First Release of the document 12/10/2017 Doc Revision added AVP common server notes Introduction This document provides late-breaking information to supplement Avaya Equinox Conferencing Media Server software and documentation. For updated documentation, product support notices, and service pack information, go to the Avaya Support site at Installation Product compatibility For the latest and most accurate compatibility information go to Avaya Equinox Conferencing Media Server for Equinox Solution FP is compatible with the following product versions: Conferencing Bundle Component Version Avaya Equinox Management (Management) (GK) (UCCS) (ESF\Portal) Avaya Equinox Media Server (MCU) (AAMS) (WCS) Avaya Scopia Elite 6000 MCU Avaya Scopia Elite 5000 MCU

6 Component Version Avaya Scopia Desktop/XTDesktop Avaya Scopia Mobile for Android Avaya Scopia Mobile for ios Avaya Scopia XT5000 / XT4200 / XTE Avaya Scopia XT XT Scopia Control Avaya Equinox H.323 (PF) Server Avaya Equinox H.323 (PF) Client Avaya Equinox Streaming & Recording Avaya Equinox Recording Gateway Web Client (SWC) JS Client SDK Avaya Scopia Video Gateway for Microsoft Lync Avaya Scopia Gateway Equinox Client Required patches No patches required for this version. Backing up the software Please refer to the documentation, which is available from: Deploying Avaya Equinox Conferencing 9.0 Solution Administering Avaya Equinox Conferencing Media Server Using Avaya Equinox Conferencing Media Server 6

7 Installing the release Upgrade of the Avaya Equinox Media Server must be performed only after the upgrade of the Avaya Equinox Management Server software. Please upgrade first the Avaya Equinox Management Server. NOTE: If you are using an Avaya Common Server with AVP please do not re-image the AVP software. Instead please follow the documented activation process and then upgrade AVP if required. Re-imaging of Equinox Ultra High servers is not supported. For enabling the AVP license for >32 vcpu please check Appendix A Installing Avaya Common Servers (CSR) with Avaya Appliance Virtualization Platform (AVP) Please refer to 9.0 release notes first. The following important additional notes are applicable to FP: Upgrade The Equinox Conferencing Media Server Upgrade archive downloaded from PLDS (EquinoxMediaServer_9_0_2_5.zip) contains separate upgrade files relevant to the specific release (MediaServer_9_0_2_5.zip, SecurityUpdate_CVE_3.zip and PMGR_9_0_2_72.zip). Those files need to be extracted and installed separately according to the order specified below. Attempting to install the archive downloaded from PLDS directly will result in an error. The required installation order is as follows: 1. SecurityUpdate_CVE_3.zip 2. PMGR_9_0_2_72.zip 3. MediaServer_9_0_2_5.zip The PMGR version can be checked in the Software version field of the management web interface: Devices -> Media Servers. 7

8 Full Installation The Media Server Full Installation (OVA) archive downloaded from PLDS (EquinoxMediaServer_9_0_2_5_OVA.zip) also contains separate upgrade files relevant to the specific release: MediaServer_9_0_2_5.ova and SecurityUpdate_CVE_3.zip. Those files need to be extracted and installed separately according to the order specified below. The main reason is that the OVA does not incorporate all security enhancements. Therefore, after deploying the OVA the virtual machine must be updated using SecurityUpdate_CVE_3.zip. The required installation order is as follows: 1. MediaServer_9_0_2_5.ova 2. SecurityUpdate_CVE_3.zip It is mandatory to perform installation procedures from a computer located on the same network as your Media Server in order to ensure that there are no failures due to network connectivity issues. For information about patches and product updates, see the Avaya Technical Support Web site Troubleshooting the installation For information about troubleshooting the installation, see the Avaya Technical Support Web site Restoring software to previous version It is not possible to go back to a previous version. If needed perform a new installation What s new The following table lists the enhancements in the Avaya Equinox Conferencing Media Server for Equinox Solution 9.0 SP1 and is cumulative since the last major/minor release, showing the most recent release first and oldest release last. Equinox Solution FP Avaya Equinox Conferencing Media Server is a Service Pack part of the Equinox Solution Feature Pack. This software release implements multiple security vulnerability and system stability improvements. No new features are introduced on the Media Server side. Equinox Solution SP1 Avaya Equinox Conferencing Media Server is a service pack so no new features are introduced. 8

9 Equinox Solution 9.0 Avaya Equinox Conferencing Media Server initial release for Equinox Solution Enhancement Wallpaper in video menu customization Support of 1080p resolution in Web Collaboration presentation WCS cascading support Audio prompts localization Endpoint mute Indication Mute-all except the moderator Bandwidth setting at 448k Audio only participants indication Avaya Equinox Communicator 3.0 Description The administrator can configure independently not only the logo in the Welcome and IVR pages but also the wallpaper slide. (GRIP 17974) When the content resolution is 1080p and all the participants are able to receive content resolution at 1080p the MCU sends content with 1080p resolution. When a participant with an endpoint that is able to receive the content with a resolution of up to 720p only joins the conference, the MCU sends content with resolution 720p only to the participants not able to receive 1080p resolution. (GRIP 16798) Web Collaboration Server cascading is now supported Audio prompts are now available in 12 languages as a basic package. The language selection is available from the Avaya Equinox Management. Avaya Equinox Management will reflect the effective mute status in the endpoint. (XT series / Scopia Desktop / WebRTC client) The Mute-all option issued by the moderator will mute the audio of all the participants but not the audio of the moderator who issues the request. A new bandwidth setting is available at a rate of 448k as requested from customers. (GRIP 15927) While recording and streaming video, the Audio only participant message will not appear. In lecture mode the Audio only participant message will be sent only to the lecturer. When the above message is disabled (by an Advanced Command), the on-screen Audio only participant indication will be displayed for 5 seconds and then hidden. The Avaya Equinox Communicator 3.0 interoperability is fully supported. Avaya Equinox Conferencing Media Server The Avaya Equinox Conferencing Media Server is a merge of Avaya Media Server technology, Avaya web collaboration technology and Scopia Elite MCU technology. It is software-based and all media processing is performed on the Server native CPUs. The Avaya Equinox Conferencing Media Server is available as software OVA package that can be installed on: Customer s Virtual Machine which is running standard VMware, installed mandatory on an Intel Xeon Processor based server. (AMD CPUs not supported) Avaya Common Server running VMware based Appliance Virtualization Platform (AVP 7.0, AVP 7.1). The OVA is a virtualization format with the Linux Red Hat 6.7 operating system and is deployed to run on VMware 5.5 or 6.0 versions. 9

10 The Avaya Equinox Conferencing Media Server includes several virtualized applications: an HD Video Transcoding Software MCU, a High Scale audio engine derived from Avaya Media Server, a Web Collaboration Engine, a WebRTC capability. The Avaya Equinox Conferencing Media Server is ready to support different video technologies such as transcoding and switching and ensures a future proof investment to all customers using the TE or the OTT models. Video multi stream switching technology will be introduced with the following releases of the Media Server in synergy with the adopted software and hardware client support. That technology will enable end-to-end user experience, supporting specific use cases and allowing the solution to scale according to the user needs. The Avaya Equinox Conferencing Media Server can also be deployed as a Gateway/Add-on for the existing Elite 6000 MCU series. In this mode it can function as a WebRTC Gateway to add a WebRTC functionality to the deployment or as a Web Collaboration-only server to add a Web Collaboration service for advanced content sharing. The Avaya Equinox Conferencing Media Server supports two main working modes. Each mode is based on the deployed: Virtual Machine (VM) & hardware (HW) characteristics Licensing The system administrator should choose one of those modes in Avaya Equinox Management: 1. Full Audio, Video, and Web Collaboration per single OVA Support from 10 HD 720p/30fps up to 40 HD 720p/30fps video transcoded channels per single OVA. 2. High Capacity Audio and Web Collaboration per single OVA Support from 500 audio-web collaboration connections, up to 2000 audio-web collaboration connections per single OVA. The working mode can be switched from the Avaya Equinox Management interface. The Media Server cannot work in a mixed mode. Two Avaya Equinox Conferencing Media Server machines are needed in order to deploy a solution with both working modes: One server is needed for Full Audio, Video, Web Collaboration, which includes also WebRTC One server is needed for High Capacity Audio and Web Collaboration. The conference cascading between the two working modes is supported. Please refer to the documentation which is available from: Deploying Avaya Conferencing 9.0 Solution Administering Avaya Conferencing Media Server Using Avaya Conferencing Media Server Server requirements The tables in the following sections provide references for each one of the possible deployment models. The deployment model must be chosen based on hardware specifications during the installation of the OVA image. Table 1 and Table 1a: 10

11 Minimal VM requirements and minimal hardware (HW) requirements for deployment of the Media Server according to the capacity the customer requires. The specified configurations of VM and HW (Medium, High, Ultra High) allow customers to install the proper OVA module based on the capacity they need. Selecting the proper configuration prevents over allocation of VM and/or HW resources. In order to support Avaya Aura Conferencing (AAC) migration from the current ACC Release 8 HW and VM deployed in the field, a 4 th OVA configuration (Low) is specified to be used for configuration of audio-web mode only. Table 1: Minimal VM requirements Parameter Low Configuration Medium Configuration High Configuration Ultra High Configuration Recommended Server CPU (processor X physical cores) 2.0 X X X X 24 VM vcpus Reservation VM CPU Reservation (MHz) VM RAM Reservation (GB) Disk Reservation (GB) NICs number Max number of licenses applicable in OTT model Max ports 720p/30fps Video ** Max ports Audio *** Notes: special* 1 up to 2 up to The virtual machine must be installed mandatory on an Intel Xeon Processor based server. Virtualization supported on VMware ESXi version 5.5 or 6.0 and on Avaya AVP (7.0, 7.1) It is very important not to change any parameters after deploying OVA. For Low and Medium deployment Hyper threading BIOS option can be disabled, then the number of physical cores equals to the number of VM vcpus reservation. For High and Ultra High deployment Hyper threading BIOS option must be enabled, then number of VM vcpus reservation should be twice as the number of physical cores. The Low Configuration is relevant only for Avaya Aura Conferencing (AAC) Migration from an existing deployment, when an existing server needs to be re-used. It provides up to 200 ports audio only together with Web Collaboration. *This license is for AAC Audio-only migrations and is not available for the OTT model. ** In Full Audio, Video and Web Collaboration mode, for this working mode the audio capacity of the Media Server is twice the 720p/30fps port capacity. (Example: in Medium configuration p Ports correspond to 20 audio Ports). *** In High Capacity Audio and Web Collaboration mode. 11

12 Table 1a: Minimal Hardware server requirements Parameter Low Configuration Medium Configuration High Configuration Ultra High Configuration CPU Physical Cores Core Frequency 2.0 GHz 2.0 GHz 2.5 GHz 2.5 GHz RAM Memory 12 GB 16 GB 24 GB 64 GB HDD Drive 2.5 SAS 120 GB 120 GB 120 GB 120 GB Max number of licenses applicable in OTT model special* 1 up to 2 up to 4 Max ports 720p/30fps Video ** Max ports Audio *** Notes: The virtual machine must be installed mandatory on an Intel Xeon Processor based server. Virtualization supported on VMware ESXi version 5.5 or 6.0 and on Avaya AVP (7.0, 7.1) It is very important not to change any parameters after deploying OVA. For Low and Medium deployment Hyper threading BIOS option can be disabled, then the number of physical cores equals to the number of VM vcpus reservation. For High and Ultra High deployment Hyper threading BIOS option must be enabled, then number of VM vcpus reservation should be twice as the number of physical cores. The Low Configuration is relevant only for Avaya Aura Conferencing (AAC) Migration from an existing deployment, when an existing server needs to be re-used. It provides up to 200 ports audio only together with Web Collaboration. * This license is for AAC Audio only migrations and is not available for the OTT model. ** In Full Audio, Video and Web Collaboration mode, for this working mode the audio capacity of the Media Server is twice the 720p30 port capacity. (Example: in Medium configuration p Ports correspond to 20 audio Ports). *** In High Capacity Audio and Web Collaboration mode. Table 2: The capacity of the Equinox Media Server configured to work in Full Audio, Video and Web Collaboration Mode. The capacity of the Media Server depends on the license which determines the available ports. The licenses/ports relevant to the Over The Top (OTT) deployment model are included in the table below. When a user-specific Power Suite Model is employed, the license is unique and is equivalent to four (4) OTT model licenses. The capacity in this case is related only to the VM/Hardware Deployment Model Configuration. 12

13 Table 2: Ports number capacity in Full Audio, Video and Web Collaboration mode Video # Licenses H p/30fps/ VP8 720p/30fps H p30/30fps/ VP8 480p/30fps H p/30fps Audio WebCollab Deployment Model Configuration Ultra High Ultra High High Medium Notes: Audio refers to G.711 codec. Video ports resources: 1 (H p/30fps / VP8 720p/30fps) port uses resources equal to 2 (H p/30fps / VP8 480p/30fps) ports. 1 (H p/30fps / VP8 480p/30fps) port uses resources equal to 2 (H p/30fps) ports. The port allocation is dynamic so each connection uses the exact amount of needed resources. A mix of connections with different resolutions is supported for each meeting. Example: A 480p/30fps connection uses one quarter of the resources needed for a 1080p/30 fps connection or one half of the resources needed for a 720p/30 fps connection. The 1080p/60fps resolution is available in switching mode in H.264 using H.323 or SIP and in H.265 in SIP The H.265 video standard is available in switching mode, so without transcoding, in SIP. Table 3: The capacity of the Equinox Media Server configured to work in High Capacity Audio and Web Collaboration Mode. The capacity of the Media Server depends on the license which determines the available ports. The licenses/ports relevant to the Over The Top (OTT) deployment model are included in the table below. When a user specific Power Suite Model is employed the license is unique and is equivalent to four (4) OTT model licenses. The Low Deployment Model Configuration is relevant and specific only for AAC migrations from existing AAC Release 8 field deployments. 13

14 Table 3: Ports number capacity in High Capacity Audio and Web Collaboration mode Deployment # Licenses Audio WebCollab Model Configuration Ultra High Ultra High High Medium special* Low** Notes: Audio refers to G.711 codec (SIP only) *This license is available for AAC Audio migrations only and not for the OTT model. **The Low Configuration is relevant only for AAC Migration from an existing deployment, when an existing server needs to be re-used. It provides up to 200 ports audio only + with Web Collaboration. Supported video codecs and resolutions Video codec H.264 baseline-profile H.264 high-profile Supported resolutions Decode all resolutions from CIF up to 1080p Encoded resolutions: CIF, 240p, 352p, 480p, 720p and 1080p H.263 CIF, 4CIF VP8 240p, 352p, 480p, 720p Note: in switching mode, so without transcoding, H.265 is supported in SIP and H.264 baseline profile is supported in SIP and H.323. Avaya Equinox Conferencing Media Server Supported audio codecs Audio codec Video Calls Audio-only Calls AAC-LC Yes No Opus* Yes Yes Siren14/G Annex C Yes G.722 Yes Yes G Yes Yes G.729 Yes Yes G.711 Yes Yes *Opus codec Supported in audio only call in High Capacity Audio and Web Collaboration mode and only in WebRTC calls in Full Audio, Video and Web Collaboration mode. No 14

15 Integrated Web Collaboration Virtual whiteboard with annotation by multiple participants simultaneously. Remote desktop control. High quality content. H.239/BFCP gateway for video room system interoperability. (Full Audio, Video and Web Collaboration Mode) Embedded WebRTC functionalities The WebRTC functionalities are implemented in the Equinox solution as a distributed application. The deployment needs not only the Media Server but also the Equinox Management and the SBCE. Security TLS version 1.2 support. NIST-mode support: Certificate public/private Key RSA-2048, signature algorithm uses SHA256. Configuration web pages available only from Avaya Equinox Management. Content Support of 1080p resolution in Web Collaboration presentation: When the content resolution is 1080p and all the participants are capable of receiving content resolution at 1080p, the MCU sends content with resolution 1080p. When an endpoint that is capable of receiving content with resolution 720p only joins the conference, the MCU sends content with resolution 720p only to the participants not capable of receiving resolution 1080p. Additional features WebRTC only Gateway License The Avaya Equinox Media Server in WebRTC only mode and appropriate license works as a WebRTC Gateway. In practice, the WebRTC Gateway is the same software virtualized application (OVA) as the Equinox Media Server with a WebRTC license. It has the same part number as the Equinox Media Server. The WebRTC Gateway allows customers with an existing Elite 6000 MCU or purchasing an Elite 6000 MCU, to add the new WebRTC functionalities. The WebRTC Gateway will transcode each WebRTC Port media, converting traffic from the WebRTC standard to the SIP standards. Then the traffic will be handled by the Elite 6000 series MCU. Main features supported: Video Up to 40 H p/30fps calls or 80 H p/30fps calls or 160 H p/30fps calls Audio Up to: 160 calls (Opus narrowband, Opus wideband, G.711, G.722 supported) The WebRTC Gateway can support VP8 H.264 video bidirectional transcoding with limited audio-video capacity: up to 3 VP8 720p/30fps or 12 VP8 480p/30fps calls. 15

16 The maximum capacity of the Gateway depends on the number of vcpus on the target machine; The mandatory configuration is the Medium Configuration as stated in Table 1. The WebRTC Gateway needs to be coupled with an Elite 6000 series MCU - one WebRTC Gateway is needed for each Elite 6000 series MCU. Resolved Issues Equinox Solution FP Avaya Equinox Conferencing Media Server v Equinox Solution FP ID Visible symptoms Security vulnerability improvements. System stability improvements Conference control problem in MCU cascading after participant disconnection When a participant fails to join a PIN protected meeting due to incorrect PIN entry, a notification is played to the Meeting. Equinox Solution 9.0 First official release so no Resolved Issues available. Known Issues and Workarounds Avaya Equinox Conferencing Media Server v Equinox Solution FP ID Visible symptoms Workaround RVELITE-8539 The access to the system console is blocked after the IP-address is set The display of the Auto Attendant message might be delayed. The network configuration can be changed through the Equinox Management. By pressing Ctrl-Alt-F2 the user can login to the system. By pressing Ctrl-Alt-F1 the access is blocked again. Set the following hidden Advanced Command Command name: imcifirstparticipantdelay Value: 1000 Avaya Equinox Conferencing Media Server v Equinox Solution 9.0 SP1 16

17 ID Visible symptoms Workaround RVELITE RVELITE RVELITE RVELITE RVELITE After a new license is applied to a Equinox Media Server configured in Secured Mode, the unit configuration resets to Normal Mode. Equinox 9.0 WebRTC client does not receive video after the user pauses/resumes the remote video. SIP participants and Scopia Desktop clients might not receive a presentation when the Equinox Media Server is in Secured Mode and a H.323 Endpoint sends the presentation in Secured Mode (H.239, H.235). A participant dialing from Equinox Communicator client (AC 3.0) into Equinox meeting via Auto Attendant receives black video after joining the meeting for about 1 min. After that the video is established, however is displayed with low quality. In some rare cases, participants might see a black screen when Scopia Desktop Client sends Whiteboard presentation. There are no configuration options in some dropdown lists when deploying an OVA with a VMware vshpere Client in a non-english based system. Uncheck and check again the Secure Connection check-box. Pause/resume the remote video again until it is back to normal. Configure the Meeting Service to Best Effort and the Endpoint to nonencrypted mode. To receive high quality video when connecting from AC3.0 to Equinox 9.0 meeting, dial directly and not via the Auto Attendant. The presentation will be seen correctly after the presenter performs an action on the whiteboard. When deploying the Management Server or the Media Server OVAs with a VMware vsphere Client or VMware vcenter Server in a non-english based system the following problem might be encountered: the contents of some dropdown lists used to set some configuration parameters values might be empty. In order to resolve the problem change the native language to English and perform the OVA deployment from the beginning. The language can be changed via the computer Region and Language Control Panel: Control Panel\All Control Panel Items\Region and Language -> Formats; Select English (United States). Documentation Note Please note that in the Port Security for the Equinox Conferencing 9.x Solution the bidirectional ports to open on the Firewall for the Avaya Equinox Media Server are specified incorrectly. The actual RTP/RTCP/SRTP (UDP) port range to be opened is and not

18 Supported Languages The supported languages for audio messages are those covering the G14 countries: English (U.K.), English (U.S.), Spanish, French (Canadian), French, Italian, Japanese, Korean, Portuguese, Russian, Simplified Chinese, German. The supported languages for video messages are: English, Chinese, Traditional Chinese, Japanese, Korean, Hebrew, French, Thai, German. Contacting support Contact Support Checklist If you are having trouble with Avaya Equinox Conferencing Media Server Version 9.0.2, you should: 1. Retry the action. Carefully follow the instructions in the written or the online documentation. 2. Check the documentation that came with your hardware for maintenance or hardware-related problems. 3. Note the sequence of events that led to the problem and the exact messages displayed. Have the Avaya documentation available. If you continue to have a problem, contact Avaya Technical Support: 1. Log in to the Avaya Technical Support Web site 2. Contact Avaya Technical Support at one of the telephone numbers in the Support Directory listings on the Avaya support Web site. Avaya Global Services Escalation Management provides the means to escalate urgent service issues. For more information, see the Escalation Contacts listings on the Avaya Web site. Contact Support Tasks You may be asked to one or more files to Technical Support for analysis of your application and its environment. 18

19 Appendix A Installing Avaya Common Servers (CSR) with Avaya Appliance Virtualization Platform (AVP) Downloading documentation About this task Avaya Common Servers (CSR) are delivered with Appliance Virtualization Platform (AVP) hypervisor pre-installed. This license is also pre-installed and cannot be modified. Avaya Common Servers utilize OEM hardware from HP or Dell. Use this procedure to find and download documents on HP or Dell servers that you are using in your deployment. The documentation includes information on the servers and procedures for installing them in racks. Procedure 1. Open a browser and go to 2. Enter Common Servers in the Enter Your Product Here field, and select the server version from the Choose Release dropdown. 3. Download the documents that you need. Initial AVP host configuration About this task Note: AVP is pre-installed on Common Servers with In-band Management (applications and host management are accessed through a single port). If you require Out of Band Management, enable this feature as explained in the guide for Migrating and Installing Avaya Appliance Virtualization Platform; you should not reinstall the AVP. Note: Ultra High capacity Common Servers include an additional license to enable AVP to use more than 32 vcpus for a single OVA. This license is enabled automatically after the license agreement is accepted for the host during initial setup. For Ultra High servers, you must connect to the host via SSH using a client such as PuTTY in order to accept the agreement and fully enable the host. Note: It is mandatory to install Utility Services as the first VM in an AVP environment (before Equinox Management and Equinox Media Server). It is sufficient to install this in Services Port Only mode. When installing Utility Services in an Equinox Conferencing OTT/standalone deployment, configure the WebLM, CM and SMGR IP addresses to if those components are not present in the environment. 19

20 Warning: You should not reinstall the AVP software on an Ultra High server due to the special license which is pre-deployed during assembly. If configuration changes are required, follow the documented process to achieve this. If the AVP software requires reinstallation, the server must be replaced via Avaya s Return Material Authorization (RMA). Note: SSH is enabled by default until the EULA license is accepted. Once accepted, SSH is automatically disabled after 24 hours. You need to connect to the host using SSH and accept the EULA before deploying any applications on the host. Procedure 1. Connect a laptop to port 2 of the AVP host. Configure the laptop with the following: IP address: Subnet mask: Add host to the Solution Deployment Manager (SDM). 3. (Optional) Enable SSH on host via SDM (if more than 24 hours has elapsed since initial power on). 4. Start an SSH session, log in to The username varies depending on the AVP version. For AVP release 7.0.1, it is root; for AVP release 7.1, it is admin. The temporary setup password is Avaya123$. Once you log in, you are prompted to change this immediately. (The system is not operational until the setup password has been changed.) 5. Read and accept EULA. 6. (Required for Ultra High servers only) Execute the enable_enhanced_avp script by entering the following on the AVP command line: /vmfs/volumes/server-local-disk/enable_enhanced_avp 7. (Required for Ultra High servers only) Read and accept EULA. 8. (Required for Ultra High servers only) The script states AVP enhanced mode successfully enabled when completed. 9. (Optional for Ultra High servers only) To confirm successful enablement of AVP enhanced mode, execute the following command on the AVP command line: vim-cmd vimsvc/license --show grep "VMware vsphere" You should see an output that states name: VMware vsphere 5 Standard. Deploying the Solution Deployment Manager client About this task To manage the system and deploy OVAs, you need to install the Solution Deployment Manager (SDM) client on a PC. The SDM application requires a PC running 64 bit Windows 7 OS. Before you begin Download the SDM user guide from The guide also explains how to access the AVP host for a fresh installation. The AVP host is shipped with default IP and login. 20

21 Procedure 1. Download the SDM client application from the Avaya PLDS. The SDM version must match the AVP version (for example, 7.1 for both). 2. Install the SDM application. 3. In the SDM Client Dashboard, select the VM Management page. 4. In the Location Management page, create a location for your hosts cluster by selecting Location > New. a. Add a name for the location. b. Leave the optional fields empty. 5. In the Host Management page, enter the AVP host name, FQDN or IP, user name, and password. 6. Open the SDM client, and select the host for the OVA you want to install. This opens a page showing the host details. Select Next. 7. Add the OVA file you need to deploy: full pathname (for example, C:\Program Files\Avaya\AvayaSDMClient\Default_Artifacts\EquinoxMediaServer_8_5_0_23_5.ova) and select Submit. 8. Enter the virtual machine name and configure the network properties: default gateway, public IP address, public netmask. Select Deploy. 9. In the EULA acceptance page, select Accept. 21