Common VoIP Myths

By Stephen Brown

logo_voip2.jpgRecently our manager of sales engineering, Charles Thompson, gave a talk on popular misconceptions surrounding VoIP. I thought I would discuss the top three myths.

Myth #1: Running VoIP without Quality of Service is acceptable
When implementing VoIP administrators often fail to consider issues of contention. It is critical to have the ability to set precedence for VoIP traffic. Failing to do so, opens up the possibility of interference from other applications on the network known as contention. Contention leads to common VoIP performance problems including jitter and packet loss. Throwing bandwidth at contentions problems doesn’t solve the issue. Even a network with large bandwidth capacity can have poor call quality due to network contention.

You also need to set precedence appropriately for all connections that compose the VoIP call including call set-up and tear-down. A common mistake is to set highest precedence for the conversation and neglect the other components of a call.

Myth #2: No VoIP site survey is necessary
When implementing VoIP, one of two decisions is usually made. Rather than conducting a site survey, IT managers will either keep network conditions the same and add VoIP, or they may choose to upgrade their bandwidth capacity and then roll out VoIP. The choices lead to performance problems after the deployment. These problems result in poor call quality and users who become resistant to using VoIP. You can read more about detecting network problems through pre-deployment surveys in an earlier post.

Myth #3: Voice conversations are secure
End-users and network engineers may not consider the security ramifications of a hacker or any other user using a tool to not only capture but play back VoIP conversations. Higher-end VoIP systems may offer ways to encrypt the data, but lower-end products often do not. You’ll want to consider this before you purchase a solution. Second, VoIP traffic is usually most vulnerable on the LAN since Internet WAN traffic is typically routed through VPNs.

Additional VoIP Resources
Improve VoIP performance with monitoring – SearchNetworking.com
Know your network before implementing VoIP – Network World
Predeployment Testing – Network Observations
Network Instruments Observer and VoIP – Network Instruments
In-depth information on VoIP Performance Management – Network Performance Daily

6 Responses to “Common VoIP Myths”

  1. Common VoIP Myths | Says:

    [...] Article: http://networkinstruments.wordpress.com  tag this | permalink | trackback url Leave a [...]

  2. Top 3... make it Top 5 Common VoIP Myths » Developages - Development and Technology Blog Says:

    [...] Brown from Network Instruments, a relatively new blogger has a post describing common VoIP myths. He only has 3 though, so I’ll add a couple which I’ll [...]

  3. Redes Malladas » Blog Archive Algunos mitos sobre VoIP » Says:

    [...] este post que pretende desmitificar ciertos aspectos de la Voz IP. Muy bueno desde un punto de vista [...]

  4. Ashley Nichols Says:

    Your post is interesting. What sort of vendors can assist in the quality of service surveys? We’d like to implement VOIP in a unified way with our email and web conferencing – but have no idea where to start…

    We are trying to avoid upgrading our bandwidth as we are in a remote area of the country.

  5. VoIP Confidence and Concerns « Network Observations Says:

    [...] Deployment and Testing Managing VoIP in the Field Common VoIP Misconceptions Top VoIP [...]

  6. Monitoring Resources: Network Observations – The Network View Says:

    [...] Common VoIP Myths [...]

Leave a Reply