In this section:
In this article, we describe the necessary steps to configure
Topology
There are two types of 911 (emergency) calls, Basic and Enhanced:
When Enhanced Emergency Services are enabled in Lync, location information about a 911 caller is passed to the destination (emergency services dispatcher, police, fire, etc.). 911 calls from Lync clients signed-in at an office location include location information, calls from Lync clients not signed in at an office location are connected to the destination using a fallback 911 route which does not contain location information.
Related Articles
The Lync side configuration steps are accomplished using the following tools:
To configure the location policy:
Edit the Global Location Policy as shown below.
Configure Location Policy
Ensure to Commit the changes after configuring the attributes.
To configure a dial plan:
Add a new Normalization Rule for 911 call as shown below.
Configure Dial Plan
Make sure to Commit the changes after configuring the attributes shown above.
Be sure to have the relevant
Route Configuration
Make sure to Commit the changes after configuring the attributes shown above.
Get-CSTrunkConfiguration
command.EnablePIDFLOSupport
attribute is True. If not:Set-CSTrunkConfiguration -EnablePIDFLOSupport $True
script.Get-CSTrunkConfiguration
returns a EnablePIDFLOSupport
attribute as True, as shown below.Trunk Configuration
This set of steps creates a Location Information Server (LIS) subnet. LIS Subnets are used to associate a location with a specific subnet. LIS Subnets are used in Enhanced 9-1-1 (E9-1-1) Enterprise Voice implementations to notify an emergency services operator of the caller's location.
To create a Location Information Server Subnet:
Set-CsLisSubnet -Subnet 134.56.105.0 -Description "Cubicle" -Location "Office" -CompanyName "Ribbon" -HouseNumber "6900" -PreDirectional N -StreetName "Paseo Padre" -StreetSuffix "Pkwy" -City "Fremont" -State "CA" -PostalCode 94555 -Country US
as shown below.Create LIS Subnet
Location Policy Configuration
Make sure to Commit the changes after configuring the attributes shown above.
The configuration steps on the
As an alternative, you can configure the SBC Edge using an easy configuration wizard, see Using Lync Setup for E911 Configuration.
Configure the PDIF-LO Passthrough field as Enable.
This example uses two Transformation Tables to route calls to a 911 Provider over SIP trunking:
A Transformation entry is created for Lync E911, which includes table entries for Called Address/Number, ELIN Identifier, and Callback Pool Identifier (the emergency call back number table or Pasthrough ELIN number used for calls destined to 911). For specific information about the Passthrough ELIN Number, see Creating and Modifying Entries to Transformation Tables.
For easy identification, the Description field matches the Scenario description you configured in Lync Setup.
For instructions on creating and modifying transformation tables, see Managing Transformation Tables and its child pages.
Transformation Table Entries - Calls to E911
Input Field Type | Input Field Value | Output Field Type | Output Field Value | Match Type |
---|---|---|---|---|
ELIN Identifier | (.*) | Callback Pool Identifier | noEntries | Mandatory (Must Match) |
Called Address/Number | \+911 | Called Address/Number | 911 | Mandatory (Must Match) |
Calling Address Number | \+.#(\d{4}) | Calling Address/Number | +1510564\1 | Mandatory (Must Match) |
Click to create a new Transformation Table. Configure the new table with the following ELIN Identifier, Called Address/Number, and Calling Address/Number field types:
Transformation Table Entries - 911 Fallback
Input Field Type | Input Field Value | Output Field Type | Output Field Value | Match Type |
---|---|---|---|---|
ELIN Identifier | (.*) | Calling Name | OtherLocations | Mandatory (Must Match) |
Called Address/Number | \+911 | Called Address/Number | 9911 | Mandatory (Must Match) |
Calling Address Number | \+.#(\d{4}) | Calling Address/Number | +1510246\1 | Mandatory (Must Match) |
A Lync E911 entry is created in the Call Routing Table for routing calls from SIP to ISDN. For more information about Call Routing Tables, see Managing Call Routing Tables.
Add two entries (see below for configuration): one for calls with configured Office Location Information, and another one that does not have the Location Information as Office. Note that both route entries are destined to 911 Provider over a SIP Trunk.
Transformation Table Entries - Calls to E911
Transformation Table | Destination Type | First Signaling Group | Description |
---|---|---|---|
SBA: To E911 | Normal | (SIP) SIPp Server SIP Trunk | To E911 |
911 Fallback | Normal | (SIP) SIPp Server SIP Trunk | To 911 as Fallback form Other Locations |
Calling Address Number | \+.#(\d{4}) | Calling Address/Number | +1510564\1 |
In the example configuration, when a 911 call from Lync client arrives on the
This can be verified in the logs by tracing the relevant inbound INVITE message from Lync to the
Tracing Relevant Inbound INVITE Message