Jason Collier/Alan MaddisonPremier Field Engineer/Senior ConsultantMicrosoft Corporation

Deploying Location Services and Enhanced 911 with Lync Server 2013

VOICE402

Jason CollierLync Premier Field EngineerNorth America Technology Lead for LyncBased in Seattle, WA

IP Contributor for the followingLync Roll Out and Adoption Success KitLync Server 2013 Workload PosterLync Server 2013 Networking Guide: Network Panning, Monitoring and Troubleshooting with Microsoft Lync Server

Masters Trainer and Author of the following classesLync Server 2013 Advanced Core workshopWorkshop - Lync Server 2013: Administration workshopWorkshop - Lync Server 2013: Advanced Core workshopWorkshop - Exchange 2013 Unified Messaging workshopWorkshop - Lync Online: Administration and Configuration workshop

Alan MaddisonSenior Consultant, Microsoft Consulting ServicesMale Model based in Milan (Part-Time)Based in Tampa, Florida

Microsoft Certified Master Lync Server 2010

Published AuthorTechNet MagazineMicrosoft Architecture JournalRedmond Magazine

911Background

Background911 is the official national emergency number in North America

Final destination of a 911 call is to a Public Safety Answering Point (PSAP) that dispatches first responders

PSAP jurisdictions generally follow local government (city/county) boundaries

Enhanced 911 determines location information automatically and routes to correct PSAP

Enterprises face a number of challengesHundreds or thousands of phonesMulti-floor, multi-building and even multi-city environmentVOIP provides highly mobile work environmentManagement and deployment considerations

PBX SolutionsTDM PBXUpload a location record to the Private Switch Automatic Location Identification ALI (PS-ALI) database for each phone number on the PBX

Ensure all phones have direct inward dial numbers in order to allow call back

PSAP receives the Automatic Number Identification (ANI) with the call and queries the PS-ALI for the associated location

VoIP PBXIntroduced this concept called “pseudo ANI” where locations are assigned unused phone numbers; these numbers are associated with an Emergency Response Location (ERL) and uploaded to PS-ALI

IP phones are correlated to a location – at the time of the emergency call the “pseudo ANI” is sent instead of the caller’s ANI

PSAP receives the P-ANI with the call and queries the PS-ALI for the associated location

E911 – Planning ConsiderationsState Legislation18 States currently have statutes regulating Multi-Line Telephone Systems (PBXs) and E911

Rules generally require unique location for different buildings (campus), floors (multi-floor building), zones on a floor (sq footage)

Your are obligated to understand any requirements that State and Federal Law impose

In the absence of regulatory requirementsThink Life Safety and Lawsuits!

Lync supports E911 via SIP trunks and ELIN gatewaysYou must select an E911 service provider certified by Microsoft through the Open Interoperability Program (OIP)

Lync and E911

Location Information ServerNational Emergency Number Association (NENA) “i2” Reference Architecture for Address Validationi2 is the recommended standard for the interconnection of VoIP systems with the existing Emergency Services Network infrastructure Represents an interim step in the migration towards end to end IP networks

Standards based approachPresence Information Data Format (PIDF - RFC 3863)A Presence-based GEOPRIV Location Object Format (Extensions to PIDF for Location - RFC 4119)Presence Information Data Format Location Object (PIDF-LO) standards with extensions for Location Format (RFC 5139)

Location Information ServerWeb Services implementation for location servicesIdentify and populate user location in the clientMaps network identifiers to civic addressIf a location is not found the request can be sent to an external LISClients have no specific knowledge of which source supplies the locationThe LIS will return addresses that are both validated and not validatedProvides for manual input of location if client is remote

Precedence of Matching Client Location RequestsBasic Service Set Identifier (BSSID) of Wi-Fi Access Point (AP)Switch/port from Link Layer Discovery Protocol Media Endpoint (LLDP-MED)Switch from LLDP-MEDSubnetMedia Access Control (MAC) match of switch/port

Location Information ServerMapping MAC address to locationLync doesn’t natively map MAC address to location

Phone Discovery Manager (PDM)SNMP scan against the access switches

