Rate limiting

List overview All Threads
Download

newer

older

Weird issue with kamailio relaying...

Configuration to use rtpengine for...

NITESH BANSAL

12 Jul 2016 12 Jul '16

4:19 a.m.

Hello, I plan to add some rate limiting in the Kamailio. I'm already using Pike to rate limit based on the source IP. But in this case, i want to do the rate limiting per customer(regardless of the source IP), I can identify the customer based on a custom header in the INVITE, idea is to limit the customer to 'x' number of requests per second. Nitesh

Attachments:

attachment.html (text/html — 794 bytes)

Show replies by date

NITESH BANSAL

13 Jul 13 Jul

4:09 a.m.

Actually, I forgot to mention that, I'm looking for a Kamailio module which can do that. I want to avoid doing it on the application level (in perl/python). Thanks, Nitesh ________________________________ From: sr-users <sr-users-bounces(a)lists.sip-router.org> on behalf of NITESH BANSAL <nitesh.bansal(a)outlook.com> Sent: Tuesday, July 12, 2016 10:19:35 AM To: sr-users(a)lists.sip-router.org Subject: [SR-Users] Rate limiting Hello, I plan to add some rate limiting in the Kamailio. I'm already using Pike to rate limit based on the source IP. But in this case, i want to do the rate limiting per customer(regardless of the source IP), I can identify the customer based on a custom header in the INVITE, idea is to limit the customer to 'x' number of requests per second. Nitesh

Alex Balashov

9:47 a.m.

The pipelimit module is the solution to all your problems. On 07/13/2016 04:09 AM, NITESH BANSAL wrote:

...

Actually, I forgot to mention that, I'm looking for a Kamailio module which can do that. I want to avoid doing it on the application level (in perl/python). Thanks, Nitesh ------------------------------------------------------------------------ *From:* sr-users <sr-users-bounces(a)lists.sip-router.org> on behalf of NITESH BANSAL <nitesh.bansal(a)outlook.com> *Sent:* Tuesday, July 12, 2016 10:19:35 AM *To:* sr-users(a)lists.sip-router.org *Subject:* [SR-Users] Rate limiting Hello, I plan to add some rate limiting in the Kamailio. I'm already using *Pike* to rate limit based on the source IP. But in this case, i want to do the rate limiting per customer(regardless of the source IP), I can identify the customer based on a custom header in the INVITE, idea is to limit the customer to 'x' number of requests per second. Nitesh _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

NITESH BANSAL

15 Jul 15 Jul

4:59 a.m.

Hi Alex, I looked at the pipelimit module and apparently it relies on database, for performance reasons, I want to avoid DB looks and want to maintain something in-memory, just like 'Pike' does for source-ip limiting. Is there any way to do that in Kamailio? Nitesh ________________________________ From: sr-users <sr-users-bounces(a)lists.sip-router.org> on behalf of Alex Balashov <abalashov(a)evaristesys.com> Sent: Wednesday, July 13, 2016 3:47:32 PM To: sr-users(a)lists.sip-router.org Subject: Re: [SR-Users] Rate limiting The pipelimit module is the solution to all your problems. On 07/13/2016 04:09 AM, NITESH BANSAL wrote:

...

Alex Balashov

7:54 a.m.

I have never used pipelimit with a database. The essence is the ability to pass a dynamic pipe to pl_check() which is created if it doesn't exist. On July 15, 2016 4:59:01 AM EDT, NITESH BANSAL <nitesh.bansal(a)outlook.com> wrote:

...

Actually, I forgot to mention that, I'm looking for a Kamailio module which can do that. I want to avoid doing it on the application level (in perl/python). Thanks, Nitesh

------------------------------------------------------------------------

*From:* sr-users <sr-users-bounces(a)lists.sip-router.org> on behalf of NITESH BANSAL <nitesh.bansal(a)outlook.com> *Sent:* Tuesday, July 12, 2016 10:19:35 AM *To:* sr-users(a)lists.sip-router.org *Subject:* [SR-Users] Rate limiting Hello, I plan to add some rate limiting in the Kamailio. I'm already using *Pike* to rate limit based on the source IP. But in this case, i want to do the rate limiting per

customer(regardless

of the source IP), I can identify the customer based on a custom header in the INVITE, idea is to limit the customer to 'x' number of requests per second. Nitesh _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing

list

sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Alex Balashov | Principal | Evariste Systems LLC 1447 Peachtree Street NE, Suite 700 Atlanta, GA 30309 United States Tel: +1-800-250-5920 (toll-free) / +1-678-954-0671 (direct) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users ------------------------------------------------------------------------ _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Alex -- Principal, Evariste Systems LLC (www.evaristesys.com) Sent from my Google Nexus.

NITESH BANSAL

24 Aug 24 Aug

4:16 a.m.

