Overview

• Emergency calls are properly routed to the appropriate Public Safety Answering Point (PSAP).
• The caller's correct "dispatchable" location information is made available to the emergency services operator.

• This information is provided as a guide to 8x8 Voice for Teams administrators. You may need to tailor these instructions to the configuration of your specific Microsoft Teams tenant. IT administrators who require assistance with configuration of this Teams-side service beyond the documentation below must approach Microsoft support services.
• 8x8 Admin Console: In addition to the Microsoft Teams service configuration, the Emergency Routing Service option (see below) must be enabled in Admin Console user profiles for each 8x8 Voice for Microsoft Teams user, even if those Teams users will not be using 8x8 Work phones or applications.

• 8x8 Voice for Microsoft Teams: Your Voice for Teams service must be configured and fully synced in the 8x8 Voice for Teams admin portal before performing the configuration steps in this article.
• As part of your initial setup sync in the Voice for Teams admin portal, PSTN Usage Records are generated in the Microsoft Teams admin center under Voice > Voice routing policies. These are critical to your Teams users' ability to dial emergency service numbers (911 & 933).
• Please see the Set Up Emergency Call Routing Policy section below for details.

Applies To

• 8x8 Nomadic 911 Service
• 8x8 Voice for Microsoft Teams
• Microsoft Teams
• Microsoft Teams Admin Center

Why do I need to do this?

Planning Your Deployment

• Public IP addresses
  • All public IP addresses that will be presented by the Teams client application when connected to the corporate network (their public NAT IP) must be defined in the Trusted IP list. This includes IPv4 and IPv6 addresses. See Set Up Trusted IP Addresses, below.
• Locations
  • Civic Addresses: These are your physical/site locations with unique postal addresses, the primary locations to which emergency responders will be dispatched.
  • Places: Places provide more precise dispatchable locations within a civic address, to which an emergency responder can be directed. For example: Building 2, Floor 3, North West corner, etc. Teams user Place locations are are identified by how users are connected to your corporate network, through the following:
    • Subnets: Defined by the network ID matching the subnet IP range assigned to clients. For example, the network ID for a client IP/mask of 10.10.10.150/25 is 10.10.10.128.
    • Wi-Fi Access Points: For this you would need your wireless access point BSSIDs (a.k.a. MAC addresses).
    • Switches: You'll need the Chassis IDs of any switches within your corporate network that your Teams users might be connected to.
    • Ports: Location can be further narrowed down on switches. Each port assignment requires the Chassis ID of its switch.

Other Deployment Information to be Aware of

Automatic Address Detection vs Manual Address Entry in Microsoft Teams

• Teams user calls to 911 emergency services will be routed to a local emergency call center (PSAP), rather than the national response center.
• Teams user calls to the 933 test service will play back the user's detected location for verification.

• Teams user calls to 911 emergency services will be routed to a national response center instead of a local call center (PSAP). In this case, the Teams user will be asked to provide their location, and will then be transferred to a PSAP.
• Teams user calls to the 933 test service will not play back the user's configured location, as location detection has failed.

   

Microsoft Documentation

• Plan and configure dynamic emergency calling
• Microsoft Teams Dynamic Emergency Calling (Video, 01:13:44)
• Microsoft Teams Emergency Calling Explained (Video, 00:07:48 Introduction)

Regarding Mac Users

• LLDP enablement software for Mac Operating Systems used by Microsoft Teams

Emergency Service 933 Test Calls

8x8 Emergency Routing Service Portal

• Teams Only: Configuration in the 8x8 Emergency Routing Service portal is not required if Microsoft Teams is the only phone endpoint available to your Teams users.
• Teams and 8x8 Work: Configuration of both the Microsoft Teams tenant and the 8x8 Emergency Routing Service portal is required in the following scenarios:
  • When there are Teams client users who also use 8x8 Work desk phones and/or the 8x8 Work for Desktop application.
  • When your 8x8 Voice for Teams service is a mixed environment which includes both Teams users and 8x8 Work users.

• Emergency Routing Service portal: This refers to the administrative portal where Nomadic 911 location detection configuration is applied regarding only 8x8 Work extension users.
  • This portal is not used in any way for Microsoft Teams application user location detection.

• Emergency Routing Service option: This refers to the Nomadic 911 service enablement option in 8x8 Admin Console user profiles.
  • This option is required to be enabled for both 8x8 Voice for Microsoft Teams and 8x8 Work users.
  • Please see the section Enable Emergency Routing Service for Users in 8x8 Admin Console below for further information.
    
    
    

Deployment

