High Availability - System Level Programming

Introduction

All communication between the HARC configuration and the devices, external interfaces, and applications is expected to use the Cluster IP Address.  If you have followed the addressing strategy identified in Step Two - IP Address Planning of the High Availability - Installation and Configuration documentation, then no changes to the programming of these system components should be required.  If, however, you have not followed that strategy, then the following section discusses the changes required to these system level components.

System Functionality and Programming in High Availability mode

Basic UCx Telephony

Once the systems have been configured as a High Availability cluster, all communication to the cluster will take place through the cluster IP Address.  Also, note that any PBX programming already performed on the Primary Server will be propagated to the Secondary node after creating the cluster, and any programming on the Secondary Node will be lost.  As noted in the High Availability - Installation and Configuration section of this document, it is recommended that the programming of both nodes be reviewed and a backup created prior to configuring the High Availability cluster.

Care must also be be taken in configuring peripheral system components such as IP phones, gateways, and 3rd party devices to make sure that the cluster IP address is used.

IP Phone Programming

All E-MetroTel Infinity phones using the XStim protocol along with all Nortel Unistim IP phones must be programmed with the cluster IP address as the S1 server.  The phones can be programmed as required for Configuring Devices and Extensions for SRG Operation.

SIP Telephone Programming

SIP phones must be programmed with the cluster IP address or DNS-resolvable domain name.

User Portal

Users should be instructed to connect to the User Portal using the IP address or DNS-resolvable domain name of the cluster configuration.

SIP Trunks

SIP Trunks must be programmed with the IP address or DNS-resolvable domain name of the cluster configuration.

DGS, DGS2, and DSM16 Peripherals

These devices must be programmed with the cluster IP address as the Primary Server IP Address on the Call Server page in the Gateway tab.  These devices can also be programmed as required for Configuring Devices and Extensions for SRG Operation.

Peripherals

Galaxy100 FXS8P

The SIP Server Address field on the SIP Server page of the Web Management system must be programmed with the cluster IP address. 

External Routing or Networking Devices

Any port forwarding, firewall rules or other networking interfaces designed to enable external devices to communicate with the UCx for management, SIP, etc. must be programmed with the cluster IP address. 

Security

Firewall Rules

Once the Firewall Rules in the Security tab are configured using the Web-based Configuration Utility, they will apply regardless of which server is in Active mode.

Certificates

To increase security of the cluster, certificates should be created using the Certificates Page in the Security tab of the IP address of the cluster configuration.

Applications

External CDR Interface

The MySQL Client Application Hostname / IP field must be programmed with the IP address or DNS-resolvable domain name of the cluster configuration..

Enhanced Archive

If you are using the Enhanced Archive Server license (EAv2), the Archive Server Configuration page in the Administration tab of the Enhanced Archive Server web management interface must be programmed with the cluster IP address.If you are using the UCx Enhanced Archive (Call Recording Backup) application license (EA), there typically is no change required on the FTP server as the UCx sends files to the server.

Call Center Reporting

There are no impacts on IP addressing with respect to the UCx Call Center Reporting capabilities.

Call Center

There are no impacts on IP addressing with respect to the UCx Call Center Reporting capabilities.

Hospitality

Both the PMS Server and the HOBIC server must be programmed with the cluster IP address.

InfinityOne

There are no impacts on IP addressing with respect to InfinityOne. The subdomain associated with the SSL certificate should be forwarded to the the customer's public address, and the customer router shuold have port 21326 (default setting) forwarded to the cluster IP address.

Microsoft Lync

This must be programmed with the IP address or DNS-resolvable domain name of the cluster configuration.

Notifier

To manage and configure the Notifier application, you must use the cluster IP address with Port 4001 (eg. https://192.168.1.202:4001). 

TAPI Application

The Host IP field in the UCX TAPI Service Provider configuration screen must be programmed with the cluster IP address.

UCx APIs

If you have applications designed to use any of the UCx APIs it must be programmed with the cluster IP address.

Scheduled Announcement

There are no impacts on Scheduled Announcement with respect to IP addressing.

Wallboard

The Wallboard application is now an integral part of the UCx InfinityOne application.  Please refer to the above notes with respect to its configuration in a High Availability cluster.

There are no impacts on IP addressing with respect to the UCx Call Center Reporting capabilities.

 
Page Tags: 
high availability
ha
harc
active standby