An alternative option would be to leverage cachedb_local and opensips-cli
to implement your list of accounts and rate limits. It has the advantage of
using the internal opensips cache service and is probably your most high
performance option, with the CLI you can automate data refreshes using
basic
There are no db queries, unless explicitly enabled for distributed
rate limiting, in which case memcache or redis can be used.
-ovidiu
On Sun, Jan 24, 2021 at 1:57 AM Schneur Rosenberg
wrote:
>
> Maybe use memcache, it's global and it won't create a bottleneck like a
> database query would.
>
>
Maybe use memcache, it's global and it won't create a bottleneck like a
database query would.
Scott (Schneur)
On Thu, Jan 21, 2021, 05:43 Ovidiu Sas wrote:
> Take a look at the ratelimit module:
> https://opensips.org/docs/modules/3.1.x/ratelimit.html
>
> -ovidiu
>
> On Wed, Jan 20, 2021 at 10:
Take a look at the ratelimit module:
https://opensips.org/docs/modules/3.1.x/ratelimit.html
-ovidiu
On Wed, Jan 20, 2021 at 10:01 PM Alexander Perkins
wrote:
>
> Hi All. Is there a way to limit the calls per second by pulling the
> information from a database? I was looking at the call_control
Hi Alex,
You can save the data from your database to memory and fetch it during all
control. I will not recommend to use db directly. There might be any other
better way someone from the community can tell us ;)
Regards,
Jehanzaib
On Thu, Jan 21, 2021 at 4:01 PM Alexander Perkins <
alexanderhe
Hi All. Is there a way to limit the calls per second by pulling the
information from a database? I was looking at the call_control module and
that seems to be a global value. but I would need something that I can
control at the call level (I will be handling different accounts that have
different
