Avaya Communication Manager Administrator's Manual page 1525

Administrative scenarios
Two administrative possibilities are:
1
If a media gateway is connected to the local exchange carrier using a Central Office trunk, the
Central Office trunk extension number will identify the gateway service address. The service
address is the physical location that emergency response personnel will be sent. The trunk should
only be used to send and receive emergency calls. Calls from any station registered to the gateway
will present the Central Office trunk number to the PSAP. Emergency response will then be sent
to the service address. It is important to verify with your local exchange carrier that the extension
number of the Central Office trunk is in the PSAP database so that all emergency help is sent to
the correct location.
2
If a media gateway is connected to the local exchange carrier using a PRI trunk, each extension
registered to the gateway will send its' separate extension number to the PSAP. It is important to
verify with the local exchange carrier that all the extensions are in the PSAP database. If the
extension numbers at the gateway are administered using DID numbers from the main server
running Communication Manager, the numbers being used at the media gateway must be moved
to the central office where the 911 calls will terminate. Otherwise, emergency help will be sent to
the main server location and not the media gateway location.
If the main server running Avaya Communication Manager and the media gateway are in different local
exchange carrier jurisdictions, then the following administrative scenarios would apply:
1
If you are using a Central Office trunk from the gateway to the central office, follow the
procedure described in administrative scenario
PSAP database for the Central Office trunk. All calls made from the gateway will use this number.
2
If you are using a PRI trunk, you will need to purchase a block of DID numbers from the local
exchange carrier for your gateway stations. The gateway extensions can be shortened for private
calls within the system (1-7 digits), but when calling to the PSTN, the correct digits must be
added so that the number is correctly recognized at the PSAP for emergency calls.
All the scenarios described apply to each media gateway that is in a separate location. The applicable
procedure should be repeated for each media gateway connected to a server running Communication
Manager with a unique PSAP.
Gateways in the same location as the main system, or multiple gateways in the same location, can use the
same Location Specific Routing tables and trunks. Please contact your Avaya representative if you have
questions about these procedures or scenarios.
E911 ELIN for IP wired extensions
This feature automates the process of assigning an emergency location information number (ELIN)
through an IP subnetwork ("subnet") during a 911 call. The ELIN is then sent over either CAMA or
ISDN PRI trunks to the emergency services network when 911 is dialed. This feature properly identifies
locations of wired IP telephones that call an emergency number from anywhere on a campus or location.
NOTE:
This feature depends upon the customer having subnets that correspond to geographical
areas.
This feature works for both types of IP endpoints:
•
H.323
•
SIP
Administrator's Guide for Avaya Communication Manager
November 2003
Step 1. Make sure the correct number is in the
Feature Reference
Emergency 911 calls
1525