I N S T A L L A T I O N M A N U A L

Emergency Notification Server

Version 2

Alcatel-Lucent Enterprise Services Page 1/41

 Emergency Notification Server - Installation Manual

Index Table

Entries below are hyperlinked. Click on the required entry, to move to the page where it is dealt
with.

Contents
1 Document history 4
2 Scope 5
2.1 Overview ............................................................................................... 5
2.1.1 The Application – What it means to the User ....................................................... 5
2.1.2 Purpose of this guide ................................................................................... 5

3 Glossary 6
4 Introduction 7
4.1 Intended Readership ................................................................................. 7
4.2 Applicability Statement ............................................................................. 7
4.3 Overview of this manual ............................................................................ 7
4.4 Licensing ................................................................................................ 7
4.5 Technical Support .................................................................................... 8

5 Hardware & Software - Minimum Requirements 9

5.1 Hardware Configuration ............................................................................. 9
5.2 System Configuration ................................................................................ 9
5.3 Prerequisite ............................................................................................ 9
5.4 Software Licensing Requirements ................................................................10

6 Connectivity - Illustrated 11
6.1 Standalone PBX and single ENS ...................................................................12
6.2 Standalone duplicated PBX and single ENS .....................................................13
6.3 Standalone duplicated PBX and duplicated ENS ...............................................14
6.4 PBX Network and duplicated ENS.................................................................15

7 Installation 16
7.1 Red Hat Enterprise Linux 6U5 64 bits installation ............................................16
7.2 ENS installation .......................................................................................16

8 Upgrade procedure 17

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 2/41

 Emergency Notification Server - Installation Manual

8.1 Upgrade ENS Release < R1.9.......................................................................17

8.2 Upgrade R1.9 <= ENS Release <= R1.24 .........................................................17
8.2.1 Backup Procedure...................................................................................... 17
8.2.2 Restore procedure ..................................................................................... 18
8.3 Upgrade ENS Release >= R2........................................................................19

9 High Availability 20
9.1 Trunk configuration on PBX with HA installation .............................................21
9.1.1 ENS HA with one trunk on one PBX .................................................................. 21
9.1.2 ENS HA with 2 trunks on one PBX .................................................................... 22
9.1.3 ENS HA with 2 trunks on 2 different PBXs .......................................................... 22
9.2 High Availability installation .......................................................................24
9.2.1 New ENS HA installation .............................................................................. 24
9.2.2 HA installation on an existing ENS ................................................................... 27

10 Appendixes 39
10.1 Appendix – I : Table of Diagrams .......................................................39
10.2 Appendix – II : Table of Screenshots ..................................................40

Legal notice

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All
other trademarks are the property of their respective owners. The information presented is
subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies
contained herein.

Copyright © 2016 Alcatel-Lucent. All rights reserved.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 3/41

 Emergency Notification Server - Installation Manual

1 Document history
Edition Date Changes / Comments / Details

01 28-03-2011 Creation
Document refined to improve information provided to the user with screenshots
02 18-05-2011
from latest version
03 24-05-2011 Document updated with comments addressed
04 27-06-2011 Document updated with comments addressed
05 13-07-2011 Connectivity diagrams explained
06 10-08-2011 High Availability section introduced
07 27-04-2012 Writing style changed
08 10-05-2014 High Availability section updated
09 5-21-2014 Licensing details updated
10 5-22-2014 Restore and upgrade processes added
11 1-27-2015 Incorporated updates, brought up to date with the 2.0 version.
12 3-18-2015 ENS installation process changes.
13 10-23-2015 ENS installation process changes.
14 02-17-2016 ENS installation process changes.
15 12-07-2016 ENS installation process changes.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 4/41

 Emergency Notification Server - Installation Manual

2 Scope
2.1 Overview
2.1.1 The Application – What it means to the User

The Alcatel-Lucent Emergency Notification Server (ENS) is an enhanced alerting system.

This triggers alarms of various types to

o Mobile phones,
o Fixed lines,
o IP phones,
o PCs, and
o Emails

assigned to designated personnel, when someone dials emergency number. These alerts
provide details of location, etc, of a caller to designated personnel. In the case of a 9-1-1
call, it helps PSAP find the caller’s accurate location. Other facilities available to
designated personnel include: call recording and participation, silent monitoring,
conferencing, and visual display of caller’s location. Many of these are optional and can be
customized. Besides, a broken call will be automatically reconnected. The recorded calls
can be played back at a future time and followed up.

