LINK TO RECORDED PRESENTATION CONFIDENTIAL& NOT TO BE DISCLOSED BEFORE JUNE 8TH. - презентация

1 LINK TO RECORDED PRESENTATION CONFIDENTIAL& NOT TO BE DISCLOSED BEFORE JUNE 8TH.

2 Avaya Aura TM Conferencing Presenter: Ignacio Miranda CONFIDENTIAL & NOT TO BE DISCLOSED BEFORE JUNE 8TH

3 Avaya – Proprietary. Use pursuant to Avaya policy.3 Overview New Release Offering Enterprise Edition and Standard Edition Aura TM Conferencing Standard Edition Solution Installation Licensing System Configuration Management Solution Modeller Logging and Alarming Upgrades Aura TM Conferencing Enterprise Edition Solution Installation Licensing System Configuration Management Solution Modeller Logging and Alarming Upgrades

4 Avaya – Proprietary. Use pursuant to Avaya policy.4 New Release Offering 4 Extends Avaya Aura TM integration through platform adoption – foundation application for enterprise communications Simplifies administration and lowers cost of serviceability (Avaya Aura TM System manager, Avaya Aura TM System platform) Deployment on Avayas System Platform Rapidly deploy pre-configured systems into the field. It will also provide the ability to run several Avaya products on a single server. Integration with Avayas System Manager which will include web- based configuration, common logging, and SNMP Support for Avayas Secure Access Link Standard Edition will Replace the MX Express technology This release will be capable of supporting Asian (double byte) languages Licensing will be Integrated with Avayas PLM framework

5 Avaya – Proprietary. Use pursuant to Avaya policy.5 Standard VS Enterprise BridgeStandardEnterprise Audio BridgeYY IP H.323 Y (through Avaya Aura TM Communication Manager) IP SIPYY Maximum Capacity Single ServerY LanguagesYY SNMPYY Adhoc ConferencingYY Disaster RecoveryY Video Y Database Interface (API or Stored Procedures)YY Flex Call FlowY Y Bridge Talk Y Real-Time Conference Control APIYY

6 Avaya – Proprietary. Use pursuant to Avaya policy.6 Standard VS Enterprise Media Server Standard Enterprise SRTPYY Video Conferencing Y Multiple Codecs Y Separate Media Server Y ApplicationsStandardEnterprise Multisite Y Conference Viewer Y LDAP IntegrationYY Audio Console Y Y CRS Y Y Self Reg Y Web Scheduling and Web AdminYY SMS Notifications Y Wholesaler / Reseller Model Y BillingYY ReportingYY Notification SubsystemYY Multi-system Y Logical Cabinet Redundancy Y

7 Avaya – Proprietary. Use pursuant to Avaya policy.7 Standard VS Enterprise Groupware Standard Enterprise Outlook Integration Y Y OCS 2007 R2 Integration Y Y Sametime Integration YY Adobe Integration Y Y Notes Integration Y Y AWC Recording Server Y AWC Playback Server Y AWC Integration YY

8 Avaya – Proprietary. Use pursuant to Avaya policy.8 Aura TM Conferencing Standard Edition

9 Avaya – Proprietary. Use pursuant to Avaya policy.9 Standard Solution 9 Single server solution Standard IBM 3550 M2 aka. Avaya S8800 MX 6.0 S8800 Comcode is The orderable code is Requires installation of System Platform ISO, provided via CD System Platform ISO installs the CentOS, the XEN software and other software/tools to provide virtualization Requires the installation of a system platform template that contains the following VM images: System Manger Web Conferencing Web Portal plus Audio Console Client Registration Server Application server/Media Server Standard Edition will be the upgrade path for Meeting Exchange Express 300 port systems. The upgrade from these older platforms to Standard will be a forklift upgrade. All configuration managed through System Manager web interface.

