EmergencyCalls
Latest
Nexus S on Vodafone Australia won't get Jelly Bean today after all
Continuing this morning's Jelly Bean soap opera, we've just heard that Nexus S owners on Vodafone Australia won't be getting their pioneering update today -- despite the fact that only 24 hours have elapsed since the carrier said the roll-out was on its way. According to the carrier's official blog, the update has been delayed because Android 4.1 "does not meet all Australian regulatory requirements related to emergency calls." Ouch. On the other hand, that sounds eminently fixable. [Thanks, Daniel]
Verizon dropped 10,000 emergency calls during January snowstorm in Maryland, FCC finds it 'alarming'
Uh oh, Verizon's got itself into a bit of hot water with the old FCC. An outage during a snowstorm last month has reportedly resulted in a whopping 10,000 calls to 911 not being connected by the big red carrier. That would be bad enough in itself, but the less-than-pleased Communications Commission also notes that the emergency services that missed out on these calls were not alerted to the connectivity failure -- in fact, Maryland's Montgomery County officers were the ones to inform Verizon of the fault it was having, which was then promptly repaired within 15 minutes. The FCC is now curtly asking the network to check its entire footprint for similar vulnerabilities -- as the January events were apparently "not unique" -- and to propose remedial actions and monitoring systems to prevent it happening again.
AT&T redirecting 911 calls from Salt Lake City to Seattle, working on a fix (update: fix is in)
Ready for a surreal way to start your day? Salt Lake City's KSL News has a report out this morning detailing the baffling experience of AT&T subscribers trying to access emergency services in the city. Instead of being routed through to their local dispatcher, the urgent calls somehow found their way to Seattle's 911 response center. Brought to the news team's attention by one Tony Sams, this issue was originally thought to originate in his iPhone's GPS system, as he was being identified as being located in the Seattle area, but then his local police also tried dialing their own number only to find themselves chatting it up with their Emerald City colleagues. Until they figure this out, we'd recommend using your landlines -- if you still have one of those antiques -- or just yelling at passersby for help. Hit the source for the full video report and the 10-digit direct number for Salt Lake City general dispatch. Update: AT&T has been very nippy in getting this routing problem sorted out, and proper service has been restored. The company is now investigating the cause of this problemo. [Thanks, Ryan]
Jitterbug issues recall to fix emergency calling in "no service" areas
When we first saw this, our immediate reaction was, "trust us, Jitterbug, we appreciate your extra-mile attitude here, but it's not your fault that 911 doesn't work without a signal." Turns out that's not quite the issue, though -- in reality, Jitterbug is recalling phones sold after March 1 of last year because they maybe be unable to place calls to 911 in areas where the company doesn't have MVNO or roaming agreements in place. In other words, the phone is showing "no service," but you've still got a signal -- and whenever a phone's got a signal, it should be able to dial the cops. Jitterbug is offering affected customers the option either of taking their handset into a local Samsung service center or mailing it in, at which point a software update will be applied. Too bad these things don't do firmware updates over the air, isn't it? [Via Phone Scoop]
