Adaptive Routing and Quality of Service

Setting up Adaptive Routing

Add Routing Criteria

Add a routing criterion for a destination group

 

Define Routing Criteria for Specific Connection

Tracking Connection Status

 

 

PortaBilling® allows you to automate the process for controlling the call quality which becomes increasingly important today. That is, if you want to evaluate acceptable vendors for terminating VoIP calls, there is no need to hire numerous human operators or network engineers, who will track and analyze the specific route. All you need is to implement adaptive routing model.

Setting up Adaptive Routing

The main idea of adaptive routing is to dynamically measure a vendor’s quality parameters, and adjust the routing priority accordingly. These quality requirements are predefined in the form of threshold parameters on the Routing Criteria page, and are then automatically applied to specific vendors. Any vendor who fails to satisfy your quality requirements will go to the “penalty box” – the very bottom of the routing list. This means that the system will try first to terminate calls using other carriers (with a good quality evaluation). However, if all of them fail or are unavailable, the “penalized” carrier will have a chance to terminate the call. It is still better to send a call via an inferior vendor than to have it fail completely.

 

Thus, if the quality requirements are applied, a carrier’s place on the routing list is determined not only by the route category, the assigned preference value, and the cost parameters (LCR model), but additionally by quality criteria.

Add Routing Criteria

1.      On the Main Menu page, in the Routing section, click Routing Criteria.

2.      On the Routing Criteria page, click add Add on the toolbar.

3.      On the Add Routing Criteria page, fill in the required information on the top:

o   Name – The logical name of the routing criterion for use within PortaBilling®.

o   Description – A description of the routing criterion.

o   Sampling Interval – The time interval for which statistics are computed. Smaller intervals will make the system “quicker” to notice any change in a vendor’s quality, but there is also a higher chance that a short-term problem on the vendor’s side (which can be fixed in a matter of minutes) will penalize his route for a relatively long period of time.

o   Destination Group Set – A set of destination groups you would like to use for more convenient quality criteria entry; later you can define the routing criteria for individual groups of this set.

 

4.      In the Criteria Defaults table, specify the initial default values to be applied for all routing criteria you will create next:

o   Minimum Calls – The minimal required amount of calls via a given connection for the statistics to be considered representative. If the number of calls is below the specified value, the quality parameters will not be matched against the threshold, and no routing adjustments will be made.

o   Penalty Time – The time interval for which a connection will be “penalized” (at the very bottom of the routing list) if a given vendor does not meet the quality criteria.

o   ASR (Answer Seizure Ratio) The number of successfully connected calls divided by the total number of call attempts.

o   Min PDD (Post Dial Delay) – Defines the minimum acceptable PDD (Post-Dial Delay), i.e. the time interval between the moment a connection request is sent to the vendor and the moment ring-back is received. Too low a PDD is suspicious, and in this case the vendor is probably doing “false ringing” to hide the long time it actually takes him to route the call.

o   Low PDD Calls, % – Maximum acceptable percentage of calls with a PDD below the specified value.

o   Max PDD – Defines the maximum acceptable PDD. Too high a PDD has a strong negative impact on your business, since during the delay time the end user hears only silence, and generally assumes that there is a problem with the service.

o   High PDD Calls, % – Maximum acceptable percentage of calls with a PDD above the specified value.

o   ALOC – An average length of call.

o   Profit per Minute – The aggregated profit, i.e. the difference between the actual charged amounts in your customers’ and vendors’ xDRs.

NOTE: The ASR, PDD, ALOC, PPM parameters require two values that define the warning and penalty thresholds, respectively.

5.      Click Adobe Systems Save.

 

RoutingCirteria1

 

After that, a title “Please add a Criteria definition for at least one Destination Group” and a new table appears on the page.

Add a routing criterion for a destination group

1.      On the Add Routing Criteria page, click add Add on the toolbar.

2.      Click the Destination Groups column header link to choose a group from a searchable list inside the pop-up window. You can access only groups that be belong to the set specified in the Destinations Groups Set option on the top of the page.

3.      Provide the quality parameters to be applied to your vendors. You need to provide to values for each parameter: warning and penalty thresholds.

o   ASR (Answer Seizure Ratio) – The number of successfully connected calls divided by the total number of call attempts.

o   Min PDD (Post Dial Delay) – Defines the minimum acceptable PDD (Post-Dial Delay), i.e. the time interval between the moment a connection request is sent to the vendor and the moment ring-back is received. Too low a PDD is suspicious, and in this case the vendor is probably doing “false ringing” to hide the long time it actually takes him to route the call.

o   Low PDD Calls, % – Maximum acceptable percentage of calls with a PDD below the specified value.

o   Max PDD – Defines the maximum acceptable PDD. Too high a PDD has a strong negative impact on your business, since during the delay time the end user hears only silence, and generally assumes that there is a problem with the service.

o   High PDD Calls, % – Maximum acceptable percentage of calls with a PDD above the specified value.

o   Profit per Minute – The aggregated profit, i.e. the difference between the actual charged amounts in your customers’ and vendors’ xDRs.

 

4.      Click Adobe Systems Save.

 

RoutingCriteria2

 

Note that “default” means that parameter values will be taken from the Criteria Defaults table.

Define Routing Criteria for Specific Connection

After you created the routing criteria, you can apply your quality requirements to specific vendor’s connection. Thus, when such a routing model is associated with a connection, PortaBilling® will automatically arrange routes according to your quality preferences.

 

1.      On the Main Manu page of the admin interface, in the Participants section, click Vendors.

2.      Click on the Connections icon next to the vendor name.

3.      From the Routing Criteria list, select the routing criteria that you have created.

4.      Click Adobe Systems Save.

 

Connections3

 

After that, the additional Tracking tab will appear.

Tracking Connection Status

When the value of a parameter reaches the predetermined threshold, the administrator receives an email alert about the latest connection threats. The administrator can track the current connection status on the Tracking tab of the Edit Connection page. This status is represented by different colors, as follows:

·       online_grey GREY – The number of calls is not enough to apply filtering differentiation.

·       online_green GREEN – The route meets the quality requirements.

·       online_yellow YELLOW – The route is active, but some of its quality parameters are outside the warning thresholds.

·       Blocked BLOCKED – This route is currently being penalized.

NOTE: The penalized route will be on the “penalty row” for a certain period of time, specified in the Penalty Time box and then will be unblocked automatically. Alternately, you can click the Unblock Now button to unblock the penalized route manually.

·       online_red RED – The route was manually unblocked; this status will remain unchanged till the next time interval for which the statistics will be computed.

 

Connections_Tracking