The purpose of this application is to alert and provide plenitude of information

conveniently. This information is sent to hand-picked multiple personnel who are nearby
the caller. This enables quick and easy rescue of the caller in distress.

2.1.2 Purpose of this guide

This guide explains the installation of the application: ENS Appliance Server. This also
explains the environment that is required to do this installation. This includes the various
hardware and their connectivity. This enables the Telecom Engineer to get the whole setup
ready for configuration.

This guide targets at the Telecom Engineer. This guide does not explain the configuration
part or the method of using it. They are explained in respective manuals.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 5/41

 Emergency Notification Server - Installation Manual

3 Glossary

ACRONYM EXPANSION

ALI Automatic Location Identification

DB Data Base

ENS Emergency Notification Server

HTTP HyperText Transfer Protocol

IP Internet Protocol

MAC Media Access Control

OXE OmniPCX Enterprise

PBX Private Branch Exchange

PSAP Public Safety Answering Point

PSTN Public Switched Telephone Network

RTCP Real Time Control Protocol

RTP Real Time Protocol

SMTP Simple Mail Transfer Protocol

SNMP Simple Network Management Protocol

VoIP Voice over Internet Protocol

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 6/41

 Emergency Notification Server - Installation Manual

4 Introduction
4.1 Intended Readership
This manual targets at the Telecom Engineer, who deals with installation activities of the
application: ENS Appliance Server.

4.2 Applicability Statement

This manual applies to all the Administrative activities required for the installation of: ENS
Appliance Server

4.3 Overview of this manual

This manual is dedicated to installing the application ENS Appliance Server. Installing this
application is a simple process. The ENS is delivered as a zip file installed thanks to a shell
script. It has to be installed on a RHEL 6U5 64 bits. To install it on a virtual machine, first
create the virtual machine with sufficient RAM and hard drive space, and a virtual network
interface (the network interface must be E1000). But before doing all of this, the setup
will have to be made ready.

This manual specifies the Hardware requirements. It does specify only RHEL6U5 64 bits
basic as Operating System requirements because it does not need other software. All
needed third party software is contained in the DVD itself.

4.4 Licensing
This application has a base package with a wide range of functionalities. For this, a
separate license is provided.

To use the license, the appropriate hostname of the server must be in the license file
before uploading it.

If you do not wish to associate a Fully Qualified Domain Name (FQDN) to the IP address of
the ENS server, you will use the short name “localhost” (from the default value,
“localhost.localdomain”) as the hostname in the license file. This value is already included
in the license by default.

Customers who wish to associate an FQDN to the ENS server IP address will use the short
form of the FQDN as the hostname in the license file. For example, a customer with the
FQDN “customerhostname.customerdomain” will use “customerhostname” as the hostname
in the license file.

To get more functionalities added to the base package, licenses will have to be obtained
separately for each additional package. Below are the functionalities of base package, and
those of each add-on.

Note: Installation procedure is same irrespective of any license

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 7/41

 Emergency Notification Server - Installation Manual

BASE PACKAGE:

o 911 Service for wired Hardphones

o Voice Notification - Silent Mode
o Voice Notification - Conference Mode
o Mini Message Notification
o Web Admin Console with multi level access
o Call Log and Audit Trail
o Call Recording
o Import/Export
o Linux OS & Packaging
o English
o Windows XP and 7 Notification Popup Application
o email/sms notifications
o Voice prompt for Onsite Responders

Add On – I: AUTOMATIC USER CHANGES TRACKER

o IPTouch Users with IP Layer 2 mechanisms

o IPTouch Users with IP Layer 3 mechanisms
o TDM Users & Analog Users
o SIP Phone Users

Add on – II: DASH PACKAGE (specific to 9-1-1 call)

o Connector with DASH ALI Update Services

o 911 Service for Softphone is in DASH Package

Add on – III: HA PACKAGE

o Hot Standby Service

Add on – IV: MAP PACKAGE

o Display user’s location or zone’s location on maps

The above is for information only.

4.5 Technical Support

Please contact: Alcatel-Lucent Technical Support

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 8/41

 Emergency Notification Server - Installation Manual

5 Hardware & Software - Minimum Requirements

Below, hardware requirements are tabulated. These are the minimum requirements. The
actual environment can be more, but not less. If these are all in order, then the
installation process can be commenced.

5.1 Hardware Configuration

