Core VoIP and 911 issues and alternatives Henning Schulzrinne Columbia University August 2003.

Slides:



Advertisements
Similar presentations
Presence and IM as SIP Services Jonathan Rosenberg Chief Scientist.
Advertisements

SIP and Instant Messaging. SIP Summit SIP and Instant Messaging What Does Presence Have to Do With SIP? How to Deliver.
Fall VoN 2000 SIP Servers SIP Servers: A Buyers Guide Jonathan Rosenberg Chief Scientist.
VON Europe /19/00 SIP and the Future of VON Protocols SIP and the Future of VON Protocols: Presence and IM Jonathan Rosenberg.
Fall VoN 2000 SIP for IP Communications Jonathan Rosenberg Chief Scientist.
ENUM Overview – July The ENUM Objective Mapping PSTN addresses into the IP world ENUM allow any IP device to establish whether an E.164 telephone.
There are many types of WAN technologies that can be used to solve the problems of users who need network access from remote locations. We will go through.
The current System Landline caller The emergency call process starts with a caller dialing (highly simplified) © 2011 Colorado Resource.
Johan Garcia Karlstads Universitet Datavetenskap 1 Datakommunikation II Signaling/Voice over IP / SIP Based on material from Henning Schulzrinne, Columbia.
Document IPW-111 TIPHON Perspective on VoIP Numbering John Horrocks (DTI) Tiphon WG4 Chair.
Preparing for the Future.  Emergency calls today are primarily voice.  People expect to reach PSAP when dials 911.  People have multiple ways and devices.
Origins of ECRIT IETF has been working on location since 2000 –Spatial BoF, eventually GEOPRIV chartered in 2001 GEOPRIV provides location information.
NENA’s 11 th Annual Technical Development Conference A proposal to support E911 calls on Voice over IP Networks Martin Dawson – Nortel Networks.
© 2010 Level 3 Communications, LLC. All Rights Reserved. Level 3 Communications, Level 3, the red 3D brackets and the Level 3 Communications logo are registered.
A prototype i3 VoIP PSAP implementation Henning Schulzrinne, Anshuman Rawat, Matthew Mintz-Habib, Xiaotao Wu and Ron Shacham Dept. of Computer Science.
A Generic Event Notification System Using XML and SIP Knarig Arabshian and Henning Schulzrinne Department of Computer Science Columbia University
IETF 61 (November 2004) ECRIT1 Requirements and Architecture for Emergency Calling draft-schulzrinne-sipping-emergency-arch draft-schulzrinne-sipping-emergency-req.
911 services: wireline, wireless and VoIP Prof. Henning Schulzrinne Dept. of Computer Science Columbia University, New York FCC Solutions Summit March.
Internet E-911 System Henning Schulzrinne and Knarig Arabshian Department of Computer Science Columbia University
Internet Telephony Helen J. Wang Network Reading Group, Jan 27, 99 Acknowledgement: Jimmy, Bhaskar.
28 June 2015 Emergency services for SIP Henning Schulzrinne.
NG911 – Development plans Henning Schulzrinne Columbia University.
The Next Generation Proof-of-Concept System.
Providing Emergency Services in Internet Telephony Henning Schulzrinne and Knarig Arabshian Department of Computer Science Columbia University
Presence Vishal Kumar Singh and Henning Schulzrinne Feb 10, 2006.
An SAIC Company Telcordia View of NENA Progress on VoIP Migration Plan Telcordia Contacts: Nadine Abbott (732) An SAIC Company.
Alternatives for Providing Routing and Location Information to support Emergency Calling from IP Enterprises Prepared For: NENA VoIP Meeting on behalf.
Ernst Langmantel Technical Director, Austrian Regulatory Authority for Broadcasting and Telecommunication (RTR GmbH) The opinions expressed in this presentation.
March 2004SIPPING - IETF 59 (Seoul)1 Emergency calling draft-ietf-sipping-sos draft-schulzrinne-emergency-arch Henning Schulzrinne Columbia University.
1 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Emergency calls related work done in IETF Gabor Bajko May 22, 2006.
Windows Internet Connection Sharing Dave Eitelbach Program Manager Networking And Communications Microsoft Corporation.
© 2008 AT&T Knowledge Ventures. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures. 1 Video Relay Service and Assignment.
SIP.edu Speaker: Changyu Wu Adviser: Quincy Wu Date:2006/12/18.
NENA Next Generation Architecture
Fall VON - September 28, 1999 C O N N E C T I N G T H E W O R L D W I T H A P P L I C A T I O N S SIP - Ready to Deploy Jim Nelson,
DNS: Domain Name System
1 NGN Issues - Numbering and Addressing Peter Darling ACIF NGN FOG No. 3.
PSTN – User ENUM – „Infrastructure ENUM“ An ETSI View Richard Stastny IETF60 San Diego.
1 DNS: Domain Name System People: many identifiers: m SSN, name, Passport # Internet hosts, routers: m IP address (32 bit) - used for addressing datagrams.
Applied Communications Technology Voice Over IP (VOIP) nas1, April 2012 How does VOIP work? Why are we interested? What components does it have? What standards.
© Copyright 2007 Arbinet-thexchange, Inc. All Rights Reserved. Voice Peering Steve Heap Chief Technology Officer.
DNS based IP NetLocation Service China Telecom Guangzhou Institute
1 ENUM’s Role in VoIP IP Telephony Conference & Expo Miami February 12, 2004 Sheri Jenkinson VeriSign Communication Services Product Manager - ENUM
Internet Telephony (VoIP) Henning Schulzrinne Dept. of Computer Science Columbia University Fall 2003.
Draft-rosen-ecrit-emergency- framework-00 Brian Rosen NeuStar CPa
IP Network Clearinghouse Solutions ENUM IP-Enabling The Global Telephone Directory Frank Estes Vice President , ext 224
CP-a Emergency call stage 2 requirements - A presentation of the requirements from 3GPP TS Keith Drage.
148 Sidevõrgud IRT 0020 loeng nov Avo Ots telekommunikatsiooni õppetool, TTÜ raadio- ja sidetehnika inst.
November 2005IETF64 - ECRIT1 Emergency Service Identifiers draft-ietf-sipping-sos-01 draft-schulzrinne-sipping-service-01 Henning Schulzrinne Columbia.
The State of VoIP Peering Charles Studt Director of Product Management, VoEX.
Project Objectives A multi-function programmable SIP user agent for multimedia communications, such as audio, video, white board, desktop sharing, shared.
August 2005IETF 63 - SIPPING Specifying Media Privacy Requirements in SIP Ron Shacham Henning Schulzrinne Dept. of Computer.
1 911 Background  Traditional 911 ~6,000 PSAPs in the US Selective routers route calls to correct PSAP –Operated by carriers –Relies on DB of fixed subscriber.
17 February 2016 SIPPING - IEPREP Joint Meeting Fred Baker - IEPREP co-chair Rohan Mahy - SIPPING co-chair.
Internet Real-Time Lab, Columbia University NG9-1-1 Prototype Demo Jong Yul Kim, Wonsang Song, and Henning Schulzrinne.
VoIP Emergency Calling Support Telcordia Contacts: Nadine Abbott (732) An SAIC Company Provided to support discussions in.
SIP & How It Relates To YOUR Business. Jeff S. Olson Director of Marco Carrier Services David Bailey-Aldrich Technology.
SOSIMPLE: A Serverless, Standards- based, P2P SIP Communication System David A. Bryan and Bruce B. Lowekamp College of William and Mary Cullen Jennings.
HOW TO GUIDE: INEXPENSIVE INTERNET PROTOCOL TELEPHONY SOLUTION Created by: Cameron Adkisson Eastern Kentucky University
Postech DP&NM Lab Session Initiation Protocol (SIP) Date: Seongcheol Hong DP&NM Lab., Dept. of CSE, POSTECH Date: Seongcheol.
ECRIT - IETF 62 (March 2005) - Minneapolis 1 Requirements for Emergency Calling draft-schulzrinne-sipping-emergency-req-01 draft-ietf-sipping-sos-01 Henning.
VoIP ALLPPT.com _ Free PowerPoint Templates, Diagrams and Charts.
IP Telephony (VoIP).
THIS IS THE WAY ENUM Variants Jim McEachern
DNS.
Preparing for the Future
Purpose of Project Conduct research in support of NENA’s Next Generation E9-1-1 initiative Conduct that research without endangering public safety Share.
Thoughts on VoIP and Emergency Calling
Emergency Calling Architecture
Policy enforcement and filtering for geospatial information
Presentation transcript:

