4 Mar
2022
4 Mar
'22
9:55 a.m.
Hello,
I have two Kamailio nodes. Couple of days of ago I enabled dmq to
replicate dialogs between these two Kamailio nodes. Now that the dmq
is enabled, we are seeing lot of warning and notice messages on
kamailio logs related to the dialog module. Is there something I have
missed when configuring dlg_manage & dmq replication that might cause
this? No calls have been affected negatively by this though.
Kamailio 1 node prints lot of this:
Mar 4 08:20:25 /usr/sbin/kamailio[14316]: WARNING: dialog
[dlg_handlers.c:1328]: dlg_onroute(): unable to find dialog for ACK
with route param 'a5d.ebf1' [3418:8126] and call-id
'SDiu98001-dd9c12fea650b9d1408dd672a2c51c9f-v300g00020'
Mar 4 08:20:28 /usr/sbin/kamailio[14313]: WARNING: dialog
[dlg_handlers.c:1328]: dlg_onroute(): unable to find dialog for BYE
with route param 'a5d.ebf1' [3418:8126] and call-id
'SDiu98001-dd9c12fea650b9d1408dd672a2c51c9f-v300g00020'
Mar 4 08:21:56 /usr/sbin/kamailio[14315]: WARNING: dialog
[dlg_handlers.c:1328]: dlg_onroute(): unable to find dialog for ACK
with route param '689.f2f1' [2438:7983] and call-id
'SD8o63c01-47972a87ee1fd8791ddf27b650badcba-v300g00010'
Kamailio 2 node prints lot of this:
Mar 4 08:20:29 /usr/sbin/kamailio[8005]: NOTICE: dialog
[dlg_hash.c:242]: dlg_clean_run(): dialog in early state is too old
(0x7fe07b84e980 ref 1)
Mar 4 08:20:29 /usr/sbin/kamailio[8005]: NOTICE: dialog
[dlg_hash.c:242]: dlg_clean_run(): dialog in early state is too old
(0x7fe07bb03360 ref 1)
Mar 4 08:21:59 /usr/sbin/kamailio[8005]: NOTICE: dialog
[dlg_hash.c:242]: dlg_clean_run(): dialog in early state is too old
(0x7fe07b528300 ref 1)
(Version: kamailio 5.5.3 (x86_64/linux) 473cef on both kamailio nodes)
[root@kamailio-1]# kamcmd dmq.list_nodes
{
host: 172.19.194.140
port: 5060
proto: *
resolved_ip: 172.19.194.140
status: active
last_notification: 0
local: 0
}
{
host: 172.19.194.132
port: 5060
proto: *
resolved_ip: 172.19.194.132
status: active
last_notification: 0
local: 1
}
[root@kamailio-2]# kamcmd dmq.list_nodes
{
host: 172.19.194.132
port: 5060
proto: *
resolved_ip: 172.19.194.132
status: active
last_notification: 0
local: 0
}
{
host: 172.19.194.140
port: 5060
proto: *
resolved_ip: 172.19.194.140
status: active
last_notification: 0
local: 1
}
### On Kamailio 1: ###
#!define DMQ_LOCAL_ADDR "sip:172.19.194.132:5060"
#!define DMQ_PEER_ADDR "sip:172.19.194.140:5060"
### On Kamailio 2: ###
#!define DMQ_LOCAL_ADDR "sip:172.19.194.140:5060"
#!define DMQ_PEER_ADDR "sip:172.19.194.132:5060"
### On Kamailio 1 & 2:###
modparam("dmq", "server_address", DMQ_LOCAL_ADDR)
modparam("dmq", "notification_address", DMQ_PEER_ADDR)
modparam("dialog", "profiles_with_value", "total_dialogs")
modparam("dialog", "enable_dmq", 1)
route[INITIAL] {
...located at the bottom of the initial route...
if(is_method("INVITE") && !has_totag()) {
dlg_manage();
}
}
Cheers,
Olli
11 Mar
11 Mar
3:48 p.m.
Hello,
the log:
... dlg_clean_run(): dialog in early state is too old
indicates that the dialog was not confirmed and its corresponding
structure is going to be destroyed. Try to run with debug=3 as well as
watch the dmq traffic between servers to be sure that dialogs states are
updated based on sip requests/responses belonging to the same calls.
Cheers,
Daniel
On 04.03.22 07:55, Olli Attila wrote:
Hello,
I have two Kamailio nodes. Couple of days of ago I enabled dmq to
replicate dialogs between these two Kamailio nodes. Now that the dmq
is enabled, we are seeing lot of warning and notice messages on
kamailio logs related to the dialog module. Is there something I have
missed when configuring dlg_manage & dmq replication that might cause
this? No calls have been affected negatively by this though.
Kamailio 1 node prints lot of this:
Mar 4 08:20:25 /usr/sbin/kamailio[14316]: WARNING: dialog
[dlg_handlers.c:1328]: dlg_onroute(): unable to find dialog for ACK
with route param 'a5d.ebf1' [3418:8126] and call-id
'SDiu98001-dd9c12fea650b9d1408dd672a2c51c9f-v300g00020'
Mar 4 08:20:28 /usr/sbin/kamailio[14313]: WARNING: dialog
[dlg_handlers.c:1328]: dlg_onroute(): unable to find dialog for BYE
with route param 'a5d.ebf1' [3418:8126] and call-id
'SDiu98001-dd9c12fea650b9d1408dd672a2c51c9f-v300g00020'
Mar 4 08:21:56 /usr/sbin/kamailio[14315]: WARNING: dialog
[dlg_handlers.c:1328]: dlg_onroute(): unable to find dialog for ACK
with route param '689.f2f1' [2438:7983] and call-id
'SD8o63c01-47972a87ee1fd8791ddf27b650badcba-v300g00010'
Kamailio 2 node prints lot of this:
Mar 4 08:20:29 /usr/sbin/kamailio[8005]: NOTICE: dialog
[dlg_hash.c:242]: dlg_clean_run(): dialog in early state is too old
(0x7fe07b84e980 ref 1)
Mar 4 08:20:29 /usr/sbin/kamailio[8005]: NOTICE: dialog
[dlg_hash.c:242]: dlg_clean_run(): dialog in early state is too old
(0x7fe07bb03360 ref 1)
Mar 4 08:21:59 /usr/sbin/kamailio[8005]: NOTICE: dialog
[dlg_hash.c:242]: dlg_clean_run(): dialog in early state is too old
(0x7fe07b528300 ref 1)
(Version: kamailio 5.5.3 (x86_64/linux) 473cef on both kamailio nodes)
[root@kamailio-1]# kamcmd dmq.list_nodes
{
host: 172.19.194.140
port: 5060
proto: *
resolved_ip: 172.19.194.140
status: active
last_notification: 0
local: 0
}
{
host: 172.19.194.132
port: 5060
proto: *
resolved_ip: 172.19.194.132
status: active
last_notification: 0
local: 1
}
[root@kamailio-2]# kamcmd dmq.list_nodes
{
host: 172.19.194.132
port: 5060
proto: *
resolved_ip: 172.19.194.132
status: active
last_notification: 0
local: 0
}
{
host: 172.19.194.140
port: 5060
proto: *
resolved_ip: 172.19.194.140
status: active
last_notification: 0
local: 1
}
### On Kamailio 1: ###
#!define DMQ_LOCAL_ADDR "sip:172.19.194.132:5060"
#!define DMQ_PEER_ADDR "sip:172.19.194.140:5060"
### On Kamailio 2: ###
#!define DMQ_LOCAL_ADDR "sip:172.19.194.140:5060"
#!define DMQ_PEER_ADDR "sip:172.19.194.132:5060"
### On Kamailio 1 & 2:###
modparam("dmq", "server_address", DMQ_LOCAL_ADDR)
modparam("dmq", "notification_address", DMQ_PEER_ADDR)
modparam("dialog", "profiles_with_value", "total_dialogs")
modparam("dialog", "enable_dmq", 1)
route[INITIAL] {
...located at the bottom of the initial route...
if(is_method("INVITE") && !has_totag()) {
dlg_manage();
}
}
Cheers,
Olli
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Online
March 28-31, 2022 (Europe Timezone)
* https://www.asipto.com/sw/kamailio-advanced-training-online/
22 Mar
22 Mar
8:46 a.m.
Hello,
Try to run with debug=3 as well as
watch the dmq traffic between servers to be sure that dialogs states are
updated based on sip requests/responses belonging to the same calls.
I tried running debug=3 on the other server with the following command
but I suspect it generated too much load because the server got
unresponsive after a while and I had to turn off the debug:
"kamcmd cfg.set_now_int core debug 3"
I searched calls on the time window when the "dlg_clean_run(): dialog
in early state is too old" -messages were appearing in the log, and
noticed some calls that were on the early stage quite some time. The
early stage lasted about 40seconds. Could this trigger the alarms and
is there any way to adjust the timers if that is the case here? The
target is a PSTN gateway so its quite normal that sometimes there is a
longer period of time when we try to reach the B party. Also it would
be nice to confirm this via the proposed debug logging, but with less
impact generally on the server calls. Maby there is a way to just
debug the dialog module itself and not the whole core ?
Cheers,
Olli Attila
pe 11. maalisk. 2022 klo 14.48 Daniel-Constantin Mierla
(miconda(a)gmail.com) kirjoitti:
Hello,
the log:
... dlg_clean_run(): dialog in early state is too old
indicates that the dialog was not confirmed and its corresponding
structure is going to be destroyed. Try to run with debug=3 as well as
watch the dmq traffic between servers to be sure that dialogs states are
updated based on sip requests/responses belonging to the same calls.
Cheers,
Daniel
On 04.03.22 07:55, Olli Attila wrote:
--
Terveisin,
Olli Attila, p.+358440442300, attiolli(a)gmail.com
Hello,
I have two Kamailio nodes. Couple of days of ago I enabled dmq to
replicate dialogs between these two Kamailio nodes. Now that the dmq
is enabled, we are seeing lot of warning and notice messages on
kamailio logs related to the dialog module. Is there something I have
missed when configuring dlg_manage & dmq replication that might cause
this? No calls have been affected negatively by this though.
Kamailio 1 node prints lot of this:
Mar 4 08:20:25 /usr/sbin/kamailio[14316]: WARNING: dialog
[dlg_handlers.c:1328]: dlg_onroute(): unable to find dialog for ACK
with route param 'a5d.ebf1' [3418:8126] and call-id
'SDiu98001-dd9c12fea650b9d1408dd672a2c51c9f-v300g00020'
Mar 4 08:20:28 /usr/sbin/kamailio[14313]: WARNING: dialog
[dlg_handlers.c:1328]: dlg_onroute(): unable to find dialog for BYE
with route param 'a5d.ebf1' [3418:8126] and call-id
'SDiu98001-dd9c12fea650b9d1408dd672a2c51c9f-v300g00020'
Mar 4 08:21:56 /usr/sbin/kamailio[14315]: WARNING: dialog
[dlg_handlers.c:1328]: dlg_onroute(): unable to find dialog for ACK
with route param '689.f2f1' [2438:7983] and call-id
'SD8o63c01-47972a87ee1fd8791ddf27b650badcba-v300g00010'
Kamailio 2 node prints lot of this:
Mar 4 08:20:29 /usr/sbin/kamailio[8005]: NOTICE: dialog
[dlg_hash.c:242]: dlg_clean_run(): dialog in early state is too old
(0x7fe07b84e980 ref 1)
Mar 4 08:20:29 /usr/sbin/kamailio[8005]: NOTICE: dialog
[dlg_hash.c:242]: dlg_clean_run(): dialog in early state is too old
(0x7fe07bb03360 ref 1)
Mar 4 08:21:59 /usr/sbin/kamailio[8005]: NOTICE: dialog
[dlg_hash.c:242]: dlg_clean_run(): dialog in early state is too old
(0x7fe07b528300 ref 1)
(Version: kamailio 5.5.3 (x86_64/linux) 473cef on both kamailio nodes)
[root@kamailio-1]# kamcmd dmq.list_nodes
{
host: 172.19.194.140
port: 5060
proto: *
resolved_ip: 172.19.194.140
status: active
last_notification: 0
local: 0
}
{
host: 172.19.194.132
port: 5060
proto: *
resolved_ip: 172.19.194.132
status: active
last_notification: 0
local: 1
}
[root@kamailio-2]# kamcmd dmq.list_nodes
{
host: 172.19.194.132
port: 5060
proto: *
resolved_ip: 172.19.194.132
status: active
last_notification: 0
local: 0
}
{
host: 172.19.194.140
port: 5060
proto: *
resolved_ip: 172.19.194.140
status: active
last_notification: 0
local: 1
}
### On Kamailio 1: ###
#!define DMQ_LOCAL_ADDR "sip:172.19.194.132:5060"
#!define DMQ_PEER_ADDR "sip:172.19.194.140:5060"
### On Kamailio 2: ###
#!define DMQ_LOCAL_ADDR "sip:172.19.194.140:5060"
#!define DMQ_PEER_ADDR "sip:172.19.194.132:5060"
### On Kamailio 1 & 2:###
modparam("dmq", "server_address", DMQ_LOCAL_ADDR)
modparam("dmq", "notification_address", DMQ_PEER_ADDR)
modparam("dialog", "profiles_with_value", "total_dialogs")
modparam("dialog", "enable_dmq", 1)
route[INITIAL] {
...located at the bottom of the initial route...
if(is_method("INVITE") && !has_totag()) {
dlg_manage();
}
}
Cheers,
Olli
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
* sr-users(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to the sender!
Edit mailing list options or unsubscribe:
* https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - Online
March 28-31, 2022 (Europe Timezone)
* https://www.asipto.com/sw/kamailio-advanced-training-online/
978
days inactive
996
days old
2 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
Olli Attila