10 Avaya – Proprietary. Use pursuant to Avaya policy.10 Standard Solution Diagram 10 The light blue is the Domain-0 which represents System Platform and needs to be installed on the server before a template can be applied. The darker blue represents the conferencing Virtual Machines that will form the Standard Edition Template. The template includes the whole solution except for the system platform that has to be installed in the machine initially. Upgrades will be provided as a new template Conferencing Standard Edition Template

11 Avaya – Proprietary. Use pursuant to Avaya policy.11 Application Aura TM Conferencing Standard Edition Make/Model IBM X3550 M2 ProcessorTwo x Quad Core Intel® Xeon Processor X5570 4C (2.93GHz 8MB L3 Cache 1333MHz 95w) Memory24 GB (12 x 2GB DDR Rx8 LP RDIMM) BezelAVAYA BEZEL RaidRAID 5 - MR10i Integrated RAID Controller. Disk Drives3 x 300GB SAS 2.5" 10K RPM Hard Drive. Addl NIC'sBroadcom Corporation NetXtreme II BCM5709 Gigabit Ethernet Removable Media DVD-R/W SATA slimline Power Supply2 x 675W 12V Hotplug AC power supply. FansRedundant Multi-Speed Fans FirmwareIMM v1.05, RAID v , uEFI v1.03 and HDD v1.05 Server Specification

12 Avaya – Proprietary. Use pursuant to Avaya policy.12 Avaya Aura Conferencing Standard Edition Installation Conferencing R&D

13 Avaya – Proprietary. Use pursuant to Avaya policy.13 Installing Standard Edition First The System Platform ISO has to be installed, it contains the CENTOS OS and the template management console which will allow the installation of templates. Use the Template DVDs or Download a Template from PLDS website. plds.avaya.com Using System Platform install the template Via the GUI.

14 Avaya – Proprietary. Use pursuant to Avaya policy.14 After the template is installed, the Windows Virtual Machines for the CRS and AWC will have to be activated with a valid license from Microsoft, for the Windows server 2008 Windows required updates will have to be installed after the system is up and running The Antivirus has to be installed after the update The IP address for all the Virtual Machines will have to be configured during the Installation of the Template

15 Avaya – Proprietary. Use pursuant to Avaya policy.15 AURA TM Conferencing Licensing

16 Avaya – Proprietary. Use pursuant to Avaya policy.16 Licensing Feature NameFeature Description VALUE_CONF_EDITIONStandard or Enterprise VALUE_CONF_AWC_USERSMaximum Avaya Web Conferencing (AWC) Users AWC licensing mechanism same as 5.2 FEAT_CONF_AWC_RECORDING_PLAYBACKAWC Recording/Playback AWC licensing mechanism same as 5.2 VALUE_CONF_EXTERNAL_UC_CI_USERSMaximum External UC Client Integration Users VALUE_CONF_AUDIO_PORTSMaximum Audio Ports per Application Server VALUE_CONF_VIDEO_PORTSNot currently used. VALUE_CONF_ISAC_CODEC_PORTSNot currently used. Licensed Attributes

17 Avaya – Proprietary. Use pursuant to Avaya policy.17 Licensing A newly installed Conferencing system will have a grace period of 30 days in the following cases: – There is no license or it is not valid – To get the Grace Period started the system has to be able to register with SMGR at least once – The SMGR is down or cannot be contacted The Grace period will allow all components to operate as normal up to their maximum default value Once the Grace Period expires the system will stop functioning Once a valid license is retrieved from WebLM the components are configured as per the licensed and started A valid license will never expire The license is cached in the local system and will be updated only if new licenses are installed or de-installed in the WebLM server In the case of a license failure an alarm and log statement will be raised In a multisystem scenario there is a single license with the total number of ports for the customer: – Each bridge takes the number of ports its configured for – If not enough ports are available in the license it will take the max available

