On Thursday 24 June 2010, Ovidiu Sas wrote:
> With dialers, it's the cps that is causing issues (the calls are very
> short). Actually, both cps and channel limitation can be implemented
> simultaneously (via ratelimit and dialog module).
> The burden on the server is not high even at high cps (>1
With dialers, it's the cps that is causing issues (the calls are very short).
Actually, both cps and channel limitation can be implemented
simultaneously (via ratelimit and dialog module).
The burden on the server is not high even at high cps (>150cps) with
channel limitation in place (i.e. dialog
Define a pipe for each subscriber that you want to limit. Each pipe
will have it's one settings.
Keep in mind that there is a limitation (only 16 pipes):
http://kamailio.org/docs/modules/1.5.x/ratelimit.html#id2506247
If you want more then 16 pipes, you will need to modify the code and recompile.
On Thursday 24 June 2010, Stagg Shelton wrote:
> I would like to limit on a subscriber by subscriber basis the amount of
> outgoing calls per second that they can do. I am reading through the
> ratelimit module documentation, but haven't been able to determine if I
> can use it to limit one partic
Does the call to rl_check_pipe add the invite to the pipe, and update
the counters before returning. Also would I need to define multiple
pipes for multiple subscribers who I wish to rate limit? ie. The cps
from subscriber A does not affect the cps from subscriber B
Stagg Shelton
VocalCloud
The ratelimit module will do the job here. It was designed for
something like that.
You will need to define a pipe with the desired cps and then run all
the incoming INVITEs from that specific subscriber through your pipe:
http://kamailio.org/docs/modules/1.5.x/ratelimit.html#id2467664
Regards,
O
I have a customer who has just started operating a dialer. Over the
past couple of days this dialer has been creating some minor issues with
our US48 termination. We are currently running Server:: Kamailio
(1.5.1-notls (x86_64/linux)).
I would like to limit on a subscriber by subscriber basi
On Thursday 24 June 2010, marius zbihlei wrote:
> The Memcached module uses the libmemcache client library
> (http://freshmeat.net/projects/libmemcache/) not
> libmemcached(www.libmemcached.org).
indeed, it uses the "old" memcache library, as the new one was not available
in Debian and OpenSUSE d
On Jun 24, 2010 at 12:06, Iñaki Baz Castillo wrote:
> 2010/6/17 Andrei Pelinescu-Onciul :
> > Try 3.0 (kamailio or sip-router). You can control how unreplied branches
> > are canceled, see
> > http://sip-router.org/docbook/sip-router/branch/master/modules/tm/tm.html#cancel_b_method
>
>
> A quest
2010/6/17 Andrei Pelinescu-Onciul :
> Try 3.0 (kamailio or sip-router). You can control how unreplied branches
> are canceled, see
> http://sip-router.org/docbook/sip-router/branch/master/modules/tm/tm.html#cancel_b_method
A question about case 2:
---
2 will send and retransmit CANCEL ev
Ricardo Martinez wrote:
Hi.
I'm using Fedora Core 13.
With
[r...@ser mysql]# uname -a
Linux ser 2.6.33.5-124.fc13.i686.PAE #1 SMP Fri Jun 11 09:42:24 UTC 2010 i686
i686 i386 GNU/Linux
Regards,
Ricardo.
Hello Ricardo,
The Memcached module uses the libmemcache client library
(http://freshm
http://kmkhzr.http://tabletsdrugs.com/
___
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
12 matches
Mail list logo