Core VoIP and 911 issues and alternatives Henning Schulzrinne Columbia University August 2003

Crucial differences between VoIP and traditional landline PSTN All devices should be treated as mobile, even if they are desk phones Users can take phone home and maintain identity Long-term, users may not have E.164 numbers E.164 numbers may not reflect geographic area Area code can be arbitrary There are no central “switches” Maybe gateways There is no technical need for telephone carriers we don’t have “ carriers” either just ISPs (who do not need to know that some packets carry voice)

Core issues Identifying emergency calls Identifying the right PSAP Conveying location information to PSAP

Identifying emergency calls Outbound proxy must be able to reliably identify emergency calls for routing and special handling Despite different naming conventions caller may be “roaming” Suggestion: tel:112 Local dialplan on phone translates dialed digits to common identifier (e.g., 112, 911, 9-911, etc.)

Finding the right PSAP Option 1: Query Outbound proxy queries public mapping database Database address is pre-configured mapping DB What PSAP handles geoloc o N; o W; ALT: floor 0? SIP e.g., SOAP SIP tel:

Finding the right PSAP Option 2: Proxy request Outbound proxy routes all requests to designated SIP proxy with well-known name (e.g., psap.us.info) DNS SRV allows redundancy and load balancing mapping DB What PSAP handles geoloc o N; o W; ALT: floor 0? SIP internal query (not exposed)

