[OpenSIPS-Users] Rate limit question
john.nash778 at gmail.com
Fri Jun 3 11:15:02 CEST 2016
Thank you for detailed reply. I will choose to implement on Opensips. I
would also prefer performance over accuracy as my objective is to stop
customers from flooding with too many calls so I can select RED?
On Fri, Jun 3, 2016 at 12:47 PM, Răzvan Crainea <razvan at opensips.org> wrote:
> Hi, John!
> It depends on the logic of your platform. If you have multiple FreeSWITCH
> servers behind OpenSIPS, and you want to have a "global" limit, then you
> must do it on OpenSIPS side. It is also recommended to do it there because
> for example if the threashold is reached, you don't have to load FreeSWITCH
> with traffic that's about to be denied. However, if you have local (per
> FreeSWITCH) limits, then you can do it on the FreeSWITCH side (with the
> earlier observations).
> Regarding the algorithm, it depends on what you want to limit. If you want
> to do CPS, then TAILDROP or RED is more suitable. If you want to do a
> limitation based on the network load, then use NETWORK.
> Also take into account that the way RED and TAILDROP algorithm work, they
> are not so accurate. That's why in OpenSIPS 2.2 we added a new algorithm,
> SBT, which is very accurate and custamizable.
> Best regards,
> Răzvan Crainea
> OpenSIPS Solutionswww.opensips-solutions.com
> On 06/02/2016 08:49 AM, John Nash wrote:
> Also how can I decide which Rate limit algorithm should I choose ? Like
> RED or TAILDROP or NETWORK
> On Thu, Jun 2, 2016 at 9:37 AM, John Nash <john.nash778 at gmail.com> wrote:
>> I am using opensips(2,1) + freeswitch. At opensips doing auth and
>> drouting. Now i plan to test rate limit but should I be checking CPS at
>> opensips or at freeswitch?...as Rate limit uses timers would it be more
>> appropriate to check at freeswitch?
> Users mailing listUsers at lists.opensips.orghttp://lists.opensips.org/cgi-bin/mailman/listinfo/users
> Users mailing list
> Users at lists.opensips.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Users