Hello,
I have 2 kam instances using one shared database and both kam servers
running the same routing logic code. Kamailio servers are configured to use
the same database as dialog backend.
I am limiting the concurrent dialogs in the following way but it seems that
kamailio is using its own memor
On Sun, Sep 29, 2019 at 11:03:47AM +0300, Olli Attila wrote:
> modparam("dialog", "profiles_with_value", "concurrent_calls")
> modparam("dialog", "dlg_flag", 4)
> modparam("dialog", "db_url", DBURL)
> modparam("dialog", "db_mode", 1)
Have you tested with a lower value of
https://kamailio.org/docs
services - https://skalatan.de/services
From: sr-users On Behalf Of Olli Attila
Sent: Sunday, September 29, 2019 10:04 AM
To: Kamailio (SER) - Users Mailing List
Subject: [SR-Users] Call limit through shared database
Hello,
I have 2 kam instances using one shared database and both kam servers running
On 30.09.19 14:55, Daniel Tryba wrote:
> On Sun, Sep 29, 2019 at 11:03:47AM +0300, Olli Attila wrote:
>> modparam("dialog", "profiles_with_value", "concurrent_calls")
>> modparam("dialog", "dlg_flag", 4)
>> modparam("dialog", "db_url", DBURL)
>> modparam("dialog", "db_mode", 1)
>
> Have you test
Just a note, I would suggest to use htable+dmq to do such limits,
dialog+dmq has some issues when handling dialog expiration when a node for
whatever reason is restarted.. (search GH issues and you will find one with
a long thread where Charles explains the reasons: TL;DR: You could end up
having
Found it:
https://github.com/kamailio/kamailio/issues/1591#issuecomment-409205552
On Tue, Oct 1, 2019 at 07:15 Joel Serrano wrote:
> Just a note, I would suggest to use htable+dmq to do such limits,
> dialog+dmq has some issues when handling dialog expiration when a node for
> whatever reason
: Kamailio (SER) - Users Mailing List ;
mico...@gmail.com
Subject: Re: [SR-Users] Call limit through shared database
Just a note, I would suggest to use htable+dmq to do such limits, dialog+dmq
has some issues when handling dialog expiration when a node for whatever reason
is restarted.. (search
Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
From: sr-users On Behalf Of Joel Serrano
Sent: Tuesday, October 1, 2019 4:35 PM
To: Kamailio (SER) - Users Mailing List ;
mico...@gmail.com
Subject: Re: [SR-Users] Call limit through shared database
Found it
t;
>
> --
>
> Henning Westerholt - https://skalatan.de/blog/
>
> Kamailio services - https://skalatan.de/services
>
>
>
> *From:* sr-users *On Behalf Of *Joel
> Serrano
> *Sent:* Tuesday, October 1, 2019 4:35 PM
> *To:* Kamailio (SER) - Users Mailing List ;
>
Hello Henning,
I tried the dialog profile sharing with dmq&dialog modules and now the
syncing works between the two kam nodes. Thank you!
Is there a way to keep the dialog profiles persistent (load from db if kam
restarts)? I was thinking a scenario where kam1 has already the call limit
maxed out
Hi Olli,
if I have interpreted the question and the situation in which you are
correctly, the way to persist a dialog in DB is to use the db_mode param
https://kamailio.org/docs/modules/5.2.x/modules/dialog.html#dialog.p.db_mode
you have 4 possibilities to persist that data in DB
-
*0 - NO
Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services
From: Olli Attila
Sent: Friday, October 4, 2019 5:54 AM
To: Henning Westerholt
Cc: Kamailio (SER) - Users Mailing List
Subject: Re: [SR-Users] Call limit through shared database
Hello Henning,
I tried the dialog
Hello,
I had the following enabled in db_mode param and now it is actually working:
*1 - REALTIME* - any dialog information changes will be reflected into
the database immediately.
Restarting either of the kam1 or kam2 proxies "on the fly" will result
in retrieving dialog profiles correctly
https://skalatan.de/blog/
>
> Kamailio services - https://skalatan.de/services
>
>
>
> From: Olli Attila
> Sent: Friday, October 4, 2019 5:54 AM
> To: Henning Westerholt
> Cc: Kamailio (SER) - Users Mailing List
> Subject: Re: [SR-Users] Call limit through shared da
14 matches
Mail list logo