John Miller / / Categories: Microsoft Teams Calling

Location Scoping of Teams Emergency Policies

Introduction

This article discusses how to dynamically assign Teams Emergency Calling and Emergency Call Routing policies to an emergency services caller based on their current physical location. While Teams Location Based Routing (LBR) and Local Media Optimization (LMO) use the same objects described below, this article does not discuss location scoping for either of these features

This is a completely optional configuration task when configuring Microsoft Teams Dynamic 911 calling. If you are only configuring the “Global” instances of the Teams Emergency Calling and Emergency Call Routing policies, you need not read any further! This article is for those who need to configure several versions of either of these policies and dynamically assign them to their users based on where on the client’s internal networks the users are connected when they make an emergency call

In this series of articles about setting up Microsoft Teams Dynamic 911 we have talked about configuring dispatchable locations to be used when Teams users make emergency calls. One of the components in that configuration are Location Information System (LIS) subnets. The LIS subnets and the Tenant Network Subnets described in this article are used for two (2) completely different purposes. Yes, if you are setting up location scoped Teams Emergency Policies, you will be referencing the same subnets that you referenced when setting up the dispatchable locations to comply with the RAY BAUM act, you will be adding your subnets to Teams twice!

Why do we need Location Based Scoping of the Teams Emergency Policies?

Emergency Calling Policies

  • Emergency Calling Policies are used to satisfy the notification requirements of Kari’s Law
  • The policies specify the type and to whom notifications should be sent when a user makes an emergency services call
  • If you are sending the notifications to the same user or the same group of users, the Global Emergency Calling policy is the answer
  • If you want to send notifications to different groups of users based on the caller’s location on the internal networks, you will need to configure location based scoping

Emergency Call Routing Policies

  • Emergency Call Routing Policies are used to:
    • Define the format of the emergency services numbers as they are presented to the Session Border Controllers (SBCs); 911, 933, etc
    • List the acceptable formats of the emergency services numbers dialed by the users. For example 911, 112, etc
    • Mapping the presented numbers to Teams PSTN Usages. The Usages and underlying Voice Routes are used to deliver the emergency calls to the SBCs
  • If all your users use the same dialstrings to place emergency services calls and you only have one Teams Direct Routing SBC, you can use the Global Emergency Call Routing policy
  • If you have users in different countries, you will almost certainly need more than one policy and you should be able to leverage location based scoping to dynamically assign the policies based on the emergency callers location
  • If you have multiple SBCs, you will need to use location based scoping if you are routing calls to the SBCs based on where the calls are coming from on your internal networks. If you have multiple SBCs to provide resiliency, you probably will not need more than one Emergency Call Routing policy nor will you need location-based scoping

Configuring Teams to provide Location Scoped Emergency Policies

  • As a reminder, the Teams Emergency Calling policy applies to both Microsoft Teams Calling Plan and Direct Routing users. The Teams Emergency Call Routing policy is for Direct Routing users only
  • To enable location scoping of these policies, you will have to configure:
    • Teams Tenant Trusted IP Addresses
    • Teams Tenant Network Regions
    • Teams Tenant Network Sites
    • Teams Tenant Network Subnets
  • You will also have to configure Teams Emergency Calling and Emergency Call Routing policies to be associated with the created Tenant Network Sites. The creation of these policies is covered in another article in this series. These policies can also be assigned directly to specific users. If a policy is assigned to a user, the policy will be in effect regardless of where the users is located when they call emergency services
  • A Tenant Network Site can only be associated with one (1) Teams Emergency Calling Policy and one (1) Teams Emergency Call Routing Policy. It is perfectly acceptable for a Tenant Network Site to assign an Emergency Calling Policy appropriate to the site and to “let” the Tenant Network Site use the “Global” Emergency Call Routing Policy. The reverse is also true

Teams Tenant Trusted IP Addresses

  • Required for implementing location scoped Teams Emergency policies
  • If you have configured Microsoft Teams to comply with the RAY BAUM Act to provide dynamic dispatchable locations to a Public Safety Answering Point (PSAP) or Emergency Routing Service Provider (ERSP), you will have already added these addresses to Teams
  • Teams Tenant Trusted IPs are used to determine whether the caller is making an Emergency Services call from an internal network
  • An IPv4 Tenant Trusted IP record should be added for all routers, firewalls, or other perimeter devices that provide user access to the Internet
  • Entries can be made for single IP addresses or a range based on the address and a subnet mask
  • Microsoft recommends that both an IPv4 and IPv6 address for these devices be added to the Tenant Trusted IP table
    • If not already configured, the client should ask their Internet Service Provider (ISP) to provision an IPv6 address for their devices providing Direct Internet Access (DIA) to their users.
    • These can be single IPv6 addresses or ranges with subnet masks like the IPv4 addresses. All addresses should be statically provided by the ISPs
    • The device will have to be configured to listen for and send traffic using IPv6
    • The client’s internal networks do not need to be configured to support IPv6 addressing or routing

Tenant Network Regions

  • Tenant Network Sites must be assigned to a Tenant Network Region
  • Tenant Network Regions are not directly used for dynamic Emergency policy assignment. They come more into play with Teams LBR and LMO
  • If you are not using Teams LBR or LMO, then create a Region for each Country in which you have a location

