Re: [SR-Users] Dialog and DMQ on restart

[Björn Klasen]

I have been done some tests today. I found out, that if I do a 'service 
kamailio stop' and wait some time, like 30 seconds, and the do a 
'service kamailio start' everythings works like expected. The dialogs 
are resynced.

If I do a 'service kamailio restart' or do not wait long enough it 
doesn't work and no dialogs are resynced

BR, Björn

Am 29.09.20 um 10:30 schrieb Björn Klasen:
Hi Daniel,

of course I can.

This is the trace from node 1 where dialog is established. But after 
the restart I do not get any data on the KDMQ-request

U 2020/09/29 10:21:43.460005 192.168.253.78:5062 -> 192.168.253.77:5062

KDMQ sip:dialog@192.168.253.77:5062 SIP/2.0.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bKfa25.8d452755000000000000000000000000.0.
To: <sip:dialog@192.168.253.77:5062>.
From: 
<sip:dialog@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-2dc1b109.
CSeq: 10 KDMQ.
Call-ID: 541587cc358b30a7-31951@127.0.0.1.
Content-Length: 358.
User-Agent: kamailio (5.4.1 (x86_64/linux)).
Max-Forwards: 1.
Content-Type: application/json.
.
{"action":2,"h_entry":106340,"h_id":370791,"state":4,"start_ts":1601367703,"lifetime":43900,"tag1":"bc144488-32e1-44ce-88b0-8b0b9f156a24","tag2":"3854cf57-4d3a-4313-a3f2-b68f0a65810a","cseq1":"27196","cseq2":"0","route_set1":"","route_set2":"","contact1":"sip:43190899250-qrhsodhehkl28@192.168.253.60:5060;transport=udp","contact2":"sip:192.168.253.30:5060"} 


U 2020/09/29 10:21:43.460718 192.168.253.77:5062 -> 192.168.253.78:5062

SIP/2.0 200 OK.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bKfa25.8d452755000000000000000000000000.0.
To: 
<sip:dialog@192.168.253.77:5062>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.1adaf2d0.
From: 
<sip:dialog@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-2dc1b109.
CSeq: 10 KDMQ.
Call-ID: 541587cc358b30a7-31951@127.0.0.1.
Server: kamailio (5.4.1 (x86_64/linux)).
Content-Length: 0.
.

Unknown METHOD: KDMQ

U 2020/09/29 10:21:47.619814 192.168.253.77:5062 -> 192.168.253.78:5062

KDMQ sip:notification_peer@192.168.253.78:5062 SIP/2.0.
Via: SIP/2.0/UDP 
192.168.253.77:5062;branch=z9hG4bKc793.db7266f7000000000000000000000000.0.
To: <sip:notification_peer@192.168.253.78:5062>.
From: 
<sip:notification_peer@192.168.253.77:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-65cfbaf9.
CSeq: 10 KDMQ.
Call-ID: 74df875f559812b9-32477@127.0.0.1.
Content-Length: 78.
User-Agent: kamailio (5.4.1 (x86_64/linux)).
Max-Forwards: 1.
Content-Type: text/plain.
.
sip:192.168.253.78:5062;status=active.
sip:192.168.253.77:5062;status=active.


U 2020/09/29 10:21:47.620213 192.168.253.78:5062 -> 192.168.253.77:5062

SIP/2.0 200 OK.
Via: SIP/2.0/UDP 
192.168.253.77:5062;branch=z9hG4bKc793.db7266f7000000000000000000000000.0.
To: 
<sip:notification_peer@192.168.253.78:5062>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.d57c8d5f.
From: 
<sip:notification_peer@192.168.253.77:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-65cfbaf9.
CSeq: 10 KDMQ.
Call-ID: 74df875f559812b9-32477@127.0.0.1.
Content-Type: text/plain.
Server: kamailio (5.4.1 (x86_64/linux)).
Content-Length: 78.
.
sip:192.168.253.77:5062;status=active.
sip:192.168.253.78:5062;status=active.

Unknown METHOD: KDMQ

U 2020/09/29 10:21:52.111632 192.168.253.78:5062 -> 192.168.253.77:5062

KDMQ sip:notification_peer@192.168.253.77:5062 SIP/2.0.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bKa585.912f98f3000000000000000000000000.0.
To: <sip:notification_peer@192.168.253.77:5062>.
From: 
<sip:notification_peer@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-3209222a.
CSeq: 10 KDMQ.
Call-ID: 541587cc358b30a5-31933@127.0.0.1.
Content-Length: 80.
User-Agent: kamailio (5.4.1 (x86_64/linux)).
Max-Forwards: 1.
Content-Type: text/plain.
.
sip:192.168.253.77:5062;status=active.
sip:192.168.253.78:5062;status=disabled.


