Export (0) Print
Expand All

Defining your requirements for emergency calls in Lync Server 2013

 

Topic Last Modified: 2012-06-06

Before you begin a Microsoft Lync Server 2013 E9-1-1 deployment, you should first be able to answer the questions detailed in the following sections. The planning you need to do depends on the type of E9-1-1 solution that you choose to deploy—a SIP trunk E9-1-1 service provider or an Emergency Location Identification Number (ELIN) gateway. The following table identifies the sections in this planning workbook that you’ll need to review for each of those solutions.

Planning Steps by Type of E9-1-1 Solution

SIP trunk service provider ELIN gateway

Defining the scope of the E9-1-1 deployment in Lync Server 2013

Defining the scope of the E9-1-1 deployment in Lync Server 2013

Defining the network elements used to determine location in Lync Server 2013

Defining the network elements used to determine location in Lync Server 2013

Enabling users for E9-1-1 in Lync Server 2013

Enabling users for E9-1-1 in Lync Server 2013

Managing locations for SIP trunk service providers in Lync Server 2013

Managing locations for ELIN gateways in Lync Server 2013

Defining the user experience for manually acquiring a location in Lync Server 2013

Defining the user experience for manually acquiring a location in Lync Server 2013

Designing the SIP trunk for E9-1-1 in Lync Server 2013

Including the security desk in Lync Server 2013

Including the security desk in Lync Server 2013

Defining the location policy for Lync Server 2013

Choosing an E9-1-1 service provider for Lync Server 2013

Assigning location policy scope in Lync Server 2013

Defining the location policy for Lync Server 2013

Assigning location policy scope in Lync Server 2013

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft