Hello Henning, althugh I don't think this will help, because every DMQ Request has a unique call id, I will give it a try. But in my understanding, this paramater just helps ordering the packets within the same callid.
I'll report back as soon as I'm done with testing. With best regards, Björn Am 19.09.25 um 15:41 schrieb Henning Westerholt: Hello Björn, right now, this is not possible to configure, you are right. The DMQ workers are shared and just processing all the different messages for it randomly depending on the Linux scheduler. So, it can happen, as you observed, that the order of some messages is not correct. Thinking about it, the better modification might be to somehow order the requests before they are processed from the DMQ workers. I am not sure if it will help, but worth a try nevertheless – please set this option: https://www.kamailio.org/wikidocs/cookbooks/5.8.x/core/#route_locks_size See if it maybe helps with the message ordering also in the DMQ case. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: Björn Klasen via sr-users <[email protected]><mailto:[email protected]> Sent: Donnerstag, 18. September 2025 11:26 To: [email protected]<mailto:[email protected]> Cc: Björn Klasen <[email protected]><mailto:[email protected]> Subject: [SR-Users] Proposal for a more granular configuration of DMQ Hello I'm testing a lot with DMQ and its possibilities for replicating data between several nodes. We also use DMQ in production for replicating usrloc, htable and dialog. So far so good. But in my log I regularly see the following message: ERROR: dialog [dlg_dmq.c:293]: dlg_dmq_handle_msg(): dialog [22051:221142] not found As I tried to troubleshoot this message I discovered the following: On network everything is OK. The KDMQ messages are sent and received in the correct order. But they are not processed by the DMQ system in Kamailio in the correct order. It might happen that the dialog KDMQ message for the initial INVITE is not processed before the KDMQ message for the provisional response. I repeated the tests in my lab with different number of workers for DMQ. But after I set the number of workers to 1 everything seems to be fine. But now comes the problem. As I mentioned, we also replicate htable between the nodes, so we can use all nodes as hot standby. If I raise the CPS one worker is not enough to handle htable and dialog and userloc. So I thought it might be cool to have the possibility to set the amount of worker for the modules separately. So I would just use one worker for dialog and all other workers for any other modules that use DMQ because in my opinion dialog is the only thing where the order of the KDQM messages matters. As I'm not capable of programming things like that I wanted just put this a think for further developments of DMQ. I'm really looking forward to your thoughts about this. With best regards from northern Germany Björn -- Björn Klasen, Teamleitung NGN VoIP-Backbone TNG Stadtnetz GmbH, TNG-Technik Gerhard-Fröhler-Straße 12 24106 Kiel・Deutschland T +49 431 7097-10 F +49 431 7097-555 [email protected]<mailto:[email protected]> https://www.tng.de Executive board (Geschäftsführer): Dr. Sven Willert (CEO), Sabine Domes, Gunnar Peter, Bernd Sontheimer Amtsgericht Kiel HRB 6002 KI USt-ID: DE225201428 Die Information über die Verarbeitung Ihrer Daten gemäß Artikel 13 DSGVO können Sie unter https://www.tng.de/datenschutz/ abrufen. ______________________________________________________________________ -- Björn Klasen, Teamleitung NGN VoIP-Backbone TNG Stadtnetz GmbH, TNG-Technik Gerhard-Fröhler-Straße 12 24106 Kiel・Deutschland T +49 431 7097-10 F +49 431 7097-555 [email protected]<mailto:[email protected]> https://www.tng.de Executive board (Geschäftsführer): Dr. Sven Willert (CEO), Sabine Domes, Gunnar Peter, Bernd Sontheimer Amtsgericht Kiel HRB 6002 KI USt-ID: DE225201428 Die Information über die Verarbeitung Ihrer Daten gemäß Artikel 13 DSGVO können Sie unter https://www.tng.de/datenschutz/ abrufen. ______________________________________________________________________
__________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected] To unsubscribe send an email to [email protected] Important: keep the mailing list in the recipients, do not reply only to the sender!