Processor Intel Core 2 Duo 2.4 GHz

Memory 4 GB

Disk Space 320 GB

Network Connection 1 Gb/s

DVD-R Optical Drive Integrated or External (USB)

If HA license is obtained, there should be one more server with the above specified
configuration

5.2 System Configuration

Red Hat Enterprise Linux 6 Update 5

Platform 64 bits

This requirement applies also to both servers in case High Availability option is enabled.

5.3 Prerequisite

OmniPCX Enterprise (OXE) Release 9.0 or later

PCX Requirements – without VoIP trunk group accesses for

High Availability ABC supra-network = 1

PCX Requirements – with VoIP trunk group accesses for

High Availability ABC supra-network = 2

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 9/41

 Emergency Notification Server - Installation Manual

5.4 Software Licensing Requirements

Different types of licenses are required to use the different facilities of ENS. Those licenses
are listed in section 4.4 Licensing.

The Telecom Engineer will have to submit the MAC address of the server to Alcatel-Lucent
to obtain the License file. If High Availability is desired, then it requires 2 servers. For this
the Engineer will have to submit the MAC address of both the servers. An ISO image file will
be provided for installation. After completion of installation, the License file is uploaded
to the system via the ENS System Configuration.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 10/41

 Emergency Notification Server - Installation Manual

6 Connectivity - Illustrated
The first step in installing this application is to establish connectivity among different
components of the setup. Below is a general connectivity diagram:

DIAGRAM 1 – General Connectivity

Below is the list of ports that are to be enabled in various systems and enterprise firewalls
as required. This is with reference to the markings in the above diagram:

ID Service Source IP Destination IP Destination Ports

2 ABC-F IP PBX ENS UDP 2571
2 ABC-F ENS IP PBX UDP 2571
2 SIP (If SIP is IP PBX ENS TCP & UDP 5069
enabled)
2 SIP (If SIP is ENS IP PBX TCP & UDP 5069
enabled)
3 RTP/RTCP IP PBX ENS UDP 33000 to 33999
3 RTP/RTCP ENS IP PBX UDP 1024 to 65535
4 RTP/RTCP Phones ENS UDP 33000 to 33999
4 RTP/RTCP ENS PHONES UDP 1024 to 65535
1 SNMPTRAP Switches ENS UDP 162
1 SNMP ENS Switches UDP 161

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 11/41

 Emergency Notification Server - Installation Manual

ID Service Source IP Destination IP Destination Ports

6 SMTP ENS Email Server TCP 25
6 ENS PRIVATE ENS Desktop Notifier UDP 8000
6 ENS PRIVATE Desktop Notifier ENS UDP 8001
5, HTTP Softphone User ENS TCP 80
C ENS Control Board TCP 81
A HTTPS ENS DASH TCP 443
8 SMTP SMS ENS Service Provider TCP 25
B SSH Remote Maintenance ENS TCP 22
D HTTPS Team viewer Remote Maintenance TCP 443

Once the environment is setup to suit the purposes, then ENS Appliance Server can be
installed.

The above diagram is of a general kind. This will have to be translated to suit the current
environment. As samples, below are the topologies under the following four environments:

o Standalone PBX and single ENS

o Standalone duplicated PBX and single ENS
o Standalone duplicated PBX and duplicated ENS
o PBX Network and duplicated ENS

6.1 Standalone PBX and single ENS

DIAGRAM 2 – Standalone PBX and Single ENS

The above diagram illustrates how the 9-1-1 calls are catered to, in the absence of ENS, and
the significant role that ENS plays in this process.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 12/41

 Emergency Notification Server - Installation Manual

When a person makes a call to 9-1-1, it reaches the OXE (PABX). In the absence of ENS, the
call passes through PSTN, and reaches the PSAP via Local Exchange. This is marked in the
above diagram by way of red arrows. In this situation, the PSAP personnel will have to
obtain information about the caller’s location from the caller only. This is because they
will have location details of PABX at the most. They will not have the extension details
from where the person is calling.

If ENS is installed, then the call is taken up by the ENS server and passed on to PSAP. This
is marked by black arrows. ENS updates the ALI DB with callers’ accurate location
information using DASH. This enables PSAP personnel to obtain details of the caller from
the ALI DB. They need not depend on the caller for information. In a situation where the
caller is unable to provide details of his location, this facility comes as a lifesaver.

6.2 Standalone duplicated PBX and single ENS