• Set Up Trusted IP Addresses
• Set Up Emergency Addresses
• Set Up Networks & Locations
• Set Up Emergency Call Routing Policy
• Set Up Emergency Calling Policy
• Set Up Network Sites (Optional)
• Enable Emergency Routing Service for Users in 8x8 Admin Console

Set Up Trusted IP Addresses

• Entry of Trusted IPs is critical: When the Teams application is determining its location, the Trusted IPs are checked before anything else. If no match is found, the emergency location discovery process will fail.
• All public IP addresses that will be presented by Teams clients when connected to the corporate network (their public NAT IP) must be defined in the Trusted IP list. This includes IPv4 and IPv6 addresses.

• Changes to Locations > Network Topology in the Microsoft Teams admin center environment (such as Trusted IPs) can take up to two hours to become operationally active due to Microsoft's caching process.

1. In the Microsoft Teams admin center, navigate to Locations > Network topology and click on the Trusted IPs tab.
2. Click Add.
3. In the Edit trusted IP address pane, add the following information:
   • IP version: Select IPv4 or IPv6 for the type of address you're adding. Microsoft recommends that you add both to your configuration, when possible (you would need to add a new entry for each).
   • IP address: Enter the external public IP address your connectivity provider has assigned to your site internet (WAN) connection.
   • Network range: Enter a number between 0 and 32 for IPv4 addresses, or 0 through 128 for IPv6 addresses. This is the Mask Bits number of the subnet that the IP address resides in, and governs the total number of hosts that can exist within that subnet. Typically for an address range of a single host, you would enter 32 for IPv4 and 128 for IPv6.
   • Description: In this optional field, you can place identifying information that will appear in the list display of Trusted IPs.
4. Click Save.
5. Repeat this process for each external IP address that your Teams clients may use when connecting from your corporate locations to the Microsoft Teams platform. If using both IPv4 and IPv6 in your environment, configure both.

Set Up Emergency Addresses

Add Emergency Addresses (a.k.a. Civic Address)

1. In the Microsoft Teams admin center, navigate to Locations > Emergency addresses.
2. Click + Add.

3. Enter a name for your emergency address. This name will appear in the Description field as a label for the address entry.
4. In County or Region, click the dropdown arrow and select United States or Canada.
5. Enter the physical address:
   • Set Input address manually to On if you want to manually enter each detail of the physical location information, including GPS Latitude and Longitude info.
   • Set Input address manually to Off if you want the service to automatically add the physical location information for you, including GPS Latitude and Longitude.
6. Click Save.
7. Repeat the process above for each of your Teams user's distinct (corporate) civic address locations, as needed.

Add Place Information to your Emergency Addresses

1. In the Microsoft Teams admin center, navigate to Locations > Emergency addresses.
2. Click on the Description name of the emergency address your are altering.

3. On the Places tab, click + Add to begin adding places within your Emergency Address (a.k.a. Civic Address).

4. Enter a unique Name for the place, and click Apply.

5. Create Places for each Location (civic address) that you've added to your configuration, as needed.

Set Up Networks & Locations

1. In the Microsoft Teams admin center, navigate to Locations > Networks & locations. You'll see tab options for each of the following:
   • Subnets
   • Wi-Fi access points
   • Switches
   • Ports

2. Click on each location type's individual tab (such as Subnets) and click + Add to begin adding them to your configuration.
3. During the process, search for and select the correct civic address, which you will have added in previous steps. This can be narrowed down to specific Places within the civic address, if you've already added them in the steps above.
4. Click Apply to save each change.
5. Perform the above steps for all locations (civic addresses) and places from which your Teams client users will operate.

• Wi-Fi access points
• Ports
• Switches
• Subnets

Set Up Emergency Call Routing Policy

1. In the Microsoft Teams admin center, navigate to Voice > Emergency Policies.
2. Click on the Call routing policies tab.

3. Click + Add.
4. Enter a unique name for your new policy.
5. Enable Dynamic emergency calling by clicking the switch to select On 
   
   .
6. In Emergency numbers:
   1. Click + Add.
   2. In Emergency dial string, enter 911.
   3. In PSTN usage record, search for 8x8 and select either the 8x8-USW or 8x8-USE PSTN usage record.
   4. Click + Add again.
   5. In Emergency dial string, enter 933.
   6. In PSTN usage record, search for 8x8 and select either the 8x8-USW or 8x8-USE PSTN usage record.
   7. Emergency dial mask is not required.
7. When you are finished, click Save at the bottom of the page.
8. Your new policy is now ready to assign to your 8x8 Voice for Microsoft Teams users.

Set Up Emergency Calling Policy

1. In the Microsoft Teams admin center, navigate to Voice > Emergency Policies.
2. Click on the Calling policies tab.

