FAQs - autoVoIP Blaster tree branch

 Remote Manager - Using Blaster Manager and Sink systems

  FAQ index for Codima Toolbox

Part of

  • Codima All in One Toolbox

  • Codima VoIP Readiness Toolbox

Tools covered in this FAQ page include :-

  • VoIP Pre Deployment Assessment tool

 

The Remote Manager tool is included in all the Codima Toolboxes, it is used to view and in some cases control Remote systems. These remote systems can be Sink systems that are designated as Blaster Managers for the duration of the test run, for more information, see the VoIP Pre Deployment Assessment tool section of the :-

 

 
Click to access FAQs. Fast access to key information
 

 

 

 
The functions accessible via the autoVoIP Blaster tree branch need to send traffic to different destination IP addresses on the network. The traffic is sent to the:-

 
Notes - For use on all types of VoIP networks

 

   FAQ Index - autoVoIP Blaster tree branch

 

Area

Question
Background Information :- General information :-
Installation, Licensing and Deployment :-

 

 

 

 

 

 

Installation :-

How much memory do I need to install?

How much disk space do I need?

Licensing :-

Deployment :-

Software delivery :-

 
Getting Started

Operation :-

 
Software Updates :-

 

 Update Service :-
Reports :-

 

        - includes information on VoIP Predeployment Report

Scope/Applications :-

 
Support/Troubleshooting :-

For Check lists/Reference Material and Evidence requirements - see also FAQ - Troubleshooting Codima Toolbox

 
VoIP Technology :-

 

Microsoft® Patch level :-  

 

 

 

 FAQs and answers

 

Background Information:-

 

What is the autoVoIP Blaster tree branch used for?

 

The functions accessible via the autoVoIP Blaster tree branch:-

 

•   Are used to provide controlled loading - for example to measure the impact of the loading associated with adding more phones.

•   Can be used to test two different Codec at the same time - this allows the effect of different packet sizes associated with different Codec to be examined in a single test

•   Can be used to test two different Diff Serv values at the same time - this allows for VoIP and non VoIP loading to be sent at the same time

 

They enables users to identify the loading level where the QoS is not acceptable. The Toolbox provides a VoIP Pre Deployment Test Report that consists of a Test Period Summary report showing the test results for the different phone loading levels used during the Test period, covering Jitter, % Lost frames, R and MOS values for the upstream and downstream links and the round trip delay and a set of 7 day reports broken down per hour showing the MOS and R values achieved during the test for the upstream and downstream links.

 

Deployment Options:- 

There are two options for deployment:-

  • Option 1 - Blaster operation controlled from the site
  • Option 2 - Blaster operation controlled from an external site

Option 1  - A minimum of two PC platforms are needed :-

  • BLASTER MANAGER PC – This is used to send out RTP frames based on user input to the Sink PCs IP address and send RTCP APP frames in response to RTP frames sent by Sink PC, it is also used to send out extra loading to stress the link between Host PC and Sink PC 
  • SINK PC – Remote end, is used to respond, i.e., send back RTCP reports to the Host PC, and send out RTP frames to the Host PC.

Option 2 - A minimum of three PC platforms are needed :-

  • BLASTER MANAGER PC – This is used to send out RTP frames based on user input to the Sink PCs IP address and send RTCP APP frames in response to RTP frames sent by Sink PC, it is also used to send out extra loading to stress the link between Host PC and Sink PC 
  • SINK PC – Remote end, is used to respond, i.e., send back RTCP reports to the Host PC, and send out RTP frames to the Host PC.
  • BLASTER REMOTE MANAGER PC : Required if you wish to manage the Blaster Process from out side the customers network, one system can be used to control all the Blaster Managers on multiple customer sites. The Blaster Remote Manager uses multiple Sink PCs and for the duration of a test run will assign a Sink PC to the role of Blaster Manager.

 

For more information on deployment options (including diagrams), see :-

 

 

What is a Sink system?

 

This is the system that responds to the Blaster traffic, i.e., sends back RTCP reports.

 

The PC platform used by the Sink system can be portable, allowing it to be moved to different points on the network.

 

See deployment option 1

 

Downloading Sink Software

 