Hello, I tried calling the function pl_check , this is how I'm trying to use. $var(check_result) = pl_check("$avp(s:LOGIN)"); This is always returning -2, shouldn't it create a new PIPE next time it receives a message from the same login? I'm using Kamailio 4.1, could that be the difference? Thanks, Nitesh ________________________________ From: sr-users <sr-users-bounces(a)lists.sip-router.org> on behalf of Alex Balashov <abalashov(a)evaristesys.com> Sent: Friday, July 15, 2016 1:54:49 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Rate limiting I have never used pipelimit with a database. The essence is the ability to pass a dynamic pipe to pl_check() which is created if it doesn't exist. On July 15, 2016 4:59:01 AM EDT, NITESH BANSAL <nitesh.bansal(a)outlook.com> wrote:

...

Actually, I forgot to mention that, I'm looking for a Kamailio module which can do that. I want to avoid doing it on the application level (in perl/python). Thanks, Nitesh

------------------------------------------------------------------------

customer(regardless

list

sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Alex -- Principal, Evariste Systems LLC (www.evaristesys.com<http://www.evaristesys.com>) Sent from my Google Nexus. _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

NITESH BANSAL

4:22 a.m.

What I really want is something similar to the Pike module, which dynamically controls the traffic based on the source address. In my case, instead of the source address, I need to control traffic based on the LOGIN, there is no way to statically configure the LOGIN, I want the module to treat the LOGINs just like dynamic source addresses. ________________________________ From: sr-users <sr-users-bounces(a)lists.sip-router.org> on behalf of NITESH BANSAL <nitesh.bansal(a)outlook.com> Sent: Wednesday, August 24, 2016 10:16:20 AM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Rate limiting Hello, I tried calling the function pl_check , this is how I'm trying to use. $var(check_result) = pl_check("$avp(s:LOGIN)"); This is always returning -2, shouldn't it create a new PIPE next time it receives a message from the same login? I'm using Kamailio 4.1, could that be the difference? Thanks, Nitesh ________________________________ From: sr-users <sr-users-bounces(a)lists.sip-router.org> on behalf of Alex Balashov <abalashov(a)evaristesys.com> Sent: Friday, July 15, 2016 1:54:49 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Rate limiting I have never used pipelimit with a database. The essence is the ability to pass a dynamic pipe to pl_check() which is created if it doesn't exist. On July 15, 2016 4:59:01 AM EDT, NITESH BANSAL <nitesh.bansal(a)outlook.com> wrote:

...

Actually, I forgot to mention that, I'm looking for a Kamailio module which can do that. I want to avoid doing it on the application level (in perl/python). Thanks, Nitesh

------------------------------------------------------------------------

customer(regardless

list

sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

NITESH BANSAL

29 Aug 29 Aug

11:37 a.m.

Finally I got it working. The issue was that I was trying to use pikelimit with Kamailio version 4.1, 4.1 version doesn't allow for dynamic pipe creation. In the end, I backported pipelimit code from Kamailio version 4.2 and used pl_check function to create dynamic pipes. ________________________________ From: sr-users <sr-users-bounces(a)lists.sip-router.org> on behalf of NITESH BANSAL <nitesh.bansal(a)outlook.com> Sent: Wednesday, August 24, 2016 10:22:14 AM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Rate limiting What I really want is something similar to the Pike module, which dynamically controls the traffic based on the source address. In my case, instead of the source address, I need to control traffic based on the LOGIN, there is no way to statically configure the LOGIN, I want the module to treat the LOGINs just like dynamic source addresses. ________________________________ From: sr-users <sr-users-bounces(a)lists.sip-router.org> on behalf of NITESH BANSAL <nitesh.bansal(a)outlook.com> Sent: Wednesday, August 24, 2016 10:16:20 AM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Rate limiting Hello, I tried calling the function pl_check , this is how I'm trying to use. $var(check_result) = pl_check("$avp(s:LOGIN)"); This is always returning -2, shouldn't it create a new PIPE next time it receives a message from the same login? I'm using Kamailio 4.1, could that be the difference? Thanks, Nitesh ________________________________ From: sr-users <sr-users-bounces(a)lists.sip-router.org> on behalf of Alex Balashov <abalashov(a)evaristesys.com> Sent: Friday, July 15, 2016 1:54:49 PM To: Kamailio (SER) - Users Mailing List Subject: Re: [SR-Users] Rate limiting I have never used pipelimit with a database. The essence is the ability to pass a dynamic pipe to pl_check() which is created if it doesn't exist. On July 15, 2016 4:59:01 AM EDT, NITESH BANSAL <nitesh.bansal(a)outlook.com> wrote:

...

Actually, I forgot to mention that, I'm looking for a Kamailio module which can do that. I want to avoid doing it on the application level (in perl/python). Thanks, Nitesh

------------------------------------------------------------------------

customer(regardless

list

sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Alex Balashov

11:39 a.m.

On 08/29/2016 11:37 AM, NITESH BANSAL wrote:

...

Excellent. That was indeed an important shift. :-) -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 (direct) / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

Andreas Granig

30 Aug 30 Aug

6:15 a.m.

Hi Alex, http://www.kamailio.org/docs/modules/4.4.x/modules/ratelimit.html is another approach here. Tried it as a proof of concept recently and it seems to do its job. Seems like pipelimit is derived from ratelimit. What's the main difference from ratelimit, other than named pipes and DB support? What's the purpose of the DB support of pipelimit? Does it cache its values and can be reloaded from DB on demand (I don't see an rpc command for that)? That would be really valuable. Andreas On 08/29/2016 05:39 PM, Alex Balashov wrote:

...

On 08/29/2016 11:37 AM, NITESH BANSAL wrote:

Excellent. That was indeed an important shift. :-)

Daniel-Constantin Mierla

1 Sep 1 Sep

6:50 a.m.

Hello, the pipelimit aims to be more dynamic, while dropping the queues concepts of ratelimit, given those can be done with IF conditions inside kamailio.cfg. In ratelimit, the pipes are defined as parameters, with some limits in the number of pipes as well as constrained to integer ids for pipes. Pipelimit can load the definitions of pipes from database, making it easier to provision via some gui. It doesn't store back anything, given that even few seconds of shutdown will invalidate the pipes counters. Moreover, the pipes can be created on the fly, they don't have to be defined in advance via db or parameters. You can load the limit and algorithm from a user profile and then just use them as parameter with the username as pipe id parameter and you get a new pipe created at that moment if there is none with same id. Cheers, Daniel On 30/08/16 12:15, Andreas Granig wrote:

...

On 08/29/2016 11:37 AM, NITESH BANSAL wrote:

Excellent. That was indeed an important shift. :-)

_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Daniel-Constantin Mierla http://www.asipto.com - http://www.kamailio.org http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

John Petrini

31 Jul 31 Jul

10:10 a.m.

...

On 08/29/2016 11:37 AM, NITESH BANSAL wrote:

Excellent. That was indeed an important shift. :-)

