E911 Manager represents a significant step forward in the automation and management of E911 location information for organizations with Multi-Line Telephone Systems (MLTS). Architected using Microsoft .NET, E911 Manager not only streamlines the management of your E911 data records, but helps reduce the Total Cost of Ownership (TCO) of your solution and improving your Return on Investment (ROI). The single-server architecture eliminates costly ancillary components and enables real-time updates between your Call Servers/PBX and the RedSky application. In an IP telephony environment costs are further reduced because RedSky's new Network Discovery feature enables the real-time tracking and updating of the location of IP phones on the network. Our browser-based client access enables the management and administration of the application from any PC with a standard web browser.
Avaya S8x00 Media Servers with ACM Software and Avaya Definity Servers with C-LAN
Direct connect via C-LAN/Native Ethernet and Directory Enabled Management (DEM)
Nortel Meridian, release 23 and higher
Dial-up via modem and CSV file download from switch
(All others)
Dial-up via modem and CSV file download from switch
E911 Manager Server
E911 Manager is installed on a customer-provided Pentium 4 server running Windows 2003 Server. E911 Manager uses the native LDAP database in Windows 2003 Server (AD/AM) as the data store so no additional licensing of a database is required. Customers administer E911 Manager using a standard web browser. Both LAN/WAN and dial-up connectivity to Call Server/PBXs is available.
EON (Emergency On-site Notification)
EON notifies local security of a 911 call in real time and gives the precise location of the caller. EON requires the purchase of API software or hardware depending on the make and model of Call Server/PBX.
Gateway Account to the Local Regional (ALI) Database
Customers are required to contract with Local Service Providers to establish Automatic Location Information (ALI) records in the regional ALI database which, in turn, updates the local Public Safety Answering Point (PSAP). Each DID will have an associated record in the regional ALI database which defines the building address and precise location within a building. Customers with a national presence will require contracts with Local Service Providers supporting each location.
Call Server/PBX
Each Call Server/PBX must be configured to out-pulse the appropriate ten- or seven-digit number for 911 according to local requirements. Emergency Response Locations must be configured for IP phones and location fields in station screens must be updated for digital and analog phones.
Direct Inward Dial (DID) Numbers
Each phone must be associated with a ten-digit DID number for E911 to work properly. The user's actual DID number may be used which will represent the individual location, or a DID number that represents a floor or a region on the floor can be used. This is sometimes referred to as an Emergency Location Identification Number (ELIN). DIDs may be purchased from your Local Service Provider.
911 Trunking
ISDN-PRI or CAMA trunks are required for each call server/PBX and IP gateway to ensure proper 911 call routing and location identification at the local PSAP. 911 trunks are typically required at all sites where Call Servers/PBXs are located or at large to medium-sized branch offices that are served by VoIP gateways.
Location Definition and Audits
E911 relies on accurate location data residing in the regional ALI database. If not already done, the customer must define the location of all phones and IP ports in each building in accordance with the Master Street Address Guide (MSAG) and ALI database requirements. RedSky provides a professional service to do this work for customers, or customers can undertake this task themselves.
