Re: [SR-Users] Call limit through shared database

2019-10-04 Thread Olli Attila
Hello Henning, I tried the dialog profile sharing with dmq 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 and

[SR-Users] q_malloc crash on Kamailio 5.2.3 with http_async_query function

2019-10-04 Thread Michal Škuta
Hello everyone, I am adding some new features to our Kamailio server, one of them is sending HTTP POST request after calls end. We created simple route like this and we are calling it from event_route[dialog_end]: route[HTTP_TEST_CALL_END] { t_newtran(); $http_req(body) = "TEST";

Re: [SR-Users] q_malloc crash on Kamailio 5.2.3 with http_async_query function

2019-10-04 Thread Federico Cabiddu
Hi, I've seen the github issue, I'll have a look asap. To be clear, are you using http_async_query in dialog's event route also in 4.4.x or is this something new in your routing script? Regards, Federico On Fri, Oct 4, 2019 at 10:42 AM Michal Škuta wrote: > Hello everyone, > I am adding some

Re: [SR-Users] lookup(aliases) issues with 5.2

2019-10-04 Thread igor.potjevlesch
Hello Daniel, I confirm that we did that indeed. Just added the support of "_" instead of rollback on the whole code. Thank you! Regards, Igor. De : Daniel-Constantin Mierla Envoyé : mercredi 11 septembre 2019 09:51 À : igor.potjevle...@gmail.com; 'Kamailio (SER) - Users

Re: [SR-Users] Call limit through shared database

2019-10-04 Thread Giovanni Tommasini - evosip
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 -

[SR-Users] storing vars in htable

2019-10-04 Thread David Villasmil
Hello guys, I'm storing some data in an htable, like so: $var(http_query) = "/default/en_US/send.html?u=user=pass=$var(next_channel)=$var(to)=$var(message)"; then i need to store it: $sht(http_requests=>$http_req_id) = $var(http_query); But what's stored is the actual vars, not the the

Re: [SR-Users] storing vars in htable

2019-10-04 Thread Alex Balashov
Kamailio has inconsistent interpolation behaviour; static string assignment values are not interpolated. So, this won’t work: $var(x) = “$var(y)abc”; But this will: $var(x) = $var(y) + “abc”; Also see:

Re: [SR-Users] Call limit through shared database

2019-10-04 Thread Henning Westerholt
Hello Olli, the profile information should be also synchronized with DMQ – but not sure if they are also synchronized during startup. If kam2 reboots it should get the dialog information from kam1 after it has started. Have you tried if its works already? Cheers, Henning -- Henning

Re: [SR-Users] Call limit through shared database

2019-10-04 Thread Olli Attila
Hello Henning, Ok I think I was wrong when I assumed the mysql would do the dialog profile syncing somehow during kamailio reboot but instead the DMQ is actually doing it like you posted earlier. I traced with wireshark and noticed that after kam2 rebooted itself and became responsive again,

Re: [SR-Users] Call limit through shared database

2019-10-04 Thread Olli Attila
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

[SR-Users] Bad BYE request

2019-10-04 Thread Duarte Rocha
Greetings, This is a repeated problem, but i have more info now. Please help understand if there is a problem on my code or if there is any kind of Kamailio bug. On the first INVITE of every call i apply uac_replace_from() and uac_replace_to() in order to normalize numeration. I have the

[SR-Users] using http_async_query

2019-10-04 Thread David Villasmil
Hello guys, So, i'm using http_async_query to send out requests. It may happen that the request times out, in this case, i would like to try a new destination, i.e. with ds_select (NOT ds_delect_dest or ds_next, because i don't want the $du to be set, since in my case i don't actually have a SIP