18 Avaya – Proprietary. Use pursuant to Avaya policy.18 Licensing CRS Licensing Pulls the Edition from the license, to know whether it is Enterprise or Standard Pulls the number of external UC CI users, for every user that tries to use the SOAP adaptor. External adaptors, like Microsoft, OCS, IBM, Outlook. The Grace Period will allow the CRS to have as many users as required up to the maximum. Once the grace period expires none will be allowed. It manages how many users get a license internally When the grace period finishes, the Users are still allowed to complete their session but no new sessions will be allowed WEB Portal Licensing Query for VALUE_ACC_EDITION, to know if it is enterprise or standard The distinction is just a formality, the software behaves the same way in standard and enterprise During Grace Period Enterprise will be assumed If there is a license failure, or grace period expires, the web portal will still run, but it will display a page saying that the license is expired.

19 Avaya – Proprietary. Use pursuant to Avaya policy.19 Licensing Bridge Licensing The Licence Proxy will retrieve the VALUE_ACC_AUDIO_PORTS and the VALUE_ACC_EDITION properties from the license server The numChannels value in system.cfg will be populated with the VALUE_ACC_AUDIO_PORTS count prior to the processes start up If the server edition is standard, only G.711 codecs will be allowed During Grace Period the proxy manager will check if the system is running in SP, if so it will assume standard and allow 300 ports if not it will assume enterprise and allow 3200 ports. AWC Licensing In Conferencing 6.0 we will be licensing AWC using DCLs proprietary license, without any changes to the way it was normally done in 5.2

20 Avaya – Proprietary. Use pursuant to Avaya policy.20 Configuring system View license details or installing a new license file – - admin/admin admin/admin123 – Navigate to Licenses: Server Properties – display the details needed to create a license file Install License – provides a page to install a new license file Licensed Products – shows the installed license and its usage

21 Avaya – Proprietary. Use pursuant to Avaya policy.21 Licensing License Installation GUI Interface to install the license for the product One single license for the product per site, with all the properties acquired by the customer

22 Avaya – Proprietary. Use pursuant to Avaya policy.22 AURA TM Conferencing System Configuration Management

23 Avaya – Proprietary. Use pursuant to Avaya policy.23 Configuration Management Aura TM Conferencing Element Manager will provide configuration pages to be able to setup the Bridge. The configuration Manager will GET the configuration data for all the components It Queries the bridge regularly and caches the information in the System Manager Each component (Bridge, CRS, Web Portal….) continues to use their specific configuration files and databases, with their current specific formats. The new configuration changes are verified before they are SET back to the components. If two people make changes to the configuration in parallel, the last one will get a warning and the option to either discard the changes or overwrite the other parallel changes. If a configuration parameter exists in any of the configuration files that is not managed by the configuration manager, this parameter will not be modified or affected when changes are made to that file via the System Manger GUI Manual changes could be made to the original configuration files (this is strongly discouraged) Any changes made to the files will be picked by the Configuration Manager and displayed next time someone access the web pages

24 Avaya – Proprietary. Use pursuant to Avaya policy.24 Configuration Management The configuration of AWC will be done via its own WEB pages The Conferencing element manager will have a link to the AWC WEB pages There are certain parameters in the Web Portal and CRS that need to be exposed and affect the configuration of AWC AWC Configuration

25 Avaya – Proprietary. Use pursuant to Avaya policy.25 Configuring system Adding Conferencing nodes – bridge/crs/wp and AWC to the SMGR – - admin/admin admin/admin123 – Navigate to Elements => Inventory => Manage Elements – Add the 4 entities selecting Type Conferencing 6.0, committing changes each time

26 Avaya – Proprietary. Use pursuant to Avaya policy.26 Configuring system Useful information – Accounts/passwords BRIDGE craft/craft01 – sroot/sroot01 CRS administrator/gatekeeper WP craft/craft01 – sroot/sroot01 AWC administrator/gatekeeper System Manager – root/root01 (shell) admin/admin123 (web) System Platform admin/admin01 Dom0 root/root01

