[SR-Users] Dialog module errors with dmq

Olli Attila attiolli at gmail.com
Fri Mar 4 07:55:58 CET 2022


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 at 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 at 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



More information about the sr-users mailing list