[This is pre-release documentation and subject to change in future releases. This topic's current status is: Milestone-Ready]

Topic Last Modified: 2010-07-14

Effective planning for Enhanced 9-1-1 requires that you take into account the following:

Deployment Prerequisites for E9-1-1

Before you deploy E9-1-1, you must already have deployed your Microsoft Communications Server 2010 internal servers, including either an Enterprise pool or a Standard Edition server, and Communications Server 2010 clients. In addition, an E9-1-1 deployment requires A SIP connection to a certified Emergency Service Provider. Communications Server only supports using E9-1-1 with certified Emergency Services Providers located inside of the United States.

Deployment Process

The following table provides an overview of the E9-1-1 deployment process. For details about deployment steps, see Configure Enhanced 9-1-1 in the deployment documentation.

Phase Steps Permissions Documentation

Configure Voice Routes
  1. Create a new PSTN usage record using the same name that is used for the PSTN setting in the Location Policy.

  2. Create a new voice route using the PSTN usage record created in the previous step

  3. Optionally, create a local route for calls that are not handled by the Emergency Server Provider’s SIP Trunk.

Administrators group

Configure an E9-1-1 Voice Route

Create Location Policies and assign them to users and subnets
  1. Create a tagged Location Policy.

  2. Assign the tagged location policy to user policies.

  3. Assign the tagged Location Policy to subnets

    • Assign the tagged location policy to an existing or new network site.

    • Add the appropriate subnets to the network site.

Administrators group

Create Location Policies

Adding a Location Policy to a Network Site

Associate Subnets with Network Sites for E9-1-1

Configure the Location Database
  1. Populate the database with a mapping of network elements to locations.

  2. Validate the addresses against the Master Street Address Guide (MSAG) maintained by the Emergency Services Provider.

  3. Publish the updated database.

Administrators group

Configure the Location Database

Configure Advanced Features (Optional)
  1. configure the URL for the SNMP application.

  2. configure the URL for the location of the Secondary Location database.

Administrators group

Configure an SNMP Application

Configure a Secondary Location Database