Dynamic Emergency Calling Configuration (Corporate Locations)

Regulations

Kari’s Law

States you must be able to dial 911 directly without needing an additional 9 for an outside line. Notifications are also required to be sent to relevant users within the corporate office, so they are aware of the call. Finally, your location information which includes the street address needs to be sent to the PSAP.

For more information, please click here.

Ray Baum’s Law

Adds to Kari’s Law to include Location Information to improve the location information down to Floor/Building/Suite etc.

For more information, please click here.

Prerequisites

The following prerequisites will be required to fully deploy the dynamic emergency calling solutions via Teams.

Network

The below table can be used to track the required information relating to each site located in the United States. This information will be used later in the guide to configure your environment so be sure to gather this data.

• Country
• State
• Street Name
• Building (if applicable)
• Street Number
• Zip Code
• City
• Public IP Address (single or multiple)
• Local Subnet Range (including subnet mask)
• WiFi Access Point (BSSID)
• Latitude
• Longitude

Configuration

The following steps will be reliant on access to your Teams Admin Center (TAC) and Teams PowerShell. You will require your user account to have at least a Teams Communications Admin role assigned.

Step 1: Emergency Addresses

Navigation to Location > Emergency Addresses.

Utilize the information table in section 2.1 to create each office (aka Civic Address) here.

Select “Emergency addresses” – “Add”

In the example below we create the “San Francisco” Office. Enter the Address and GPS co-ordinates. If the address search fails – manually enter the address and latitude / longitude details as per below

Continue to create as many Civic Addresses as required for your organization. Once validated you can add “Places” under each to separate buildings on a campus for instance or per floor for larger office blocks.

Step 3: Places

You can create “Places” within each Civic address by drilling into each Location created above if more granularity is required.

Step 4: Network Topology

Under “Locations” – “Network Topology” you will need to configure:

• Regions
• Network sites
• Subnets
• Trusted IPs

Regions, Network sites & Subnets

Firstly, create a network site. In the example below, we have created a Region “US” and then created one of our offices “San Francisco” as a site. We then associate all the subnets with this site.

Add all the network ranges and subnets related to this Site. All Sites must have unique subnets.

The configured subnets in this section are used by Microsoft to determine the location of the client along with the following Trusted IPs and Site.

Now we need to move on to adding all the “Trusted IPs”. These are all the egress public facing IP addresses for the site.

Step 5: Networks & Locations

Now that Emergency Location(s) and Places are established, network elements such as Subnets or Wireless Access Points can now be created and mapped accordingly.

Navigate to “Locations – Networks & Locations” in the Teams Admin Center. This section is where you specify all your network address subnets across the organization and the location it relates to.

Each subnet can only be associated with one site. There are 4x network element options to you can add here: Subnets, WAPs, Switches and Ports. Subnets and WAPs are the supported fields and recommended use at the time of writing this document.

The example below shows the subnet configuration example:

Step 6: Emergency Calling Policy

You can set who to notify and how they are notified when a user who is assigned the policy calls emergency services. For example, you can configure policy settings to automatically notify your organization's security desk and have them listen in to emergency calls. The following notifications are available:

• Notification Only
• Conference but muted
• Conference unmuted

You can specify an external PSTN number if using one of the conference settings. See here for additional information.

This is a solution to regulation stated in Kari’s Law to enable at least one notification group/user or distribution list per site.

Notification example:

Alerts are generated in a chat within teams.

The obfuscated section shows the caller who made the emergency call

Conference in and unmuted option example:

Testing

Teams Client Verification

If all the above deployment steps have been setup correctly, users that satisfy the Trusted IPs and configured Network Subnets should see the below Emergency Location within the “Settings > Calls” section of the Teams client

When making a call from the Teams Client calls that are detected as an Emergency will appear as per below.

You can use the Bandwidth 933 service to check your location and number that’s received on the call. Dial 933 and you call will be answered by an IVR and read back you number and address.

Note: Calls that are not detected as an emergency call from the Emergency Calling Routing Policy rules will use your region to normalise and route the call. This will go out as a normal call without any location information included and will be answered by the PSAP who should verify your location.

Enablement

Make sure to assign the Emergency Calling policy to users that require dynamic emergency calling functionality (LoopUp recommend creating a dedicated policy for dynamic emergency calling related features).