27 Avaya – Proprietary. Use pursuant to Avaya policy.27 Avaya Aura Conferencing 6.0 Solution Modeller The replacement for EPW

28 Avaya – Proprietary. Use pursuant to Avaya policy.28 Avaya Aura Conferencing 6.0 Solution Modeler Supports configuration of Bridge, CRS, AWC and Web Supports backward compatibility within a Major.Minor i.e. within 6.0.?.?.? The default values are the default values of the systems it was built against. Note: if the default values have changed between 6.0.a.b.c and 6.0.x.y.z and you load a model created with 6.0.a.b.c into 6.0.x.y.z the default values will not be updated. If a parameter can be configured from the conferencing element manager in Avaya Aura System Manager, it can be pre-configured from Avaya Aura Conferencing 6.0 Solution Modeler We take the same Conferencing Element manager and package it in both Avaya Aura System Manager and Avaya Aura Conferencing 6.0 Solution Modeler

29 Avaya – Proprietary. Use pursuant to Avaya policy.29 Avaya Aura Conferencing 6.0 Solution Modeller Solution Modeller takes the Conferencing EM and embeds it in a standalone web server that runs from a laptop. It is the same EM as bundled in System Manager therefore no issues with synchronization. Will provide some default models reflecting common configuration scenarios. Models can then be exported for subsequent import into the Conferencing Element Manager running in System Manager Importing a configuration exported from the Solution Modeller into System Manager will behave the same as importing a configuration from another System Manager. Note: Models do not contain the actual IP addresses of servers. The Import functionality within the Conferencing Element Manager in System Manager provides a means for resolving which servers are which 29 Architecture System Manager Conferencing 6.0 Solution Modeller Conferencing Element Manager IPTCM Element Manager Session Manager Element Manager SFS Element Manager Presence Element Manager Solution Modeller UI Default Models

30 Avaya – Proprietary. Use pursuant to Avaya policy.30 Avaya Aura Conferencing 6.0 Solution Modeller The embedded web server is configured to listen for connections from local host only and to listen on a random port. System Requirements: – Java Development Kit version 6.0_18 or newer – 2 GB RAM – 1GB free disk space Architecture (continued)

31 Avaya – Proprietary. Use pursuant to Avaya policy.31 Avaya Aura Conferencing 6.0 Solution Modeller On start up it shows an application window with buttons to exit and to launch a browser (as it listens on a random port) The application can only be accessed from the computer on which it is running. 31 Avaya Aura Conferencing 6.0 Solution Modeller Avaya Aura TM Conferencing 6.0 Solution Modeller

32 Avaya – Proprietary. Use pursuant to Avaya policy.32 Avaya Aura Conferencing 6.0 Solution Modeller Same look and feel as System Manager Solutions component is used to manage models: – Provision servers into the model – Save / Load current model – Throw away the model and start again Conferencing Element Manager is the same as in System Manager 32

33 Avaya – Proprietary. Use pursuant to Avaya policy.33 Avaya Aura Conferencing 6.0 Solution Modeller From the Servers screen you can provision new servers into the model Servers screen also shows: – The servers that have been provisioned in the model – How many IP addresses will be required for each server 33

34 Avaya – Proprietary. Use pursuant to Avaya policy.34 Avaya Aura Conferencing 6.0 Solution Modeller You then can use the Conferencing Element Manager to configure the model Wire up each of the servers using their pseudo-IP addresses Make any necessary changes to the configuration. You can apply changes to the model as you go along – provides a layer of undo Shows the potential impact of your changes on a real system 34

35 Avaya – Proprietary. Use pursuant to Avaya policy.35 Avaya Aura Conferencing 6.0 Solution Modeller When the model is ready, you export the configuration from the Conferencing Element Manager Note: – Solution modeller works with two types of files: Conferencing Models – contains details of the provisioned servers and their configuration – Can Only Be Read by Solution Modeller Exported Configurations – contains details of the configuration of conferencing servers – Can be read and written by Both Solution Modeller and System Manager – Used to copy configurations between System Manager installations (e.g. useful for replicating a deployment, e.g. test lab, etc) – Does not contain details of the SAP codes of the provisioned servers as System Manager does not know this information. 35

