Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Panel

Add_workflow_for_techpubs
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
JIRAIDAUTHSYM-23175
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ce320b29, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc0e070f, userName='null'}

In this section:

Table of Contents
maxLevel3

 

In this article, we describe the necessary steps to configure configure 

Spacevars
0product
and  and Lync for Enhanced Emergency Services (E911) support.

...

Caption

...

0

...

Figure

...

1Topology

...

Image Added

Overview

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

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

When When Enhanced Emergency Services are  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

...

To configure the location policy:

  1. Launch Launch Lync Server 2010 Configuration Manager.

  2. Click Click Network Configuration on  on left pane.

  3. Click Click Location Policy on  on right pane.

  4. Edit the the Global Location  Location Policy as shown below.

    Panel
    borderStylenone

    Caption
    0Figure
    1Configure Location Policy

    Pagebreak

     

 

...

Note

Ensure to Commit the changes after configuring the attributes

...

.

Dial Plan Configuration

To configure a dial plan:

  1. Launch Launch Lync Server 2010 Configuration Manager.

  2. Click Click Voice Routing on  on left pane.

  3. Click Click Dial Plan on  on right pane.

  4. Edit the the Dial Plan as  as required.

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

    Panel
    borderStylenone

    Caption
    0Figure
    1Configure Dial Plan

...

Note

...

Make sure

...

to Commit

...

 the changes after configuring the attributes shown above.

Route Configuration

  1. Launch Launch Lync Server 2010 Configuration Manager.
         
  2. Click Click Voice Routing on  on left pane.

  3. Click Click Route on  on right pane.

  4. Edit the relevant relevant Voice Route and  and add a new new Pattern for  for 911 call.
         
  5. Be sure to have the relevant 

    Spacevars
    0product
    gateway  gateway selected in in Associated Gateways field  field as shown below.

    Panel
    borderStylenone

    Caption
    0Figure
    1Route Configuration

...

Note

...

Make sure

...

to Commit

...

 the changes after configuring the attributes shown above.

Trunk Configuration

  1. Launch Launch Lync Server Management Shell.

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

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

Caption
0Figure
1Trunk Configuration

...

Create a Location Information Server (LIS) Subnet

...

To create a Location Information Server Subnet:

  1. Launch Launch Lync Server Management Shell.

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

  3. Press Press Enter.
Panel
borderStylenone

Caption
0Figure
1Create LIS Subnet

Image RemovedImage Added

 

Pagebreak

Location Policy Configuration

  1. Launch Launch Lync Server 2010 Configuration Manager.

  2. Click Click Network Configuration on  on left pane.

  3. Click Click Location Policy on  on right pane.

  4. Edit the relevant relevant Voice Route.

  5. Select the the Enable enhanced emergency services check  check box.
Panel
borderStylenone

Caption
0Figure
1Location Policy Configuration

...

Note

...

Make sure

...

to Commit

...

 the changes after configuring the attributes shown above.

...

Ribbon SBC

...

Edge Configuration

The configuration steps on the Sonus SBC 1000/2000 are the 

Spacevars
0product
 are achieved directly via the WebUI broken down in the following sections:

Note

As an alternative, you can configure the SBC Edge using an easy configuration wizard, see Using Lync Setup for E911 Configuration.

SIP Profiles

  1. In the WebUI, click the the Settings tab tab.

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

  3. In the the MIME PayloadsPayloads panel:
    1. Configure the the ELIN Identifier field as shown below: LOC.
    2. Configure the the PDIF-LO Passthrough field as shown below:

      Panel
      borderStylenone

      Caption
      0Figure
      1SIP Profiles

      Image Removed

      Pagebreak

       

Number Transformation

    1. Enable.

Number Transformation

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

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

Transformation Table for calls to E911

Tip
  1. In the WebUI, click the the Settings tab tab.
  2. In the left navigation pane, go to click Transformation.
  3. Create a new Click (plus) to create a new Transformation TableConfigure the new table with the following ELIN Identifier, Called Address/Number, and and Calling Address/NumberNumber field types as shown below. Panel
    borderStylenone

Caption
0

...

Table
1Transformation Table Entries - Calls to E911

...

Image Removed

 

Input Field TypeInput Field ValueOutput Field TypeOutput Field ValueMatch Type
ELIN Identifier(.*)Callback Pool IdentifiernoEntriesMandatory (Must Match)
Called Address/Number\+911Called Address/Number911Mandatory (Must Match)
Calling Address Number\+.#(\d{4})Calling Address/Number+1510564\1Mandatory (Must Match)

...

Note
iconfalse

...

Use the appropriate value for your location in the Calling Address/Number > Output Field Value field.

The Output Field value "

...

noEntries" is only an example.

...

You could use a partial string match or a regular expression to catch all (.*).

Pagebreak

 

Transformation Table for 911 Fallback calls

  1. In the WebUI, click the the Settings tab tab.
  2. In the left navigation pane, go to click Transformation.
  3. Create a new Click (plus) to create a new Transformation TableConfigure the new table with the following ELIN Identifier, Called Address/Number, and and Calling Address/NumberNumber field types as shown below.

    Panel
    borderStylenone

    :

    Caption
    0

    Figure

    Table
    1Transformation Table Entries - 911 Fallback

    Calls

    Image Removed

...

  1. Input Field TypeInput Field ValueOutput Field TypeOutput Field ValueMatch Type
    ELIN Identifier(.*)Calling NameOtherLocationsMandatory (Must Match)
    Called Address/Number\+911Called Address/Number9911Mandatory (Must Match)
    Calling Address Number\+.#(\d{4})Calling Address/Number+1510246\1Mandatory (Must Match)

    Note
    iconfalse

    Use the appropriate value for your location in the Calling Address/Number > Output Field Value field.

Call Routing

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.

  1. In the WebUI, click the the Settings tab tab.
  2. In the left navigation pane, go to to Call Routing Table.
  3. Click the relevant relevant Call Route table  table used for calls received from Lync.

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.

...

Caption
0Table
1Transformation Table Entries - Calls to E911
Transformation TableDestination TypeFirst Signaling GroupDescription
SBA: To E911Normal(SIP) SIPp Server SIP TrunkTo E911
911 FallbackNormal(SIP) SIPp Server SIP TrunkTo 911 as Fallback form Other Locations
Calling Address Number\+.#(\d{4})Calling Address/Number+1510564\1

Panel
borderStylenone

Caption
0Figure
1Call Routing

Image Removed

 

...

Note
iconfalse

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

Pagebreak

 


Call Flow

With above In the example configuration, when a 911 call from Lync client arrives on the Sonus SBC 1000/2000 with the Location Information as the 

Spacevars
0product
 with the Location Information as Office, Lync will then provide the relevant location profile in the Inbound INVITE message. Sonus SBC 1000/2000
Spacevars
0company
 
Spacevars
0longproduct
then passes this information to the the 911 Provider in  in the outbound INVITE message.

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

Spacevars
0product
:

Panel
borderStylenone

Caption
0Figure
1Tracing Relevant Inbound INVITE Message

Pagebreak