All the time there is space for more :). This blog post is the first
from a set of docs trying to explain the routing with OpenSIPS.
Including some feedback from you, I can draft as following chapters:
1) how to insert a balancer in your SIP traffic - like dialog
statefull proxy, transaction statefull proxy, stateless proxy, etc....
2) routing modules in opensips, like dispatcher versus drouting
In your classification, I noticed many missing features for Dynamic Routing:
- in memory matching with prefix-tree - O(prefix_len)
- has gui in Control Panel
- destination pinging, failover, re-enable
- clustering capabilities for the state of the GW/destinations
- rule fallback (on matching)
Again, any feedback is more the welcome as it will give us some ideas
about the hot topics from the user perspective.
OpenSIPS Founder and Developer
OpenSIPS Bootcamp 2017, Houston, US
On 06/15/2017 09:36 PM, Mundkowsky, Robert wrote:
> This is helpful. But would like a little more details there. Such as:
> 1) openSIPS when it actions as a Load Balancer is always a SIP proxy during the complete dialog. In other words, the caller RTP is direct connected backend gateway, but openSIPS is always between them for the SIP traffic.
> 2) Some information for the traffic distributions modules is stored in the database, but some info is only in memory (e.g. which gateway is enabled, count of active dialogs)
> This might be naïve details for most telecom folks, but helpful for naïve users like myself.
> I haven't played with "Carrier Route","Dispatcher", and "Dynamic Routing", but similar notes for those would be helpful too.
> The following video was very helpful in describing the different traffic distributions modules openSIPS supports:
> Not sure if my notes are helpful, but they are below.
> Routing modules:
> Carrier Route
> - old module and not maintained, but seems to work
> - features: routing, load balancing, blacklisting
> - not installed by default
> - no web GUI
> - performs longest prefix matching
> - you use longest preefix to pull "least cost" route out of database table
> - strips prefix, adds prefix/suffix
> - probabilities to load balancer
> Load Balancer
> - light weight
> - balancing based on load
> - can config via GUI
> - single database table
> - features:
> - no prefix/suffix changing
> - with version 1.8, you can keep counters in database
> - docs:
> DB schema:
> - computes hash over parts of request and selects an address from the destination list
> - can config via GUI
> - CallerID, From URI, To URI, Request URI
> - via config file or databaseas
> - does not strip or append prefix/suffix
> - out of service destinations detected by probing
> - can mark as out of service
> - can mark as in service when gateway comes back online
> Dynamic Routing
> - heavy weight
> - multiple criteria to determine route
> - prefix, caller, group, time, priority
> - databse only
> 4 tables (groups, rules, carriers, gateways)
> - functions
> - do_routing() uses all 4 tables
> - route_to_carrier uses carriers & gateways tables
> - route_to_gateway - uses gateways table
> Robert Mundkowsky
> -----Original Message-----
> From: Devel [mailto:[hidden email]] On Behalf Of Bogdan-Andrei Iancu
> Sent: Thursday, June 15, 2017 2:01 PM
> To: [hidden email]; developensips <[hidden email]>; [hidden email]; [hidden email]
> Subject: [OpenSIPS-Devel] [Blog] Traffic balancing – load, weights, round robin ??
> Many times, during discussion about various OpenSIPS based solutions, I noticed that people make a confusion when comes to the meaning of “load balancing”.....
> Enjoy the reading :)
> Bogdan-Andrei Iancu
> OpenSIPS Founder and Developer
> OpenSIPS Bootcamp 2017, Houston, US
> Devel mailing list
> [hidden email]
> This e-mail and any files transmitted with it may contain privileged or confidential information. It is solely for use by the individual for whom it is intended, even if addressed incorrectly. If you received this e-mail in error, please notify the sender; do not disclose, copy, distribute, or take any action in reliance on the contents of this information; and delete it from your system. Any other use of this e-mail is prohibited.
> Thank you for your compliance.
> Users mailing list
> [hidden email]
Devel mailing list
|Free forum by Nabble||Edit this page|