Hi,
we're trying to have scalable Kamailio nodes that are stateless.
That means that we can for example load dispatchers and reload them from an API endpoint.
Now we're stuck on the dialog part. All our nodes load the dialogs from a shared db, what happens when a node gets down is that a packet reaches another node and does not know how to handle that because the dialog does not have it's ip address. Also there is no possibility to reload the dialogs from db so that we could update the records in the db and have the dialogs ip changed on an anctive node's ip.
Is there a possibility to have a function to reload the dialogs from db on a running kamailio?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1274
Hello,
I'm using keepalive module with drouting module... the event route works fine:
NOTICE: <script>: Gateway up: OPTIONS sip:1.2.3.4
NOTICE: <script>: Gateway up: OPTIONS sip:5.6.7.8
but kamcmd command not:
kamcmd keepalive.list
foobar
42
foobar
42
{
text: foobar
number: 42
}
{
list: {
nn: 17
nn: 22
}
}
{
uri: sip:1.2.3.4
owner: drouting
last checked: Wed Feb 21 11:20:12 2018
last up: Wed Dec 31 19:00:00 1969
last down: Wed Feb 21 11:20:13 2018
}
{
uri: sip:5.6.7.8
owner: drouting
last checked: Wed Feb 21 11:20:12 2018
last up: Wed Dec 31 19:00:00 1969
last down: Wed Feb 21 11:20:12 2018
Thank you
Regards...
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1476
Module: kamailio
Branch: 5.0
Commit: f7633fb7033aabad41a2055c851361f0c81f4444
URL: https://github.com/kamailio/kamailio/commit/f7633fb7033aabad41a2055c851361f…
Author: Henning Westerholt <hw(a)kamailio.org>
Committer: Henning Westerholt <hw(a)kamailio.org>
Date: 2018-04-12T21:38:08+02:00
msilo: remove not working tm parameter in the example cfg, reported from Abdul Basit
- remove the not working, too small tm parameter in the example cfg
- has been not changed in the last 10 years, probably not valid anymore
- reported from Abdul Basit on sr-users
(cherry picked from commit 22b13d4d44cb0dbd71b87deab42af5f7c8ea932f)
---
Modified: src/modules/msilo/doc/msilo.cfg
---
Diff: https://github.com/kamailio/kamailio/commit/f7633fb7033aabad41a2055c851361f…
Patch: https://github.com/kamailio/kamailio/commit/f7633fb7033aabad41a2055c851361f…
---
diff --git a/src/modules/msilo/doc/msilo.cfg b/src/modules/msilo/doc/msilo.cfg
index 05329f0299..e6c74ff6d2 100644
--- a/src/modules/msilo/doc/msilo.cfg
+++ b/src/modules/msilo/doc/msilo.cfg
@@ -48,12 +48,6 @@ modparam("msilo","contact_hdr","Contact: registrar@192.168.1.2:5060;msilo=yes\r\
modparam("msilo","content_type_hdr","Content-Type: text/plain\r\n")
modparam("msilo","offline_message","*** User $rU is offline!")
-# -- tm params --
-
-modparam("tm", "fr_timer", 10 )
-modparam("tm", "fr_inv_timer", 15 )
-modparam("tm", "wt_timer", 10 )
-
route{
if ( !mf_process_maxfwd_header("10") )