Topic Last Modified: 2012-10-03
To plan effectively for Enhanced 9-1-1 (E9-1-1), be sure to include the following deployment requirements:
Deployment Prerequisites for E9-1-1
Before you deploy E9-1-1, you must already have deployed your Lync Server internal servers, including a Central Management store, a Front End pool or a Standard Edition server, one or more Mediation Servers or Mediation Server pools, and Lync Server clients. In addition, an E9-1-1 deployment requires a SIP trunk to a qualified E9-1-1 service provider or an Emergency Location Identification Number (ELIN) gateway to your public switched telephone network (PSTN). Lync Server supports using E9-1-1 service providers only inside 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 Lync Server 2013 in the Deployment documentation.
Configure voice usages, routes, and trunk configurations |
Create a new PSTN usage record. This is the same name that is used for the PSTN Usage setting in the location policy. Create or assign a voice route to the PSTN usage record created in the previous step and then point the gateway attribute to the E9-1-1 SIP trunk or ELIN gateway. For a SIP trunk E9-1-1 service provider, set the trunk that will be handling E9-1-1 calls over the SIP to pass PIDF-LO data by using the Set-CsTrunkConfiguration –EnablePIDFLOSupport cmdlet. Optionally, for a SIP trunk E9-1-1 service provider, create or assign a local PSTN route for calls that are not handled by the E9-1-1 service provider’s SIP trunk. This route will be used if the connection to the E9-1-1 service provider is not available. If supported by your E9-1-1 service provider, assign a trunk configuration rule to the gateway that translates the 911 dial string into the direct inward dialing (DID) number of the national/regional Emergency Call Response Center (ECRC). |
CSVoiceAdmin |
Configure an E9-1-1 voice route in Lync Server 2013 |
Create location policies and assign them to users and subnets |
Review the global location policy. Create a location policy with a user-level scope; or, if the organization has more than one site with different emergency usages, create a location policy with a network-level scope. Assign the location policy to network sites. Add the appropriate subnets to the network site. (Optional) Assign the location policy to user policies. |
CSVoiceAdmin
CSLocationAdmin (except for creating Location Policies) |
Create location policies in Lync Server 2013
Add a location policy to a network site in Lync Server 2013
Associate subnets with network sites for E9-1-1 in Lync Server 2013 |
Configure the location database |
Populate the database with a mapping of network elements to locations. For ELIN gateways, add the ELINs to the <CompanyName> column. Configure the connection to the E9-1-1 service provider for validating addresses. Validate the addresses with the E9-1-1 service provider. Publish the updated database. For ELIN gateways, upload the ELINs to your PSTN carrier's Automatic Location Identification (ALI) database. |
CSVoiceAdmin
CSLocationAdmin |
Configure the location database in Lync Server 2013 |
Configure Advanced Features (optional) |
Configure the URL for the SNMP application. Configure the URL for the location of the Secondary Location Information service. |
CSVoiceAdmin |
Configure an SNMP application in Lync Server 2013
Configure a secondary Location Information service in Lync Server 2013 |