Versions Compared

Old Version 4

changes.mady.by.user Ribbon Communications

Saved on

compared with

New Version Current

changes.mady.by.user Ribbon Communications

Saved on

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 

Spacevars
0product
 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 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 (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

...

  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.

    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 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.

    Panel
    borderStylenone

    Caption
    0Figure
    1Configure Dial Plan

...

Note

...

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 

    Spacevars
    0product
     gateway selected in Associated Gateways 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 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.
Panel
borderStylenone

Caption
0Figure
1Trunk Configuration

...

Create a Location Information Server (LIS) Subnet

...

  1. Launch Lync Server Management Shell.

  2. 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 shown below.

  3. Press Enter.
Panel
borderStylenone

Caption
0Figure
1Create LIS Subnet

Image RemovedImage Added

 

Pagebreak

Location Policy Configuration

...

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 Settings tab.

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

  3. In the MIME PayloadsPayloads panel:
    1. Configure the ELIN Identifier field as shown below: as LOC.

    2. Configure 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 SIP trunking:

...

Transformation Table for calls to E911

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.

Tip

For instructions on creating and modifying transformation tables, see Managing Transformation Tables and its child pages.

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

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 Settings tab.
  2. In the left navigation pane, go to click Transformation.

  3. Create Click (plus) to create a new Transformation Table with . Configure the new table with the following ELIN Identifier, Called Address/Number, and Calling Address/NumberNumber field types as shown below.

    Panel
    borderStylenone

    :

    Caption
    0

    Figure

    Table
    1Transformation Table Entries - 911 Fallback

    Calls

    Image Removed

Call Routing

  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 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.

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 

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 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/2000the 

Spacevars
0product
:

Panel
borderStylenone

Caption
0Figure
1Tracing Relevant Inbound INVITE Message

Pagebreak