Interactions for Enhanced 911

Last Updated : Aug 07, 2020 |

This section provides information about how the Enhanced E911 feature interacts with other features on the system. Use this information to ensure that you receive the maximum benefits of E911 in any feature configuration.

  • Bridged Call Appearances

    Emergency 911 calls from a bridged extension report the extension of the physical telephone, not the bridged call appearance.

  • Class of Restriction (COR), Tenant Partitioning, and Facilities Restriction Level (FRL)

    COR, Tenant Partitioning, and FRL restrictions apply to CAMA trunks and 911 calls.

  • Expert Agent Selection (EAS)

    When an EAS agent dials 911, the number is the number of the physical telephone, and not of the logical agent.

  • Network Address Translation (NAT) devices

    If a telephone operates behind a NAT device, the ELIN is based upon the translated IP address of the telephone, and not the native IP address. If you use a NAT device, the NAT device must preserve IP subnetworks. To require a change in IP address, the E911 for wired IP telephones capability expects a move from one geographic area to another.

    For example, you have two subnetworks, 1.1.1.* and 2.2.2.*, that are mapped to two different ELINs in the IP Network Mapping screen. Both of these subnetworks operate behind a NAT device. If the NAT device maps both subnetworks of 1.1.1.* and 2.2.2.* into addresses in the range 3.3.3.*, Communication Manager cannot detect if someone moves a telephone from 1.1.1.* to 2.2.2.*.

  • Non-ARS calls

    The E911 feature uses Automatic Route Selection (ARS) digit analysis to classify an outgoing call as an emergency or crisis alert call. If a user does not use ARS to dial an emergency call, the E911 feature only applies if the trunk types are CO or FX. Examples of calls that do not use ARS are:

    • Calls that use a trunk access code

    • Personal CO line button calls

    • Facility test calls

    • AAR access code calls if AAR digit analysis does not overflow to ARS

The following interactions apply to the Crisis Alert capability:

  • Centralized Attendant Service (CAS)

    If CAS is enabled, the emergency alert still goes to the local attendant.

  • Multiple Locations

    A crisis alert call to a digital pager is treated by the system as if the call is from Location 1. This treatment means that the pager number digits are analyzed using the Location 1 dial plan and the Location 1 ARS Analysis Table. The system does not use the location of the station that dialed the emergency call.

  • Outgoing Trunk Queuing

    If a user attempts to make an emergency call when all trunks are busy, the call does not generate an alert. If the Outgoing Trunk Queuing feature is enabled for a trunk group, the call is placed in a queue but does not generate an alert.

  • Tenant Partitioning

    If Tenant Partitioning is active, stations and attendants with crisis alert buttons receive emergency notification from those callers who are within the tenant partition. If no stations or attendants with crisis alert buttons are assigned to a partition from which an emergency call originates, the system still sends a record of the call to the system printer, and to the Emergency Access Calls report.

  • Terminal Self-Administration

    Users who can administer their telephones cannot disable a crss-alert button.