Module Overview
• Introducing Location Information Server
• Overview of Setup and Call Flow
• Designing Location Policies
• Implementing LIS
• Address Discovery
• User Experience
Lesson 1: Introducing Location Information Server
• What Is Location Awareness?
• "Location Aware" Emergency Routing
• Voice Routing
• E9-1-1 Lync Server 2013 Components
What Is Location Awareness?
• Location Information Service (LIS)
• Identify and populate user location in the client
•Affects routing of emergency calls
• Provides street address for E911
"Location Aware" Emergency Routing
• Emergency calls can be routed to specific PSTN gateways by Location Policy
• Location Policy can be assigned to network site
• Example: User roaming outside
North America
• User travelling in Ireland dials 112
(for emergency)
• Call is routed to a local gateway
Voice Routing
Announcement orCall Park Application
1. Vacant Number Range
2. Call Park Orbit Range
DialingBehaviors
Routing &Authorization
Normalization Rule
Normalization Rule
Normalization Rule
Dial Plan
PSTN Usage
PSTN Usage
PSTN Usage
3. Voice Policy Routes
Route
RouteRoute
Route
External Endpoint Receives Call UC Endpoint Receives Call
User Initiates Call
User=phone
Yes
Global?
No
SIP URI
Match
Reverse Number Lookup
No match
Mediation Server andTrunk Configuration
Gateway / IP-PBX / SIP Trunk Inbound Routing
404: No matching rule
403: No route found
Yes
EmergencyCall?
No
PSTN Usage
Location Policy
Call Park Orbit Range
E9-1-1 Lync Server 2013 Components
• Can be “location aware” or static assignment
• Defines emergency numbers
• Defines emergency call routing
• Defines IM notification destination
• Defines security desk phone number for conference
Location
Policies
• Takes BSSID, MAC, Subnet, Switch/Port and returns
validated location
• Validates addresses against the Master Street Address
Guide (MSAG)
• Validated LIS address returned is passed to
E911 provider via PIDF-LO (Presence Information Data
Format Location Object
Location
Information
Server (LIS)
Lesson 2: Overview of Setup and Call Flow
• E9-1-1 Configuration
• Location Discovery
• Placing an Emergency Call
E9-1-1 Configuration
•Q
Admin
Lync Server 2013 Infrastructure
LIS WSFE
E9-1-1 Service Provider
MSAG
SBC
PSTN
Internet
SIP
Trunk
2
3
4
Location Discovery
Caller
Lync Server 2013 Infrastructure
LIS WSFE
E9-1-1 Service Provider
MSAG
SBC
PSTN
Internet
SIP
Trunk
2
1
3
4
Placing an Emergency Call
• S
Caller
Security
PSAP
Lync Server 2013 Infrastructure
LIS WSFE
E9-1-1 Service Provider
MSAG
SBC
PSTN
Internet
SIP
Trunk
1
2
4a3
4b
5
3
Lesson 3: Designing Location Policies
• Location Policy Definition
• Location Policy Scope
• PSTN Usage Creation
• Voice Route Creation
• PIDF-LO Support on Trunk
Location Policy Definition
•Defines user experience, routing, dial string, and Security Desk
notification
Location Policy Scope
• If present, apply the policy
assigned to network siteNote: This is a “user” policy that you create
and assign to the network site
•Or, if present, apply the policy
assigned to user
•Or, consider the Topology Site
Policy, and then the Global
Location Policy
Global Policy
Topology Site Policy
User Policy
User Policy
Assigned to
user
Assigned to
network site
PSTN Usage Creation
• The Location Policy PSTN Usage selects a route for the emergency
call
• This may be the service provider’s SIP trunk (one usage for all
location policies) or it may be a local gateway (a unique usage for
each policy)
• The PSTN Usage is not added to existing Voice policies:– It is used for an emergency call if a user has a Location Policy applied
• You can create PSTN Usage in either Lync Server Control Panel or
Lync Server Management Shell
PS>Set-CsPstnUsage –Usage @{add="EmergencyCallsUsage"}
Voice Route Creation
• The Voice Route allows calls to the Emergency Number to go
through the PSTN Gateway that references the Emergency Service
Provider
Note: It does not differ from any other Voice Route
PS>New-CsVoiceRoute –Name "EmergencyCallsRoute" -NumberPattern
"^\+911$" –PstnUsage @{add="EmergencyCallsUsage"} –PstnGatewayList
@{add="e911gw.fabrikam.net"}
Identity : EmergencyCallsRoute
Priority : 3
Description :
NumberPattern : ^\+911$
PstnUsages : {EmergencyCallsUsage}
PstnGatewayList : {PstnGateway:e911gw.fabrikam.net}
Name : EmergencyCallsRoute
SuppressCallerId :
AlternateCallerId :
PIDF-LO Support on Trunk
• To send location information to
the E911 certified provider,
PIDFLO information must be
allowed to transit through the
Lync Trunk
• Ensure that
EnablePIDFLOSupport on the
Trunk is set to True
PS>Get-CsTrunkConfiguration
Service:PstnGateway:e911gw.fabrikam.net
Identity :
Service:PstnGateway:e911gw.fabrikam.net
OutboundTranslationRulesList : {}
SipResponseCodeTranslationRulesList : {}
Description :
ConcentratedTopology : True
EnableBypass : False
EnableMobileTrunkSupport : False
EnableReferSupport : True
EnableSessionTimer : False
EnableSignalBoost : False
MaxEarlyDialog : 20
RemovePlusFromUri : True
RTCPActiveCalls : True
RTCPCallsOnHold : True
SRTPMode : Required
EnablePIDFLOSupport : True
Set-CsTrunkConfiguration -Identity "Service:e911gw.fabrikam.net" -
EnablePIDFLOSupport $true
Lesson 4: Implementing LIS
• Location Information Server (1 of 2)
• Location Information Server (2 of 2)
• Configuring Location Information Server
• Location Information Server - Subnet
• Address Status
Location Information Server (1 of 2)
• Part of Lync Server 2013 web services components:– Load-balanced within a cluster for high availability
• Precedence of matching client location requests:– Basic service set identifier (BSSID) of Wi-Fi AP
– Switch/port from Link Layer Discovery Protocol Media Endpoint (LLDP-MED)
– Switch from LLDP-MED
– Subnet
• Media Access Control (MAC) match of switch/port– 3rd Party solution
Location Information Server (2 of 2)
• Microsoft Windows PowerShell and GUI-based administration
• Follows NENA “i2” reference architecture for address validation
• Follows Internet Engineering Task Force (IETF) Presence Information
Data Format Location Object (PIDF-LO) standards with extensions for
location format
• Other vendor/in-house LIS can be integrated:– Adhere to schema
Configuring Location Information Server
• Network identifiers are associated with street addresses:– BSSID
– Subnet
– Switch
– Switch/Port
• The size of this data set will correspond to how detailed the locations are and
whether wireless is within scope
• You can use Windows PowerShell scripts to import this data from .csv files
• Address management–related administrative tasks include:– Configuring the address validation service provider
– Uploading validation credentials
– Validating the addresses and error correction
Location Information Server - Subnet
• Configure the LIS subnet
Note: There is no subnet mask. The client uses its own IP/subnet mask to
determine its subnet, and then sends this in the Web Query to the LIS Web
Service
• Publish the LIS configuration
Set-CsLisSubnet -Subnet 172.16.20.0 -Description "Munchen" -
Location "Munchen"
-CompanyName "Fabrikam" -HouseNumber 2 -StreetName "Lindenstrasse"
-City "Munchen"
-Country DE
Publish-CsLisConfiguration
Address Status
• Every address added to the LIS database should be validated by a
Master Street Address Guide (MSAG)
•MSAG validation ensures that emergency calls can be correctly
routed
Lesson 5: Address Discovery
• Client Location Request
• Automatically Acquiring a Location
• Using a MAC Address to Find a Location
• E9-1-1 Support for Remote Users
Client Location Request
• Location Request includes the following information:– Link Layer Discovery Protocol (LLDP) from Layer 2 connection – switch and port IDs (if
available)
– Subnet
– WAP BSSID (if available)
– MAC address
• LLDP is not supported for Lync on Windows 7 and earlier:– This makes it difficult to get detailed locations for wired softphones
– You will need to use an SNMP application in order to do this
• LLDP is supported on Lync Phone Edition:– Switches may need upgrades to support LLDP
Automatically Acquiring a Location
• Location database is global – each LIS has all defined locations
• Client automatically initiates a “location request” to its LIS:– Includes its network connectivity data
• LIS location matches precedence:– Wi-Fi AP BSSID
– LLDP-MED Switch/Port
– LLDP-MED Switch
– Subnet
– MAC (If configured via Set-CsWebServiceConfiguration -MacResolverUrl) for third-party
• If a location is not found, the request can be sent to an external database
(Set-CsWebServiceConfiguration –SecondaryLocationSourceUrl)
Using a MAC Address to Find a Location
• Lync does not natively map MAC address to Location information
• LIS must resolve MAC address into Switch/Port for resolution:– Lync client sends MAC address, and then:
1) LIS queries external MAC Resolver via Web Services
2) MAC Resolver returns Switch/Port
3) LIS uses Switch/Port to return location information to client
• This raises a question: What is a MAC Resolver?
– It is an appliance provided by the Service Provider
– 911Enable MAC Resolver = Phone Discovery Manager (PDM such as 911
Enabling’s Soultion)
E9-1-1 Support for Remote Users
• LIS Web Service is not exposed to external users
• How it works:1) Users self-report their location
2) The call is automatically routed to the Emergency Call Response Center
(ECRC) with location data
3) The ECRC confirms the location with caller, and then transfers the call to the
correct PSAP
Manual Location Entry
• Location Policy field LocationRequired
impacts user experience:
• Location Required = No:
• User not prompted
• Location Required = Yes:
• UI highlights location with “X” and “!” for emphasis
• Can be dismissed without warning
• Location Required = Disclaimer:
• UI highlights location with “X” and “!” for emphasis
• Disclaimer shown when dismissed
• Only shows during sign in. No effect on call
Emergency Dialing
•User dials emergency number
•Call goes straight through to the correct PSAP:
• If the location has been validated
Security Desk Integration
• IM automatically established between
emergency caller and security desk:
• Location information is contained in the
conversation window
•An E.164 number can be bridged
onto emergency calls
• One-way / two-way
• Partner is responsible for initiating
conference – cannot be tested without a
partner solution in place
©2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, Office, Azure, System Center, Dynamics and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.