Enhanced 911 (E911) Emergency Services

You can choose RedSky as the E911 emergency call provider. The RedSky Enhanced Emergency (E911) service is designed for organizations with a hybrid or nomadic workforce. It provides dynamic location support and a network that routes emergency calls to Public Safety Answering Points (PSAP) around the US, its territories, and Canada. RedSky provides an emergency call management portal and an integration point in Webex Calling’s Calling Admin Portal (CAP).

Important: Effective January 6, 2022, new federal laws require customers operating voice calling systems with movable or “nomadic” lines to automatically deliver a 9-1-1 caller’s “dispatchable location” to 9-1-1 operators to enable first responders to quickly locate the caller. Learn more about this regulation and your emergency service options here.

A. Feature Notes

The service is enabled on a per-location/site basis. When configured to a site, all users/devices at that site will be allocated the E911 RedSky feature. When a location/site is fully enabled in CAP, emergency calls (933 for test calls and 911 for emergency calls) placed from all phones and soft clients assigned to that location in CAP use RedSky's services. RedSky's role in the solution is as follows:

• Maintains the partner/customer provisioned database that is used to map an emergency call to a dispatchable location.
• Based on a calling device's dispatchable location, directs emergency calls to the correct PSAP with information that allows the PSAP to determine the location where emergency personnel should be dispatched as well as the call-back number.
• Generates optional notifications to enterprise personnel.
• Customers that have enabled Enhanced Notification benefit from the service bridging enterprise personnel into emergency calls placed by enterprise users and provide pop notifications.

B. Step 1: Obtain Your RedSky License

If you’ve decided to implement the Enhanced 911 service, the first step is to get set up with RedSky. The steps outlined below are designed to walk administrators through configuring the service on your own. Or, you can use our Professional Services team who can handle your implementation.(additional charges apply).

To order this service, contact your account manager and let them know which sites you would like to order RedSky for. Once your account manager has completed the order, RedSky will send the administrator (or Verizon Professional Services) your RedSky Company ID and Secret Key.

C. Step 2: Log in to Horizon Mobility

After you’ve obtained your RedSky license, you’ll receive your username and password for the Redsky Horizon Mobility portal. When you log in for the first time, you’ll be prompted to change your password.

D. Step 3: Add Your Softphone Users in Horizon Mobility

For the E911 service to work for softphone users using the Verizon Communicator or Mobile Connect apps, they will need the MyE911integration. Before these users can get started, you will need to provision them as a Device User in the Horizon Mobility portal. To add a user in the Horizon Mobility portal, follow these steps:

1. 1. From the Horizon Mobility portal, select Configuration from the left-hand navigation.
   2. Select Users.
   3. Select Add User.

1. Enter the Phone Number, Email, First Name and Last Name of the user.
2. Select Save.

To do a bulk import of Device Users, follow the import steps outlined in Step 5.

E. Step 4: Network Discovery Setup - Create Wiremaps and Telephone Number Locations in Horizon Mobility

For your employees to be properly located as they move around your organization, each location must be mapped to a network element, such as IP Subnet, Network Switch, or Access Point. This is referred to as Network Discovery, or wire mapping, and it must be provisioned in the Horizon Mobility portal.

Before you do this, we recommend that you read through the Network Discovery Overview materials to get an understanding of how RedSky’s network discovery can be implemented in your environment.

Network Discovery Overview

Now that you have some background around network discovery, you should be ready to create your wiremaps. For step-by-step instructions on how to do this in the Horizon Mobility portal, see section 3.4 Network Discovery (starting on page 48).

To expedite importing BSSID, Buildings, Device User, LLDP, Chassis, LLDP Port, Locations, MAC Address, Private IP Range, and Trusted IP Range information into the Horizon Mobility portal, you can use the import steps to upload a completed CSV template with this information. For these steps, see the next section, Step 5.

Note: You must be logged in as an organization administrator to view, add, edit, or delete any network elements.

F. Step 5 (optional): Import Using CSV Template

Administrators can expedite importing BSSID, Buildings, Device User, LLDP, Chassis, LLDP Port, Locations, MAC Address, Private IP Range, and Trusted IP Range information into the Horizon Mobility portal by uploading CSV files.

Download the CSV Template

First, you need to create the CSV file with the appropriate information for the type of import you are uploading. To do this, download the CSV template for the exact format you need for a successful import.

1. 1. From the Horizon Mobility portal, select Importing from the left-hand navigation.
   2. Select Template Files.

1. Choose the template file that you need. Your options include:
   • MAC Assignment (optional) – Only required if you want to discover the user by the MAC address of their device. Note: This is the highest priority in the discovery protocol. This is designed for devices that don't support the HELD query process or for hard phones that are deployed connected to a network that is not in the wiremap. For example, a home router with an ethernet connection.
   • BSSID Assignment (optional) – Use this template if you are discovering devices based on their wireless access point (wireless router location). Note: Only applicable to devices that have Wi-Fi network connection enabled all the time. For example, a laptop that docks and turns off Wi-Fi needs another discovery method when docked.
   • Buildings (required*) – Physical addresses of each site where Webex Calling is provisioned with RedSky deployed. Note: This is required if a corporate wiremap is going to be used. *It is not required if the enterprise will ONLY use Webex clients and everyone is responsible for creating their own personal wiremap (self-provisioning).
   • Locations (required*) – List of all locations within each building where 911 could be dispatched in addition to the main address entrance. Note: This is required if a corporate wiremap is going to be used. It is used in conjunction with Buildings, which must be set up first. *It is not required if the enterprise will ONLY use Webex clients and everyone is responsible for creating their own personal wiremap (self-provisioning).
   • Device Users (required) – These users will be prompted to enter the address in their Webex App. Note: This only applies to users who have deployed the RedSky MyE911(r). An employee that uses the Webex client for softphones does not need to be provisioned here. The Webex client emulates, to the best degree possible, a hard phone with self-provisioning prompting for Null tokens.
   • LLDP Chassis Assignment (optional) – Only required if you want to discover the user based on the Switch the user is logged into. Note: LLDP must be enabled on the customer Layer 2 network for this feature to work. It is only applicable to hard phones.
   • LLDP Port Assignment (optional) – If you are doing discovery at the switch level, you can also fill out this sheet and provide additional detail down to the port level on the switch. Note: LLDP must be enabled on the customer Layer 2 network for this feature to work. It is only applicable to hard phones.
   • Trusted IP Range Assignment (optional) – Should be completed for each location if using public IP address for discovery.
   • Private IP Range Assignment (optional) – Only required if using Trusted IP range for discovery. Note: This would be used when an enterprise used the same private IP range in multiple buildings. Must be used in combination with Public IP, which is unique to each building.

