High Availability Installation
|
Warning: Avaya IX Messaging High Availability must only be installed by trained and certified personnel. |
This document provides the installation procedure for Avaya IX Messaging with a High Availability Server (Primary, Secondary & Consolidated). The purpose of a High Availability Installation is operational continuity, in which the array of servers provides your organization with complete Messaging functionality in case of a voice server failure. The Consolidated server synchronizes the voice servers (Primary and all Secondaries) and maintains the database.
|
Warning: The instructions found in this guide cannot be guaranteed to work for all installations since each site is unique. Some problems may arise even if you follow these instructions precisely. Therefore, use this document as a reference for your own configuration, making the changes appropriate to your site's specific requirements. |
If one of the voice servers (Primary or Secondary) fails, traffic if routed away from that server to the still active ones.
•The license is maintained by the Primary Server. If it fails, you have 28 days to restore the connection before the system will revert to demo mode.
•If the Consolidated Server fails, the remaining voice servers will continue to process voice traffic, but UM services (calendar sync, Gmail integration, transcription, etc.) will not be available.
|
Requirements |
Details |
|---|---|
|
License |
A Full License for 10.8 that includes HA. |
|
Software |
For details on Messaging 10.8 Hardware and Software requirements please consult the Technical Operating Guidelines. |
|
Operating System |
Windows Server 2012 or 2012 R2 Windows Server 2016 Windows Server 2019 |
|
Important: Microsoft Windows is not provided with any version of IX Messaging. The customer must install and fully update a suitable, licensed version of Windows onto the hardware platform before proceeding with the Avaya IX Messaging software installation. |
|
Important: In an HA installation, all servers must have the same time zone set under Windows Date / Time settings. If the servers are configured for different time zones, the timestamps will not play correctly. |
A High Availability installation requires a minimum of 3 computers, each setup as a server. One server is defined as the Primary Voice Server. Between 1 and 19 additional servers are designated as Secondary Voice Servers. Controlling traffic flow, synchronization, load balancing and failover is a single Consolidated Server (also called the Database Server). A Secondary Consolidated Server can be included for additional failover security.
|
Note: Avaya IX Messaging should only be installed on dedicated servers specifically intended for the purpose. Sharing system resources with other applications may prevent Messaging from functioning properly. |
|
Note: Avaya IX Messaging has only been validated on Windows in English and in French. Other varieties of Windows may not work as intended. |
|
Warning: Once all of the HA servers (Consolidated, Primary and all Secondaries) have been installed, it is important to perform a full synch of all data. Attempting to login to the servers before the synch is complete will corrupt the database preventing all logins on all servers. Refer to Verifying File Sync for complete details. |
Antivirus, Firewall and Automatic Updates
It is recommended that any antivirus and firewall applications currently active on the server computer be disabled during installation. It is also necessary to turn off Automatic Updates during the installation.
Any other resource intensive applications or monitoring tools which may cause a conflict with the installation should also be disabled during the installation process.
In an HA installation, all servers must have the same time zone set under Windows Date / Time settings. If the servers are configured for different time zones, the timestamps will not play correctly.
Disabling User Access Control Notification
In order to install Avaya IX Messaging on a Windows Server environment, you must turn off the UAC notification feature on the local Admin user which will be utilized with Messaging.
1.Open Control Panel > User Accounts.
2.Click Turn User Account Control on or off.
3.Disable Use User Account Control then click OK.
4.You will be prompted to restart your computer.
Click Restart Now to restart the system.
1.Open Control Panel > User Accounts.
2.On this screen, click
Change User Account Control settings.
3.Pull the slider to the bottom or its range,
until Never notify me when:... is selected.
4.Click OK.
5.Restart the computer.
Ensure that all the necessary items are installed on the system before proceeding with Messaging installation.
|
Important: In an HA installation, all servers must have the same time zone set under Windows Date / Time settings. If the servers are configured for different time zones, the timestamps will not play correctly. |
Server Manager Configuration: Win 2016/2019 (All Servers)
If your servers have Windows 2016 or 2019 installed, use this section. If they are using Windows 2012, go to here.
Perform the following steps on ALL servers; Primary, Consolidated, and all Secondaries.
|
Consolidated: Where necessary, special instructions specific to the Consolidated Server setup are provided where there is a difference in the process from the Primary and Secondary Servers. |
|
Note: Some of these steps may require additional files from the Windows disk or other storage location. |
1.From the Server Manager Dashboard, click Add roles and features.
If this screen is hidden, go to View and select Show Welcome Tile.
2.Click Next.
3.Leave the default settings as they are. Click Next.
4.Leave the default settings as they are. Click Next.
5.Enable Fax Server. When prompted, select Add Features.
6.Enable Web Server (IIS). When prompted, select Add Features. Click Next.
7.On the Features panel, open .NET Framework 3.5 Features and enable HTTP Activation. When prompted, select Add Features. Click Next.
8.Optional: If you plan to use SNMP Alarms with Messaging, the SNMP Service must be added to Windows before the program can be installed.
If SNMP Alarms are required, scroll down and enable SNMP Service.
If SNMP Alarms are not required, skip this step.
9.On the Fax Server screen, click Next.
10.On the Print and Document Services screen, click Next.
11.No changes are required here. Click Next.
12.On the Web Server Role (IIS) screen, click Next.
13.Under Web Server > Common HTTP Features, enable HTTP Redirection.
14.Under Web Server > Security, enable Windows Authentication.
15.Under Web Server > Application Development, enable .NET Extensibility 3.5, .NET Extensibility 4.6, ASP, ASP .NET 3.5, ASP .NET 4.6, CGI, ISAPI Extensions, ISAPI Filters and WebSocket Protocol.
Under FTP Server, enable FTP Service.
16.Under Management Tools > IIS 6 Management Compatibility, enable all items.
Click Next when ready.
17.Review the selections here. When ready to proceed, click Install.
18.Windows will now start the installation process for the chosen items. This process may take a while.
|
Note: This window can be closed without interrupting the installation procedure |
19.Once all changes are complete, Restart the server.
The next section covers Roles and Services for Windows 2012. You can skip ahead to here, IIS Certificates (All Servers).
Server Manager Configuration: Win 2012 (All Servers)
If your servers have Windows 2012 installed, use this section. If you are using Windows 2016 or 2019, go to here instead.
Perform the following steps on ALL servers; Primary, Consolidated, and all Secondaries.
|
Consolidated: Where necessary, special instructions specific to the Consolidated Server setup are provided where there is a difference in the process from the Primary and Secondary Servers. |
|
Note: Some of these steps may require additional files from the Windows disk or other storage location. |
1.From the Server Manager Dashboard, click Add roles and features.
If this screen is hidden, go to View and select Show Welcome Tile.
2.Click Next.
3.Leave the default settings as they are. Click Next.
4.Leave the default settings as they are. Click Next.
5.Enable the Application Server, Fax Server and Web Server (IIS) checkboxes.
Click Next.
|
Note: Throughout this installation, whenever you are prompted to confirm additions, always select Add Features. 
|
6.Enable the .NET Framework 3.5 Features checkbox. Click Next.
7.Optional: If you plan to use SNMP Alarms with Messaging, the SNMP Service must be added to Windows before the program can be installed.
If SNMP Alarms are required, scroll down and enable SNMP Service.
If SNMP Alarms are not required, skip this step.
8.Review the information, then click Next.
9.Ensure that HTTP Activation, under Windows Process Activation Service Support is enabled. Click Next.
10.On the Fax Server screen, click Next.
11.On the Print and Document Services screen, click Next.
12.No changes are required here. Click Next.
13.On the Web Server Role (IIS) screen, click Next.
14.Open Web Server > Common HTTP Features. Enable Directory Browsing, HTTP Errors, Static Content and HTTP Redirection.
Scroll down to Security, and enable Windows Authentication.
Under Application Development, enable .NET Extensibility 3.5, .NET Extensibility 4.5, ASP, ASP .NET 3.5, ASP .NET 4.5, CGI, and WebSocket Protocol.
Locate FTP Server and enable FTP Service.
Enable all options under Management Tools > IIS 6 Management Compatibility.
Click Next when ready.
15.Review the selections here. When ready to proceed, click Install.
16.If prompted to provide the Windows disk to load the files, click Specify an alternate source path and direct it to the appropriate drive.
|
Hint: This is particularly important for virtual machine installations where there may not be a drive configured locally. |
17.Windows will now start the installation process for the chosen items. This process may take a while.
|
Note: This window can be closed without interrupting the installation procedure |
18.Once all changes are complete, Restart the server.
IIS Certificates (All Servers)
The site administrator must install either a self-signed certificate, or a certificate purchased from a Certification Authority.
It is not necessary to install both types of certificate.
|
Note: Corporate security protocols may require the use of certificates purchased from an appropriate authority. High-security (JITC) installations always require a CA issued certificate for the Encrypted File System (EFS). |
Additional information on installing certificates onto the voice server can be found here:
https://technet.microsoft.com/en-ca/library/cc753127(v=ws.10).aspx
Once the certificates have been installed, continue with IIS Certificate Bindings.
To enable an HTTPS connection, a certificate has to be installed on the voice server.
The HTTPS protocol must be enabled, and HTTP disabled.
1.On the computer that functions as the web server, open the IIS Manager console.
Select the local computer. Open Server Certificates in the right-hand pane.
2.Right-click in the right-hand pane and choose Import from the pop-up menu.
3.Enter the path to the certificate file and the password. Select Personal as the Certificate Store. Click OK.
4.Go to Sites > Default Web Site.
Click Bindings....
5.Add the HTTPS binding type.
Set the IP Address to All Unassigned. Leave Port at its default.
Change SSL Certificate to the certificate name installed above.
Click OK.
6.Remove HTTP from the list of bindings.
Click Close.
Install Microsoft .Net Framework 4.7.2
Perform the following steps on all servers; Primary, Consolidated, and all Secondaries.
Avaya IX Messaging requires Microsoft .Net Framework version 4.7.2 to be installed to support various features within the program. If it has not already been installed, the administrator must download it and install it manually.
|
Note: .Net Framework 4.7.2 is not installed by default. It may be part of Windows updates, optional updates, or not provided at all. Follow these instruction is it is not installed on your system, or if you do not know if it has been installed. |
1.Open a web browser and go to the Microsoft web site. Search for .Net Framework 4.7.2 and install the application on the server. For example:
https://support.microsoft.com/en-us/help/4054531/microsoft-net-framework-4-7-2-web-installer-for-windows .
2.Download the file to your server drive. When ready, run the program to install this feature.
3.When finished, restart the server.
|
Important: The Primary Server MUST be the first server to be setup since the Primary holds the license for your site. The Consolidated Server should be next, and only when the database has synchronized between them should the Secondary Servers be installed. See Verifying File Sync on page 254. |
|
Important: In an HA installation, all servers must have the same time zone set under Windows Date / Time settings. If the servers are configured for different time zones, the timestamps will not play correctly. |
|
Note: Make sure that all of the necessary Services for your operating system have been installed before proceeding with the installation. Refer to the appropriate section of the Server Installation Guide for details. Also make sure that Windows Firewall is disabled, and that Windows Automatic Update is turned off. |
1.Download the installation file from (see chapter 4). Run the file (double-click) to extract the contents. Specify the location on your hard drive where you want to save the files.
2.In the extraction folder, run Setup.exe as administrator to install Avaya IX Messaging onto the Primary server.
3.Once the Windows components have been verified, click Next to begin the installation.
|
Note: The installer will automatically install the necessary packages at the beginning of the installation if they do not already exist on the system. These packages may include Sentinel Protection, Microsoft Visual C++ Redistributable and Microsoft .Net Framework 4.5. This process may take a while depending on the required components. |
|
Note: Clicking on the Documentation button will provide you with the default set of PDF documents which comprehensively cover most aspects of Messaging. They can also be downloaded from resources.zang.io in both PDF and HTML format. |
4.Enter the DCOM user info (domain user account which has local administrator rights). This is required by services which use local administrator rights.
Click OK after entering the credentials.
|
Hint: Wherever possible, this password should be setup with no expiration date. If the password does expire, then it must be changed on every computer that uses it. Many services will be unavailable until the change has been made everywhere. |
5.Review all the license agreements, click Continue.
When ready, enable I accept the license agreement.
Click Next to continue.
6.You will be asked to select the destination of the installation. You may change the hard drive destination through the drop down menu. By default, the installation will create a UC folder on the C drive.
Click Next to continue.
|
Note: It is highly recommended that you install the program to a drive other than C to prevent any conflicts or performance issues. |
7.Enable Multiple UC Servers in High Availability.
Click Next.
Single UC Server: When operating Messaging on a single server computer.
Multiple UC Servers in High Availability: When running Messaging in High Availability mode for redundancy.
IX Messaging Cloud Gateway: Gateway allows end-to-end synchronization between the Avaya Aura Messaging server and Google's Gmail using Avaya IX Messaging message sync and the CSE. Refer to chapter 15, Install and Configure Cloud Gateway for complete details.
8.Select Primary Voice Server.
Click Next.
9.This screen is a reminder that HA installations require an HA license. Click OK.
10.Select the license type you will using for this installation.
Most sites will use the WebLM License option.
|
Note: If you select Messaging, go to chapter 12, Installing the Messaging License. When finished, return here and continue the installation from step 13. Skip step 11 through 12. |
|
Warning: It is essential that the system/PC clock be properly set before activating the license. Any subsequent changes to the clock can adversely affect or terminate the license. |
11.The License Upgrade Utility program opens and prompts you to enter the IP Address for the computer that houses the WebLM license engine.
Enter the address in the space provided, then click OK.
|
Important: This step requires that the Web License Manager has been installed and configured on the license server computer. See Installing the WebLM License and Server on page 437. |
12.The utility will retrieve your license details from the server and display them here. Review the license details and click Exit when ready.
|
Note: The number of voice ports is calculated based upon your license. |
13.Select the Components required at your site.
Click Next.
|
Note: If the Dialogic SR140 fax software will be used with this installation, ensure that the Hardware Fax Driver option is enabled here. |
14.This screen shows all of the Windows roles and features that Messaging requires to operate properly.
|
Note: This screen will only appear if one or more required components are not installed on the computer. |
For all items that are not checked, return to Windows and add any missing pieces to the operating system.
Click Next when finished or to refresh the display.
|
Note: The installation will not continue until all of the required components have been added to Windows. |
15.This screen shows IIS settings that Messaging requires to operate properly.
|
Note: This screen will only appear if one or more of the required settings has not been made on the computer. |
For all items that are not checked, return to the IIS Manager in Windows and set these options as required.
Click Next when finished or to refresh the display.
|
Note: The installation will not continue until all of the required IIS settings have been made. |
16.Select your PBX Brand then click Next.
17.Select your PBX model from the dropdown menu.
Click Next.
18.Enter the IP Address for the Consolidated Server.
Click Next.
19.Enter the number of ports your system will use.
Click Next.
20.Enter the primary location from which most telephone calls will be placed. This will normally be where the corporate office is situated. Additional dialing locations and rules may be defined after the installation is complete.
Select the country from the dropdown menu, and enter the area code in the space provided.
Click Next to continue.
|
Note: If the Phone and Modem Settings under Windows Control Panel have already been configured, this step will not appear. The values entered there will be used automatically. |
21.Create and verify a UC IIS User Password. This is used when logging into any associated web applications, such as Web Access.
22.The preliminary information required for installation is now complete.
Click Next.
23.The selected components will now be installed. This process may take a while.
24.If you are warned about components being in use, either use the Automatically Close option or manually close the process which is interfering with the installation.
Click OK when ready.
25.After all the components are copied, you may be asked to provide the settings for the PBX that you have chosen. Since this process varies greatly from system to system, please ensure that you configure your site’s PBX exactly as required.
26.In this section of the installation wizard you will be asked to provide additional settings for SIP integration.
Click Next to continue.
27.Fill out all required information. The PBX and the Number of Channels fields are automatically populated. Enter the IP Address of the PBX.
Trunk is selected by default, and is the best option for most installations.
Select Extension if it is available through the PBX, and if Pre-Paging is required. If Extension is enabled, enter the Start Extension Number established during PBX setup.
Click Next when ready.
28.Confirm the information then click Finish.
|
Note: Depending on the type of SIP integration you’ll be using, you may have to fine tune the settings from the SIP Configuration Tool in order for the system to function properly. The SIP Configuration Tool can be found in the Messaging programs folder after installation. |
29.After all the components are copied, you may be asked to provide the settings for the PBX that you have chosen. Since this process varies greatly from system to system, please ensure that you configure your site’s PBX as required.
30.On the SSO Configuration screen, enable Legacy SSO. From the dropdown menu, enable the Providers that you want your clients to be able to use to access Web Admin, Messaging Admin, Web Access, and Web Reports. Items that are disabled will not appear during client login.
|
Note: For more information on the SSO Options, see chapter 25 on page 651: Single Sign-On (SSO). |
31.Click Finish to restart the server.
If you wish to restart your computer at a later time, disable the Restart check box then click Finish.
32.This alert is to remind you to properly share the UC installation folder (see here for details).
Click OK to restart the computer.
|
Warning: Once all of the HA servers (Primary, Consolidated, and all Secondaries) have been installed, it is important to perform a full synch of all data. Attempting to login to the Primary or Secondary servers before the synch is complete will corrupt the database preventing all logins on all servers. Refer to Verifying File Sync for complete details. |
|
Important: The Primary Server MUST be the first server to be setup since the Primary holds the license for your site. The Consolidated Server should be next, and only when the database has synchronized between them should the Secondary Servers be installed. See Verifying File Sync on page 254. |
|
Important: In an HA installation, all servers must have the same time zone set under Windows Date / Time settings. If the servers are configured for different time zones, the timestamps will not play correctly. |
|
Note: Make sure that all of the necessary Services for your operating system have been installed before proceeding with the installation. Refer to the appropriate section of the Server Installation Guide for details. Also make sure that Windows Firewall is disabled, and that Windows Automatic Update is turned off. |
1.Download the installation file (see chapter 4). Run the file (double-click) to extract the contents. Specify the location on your hard drive where you want to save the files.
2.In the extraction folder, run Setup.exe as administrator to install Avaya IX Messaging onto your Consolidated server.
3.Once the Windows components have been verified, click Next to begin the installation procedure.
|
Note: The installer will automatically install the necessary packages at the beginning of the installation if they do not already exist on the system. These packages may include Sentinel Protection, Microsoft Visual C++ Redistributable and Microsoft .Net Framework 4.5. This process may take a while depending on the required components. |
|
Note: Clicking on the Documentation button will provide you with the default set of PDF documents which comprehensively cover most aspects of Messaging. They can also be downloaded from resources.zang.io in both PDF and HTML format. |
4.Enter the DCOM user info (domain user account which has local administrator rights). This is required by services which use local administrator rights.
Click OK after entering the necessary credentials.
|
Hint: Wherever possible, this password should be setup with no expiration date. If the password does expire, then it must be changed on every computer that uses it. Many services will be unavailable until the change has been made everywhere. |
5.Review all the license agreements and select
I accept the license agreement.
Click Next to continue.
6.You will be asked to select the destination of the installation. You may change the hard drive destination through the drop down menu. By default, the installation will create a UC folder on the C drive.
Click Next to continue.
|
Note: It is highly recommended that you install the program to a drive other than C to prevent any conflicts or performance issues. |
7.Enable Multiple UC Servers in High Availability.
Click Next.
Single UC Server: When operating Messaging on a single server computer.
Multiple UC Servers in High Availability: When running Messaging in High Availability mode for redundancy.
IX Messaging Cloud Gateway: Gateway allows end-to-end synchronization between the Avaya Aura Messaging server and Google's Gmail using Avaya IX Messaging message sync and the CSE. Refer to chapter 15, Install and Configure Cloud Gateway for complete details.
8.Select Consolidated Database/File Server.
Click Next.
9.Enter the IP Address of the Primary Server, then click Next.
10.Select the Components required at your site.
Click Next.
11.This screen shows all of the Windows roles and features that the Consolidated server requires to operate properly.
|
Note: This screen will only appear if one or more required components are not installed on the server. |
For all items that are not checked, return to Windows and install any missing components into the operating system.
Click Next when finished or to refresh the display.
|
Note: The installation will not continue until all of the required components have been added to the server. The screen does not refresh until you click Next. |
12.Select your PBX Brand then click Next.
13.Select your PBX model from the dropdown menu.
Click Next.
14.Unless the Primary Server has been upgraded from a Single Server installation, choose No.
Click Next.
15.Select the Email Server Type from the list of available options. This allows the system to set basic parameters which help to improve performance and reliability.
16.Create and verify a UC IIS User Password. This is used when logging into any associated web applications, such as Web Access.
17.Enter a password to provide administrator only access to the system. This account password is used to configure the many elements of the system.
|
Hint: The password cannot be left blank. It must contain both letters and numbers (no special characters), and should be at least 6 characters long. |
|
Warning: Once all of the HA servers (Consolidated, Primary and all Secondaries) have been installed, it is important to perform a full synch of all data. Attempting to login to the Primary or Secondary servers before the synch is complete will corrupt the database preventing all logins on all servers. Refer to Verifying File Sync for complete details. |
18.Enter the primary location from which most telephone calls will be placed. This will normally be where the corporate office is situated. Additional dialing locations and rules may be defined after the installation is complete.
Select the country from the dropdown menu, and enter the area code in the space provided.
Click Next to continue.
|
Note: If the Phone and Modem Settings under Windows Control Panel have already been configured, this step will not appear. The values entered there will be used automatically. |
19.Create a new user administrator account on the local computer. Type and confirm a password for the new account.
Click Next to continue.
20.Choose either Yes or No to determine whether the system will apply General Data Protection Regulation (GDPR) compliance procedures to your data.
With this option enabled, users and callers are notified that personal information will be collected. This information can also be completely removed from the system upon request.
21.The preliminary information required for installation is now complete.
Click Next.
22.The selected components will now be installed. This process may take a while.
23.On the SSO Configuration screen, enable Legacy SSO. From the dropdown menu, enable the Providers that you want your clients to be able to use to access Web Admin, Messaging Admin, Web Access, and Web Reports. Items that are disabled will not appear during client login.
|
Note: For more information on the SSO Options, see chapter 25 on page 651: Single Sign-On (SSO). |
24.If you are warned about components being in use, either use the Automatically Close option or manually close the process which is interfering with the installation.
Click OK when ready.
25.After all the components are copied, you may be asked to provide the settings for the PBX that you have chosen. Since this process varies greatly from system to system, please ensure that you configure your site’s PBX exactly as required.
26.Click Finish to restart the server.
If you wish to restart your computer at a later time, disable the Restart check box then click Finish.
27.This alert is to remind you to properly share the UC installation folder (see for here details).
Click OK to restart the computer.
|
Important: Do not proceed with any Secondary Server installations until the synchronization between the Consolidated and Primary Servers has completed or the database may become corrupted. |
|
Important: The Primary Server MUST be the first server to be setup since the Primary holds the license for your site. The Consolidated Server should be next, and only when the database has synchronized between them should the Secondary Servers be installed. See Verifying File Sync on page 254. |
|
Important: In an HA installation, all servers must have the same time zone set under Windows Date / Time settings. If the servers are configured for different time zones, the timestamps will not play correctly. |
|
Note: Make sure that all of the necessary Services for your operating system have been installed before proceeding with the installation. Refer to the appropriate section of the Server Installation Guide for details. Also make sure that Windows Firewall is disabled, and that Windows Automatic Update is turned off. |
1.Download the installation file (see chapter 4). Run the file (double-click) to extract the contents. Specify the location on your hard drive where you want to save the files.
2.In the extraction folder, run Setup.exe as administrator to install Avaya IX Messaging onto all of your Secondary servers.
3.Once the Windows components have been verified, click Next to begin the installation.
|
Note: The installer will automatically install the necessary packages at the beginning of the installation if they do not already exist on the system. These packages may include Sentinel Protection, Microsoft Visual C++ Redistributable and Microsoft .Net Framework 4.5. This process may take a while depending on the required components. |
|
Note: Clicking on the Documentation button will provide you with the default set of PDF documents which comprehensively cover most aspects of Messaging. They can also be downloaded from resources.zang.io in both PDF and HTML format. |
4.Enter the DCOM user info (domain user account which has local administrator rights). This is required by services which use local administrator rights.
Click OK after entering the necessary credentials.
|
Hint: Wherever possible, this password should be setup with no expiration date. If the password does expire, then it must be changed on every computer that uses it. Many services will be unavailable until the change has been made everywhere. |
5.Review all the license agreements and enable
I accept the license agreement.
Click Next to continue.
6.You will be asked to select the destination of the installation. You may change the hard drive destination through the drop down menu. By default, the installation will create a UC folder on the C drive.
Click Next to continue.
|
Note: It is highly recommended that you install the program to a drive other than C to prevent any conflicts or performance issues. |
7.Enable Multiple UC Servers in High Availability.
Click Next.
Single UC Server: When operating Messaging on a single server computer.
Multiple UC Servers in High Availability: When running Messaging in High Availability mode for redundancy.
IX Messaging Cloud Gateway: Gateway allows end-to-end synchronization between the Avaya Aura Messaging server and Google's Gmail using Avaya IX Messaging message sync and the CSE. Refer to chapter 15, Install and Configure Cloud Gateway for complete details.
8.Select Secondary Voice Server.
Click Next.
9.Enter the number for this Secondary Server. Each Secondary server must have a unique identifying number assigned between 2 and 20.
Click Next.
|
Note: The Master Server is automatically assigned # 1. |
10.Enter the IP Address of the Primary Voice Server.
Click Next.
11.Select the Components required at your site.
Click Next.
|
Note: If the Dialogic SR140 fax software will be used with this installation, ensure that the Hardware Fax Driver option is enabled here. |
12.Select your PBX Brand then click Next.
13.Select your PBX model from the dropdown menu.
Click Next.
14.Enter the IP Address for the Consolidated Server.
Click Next.
15.Enter the number of ports your system will use.
Click Next.
16.Create and verify a UC IIS User Password. This is used when logging into any associated web applications, such as Web Access.
17.The preliminary information required for installation is now complete.
Click Next.
18.The selected components will now be installed. This process may take a while.
19.If you are warned about components being in use, either use the Automatically Close option or manually close the process which is interfering with the installation.
Click OK when ready.
20.After all the components are copied, you may be asked to provide the settings for the PBX that you have chosen. Since this process varies greatly from system to system, please ensure that you configure your site’s PBX exactly as required.
21.On the SSO Configuration screen, enable Legacy SSO. From the dropdown menu, enable the Providers that you want your clients to be able to use to access Web Admin, Messaging Admin, Web Access, and Web Reports. Items that are disabled will not appear during client login.
|
Note: For more information on the SSO Options, see chapter 25 on page 651: Single Sign-On (SSO). |
22.Click Finish to restart the server.
If you wish to restart your computer at a later time, disable the Restart check box then click Finish.
23.This alert is to remind you to properly share the UC installation folder (see here for details).
Click OK to restart the computer.
|
Warning: Once all of the HA servers (Consolidated, Primary and all Secondaries) have been installed, it is important to perform a full synch of all data. Attempting to login to the Primary or Secondary servers before the synch is complete will corrupt the database preventing all logins on all servers. Refer to Verifying File Sync for complete details. |
Once Primary and Consolidated servers have been installed, it is important to complete a full synch of all data before attempting to add any Secondary servers. Once a each Secondary has been attached, it too must be fully synchronized. Attempting to login to the Primary or Secondary servers before the synchronization is complete will corrupt the database preventing all logins on all servers.
Data synchronization will begin once the sync service has been started on each server. On the Consolidated server, it is MobiLink - Consolidated. On the Primary and all Secondary servers, this service called SQL Anywhere - MobiLink Remote.
Open the services window and check that the named services are running on each server. If any are not active, then select it and press Start.
Use any text editor (e.g. Windows Notepad) to open the Mobiclient.log file in the DB/Logs folder of the UC installation directory.
The message Completed processing of download stream will appear once the synch has finished.
It is necessary to share the UC installation folder so that all of the programs and users have the required access.
The following user accounts require full permissions to the UC folder:
UCIIS (local) - this is called UCIISUser.
DCOM (user) - the name of the domain user with admin rights on the local machine.
Follow this procedure on the Primary, the Consolidated, and on each Secondary server on the system.
Also share the folder if you are using a Remote Web Server.
If you are using Remote CSE Servers, the folder only needs to be shared with the DCOM user.
1.Locate the UC folder in Windows Explorer, then Right-click > Properties > Sharing.
2.Click Advanced Sharing. Enable the Share this folder checkbox.
3.Click Permissions, and Add the required users, giving each Full control of the folder.
Remove the user Everyone.
4.Click Apply and return to the Windows desktop.
By default, during a failover condition, the Message Waiting Indicator (MWI) functions are not automatically re-routed to the alternate servers.
You can manually enable this functionality.
|
Note: This configuration is optional. |
•Add a new line to the ETSIPSERVICE.INI file found in /UC/Configuration folder.
•Open the INI file with a text editor (e.g. Notepad). Locate the PBX section and append the following line:
Fail Over=Yes
•Ensure that Keep Alive is also enabled ( Keep Alive=Yes ).
•Verify that there are at least 2 IP addresses listed under IP. These are for your PBXs and can be entered here if necessary, or configured through the SIP Configurator.
•Save the file and reboot the server.
|
Note: This must be done on each voice server (the Primary and all Secondary servers) in the array. |
An Avaya IX Messaging HA installation can be spread across a geographically distributed network. Geo Redundancy allows a section of the network in one part of the world to go offline without affecting the remaining elements.
Installing Messaging with Geo Redundancy proceeds the same way as it does with any other HA install, but with some of the servers existing in other locations.
Geo Redundancy has the following network connection requirements to operate properly.
•All Messaging servers must be on the same network as the PBX.
•All servers must have a minimum 1Gbps connection to the network.
•The maximum round-trip latency for optimum performance is 10ms between servers, with an acceptable tolerance up to 60ms.
•The maximum round-trip latency between the voice servers and the PBX must be no more than 200 ms.
•Optimal round-trip latency is a maximum of 150 ms.
•The path of connectivity must have 20Mbps guaranteed bandwidth with no steady-state congestion.
•At all times, the LAN network connection must provide a min guaranteed 20Mbps upload / download speed.
Contact your dealer if you have any further questions.
Adding Secondary Voice Servers
As your communication traffic expands, it may become necessary to add more Secondary Voice Servers to a High Availability environment to maintain adequate response times.
|
Note: The following procedure only applies to adding voice servers to the system. |
1.Create a new voice server (virtual or physical) with the same hardware parameters as the existing units.
2.Install and configure Windows (Roles and Features) as was done with the original voice servers.
3.Install Avaya IX Messaging on the new machine, selecting Multiple UC Servers in High Availability when prompted.
4.Continue with the installation and select Secondary Voice Server when prompted.
5.Continue with the installation. At the prompt, enter a number for the new server.
Each Secondary server must have a unique identifying number assigned between 2 and 20.
|
Note: The Primary Server is automatically assigned # 1. |
6.Complete the remaining steps of the Secondary Voice Server installation. When finished, reboot the new server.
7.When the new server has restarted, stop the DBWatcher service on both the new Secondary Voice Server and on the Consolidated Server. This will allow the new server to synchronize all data with the HA system.
8.When the synchronization has completed, restart the DBWatcher service on both the new Secondary Voice Server and on the Consolidated Server.
The new Secondary Voice Server has been added to the HA environment.