autoVoIP™ Blaster
VoIP Stress Testing Tool

An essential VoIP stress testing tool, the autoVoIP™ Blaster provides Voice over IP capacity testing. A part of the autoVoIP™ Simulator suite, it allows you to answer the question: "At what point do things begin to break down or degrade in my VoIP network?"

autoVoIP™ Blaster sends out competitive and non-competitive traffic to see what the Quality of Service (QoS) would be for a single user when different levels of VoIP and non-VoIP traffic are present. Reports then show the impact of this extra traffic on the QoS for the simulated RTP traffic.

Key Stress Testing and QoS Measurement Features

• QoS analysis - at a glance, see if VoIP is within safe limits, marginal or likely to be seriously degraded (6 color bands used); Automatically checks the QoS engineering using a sophisticated VoIP stress testing load generation algorithm
• autoVoIP™ Blaster can be used to measure the effect of adding more phones to an existing VoIP system
• Distributed loading can be used to match the exact phone deployment together with independent QoS monitoring at each deployment cluster site
• Automatically explores the capacity and limits of the network, using autoCheck Mode it shows the QoS stress and degradation as traffic patterns are automatically explored
• Multiple autoVoIP™ Simulators/autoVoIP™ Blaster systems can be used to emulate groups of phones at different locations on the network and monitor the QoS

Loading VoIP Traffic

The load can be specified by phone or codec using easy to understand phone counts. Traffic Blaster supports a number of Codecs, including: G711 - 64k, G723 - 6.3k, and G729 - 8k. Additional codecs can be added to simulations.

VoIP traffic loading may also be specified as bandwidth or frame loading. The QoS is measured in parallel for all simulation sites on the network giving a true indication of the behavior of the whole phone deployment. The Codima Correlation Engine provides an expert system to analyze the QoS graphs.

Concluding Notes:

autoVoIP™ Blaster has a safety facility to ensure it does not send traffic out indefinitely. It runs for 8 hours unmanned, stops and can be restarted manually, locally or remotely, for another 8 hours run.

Results can be exported to HTML Reports.