Language Selection

English French German Italian Portuguese Spanish

Texas sues Vonage over emergency service

Filed under
Sci/Tech
Legal

Abbott's lawsuit, filed in the District Court of Travis Country, Texas, accuses Vonage of deceptive marketing practices by not making it clear to customers that they must sign up separately for 911 service, instead of it being automatically part of the Vonage VoIP offering.

In an announcement about the lawsuit, Abbott cited a February incident in Houston in which a family with Vonage service couldn't get through to 911 dispatchers. Joyce John tried to dial 911 from a VoIP phone in her home as burglars broke into the house and shot and wounded her parents.

John's call to 911 connected to a recording saying she would have to dial 911 from a different phone. She eventually contacted authorities from a neighbor's house. “This Houston family’s moment of crisis signals a dire need for Vonage to clearly communicate to its Internet telephone customers that 911 access may not be available to them,” Abbott said in a statement. “This is not just about bad customer service; it’s a matter of life and death.”

A Vonage spokeswoman said the company would welcome a dialog with Abbott on how to improve its 911 service. Vonage customers are told multiple times, including twice during the subscription process, that they need to take action to sign up for 911 service, added Brooke Schulz, senior vice president of corporate communications for Vonage. Vonage warns customers on their dashboard online account summary that they have not signed up for 911 service, and Vonage sends e-mail to customers who have not activated 911 service, Schulz said.

The company also tells customers on its Web site's features page that they must pre-activate 911 service, although the company also notes that "Vonage offers 911 dialing to all customers."
"We want to work with the attorney general's office to resolve his concerns," Schulz said. "We do all these things today, and if those aren't adequate, let's talk about it."

The lawsuit, filed under the Texas Deceptive Trade Practices Act, requests the court issue an injunction stopping Vonage from "misrepresenting" the type of emergency telephone service it offers, according to a press release from Abbott. The suit seeks $20,000 per violation.

Because VoIP services route 911 calls through IP networks instead of the traditional telephone network, VoIP 911 service doesn't work the same way as traditional 911 service. Dispatch centers aren't able to pinpoint the address where the VoIP call originated, unlike enhanced 911 service available with most traditional telephone service today.

Vonage on March 7 reported it had exceeded 500,000 total phone lines on its network, and it was signing up customers at a rate of 15,000 lines per week.

Source.

More in Tux Machines

Security: Updates, IBM, Elytron and Container Vulnerability Scanning

  • Security updates for Friday
  • IBM Security launches open-source AI
    IBM Security unveiled an open-source toolkit at RSA 2018 that will allow the cyber community to test their AI-based security defenses against a strong and complex opponent in order to help build resilience and dependability into their systems.
  • Elytron: A New Security Framework in WildFly/JBoss EAP
    Elytron is a new security framework that ships with WildFly version 10 and Red Hat JBoss Enterprise Application Platform (EAP) 7.1. This project is a complete replacement of PicketBox and JAAS. Elytron is a single security framework that will be usable for securing management access to the server and for securing applications deployed in WildFly. You can still use the legacy security framework, which is PicketBox, but it is a deprecated module; hence, there is no guarantee that PicketBox will be included in future releases of WildFly. In this article, we will explore the components of Elytron and how to configure them in Wildfly.
  • PodCTL #32 – Container Vulnerability Scanning

NetBSD 8.0 RC1 Available, Bringing Initial USB 3.0 Support & Spectre/Meltdown Mitigation

It's a busy month for the BSDs with DragonFlyBSD 5.2 having come along with OpenBSD 6.3 and right before that was TrueOS 18.03. Now there's finally the release candidate of the long-awaited NetBSD 8.0 update. NetBSD 7.0 arrived back in October 2015 while the NetBSD 8.0 release should not be too much further out. Arguably most interesting with NetBSD 8.0 is its finally bring initial USB 3.0 support though the change-log currently just describes it as "some USB 3 support." Read more

FFmpeg 4.0 Released

  • FFmpeg 4.0 released
    Version 4.0 of the FFmpeg multimedia toolkit is out. There is a long list of new filters, formats, and more; see the announcement for details.
  • April 20th, 2018, FFmpeg 4.0 "Wu"
  • FFmpeg 4.0 Released With New Encoders/Decoders, NVIDIA NVDEC Decoding
    FFmpeg 4.0 is now available as the latest major release for this widely-used open-source multimedia encode/decoder library. FFmpeg 4.0 introduces NVIDIA NVDEC GPU-based decoding for H264 / MJPEG / HEVC / MPEG-1/2/4, VC1, VP8, and VP9 formats. This release also adds an Intel QSV accelerated overlay filter, an OpenCL overlay filter, VA-API MJPEG and VP8 decoding support, new VA-API filters, and many other accelerated code path improvements.

Graphics: AMD, Intel and Vulkan

  • AMDGPU DC Fixes For Linux 4.17 Take Care Of "The Dark Screen Issue"
    AMD's Alex Deucher has sent in a small set of fixes for the AMDGPU Direct Rendering Manager driver in the Linux 4.17 kernel. The three patches are for fixing a dark screen issue with AMDGPU DC, a fix for clock/voltage dependency tracking for WattMan, and an updated SMU interface for the yet-to-be-announced Vega 12 GPU.
  • Intel KVMGT 2018-Q1 Release Offers Mediated GPU Pass-Through Improvements
    While the relevant bits for supporting Intel GPU mediated pass-through to virtual machines with KVM are now upstream in the Linux kernel as well as in QEMU 2.12, Intel developers have just announced their quarterly release of "KVMGT" for those wanting the officially blessed configuration for running Intel virtual GPU support with KVM virtual machines.
  • RADV Vulkan Driver Adds Vega M Support
    Following RadeonSI adding "Vega M" support for the new Radeon graphics appearing embedded on select Intel Kabylake processor packages, the RADV developers have similarly staged their Vega M support in this open-source Vulkan driver.
  • The Forge Now Offers Full-Featured Vulkan Support On Linux
    Earlier this month we covered "The Forge" picking up initial Linux support and now they have rounded out their full-featured Linux support with Vulkan rendering.