The installation instructions provided in the Toolbox license delivery email provide you with the url to use to obtain a copy of this software.

 

For more information, see FAQ entry titled:-

 

 

Can I use Probes as Sink PCs?

The use of Codima Toolbox Probes as Sink Systems is not recommended.

For information on the Sink PC, see:-

For information on Remote Management and Probes, see

 

 

Reports

 

What kind of reports are available to show results of stress testing?

 

A VoIP Pre-deployment report is provided as a Microsoft Word document. 

 

VoIP Pre-deployment Report?

 

This is a user Report providing the results of the Pre-Deployment Test which was used to establish:-

• What the Phone limits are
• What the impact would be when using different Codecs and Priority settings.
 

The report is built automatically using a word document template, which can be changed to include different company logos and text.

The text used for example could be in your local language.

 

Can I see example Reports?

 

Yes, you can obtain sample HTML reports, the sample reports are available to authorized resellers of the Codima Toolbox.

 

 

 

Software Updates :-

 

How do I get the latest software version?

 

You should set up your PC platform so that it is able to access to the Web. Then you can use the Automatic Installation Update facility. This will automatically tell you if there is an update to the system available. You will also need to be authorized to receive updates.

 

You can also use the Help Menu, where the option Check for Updates will open a Web page listing the available updates, which you can select to download.

 

For more information see Help entry titled:-

  • How to upgrade Software

 

 

 

Scope/Applications

 

Can I use the functions accessible via the autoVoIP Blaster tree branch on any VoIP network? - H323, SIP etc

The functions accessible via the autoVoIP Blaster tree branch operate solely using RTP/RTCP frames and as such can be used on any VoIP network to test QOS.

 Can I create loading levels equivalent to multiple groups of phones at different network locations? 

Yes , you can run multiple Blaster tests in parallel. For more information, see the VoIP Pre Deployment Assessment Tool section of the:-

 

What kind of stress testing can I do?

The stress testing functions accessible via the autoVoIP Blaster tree branch are:-

  • Used to provide controlled phone loading – this measures the impact of adding more phones.
  • Used to test two different Codec at the same time - this allows the effect of different packet sizes associated with different Codec to be examined in a single test
  • Used to test two different Diff Serv values at the same time - this allows for VoIP and non VoIP loading to be sent at the same time
     

What Codec support is provided?

The functions accessible via the autoVoIP Blaster tree branch, allow you to undertake stress testing using a number of Codecs and additional Codecs can be added to the system easily. We just need to know the parameters used in the R or MOS value formula.

The support includes:-

  • PCMu
  • PCMa
  • G723-8k
  • G726-16
  • G728
  • G729 - 8k
  • RTA8

See below for more information on Voice Codecs

Voice Codec

Codec is a piece of computer hardware or software used for the compression and/or decompression of digital media (most usually audio or video). QoS may be modeled mathematically from the Codec.

Here is a list of some of the voice codecs standards:-

Codec Algorithm Bit rate (K bits per second) Notes
G.711 PCM 64, 56 A ITU (International Telecommunications Union) standard for a narrow-band audio codec that encodes speech into a stream of 8 bit samples (or less frequently 7 bit samples) at 8khz. This creates a data stream at either 64kbps or 56kbps. G.711 uses a logarithmic mapping that emphasizes the parts of the signal that the human ear is most sensitive to. Uses pulse code modulation

There are two variants of G.711-

  • uLaw - Used with T1 and J1 connections
  • aLaw - used with E1 connections (Europe and Australia)

High quality, high bandwidth
G.723.1 ACELP 5.3 A ITU standard for a narrow-band audio codec that encodes speech into a stream of data frames that each represents 30ms (240 samples) of speech data. Each frame can be either 24 or 20 bytes long, which makes the data stream either 6.4kbps or 5.3kbps.

License fee to use this Codec commercially. 

Lower quality and < 10% of bandwidth used by G.711

(Less bandwidth = more delay)

Uses MP-MLQ (Multi-Pulse Maximum Likelihood Quantization)
G.723.1 MP-MLQ 6.3
G.726 ADPCM 40, 32, 24, 16 A ITU standard for a narrow-band audio codec that encodes speech into a stream of 2, 3, 4, or 5 bit samples - data stream = 16kbps, 24kbps, 32kbps, or 40kbps. 

