Presentation is loading. Please wait.

Presentation is loading. Please wait.

State Legislation 18 States currently have statutes regulating Multi-Line Telephone Systems (PBXs) and E911 Rules generally require unique.

Similar presentations


Presentation on theme: "State Legislation 18 States currently have statutes regulating Multi-Line Telephone Systems (PBXs) and E911 Rules generally require unique."— Presentation transcript:

1

2

3

4

5

6

7

8 State Legislation 18 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 requirements Think Life Safety and Lawsuits! Lync supports E911 via SIP trunks and ELIN gateways You must select an E911 service provider certified by Microsoft through the Open Interoperability Program (OIP)

9

10

11

12

13

14

15 A 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

16 A 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

17

18

19

20

21

22 1. Engage with E9-1-1 Service Provider 2. Configure Lync: a. Populate LIS with network elements and associated addresses b. Configure policies, routes, and users 3. Test addresses for validity 4. Correct invalid addresses, repeat validation 2 3 4

23 1. Client sends subnet information to Registrar 2. Registrar returns LIS URI (and location policy) during in-band provisioning; this is because Subnet is enabled for E Client sends subnet to LIS – locations by subnet 4. LIS does subnet/location match and returns the location in PIDF-LO format

24 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 trunk 4. 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) a 4b 5 3

25

26

27

28

29

30 Response valid true

31

32

33 dbo.XdsPublishItems Called by dbo.XdsQueryItems Writes XML document to dbo.item table in XDS database urn:xds:Microsoft.Rtc.Management.Settings.LocationInformation.2008:LocationInformationSettings.Host.Global

34 Debug-CsLisConfiguration Deug-CsLisConfiguration | Format-Table -Wrap

35 Message-Body: true user-tagid disclaimer Emergency ;

36 This 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

37 TL_INFO(TF_COMPONENT) [6]6AC8.79E0::02/08/ :34: b03 (LocationInformationService,LIService.BeginGetLocations:liservice.svc.cs(48))[ ] GetLocationsRequest:[ a6-5b ] Snooper Trace

38 200 US WA Redmond Microsoft Way 1 Redmond Microsoft Corporation ]

39 TL_INFO(TF_COMPONENT) [10]6AC8.623C::02/08/ :34: bdf (LocationInformationService,LIService.EndGetLocations:liservice.svc.cs(61))[ ] GetLocationsResponse:[ 404 false Manual ] Snooper Trace

40 INVITE SIP/2.0 Via: SIP/2.0/TLS :52018 Max-Forwards: 70 From: ;tag=956402dbe2;epid= b2 To: Call-ID: ba89067f2bee4491beba238dcbc21173 CSeq: 1 INVITE Contact: ms-subnet: geolocation ms-endpoint-location-data: NetworkScope;ms-media-location-type=Intranet P-Preferred-Identity:, =_NextPart_000_00E8_01CF28B4.6ABBA360 Content-Type: application/pidf+xml Content-Transfer-Encoding: 7bit Content-ID: Content-Disposition: render; handling=optional

41 US WA Redmond Microsoft Way 1 Redmond Microsoft Corporation 98052

42

43 Location Search Order Lync Location Information Server MacResolver Secondary Location Source URL Snooper Trace TL_INFO(TF_COMPONENT) [20]6AC8.79E0::02/08/ :34: b29 (LocationInformationService,LocationInformationWrapper.AsyncFindLocationsViaSLS:liservice.svc.cs(598))[ ] Calling GetLocations on Web Service at: SecondaryLocationSourceUrl:[https://lyegw103p01.microsoft.com/LIService/1/index.php]

44

45

46

47 (It fails to register the new scenario unless restarted)

48

49

50

51

52

53

54

55

56

57

58

59


Download ppt "State Legislation 18 States currently have statutes regulating Multi-Line Telephone Systems (PBXs) and E911 Rules generally require unique."

Similar presentations


Ads by Google