Nomadic 911: 8x8 Voice for Teams Configuration

Other Deployment Information to be Aware of

Set Up Trusted IP Addresses

Trusted IPs are your public, external internet addresses tied to your enterprise network (typically through NAT).

They are used to determine whether or not the Teams user client application is connected through your corporate network. This in turn affects how the Teams client app behaves when a location is detected, or when no location is detected.

Important: 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. Also: 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.

To add a Trusted IP address:

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

Emergency addresses consist of a physical Civic Address (required) plus any optional Places contained within those civic addresses.

Places represent the more granular dispatchable locations to which an emergency responder can be directed. For example: Building 2, Floor 3, North West corner, etc.

Once a Civic Address has been added, you'll have access to add/change Places and their Subnets, Wi-Fi access points, Switches, and Ports.

Set Up Networks & Locations

Here you'll provide the network infrastructure information used in the detection of user location, based on the network connection that the Teams client app is currently using.

Important: 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 > 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.

Connection matching precedence: The Teams service will check through your configuration in the following order, when trying to determine a user's location and place information:

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

Set Up Emergency Call Routing Policy

In this section, you'll create or configure an Emergency Call Routing Policy.

Emergency Call Routing Policies are not related to user location discovery. Instead, they are used to set up emergency numbers for Direct Routing (e.g. 8x8 Voice for Microsoft Teams) and then specify how those emergency calls are routed.

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

Note: We've chosen to create a custom Emergency Call Routing Policy in our example, but you can edit the Global (Org-wide default) policy instead, if desired.

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.

When a Teams user dials 911 or 933, Teams should display the detected phone number and location the user is making the call from.

The answering 933 test service receives the same information that is relayed during an actual emergency 911 call. But instead of routing to an emergency services operator, the 933 service will play back the caller's detected phone number and address for verification.

Set Up Emergency Calling Policy

In this section, you'll create or configure an Emergency Calling Policy.

Emergency Calling Policies control how Teams users in your organization can use specific dynamic emergency calling features, and are not related to user location discovery.

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

Note: We've chosen to create a custom Emergency Calling Policy in our example, but you can edit the Global (Org-wide default) policy instead, if desired.

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 configuration (within Locations > Network Topology) is a collection of unique IP subnets used strictly to determine the policies applied to emergency call routing and calling.

• 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.

To configure Network Sites:

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

In addition to configuration of your Microsoft Teams tenant, you must enable the Emergency Routing Service option in the 8x8 Admin Console for each 8x8 Voice for Microsoft Teams user.

Enabling this option is required for the background provisioning of the 8x8 Voice for Microsoft Teams user's phone number (not location information) with Broadband, who handles emergency call services for Microsoft Teams users in general.

• Enabling Individual Users
• Enabling Multiple Users