-- Daniel-Constantin Mierla http://www.asipto.com - http://www.kamailio.org http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

Daniel-Constantin Mierla

10:27 a.m.

Hello, hash_size would be a parameter related to performances of searching a pipe. The size of shared memory is relevant also relevant in you have a very large amount of pipes. Cheers, Daniel On 31.07.17 16:10, John Petrini wrote:

...

HI All, What's everyone's experience with pipelimit regarding performance? Say we set dynamic pipes base on au and source ip? This would result in thousands of pipes would it not? Is this going to put a substantial load on the server? Are there other settings that should be tweaked when implementing it such as memory limits etc? Thank You, John Petrini On Thu, Sep 1, 2016 at 6:50 AM, Daniel-Constantin Mierla <miconda(a)gmail.com <mailto:miconda@gmail.com>> wrote: Hello, the pipelimit aims to be more dynamic, while dropping the queues concepts of ratelimit, given those can be done with IF conditions inside kamailio.cfg. In ratelimit, the pipes are defined as parameters, with some limits in the number of pipes as well as constrained to integer ids for pipes. Pipelimit can load the definitions of pipes from database, making it easier to provision via some gui. It doesn't store back anything, given that even few seconds of shutdown will invalidate the pipes counters. Moreover, the pipes can be created on the fly, they don't have to be defined in advance via db or parameters. You can load the limit and algorithm from a user profile and then just use them as parameter with the username as pipe id parameter and you get a new pipe created at that moment if there is none with same id. Cheers, Daniel On 30/08/16 12:15, Andreas Granig wrote:

Hi Alex,

http://www.kamailio.org/docs/modules/4.4.x/modules/ratelimit.html <http://www.kamailio.org/docs/modules/4.4.x/modules/ratelimit.html> is

another approach here. Tried it as a proof of concept recently

and it

seems to do its job. Seems like pipelimit is derived from ratelimit. What's the main difference from ratelimit, other than named pipes and DB

support? What's

the purpose of the DB support of pipelimit? Does it cache its

values and

can be reloaded from DB on demand (I don't see an rpc command

for that)?

That would be really valuable. Andreas On 08/29/2016 05:39 PM, Alex Balashov wrote: > On 08/29/2016 11:37 AM, NITESH BANSAL wrote: > >> Finally I got it working. The issue was that I was trying to use >> pikelimit with Kamailio version 4.1, 4.1 version doesn't allow for >> dynamic pipe creation. >> >> In the end, I backported pipelimit code from Kamailio version

4.2 and

used pl_check function to create dynamic pipes.

Excellent. That was indeed an important shift. :-)

_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users

mailing list

sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

<http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users> -- Daniel-Constantin Mierla http://www.asipto.com - http://www.kamailio.org http://twitter.com/#!/miconda <http://twitter.com/#%21/miconda> - http://www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users(a)lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users <http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users>

-- Daniel-Constantin Mierla www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

2710

days inactive

3094

days old

sr-users@lists.kamailio.org

Manage subscription

12 comments

5 participants

tags (0)

participants (5)

Alex Balashov
Andreas Granig
Daniel-Constantin Mierla
John Petrini
NITESH BANSAL