I think the node is still marked as inactive although it send a request for dialog data. Some lines bevor the skipping lines
Sep 28 15:01:45 voip-lab-proxy02 /usr/sbin/kamailio[28828]: DEBUG: dmq [message.c:50]: ki_dmq_handle_message_rc(): dmq_handle_message [KDMQ sip:dialog@192.168.253.77:5062] Sep 28 15:01:45 voip-lab-proxy02 /usr/sbin/kamailio[28828]: DEBUG: dmq [message.c:65]: ki_dmq_handle_message_rc(): dmq_handle_message peer found: dialog
Am 28.09.20 um 15:07 schrieb Björn Klasen:
Hi just had a log in debug log of the secondary node.
Here I found the following lines
Sep 28 15:01:45 voip-lab-proxy02 /usr/sbin/kamailio[28835]: DEBUG: dialog [dlg_dmq.c:87]: dlg_dmq_send(): sending dmq broadcast... Sep 28 15:01:45 voip-lab-proxy02 /usr/sbin/kamailio[28835]: DEBUG: dmq [dmq_funcs.c:166]: bcast_dmq_message1(): skipping node sip:192.168.253.78:5062 Sep 28 15:01:45 voip-lab-proxy02 /usr/sbin/kamailio[28835]: DEBUG: dmq [dmq_funcs.c:166]: bcast_dmq_message1(): skipping node sip:192.168.253.77:5062
But why does it skip the first node (IP 192.168.253.78)?
Am 28.09.20 um 14:47 schrieb Björn Klasen:
Hi everybody,
I'm just testing Kamailio 5.4.1 with dialog replication over DMQ. This seems to work very good. Dialogs are replicated without problems.
When I'm restarting one node I would have expected, that all dialogs are synced again, just like in dmq_usrloc.
But this does not happen. After a restart the nodes dialog-list is empty.
Did I miss somethin? Is there a special parameter that I have to set?
BR, Björn