Ticket #3034 (new Feature Requests)

Opened 4 months ago

Last modified 4 months ago

Trunk load balancing for outbound routes

Reported by: olivier1010 Assigned to: p_lindheimer
Priority: major Milestone: 3.0
Component: Core - Trunks/Routing Version:
Keywords: Cc:
Confirmation: Confirmed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

It would be really interesting if you could have trunk balancing inside outbound routes.

This would permitt to use more than one VoIP provider more easily and efficiently.

There are two big advantages of doing this :

The fisrt one is a commercial advantage :

The two providers receive approximately the same number of calls. This is commercially a better situation than having one provider for main calls, and the other for backup calls.

2) It is frequent to have signalisation problems with VoIP providers. The most difficult situation is when a provider send back a busy instead of a congestion.

In this case, the call is simply failed, because when we get a busy the next trunk is not tried.

Using trunk balancing, if a call is failed because of bad signalisation, there are good chances that for the next try it will take the other trunk and perhaps give a success call.

Change History

08/08/08 09:39:18 changed by p_lindheimer

  • confirmation changed from Unreviewed to Confirmed.
  • version deleted.
  • milestone changed from 2.5 to 4.0.

I guess it would depend on how you choose the next trunk as to if bad signaling from the provider marks it as busy vs. congestion. However, for this problem, I would say to either get the provider to fix it properly or find another provider who knows what they are doing.

Anyhow - the load balancing is a good idea and I'm going to move it to Milestone 4 as it is something that would be considered at the time we were reviewing the overhaul of trunks, routing etc. Since you probably want to provide a bit more information for load balancing like how you want to weight calls across trunks and thus review what the current load is on each trunk when choosing where to send the next call. (Which is why my first comment indicated that your other problem may not be solved since you would probably want this type of intelligence in choosing the provider.

Donate



Support
Download
Develop
Forums
News
Documentation
Paid Support
About

Paid Ads