Feature Reference
Emergency 911 calls
1524
Administrator’s Guide for Avaya Communication Manager
November 2003
For IP Softphone, if the
Remote Softphone Emergency Calls
field on the Station screen is set to
extension, Communication Manager uses the entry in the
Emergency Location Ext
field as the E911
CPN instead of the IP Softphone’s extension. See
Remote Softphone Emergency Calls
on page 646 for
important information on IP endpoints.
Considerations
•
The ANI that is sent to the CO might not be the same extension as that of the phone used to dial
emergency personnel. If the call is disconnected and emergency personnel call back they will call
the ANI and may not be able to reach the person who placed the call. However, if the emergency
location phone had a crisis alert button, the return call would be answered by someone who was
notified of the extension making the emergency call. That person could forward the return call
from the emergency personnel to the extension that made the emergency call. See “Crisis Alert.”
•
The Enhancements to E911 feature only applies to emergency calls on CAMA and ISDN trunks.
•
Several call appearances should be provided on the last phone in the Emergency Location
Extension’s coverage path and station hunting path.
•
Emergency Location Extensions should not include voice mail, automated attendant or
announcement extensions.
Configurations With Media Gateways in
Different Locations
If you have media gateways, additional administration is required to ensure that 911 calls made from
endpoints registered to each of the gateways route to the correct Public Service Answering Point (PSAP).
What you should do
To ensure that a media gateway in a separate location (which has a different PSAP than does the main
server running Avaya Communication Manager) can route emergency calls, a Central Office trunk or PRI
trunk is required from the gateway to the local exchange carrier. Each media gateway connected to
Communication Manager and in a different PSAP jurisdiction than the main server must be administered
in a separate location to ensure that emergency calls can be routed from that location. If a media gateway
is in the same PSAP jurisdiction as the main server running Communication Manager, then it will not
need to be in a separate location. The gateway’s ARS calls will route with the main system’s.
In a configuration with one location, all outgoing calls to the PSTN route in accordance with the ARS
table for location 1. If media gateways are introduced into different locations, then "Location Specific
Routing" is required for each location. If a media gateway is in a separate location from the main server
running Communication Manager, it can be administered in a diiferent location (in locations 2-64 for
Linux servers and 2-44 for Avaya DEFINITY servers).
The administration command for Location Specific Routing is
change ars analysis location "X" 0
,
where
X
is the chosen location (2-64 or 2-44) and
0
is the first placeholder in the analysis table. Once the
table appears, you must then enter the routing, including: chosen dialed string (probably 911), min and
max digits, route pattern, and call type. The required route pattern information must also be set up. Once
this administration is complete, 911 calls from the location will route using a Central Office or PRI trunk
to the local exchange carrier.