On Mon, Dec 04, 2017 at 03:28:08PM -0500, Mark Blackford wrote:
> So, it sounds like from what you describe, I will set my hash size to
> be a few times larger than my forecasted profile size to keep matching
> operations to a minimal. And since dialogs timeout anyway if they are
> not cleared
Hello,
Wanted to ask if you found something
Alexandru Covalschi
VoIP Engineer and System Administrator
tel: +373 673 98 493
> 24 нояб. 2017 г., в 22:19, Alexandru Covalschi <568...@gmail.com> написал(а):
>
> Hello, sharing whole config except vars.cfg file,
Thank you for your response!
I am currently replacing the call_control module used with CDRTool Prepaid
with the dialog module using hash tables. The speed and stability are
tremendously better!
My concern is two-fold:
1) I do not want calls to be blocked because I set the hash table size too
The hash_size has no relevance on how many dialogs can be handled. It is
only related to the lookup performance. So even with hash_size=1 you can
have same number of dialogs as with hash_size=4096 or higher.
The difference is that with hash_size=1, all the dialogs are in a single
linked list, so
Hi Daniel,
Thanks for your responses. This discussion has been very useful.
Our code is along the lines that you suggest in which we are using some
database ops prior to the dialog calls to gather if the user is call
limited and if so, the provisioned users "max calls allowed" per billing
Hi,
I am using *Kamailio 4.4*. I would like to forward the request to a
different port number of my endpoint. I have changed the destination *URI *and
the *INVITE *correctly reached to the new port. But the *To header
*in the *INVITE
*request has the old port. so the endpoint is not responding to
Hi,
most user agents ignore the domain and port in the from header. Your
UAC must be special.
However, the uac module has some functions to help you. But don't
forget to restore it on the way back.
Regards,
Sebastian
On Tue, Dec 5, 2017 at 5:32 AM, Arun NV wrote:
> Hi,
Hi
Have used allow_trused to pass the allowed ip.
Now I want to check the request has a correct tech prefix.
With an entry in ruri-patten column in the trusted table for example 75622#.
So if calls are to olny be allowed when the "to" destination starts with
75622#.
Regards
Hello,
after restart, if you list the dialogs via rpc command, do you see them
in what is returned?
Cheers,
Daniel
On 29.11.17 20:52, Kordován Szabolcs wrote:
> Hi All,
>
> In March there was a discus about this issue.
>
> We tested the new 5.2 dev and 5.0.4 version of Kamailio and we
>
Hello,
there should be some configs out there for installing kamailio using
ansible, puppet, chef ... that can be used to extract the shell
commands. Just search on the web for preferred deployment tool.
As alternative, you can extract the shell commands from Dockerfile,
there are couple of
Hello,
look at tsilo module as well as the presentation by Federico at Kamailio
World Conference about using Kamailio for mobile networks:
-
https://www.kamailio.org/events/2016-KamailioWorld/Day2/16-Federico.Cabiddu-Thriving-In-A-Mobile-World.pdf
-
Hello,
short note to remind that the next major release is planned in one week
-- testing of branch 5.1 and improvements to documentation are very
appreciated!
Cheers,
Daniel
On 27.11.17 09:23, Daniel-Constantin Mierla wrote:
> Hello,
>
> with no relevant new bugs reported lately, it is time to
Actually, dispatcher works for incoming requests that are going to be
sent out. You generate the requests locally using uac, so no effect on
such case when using dispatcher functions. In this case, the equivalent
of $du is $uac_req(duri), $ru is $uac_req(ruri).
Your solution to loop with
Hello,
I am trying to properly size the use of the Dialog Module hash table for
Kamailio 4.1.3 implementation using:
modparam("dialog", "hash_size", )
However, in my testing, I have been unable to figure out the relationship
between the hash size and a number of dialogs I need to support. I
14 matches
Mail list logo