DIAGRAM 3 – Standalone duplicated PBX and single ENS

The above situation is similar to the one in section 6.1 Standalone PBX and single ENS
above. But the difference is that, here, a backup Call Server is used to guarantee
continuity of service despite technical snags.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 13/41

 Emergency Notification Server - Installation Manual

6.3 Standalone duplicated PBX and duplicated ENS

DIAGRAM 4 – Duplicated PBX and duplicated ENS

This is like the previous diagram, but a backup is used for ENS also. This backup ENS will
take over at the instance of failure of main ENS. For this kind of a setup, HA (High
Availability) package license should have been obtained.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 14/41

 Emergency Notification Server - Installation Manual

6.4 PBX Network and duplicated ENS

DIAGRAM 5 – PBX Network and duplicated ENS

This is like the previous diagram, but covers different locations. OXE (PABX) is placed in
different locations, catering to different sets of callers. Calls from all of them are routed
through the same ENS server. In the absence of ENS, they are routed through the
respective Local Exchange.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 15/41

 Emergency Notification Server - Installation Manual

7 Installation
7.1 Red Hat Enterprise Linux 6U5 64 bits installation
It is the responsibility of the customer or business partner to provide a server with RHEL6U5 64
bits installed.

Important notes regarding the RHEL installation:

1. To facilitate the support, select the language “English”.

2. The type of installation to choose is “Basic Server”.

3. The network (IP address, DNS, Gateway) has to be configured and the server
has to be reachable (ping, ssh).

4. The NTP servers can be configured during RHEL installation or later on in the
ENS webapp.

5. The firewall configuration automatically by ENS during its installation.

7.2 ENS installation

The ENS installer comes as a zip file that you have to copy and unzip before running a shell
script.

1. Create the directory /tmp/ENS on the server and copy the file ens-
<version>.zip into it.

2. Unzip the install script in the same directory:

# unzip –p ens-*.zip ens-<version>/setup/installEns.sh > installEns.sh

With ens-<version>: for instance ens-2.2.2

3. Make you have the right access on the content:

# chmod +rx *

4. Run the shell script:

# ./installEns.sh

Note: the installation trace file is /opt/Alcatel-Lucent/E911/setup/install.log.

5. Finally, restart the server:

# reboot

6. Please, refer to the administration guide for the configuration of the system.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 16/41

 Emergency Notification Server - Installation Manual

8 Upgrade procedure

8.1 Upgrade ENS Release < R1.9

Please contact the ENS team for assistance to upgrade your system.

8.2 Upgrade R1.9 <= ENS Release <= R1.24

To perform an upgrade, you must first create a backup file. Then, as ENS R2.* runs on a RHEL 6U5
64 bits, an Operating System reinstallation is required.

8.2.1 Backup Procedure

While backing up, the system sends out emails to all. The system properties will be saved
as a .zip file. The default name is: dbBackup.zip. Using this dialog box, save the file with
the desired name. Backing up the system can be done when there is a need to migrate
between servers. This would be needed if the system holds the required previous call logs,
call recordings and log entries.

Note: the trunk connection to the Main server must be disabled at this step

1. Log on E911WebAccess webapp.

2. In the System Config tab, do a backup of the system and download it as soon as
you get the link.

Note: The administrator receives the email with the link after a time which
depends on the size of the ENS database (for instance: around 30min for 10GB as
the database is exported in a file and then this file is compressed in a zip file). If
you don’t have access to the administrator’s email address, you can download this
file using the following URL as soon as it is available:

http://<ENSAddress>:8080/E911WebAccess/E911Configuration/exportedData/dbBackup.zip

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 17/41

 Emergency Notification Server - Installation Manual

8.2.2 Restore procedure

This is the reverse of the backup process. This gets the information from an existing
database file into the system. The system properties can be restored only by using the .zip
file in the storage that is in correct format.

1. Install ENS 2.* from scratch on a new RHEL6U5 64 bits and reboot at the end of
the installation process.

2. Log on ENSSystem webapp.

3. Upload the license.

4. Configure the PBX link depending on the customer configuration and save it.

5. Restart the server by using the button.

6. After the restart, log on E911WebAccess webapp.

7. In the System Config tab, do a restore of the system with the previous backup.
At the end of the restore process, a pop-up window will invite you to accept to
restart.

