Configuring Esa For Emergency Services - Avaya 1000 Installation And Commissioning Manual

Branch office
Hide thumbs Also See for 1000:
Table of Contents

Advertisement

How the Branch Office feature works
Important:
Do not route ESA calls to a node that has no direct ESA trunks.
Refer to
Routing ESA calls
There are two general methods to specify which digit string results in a call to emergency services:
• Use the Emergency Services Access (ESA) feature. This is the preferred method in North
America, the Caribbean and Latin America (CALA), and in those countries that are members of
the European Union. ESA provides specific features and capabilities required by legislation in
these jurisdictions.
• Use a special dialing sequence, such as a Special Number (SPN) in the Network Alternate
Route Selection (NARS) data block.
Refer to
Emergency Services configuration
configuration.

Configuring ESA for emergency services

Beginning with Communication Server 1000 Release 5.0 and later ESA, it is possible to configure
up to 16 distinct ESDNs to better suit the needs of a multinational enterprise. With support for
Multiple ESDN you are no longer restricted to a single ESDN for use in placing emergency calls.
If all sites were using the same ESDN, a conflict would occur in the NRS. The conflict is resolved by
using a unique prefix for each site, which the main office adds as it routes the call. The suggested
prefix is the ESN home location code of the MG 1000B Server, or alternately, the Number Plan Area
(NPA) code of the MG 1000B Server if there is not more than one Call Server in the NPA. Virtually
any unique string can be used as a prefix because the call is sent to the NRS as an SPN. In the
NRS, SPNs have their own separate numbering plan.
The Automatic Number Identification (ANI) data sent to the Public Safety Answering Point (PSAP)
identifies the location of the caller. In some constituencies, legislation requires one DID per fixed
number of square feet, so the physical location of the emergency can be approximated based on the
telephone number delivered to the PSAP. The ESA feature has a comprehensive scheme that can
be used to convert an extension into an appropriate DID.
If the Branch Office is relatively small, it can be easier to use a single, fixed DID number for the
Branch Office. This can be configured using the CHG ZESA command in LD 117, where the
<ESALocator> parameter is the DID telephone number to be sent for use by the PSAP to locate the
source of the emergency call. For more information on this command, refer to Avaya Emergency
Services Access Fundamentals, NN43001-613.
Branch Office Installation and Commissioning
70
on page 181 for more information on routing ESN calls.
on page 180 for more information on ESA and SPN
Comments? infodev@avaya.com
June 2014

Advertisement

Table of Contents
loading

Table of Contents