Uses ADPCM (Adaptive differential pulse code modulation.
G.728 LD-CELP 16 A ITU standard for a narrow-band audio codec that encodes speech into a stream of 10 bit frames that each represent 5 samples - data stream  = 16kbps. License fee to use this Codec commercially. 

Uses LD-CELP ( Low-delay code excited linear prediction)
G.729 CS-ACELP 8 A ITU standard for a narrow-band audio codec that encodes speech into a stream of data frames that each represent 10ms (80 samples) of speech data. Each frame is 10 bytes - data stream = 8kbps. License fee to use this Codec commercially. 

Uses CS-ACELP (Conjugate-structure algebraic-code-excited linear prediction speech coder)
GSM 06.10 PCM 13.2

A narrow-band audio codec that encodes speech into a stream of data frames that each represent 20ms (160 samples) of speech data. Each frame is 264 bits, giving a data stream of 13.2kbps.

RTA 8 MS-RTA Supports bit-rates of 8.8 kbps at 8 Khz and 18 kbps at 16 Khz Based on MS-RTA codec from Microsoft Optimized ASM/C implementation C-callable APIs Bit-exact with all Microsoft provided test sequences.

Supports little-endian and big-endian mode of operation (C64x+).

Supports packet loss concealment. Support for direct-mode and pull-mode operations.

Optional support for xDM APIs

  

Installation

What are the PC Platform Requirements for Toolbox when using the functions accessible via the autoVoIP Blaster tree branch?

 

The PC requirements are subject to the deployment option selected:-

  • Option 1 - Blaster operation controlled from the site
  • Option 2 - Blaster operation controlled from an external site

 

Click here to access information on the PC platform requirements for each of the Tools in the Codima Tools box

 

The information provided covers the PC platform requirements for these PCs. It will include answers to the following questions :-

 

  • How much memory do I need to install?
  • How much disk space do I need?

 

 

 

What operating Systems can I use?

Can I use a 64bit Operating System?

 

The Codima Toolbox will operate on platforms running the following Operating Systems

  • Microsoft Windows 2003 Server®

  • Microsoft Windows XP®

  • Microsoft Vista®

  • Microsoft Windows 7®

 

Toolbox uses WinPCap drivers (used for frame capture) that support 64bit Operating systems.

 

 

What configuration is required to monitor VoIP traffic?

 

If you wish to monitor the frames being sent and received by the Toolbox when using the functions accessible via the autoVoIP Blaster tree branch, you will need to use an independent system, i.e., you can not use the Passive Analysis tool (i.e., functions accessible via the autoAnalyzer tree branch) on the same PC platform that is generating the blaster traffic. You can either use a separate PC with the Toolbox installed or you can use other protocol analysis tools such as Wireshark®.

 

However if you just want to view other network traffic, you can configure and deploy the Toolbox for passive and active options. See :-

The Host PCs Network Adapter(s) must be correctly configured and connected to the network to monitor and transmit traffic.

 Licensing

How is the Toolbox licensed to run the functions accessible via the autoVoIP Blaster tree branch?

  1. BLASTER MANAGER PC or BLASTER REMOTE MANAGER PC

This is the system used to configure the Blaster it also provides a console to view the results. It will require a machine lock license, the license files cover the following :-

Toolbox License (File name = LICENSE.TXT)

The Toolbox License controls the following:- 

  • Toolbox structure, e.g., VoIP Readiness Toolbox

  • Expiry date

  • MAC Address used to machine lock the software

  • Software Release Version, e.g., 7.20

  • Phone Loading Limits

  • Type of License, i.e., Pay As You Go or perpetual, Pay as You Go is based on the phone loading undertaken during a calendar month.

  1. SINK PC

This is the system that responds to the traffic from the Blaster Host PC. Not machine locked.

So typically the user just needs a machine locked license for the PC controlling the Blaster process, which is used in conjunction with a number of free Sink Systems.

 

 

Software downloads

URLs to download software for all the components that are needed to run the functions accessible via the autoVoIP Blaster tree branch are provided in the installation instructions attached to the license delivery email.

Should you need to obtain more copies of the free Simulator Sink software you can use the url below:-

SOFTWARE FOR SINK PC 

 

 

This free software can only operate if you have a machine locked license for the BLASTER REMOTE MANAGER PC or BLASTER MANAGER PC

When installing and operating this tool you should refer to the Trouble Shooting Guide and Check list - autoVoIP Blaster tree branch, see FAQ entry titled:-

 

 

How do I find the MAC Address of the PC I wish to install on?

 

The license files used by the tools in the Codima Toolbox are linked to the MAC Address of the PC you install the software on. To obtain the MAC Address of a PC you should type  ipconfig/all from a DOS window.

 

The MAC Address is a 12 digit hex number, e.g., 00-07-E9-5A-77-DB

 

To get to a DOS window, click Start, then Run, then type cmd in the text box.

If PC has multiple MAC Addresses, you need only to supply one for the license link.

 

DOS Window example:-

 

Alternatively you can make use of the automated facility to request a license upgrade, this facility automatically finds your MAC address.

 

Display showing interface used to request license upgrades:-

  

 

 

 

Operations

 

 

What type of Traffic is sent out on to the network when you use the functions accessible via the autoVoIP Blaster tree branch?

The Toolbox (when using the functions accessible via the autoVoIP Blaster tree branch) uses real RTP - the voice payload, the volume of traffic, the Codec and Priority settings (Tos - Diff Serv) used in the frames will be user configurable, see FAQ entry titled:-

 

Can I monitor the Traffic being sent out by the Toolbox when using the functions accessible via the autoVoIP Blaster tree branch?

If you wish to monitor the frames being sent and received by the Toolbox while using the functions accessible via the autoVoIP Blaster tree branch, you will need to use an independent system, i.e., you can not use the Passive Analysis tool (functions accessible via the autoAnalyzer tree branch) on the same PC platform that is generating the blaster traffic. You can either use a separate PC with the Toolbox installed or you can use other protocol analysis tools such as Wireshark®.

 

Getting Started

 Is there any guidance available to help me get started when using the functions accessible via the autoVoIP Blaster tree branch ?

Yes there is, use the following reference documents:-

  • Getting Started Guide - autoVoIP Blaster tree branch - .pdf file

  • Operations Guide - autoVoIP Blaster tree branch - Power Point Presentation, the URL to access this guide is provided directly to sales staff/resellers on request.

 

There is also the following check lists:-

 

Can I have a check list to cover what is needed to successfully operate the functions accessible via the autoVoIP Blaster tree branch?

 

Yes 

 

 

 

How long can I run stress testing?

 

There is not set limit for stress testing. The Blaster report covers 7 calendar days. If you run the blaster for longer than a calendar week for example or start it mid week, you can still get 7 days worth of information. The system will run continuously until you stop it. So if for example it runs for two calendar weeks, then the statistics for Monday will be an average of the results of running the test over two Mondays.

 

 

 Support/Troubleshooting

How will the Toolbox handle Firewalls?

PC and network firewalls need to be unblocked to allow the applications to run correctly, this is covered in the Check list.

 

If I have problems using the functions accessible via the autoVoIP Blaster tree branch what evidence do I need to supply?

Click below to obtain a hard copy of the evidence requirements for the Toolbox.

 

What does it mean when the lower phone loading levels and the higher phone loading levels shows error SLA bands

It can mean that something (usually a Router) in the Blaster path cause contention issues between incoming and outgoing blaster streams.

For example the Router is overloaded and the packet buffer has not been cleared when the next loading cycle starts, i.e., the Router is overloaded following the highest loading test to such an extend that there is residual overload for the time period allocated to the lower loading levels - see Example 1

This effect will be more apparent on Routers as processing can easily backup and multiple memory pools may become exhausted. Additionally when packets are process switched by a single CPU, then traffic in/out is in contention for CPU time. Note: Software Version 6.4.8 has an enhancement that provides additional configuration options that can be used when Routers in the Blaster path cause contention issues between incoming and outgoing blaster streams

 

Switches by contrast, typically have simple hardware switched data paths and relatively simple queue overload patterns. The in/out paths are normally totally separate, especially if backplane is Non-Blocking - see Example 2

Note: Contention can occur for example when there are half duplex links, hubs, process switched low end Routers and possibly when there are firewalls, or when the network path utilizes NAT

Example 1 - Overloaded Router in the Blaster Traffic Path

Example 2 - Switch in the Blaster Traffic Path


 

To summarize if you get the kind of residual overload display shown in Example 1, then it indicates the Router can not cope with loading levels. To avoid showing the residual overload in the graph you should test with lower loading levels. In the case of Example 1, you could do loading up to 25 phones as that is when the problem begins, alternatively you can use the additional configuration options included in software version 6.4.8 to fine tune the Blaster operation.

Example 3 shows an environment where the Router is better able to cope with phone loading levels, the Router involved had time to process high loading before the time period allocated to the first loading level occurred again.

 Example 3 : Report display example where the Router is no longer overloaded when the next loading cycle starts.

VoIP Technology

What is meant by QoS?

This term applies to a system used to provide different prioritization levels for different types of traffic over a network. Protocols used to achieve the required quality of service, including the RSVP, VLAN Priority, IP DiffServ.

For example, VoIP or streaming Video should have a higher priority than Mail traffic, as the consequences of interrupting Voice traffic or streaming Video are more obvious than slowing down Mail traffic.

Four Key parameters to determine QoS are:-

  • §%Frame Loss - Rule of thumb < 1% OK -  A Codec Feature "Packet Loss Compensation" tries to fill in packet loss gaps with generally good effect
  • §Round Trip Delay - Less 175ms OK
  • §Codec - Vary from G.711 - high quality, high bandwidth 64k, to G.723 lower Quality but ONLY 10% of bandwidth so adds to Delay. Each Codec has its own ITU Mathematical Model parameters to predict MoS from the Packet Loss.
  • §Burstiness of Frame Loss - This is modeled mathematically by the Toolbox but not supported by RTCP, it is however in RTCP-XR.

 

QoS is subjective as measured by experimentation with human listeners - SUBJECTIVE QoS

QoS may be modeled mathematically from Codec, %loss/delay to predict - OBJECTIVE QoS

These two should be similar –That is the challenge of the Mathematical Model to predict subjective QoS accurately.
 
Codecs cope with Jitter by using a Time Delay Q called a Jitter Buffer. This imposes a delay but allows Jitter up to this maximum to be ironed out. Packets outside the delay are counted as LOST - Long QoS. Jitter buffers eat into the delay budget but are more robust to jitter (and subsequent packet loss). So recently Dynamic Jitter buffers are being used to auto adjust to actual Jitter and minimize delay.
 
Delay comes from the Codec, it is substantial for compressing Codecs like 723 (not 711) and serialising Voice Samples into a RTP Packet. Network Queues in routers (usually at Edge Router), Distance due to speed of Light/Electricity in cables.
 
So lots of interdependent things eat into the Delay Budget. Using a High Compression Codecs saves HUGE bandwidth but makes system more fragile and Network QoS dependent.
§

What are MOS and R values?§

MOS (mean opinion score : standard - P80) is a Metric intended to convey User Experience of Phone Conversation in a single number

§R-value (standard – G107) is an objective measurement calculated directly from measurements of packet loss, jitter and delay. It also has a strong correlation with the MOS value.

 

 

Microsoft® Patch level

What is the latest Microsoft® Patch level that the Codima Toolbox software been tested with?

The process of testing with Microsoft® patches is an ongoing one, latest level tested is as follows :-

  • Windows XP Service Pack 3

  • Windows 2003 Server SP 2

  • Windows Vista SP1

 

Toolbox FAQ Index - Click here to return to FAQ index
 

 

Copyright/Disclaimer

Copyright ©2010 Codima Inc. All Rights Reserved.
No part of this document may be copied or reproduced in any form or by any means without the prior consent of Codima Inc.
Information in this document is subject to change without notice and does not represent a commitment on the part of Codima Inc. Codima Inc. reserves the right to revise or change this document without obligation of Codima Inc. to notify any person of the revision or changes. Information in this document is believed to be accurate at the time of publication but no liability whatsoever can be accepted by Codima Inc. arising out of the use of this information. Also, this document could include typographical errors or technical inaccuracies.
Any trademarks or trade names owned or registered by any other company and used in this document are the property of their respective companies