36 Avaya – Proprietary. Use pursuant to Avaya policy.36 Avaya Aura Conferencing 6.0 Solution Modeller When the servers arrive on site, you import the configuration into System Manager: Then you need to resolve the IP addresses from the model against the IP addresses of the servers you actually have deployed 36 Once you complete the import wizard you will be directed to the standard Apply changes screen showing all the changes to be applied and the impact of these changes

37 Avaya – Proprietary. Use pursuant to Avaya policy.37 AURA TM CONFERENCING Logging and Alarming for Conferencing

38 Avaya – Proprietary. Use pursuant to Avaya policy.38 Logging and Alarming for Conferencing All conferencing logging components log to SMGR (via rsyslog/bridge/sal-agent) Logs and Alarms are viewable on SMGR interface SMGR Alarming Service can be configured to send received alarms as SNMP traps to a specified NMS location and port

39 Avaya – Proprietary. Use pursuant to Avaya policy.39 Log lifecycle Logging Component (Bridge, CRS, AWC, WP) rsyslog process on bridge sal-agent process on bridge SMGR /var/log/avaya/spirit.log NMS Location creates log writes to read by log alarm trap

40 Avaya – Proprietary. Use pursuant to Avaya policy.40 sal-agent sal-agent process runs on the bridge sal-agent process receives conferencing logs from rsyslog and: 1. Sends logs to SMGR Logging Service 2. Sends alarms to SMGR Alarming Service sal-agent must be manually configured from SMGR Element Manager. Need to provide: Alarming ID (unique per install) and; Managed Element ID (product specific)

41 Avaya – Proprietary. Use pursuant to Avaya policy.41 debugging – files on bridge: /var/log/avaya/spirit.config.log – sal-agent initialization log – Check for [Error] entries /opt/spirit/logging/spirit.log – sal-agent runtime log – Check for communications issues with SMGR /var/log/avaya/spirit.log – Conferencing components logs to this file (via rsyslog) – Lines in this file should be in the correct Avaya Common Logging Format (CLF) – All CLF lines should be forwarded to SMGR as a log and as an alarm

42 Avaya – Proprietary. Use pursuant to Avaya policy.42 AURA TM Conferencing Upgrading Standard Edition

43 Avaya – Proprietary. Use pursuant to Avaya policy.43 Upgrading Standard Using PLDS Back up of the configuration relevant data via System Manager Console. Use System Platform to upgrade the template with the new version: Delete the currently active template Download the new template from PLDs Install the new template same as for a new installation Restore the configuration using System Manager Console.

44 Avaya – Proprietary. Use pursuant to Avaya policy.44 Upgrading Standard Edition Customer running existing MXEE which is less than 300 ports will have an upgrade path to Standard Edition. The upgrade will be forklift so development will provide the instructions and scripts required to port data from each platform. In all cases new hardware will be required. Customer that are running 6.0 Standard that plan to upgrade to the Enterprise Edition or future release will have the option to do so. The Existing license will continue to be valid.

45 Avaya – Proprietary. Use pursuant to Avaya policy.45 AURA TM Conferencing Enterprise Edition

46 Avaya – Proprietary. Use pursuant to Avaya policy.46 Enterprise Solution 46 Standard IBM 3550 M2 / Avaya 8800 Conferencing applications installed on separate servers. CRS, Web Portal, AWC Web Conferencing Servers require System Platform. Bridges software installed via standard ISO on dedicated hardware. All other applications installed via standard installers. All configuration handle through System Manager web interface.

