enterprise 112 services in the eu
Post on 25-Jun-2015
195 Views
Preview:
DESCRIPTION
TRANSCRIPT
Enterprise LocationAddressing the problem of location reporting from callers within corporate networks
Presented by:Mark J. Fletcher, ENP (Fletch)Chief Architect – Worldwide Public Safety SolutionsFletcherM@Avaya.com +1 908 848-2602
© 2014 Avaya Inc. All rights reserved. 22
The problem
Emergency calling today is based on: – TN presentation to the network for routing
Citizen555-1234
Public Safety
Agency“A”
Public Safety
Agency“B”
Public Safety
Agency“C”
SRDB*555-1234 = Agcy A555-4567 = Agcy B555-6789 = Acgy C
*Selective Router Data Base
Citizen555-4567
Citizen555-6789
Telecom Provider
© 2014 Avaya Inc. All rights reserved. 33
CLocDB*555-1234 = Addr A555-4567 = Addr B555-6789 = Addr C
The problem
Emergency calling today is based on: – TN presentation to the network for routing
– TN Presentation to the Control Room for response location reference
– Registered name
– Registered address
Citizen555-1234
Public Safety
Agency“A”
SRDB555-1234 = Agcy A555-4567 = Agcy B555-6789 = Acgy C
*Caller LocationData Base
Telecom Provider
555-1234David Smith3324 Arch St
© 2014 Avaya Inc. All rights reserved. 44
CLocDB*555-1234 = Addr A555-4567 = Addr B555-6789 = Addr C
The problem
Emergency calling today is based on: – TN presentation to the network for routing
– TN Presentation to the Control Room for response location reference
– Registered name
– Registered address
– While this is typically sufficient for a residential citizen, individuals at work have additional challenges due to:
– Large Campuses with multiple buildings
– Unclear street addresses or no address
– Buildings with access control and multiple floors
Citizen555-1234
Public Safety
Agency“A”
SRDB555-1234 = Agcy A555-4567 = Agcy B555-6789 = Acgy C
*Caller LocationData Base
Telecom Provider
555-1234David Smith3324 Arch St
© 2014 Avaya Inc. All rights reserved. 55
The primary confusion is the granularity of detail needed
Since we are used to the ‘residential model’, the initial inclination is to have a Public ALI record for each individual.
– Large Database
– Complex to manage
– Incurs monthly costs
There are 50 phones on this floor, imagine 10 floors in the building and 3 buildings in a campus.
That becomes 1500 TN’s to be managed monthly.
© 2014 Avaya Inc. All rights reserved. 66
The problem scales out of control quickly
1,500 Records$3,000 Monthly
$36,000 Annually
© 2014 Avaya Inc. All rights reserved. 77
Zones reduces the number of Managed TNs required
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
ZONE
Response AddressA
Response AddressB
Response AddressC
30 Records$60 Monthly
$1,800 Annually
© 2014 Avaya Inc. All rights reserved. 8
Emergency at Cube 2C-231 – Where is that!?
Responders on scene need to be ready and know help is coming.
?
?
?
© 2014 Avaya Inc. All rights reserved. 99
Enterprise Location granularity INTERNALLY
Enterprise environments can utilize additional call handling technology to aid in response:
© 2014 Avaya Inc. All rights reserved. 1010
Enterprise Location granularity INTERNALLY
Enterprise environments can utilize additional call handling technology to aid in response:– Designated 1st Response Teams
– Campus Police Officers and EMS
– Any other authorized group or individualEMERGENCY
© 2014 Avaya Inc. All rights reserved. 1111
Enterprise Location granularity INTERNALLY
Enterprise environments can utilize additional call handling technology to aid in response:– Designated 1st Response Teams
– Campus Police Officers and EMS
– Any other authorized group or individual
Data that can be provided includes– Floor Plan
– HazMat
– IP Video Feeds
EMERGENCY
© 2014 Avaya Inc. All rights reserved. 1212
Basic System Requirements
Direct access to Emergency ServicesEliminating the ‘Trunk Access Code’ (TAC)
© 2014 Avaya Inc. All rights reserved. 1313
Basic System Requirements
Direct access to Emergency ServicesEliminating the ‘Trunk Access Code’ (TAC)
On Site Notification Alerting to devices that an emergency call has occurred
© 2014 Avaya Inc. All rights reserved. 1414
Basic System Requirements
Direct access to Emergency ServicesEliminating the ‘Trunk Access Code’ (TAC)
On Site Notification Alerting to devices that an emergency call has occurred
Interception or termination of calls internally prohibited to untrained internal staff
PD
© 2014 Avaya Inc. All rights reserved. 15
Location Discovery
Understanding where the emergency is occurring is the key piece of information required to provide assistance.
However the problem can be tackled – with cooperation from the network staff.
What is perceived as the biggest Enterprise challenge?
© 2014 Avaya Inc. All rights reserved. 16
Common VoIP Location Discovery Mechanisms
Subnet (Zone Level reporting)
IP Subnet maps to floor plan
Instantaneous discovery
ADLR
Additional DataLocation
Repository
© 2014 Avaya Inc. All rights reserved. 17
Common VoIP Location Discovery Mechanisms
Subnet (Zone Level reporting)
IP Subnet maps to floor plan
Instantaneous discovery
Switchport (Station Level reporting)
Maps to jack via wiremap
Near real-time discovery
ADLR
Additional DataLocation
Repository
© 2014 Avaya Inc. All rights reserved. 18
CableMgmt
PBXUser Data
WLANUser Data
EnviroInfo
LDAP
ActiveDirectory
Opt InInfo
Smart Building
Common VoIP Location Discovery Mechanisms
Subnet (Zone Level reporting)
IP Subnet maps to floor plan
Instantaneous discovery
Switchport (Station Level reporting)
Maps to jack via wiremap
Near real-time discovery
ADLR
Additional DataLocation
Repository
Data is packaged ready for pick-up by the Control Room or
1st Responder
© 2014 Avaya Inc. All rights reserved. 1919
Enhanced On Site Notification with ADDITIONAL DATACorrelation of Information
• Screen Pop Alert Clients can be anywhere
• Detailed Floor Plans / Video
• Integrations with Smart Building Data
• Mobile apps, Web based or Reader boards
By empowering the Enterprise with information about the incident they can contribute additional data simplifying the call for help.
A hang up call now becomes a hang up with high temperature readings in the area.
© 2014 Avaya Inc. All rights reserved. 20
Deliver detailed location information ‘by reference’ today and ‘by value’ using SIP in the future . . . .
SRDB and ALI databases will NO LONGER BE REQUIRED
Nor will their management and monthly fees.
Next Generation Emergency Services:
Today: OVER The TOP NG Emergency Services Tomorrow: URI/URL sent VIA the SIP header
NG Emergency Services Data
Aggregator
ANI/ or Location Data
Over the Top NG Emergency ServicesGetting the network ready TODAY = No Migration
© 2014 Avaya Inc. All rights reserved. 2121
Remote and Home based Devices
Almost any device can be nomadic– TDM (Virtual Office at remote location)
– VoIP (User Moves without notice)
– WLAN (Inherent Mobility built in device)
– Remote Workers (Nomadic VPN off premesis)
Enterprise MLTS / PBX can provide tracking– On Site Notification
– Proper call routing
– Caller ID (ANI) Manipulation
VPC Provider will be required for REMOTE users
© 2014 Avaya Inc. All rights reserved. 22
CONCLUSION: While challenges do exist, enterprise networks can provide valuable and
relevant information to public safety control rooms that can significantly increase both location accuracy and on-site situational awareness of
emergency calls from within enterprise networks.
The most significant challenges are public awareness, and published best practices/legislation requiring commercial entities to implement a solution.
© 2014 Avaya Inc. All rights reserved. 2323
top related