U 2020/09/29 10:21:52.112395 192.168.253.77:5062 -> 192.168.253.78:5062

SIP/2.0 200 OK.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bKa585.912f98f3000000000000000000000000.0.
To: 
<sip:notification_peer@192.168.253.77:5062>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.1adaf2d0.
From: 
<sip:notification_peer@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-3209222a.
CSeq: 10 KDMQ.
Call-ID: 541587cc358b30a5-31933@127.0.0.1.
Content-Type: text/plain.
Server: kamailio (5.4.1 (x86_64/linux)).
Content-Length: 39.
.
sip:192.168.253.77:5062;status=active.

Unknown METHOD: KDMQ

U 2020/09/29 10:21:52.941401 192.168.253.78:5062 -> 192.168.253.77:5062

KDMQ sip:notification_peer@192.168.253.77:5062 SIP/2.0.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bK82ce.01773554000000000000000000000000.0.
To: <sip:notification_peer@192.168.253.77:5062>.
From: 
<sip:notification_peer@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-58e2222a.
CSeq: 10 KDMQ.
Call-ID: 535736740ae50ad1-32108@127.0.0.1.
Content-Length: 39.
User-Agent: kamailio (5.4.1 (x86_64/linux)).
Max-Forwards: 2.
Content-Type: text/plain.
.
sip:192.168.253.78:5062;status=active.


U 2020/09/29 10:21:52.942045 192.168.253.77:5062 -> 192.168.253.78:5062

SIP/2.0 200 OK.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bK82ce.01773554000000000000000000000000.0.
To: 
<sip:notification_peer@192.168.253.77:5062>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.1adaf2d0.
From: 
<sip:notification_peer@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-58e2222a.
CSeq: 10 KDMQ.
Call-ID: 535736740ae50ad1-32108@127.0.0.1.
Content-Type: text/plain.
Server: kamailio (5.4.1 (x86_64/linux)).
Content-Length: 39.
.
sip:192.168.253.77:5062;status=active.

Unknown METHOD: KDMQ

U 2020/09/29 10:21:55.676577 192.168.253.78:5062 -> 192.168.253.77:5062

KDMQ sip:dialog@192.168.253.77:5062 SIP/2.0.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bKae4c.d5cf8a73000000000000000000000000.0.
To: <sip:dialog@192.168.253.77:5062>.
From: 
<sip:dialog@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-505cb109.
CSeq: 10 KDMQ.
Call-ID: 535736740ae50ad1-32121@127.0.0.1.
Content-Length: 12.
User-Agent: kamailio (5.4.1 (x86_64/linux)).
Max-Forwards: 1.
Content-Type: application/json.
.
{"action":4}
Unknown METHOD: KDMQ

U 2020/09/29 10:21:55.677061 192.168.253.78:5062 -> 192.168.253.77:5062

KDMQ sip:usrloc@192.168.253.77:5062 SIP/2.0.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bK7e4c.c1d43f46000000000000000000000000.0.
To: <sip:usrloc@192.168.253.77:5062>.
From: 
<sip:usrloc@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-415f0782.
CSeq: 10 KDMQ.
Call-ID: 535736740ae50ad2-32121@127.0.0.1.
Content-Length: 12.
User-Agent: kamailio (5.4.1 (x86_64/linux)).
Max-Forwards: 1.
Content-Type: application/json.
.
{"action":3}

U 2020/09/29 10:21:55.690119 192.168.253.77:5062 -> 192.168.253.78:5062

SIP/2.0 200 OK.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bKae4c.d5cf8a73000000000000000000000000.0.
To: 
<sip:dialog@192.168.253.77:5062>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.1adaf2d0.
From: 
<sip:dialog@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-505cb109.
CSeq: 10 KDMQ.
Call-ID: 535736740ae50ad1-32121@127.0.0.1.
Server: kamailio (5.4.1 (x86_64/linux)).
Content-Length: 0.
.

This is the trace of the second node. It received the dialog 
information of the first node but do not give any dialog information 
over DMQ after node 1 ist restarted, although there a confirmed 
message from node 1 that it is active again.

U 2020/09/29 10:21:43.460461 192.168.253.78:5062 -> 192.168.253.77:5062

