Transcript Weaving the process into the data standards

Migrating to IP? Why You
Should Plan for E911 First
Presented by
Michael Anderson
Agenda
 Why Implement E-911?
 Considerations before deploying E-911 in
a VoIP Environment
 What about Wi-Fi Phones?
 Flatten and Consolidate
 On-site Notification
 Q&A
Why Implement E-911?
 Ethical
 It is the right thing to do
 Protects the organization’s people
 Legal
 Enhanced 911 is being mandated across much of the U.S.
 Various mandates in AL, AR, CO, CT, FL, IL, KY, LA, MA, ME, MN,
MS, TX, VA, VT, WA
 FCC VoIP Carrier Ruling (S428) Feb. 2008
 FCC Notice of Inquiry for Broadband 2011
 General Duty Clause in OSHA
 www.911etc.com/legislation
 Enterprise Network Topology
 Flatten and Consolidate Network
 Remote Sites (no local trunks)
 Mobile IP end-users
 Geographically Nomadic Softphone users
Who is Responsible?
A Technical Requirements Document
published in February of 2009 by
NENA says that:
The owner of or leadership of the organization who gains
benefit from the services of an MLTS is ultimately
responsible to ensure that the information contained in the
PS/ALI database is accurate.
16 States with Current
E-911 Legislation
(Six States have legislation pending)
911 ETC Data Flow for Traditional TDM
PS/ALI Solution
E911 Database
Scheduled Dynamic
Directory Export
PBX
911 Call Placed
ISDN PRI
Internet
Selective Router
911 ETC
Import Processor
(E-Mate Auto-MAC)
911 ETC
Export Processor
(911 Call Center)
Public Safety Answer Point
911 ETC Data Center
Errors
Regional
ALI Data Center(s)
Considerations for E-911 within a VoIP
infrastructure
Network region maps
VLAN configurations
Cable plant diagrams
Self-administration of MACs
Mobile end-users
Enterprise Network
 SIP Trunks
 MPLS
 Main hub sites
 Remote spoke sites
 Nomadic end-users






New Common Terms (VoIP)
ELIN-ERL
What is an ELIN?
 As defined by NENA:
Emergency Location Identification Number
ANI or pANI presented to the PSAP
What is an ERL?
 As defined by NENA:
Emergency Response Location
Network Region within the Switch?
VLAN subnets?
E911 Zones using ELINs / ERLs
Considerations before deploying E-911
in a VoIP Environment.
 Free
Mobility
 Discovery
 PBX
 Subnets
 Granularity
 Discovery
Software
 Network
Region
map
E911 and WI-FI Phone
Wireless
AP
Wireless
AP
Wireless
AP
 Wireless Access Point
Location Could Give
Incorrect Location
Information
 Movement of the
User During the 911
Call
911 ETC VoIPConnect
Enterprise Diagram
VPN CONNECTION
Soft Phone
SoftLoc
Remote
Communication Call Server
(PBX)
AES (Avaya)
Off Campus Office
Phone 911 Call
Home
TSAPI
SIP
Handoff
Location
Dashboard
Updates
IP DISCOVERY
IP Phone Registry
Network Map (ELIN/ERL)
Telco PS/ALI
Data Centers
ERL #3
3rd Floor East Side
Voice Positioning
Center/Location
Provisioning Server
PSAP
(911 Call Center)
Selective
Router
Legend
Pre-911 Call Location Updates
IP PHONE
On Campus
VoIP Phone
911 Call
ERL #2
2rd Floor East Side
IP PHONE
On Campus Call Order
ERL #1
1rd Floor East Side
Active On-Campus 911 Call Path
IP PHONE
Active Off-Campus 911 Call Path
Off Campus Call Order
Emergency Onsite Alerts
Flatten, Consolidate, and Extend
(PS/ALI location updating)
New York
Chicago
AT&T SBC
Data Center
AT&T CA
Data Center
Cleveland
Verizon N.
Data Center
VA / DC
Verizon S.
Data Center
San Diego
Honolulu
Flatten, Consolidate, and Extend
(SIP and VPC location updating)
VPC
Enterprise
Node #2
Chicago
New York
AT&T SBC
Data Center
VA / DC
AT&T CA
Data Center
Verizon S.
Data Center
San Diego
Honolulu
Enterprise
Node #1
Verizon N.
Data Center
Mobile + Remote User location Identification
SoftLoc Screenshot Tour
The following is a visual tour of the SoftLoc application and its Configuration Server:
User enters location details and
clicks “validate”
SoftLoc Screenshot Tour, cont.
The user has closed the interface and has
not chosen a location.
SoftLoc has terminated the configured
application because a location has not
been provisioned. The monitored
application and termination settings can
be set from the configuration server(s).
VoIP-VPC E-911 Emergency Services
Features to Consider
 Support of all emerging technologies
 Start-up and Maintenance Costs - TCO
 Automation and accuracy
 Address validation success and efficiency
 Ease of integration (PBX agnostic)
 Speed to deployment (time to compliance)
 Customization capability
 Coverage and Connectivity options
 Responsive Customer Support
911 ETC’S Customers:
ROCKEFELLER CENTER
U.S. General Services Administration
Client case-studies at www.911etc.com
911 ETC Provides:













Full time customer support with a trouble ticketing
process
Campus IP Discovery Appliance/software
Ongoing scheduled database management services
Synchronized error correction and status reconciliation
Data and event reports available upon request
Full data back-ups
Emergency Onsite Notification
Data file processing logs and notifications
Interface support with Telco contacts for routing issues
Testing support
E911 database design consulting
Custom data loaders to accommodate client database
needs
PSAP and Telco coordination and administration
911 ETC: Contact Information
Michael Anderson
425-444-7990
[email protected]
w w w . 9 1 1 E T C . c o m
911 ETC/Bandwidth Platform Differences
 Services all carriers on single, integrated platform
 Dynamic Geospatial Routing – Routing decisions made at
time of call based on real-time X,Y coordinate of caller
and PSAP boundary; automated and dynamic
 Dynamic Address Validation – Efficient and intelligent with
a 98% or better validation success rate on average
 Emergency call center (ECC) for NRFs and I1 calls
 100% (93% Enhanced) Coverage in US, Canada, Puerto
Rico
 Fully-redundant nationwide network
 SIP or ISDN PRI interconnection capable