3. Click + Add.
4. In the side panel at the right (see screenshot, below), enter a unique Name for your new policy.
5. Set External location lookup mode to On or Off, depending on your requirements:
   • If set to On, Teams users will be allowed to set Emergency addresses for remote locations (i.e. when they are outside of their corporate network, so that their public IP address does not match any of your configured trusted IP addresses).
   • Regardless of the setting: whenever corporate location detection has failed (or if an address has been entered manually), user emergency calls will be routed to a non-PSAP emergency call center, where an emergency service operator must ask for location details. Additionally, 933 calls in this case will not provide location information.
6. In Notification mode, select the type of notification that will be initiated when a user makes an emergency call:
   • Send notification only: A Teams chat message is sent to the users and groups that you specify in the Notification group.
   • Conferenced in but are muted: Users or groups listed in the Notification group are automatically conferenced into the user's emergency call, and are muted. The conferenced users cannot be unmuted.
     • Enter an E.164-formatted phone number (+1xxxyyyzzzz) in Numbers to dial for emergency calls notifications.
   • Conferenced in and are unmuted: Users or groups listed in the Notification group are automatically conferenced into the user's emergency call, and are unmuted. The conferenced users cannot be muted.
     • Enter an E.164-formatted phone number (+1xxxyyyzzzz) in Numbers to dial for emergency calls notifications.
7. In Users and groups for emergency calls notifications, search for and select users and/or groups who will be notified when an emergency call is made.
8. Click Apply to save your policy settings.
9. You can now assign your custom Emergency Calling Policy to your 8x8 Voice for Microsoft Teams users.

Set Up Network Sites (Optional)

• Network sites allow for a user’s default emergency calling and call routing policies to be overridden with site-specific policies if the user is detected as being at that site.
• Site detection is ONLY on private IP addresses, as configured in the Network sites section.
• Site detection is used purely to determine the user’s applied policies, and has no relation to location detection.

1. In the Microsoft Teams admin center, navigate to Locations > Network topology.
2. Click on the Network sites tab if it's not already selected.
3. Click Add.

4. Add a unique Network Site name and a Description (optional) for the site.
5. Click Add network region as needed. Click Add to create a network region (collection of network sites), and then click Link to connect your new site to a network region.

6. Enable/disable Location based routing depending on your requirements. You can find more information about that, here.
7. Set the Emergency calling policy and Emergency call routing policy that should apply to users in this network site.

8. Click Add subnets. Per Microsoft:
   • "Each subnet must be associated with a specific network site. A client's location is determined based on the network subnet and the associated network site. You can associate multiple subnets with the same network site, but you can't associate multiple sites with the same subnet. Learn more"
9. Select the IP version to be used:
   • IPv4
   • IPv6
10. In IP address, enter the subnet ID. For example, 10.10.10.0.
11. In Network range, enter the mask bits of the subnet, ranging from 0-32 (IPv4) or 0-128 (IPv6).
    • Example. If your 10.10.10.0 IPv4 subnet has a total range of 10.10.10.0-10.10.10.127, allowing for host IPs from 10.10.10.1-10.10.10.126, the network range would be 25.
12. Enter a Description of the Subnet, as needed.
13. Click Apply.

14. Click Save to complete the configuration of your network site.

Enable Emergency Routing Service for Users in 8x8 Admin Console

• Enabling Individual Users
• Enabling Multiple Users

Enabling Individual Users

1. Log in to the 8x8 Admin Console as an administrator.
2. Navigate to Home > Users.
3. Click on the pencil icon
   
    at the far right of a user to begin editing their user profile.

4. Scroll down to Services and permissions.
5. Click on the Enable Emergency Routing Service slider switch
   
    to enable it.
6. Click Save at the bottom of the page to complete the change.

Enabling Multiple Users

1. Log in to the 8x8 Admin Console as an administrator.
2. Navigate to Home > Users.
3. Click the check box next to each user of 8x8 Voice for Teams to select them.
4. Click Bulk Edit at the top-right.
   • This option will only appear after you've selected at least one user to edit.

5. In Home / Users / Bulk Edit, scroll down to Services and permissions.
6. Click on the Enable Emergency Routing Service slider switch
   
    to select the option and enable it.
7. Click Continue at the bottom of the page.

8. In the Review window, verify the change that you are making to multiple users.
9. Finally, click Confirm Bulk Edits at the bottom of the page to complete the change.

External Resources

• Plan and configure dynamic emergency calling
• Microsoft Teams Dynamic Emergency Calling (Video, 01:13:44)
• Microsoft Teams Emergency Calling Explained (Video, 00:07:48 Introduction)