Read the forwarding MAC tables (using RFC standard MIBs or switch vendor proprietary MIBs) Store all discovered MAC address and the port/switch found. Location is managed in the LIS database (set-CsLisSwitch or set-CsLisPort) The Chassis ID used will be the IP address of the switch

When a client signs in, the FE server sends a MACResolver Request which consists of the MAC address of the client (sent via the HELD location request from the client)

The PDM takes the MAC address and looks in the database to find where it was discoveredThe PDM responds with the Switch IP and port the MAC was discovered onThe FE looks in the LIS to find the match and sends back the location to the client

Emergency call and voice routing

E-911 - ServicesOpen Interoperability Programhttp://technet.microsoft.com/en-us/lync/fp179863

E-911 Service Providers911 Enable – Emergency Routing ServiceIntrado – V9-1-1 for EnterpriseLevel 3 – Level 3 SIP Trunking for Lync

E-911 ELIN Gateways911 Enable – Emergency GatewayAudiocodes – Mediant Gateway & SBA Version 6.4Sonus – SBC 1000 & SBC 2000

Emergency call routing – SIP trunkA SIP INVITE that contains the location, the caller's callback number, and the (optional) Notification URL and conference callback number is routed to Lync Server.

Lync Server matches the emergency number and routes the call via a Mediation Server to the E911 service provider

The E911 service provider routes the emergency call to the correct PSAP assuming a validated Emergency Response Location (ERL). If the location has not been validated, for example the user manually entered a location, the Emergency Call Response Center (ECRC) first verbally verifies the accuracy of the location with the caller before routing the emergency call to the Public Safety Answering Point (PSAP)

If you configured the location policy for notifications, one or more of your organization’s security officers are sent a special Lync emergency notification instant message. If you configured the location policy for conferencing and it is supported by the E911 service provider, an internal Security Desk is conferenced into the call with either one-way audio or two-way audio

If the call is broken prematurely, the PSAP uses the callback number to contact the caller directly

Emergency call routing – ELIN gatewayA SIP INVITE that contains the location, the caller's callback number, and the (optional) Notification URL and conference callback number is routed to Lync Server

Lync Server matches the emergency number and routes the call via a Mediation Server to ELIN gateway

The ELIN gateway routes the call over an ISDN or Centralized Automatic Message Accounting (CAMA) trunk to the telecom provider

The telecom providers identifies the call as an emergency call and routes it to a 911 selective router. The E911 router looks up the caller's number in the ALI database and sends the call to the most appropriate PSAP based on the location information

If you configured the location policy for conferencing and it is supported by the telecom provider an internal Security Desk is conferenced into the call with either one-way or two-way audio

If the call is broken prematurely, the PSAP uses the ELIN to contact the caller directly. The ELIN gateway swaps the ELIN for the caller's DID

Location aware emergency routingEmergency calls can be routed to specific PSTN gateways by Location PolicyRequires network sites and subnets defined in Lync

Network Configuration is common for Location Policies, Call Admission Control and Media Bypass

Use Lync Server network configuration to apply Tagged Location Policies based on network sites

If not configured or if no subnet match, Global or (Topology) Site Policy (if defined) applies

Location aware emergency routingExampleNetwork subnets in Sao Paulo configured to map to network site Sao Paulo

Sao Paulo Location Policy is associated with Sao Paulo Network Site

If Alan and Matt visit Sao Paulo

Alan and Matt get Sao Paulo Location Policy applied

Alan dials an emergency call

Call is routed out local Sao Paulo gateway associated with emergency calls

Branch OfficesConsider impact of WAN Failure E911 routes generally centralizedClients will potentially lose E911 capabilities if WAN failure occurs

CAC can impact emergency callsIf available bandwidth for audio is insufficient calls will failDesign CAC to ensure that emergency calls are not impacted

Dedicated Mediation pool for E911 callsAllows for dedicated site and inter-site policies to change restrictionsDO NOT overlook the fact that these strategies do not address the underlying bandwidth constraints

Strategies to mitigate impactConsider routing all Emergency calls to local gateway

