You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

In this section:

 

In this article, we describe the necessary steps to configure

Unable to show "metadata-from": No such page "_space_variables"
and Lync for Enhanced Emergency Services (E911) support.

Topology

Overview

In the context of Internet Telephony, there are two types of 911 (emergency) calls, Basic and Enhanced:

  • Basic 911 calls contain no location information
  • Enhanced 911 calls do contain location information

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 (e.g., Starbucks, public library, etc.) are connected to the destination using a fallback 911 route which does not contain location information.

Related Articles

Central Site Configuration

The Lync side configuration steps are accomplished using the following tools:

  • Lync Server 2010 Configuration Manager
  • Lync Server Management Shell

Location Policy Configuration

To configure the location policy:

  1. Launch Lync Server 2010 Configuration Manager.

  2. Click Network Configuration on left pane.

  3. Click Location Policy on right pane.

  4. Edit the Global Location Policy as shown below.

(warning) Make sure to Commit the changes after configuring the attributes shown above.

Dial Plan Configuration

To configure a dial plan:

  1. Launch Lync Server 2010 Configuration Manager.

  2. Click Voice Routing on left pane.

  3. Click Dial Plan on right pane.

  4. Edit the Dial Plan as required.

  5. Add a new Normalization Rule for 911 call as shown below.

(warning) Make sure to Commit the changes after configuring the attributes shown above.

Route Configuration

  1. Launch Lync Server 2010 Configuration Manager.

  2. Click Voice Routing on left pane.

  3. Click Route on right pane.

  4. Edit the relevant Voice Route and add a new Pattern for 911 call.
  5. Be sure to have the relevant 
    Unable to show "metadata-from": No such page "_space_variables"
    gateway selected in Associated Gateways field as shown below.

(warning) Make sure to Commit the changes after configuring the attributes shown above.

Trunk Configuration

  1. Launch Lync Server Management Shell.

  2. Check the Trunk Configuration using Get-CSTrunkConfiguration command.

  3. Verify that EnablePIDFLOSupport attribute is True. If not:
    1. Run the Set-CSTrunkConfiguration -EnablePIDFLOSupport $True script.
    2. Press Enter.
    3. Verify that script Get-CSTrunkConfiguration returns a EnablePIDFLOSupport attribute as True, as shown below.

Create a Location Information Server (LIS) Subnet

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:

  1. Launch Lync Server Management Shell.

  2. Type Set-CsLisSubnet -Subnet 134.56.105.0 -Description "Cubicle" -Location "Office" -CompanyName "Sonus" -HouseNumber "6900" -PreDirectional N -StreetName "Paseo Padre" -StreetSuffix "Pkwy" -City "Fremont" -State "CA" -PostalCode 94555 -Country US as shown below.

  3. Press Enter.

Location Policy Configuration

  1. Launch Lync Server 2010 Configuration Manager.

  2. Click Network Configuration on left pane.

  3. Click Location Policy on right pane.

  4. Edit the relevant Voice Route.

  5. Select the Enable enhanced emergency services check box.

(warning) Make sure to Commit the changes after configuring the attributes shown above.

Sonus SBC 1000/2000 Configuration

The configuration steps on the Sonus SBC 1000/2000 are achieved directly via the WebUI broken down in the following sections:

SIP Profiles

  1. In the WebUI, click the Settings tab.

  2. In the left navigation pane, go to SIP Profiles > relevant SIP Profile.

  3. In the MIME Payloadspanel:
    1. Configure the ELIN Identifier field as shown below:

    2. Configure the PDIF-LO Passthrough fieldas shown below:

Number Transformation

In this exercise we create two Transformation Tables to route calls to a 911 Provider over SIP trunking:

  • Transformation for calls from Lync clients signed-in at Office Locations.
  • Transformation for calls from Lync clients signed-in at Remote Locations such as Starbucks, etc..

Transformation Table for calls to E911

  1. In the WebUI, click the Settings tab.

  2. In the left navigation pane, go to Transformation.

  3. Create a new Transformation Table with ELIN Identifier, Called Address/Number, and Calling Address/Numberfield types as shown below.

    The Input Match Field value "Office" is only an example. Instead of exact match, you could use a partial string match or a regular expression to catch all (.*).

Transformation Table for 911 Fallback calls

  1. In the WebUI, click the Settings tab.

  2. In the left navigation pane, go to Transformation.

  3. Create a new Transformation Table with ELIN Identifier, Called Address/Number, and Calling Address/Numberfield types as shown below.

Call Routing

  1. In the WebUI, click the Settings tab.

  2. In the left navigation pane, go to Call Routing Table.

  3. Click the relevant Call Route table used for calls received from Lync.

  4. Add two entries in the table: 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 Providerover a SIP Trunk.

    Note that when integrating with E911 providers, the Call Priority may have to be set to Emergency.

Call Flow

With above configuration, when a 911 call from Lync client arrives on the Sonus SBC 1000/2000 with the Location Information as Office, Lync will then provide the relevant location profile in the Inbound INVITE message. Sonus SBC 1000/2000 then passes this information to the 911 Provider in the outbound INVITE message.

This can be verified in the logs by tracing the relevant inbound INVITE message from Lync to Sonus SBC 1000/2000:

  • No labels