Feature Requests item #1696125, was opened at 2007-04-07 14:08 Message generated for change (Comment added) made by osas You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743023&aid=1696125&group_id=139143
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: modules Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: LyleThaut (lylethaut) Assigned to: Nobody/Anonymous (nobody) Summary: LCR Gateway Priority Initial Comment: With the current LCR module (1.2.0) we have the ability to send prefixes to a certain group of gateways with the specified group id and priority field in the lcr table. I have the need to prioritize the gateways within a gateway group. Right now if you have 3 gateways in a group, your traffic will get sent to one of the gateways in a random fashion. I want to be able to choose which of the gateways out of the group gets used. Scenario as follows: My SIP peer has 3 gateways that that I can send traffic to. However, they prefer that I send traffic to their primary gateway and only use the other two if the first one fails. Seems like this can be accomplished by adding a priority field in the gateways table so we can choose which server within a group to send traffic to. ---------------------------------------------------------------------- Comment By: Ovidiu Sas (osas) Date: 2007-04-09 10:05 Message: Logged In: YES user_id=1395524 Originator: NO My understanding is that a the gw table is for attributes that belong to a gateway and priority is not an attribute of a gateway. Priorities are for routes. For instance: you can't make the assumption that a gateway will have the same priority for all calls (e.g. local calls vs. long distance calls). Having the priority field inside routes will allow you to use the same gateway with different priorities, for example: high priority for local calls, medium priority for emergency calls and low priority for long distance calls. ---------------------------------------------------------------------- Comment By: LyleThaut (lylethaut) Date: 2007-04-07 23:34 Message: Logged In: YES user_id=1763646 Originator: YES My concern is to not make the lcr table unnecessarily large. Take my example above and multiply it times 5 or 6 sip providers and you can easily have over a million rows in the lcr table. I believe that the solution offered by osas would create more duplication than desired in the lcr table. For three sip providers and one prefix you need 9 entries in the lcr table. With priority field only in the lcr table (9 lcr table rows): SIP provider A: group 1 - prefix 222 - priority 0 group 2 - prefix 222 - priority 1 group 2 - prefix 222 - priority 1 Group 1 has primary gateway for this provider, group 2 has secondary gateway(s). SIP provider B: group 3 - prefix 222 - priority 2 group 4 - prefix 222 - priority 3 group 4 - prefix 222 - priority 3 Group 3 has primary gateway for this provider, group 4 has secondary gateway(s). SIP provider C: group 5 - prefix 222 - priority 4 group 6 - prefix 222 - priority 5 group 6 - prefix 222 - priority 5 Group 5 has primary gateway for this provider, group 6 has secondary gateway(s). With proposed gateway_priority field in gw table (3 lcr table rows): SIP provider A: group 1 - prefix 222 - priority 0 Group 1 can have any number of gateways prioritized as necessary SIP provider B: group 2 - prefix 222 - priority 1 Group 2 can have any number of gateways prioritized as necessary SIP provider C: group 3 - prefix 222 - priority 2 Group 3 can have any number of gateways prioritized as necessary Ultimately I believe that having a priority field in the gw table would give users more granular control over how to route traffic with LCR with less overhead. ---------------------------------------------------------------------- Comment By: Ovidiu Sas (osas) Date: 2007-04-07 14:44 Message: Logged In: YES user_id=1395524 Originator: NO You can achieve that by using the priority field in the lcr table. Put the primary gateway into the primary_group. Put the other two gateways into the secondary_group. In the lcr table add two entries for the same prefix/from_uri: - primary_group with priority 0 - secondary_group with priority 1 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=743023&aid=1696125&group_id=139143 _______________________________________________ Devel mailing list Devel@openser.org http://openser.org/cgi-bin/mailman/listinfo/devel