Ensure backup route to E911 call center via local gatewayManipulate outbound calling number to ensure it matches PS-ALI data at Telco and pass call directly to PSTN

User experienceLocation RequiredLocation Required = No:

User not prompted Location Required = Yes:

UI highlights location with “X” and “!” for emphasisCan be dismissed without warning

Location Required = Disclaimer:UI highlights location with “X” and “!” for emphasisDisclaimer shown when dismissed

Only shows during sign in. No effect on call.

E911 in a nutshell

Configuring E911 and LIS

1. Engage with E9-1-1 Service Provider2. Configure Lync:

a. Populate LIS with network elements and associated addresses

b. Configure policies, routes, and users3. Test addresses for validity4. Correct invalid addresses, repeat

validation

Admin

Lync Server 2013 Infrastructure

LIS WSFE

E9-1-1 Service Provider

MSAG

SBC

PSTN

Internet

SIPTrunk

2

34

Location Discovery

1. Client sends subnet information to Registrar2. Registrar returns LIS URI (and location

policy) during in-band provisioning; this is because Subnet 172.24.33.0 is enabled for E911

3. Client sends subnet to LIS – locations by subnet

4. LIS does subnet/location match and returns the location in PIDF-LO format

Caller

Lync Server 2013 Infrastructure

LIS WSFE

E9-1-1 Service Provider

MSAG

SBC

PSTN

Internet

SIPTrunk

21

34

Placing an Emergency Call

Caller

Security

PSAP

Lync Server 2013 Infrastructure

LIS WSFE

E9-1-1 Service Provider

MSAG

SBC

PSTN

Internet

SIPTrunk

1. Client dials 911 – includes PIDF-LO in SIP INVITE

2. IM notification of emergency call. Party and location sent to Security Desk (optional)

3. E911 call routed over SIP trunk4. Routing Provider connects to appropriate

PSAP. Automatic, if possible (4a). Via call center agent, if address cannot be validated (4b).

5. Voice path connected to Security Desk (optional)

1 2

34a 4b

5

3

How does all this work?

LIS Database

LIS Databasedbo.LisSetSubnetLocationStored procedure executed on Central Management Store SQL ServerCalled after running Set-CsLisSetSubnet

exec LisSetSubnetLocation @_Subnet=N'10.2.135.0',@_Description=N'',@_LOC=N'Datacenter',@_NAM=N‘Microsoft',@_HNO=N'5000',@_HNS=N'',@_PRD=N'',@_RD=N‘Redmond',@_STS=N'Dr',@_POD=N'',@_A3=N‘Redmond',@_A1=N‘WA',@_PC=N‘98104',@_Country=N'US'

Address ValidationCivic addresses in LIS must be verifiedPOST https://www.911enable.com/ocsvalidation/ HTTP/1.1User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client Protocol 4.0.30319.18444)Content-Type: text/xml; charset=utf-8

SOAPAction: "VDBAddressValidate/ValidateAddress"

Host: www.911enable.comContent-Length: 641Expect: 100-continueConnection: Keep-Alive

Address ValidationHTTPS POST using SOAP<?xml version="1.0" encoding="utf-8"?><soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

<soap:Body><ValidateAddressIn xmlns="urn:nena:xml:ns:es:v7"><MessageID>0</MessageID><StreetAddress><HouseNum>5000</HouseNum><HouseNumSuffix /><PrefixDirectional /><StreetName>Development</StreetName><StreetSuffix>Dr</StreetSuffix><PostDirectional /><MSAGCommunity>Durham</MSAGCommunity><StateProvince>NC</StateProvince><PostalCode>27709</PostalCode><Country>US</Country></StreetAddress></ValidateAddressIn></soap:Body></soap:Envelope>

Address ValidationResponse<?xml version="1.0" encoding="UTF-8"?>-<SOAP-ENV:Envelope xmlns:ns1="urn:nena:xml:ns:es:v7" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">-<SOAP-ENV:Body>-

<ns1:ValidateAddressOut><ns1:MessageID>0</ns1:MessageID><ns1:ReturnCode>200</ns1:ReturnCode><ns1:Valid>valid</ns1:Valid><ns1:E911Coverage>true</ns1:E911Coverage>

