Configuring Esa For The Branch Office - Avaya 1000 Installation And Commissioning Manual

Emergency Services configuration

Configuring ESA for the Branch Office

For ESA, the main office Call Server forwards the call to the Branch Office for termination. Calls are
redirected over a Virtual Trunk using the NRS services. The NRS routes the calls using a special
number, referred to in this section as the ESA Special Number.
ESA must be configured and tested on each call processor (the main office Call Server and each
MG 1000B CP PM) to differentiate between emergency calls originating from IP Phones at each
location and calls originating on trunks.
The steps to configure ESA for emergency access at each location are:
1. Determine the dialing plan for ESA calls.
2. Configure the main office emergency trunk (CAMA or PRI).
3. Configure the Virtual Trunk at the main office.
4. Configure ESN at the main office.
5. Configure ESA at the main office.
6. Configure the branch zone on the main office.
7. Configure the ESA Special Number on the main office.
8. Test ESDN using a main office telephone.
9. Configure the MG 1000B emergency trunk (CAMA or PRI).
10. Configure the Virtual Trunk at the MG 1000B.
11. Configure ESN at the Branch Office.
12. Configure ESA at the Branch Office.
13. Configure the Branch Office zone on the Branch Office.
14. Configure the ESN SPN on the Branch Office.
15. Configure the NRS for the ESA Special Number used.
16. Test ESDN using an MG 1000B IP Phone.
17. Test ESDN using an analog (500/2500-type) or digital telephone located at the Branch
Office.
Reregistering to minimally configured branch
A Branch User in Local Mode but not physically at the branch may get incorrect emergency service
handling. A Branch Office (for example, Survivable Branch Office or Survivable Remote Gateway)
may not be provisioned with knowledge of all the ERLs in the enterprise. In this case, one of two
scenarios occurs if an IP phone reregisters to the branch (either by VO ESA redirection or by
fallback to Local Mode):
• If the local TN is provisioned as Manual Update, then the phone inherits the static location
data. The static location data probably indicates basic ESA processing (per LD 24) if this is a
small branch.
• If the local TN is provisioned as Auto Update, then cached location data in the phone is
rejected if undefined locally, and unknown location values (ERL = 0, ECL = 0, LocDesc =
Branch Office Installation and Commissioning
182
Comments? infodev@avaya.com
June 2014