Upload and Import Your Completed CSV

After you’ve filled out the CSV template(s), you can import the information by following these steps:

1. 1. From the Horizon Mobility portal, select Importing from the left-hand navigation.
   2. Select Add Import.

1. 1. Select the type of import you will be uploading from the drop-down menu (BSSID, Buildings, Device User, LLDP Chassis, LLDP Port, Locations, MAC Address, Private IP Range, and Trusted IP Range).

Note: When importing Chassis and Ports, the Chassis data must be imported first, as the Port data must reference the Chassis to which it belongs.

1. Select Upload CSV.
2. Click Save. Once saved, the information in your CSV file begins importing into the Horizon Mobility portal.
3. After the import is complete, the table shows you how many records have successfully uploaded and how many have failed.
4. You can click on the number of failures to see more details.

G. Step 6: Set Up Emergency Call Notifications

Once you know where your devices are (as per the wiremapping configuration that was completed in Step 4), it’s time to set up emergency call notifications

To comply with Public Law 115-127, also known as Kari’s Law, any call that's made from within your organization to emergency services must generate an email notification. You can enable notifications across all locations or customize notifications for individual locations, which can be sent to location-specific security personnel.

With the E911 service, you can get notifications to enterprise personnel through email, SMS, or a desktop application. This is configured in RedSky’s Horizon Mobility portal.

When configuring emergency call notifications in the RedSky admin portal, you can do the following:

• Specify multiple email addresses and SMS recipients. For example, you may want your emergency response team, security officer, and/or your main receptionist to get these notifications.
• Bridge your internal emergency team with emergency calls placed by users and provide pop notifications from a desktop application.
• Set up alerts when a 933 test call is placed or when a device performs a HELD request from an unknown location, providing the administrator to monitor where the users are connecting from.

For step-by-step instructions on how to set up notifications (also referred to as alerts), see section 3.1 Alerts & Emails (starting on page 23).

Note: You must be logged in as an organization administrator to view, add, edit, or delete any network elements.

Important: If you decide not to set up your emergency call notifications with the E911 service, in order to be compliant, you must, at a minimum, set it up using these steps.

H. Step 7: Enable E911 Integration in the Calling Admin Portal

Once you’ve created a RedSky account and provisioned wiremap-based and caller-ID based information for one or more locations, you can enable at the site level in the Calling Admin Portal.

Note: In addition to enabling the E911 service for a site/location, these steps also include:

• Restarting your MPP phones in enabled locations
• Using 933 to validate in RedSky IVR for all devices in the site
• Turning on the E911 routing flag

1. 1. From the Calling Admin Portal, choose the site you’d like to enable E911 for in the upper, right-hand corner.
   2. Select Profile in the left-hand navigation.
   3. Check the box next to Allow RedSky to receive network connectivity information and test calls to allows the 933 test call to RedSky.

This setting updates the device configuration to enable HELD functionality for all HELD compatible devices at that location. After the devices are reinitialized and pick up the new configuration they will make HELD requests to RedSky's Location Information Server (LIS) to determine a valid location.

This setting also routes all test calls (933) from that location to RedSky. At this point, emergency calls (911) are not impacted and are still routed to the PSTN provider.

1. Place test calls to 933 to ensure that the calls are routed properly before you enable full 911 routing for the location. Test calls can be placed from all endpoints assigned to the location, including HELD capable devices, softphones, and non-HELD devices. The test call (933) connects the caller to a RedSky IVR, which announces the caller ID and currently known address for that device.
2. After you confirm that test calls are routing correctly, return to the profile screen in the Calling Admin Portal.
3. Select the toggle next to Route Emergency Calls to RedSky. This setting ensures that not only are MPP phones getting location information from a RedSky LIS, but that actual 911 calls also route to RedSky.
4. Once reinitialized, HELD capable devices assigned to the location will make HELD requests and receive tokens.

I. Additional Feature Specifications

• In RedSky, there is a setting called HELD/HELD+ Routing Options. If this is toggled to on, when an emergency call is made from a HELD / HELD+ device (which did not have an address mapping from the network info), this service will see if there is a matching DID (in Locations or User) and use the corresponding address.
• For Non-HELD devices, the above setting does not have any impact. For Non-HELD devices this service will always see if there is a matching DID (in Locations or User) and use the corresponding address.
• DECT and ATAs don't communicate with this service. Their calls route to emergency service provider, so RedSky administrative portal needs to be configured with a location associated with their caller ID.
• Emergency calls from MPP devices not physically on the wiremap (their location was not discovered through HELD) are treated based on their asserted Caller ID. If there is a location associated with the TN of a E911 user or E911 location that matches the Caller ID, the call will be routed based on that.