</ns1:ValidateAddressOut></SOAP-ENV:Body></SOAP-ENV:Envelope>

Address Validationdbo.LisSetCivicAddressValidity Stored procedure executed on Central Management Store SQL ServerCalled after running Test-CsLisCivicAddress -UpdateValidationStatus

exec LisSetCivicAddressValidity @_HNO=N'5000',@_HNS=N'',@_PRD=N'',@_RD=N‘Redmond',@_STS=N'Dr',@_POD=N'',@_A3=N'Redmond',@_A1=N'MA',@_PC=N‘98104',@_Country=N'US',@_MSAGValid=0

Publish LIS Configurationdbo.LisExportLocationInformationSettingsXmlStored procedure executed on Central Management Store SQL ServerCalled after running Publish-CsLisConfigurationCreates in memory data setCalls dbo.XdsQueryItems in database XDS

dbo.XdsQueryItemsexec XdsQueryItems @_Query=N'<DocItemKeySet xmlns="urn:schema:Microsoft.Rtc.Management.Xds.AppLayer.2008"> <DocItemKey Name="urn:xds:Microsoft.Rtc.Management.Settings.LocationInformation.2008:LocationInformationSettings.Host.Global" ItemId="00000000-0000-0000-0000-000000000000" /></DocItemKeySet>

Publish LIS Configurationdbo.XdsPublishItemsCalled by dbo.XdsQueryItemsWrites XML document to dbo.item table in XDS database

urn:xds:Microsoft.Rtc.Management.Settings.LocationInformation.2008:LocationInformationSettings.Host.Global

<AnchoredXml xmlns="urn:schema:Microsoft.Rtc.Management.ScopeFramework.2008" SchemaWriteVersion="1"> <Key ScopeClass="Global"> <SchemaId Namespace="urn:schema:Microsoft.Rtc.Management.Settings.LocationInformation.2008" ElementName="LocationInformationSettings" /> <AuthorityId Class="Host" InstanceId="00000000-0000-0000-0000-000000000000" /> </Key> <Dictionary Count="1"> <Item> <Key /> <Value Signature="ca777153-c617-4c6e-931b-928f4dacdd3f"> <LocationInformationSettings xmlns="urn:schema:Microsoft.Rtc.Management.Settings.LocationInformation.2008" Data="MAQAAB+LCAAAAAAABAC1lNlugzAQRX/F8gcYg6FZFCJRaJWoZFHo8uyCk1gldmW7VT+/ZsvSJFVf+oIHzZ17xmPwKJU5NVyKqVhLtavDjBnDxUaDr10pdAg/lBjqfMt2dDjjuZJarg1amRylXKNOjC4YIQ/jPgTjUcw/eR4VhWJaM23fwbQIoQvBZL4IYYAxrsIshBAsV0m1VM+EfnINQfZoE4myqUWdikgIV0wzqvIteFScik3JwJKqN5tzQziPrTQOodfr4QEEcVwVPYcQQ6cjk5bsEnIJfCu1kQIs7dLiV8UJ/oVVggY3ixoc9vwBaXBPWQ10D0D/f7Z6nX202aBle+QyO5bvTGzphonLDUx4WTIli6vI5OGAdH4edfdZVGF36unCVgVmC+5LKRW4o9Wc59HMTp5L24fVsdx6t/KnaNq6p93p1Q6eKP7iQM4d/NYhoYbmTBimrlb759VBWz2ZpuAPDsGxg3M0j+zjVTBjgzloQrtbbP8Z1L9B7sCzlGYAzg+F6yOXBAi3AnIm8E7y/lneryj9vSCoG9t34/xyJYy/AQxVVtAwBAAA" /> </Value> </Item> </Dictionary></AnchoredXml>

Publish LIS ConfigurationDebug-CsLisConfigurationDeug-CsLisConfiguration | Format-Table -Wrap