47 Avaya – Proprietary. Use pursuant to Avaya policy.47 System Platform Templates for Enterprise Edition 47 Template containing the CRS contains: MS Windows 2008 Server, SQL 2008, Client Registration Server, Schapi Manager, CDRLoader, Sbill, Reports, Import Utility, DCSA, CRS Front End. Template containing the Web Portal and Audio Console contains: Linux, Web Scheduling, Web Administration / Configuration, Runtime Conference Roster for conference Monitoring and Control Enterprise uses template only for the following applications. Template Containing the Web Conferencing contains: MS Windows 2008 Server, Web Collaboration CRS Template Web Portal / Audio Console Template Web Conferencing Template

48 Avaya – Proprietary. Use pursuant to Avaya policy.48 ISO/Installers/Templates for Enterprise 48 ISOOS Conferencing Enterprise Edition Bridge and Media Server Linux RHEL5 INSTALLERSOS Conferencing Enterprise Edition Web Conferencing Recording Server Windows Conferencing Enterprise Edition Web Conferencing Playback Server Windows Conferencing Enterprise Edition Conference Viewer Windows Conferencing Microsoft Integration Server Windows Conferencing Microsoft Outlook Integration Windows Conferencing IBM Lotus Sametime Integration Windows Conferencing IBM Lotus Notes Integration Windows Conferencing Bridge Talk Windows Conferencing Client Registration Server Front End Windows Conferencing Application Programmer Interfaces Windows TemplatesOS Conferencing Enterprise Edition Client Registration Server Windows Conferencing Enterprise Edition Web Portal with Audio Console Linux RHEL5 Conferencing Enterprise Edition Web Conferencing Server Windows

49 Avaya – Proprietary. Use pursuant to Avaya policy.49 Enterprise Edition Example Standby Pyramid Stack, 2 media servers Active Pyramid Stack, 2 media servers 49 Primary CRS Server Web Portal and Audio Console Server Avaya Web Conferencing (AWC) Server Conference Viewer Server Standby CRS Server System Manager Server

50 Avaya – Proprietary. Use pursuant to Avaya policy.50 Enterprise Edition Installation

51 Avaya – Proprietary. Use pursuant to Avaya policy.51 Installing Enterprise Edition ISO installation of MX Application and Media Server. Available in PLDS for download or available on CDs Single ISO will install all the components required in the bridge System Platform Templates The installation of SP templates is done exactly the same way as for Standard Edition CRS template Web Portal and Audio Console Template AWC template Templates for these machines will be available in PLDS After doing the install, the Windows machine licenses will have to be activated ISO installer for the 6200 and Media Server

52 Avaya – Proprietary. Use pursuant to Avaya policy.52 Enterprise Edition Licensing Configuration Management Logging and Alarming Identical to Standard Edition

53 Avaya – Proprietary. Use pursuant to Avaya policy.53 Enterprise Edition Upgrades

54 Avaya – Proprietary. Use pursuant to Avaya policy.54 Upgrades from an Older release to MX6.0 Considerations In a Pyramid configuration, media servers can be upgraded first one at a time to eliminate the downtime, since calls will be automatically reallocated If app server fail over is available the standby can be upgraded first, then fail over while the active is being upgraded, to reduce downtime to a maximum of 3 minutes For Avaya Plug-ins, Outlook, MS, IBM…, the configurations are not copied across in an upgrade so they will have to be done manually Upgrading from MX5.2 the hard disk will be formatted by the upgrade, so to roll back MX5.2 will have to be reinstalled, and the backed configuration applied. Prior to Upgrading, a System Manager machine should be made available, the System Manager is required for the systems to get the license

55 Avaya – Proprietary. Use pursuant to Avaya policy.55 Upgrades from an Older release to 6.0 Bridge Upgrade from 5.2 An IBM 3550 M2 machine is required for Conferencing 6.0 A script bridge-backup52. sh will be provided to back up all the information from the 5.2 bridge, which will be generated in some specific files After 5.2 is backed up, Install Aura TM Conferencing 6.0 in the IBM3550 M2 A script bridge-restore52. sh will be provided to restore the specific backup files created by bridge-backup52. sh into a 6.0 installation Start Conference 6.0 from System Manager, it will take approximately 1 minute for all the processes to start Certain configurations will not be restored automatically and will require manual intervention to apply them, the files required are backed by the bridge-backup52. sh script A roll back procedure will also be provided

