Long Term Definition
• Because the VoIP world is SO different from the
current environment, we have to go back to basic
requirements:
– Identify a call as an emergency call
– Get it to the right PSAP
– Provide location of the caller
• The VoIP environment is ~2 orders of magnitude
more complex than existing voice telephony
systems
Complexities, complexities
– “Voice Service Provider” is not necessarily the pipe
provider
• There may not even be a “voice service provider”
– Calls WILL come from the big bad Internet
• You can “firewall”, but by definition, calls will be forwarded
anyway, right?
– There can be 4+ levels of service in the path
– Calls can come from anywhere, handled by equipment
shared across continents
– All voice endpoints are considered mobile
– End identifiers are uri’s not numbers
– Media Streams are not limited to voice
Chicago Café Scenario
Sierra Leone
Exports Ltd
Sierra
Leone
ISP
S.L. VSP
Sprint
globenet
uunet
tMobile
IL PSAP
NET
Chicago
PSAP Net
Big Picture of what we want to
do
• Figure out what the end goal is – when we
aren’t limited by PSTN, and current
deployment
• THEN figure out how to get from where we
are to where we want to be
• The tendency is always to jump to
solutions, but please, we need to write down
the system requirements
i18n
• VoIP, like the Internet does not respect political
boundaries.
• You cannot put a requirement on, or charge the
“service provider” if he is in Sierra Leone unless
you get a treaty
• The protocol work has to be done in IETF
(probably), and it WILL NOT do it unless it is
international
• NENA must start liaison work with others, e.g.
ETSI if protocol work will be needed (and it will)
Some VoIP basics
• Lots of different kinds of endpoints
– Hardphones, softphones, pdas, cellphones, wireless
(802.11)
• Lots of different networks
– Access Network
• Dialup, DSL, cable, T1, fiber
–
–
–
–
–
Core Network
Service overlays
Wholesale/Retail
Enterprise
VPN Tunnel