Warning: When Restore System is used, the entire system is configured, and will be
working from the .zip file selected. Previous database, logs, configurations
will not be available anymore. Hence exercise caution while performing
Restore System.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 18/41

 Emergency Notification Server - Installation Manual

8.3 Upgrade ENS Release >= R2

This procedure doesn’t require to backup the system. Just copy the installer in a directory on the
ENS server (for instance /tmp/ens) and then run shell file and answer “y” when asked to upgrade
the system as below.

1. Create the directory /tmp/ENS on the server and copy the file ens-
<version>.zip into it.

2. Unzip the install script in the same directory:

# unzip –p ens-*.zip ens-<version>/setup/installEns.sh > installEns.sh

With ens-<version>: for instance ens-2.2.2

3. Make you have the right access on the content:

# chmod +rx *

4. Run the shell script:

# ./installEns.sh

-------------------------------------------------------------------
[INFO] ENS solution Installer
-------------------------------------------------------------------

Warning: Another ENS version is already installed. Verify that it is an ENS R2.*
before upgrading. Do you want to upgrade it ? (y or n) y

5. Finally, restart the server:

# reboot

Note: the installation trace file is /opt/Alcatel-Lucent/E911/setup/install.log.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 19/41

 Emergency Notification Server - Installation Manual

9 High Availability
This refers to provision of a standby server that is similar to the primary server. The
purpose of this server is to take over the functionality of the Primary server, when it fails.
When the Primary server starts functioning again, the Standby server transfers back the
functionality to the Primary server. This ensures continuous service from Servers even
during times of inevitable failure of a server.

To setup this environment, two Servers are needed, with identical configuration. In each of
them, install the application as explained in the previous section, and load the license.
Further, decide which Server is to act as the Primary Server and which one as Secondary
Server. Accordingly, do the configuration. This also should be identical in both the
Servers.

Please read carefully the following sections to figure out how to install or upgrade an ENS
with High Availability.

Below are the different types of HA installation:

• New ENS High Availability installation

• HA installation on an existing ENS

- Without upgrade

- With upgrade

• Upgrade of an existing HA installation

For all these HA installations, there is a corresponding procedure in the next pages.

If license is obtained for HA package, then, the ENS System configuration page will have
additional fields. Into these fields, details of HA will have to be keyed in. Below are the
additional fields:

Entries into all the boxes are mandatory. Below, these fields are explained:

HA Checkbox: Even if entries are made in all fields, HA will work, only if this box is ticked.

Main Physical IP: This is the IP address of the main ENS server that was provided earlier.

Stby_physical_ip: Here, key in the IP address of the server that is to takeover, if and
when the main server fails.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 20/41

 Emergency Notification Server - Installation Manual

9.1 Trunk configuration on PBX with HA installation

First, it is important to know the PBX configuration that will be associated to the HA installation.
There are mainly 3 different ones:

- ENS HA with one trunk on one PBX

- ENS HA with one trunk on one PBX

- ENS HA with two trunks on two different PBXs

9.1.1 ENS HA with one trunk on one PBX

ENS Main HA ENS Standby

Trunk 1

PBX

DIAGRAM 6 – ENS HA with 1 trunk on 1 PBX

In this case, the “Main PBX” configured on ENS System webapp is the same for both servers:

In this case, the trunk has to be configured as below in “mgr > Trunk groups>Go down
Hierarchy > Trunk Group > Go down hierarchy > Virtual Access For IP”:

SCREENSHOT 10 – TRUNK CONFIGURATION WITH MAIN CPU 2

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 21/41

 Emergency Notification Server - Installation Manual

9.1.2 ENS HA with 2 trunks on one PBX

ENS Main ENS Standby

HA

Trunk 1 Trunk 2

PBX

DIAGRAM 7 – ENS HA with 2 trunks on 1 PBX

In this case, the “Main PBX” configured on ENS System webapp is the same for both servers:

9.1.3 ENS HA with 2 trunks on 2 different PBXs

ENS Main ENS Standby

HA

Trunk 1 Trunk 2

PBX PBX

DIAGRAM 8 – ENS HA with 2 trunks on 2 different PBXs

In this specific case, the ENS Main won’t have the same PBX configuration than on the
Standby. To configure it, log on ENS System webapp and modify the “Main PABX” value:

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 22/41

 Emergency Notification Server - Installation Manual

In addition to that, the Standby server must be able to receive the calls in case there is a
failover. That’s why there is a connection between both PBXs on the above diagram.

