VoIP Technology for Emergency Services Spring VON 2006

1. VoIP Technology for Emergency Services Spring VON 2006 James RaffertySr Product Manager jraff@cantata.com Proprietary and Confidential

2. Agenda • Background • Emergency Svcs – Pre-VoIP • Issues for VoIP and Emergency Services • Transition to Hybrid VoIP Model • What if we did it right? • Vision for tomorrow’s Emergency Services • On the Drawing Board • Resources

3. Background • In the middle of the night, a crisis occurs in a family • We dial 911 • We connect to an operator • Ideally, we get the emergency service we need • But, what if? • We are on a mobile phone away from home • We have a VoIP service with limited or no E911 support • We’d like to use Instant Messaging to get service • What then?

4. The Story Continues… • Today’s Basic 911 service in the US • Was designed for landline use • Can connect us to one of 6000 Public Service Access Points (PSAPs) • In 80% of cases, CAMA tonal signaling passes your caller ID (ANI) to the PSAP for a lookup of your address in an ALI (Automatic Location Information) database • Enhanced (E911) Service • Uses SS7 to pass the calling number, which then causes a database lookup Much less precise location information if called from a mobile phone

5. Emergency Services – Fixed Line

6. Here Comes VoIP • VoIP has some of the same issues as wireless • Location may either be fixed or mobile • Early VoIP services had NO 911 connections or limited • Recently, FCC required VoIP operators to connect to the E911 infrastructure “as is” • Most VoIP operators of phone replacement services such as Vonage complied • Still no way to connect via PTP services such as Skype

7. Transition to IP Emergency Services • Voip connections to the existing infrastructure • Keep the PSAPs as is, but improve the database structure (ala NENA i2) • Upgrade the PSAPs to accept direct VoIP connections • Evolution: Bring the PSAPs into the 21st century with better databases, multi-media access and the user’s choice of communication method

8. Connect to Today’s System with VoIP

9. Improve the Database

10. Add VoIP to PSAPs

11. Multi-Modal IP Emergency Services

12. On the Drawing Board • ECRIT Standards work from IETF • Assumes that PSAPs or equivalent can be reached directly via SIP • Will provide methods for automatically extracting location of the endpoint from the network • Will allow for regional differences • Will provide methods for routing emergency calls based on location • Likely to use special URI address characters such as SOS • Will provide methods that support VoIP and other real time communications • Beyond the ECRIT Standards • Will need to support backward compatibility with PSTN and PLMN phones

13. Summary • Ample Opportunity to improve Emergency Services by moving to VoIP • Changes will take place in phases • Improve the Database (ala NENA i2) • VoIP connection to PSAPs • Multimodal IP connection to PSAPs • Challenge is to fund the upgrades while continuing to improve emergency service • Standards for all-IP Emergency Services under Development • Still need to support PSTN and wireless phones

14. Resources • NENA Web site: • www.nena.org • i2 specification • Various other E911 emergency specifications • IETF ECRIT Working Group • http://www.ietf.org/html.charters/ecrit-charter.html • Paper on VoIP Emergency Services Architecture and Prototype • http://www.cs.columbia.edu/~hgs/papers/Mint0510_VoIP.pdf