Slashdot Mirror
Vonage 911 Deadline Passed
An anonymous reader writes "Yahoo is reporting that the FCC may block any new customers wishing to sign up with Vonage. The internet phone service company has passed the Monday deadline that was given to them to provide reliable 911 service. From the article: "The company -- which has more than 1 million subscribers -- said it was capable of transmitting a call back number and location for 100 percent of its subscribers, but that it still was waiting for cooperation from competitors that control the 911 network."
We have completed 911 Dialing activation for your Vonage line...
e x.htm and edit your information from the 911 Dialing feature box.
...
Now when you dial 911, Vonage will route your call to a general number at your nearest emergency response center, based on the address below:
If this address is incorrect, simply click on the following link to login to your web account https://secure.vonage.com/vonage-web/features/ind
Please note if you move your device you must reactivate 911 Dialing with your new address. If you add a line to your account you will need to activate 911 Dialing for that line as well.
If you would like more information about Vonage's 911 Dialing service, please visit the 911 Feature page at http://www.vonage.com./ If you have any questions please reply to this email, or call us Toll Free at: 1-VONAGE-HELP (1-866-243-4357), 24 hours a day, 7 days a week.
We appreciate your business.
So what gives?
As a Vonage user, I've wondered what kind of problems I might run into, but last week, I began to feel anxious and my heart began to pound / chest pains... I asked a friend to call 911.
;).
There was a 1-2 second delay and I could tell that my friend had been transfered, but within minutes medics were at my house. I'm not sure what kind of system they use, but here in St Louis it works.
On a lighter note, the medics didn't find anything wrong with me, and I've chalked it up to stress / coffee
That would be Unamerican
I think that depends on whether the year is mod 4.
As I see it, one of the problems with this is simply determining where "phone" services begin and end. For example, while Vonage or Lingo may be a real 'phone replacement' and for 99.9% of users should be able to do 911 service, how about Skype? If you only use Skypeout and you only use it via a headset on a laptop, is that VoIP? It certainly *is* "Voice over IP", but does that make it a phone service that should need 911 service?
If they start classifying things like Skype as a voice telecommunications service and requiring 911 calls to function, then what's next? 911 requirements for Teamspeak?
Maybe a VoIP "phone" is one which can place a call which eventually gets circuit switched on one end, even if 99% of the transit is packet switched.
It seems to me that what really needs to happen is a revamping of the 911 system to deal with the portability of numbers. You want 911? Fine, go somewhere and configure your address any time you move the phone around. When you dial 911, it transmits your entered address. Possibly the hardware/software acting as your phone also monitors the MAC address of its default gateway after you change the address associated; if the MAC address changes but the address has not, a warning goes out to emergency services that notes that there is reason to believe the address may not be completely reliable (and thus, hopefully an emergency operator can confirm it with you when you call).
Lots of little things rely on the phone network. My house alarm, for example, will freak out completely if I cut my phone service entirely, because it uses the phone line to keep in touch with the alarm monitoring service.
Fight the fall of slashdot by supporting PlayfullyClever in your sig.
From the time the FCC released the new rules, VoIP providers only had four months to provide E911 services to all of their customers. Wireless carriers (who have considerably more clout and better paid lobbyists), were given ten years to comply. Still think it's fair to start slapping fines on an industry that's barely out of the gate?
Entrepreneur : (noun), French for "unemployed"
"land-lines" have a major advantage over cell phones (at least in california). Here, if you call 911 on a cell phone, you get forwarded to one of two CHP call centers, they can be massively swamped during rush hour, and really have no idea about your area.
A land-line 911 call, however, goes straight into your local fire/ems dispatch center, and they usually respond faster, respond the right engines/ambulances, and even get the roads right.
(volunteer FF in Cali)
I work for a company that provides E911 service for VoIP providers. I won't get into all the details but there are quite a few misconceptions so far on this board. The big problem with VoIP, other than the fact that we can't determine where you are (unlike wireless where at least we know your closest cell tower, if not your GPS or location via triangulation) is the totally nomadic nature of the device. Right now if you don't tell us where you are we have no clue. You could be in Australia. There are lots of technical proposals for this (DHCP sending Geopriv location when you get IP, etc.) but none are there yet.
A basic primer: the E911 network is actually a separate network. The local Wireline End Office switch has dedicated trunks to a 911 tandem (aka Selective Router), which has dedicated trunks to a set of PSAPs (local 911 call centers). For wireless the wireless carriers simply ordered dedicated trunks from their local MSC (mobile switching center) to these selective routers. Obviously, Vonage does not have a local presence. They had to figure out a way to connect to all 650 selective routers nationwide from their data centers. Imagine now some local startup in Florida that has to connect redundant T-1s (the requirement of the ILECs like SBC in order to have E911 access) to all 650 selective routers. It ain't going to happen in 120 days.
Wait, we're not done. The next issue is how to transmit the address of the subscriber to the PSAP real-time. The wireline E911 databases hold static addresses under the assumption that you never moved. This doesn't work when you can move your device. If I live in Texas but travel to Chicago for work (and go to the website to update my address) how do I get the address into the right system real-time? These databases are mostly managed by the ILECs and there are probably 50 or so out there, each totally standalone. The legacy 911 service order processes of the phone companies for order flowthrough typically take a few days.
Fortunately, the wireless carriers figured out a solution: real-time steering from the local 911 database to a central datastore which transmits the location. For wireless the X,Y coordinates are transmitted. We piggy-backed off this standard but had to modify it to support civic locations (well, MSAG, but that's another essay). Of course, the ILECs (SBC, etc.) required new agreements for this. It also requires a new query key assigned for VoIP so everyone knows this is a VoIP call and the carrier to call in the event of a problem. This query key lets the local 911 database know which provider to query. This query key also gets around the constraint of the selective routers that only support local rate center NPA/NXXs. Basically, if you have a Chicago number in Dallas you can't get your call through. A p-ANI was developed for wireless to get around that.
Here's the problem: the query keys must be assigned to each provider. These are called ESQKs, or p-ANIs in the industry. The FCC was supposed to name a numbering authority to distribute these keys to all the providers. The industry recommended Neustar as the temporary RNA. Until this is done noone can provide true E911. Well, the FCC has been silent on this so we have all been in a Catch-22 situation.