<LocationInformationSettings xmlns="urn:schema:Microsoft.Rtc.Lis.Settings.LocationInformation.2008"><CivicAddresses><CId="1" HNO="5000" HNS="" Prd="" St="Davis" STS="Dr" POD=""A3="Redmond" A1="WA" PC="27709" CC="" V="0"/><C Id="3"HNO="133" HNS="" Prd="" St="40th" STS="St" POD="" A3="Issaquah" A1="WA"PC="02493" CC="US" V="1"/><C Id="4" HNO="5000" HNS="" Prd="" St="Davis"STS="Dr" POD="" A3="Redmond" A1="WA" PC="02493" CC="US"V="0"/><C Id="5" HNO="2300" HNS="" Prd="" St="Copenhagen" STS="Dr" POD=""A3="Hillerod" A1="WA" PC="02493" CC="DK" V="0"/></CivicAddresses><Locations><LId="1" LOC="5th Floor East" NAM=“Microsoft" CId="1" UAI="0"/><L Id="3"LOC="2nd Floor East" NAM=“Microsoft" CId="3" UAI="0"/><L Id="4"LOC="Datacenter" NAM=“Microsoft" CId="4" UAI="0"/><L Id="5" LOC="HILDatacenter" NAM=“Microsoft" CId="5" UAI="0"/></Locations><Subnets><NSubnet="10.20.86.192" LId="1"/><N Subnet="10.14.135.0" LId="3"/><NSubnet="10.2.135.0" LId="4"/><N Subnet="10.40.208.0"LId="5"/></Subnets></LocationInformationSettings>

In-Band ProvisioningMessage-Body: - <provisionGroupList xmlns="http://schemas.microsoft.com/2006/09/sip/provisiongrouplist-notification"> <provisionGroup name="publicProviders"> + <provisionGroup name="userSetting"> + <provisionGroup name="ServerConfiguration"> - <provisionGroup name="locationPolicy"> - <propertyEntryList> <property name="EnhancedEmergencyServicesEnabled">true</property> <property name="LocationPolicyTagID">user-tagid</property> <property name="LocationRequired">disclaimer</property> <property name="PstnUsage">Emergency</property> <property name="EmergencyDialString">911</property> <property name="EmergencyDialMask">911;9911</property> <property name="LocationRefreshInterval">4</property>..

SIP 200 OK

Web Service for E911 Support ProtocolThis protocol is defined as a web service

Specifies the structure of the schema used to construct the body in the request and response messages. This protocol uses SOAP and Web Services Description Language to describe the structure of the message body.

Used to retrieve the locations based on network identifiers

Specifies a request that contains the network identifiers for which locations need to be retrieved

The response contains the response status and, if the request is processed successfully, the locations that are most appropriate for the network identifiers specified

Must connect via SSL and client authentication is NTLM or Kerberos

http://msdn.microsoft.com/en-us/library/ff595797(office.12).aspx

Location Request

TL_INFO(TF_COMPONENT) [6]6AC8.79E0::02/08/2014-16:34:23.705.00004b03 (LocationInformationService,LIService.BeginGetLocations:liservice.svc.cs(48))[329805919]

GetLocationsRequest:[<?xml version="1.0" encoding="utf-16"?>

<GetLocationsRequest xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">

<Entity>sip:alan.maddison@microsoft.com</Entity> <RSSI>0</RSSI>

<MAC>00-50-56-a6-5b-26</MAC> <SubnetID>10.2.135.0</SubnetID> <IP>10.2.135.20</IP>

</GetLocationsRequest>]

Snooper Trace

Location Response<GetLocationsResponse xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">  <ReturnCode>200</ReturnCode>  <presenceList>    <presence entity="sip:alan.maddison@microsoft.com xmlns="urn:ietf:params:xml:ns:pidf">      <tuple id="_LIS:0">        <status>          <geopriv xmlns="urn:ietf:params:xml:ns:pidf:geopriv10">            <location-info>              <civicAddress xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">                <country>US</country>                <A1>WA</A1>                <A3>Redmond</A3>                <PRD />                <RD>Microsoft Way</RD>                <STS />                <POD />                <HNO>1</HNO>                <HNS />                <LOC>Redmond</LOC>                <NAM>Microsoft Corporation</NAM>                <PC>98052</PC>              </civicAddress>           .           .</GetLocationsResponse>]