KDMQ sip:dialog@192.168.253.77:5062 SIP/2.0.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bKfa25.8d452755000000000000000000000000.0.
To: <sip:dialog@192.168.253.77:5062>.
From: 
<sip:dialog@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-2dc1b109.
CSeq: 10 KDMQ.
Call-ID: 541587cc358b30a7-31951@127.0.0.1.
Content-Length: 358.
User-Agent: kamailio (5.4.1 (x86_64/linux)).
Max-Forwards: 1.
Content-Type: application/json.
.
{"action":2,"h_entry":106340,"h_id":370791,"state":4,"start_ts":1601367703,"lifetime":43900,"tag1":"bc144488-32e1-44ce-88b0-8b0b9f156a24","tag2":"3854cf57-4d3a-4313-a3f2-b68f0a65810a","cseq1":"27196","cseq2":"0","route_set1":"","route_set2":"","contact1":"sip:43190899250-qrhsodhehkl28@192.168.253.60:5060;transport=udp","contact2":"sip:192.168.253.30:5060"} 


U 2020/09/29 10:21:43.460918 192.168.253.77:5062 -> 192.168.253.78:5062

SIP/2.0 200 OK.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bKfa25.8d452755000000000000000000000000.0.
To: 
<sip:dialog@192.168.253.77:5062>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.1adaf2d0.
From: 
<sip:dialog@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-2dc1b109.
CSeq: 10 KDMQ.
Call-ID: 541587cc358b30a7-31951@127.0.0.1.
Server: kamailio (5.4.1 (x86_64/linux)).
Content-Length: 0.
.

Unknown METHOD: KDMQ

U 2020/09/29 10:21:47.620025 192.168.253.77:5062 -> 192.168.253.78:5062

KDMQ sip:notification_peer@192.168.253.78:5062 SIP/2.0.
Via: SIP/2.0/UDP 
192.168.253.77:5062;branch=z9hG4bKc793.db7266f7000000000000000000000000.0.
To: <sip:notification_peer@192.168.253.78:5062>.
From: 
<sip:notification_peer@192.168.253.77:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-65cfbaf9.
CSeq: 10 KDMQ.
Call-ID: 74df875f559812b9-32477@127.0.0.1.
Content-Length: 78.
User-Agent: kamailio (5.4.1 (x86_64/linux)).
Max-Forwards: 1.
Content-Type: text/plain.
.
sip:192.168.253.78:5062;status=active.
sip:192.168.253.77:5062;status=active.


U 2020/09/29 10:21:47.620647 192.168.253.78:5062 -> 192.168.253.77:5062

SIP/2.0 200 OK.
Via: SIP/2.0/UDP 
192.168.253.77:5062;branch=z9hG4bKc793.db7266f7000000000000000000000000.0.
To: 
<sip:notification_peer@192.168.253.78:5062>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.d57c8d5f.
From: 
<sip:notification_peer@192.168.253.77:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-65cfbaf9.
CSeq: 10 KDMQ.
Call-ID: 74df875f559812b9-32477@127.0.0.1.
Content-Type: text/plain.
Server: kamailio (5.4.1 (x86_64/linux)).
Content-Length: 78.
.
sip:192.168.253.77:5062;status=active.
sip:192.168.253.78:5062;status=active.

Unknown METHOD: KDMQ

U 2020/09/29 10:21:52.112089 192.168.253.78:5062 -> 192.168.253.77:5062

KDMQ sip:notification_peer@192.168.253.77:5062 SIP/2.0.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bKa585.912f98f3000000000000000000000000.0.
To: <sip:notification_peer@192.168.253.77:5062>.
From: 
<sip:notification_peer@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-3209222a.
CSeq: 10 KDMQ.
Call-ID: 541587cc358b30a5-31933@127.0.0.1.
Content-Length: 80.
User-Agent: kamailio (5.4.1 (x86_64/linux)).
Max-Forwards: 1.
Content-Type: text/plain.
.
sip:192.168.253.77:5062;status=active.
sip:192.168.253.78:5062;status=disabled.


U 2020/09/29 10:21:52.112590 192.168.253.77:5062 -> 192.168.253.78:5062

SIP/2.0 200 OK.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bKa585.912f98f3000000000000000000000000.0.
To: 
<sip:notification_peer@192.168.253.77:5062>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.1adaf2d0.
From: 
<sip:notification_peer@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-3209222a.
CSeq: 10 KDMQ.
Call-ID: 541587cc358b30a5-31933@127.0.0.1.
Content-Type: text/plain.
Server: kamailio (5.4.1 (x86_64/linux)).
Content-Length: 39.
.
sip:192.168.253.77:5062;status=active.

Unknown METHOD: KDMQ

U 2020/09/29 10:21:52.941834 192.168.253.78:5062 -> 192.168.253.77:5062

