VOIP Calls Need Strong Privacy Protection

Published: Dec 28, 2007
Updated: Feb 2, 2021
2 minute read
eWeek content and product recommendations are editorially independent. We may make money when you click on links to our partners. Learn More

Just before Christmas I had a chance to catch up with Network Instruments on Dec. 12. Our subject was the GigaStor network analysis family of tools. I’ve been impressed with the quality of Network Instruments tools and network analytics for some time. But today, as I look over my notes, I’m struck by the erosion of privacy in the workplace and at home with every network analytics advance.

Starting with my first test of a VOIP system, I’ve wondered what wiretap rules would apply to these types of telephone calls. From what I’ve seen, e-mail “acceptable use” policies have made it pretty clear that in the United States employees using company networks and computers can have no expectation of privacy in their written, electronic communication. Many of these policies are being applied to VOIP calls. After all, both e-mail and voice communication end up as data packets on the network, no different technically from any other application.

When I first entered the work force and got a phone that could make direct-dialed, long-distance calls (I started in tech support) I saw how phone records were used to enforce acceptable rules. Then, the president’s admin assistant would look over the monthly phone bill and search for long call times or suspicious area codes.

Network sniffers have had for some time now the ability to capture and replay a VOIP call. Network Instruments demonstrated an ability to retain the packet data needed to troubleshoot connectivity or call quality problems without saving the actual call payload. Even so, for the most part, it’s up to the scruples of the network technician to skip listening in on the actual telephone conversations that can be saved and replayed by network analysis tools.

I think it’s time to make it clear that telephone calls are a special form of communication that should be protected from eavesdropping. It should be mandated in law and become part of the generally accepted practice of network engineers to put the content of voice calls strictly off-limits. The settled practice of monitoring call origin, destination and length should be enough to ensure the acceptable use and effective troubleshooting of VOIP calls.

Cameron Sturdevant

Cameron Sturdevant

Content Writer

Cameron Sturdevant is the executive editor of Enterprise Networking Planet. Prior to ENP, Cameron was technical analyst at PCWeek Labs, starting in 1997. Cameron finished up as the eWEEK Labs Technical Director in 2012. Before his extensive labs tenure Cameron paid his IT dues working in technical support and sales engineering at a software publishing firm . Cameron also spent two years with a database development firm, integrating applications with mainframe legacy programs. Cameron's areas of expertise include virtual and physical IT infrastructure, cloud computing, enterprise networking and mobility. In addition to reviews, Cameron has covered monolithic enterprise management systems throughout their lifecycles, providing the eWEEK reader with all-important history and context. Cameron takes special care in cultivating his IT manager contacts, to ensure that his analysis is grounded in real-world concern. Follow Cameron on Twitter at csturdevant, or reach him by email at cameron.sturdevant@quinstreet.com.

eWeek Logo

eWeek has the latest technology news and analysis, buying guides, and product reviews for IT professionals and technology buyers. The site's focus is on innovative solutions and covering in-depth technical content. eWeek stays on the cutting edge of technology news and IT trends through interviews and expert analysis. Gain insight from top innovators and thought leaders in the fields of IT, business, enterprise software, startups, and more.

Property of TechnologyAdvice. © 2026 TechnologyAdvice. All Rights Reserved

Advertiser Disclosure: Some of the products that appear on this site are from companies from which TechnologyAdvice receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. TechnologyAdvice does not include all companies or all types of products available in the marketplace.