VoIP Quality Assessment

From a Windows computer on the customer's network, browse to http://test.networkedvoice.com/VoipReadinessTestNodes/TestCreate?systemTenantId=1

and fill in the fields as described below. This must be run on a computer wired to the LAN - no wireless connections. It's best to run this on a computer that is not in use. If you do run the test on a PC that is in use by an employee, instruct the employee to not close the test application or reboot the PC for the duration of the test.

1. Set the Measurements Interval to the average length of the company's calls. If you don't know, use 3 minutes.

2. Set the Number of Channels as the maximum number of simultaneous calls at the company's office. Note that each channel will use ~80kbps of bandwidth.

3. The Max Measurements Duration fields define how long you want the test to run for. Generally, we reccomend this be run for the duration the office's business hours, but shorter tests can still provide useful information.

4. Enter your name.

5. Enter the customer's name, then click Start VoIP Readiness test. Two links will be generated:

Click the Download link to download the test client. This client will simulate voice traffic to and from our networks based on the parameters specified above. After downloading, run the test client. Make sure to 'Allow Access' if a Windows Firewall prompt displays.

You'll see a notification on the client when the test is complete. Click on the View Results link to analyze the test. Review the "SIP ALG", then "upload stream" and "download stream" results:

All 4 SIP ALG tests should be false. While the test client will not identify every SIP ALG, or RTP ALGs, any positive result here means the customer's firewall needs to be configured to disable SIP ALG.

Uptime should be 100%. MAX RFC3550 jitter should be under 100ms. Ideally, max packet loss should be under 1%. If all of these parameters are met for both the upload and download streams, the network can support VoIP traffic at this time.

If packet loss is over 1%, re-run the test. It's possible a transient network issue was responsible.

If you have any questions about the test, please send us the test ID - visible on the results page -and we can review the details.