VoIP Traffic Analysis. Break through your data

Size: px

Start display at page:

Download "VoIP Traffic Analysis. Break through your data"

Olivia Banks
10 years ago
Views:

1 VoIP Traffic Analysis Break through your data

We have ACD and ASR, what is missing? Traffic analysis module includes several advanced tools to help you understand what is happening in your network: Call histograms by duration second/minute.

2 We have ACD and ASR, what is missing? Traffic analysis module includes several advanced tools to help you understand what is happening in your network: Call histograms by duration second/minute. Call histograms by PDD, TTC, TTR second. Disconnect code statistics per every object of the switch. Route priorities, ranked by any single parameter or a formula including several parameters. Source number areas statistics. SRC/DST numbers statistics. Please add a new screen Traffic analysis to start working with the module.

by duration second/minute. Call histograms by PDD, TTC, TTR second. Disconnect code statistics per every object of the switch.

3 Call histograms by duration second A histogram is a distribution of calls by their duration over a given time period. A good histogram would look like the one on the left. Each number on the X axis represents a duration second, and on the Y you can see how many calls, %-wise, were ended at this very second compared to the peak. If calls are ended based solely on human behaviour, a histogram will be close to a normal, Gaussian-like distribution with a smooth curve climbing up to a single peak, and then gradually declining as calls durations grow. This histogram, however, still has 2 small irregularities at seconds 33 and 82.

Each number on the X axis represents a duration second, and on the Y you can see how many calls, %-wise, were ended at this very second compared to the peak.

4 Call histograms by duration second A histogram shaped weirdly calls for an investigation. Here is an example of a histogram that was definitely not formed by human decisions on when to end the calls. Each peak represents a machine decision to end a higher than usual number of calls at a certain duration. Such peaks could indicate a FAS from some of your vendors, or timers on customer's side (for instance, if a call stayed in a queue of a call centre for too long, and was dropped), or could be some of your softswitch timers (say, ending a call with no media after X seconds). A histogram wont tell you why it has a shape like this, but it may alert you that something is not right in your network.

Each peak represents a machine decision to end a higher than usual number of calls at a certain duration.

5 Call histograms by duration second We have a bad histogram of total calls, what is next? If a histogram has harsh peaks, there are only 3 main reasons for this: 1. A vendor is disconnecting a lot of calls at certain seconds. 2. A customer is disconnecting calls at these seconds itself. 3. Your switch is disconnecting these calls. The third case is the easiest to investigate you may randomly check histograms for 3 of your customers and 3 of your vendors, and if you see the same peaks everywhere this is your switch.

A vendor is disconnecting a lot of calls at certain seconds. 2. A customer is disconnecting calls at these seconds itself. 3.

6 Call histograms by duration second How to find bad vendors/customers? There are 3 new parameters in reports: 1. In Hr Max sec - the second that had the maximum number of calls with this duration during each hour. 2. In Hr Max% sec - the ratio of the number of calls per the maximum duration second to the average number of calls per duration second in each hour. 3. In Hr Rough sec - the roughness of the histogram chart. Here is a 4-hour report on all vendors on the left. Normally, every hour would have a different max second. If the max second is same over several hours this vendor is giving us a peak. The chart on the left shows a histogram for a vendor with max second = 62 in every single hour. Please refer to the Manual for a description of 2 other parameters.

In Hr Max% sec - the ratio of the number of calls per the maximum duration second to the average number of calls per duration second in each hour. 3.

7 Call histograms by PDD, TTC, TTR second A histogram can also be built for PDD or other parameters. This is a histogram of non-connected calls rejected at a certain second (parameter TTR Time To Reject). We can see that, first, this vendor takes too much time to reject most of the calls, second, an abnormally high number of calls are rejected at seconds 7 and 8, 8 and third, too many calls are rejected at second 60, and all seconds over 60 (last bar on the left). PDD, TTC and TTR histograms may help investigate FAS, unwanted timers, and other issues.

We can see that, first, this vendor takes too much time to reject most of the calls, second, an abnormally high number of calls are

8 Disconnect code statistics This module adds detailed disconnect code statistics (ID starting with r for Reason ) per every object or combination. Possible combinations: Customer->Reason, Vendor->Reason, Area->Reason, Customer->Area->Reason. Disconnect codes can also be viewed in charts.

9 Route priorities Routes for each Destination area can be prioritized using real-life statistical data over a period of up to 4 weeks.

Route priorities Usually, carriers set route priorities using cost (LCR) or profit. 5gVision, in addition to calculating priorities by any single parameter cost/min, profit/min, ACD, ASR, etc.

10 Route priorities Usually, carriers set route priorities using cost (LCR) or profit. 5gVision, in addition to calculating priorities by any single parameter cost/min, profit/min, ACD, ASR, etc., allows use of formulas to get the best performing, while still not too costly, routes on top. In the example above, routes are ranked by a Total Quality Indicator, using a formula: ACD * ASR * profit. Indeed, if we are getting 1000 calls from a customer, sending them to a route with higher ACD and ASR, but a lower profit per minute may result in us making more money. One can also set filters like Connected calls > 500 over a period analyzed, or ACD > 3 min. to exclude vendors that did not get enough traffic, or were performing too poorly.

, allows use of formulas to get the best performing, while still not too costly, routes on top.

11 Source areas statistics Source areas are much like Destination areas, but are determined using Source, not Destination numbers. Source areas statistics may be valuable if you would like to know where the customers, calling your switch, are from. Source areas names and codes may be different from Destination areas, and can be loaded separately. Unlike Destination areas, object combinations, like Customer->Area->Vendor are not calculated for the Source areas. Source areas object IDs start with b (Destination areas start with a ).

Source areas names and codes may be different from Destination areas, and can be loaded separately.

12 SRC/DST numbers statistics This module collects connected calls, ACD, and some other parameters for the actual numbers, not areas. Such statistics may be valuable if you would like to identify numbers that are calling your switch, or are being called too often, or numbers that are calling too many different areas (which, for retail service providers, may ask for an investigation).

Such statistics may be valuable if you would like to identify numbers that are calling your

13 Thank you for your time If you wish to request a fully functional trial, please contact: Skype: Web: [email protected] support_5gfuture

Route-Testing Auto Dialer

Route-Testing Auto Dialer Dialer Overview What is a dialer? The route testing dialer is a software module that lets you test quality of routes provided by your vendors by automatically dialing certain