Location not foundTL_INFO(TF_COMPONENT) [10]6AC8.623C::02/08/2014-16:34:24.548.00004bdf (LocationInformationService,LIService.EndGetLocations:liservice.svc.cs(61))[329805919]

GetLocationsResponse:[<?xml version="1.0" encoding="utf-16"?><GetLocationsResponse xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ReturnCode>404</ReturnCode> <presenceList> <presence entity="sip:voip_911_user1@contoscovdomain.com" xmlns="urn:ietf:params:xml:ns:pidf"> <tuple id="_LIS:0"> <status> <geopriv xmlns="urn:ietf:params:xml:ns:pidf:geopriv10"> <location-info /> <usage-rules> <retransmission-allowed xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:basicPolicy">false</retransmission-allowed> </usage-rules> <method>Manual</method> </geopriv> </status> </tuple> </presence> </presenceList></GetLocationsResponse>]

Snooper Trace

Caller SIPINVITE sip:+911@microsoft.com;user=phone SIP/2.0Via: SIP/2.0/TLS 10.14.245.196:52018Max-Forwards: 70From: <sip:alan.maddison@microsoft.com>;tag=956402dbe2;epid=65373670b2To: <sip:+911@microsoft.com;user=phone>Call-ID: ba89067f2bee4491beba238dcbc21173CSeq: 1 INVITEContact: <sip:alan.maddison@microsoft.com;opaque=user:epid:F7I53NTBkVu_v6AhlQFUAwAA;gruu>ms-subnet: 10.14.244.0geolocation <cid:sip:alan.maddison@microsoft.com>;inserted-by="sip:alan.maddison@microsoft.com"ms-endpoint-location-data: NetworkScope;ms-media-location-type=IntranetP-Preferred-Identity: <sip:alan.maddison@microsoft.com>, <tel:+18134645273>

------=_NextPart_000_00E8_01CF28B4.6ABBA360Content-Type: application/pidf+xmlContent-Transfer-Encoding: 7bitContent-ID: <alan.maddison@microsoft.com>Content-Disposition: render; handling=optional

Caller SIP<?xml version="1.0" encoding="utf-8"?><presence entity="sip:alan.maddison@microsoft.com xmlns="urn:ietf:params:xml:ns:pidf">  <tuple id="_LIS:0">     <status>        <geopriv xmlns="urn:ietf:params:xml:ns:pidf:geopriv10">            <location-info>              <civicAddress xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">                <country>US</country>                <A1>WA</A1>                <A3>Redmond</A3>                <PRD />                <RD>Microsoft Way</RD>                <STS />                <POD />                <HNO>1</HNO>                <HNS />                <LOC>Redmond</LOC>                <NAM>Microsoft Corporation</NAM>                <PC>98052</PC>              </civicAddress> </location-info>

Secondary Location SourcesMACResolverSNMP scans of network to discover the ports and switches to which Lync clients connectLIS can query the MACResolver to obtain the Lync client’s switch and switch port

Set-CsWebServiceConfiguration –SecondaryLocationSourceUrlSwitch must support Bridge MIB (RFC 1493)911 Enable Phone Discovery Manager (PDM)

Secondary Location Source URLProvides for 3rd party location servicesProvides for same type of location identification as Lync LIS

Set-CsWebServiceConfiguration -MACResolverUrlAn example is the 911 Enable Emergency Gateway

Secondary Location SourcesLocation Search Order

Lync Location Information ServerMacResolverSecondary Location Source URL

Snooper TraceTL_INFO(TF_COMPONENT) [20]6AC8.79E0::02/08/2014-16:34:23.708.00004b29 (LocationInformationService,LocationInformationWrapper.AsyncFindLocationsViaSLS:liservice.svc.cs(598))[329805919]

Calling GetLocations on Web Service at: SecondaryLocationSourceUrl:[https://lyegw103p01.microsoft.com/LIService/1/index.php]

Troubleshooting

TroubleshootingLocation Information Services data is imported into LIS DatabaseThe data is only imported hereSize 20pt for the subtopics

Main topic 2: size 40ptSize 20pt for the subtopicsSize 20pt for the subtopics

Main topic 3: size 40ptSize 20pt for the subtopicsSize 20pt for the subtopics

Lync Server Management ShellTest-CsLisConfigurationTest-CsLisConfiguration -TargetFqdn atl-cs-001.litwareinc.com -Subnet 192.168.0.0

Test-CsLisConfiguration -TargetFqdn atl-cs-001.litwareinc.com -Subnet 192.168.0.0 -UserSipAddress sip:kmyer@litwareinc.com

Lync Server 2013 – Centralized Logging No Out-of-the-Box ScenarioLet’s create our own!!Remember only two Scenarios can run at one time

$LisProvider = New-CsClsProvider -Name "LocationInformationService" -Type "WPP" -Level "Verbose" -Flags "All"New-CsClsScenario -Identity "global/LIS" -Provider $LisProvider Restart Lync Management Shell

Start-CsClsLogging -Scenario "LIS" -Pools pool.domain.com (Pools parameter is optional)Sync-CsClsLoggingStop-CsClsLogging -Scenario "LIS" -Pools pool.domain.com (Pools parameter is optional)Search-csclslogging -outputfilepath c:\lis.log (add any parameters to filter the data or just filter in snooper)

(It fails to register the new scenario unless restarted)

Lync Server - OcsLoggerLocationInformationServicesClient requestClient responseLIS Source

SipStackIn-band provisioningSignalingMedia

User Experience

User Experience

User Experience

Microsoft PavilionDemos, Speakers, Demos, Lync Room System, Experts, Demos, a Bar....and more Demos

ATTENDEE PARTY Wednesday, February 19th

6:30pm-9:30pmHakkasan, MGM Grand

Brought to you by

When it comes to Vegas nightclubs, it doesn’t get any hotter than Hakkasan. And when it comes to opportunities to connect and reasons to party, no one does it better than Lync Conference! Our attendee party has a full lineup: an open bar, awesome food, and one of the best DJs that Vegas has to offer. Don’t miss out on the fun—stop by at 6:30pm and kick off and evening to remember. Come together.

HANDS-ON LABS

You can also access labs on MyLync!

3:00pm – 9:00pm10:30am – 9:00pm7:30am – 9:00pm8:00am –1:30pm

LOCATIONPinyon 3

Monday, February 17Tuesday, February 18Wednesday, February 19 Thursday, February 20

LRS

LOCATIONCopperleaf 12

Wednesday, February 198:30am – 9:45am10:15am – 11:30am1:00pm – 2:15pm2:45pm – 4:00pm4:30pm – 5:45pm

Thursday, February 209:00am – 10:15am10:45am – 12:15pm12:45pm – 2:00pm

MyLync allows you to create a custom experience and network with the Lync Community both online and in person.With MyLync, you can:• Build your own personalized calendar while browsing all available sessions• View breakout session material including PPTs and Videos within

48 hours of each session• Participate in the Community and find people in your social networks

who are attending and interact with speakers• Arrange meetings or social activities• Navigate the Exhibit Hall floor plan and learn more about our Sponsors• Fill out evaluations to win prizes

Log into MyLync at http://mylync.lyncconf.comFor MyLync support, please visit the Registration Desk.*

* Please note that adding a session to your calendar does not reserve a seat. Seating is on a first-come, first-served basis.

Birds of a FeatherBirds of a Feather flock together! Join daily breakfast discussions of relevant topics by sitting in the separately designated areas of the Meal Hall. Seating will be sorted in a different way for each Birds of a Feather breakfast:Wednesday, February 19:Where are you from? Asia/Pacific, Eastern & Central Europe, Latin America, Middle East & Africa, US (West, Central & East) and Canada, Western Europe

Thursday, February 20:What is your interest?Best Practices, Business Value, Clients & Mobility, Lync Meetings and Video, Lync Online, Networking, Platform, Server & Manageability, Voice

Fill out evaluations to win prizesFill out evaluations on MyLync or MyLync Mobile.Prizes awarded daily.

© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista 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.