KDMQ sip:notification_peer@192.168.253.77:5062 SIP/2.0.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bK82ce.01773554000000000000000000000000.0.
To: <sip:notification_peer@192.168.253.77:5062>.
From: 
<sip:notification_peer@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-58e2222a.
CSeq: 10 KDMQ.
Call-ID: 535736740ae50ad1-32108@127.0.0.1.
Content-Length: 39.
User-Agent: kamailio (5.4.1 (x86_64/linux)).
Max-Forwards: 2.
Content-Type: text/plain.
.
sip:192.168.253.78:5062;status=active.


U 2020/09/29 10:21:52.942257 192.168.253.77:5062 -> 192.168.253.78:5062

SIP/2.0 200 OK.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bK82ce.01773554000000000000000000000000.0.
To: 
<sip:notification_peer@192.168.253.77:5062>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.1adaf2d0.
From: 
<sip:notification_peer@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-58e2222a.
CSeq: 10 KDMQ.
Call-ID: 535736740ae50ad1-32108@127.0.0.1.
Content-Type: text/plain.
Server: kamailio (5.4.1 (x86_64/linux)).
Content-Length: 39.
.
sip:192.168.253.77:5062;status=active.

Unknown METHOD: KDMQ

U 2020/09/29 10:21:55.677014 192.168.253.78:5062 -> 192.168.253.77:5062

KDMQ sip:dialog@192.168.253.77:5062 SIP/2.0.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bKae4c.d5cf8a73000000000000000000000000.0.
To: <sip:dialog@192.168.253.77:5062>.
From: 
<sip:dialog@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-505cb109.
CSeq: 10 KDMQ.
Call-ID: 535736740ae50ad1-32121@127.0.0.1.
Content-Length: 12.
User-Agent: kamailio (5.4.1 (x86_64/linux)).
Max-Forwards: 1.
Content-Type: application/json.
.
{"action":4}
Unknown METHOD: KDMQ

U 2020/09/29 10:21:55.677509 192.168.253.78:5062 -> 192.168.253.77:5062

KDMQ sip:usrloc@192.168.253.77:5062 SIP/2.0.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bK7e4c.c1d43f46000000000000000000000000.0.
To: <sip:usrloc@192.168.253.77:5062>.
From: 
<sip:usrloc@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-415f0782.
CSeq: 10 KDMQ.
Call-ID: 535736740ae50ad2-32121@127.0.0.1.
Content-Length: 12.
User-Agent: kamailio (5.4.1 (x86_64/linux)).
Max-Forwards: 1.
Content-Type: application/json.
.
{"action":3}

U 2020/09/29 10:21:55.690306 192.168.253.77:5062 -> 192.168.253.78:5062

SIP/2.0 200 OK.
Via: SIP/2.0/UDP 
192.168.253.78:5062;branch=z9hG4bKae4c.d5cf8a73000000000000000000000000.0.
To: 
<sip:dialog@192.168.253.77:5062>;tag=9dd61ff61e802d8e2bef5f14621ef3c2.1adaf2d0.
From: 
<sip:dialog@192.168.253.78:5062>;tag=3393f0703fb0ccaca74109ff37de39f5-505cb109.
CSeq: 10 KDMQ.
Call-ID: 535736740ae50ad1-32121@127.0.0.1.
Server: kamailio (5.4.1 (x86_64/linux)).
Content-Length: 0.
.

Unknown METHOD: KDMQ


BR, Björn


Am 29.09.20 um 09:40 schrieb Daniel-Constantin Mierla:
Hello,

can you capture the sip traffic on the network and see what traffic is
sent between the two nodes?

Cheers,
Daniel

On 28.09.20 15:15, Björn Klasen wrote:
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

--
Björn Klasen, Specialist
TNG Stadtnetz GmbH, Network Management (VoIP)
Projensdorfer Straße 324
24106 Kiel
Germany

T +49 431/ 530530
F +49 431/ 7097-555
mailto: bkla...@tng.de
http://www.tng.de

Register: Amtsgericht Kiel HRB 6002 KI
Executive board (Geschäftsführung): Dr.-Ing. Volkmar Hausberg,
Sven Schade, Carsten Tolkmit, Dr. Sven Willert
Tax-Id (Steuernr.): 2029047020, VAT-Id (USt-Id): DE225201428


_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

--
Björn Klasen, Specialist
TNG Stadtnetz GmbH, Network Management (VoIP)
Projensdorfer Straße 324
24106 Kiel
Germany

T +49 431/ 530530
F +49 431/ 7097-555
mailto: bkla...@tng.de
http://www.tng.de

Register: Amtsgericht Kiel HRB 6002 KI
Executive board (Geschäftsführung): Dr.-Ing. Volkmar Hausberg,
Sven Schade, Carsten Tolkmit, Dr. Sven Willert
Tax-Id (Steuernr.): 2029047020, VAT-Id (USt-Id): DE225201428


_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users