Important note: ENS provides with PBX Spatial redundancy support. The Standby PABX IP
address has to be configured in the below “Standby PABX” field.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 23/41

 Emergency Notification Server - Installation Manual

9.2 High Availability installation

Below are the different types of HA installation:

- New ENS High Availability installation

- HA installation on an existing single ENS

o Without upgrade (maintenance window required)

o With upgrade (maintenance window required)

- Upgrade of an existing HA installation (maintenance window required)

A maintenance window is required for some of these installations. The estimated time may vary
depending on the size of the ENS database and the network.

9.2.1 New ENS HA installation

Note: the trunk connections to the Main and the Standby server must be disabled until the end of
this procedure

On the Main server:

1. Install ENS and reboot at the end of the installation process.

2. Log on ENS System webapp.

3. Upload the license.

4. Configure the PBX link depending on the customer configuration and save it.

5. Restart the server by using the button.

Note: At this step, if you do any configurations on the main server you will have to generate a
backup. Then, you will restore it on the future Standby server before enabling the HA on both
servers. Otherwise, none of the data created before enabling HA will be replicated on the
Standby.

On the Standby server

6. Install ENS and reboot at the end of the installation process

7. Log on ENS System webapp.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 24/41

 Emergency Notification Server - Installation Manual

8. Upload the license.

9. Configure the PBX link depending on the customer configuration and save it.

10. Restart the server by using the button.

On both servers:

11. Log on ENS System webapp.

12. Configure the IP addresses, enable and save the HA configuration.

Note: For instance in the above screenshot, the main IP address is 192.168.0.188, the Standby IP
address is 192.168.0.189 and HA is enabled. The configuration has to be exactly the same on both
servers.

13. After you save the configuration, you will get a pop up reminding you that you have to
check the configuration on both servers.

On the Main or the Standby server:

14. Then, you can restart by clicking on the “Restart HA servers” button of one of the 2
servers.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 25/41

 Emergency Notification Server - Installation Manual

Note: At this step, you must wait few minutes that ENS updates both servers. During the HA
installation process, both servers are restarted automatically once.

On the PBX:

15. Finally, the trunk connections to the Main and the Standby servers can be enabled on the
PBX

Note: The HA section will be displayed as below in the ENS System webapp at the end of the
installation process.

Note: The restore button is disabled after the HA installation. Indeed, it is only allowed to do
backups on an HA ENS. If the customer wants to restore a backup for any reasons, please ask the
ENS team.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 26/41

 Emergency Notification Server - Installation Manual

9.2.2 HA installation on an existing ENS

9.2.2.1 HA installation without upgrade of ENS single (maintenance window required)

Before ENS Single

HA installation RX

ENS Standby
ENS Main RX
After RX (New ENS server
HA installation (Single with HA enabled) installation with backup of
ENS Single restored on it.
Then, HA is enabled)

RX: Same ENS Release on all these servers.

On the new server (ENS Standby):

Note: the trunk connection to the Standby server must be disabled until the end of this
procedure

1. Install same ENS release than on Main server and reboot at the end of the installation
process.

############# MAINTENANCE WINDOW START (2 hours) #############

On both servers:

2. Log on ENS System webapp.

3. Upload the new license with HA feature.

4. Configure the PBX link depending on the customer configuration and save it.

5. Restart the server by using the button.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 27/41

 Emergency Notification Server - Installation Manual

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 28/41

 Emergency Notification Server - Installation Manual

On the existing server (ENS Main):

Note: the trunk connection to the Main server must be disabled at this step

6. Log on E911 WebAccess webapp.

7. In the System Config tab, do a backup of the system and download it as soon as you get
the link.

Note: The administrator receives the email with the link after a time which depends on the size
of the ENS database (for instance: around 30min for 10GB as the database is exported in a file
and then this file is compressed in a zip file). In the case you don’t have access to the
administrator’s email, you can download this file using the following URL as soon as it is
available:

http://<ENSAddress>:8080/E911WebAccess/E911Configuration/exportedData/dbBackup.zip

On the new server (ENS Standby):

8. Log on E911 WebAccess webapp.

9. In the System Config tab, do a restore of the system with the previous backup. At the end
of the restore process, a pop-up window will invite you to accept to restart.

Note: After the restart, both servers are ready for HA installation.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 29/41

 Emergency Notification Server - Installation Manual

On both servers:

10. Log on ENS System webapp.