Tenant Network Sites

  • Tenant Network Sites contain one or more Tenant Network Subnets and must be assigned to a Tenant Network Region
  • Tenant Network Sites can be used to assign Teams Emergency Calling Policies and Teams Emergency Routing Policies to different sets of users within a Company
  • The number of configured Tenant Network Sites and the numbers of Teams Emergency Locations\Places will probably not be the same. It is the nature of the beast
  • The layout of your Tenant Network Sites will depend on combining the requirements for Teams Emergency Calling and Teams Emergency Call Routing Policies. If you determine that you can use a “Global” Teams Emergency Call Routing Policy, you will not need to create any Tenant Network Sites. However, if you need to have several Site centric Teams Emergency Calling Policies, you will need to create Tenant Network Sites. The location scoping requirements of both policies need to be considered when determining the setup of your Tenant Network Sites and Tenant Network Subnets
  • It is generally best to create one Tenant Network Site for each of your buildings and add all the subnets in the building as Tenant Network Subnets. This provides a normalized starting point and flexibility in assigning Teams Emergency Calling and Teams Emergency Call Routing policies

Adding Teams Emergency Calling and Emergency Call Routing Policies

Adding Tenant Trusted IP Addresses

Teams Admin Center

  1. In the Teams Admin Center click on “Locations” then “Network topology” then the “Trusted IPs” tab. Click the “Add” button

miller1

2. Click the “IP Version” drop down and select “IPv4” or “IPv6”
3. Enter the IP Address in the “IP address” field
4. Put the subnet mask in the “Network Range” field
5. Add a description as required
6. Click the “Apply” button

miller2

 

Teams PowerShell Module

  • Teams Tenant Trusted IP addresses can be added through the Teams Online PowerShell Module
  • To create a new Tenant Trusted IP address, you will need to use the New-CsTenantTrustedIPAddress command

If you are going to add these with a PowerShell Script, you will need a Comma Separated Value file with the required information properly formatted.

Adding Teams Tenant Network Regions

  • The Teams PowerShell commands to manage the Tenant Network Regions are:

New-CsTenantNetworkRegion

Get-CsTenantNetworkRegion

Remove-CsTenantNetworkRegion

Set-CsTenantNetworkRegion

  • Most customers who are not also implementing Teams LBR or LMO will not have very many Tenant Network Regions to Teams. Manage these regions in the Admin Center instead of through PowerShell

Teams Admin Center

To add a Tenant Network Region through the Teams Admin Center, click on “Locations” then “Network Topology” and “Manage Network Regions” in the upper right-hand corner of the screen

miller3

2. Click in the entry box and enter the name of the region then click the “Add” button then the “Close” button on receipt of the notification that the region has been added

miller4

Teams PowerShell

  • Tenant Network Regions can be added through the Teams Online PowerShell Module
  • To create a new Tenant Network Region, you will need to use the New-CsTenantNetworkRegion command
  • If you are going to add these with a PowerShell Script, you will need a Comma Separated Value file with the required information properly formatted

 

Adding Teams Tenant Network Sites

  • The Teams PowerShell commands to manage Teams Tenant Network Sites are:

New-CsTenantNetworkSite

Get-CsTenantNetworkSite

Remove-CsTenantNetworkSite

Set-CsTenantNetworkSite

  • If you have a lot of Tenant Network Sites to add, consider using the Teams Online PowerShell Module instead of the Teams Admin Center

Teams Admin Center

1. To add a Tenant Network Site through the Teams Admin Center, click on “Locations” then “Network Topology” and click the “Network Sites” tab then the “Add” button

miller5

2. Fill in the form:
         o Add Network Site – This is the name of the Site
         o Description – An optional description
         o Add network region – Click the “+” sign and select an existing region or add one
         o Emergency calling policy – Select the previously created policy appropriate to the site
         o Emergency call routing policy - Select the previously created policy appropriate to the site
3. Click the “Save” button. The subnets will be added in the next step

Teams PowerShell

  • Tenant Network Regions can be added through the Teams Online PowerShell Module
  • To create a new Tenant Network Site, you will need to use the New-CsTenantNetworkSite command
  • If you are going to add these with a PowerShell Script, you will need a Comma Separated Value file with the required information properly formatted

Adding Teams Tenant Network Subnets

  • The Description field is optional but will help you clearly identify where the subnets are
  • The Teams PowerShell commands to manage Teams Tenant Network Sites are:

New-CsTenantNetworkSubnet

Get-CsTenantNetworkSubnet

Remove-CsTenantNetworkSubnet

Set-CsTenantNetworkSubnet

  • If you have a lot of Tenant Network Subnets to add, consider using the Teams Online PowerShell Module instead of the Teams Admin Center

Teams Admin Center

1. To add a Tenant Network Subnet to an existing Tenant Network Site, click on the Site then click the “Add” button

miller6

2. Fill in the form:
       o IP Version – Select IPv4 or IPv6
       o IP address – Enter the IP Address of the subnet
       o Network Range – Enter the subnet mask
       o Description – Enter a Description providing the location of the subnet
3. Click the “Apply” button

miller7

Teams PowerShell

  • Teams Tenant Subnets addresses can be added through the Teams Online PowerShell Module
  • command
  • If you are going to add these with a PowerShell Script, you will need a Comma Separated Value file with the required information properly formatted

Summary

  • Teams Emergency Calling and Emergency Call Routing policies can be dynamically assigned to 911 callers based on their current location
  • Configuring Tenant Network Regions, Sites and Subnets provides the mechanism to assign site centric Teams Emergency Policies
  • They can also be used when implementing LBR or LMO
  • The Tenant Network Subnets should not be confused with the Location Information Database (LIS) subnets. They are used for different purposes
  • You do not need to configure Tenant Network Regions, Sites or subnets if you do not need to dynamically assign the Teams Emergency Policies based on the emergency caller’s current location

Work with our team of Cloud Computing Consultants who have done this so many times they know all of the “minefields” to prevent missteps.

Subscribe to Email Updates

Refine by

To expand the list, please click on the double arrows.

 

Search by Category or Author:

ref:_00D80KtFf._5000y1WwWQD:ref