Page History

Panel

Add_workflow_for_techpubs AUTH1 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'} JIRAIDAUTH SYM-23175 REV5 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'} REV6 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'} REV3 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26ce320b29, userName='null'} REV1 UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc0e070f, userName='null'} In this section: Table of Contents maxLevel 3

...

In this article, we describe the necessary steps to configure 

Spacevars
0 product

 and Lync for Enhanced Emergency Services (E911) support.

Caption
0 Figure 1 Topology

...

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
   borderStyle none
   Caption 0 Figure 1 Configure Location Policy

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
   borderStyle none
   Caption 0 Figure 1 Configure 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
   0 product

    gateway selected in Associated Gateways field as shown below.

   Panel
   borderStyle none
   Caption 0 Figure 1 Route 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
borderStyle none
Caption 0 Figure 1 Create LIS Subnet Image AddedImage Removed

Pagebreak

Location Policy Configuration

...

Panel
borderStyle none
Caption 0 Figure 1 Location Policy Configuration

...

Note

...

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

Ribbon SBC Edge Configuration

...

• SIP Profiles
• Number Transformation
• Call Routing

...

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

...

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, click Transformation.
3. 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: 

Caption
0 Table 1 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)

Note
icon false
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, click Transformation.

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

   Caption
   0 Table 1 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)

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

...

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.
   
   

...

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

Pagebreak

Call Flow

In the example configuration, when a 911 call from Lync client arrives on the 

Spacevars
0 product

 with the Location Information as Office, Lync will then provide the relevant location profile in the Inbound INVITE message.

Spacevars
0 company

 

Spacevars
0 longproduct

then passes this information to the 911 Provider in the outbound INVITE message.

...