1. Microsoft ® Lync™ Server 2010 Enhanced 9-1-1 and Location Services Module 10 Microsoft Corporation

2. Session Objectives and Takeaways Session Objectives: Describe the overall goals and processes of Enhanced 9-1-1 (E9-1- 1) 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

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

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

5. Goals of E9-1-1 Design Support roaming scenarios Automatic location detection On-premise – wired and wireless Off-premise tele-working Support soft-phone scenarios Fallback for manual location entry Integrated into Lync Server 2010 Minimize new server roles / complexity Is designed directly into protocols, provisioning, routing, and management components Provide a database for locations 5 Support flexible enablement Specific sites – including users roaming onto sites Specific users Support next generation emergency services architecture Leverage standards where possible

6. E9-1-1 Service Provider Session Border Controllers (SBC) Call-Center Master Street Address Guide (MSAG) Validation database LIS DB 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 2 3 Lync Server 2010 Infrastructure Lync Server 2010 Bob 172.24.33.132 Enterprise User SIP Trunk Mediation Server E9-1-1 – Infrastructure Setup 6 Administrator 1

7. E9-1-1 Service Provider SBC Call-Center MSAG Validation DBLIS DB Lync Server 2010 Infrastructure Lync Server 2010 Bob 172.24.33.132 Enterprise User 1 2 12 3-4 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 E9- 1-1 3.Client sends subnet to LIS – locations by subnet 4.LIS does subnet/location match and returns the location in PIDF-LO format SIP Trunk Mediation Server E9-1-1 – Location Discovery 7

8. E9-1-1 Service Provider SBC Call-Center MSAG Validation DBLIS DB Lync Server 2010 Infrastructure Bob 172.24.33.132 Enterprise User SIP Trunk Mediation Server 1 1 3 2 Corporate Security Desk 3 PSTN 5 Redmond PSAP 4 Operator 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) E9-1-1 – Placing a Call 8 Lync Server 2010

9. 911 Location Client Experience 9 Location available: Location unavailable:

10. 911 Call Client Experience 10 Location available: Location unavailable:

11. 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. Associate it with subnets – allows specific business locations (campus, buildings, floors) to be enabled 2. Associate it with users – allows outside (home, hotel, coffee shop) work spaces to be enabled 11

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

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

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

15. 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 Connexon / 911Enable Intrado Others emerging Long term goal is to embed in SIP trunk carrier networks Security desk conferencing a partner feature U.S. coverage only (no Canada support yet) LLDP-MED support for IP Phones 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

16. Location Information Server Part of Lync Server 2010 web services components Load balanced within a cluster for high availability Database of network elements / addresses Note: VPN subnets should not be included in the location database. Precedence of matching client location requests: 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 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

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

18. E9-1-1 Routing Requires SIP trunk connectivity to a service provider Generally centralized SIP trunks Backup data centers E9-1-1 and 911 routing E9-1-1 routes are part of location policy Backup routes Fallback to PSTN for wide area network (WAN) outages PSAP 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 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

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

20. 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 will be blocked Emergency calls will be routed from the local PSTN gateway Emergency calls routed through a local PSTN gateway will not convey location information to the PSAP 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

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

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

23. 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 Configuring E9-1-1 – Enablement Settings: 23 Enablement settings example:

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

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

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

27. 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 GUI- based Admin Example: the Edit Location Policy Dialog Box 27

28. 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: Get-CsLocationPolicy Grant-CsLocationPolicy, used to assign a per-user location policy: Grant-CsLocationPolicy -Identity "Ken Myer" -PolicyName "RedmondLocationPolicy" New-CsLocationPolicy, used to create a new location policy at the site scope or the per- user scope: 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: Remove-CsLocationPolicy -Identity site:Redmond Set-CsLocationPolicy, used to modify an existing location policy: Set-CsLocationPolicy -Identity global -UseLocationForE9-1-1Only $True 28

29. Q&A 29

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