11. Configure the IP addresses, enable and save the HA configuration.

Note: For instance in the above screenshot, the main IP address is 192.168.0.188, the Standby IP
address is 192.168.0.189 and HA is enabled. The configuration has to be exactly the same on both
servers.

12. After you save the configuration, you will get a pop up reminding you that you have to
check the configuration on both servers.

On the Main or the Standby server:

13. Then, you can restart by clicking on the “Restart HA servers” button of one of the 2
servers.

Note: At this step, you must wait few minutes that ENS updates both servers. During the HA
installation process, both servers are restarted automatically once.

On the PBX:

14. Finally, the trunk connections to the Main and the Standby servers can be enabled on the
PBX

############# END MAINTENANCE WINDOW #############

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 30/41

 Emergency Notification Server - Installation Manual

Note: The HA section will be displayed as below in the ENS System webapp at the end of the
installation process.

Note: The restore button is disabled after the HA installation. Indeed, it is only allowed to do
backups on an HA ENS. If the customer wants to restore a backup for any reasons, please ask the
ENS team.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 31/41

 Emergency Notification Server - Installation Manual

9.2.2.2 HA installation with upgrade of ENS single (maintenance window required)

Before ENS Single

HA installation RX

ENS Main ENS Standby

RY RY
After (New ENS server (New ENS server
HA installation installation with backup of installation with backup of
ENS Single restored on it. ENS Single restored on it.
Then, HA is enabled) Then, HA is enabled)

RX: Old ENS Release on Single server.

RY: New ENS Release on HA servers.

On the new server (ENS Standby):

Note: the trunk connection to the Standby server must be disabled

1. Install ENS and reboot at the end of the installation process.

2. Log on ENS System webapp.

3. Upload the new license with HA feature.

4. Configure the PBX link depending on the customer configuration and save it.

5. Restart the server by using the button.

############# MAINTENANCE WINDOW START: #############

############# - 2 hour: ENS >= R 2.* #############
############# - 4 hours: ENS <= R 1.24 #############

On the existing server:

Note: the trunk connection to the Main server must be disabled at this step

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 32/41

 Emergency Notification Server - Installation Manual

6. Upgrade the main server following procedure detailed in Chapter “Upgrade procedure”

7. Log on E911WebAccess webapp.

8. In the System Config tab, do a backup of the system and download it as soon as you get
the link.

Note: The administrator receives the email with the link after a time which depends on the size
of the ENS database (for instance: around 30min for 10GB as the database is exported in a file
and then this file is compressed in a zip file). In the case you don’t have access to the
administrator’s email, you can download this file using the following URL as soon as it is
available:

http://<ENSAddress>:8080/E911WebAccess/E911Configuration/exportedData/dbBackup.zip

On the new server:

9. Log on E911WebAccess webapp.

10. In the System Config tab, do a restore of the system with the previous backup. At the end
of the restore process, a pop-up window will invite you to accept to restart.

Note: After the restart, you have to check that the data are the same on both servers in order to
confirm that the backup/restore worked.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 33/41

 Emergency Notification Server - Installation Manual

On the Main server:

11. Log on ENSSystem webapp.

12. Upload the new license with HA feature.

13. Restart the server by using the button.

14. After the restart, log on E911WebAccess webapp.

On both servers:

15. Log on ENSSystem webapp

16. Configure the IP addresses, enable and save the HA configuration

Note: For instance in the above screenshot, the main IP address is 192.168.0.188, the Standby IP
address is 192.168.0.189 and HA is enabled. The configuration has to be exactly the same on both
servers.

17. After you save the configuration, you will get a pop up reminding you that you have to
check the configuration on both servers.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 34/41

 Emergency Notification Server - Installation Manual

On the Main or the Standby server:

18. Then, you can restart by clicking on the “Restart HA servers” button of one of the 2
servers.

Note: At this step, you must wait few minutes that ENS updates both servers. During the HA
installation process, both servers are restarted automatically once.

On the PBX:

19. Finally, the trunk connections to the Main and the Standby servers can be enabled on the
PBX

############# END MAINTENANCE WINDOW #############

Note: The HA section will be displayed as below in ENSSystem at the end of the installation
process.

Note: The restore button is disabled after the HA installation. Indeed, it is only allowed to do
backups on an HA ENS. If for any reasons the customer wants to restore a backup, please ask the
ENS team.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 35/41

 Emergency Notification Server - Installation Manual

