VoIP and Predeployment Testing

steve_brown.jpgThis column is a little longer, but with the continual roll-out of new technologies like VoIP on to the network, I think the importance of the topic justifies the length.

Denise Dubie today in her column for NetworkWorld covered the issue of what has been termed Unified Communications - unified communications aim to blend voice, video, instant messaging and conferencing with presence, collaboration, messaging and calendaring (so think VoIP, IM, and any types of collaboration or web meeting software) - are expected to be responsible for an increase in network traffic over the next twelve months. The column was prompted by a Network General poll of their client base. The key findings:

“Network General’s survey found that nearly 80% of companies expect the network traffic from communications applications to increase over the next 12 months. In the past three months, three-quarters of the companies polled say, up to 25% of their network traffic consists of unified communications.”

The idea that demand for network bandwidth has been increasing due to these types of applications isn’t that earth-shattering. It’s more that as we roll out new technologies, whether VoIP, wireless, or any collaboration software, the importance of predeployment testing only increases. Doing a site survey and establishing performance benchmarks are an easy way to ensure that new technology roll-out go as smoothly as possible.

Site Surveys and Establishing Network Performance Benchmarks

Typically when implementing a new technology, such as VoIP, many network administrators take one of two approaches with VoIP. Many network managers install new technologies and then address performance problems as they arise. Others anticipate that the addition of VoIP will increase their bandwidth needs, and as a result upgrade their bandwidth capacity.

These steps, however, may not effectively address the potential VoIP problems. Deployment issues can cause users to resist using the new technology. In addition the disruption of VoIP services directly impacts the bottom line by halting business activities. Conducting a site survey before installing VoIP services, understanding your overall bandwidth demand and application performance, and establishing benchmarks for acceptable network performance are critical for determining how the network will handle the new VoIP traffic and identifying any changes that need to be made to effectively support VoIP communications.

An analysis tool that tracks, stores, and analyzes long-term activity will define what is considered normal for a particular VoIP environment. The insights on network and application performance gained from the initial survey site and by continual monitoring of the added VoIP traffic will help you to intelligently configure alarms on the monitoring tool to alert you when VoIP performance deviates from the norm. It is also important to maintain a database of call detail records (CDRs) from which you can generate reports for management or service providers.

Understanding overall network performance through site surveys and benchmarking is critical to being able to quickly identify anomalies, troubleshooting problems, and ensure the success of a VoIP installation. We have a really good white paper (PDF) that discusses VoIP monitoring and all of the factors involved to ensure a successful deployment.

Digg VoIP Predeployment Testing digg Bookmark Weather Services on del.icio.us del.icio.us Add VoIP Predeployment Testing to your Technorati Favorites technorati

8 Responses to “VoIP and Predeployment Testing”

  1. Common VoIP Myths « Network Observations Says:

    [...] 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. [...]

  2. Top Tips for Managing VoIP - Part 2 « Network Observations Says:

    [...] The more you know about your network, the better prepared you are to properly integrate VoIP. Conduct a site survey to review current WAN bandwidth levels, traffic flows, and existing switches for bottlenecks and [...]

  3. First monitoring then VoIP « Network Observations Says:

    [...] has a great white paper explaining the basics of VoIP monitoring and troubleshooting. For predeployment troubleshooting, I can point to blog posts that I have written as well as Network Performance Daily. I think a lot [...]

  4. Network Resolutions « Network Observations Says:

    [...] 2. Conduct predeployment network assessments before deploying any new technology. Whether for MPLS, IPv6, Wireless, or VoIP, simple site surveys and network assessments help you identify and avoid many potential performance headaches. Try to understand an application’s behavior and overall affect on the network before you deploy it through out the office. Read more tips on deployment. [...]

  5. VoIP Confidence and Concerns « Network Observations Says:

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

  6. Kristen Kiya Says:

    Site survey is not that all necessary, you just need to choose a provider who can offer best services at reliable rates. Just check the reviews about them in the market. Do they really offer the services or just take the money and disappear. There are many companies who offer voip services and gurantee to provide perfect solutions for using Voip, but they really dnt. So, be sure. Like you can go for packet8, iCallGlobe.com, and Vonage.

  7. Stephen Brown Says:

    The rule of thumb with pre-deployment assessments…if the VoIP solution you’re using adds any type of traffic to your network…you’ll want to understand through an assessment how it will impact your network. Otherwise, you’re asking for trouble.

    Choosing the VoIP provider, evaluating your network, possibly improving infrastructure…these are all a part of the VoIP implementation process. One is not more important than the other for success.

  8. Calculating VoIP Bandwidth Consumption « Network Observations Says:

    [...] first thing is to understand your network by baselineing performance and predeployment testing. Use an analyzer daily before deployment, to define normal network performance and understand [...]

Leave a Reply