Finding the right PSAP Option 3: fully distributed Outbound proxy routes all requests to PSAP All proxies subscribe to PSAP database updates (e.g., via SIP event notification) Updates are infrequent and database small in size mapping DB What PSAP handles geoloc o N; o W; ALT: floor 0? SIP internal query (not exposed) master mapping DB periodic updates secondary primary

Finding the right PSAP, cont’d Scaling is not a major issue 200 million 911 calls in 2002  roughly 6 calls/second typical SIP proxies can handle app. 100 calls/second 6000 PSAPs  table easily fits into RAM guess: 1000 bytes/entry  6 MB can store all in local table (option 3) thus, only need one server for whole US (+ backups)

Conveying location information Three options: civil geospatial unique telephone number (ELIN - may not be dialable, just for ALI lookup) worst option, since number may not be local

IETF efforts related to emergency communications SIP & SIPPING WG: network-asserted identity  may be usable for identifying caller (RFC 3325) P-Asserted-Identity: tel: framework and requirements document for emergency calling GEOPRIV WG: location object, using OpenGIS GML XML format privacy rules for retention and distribution, both simple and detailed civil and geospatial information in DHCP (auto-configuration) soon: conveying location information in SIP requests IEPREP WG: disaster communications priority for GETS-like calls at signaling and traffic level

Protocol standardization needed Approach: facilitate migration to all-IP environment do not burden VoIP with legacy considerations modular components  don’t assume mechanism used to determine location allow multiple mechanisms (e.g., options 1-3) have small number of gateways that translate between old and new avoid national standards at all cost Needed (beyond in-progress work): conventions for identifying emergency calls updating PSAP mapping database