9.2.2.3 Upgrade of existing High Availability ENS (maintenance window required)

Before ENS Main ENS Standby

HA installation RX RX

ENS Main ENS Standby

RY RY
After (New ENS server (New ENS server
HA upgrade installation with backup of installation with backup of
ENS restored on it. ENS restored on it.
Then, HA is enabled) Then, HA is enabled)

RX: Old ENS Release on Single server.

RY: New ENS Release on HA servers.

############# MAINTENANCE WINDOW START: #############

############# - 1 hour: ENS >= R 2.* #############
############# - 4 hours: ENS <= R 1.24 #############

Note: the trunk connection to the Main and Standby servers must be disabled

On both servers:

1. Log on E911WebAccess webapp

2. In the System Config tab, do a backup of the system and download it as soon as you get
the link

Warning if ENS <= R1.24:

- On the Main server:
o Contains all the data. It may be big due to a data purge problem with the ENS
replication tool in R1.15.52 and older releases. That’s why it can be interesting to
compare the backups of both servers in the case the Main backup would be too
big.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 36/41

 Emergency Notification Server - Installation Manual

- On the Standby server:

o May not contain some maps if the “Sync map to slave” (Zone tab in
E911WebAccess) action has not been run after an update of the maps on the main
server. That’s why you must make sure all the maps have well been synchronized
before doing this backup.

Note: The administrator receives the email with the link after a time which depends on the size
of the ENS database (for instance: around 30min for 10GB as the database is exported in a file
and then this file is compressed in a zip file). In the case you don’t have access to the
administrator’s email, you can download this file using the following URL as soon as it is
available:

http://<ENSAddress>:8080/E911WebAccess/E911Configuration/exportedData/dbBackup.zip

On both servers:

3. Upgrade the server following procedure detailed in Chapter “Upgrade procedure”

On the PBX:

4. Finally, the trunk connections to the Main and the Standby servers can be enabled on the
PBX

############# END MAINTENANCE WINDOW #############

Note: The HA section will be displayed as below in ENSSystem at the end of the installation
process.

Note: The restore button is disabled after the HA installation. Indeed, it is only allowed to do
backups on an HA ENS. If the customer wants to restore a backup for any reasons, please ask the
ENS team.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 37/41

 Emergency Notification Server - Installation Manual

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 38/41

 Emergency Notification Server - Installation Manual

10 Appendixes

10.1 Appendix – I : Table of Diagrams

DIAGRAM 1 – General Connectivity .............................................................10

DIAGRAM 2 – Standalone PBX and Single ENS .................................................11
DIAGRAM 3 – Standalone duplicated PBX and single ENS ...................................12
DIAGRAM 4 – Duplicated PBX and duplicated ENS ............................................13
DIAGRAM 5 – PBX Network and duplicated ENS ...............................................14
DIAGRAM 6 – ENS HA with 1 trunk on 1 PBX ...................................................25
DIAGRAM 7 – ENS HA with 2 trunks on 1 PBX ..................................................26
DIAGRAM 8 – ENS HA with 2 trunks on 2 different PBXs .....................................26

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 39/41

 Emergency Notification Server - Installation Manual

10.2 Appendix – II : Table of Screenshots

Entries below are hyperlinked. Click on the required entry, to move to that screenshot.

Screenshot 1 – Opening screen ...............................................................15

Screenshot 2 – Keyboard selection ...........................................................16
Screenshot 3 – Screen for Configuring hostname and network ..........................17
Screenshot 4 – Screen for editing network interface .....................................18
Screenshot 5 – Screen for Configuring hostname and network ..........................19
Screenshot 6 – Time Zone selection .........................................................20
Screenshot 7 – Installation in progress – screen 1 .........................................21
Screenshot 8 – Installation in progress – screen 2 .........................................22
Screenshot 9 – Installation complete ........................................................23
Screenshot 10 – Trunk configuration with main CPU 2 ...................................25

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 40/41

 Emergency Notification Server - Installation Manual

www.alcatel-lucent.com/enterprise/services

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of

Alcatel-Lucent. All other trademarks are the property of their respective owners.
The information presented is subject to change without notice. Alcatel-Lucent
assumes no responsibility for inaccuracies contained herein.
Copyright © 2015 Alcatel-Lucent. All rights reserved.

Alcatel-Lucent Enterprise Services Ref. 3KF50094MKTOSPZZA Ed.15 Page 41/41