I've done this with dialog and a sql lookup/update. The sql call updates the table with how many calls are in total for the "client" and how many international calls. There's a max calls and a max international.
If current < max, the call can go through. The db allows me to combine the lookup over multiple media servers and kamailio servers. The lookup checks the db so any modifications occur in real-time. Fred Posner The Palner Group, Inc. http://www.palner.com (web) +1-503-914-0999 (direct) +1-954-472-2896 (fax) On 07/03/2014 07:37 AM, Olle E. Johansson wrote: > Hi! > > Have you implemented a per-customer rate limit in Calls per second? If so - > how? > > I've played with ratelimit/pipelimit and it seems like I can define a > database with one pipe per customer - but have to restart Kamailio to add > customers. There are warnings for low timer settings, like 1 second, but I > don't know how up-to-date those warnings are. > > I guess I could play with hash tables and implement something pike-like > there, but it seems like a workaround for something pretty common. > > So the question remains - how are you limiting on a cps per customer? > > /O > _______________________________________________ > SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list > sr-users@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@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