56 Avaya – Proprietary. Use pursuant to Avaya policy.56 Upgrades from an Older release to MX6.0 CRS Upgrades from 5.2 CRS in Conferencing 6.0 runs in the system platform, it is also installed in new hardware, so the IBM 3550 M2 should be available System platform and the CRS template should be installed like it was a new installation The MX5.2 SQL database would have to be moved from the Windows 2005 server to the Windows 2008 Server in 6.0 Stop all applications in the CRS Executing the command MigrateToSQL2008 export.\MSSQLServer in the MX5.3 machine will run a script that backs the database in the MX5.2 machine Executing the command MigrateToSQL2008 import.\SQLExpress in the VM Avaya Conferencing 6.0 machine will restore the database in the Virtual machine Roll back is possible since we havent changed anything in the MX5.2 machine Other Apps Upgrades The rest of the APPs wont require any configuration back up, just remove the 5.2 version and install the 6.0 version No data from the other applications need to be backed up

57 Avaya – Proprietary. Use pursuant to Avaya policy.57 Upgrading Enterprise Edition MX6.0 (Bridge) To upgrade the Enterprise Edition system there will be an upgrade RPM that will manage the binaries and configuration files to be replaced or merged. The followings steps will be required to upgrade a Bare Metal Bridge: – Backup the bridge using the System Manager Console – Copy the Aura TM Conferencing Upgrade RPM to the bridge and run upgrade.sh – The script creates a backup copy of the changes so there is a script to roll back rollback.sh – After the upgrade is done, the configuration can be restore using the System Manger Console

58 Avaya – Proprietary. Use pursuant to Avaya policy.58 Upgrading Enterprise Edition Template Upgrades in Aura TM Conferencing 6.0 Using system manager just back up the configuration of the template that we want to upgrade (CRS, WEB Portal, AWC) Replace the older Aura TM Conferencing template with the newer one using System Platform Restore the configuration for that template Upgrading System Platform and System Manager There will be an upgrade procedure for the system manager server It will be provided by the System Manager Team It should be possible to upgrade System Platform without upgrading the Templates, although it is recommended to keep both SP, Templates, System Manager up to the same release for compatibility Upgrading The CRS SQL Express Edition to Standard The CRS template will be loaded with SQL 2008 Express Edition by default If the Customer wants to upgrade the database to Standard Edition then new Microsoft licenses will have to be purchased There will be a batch file based procedure to upgrade the database to the Standard Edition

59 Avaya – Proprietary. Use pursuant to Avaya policy.59 Upgrades from an Older release to MX6.0 Supported Upgrade Paths Upgrade PathUpgrade TypeCovered by Meeting Exchange 5.2 Enterprise Edition GA Aura TM Conferencing 6.0 Enterprise Edition GA manual forklift upgrade Meeting Exchange Express Edition 2.0 GA Aura TM Conferencing 6.0 Standard Edition GA manual forklift upgrade Aura TM Conferencing 6.0 Standard Edition GA Aura TM Conferencing 6.0 Enterprise Edition GA achieved via backup/restore from the System Manager Installer FS (CID ) Aura TM Conferencing 6.0 Enterprise Edition Beta Aura TM Conferencing 6.0 Enterprise Edition GA seamless upgrade via System Manager Installer FS (CID ) Aura TM Conferencing 6.0 Standard Edition Beta Aura TM Conferencing 6.0 Standard Edition GA seamless upgrade via System Manager Installer FS (CID )

60 Avaya – Proprietary. Use pursuant to Avaya policy.60 thank you Ignacio Miranda