Transcript Module 10 - Microsoft Lync Server 2010 - Enhanced 9-1

Microsoft® Lync™ Server 2010
Enhanced 9-1-1 and Location Services
Module 10
Microsoft Corporation
Session Objectives and Takeaways
•
•
Session Objectives:
•
Describe the overall goals and processes of Enhanced 9-1-1 (E9-11) and Location Services in Lync Server 2010
•
Provide details about how to deploy and configure E9-1-1 and
Location Services with Lync Server 2010
Key Takeaways
•
Lync Server 2010 provides E9-1-1 and Location Services that meet
requirements in the U.S.
2
E9-1-1 and Location Goals
•
Base requirement - provide location with emergency calls (North
American E9-1-1)
•
•
•
The dispatchers must know the civic/street address of the caller
Locations may need to be to specific building, floor, wing, office, etc.
Base goal - support the roaming nature of Microsoft
Lync 2010 users
•
•
•
Inside the network (automatic or manual)
Outside the network (manual then automatic for frequent/recent locations)
Connecting to the appropriate authorities without having a Public Switched
Telephone Network (PSTN) gateway to each emergency network
3
E9-1-1 and Location Infrastructure
•
Added location enablement policies and objects to provide flexible
deployment
•
•
•
Network sites
Users
Added a Location Information Server role
•
•
•
Contains records of civic addresses associated with network identifiers
Renders locations to Unified Communications clients
Locations can be used independent of E9-1-1
4
Goals of E9-1-1 Design
•
Support roaming scenarios
•
•
•
•
Support soft-phone scenarios
•
•
Automatic location detection
On-premise – wired and
wireless
Off-premise tele-working
Fallback for manual location
entry
Integrated into
Lync Server 2010
•
•
•
•
Support flexible enablement
•
•
•
Specific sites – including users
roaming onto sites
Specific users
Support next generation
emergency services
architecture
•
Leverage standards where
possible
Minimize new server roles /
complexity
Is designed directly into
protocols, provisioning, routing,
and management components
Provide a database for
locations
5
E9-1-1 – Infrastructure Setup
E9-1-1 Service Provider
Lync Server 2010 Infrastructure
Mediation
Server
SIP
Trunk
2
Session Border
Controllers (SBC)
Call-Center
3
Lync Server 2010
LIS DB
1
Administrator
Enterprise User
Bob
172.24.33.132
Master Street Address
Guide (MSAG)
Validation database
1. Provisioning
a) Populate Local Install Source (LIS) with
network element and location records
b) Connect SIP trunk to service provider
c) Enable sites and users
2. Addresses are sent for validation
3. Report back valid/invalid addresses
6
E9-1-1 – Location Discovery
E9-1-1 Service Provider
Lync Server 2010 Infrastructure
Mediation
Server
SIP
Trunk
SBC
Call-Center
Lync Server 2010
LIS DB
MSAG Validation DB
3-4
1
1
Enterprise User
2
Bob
172.24.33.132
2
1. Client sends subnet information to registrar
2. Registrar returns LIS URI (and E9-1-1
Enablement data) during Registration; this is
because Subnet 172.24.33.132 is enabled for E91-1
3. Client sends subnet to LIS – locations by subnet
4. LIS does subnet/location match and returns the
location in PIDF-LO format
7
E9-1-1 – Placing a Call
E9-1-1 Service Provider
Lync Server 2010 Infrastructure
3
3
Lync Server 2010 2
Mediation
Server
SIP
Trunk
LIS DB
SBC
Call-Center
MSAG Validation DB
4
1
5
PSTN
Corporate Security Desk
1
Enterprise User
Bob
172.24.33.132
1. Client dials 911 – includes PIDF-LO in SIP
INVITE
2. IM notification of emergency call, party, and
location sent to security group (optional)
3. E9-1-1 call routed over SIP trunk
4. Routing Provider connects to appropriate
Public Safety Answering Point (PSAP)
5. Voice path connected to security group
(optional)
Redmond PSAP
Operator
8
911 Location Client Experience
Location available:
Location unavailable:
9
911 Call
Client
Experience
Location available:
Location unavailable:
10
Provisioning/Enabling E9-1-1
•
•
•
With the introduction of Location Policy, attributes allow
E9-1-1 to be uniquely configured
UC clients receive a location policy during registration
The location policy can be assigned in two ways:
1.
2.
Associate it with subnets – allows specific business locations
(campus, buildings, floors) to be enabled
Associate it with users – allows outside (home, hotel, coffee
shop) work spaces to be enabled
11
Making Emergency Calls That Include Location
A phone you can trust in emergencies
UX value propositions
•
Emergency responders need to know
your location
New features
•
Automatic location support
•
Custom location setting
12
E9-1-1 Enablement:
Location Required = “Disclaimer acceptable”
E9-1-1 enabled via (in order of precedence):
• IP Subnet policy:
All locations in Redmond, WA offices are enabled
•
User policy:
A subset of Redmond teleworkers are also enabled
13
Secondary Location Source (SLS)
•
•
Enterprises can point Lync Server 2010
to get employee’s work location from a
secondary location source such as an
HR database
Needs to conform to the same
schema/protocol as OCS LIS
14
E9-1-1 Partners
•
•
Lync Server 2010 E9-1-1 requires Service Providers for routing
emergency calls
Agreements with two partners for Lync Server 2010 release
•
•
•
•
•
•
•
Security desk conferencing a partner feature
U.S. coverage only (no Canada support yet)
LLDP-MED support for IP Phones
•
•
Connexon / 911Enable
Intrado
Others emerging
Long term goal is to embed in SIP trunk carrier networks
Not Lync 2010
Switch / port level granularity requires SNMP integration for
Lync 2010, or switches not supporting LLDP-MED
•
•
Web service API for custom integration
Connexon appliance
15
Location Information Server
•
Part of Lync Server 2010 web services components
•
•
Database of network elements / addresses
•
•
•
•
•
•
•
•
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
Microsoft Windows PowerShell® and GUI-based administration
Follows NENA “i2” reference architecture for address validation
•
•
Note: VPN subnets should not be included in the location database.
Precedence of matching client location requests:
•
•
Load balanced within a cluster for high availability
Only returns validated addresses to clients
Follow Internet Engineering Task Force (IETF) Presence Information Data Format
Location Object (PIDF-LO) standards with extensions for location format
Third party / in-house LIS could be integrated
•
Adhere to schema
16
PIDF-LO and FROM
•
•
•
Calls routed from the Mediation Server to the Emergency Services
Provider include a SIP INVITE
The SIP INVITE contains the PIDF-LO, originally provided to the client
by the Location Information Server, and a 10-digit callback number
stored in FROM
PIDF-LO
•
•
•
The Location Information Server uses the PIDF-LO format to store locations and
transmit the location to the client
The PIDF-LO location is included in the SIP INVITE as a means of conveying
location from the client to the Emergency Service Provider
FROM
•
•
FROM is included in a SIP INVITE and contains a 10-digit callback number that
the PSAP can use to contact the client initiating the emergency call
For the return call, the Mediation server needs to forward appropriate SIP
headers that instruct the client to ignore call handling such as call forwarding, and
team calling
17
E9-1-1 Routing
•
Requires SIP trunk connectivity to a service provider
•
•
•
E9-1-1 and 911 routing
•
•
•
•
•
Automated PSAP routing for validated addresses
Non-validated addresses are routed to service provider partner call center for validation of
user location
Do Not Disturb and Call Forward Rules turned off
•
•
E9-1-1 routes are part of location policy
Backup routes
Fallback to PSTN for wide area network (WAN) outages
PSAP routing
•
•
Generally centralized SIP trunks
Backup data centers
Enables callback
You absolutely need to test this when you configure it
•
•
You should validate all of this end-to-end
Use synthetic transactions that can be scripted or run from the System Center Operations
Manager (SCOM) environment
18
E9-1-1 and Branch Office Resiliency
•
•
•
For E9-1-1, it is important to maintain a consistent connection from
the client, through the Mediation server, to the Emergency Services
Provider
If a user places an emergency call and the client cannot connect to
the Emergency Services Provider or the Location Information Server
to obtain a location, the call may not be routed to the correct PSAP
Lync Server 2010 provides several strategies for handling Voice
resiliency in branch offices, including:
•
•
•
Having resilient data networks
Deploying a SIP trunk at each branch, or
Pushing calls out to the local gateway during outages
19
Call Admission Control and E9-1-1
•
•
•
Call Admission Control (CAC) can interfere with emergency calls
when enforced on the connection between a network site and
the site containing the SIP trunk for E9-1-1 calls
911 call is not any different to CAC than any other number
If bandwidth limits are exceeded on the connection:
•
•
•
Emergency calls routed through a local PSTN gateway will not
convey location information to the PSAP
•
•
Emergency calls will be blocked
Emergency calls will be routed from the local PSTN gateway
PSAP must use the location associated with the static phone line
Avoid having CAC block emergency calls by:
•
•
Not implementing CAC on links connecting the network site to
the SIP trunk used by E9-1-1
Deploying a separate SIP trunk from the network site to the
Emergency Services Provider
20
Lync Server 2010 Clients
•
•
•
•
Lync Server 2010 E9-1-1 service works with Lync 2010, Lync
2010 Attendant and Lync 2010 Phone Edition clients on
multiple IP phone models
If you are in a migration scenario with a mix of OCS 2007 R2
and Lync Server 2010 clients, the E9-1-1 solution will not
work with OCS 2007 R2 clients.
Private telephone lines are inbound only and cannot be used
to make outgoing calls.
Multiple Points of Presence (MPOP) is fully supported
21
Client Enablement
•
•
To enable automatic location acquisition, switches may have
to be upgraded to enable LLDP-MED, and a thorough port
inventory is needed within each building
Interop with existing PBXs
•
Solution is completely OCS-based
•
We can always do what we do now and dial 911 out, but we
won’t be integrated with Cisco’s E9-1-1 solution, either
•
We’re working on interfaces to RedSky and others to prevent
customers from having multiple databases during this transition
22
Configuring E9-1-1
– Enablement
Settings:
Enablement settings example:
• Location Policy(s)
• Emergency Services Enabled
• Location Required
• Use Location for E9-1-1 Only
• PSTN Usage
• Emergency Dial String
• Emergency Dial Mask
• Notification URI
• Conference URI
• Conference Mode
• Subnets and description
• User sites
• One or more subnets
• Location Policy
23
Configuring E9-1-1 –
Location Information Server
•
Network Identifiers
•
•
•
•
•
•
Network reference point and location
BSSID, Subnet, Switch, Switch/Port
Network Identifiers and Locations can be defined separately, but would
then need to associated with each other
The size of this data set will correspond to how granular the locations
are and whether wireless is in scope
Windows PowerShell™ scripts can be used to import this data from .csv
files
Address management-related administrative tasks include:
•
•
•
Configuring address validation service provider
Uploading validation credentials
Validation of the addresses / error correction
24
Locations Settings Example
•
•
•
Subnet 10.10.10.1 3910 163rd AVE NE Redmond WA 98052 US
Building 30 Microsoft
Switch Chassis ID 00:00:11:4C:22:B0:52 16011 NE 36th WAY
Redmond WA 98052 US Building 1 Microsoft
WAP 00:0B:86:E2:C1:05 3910 163rd AVE NE Redmond WA 98052
US Building 30/1389 Microsoft
25
PowerShell Example
•
•
•
•
•
Lync Server 2010 PowerShell admin model includes E9-1-1
enablement and location settings
new -ocsliswirelessaccesspoint -BSSID 00-18-41-98-00-12 description Redmond/B30 2nd Floor East -housenumber 3910 streetname 163rd -streetsuffix Ave -postdirectional NE -city
Redmond -stateprovince Washington - country US -postalcode
98052 -Location 30/3062 -Name Microsoft Corp
$waps = Import-Csv o:\B30APBSSID.csv
$waps | Set-OcsLisWirelessAccessPoint
new -usersite -usersiteid Advanta -name Redmond-Advanta locationpolicytag USE9-1-1
26
GUI- based Admin
Example: the Edit
Location Policy
Dialog Box
• For more information about the
CsLocationPolicy cmdlets, type
Get-Help cmdlet_name –Full |
more
at the Lync Server Management
Shell prompt
• For example:
Get-Help Set-CsLocationPolicy –
Full | more
27
UI-to-PowerShell Mapping
Example: The Edit Location Policy Dialog
•
•
•
Location policies are used with the E9-1-1 service, which enables those who answer 911 calls to
determine the caller’s geographic location
To access location policies in the Lync Server 2010 Control Panel, click the Network
Configuration tab and then click Location Policy
The Edit Location Policy dialog and the New Location Policy dialog correspond to the properties
and parameters of the following cmdlets:
•
Get-CsLocationPolicy, used to retrieve information about your location policies:
•
•
Grant-CsLocationPolicy, used to assign a per-user location policy:
•
•
New-CsLocationPolicy -Identity site:Redmond -UseLocationForE9-1-1Only $True
Remove-CsLocationPolicy, used to remove location policies configured at the site scope or
the per-user scope, or to reset the property values of the global policy:
•
•
Grant-CsLocationPolicy -Identity "Ken Myer" -PolicyName "RedmondLocationPolicy"
New-CsLocationPolicy, used to create a new location policy at the site scope or the peruser scope:
•
•
Get-CsLocationPolicy
Remove-CsLocationPolicy -Identity site:Redmond
Set-CsLocationPolicy, used to modify an existing location policy:
•
Set-CsLocationPolicy -Identity global -UseLocationForE9-1-1Only $True
28
Q&A
29
© 2011 Microsoft Corporation. All rights reserved.
Microsoft, Windows, 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. This document may contain information related to pre-release software, which may be substantially modified before
its first commercial release. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious,
and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should be inferred.
30