|
FAQs covering :-
|
||
|
Click to view FAQs for listed subject |
Click to view FAQs for listed tool |
Toolbox and access information |
|
|
|
Part of Facilities accessible via autoVoIP Blaster tree branch
|
|
Diagram showing the components in VoIP Pre
Deployment Assessment tool and deployment information
|
Video Tutorial information |
|
|
These Tutorials can be used to answer questions:-
|
||
| Fast access to key information |
Network and Deployment Information |
Remote Manager - Using Blaster Manager and Sink systems |
|
|
For use on all types of VoIP networks
|
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 :-
|
| FAQs covering Benefits |
|
|
| FAQs covering Installation, Licensing and Deployment |
|
Installation :-
Licensing :-
|
| FAQs covering Scalability |
|
|
| FAQs covering Software delivery, Software Updates and Software Release Contents |
|
Software delivery and updates :-
Software Release content and schedule :-
|
| FAQs covering Troubleshooting and Check lists |
|
Troubleshooting :-
Check lists:-
For more on Check lists/Reference Material and Evidence requirements - see FAQ - Troubleshooting Codima Toolbox
|
| FAQs on miscellaneous/linked subjects |
| Area |
|
VoIP Technology :-
Probes :-
|
|
Microsoft®
Patch level :-
|
Tutorials
Are there any tutorials to help me get started?
Yes - there is a tutorial to assist you in learning how to use the facilities available via the autoVoIP Blaster tree branch. It is accessible from the Help facility and from the Codima Website.
Click here to access the sign in page for the Tutorials:-
The tutorial is titled :-
- How to Stress Test Network Pre Deployment
Installation
Can I use Host Platforms with 64bit Operating Systems?
What Operating Systems can I use on the Host Platforms?
The Codima Toolbox will operate on platforms running the following Operating Systems
- Microsoft® Windows Vista, XP, Server 2003, Server 2008, Server 2008 R2 or Windows 7 with 2GHz CPU (minimum)
Toolbox includes 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 Platform that is generating the blaster
traffic. You can either use a separate Platform 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 Platforms Network Adapter(s) must be correctly configured and connected to the network to monitor and transmit traffic.
The Host Platform requirements are subject to the deployment option selected, see options below. Two Platforms are required and they should be tested Back to Back prior to installing on a live network to ensure they are able to handle the planned loading levels :-
- Option 1 - Blaster operation controlled from the site
- Option 2 - Blaster operation controlled from an external site
Click here to access information on the Host Platform requirements for the Codima Toolboxes.
It will include answers to the following questions :-
-
How much memory do I need to install?
-
How much disk space do I need?
-
What level of phone loading can Platforms typically provide?
Can I install the Codima Toolbox on the same host platform as the Codima Spider?
You can either install a Codima Spider Server or a Codima Toolbox. However you can have a Codima Toolbox with Web Access, that can act as a Codima Spider Server but still allow access on the Host Platform to the tools in the Codima Toolbox.
Components
What components do I need to install to use the VoIP Pre Deployment Assessment tool?
There are two components associated with VoIP Pre Deployment Assessment tool, they are the Blaster Manager and the Sink System.
You need to install Codima software on two distinct Host Platforms. One Platform sited at each end of the path under test. One acts as the Blaster Manager and the other acts as the Sink System.
Blaster Manager Host Platform - What is it used for?
The VoIP Pre Deployment Assessment tool requires a minimum of two Platforms to operate, one sited at each end of the path being stressed. The Blaster Manager Host Platform is used to configured and control the tests. It is sited at one end of the path and a Sink system is sited at the other end.
Deployment examples showing Blaster Manager Host platforms and Sink platforms.
The
Blaster Manager is
used to send out RTP frames based on user input to the Sink systems IP address
and send RTCP APP frames in response to RTP frames sent by
Sink system, it is
also used to send out extra loading to stress the link between the Blaster
Manager Host Platform and the Sink Platform.
Sink system - What is it used for?
This is the system that responds to the Blaster traffic, i.e., sends back RTCP reports.
The Host Platform used by the Sink system can be portable, allowing it to be moved to different points on the network.
For more information, see the VoIP Pre Deployment Assessment tool section of the :-
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:-
Licensing
How do I find the MAC Address of the Host Platform I wish to install on? - required to machine lock license.
The license files used by the tools in the Codima Toolbox are linked to the MAC Address of the Host Platform you install the software on. To obtain the MAC Address of a Platform 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 the Host Platform 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:-
How is the Toolbox licensed to run the functions accessible via the autoVoIP Blaster tree branch?
- BLASTER MANAGER or BLASTER REMOTE MANAGER
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 (standard), Pay as You Go is based on the phone loading undertaken during a calendar month.
-
SINK
This is the system that responds to the traffic from the Blaster Host Platform. Not machine locked.
So typically the user just needs a machine locked license for the Host Platform controlling the Blaster process, which is used in conjunction with a number of free Sink Systems.
Scalability
The are two issues that impact on loading capabilities:-
1. The number of concurrent phone calls you are allowed to configure in the Blaster Manager dialog
The License controls the maximum amount of loading you can configure from a single VoIP Pre Deployment Assessment tool
For example if you have a license that allows for 100 concurrent phones, you can set up a configuration designed to generate RTP traffic that is equivalent to the media stream associated with 100 continuous phone calls. This traffic can be targeted at :-
- A single Sink System* - loading equivalent up to 100 continuous phone calls down one path (e.g., traffic level incremented from say 10 phones up to the license maximum of 100 phones)
or
- Multiple Sink Systems* in parallel, e.g., 5 Sink Systems* - loading equivalent to up to 20 continuous phone calls down 5 paths (e.g., traffic level incremented from say 1 phones up to 20 phones on each path, which would meet the license maximum of 100 phones)
*Sink Systems are Host Platforms used by the VoIP Pre Deployment Assessment tool, they are used to define the "B" end of the paths being tested.
2. The capabilities of your Host Platforms
Successful operation will be subject to the Host Platforms memory speed, cache size and motherboard organization. The Network Interface will also be important, ideally that should be a high spec Gigabit Ethernet Network Adapter. Not a USB plug in Ethernet Adapter for instance.
It is essential that you test the Blaster Manager Host Platform and Sink Platform operation (Back to Back) in an isolated environment in advance of deployment on a live network to check their ability to connect and handle the planned loading levels. Back to Back testing provides a means of establishing the capabilities of Host Platforms:-
To scale this up, to cover situations where you require to generate higher loading, you can add additional VoIP Pre Deployment Assessment tools.
Software Delivery and Software Updates
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
This free software can only operate if you have a machine locked license for the BLASTER REMOTE MANAGER or BLASTER MANAGER
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 get the latest software version?
You should set up your Host Platforms so that they are 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
Getting Started
Yes, you have a check list that can be used as a reference document when using the VoIP Pre Deployment Assessment tool to stress test a path on a network.
-
Click here to obtain a hard copy of the Check list and Troubleshooting Guide - autoVoIP Blaster tree branch
There is also a help page that is very useful as a quick guide:-
Use <F1> to access the Help facility then search on Help entry titled
- How to stress test a network path
Other reference documents are :-
-
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.
Applications, Scope and Operations
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:-
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 Host Platform that is generating the blaster traffic. You can either use a separate Platform with the Toolbox installed or you can use other protocol analysis tools such as Wireshark®.
Yes, you can run tests over multiple paths in parallel and you can run tests over the same path using two different codecs and/or two different priority settings.
Display how Blaster Manager Platforms and Sink Platforms can be deployed to enable multiple paths to be tested in parallel:-
Display showing facility to set up a test that uses dual Codecs and Priority settings and the associated deployment diagram:-
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.
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.
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
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-
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 |
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
For information on traffic levels, see FAQ:-
What is Back to Back testing and why is it important?
Successful operation will be subject to the Host Platforms memory speed, cache size and motherboard organization. The Network Interface will also be important, ideally that should be a high spec Gigabit Ethernet Network Adapter. Not a USB plug in Ethernet Adapter for instance.
It is essential that you test
the Blaster Manager Host Platform and Sink Platform operation (Back to Back) in an isolated
environment in advance of deployment on a live network to check their ability to
connect and handle the planned loading levels. i.e., using just the Blaster
Manager Platform and Sink Platform and a single hub/switch.
You should also ensure:-
a) That the Switch port is running full duplex for the required line speed.
b) The Toolbox Host Platform shows upstream and downstream test results.
About checks - Check CPU loading during test, it should not exceed 70%
CPU in System Manager when test reaches maximum point.
The limits found for the Platforms when used in the direct Back to Back test should be
divided in half to get the safe loading levels for use on the live network.
For example if the limit identified when running Back to Back is found to be 300 phones (i.e., CPU loading does not exceed 70% when this level is used). Then the safe limit is 150 phones
The checks on the Blaster Manager Platform should apply to the sum of all the Blaster
tests you plan to run simultaneously from the Platform.
You need to check Blaster Manager Platform and the Sink Platforms as blaster tests operate
full duplex.
Why it is important -
Undertaking validation testing ensures that the Platforms being used to Host the
Toolbox can deliver the loading levels, and will mean that when the Blaster
tests are run on the live network any degradation is proven to be due to the
network and not the test platforms
It is important to also check the type of Switch used in the blaster path.
Switches can be blocking or non blocking. Blocking switches can drop packets at
high loadings due to backplane saturation. Be aware that certain Switches
automatically lock ports and stop transmission when loading levels are high.
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.
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 Host Platforms are needed :-
- BLASTER MANAGER PLATFORM – This is used to send out RTP frames based on user input to the Sink systems IP address and send RTCP APP frames in response to RTP frames sent by Sink Platform, it is also used to send out extra loading to stress the link between Blaster Host Platform and Sink Platform
- SINK PLATFORM – Remote end, is used to respond, i.e., send back RTCP reports to the Blaster Host Platform, and send out RTP frames to the Blaster Host Platform.
Option 2 - A minimum of three Host Platforms are needed* :-
- BLASTER MANAGER PLATFORMS – This is used to send out RTP frames based on user input to the Sink systems IP address and send RTCP APP frames in response to RTP frames sent by Sink Platform, it is also used to send out extra loading to stress the link between Blaster Host Platform and Sink Platform
- SINK PLATFORM– Remote end, is used to respond, i.e., send back RTCP reports to the Blaster Host Platform, and send out RTP frames to the Blaster Host Platform.
- BLASTER REMOTE MANAGER PLATFORM : 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 systems and for the duration of a test run will assign a Sink system to the role of Blaster Manager.
*Note: Alternatively you can use remote control software such as Logmein® or TeamViewer® to access and control the Blaster Manager Host Platform.
For more information on deployment options (including diagrams), see :-
What are the Benefits of using the VoIP Pre Deployment Assessment Toolbox?
-
It is one of the most scalable pre installation products available for IP Telephony on the market today.
-
Paths on the network can be tested simultaneous using peer to peer or star configurations. Different loading levels and tests can be applied to individual paths.
-
-
Gives the Engineer the information he needs to ensure the phone deployment will not exceed the carrying capacity of links and starve data traffic.
-
Establishes the acceptable Phone limit for the path under test. Checks for any unacceptable QoS deterioration as the Phone loading levels are gradually increased – for voice traffic the user has to have an acceptable QoS.
-
-
Tests are run in real-time on the live network.
-
Uses real RTP frames, shows real results, shows impact of phone loading on network over a 7 day period 24/7.
-
-
All the tests you need to run to check if your network is ready for VoIP are already logically grouped together and ready to implement.
-
Uses an automatic process that varies the phone loading, tests the limits by using a stepped packet rate.
-
Operating full duplex to monitor QoS upstream and downstream simultaneously.
-
User can select to test using different Codecs to allow the effect of using different packet sizes to be examined in a single test.
-
User can select to test using different Priorities (Diff Serv values) to allow for VoIP and non VoIP loading to be sent at the same time, useful when testing green field sites.
-
-
Includes safety features.
-
Has an automatic cut off based on number of frames reported as lost during the user defined loading. The scope of the test is automatically adjusted so it continues operating to identify the acceptable phone loading limit for the path under test.
-
User has control off resting period between the loading steps, to allow network to recover from earlier loading level.
-
-
Saves time by running tests in Parallel.
-
Saves time as reports are automatically generated in a pre-formatted Microsoft Word® document to enable collaboration and information sharing.
-
Integrated with Expert System (Automated Correlation Engine).
-
Bottlenecks caused by the extra phone loading can be identified on the network
-
For more information review the Features and Benefits Video Tutorial for the VoIP Readiness Toolbox:-
Click here to access the sign in page for the Tutorials:-
or click here to obtain a copy of the VoIP Readiness Toolbox Features and Benefits list.
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 are user configurable. See FAQ entry titled:-
Example covering Traffic volume when sending loading equivalent to 10 continuous phone calls using G711 codec:-
(PCMU) G711 = 87.2 Kbps (headers included) X 10 (number of phones)) = 872.Kbps
Example covering Traffic volume when incrementing Phone Loading in steps of 10 phones
The VoIP Pre Deployment Assessment tool operates by increasing loading in user defined steps and repeating the cycle of steps over the duration of the test run, so you can get results covering QoS achieved for each loading level.
For 5 steps, incrementing by 10 phones per step it would be:-
G711 = 87.2 Kbps (headers included) X 10 (number of phones)) = 872 Kbps
G711 = 87.2 Kbps (headers included) X 20 (number of phones)) = 1744 Kbps
G711 = 87.2 Kbps (headers included) X 30 (number of phones)) = 2616 Kbps
G711 = 87.2 Kbps (headers included) X 40 (number of phones)) = 3488 Kbps
G711 = 87.2 Kbps (headers included) X 50 (number of phones)) = 4360 Kbps
Display example showing configuration for 5 steps -
Which ports have to be open to allow communication with a Sink system?
The ports used for the dialogs between the Blaster Manager Host Platform and the Sink Platform associated with setting up and running the VoIP Pre-deployment test are listed in the Troubleshooting Guide and Check list.
- Click here to obtain a hard copy of the Troubleshooting Guide and Check list - autoVoIP Blaster tree branch
- Reports
Yes, you can obtain sample HTML reports, the sample reports are available to authorized resellers of the Codima Toolbox.
What kind of reports are available to show results of stress testing?
A VoIP Pre-deployment report is provided as a Microsoft Word document.
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.
- Probes
Can I use Probes as Sink systems?
The use of Codima Toolbox Probes as Sink systems is not recommended.
For information on the Sink systems, see:-
For information on Remote Management and Probes, see
- VoIP Technology :-
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 may be modeled mathematically from Codec, %loss/delay to predict - OBJECTIVE QoS
MOS (mean opinion score : standard - P80) is a Metric intended to convey User Experience of Phone Conversation in a single number
Yes, click below to obtain Check list/Troubleshooting Guide:-
- VoIP Pre Deployment Assessment :Check list and Troubleshooting Guide - for facilities accessible via the autoVoIP Blaster Tree branch
How will the Toolbox handle Firewalls?
Toolbox Host Platforms and network firewalls need to be unblocked to allow the applications to run correctly, this is covered in the Check list. Click below to obtain Check list/Troubleshooting Guide:-
- VoIP Pre Deployment Assessment :Check list and Troubleshooting Guide - for facilities accessible via the autoVoIP Blaster Tree branch
Click below to obtain a hard copy of the evidence requirements for the Toolbox.
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
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.
How do I interpret the information in the Report?
The SLA graphs provide the most relevant information. For a test to be classed as successful - the SLA display should be green for the entire bar. As soon as you start to get any amber or red in a bar you know the call quality would be adversely effected by the associated loading. I will use the example below to explain the results being showing there.
Excerpt from Report
You are NOT emulating actual phone calls, there is no call set or clearance involved. You are sending out a stream of RTP traffic that is effectively equivalent to continuous calls from the number of phones associated with each of the loading step. You are testing the networks ability to handle the loading over time. This example shows the results of testing both the upstream link and the down stream link (loading is applied to both directions). Each bar in the graph display is a step in the loading cycle, for this test 20 steps were used (the loading applies to continual cycles of 15 seconds of packet transmission followed by 15 seconds resting for the entire duration of the test). The amount of traffic sent will be subject to the Codec used in the test, for example G.711 = 87.2 Kbps (when you include headers), so that would be multiplied by the number of phones you have selected to load at each step.
RESULTS DISPLAYED IN ABOVE GRAPH
-
Upstream testing - When loading gets to 250 phones, the SLA band stops being entirely green indicating the limit for phone loading on that link.
-
Downstream testing - When loading get to just over 250 phones, the SLA band stops being entirely green indicating the limit for phone loading on that link.
More guidance on interpreting reports
For more guidance on interpreting the reports you should refer to Appendix 9 of the Check List and Troubleshooting Guide
- Click here to obtain a hard copy of the Check list and Troubleshooting Guide - autoVoIP Blaster tree branch
Check Host Platforms prior to running tests
It is also important to make sure is that the Host platforms being used in the tests have no issues with generating loading at the higher phone levels. This is to ensure that the results are network specific and not an indication that the Host Platforms are struggling. This is why it is really important to do back to back testing with the kit to validate blaster operation before using it on a live network. See Appendix 8 of the Check list and Troubleshooting Guide for detailed information on this subject :-
-
Click here to obtain a hard copy of the Check list and Troubleshooting Guide - autoVoIP Blaster tree branch
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
-
Window Server 2008 SP1
-
Windows 7
Copyright/Disclaimer
Copyright ©2011 Codima Inc. All Rights
Reserved.
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