[SR-Users] dmq_usrloc writes to database on other nodes too

Henning Westerholt hw at skalatan.de
Sun Oct 17 13:16:07 CEST 2021


already tried to configure the usrloc/registrar modules in memory-only mode?




Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com<https://gilawa.com/>

From: sr-users <sr-users-bounces at lists.kamailio.org> On Behalf Of Maarten Ureel
Sent: Friday, October 15, 2021 10:38 AM
To: sr-users at lists.kamailio.org
Subject: [SR-Users] dmq_usrloc writes to database on other nodes too

I have the idea that if you enable dmq_usrloc, the other nodes that receive the usrloc info, also try to write to database.
We see this by a lot of errors indicating the index violation on postgres.

What is the easiest way to tell Kamailio that it does not need to store the usrloc in database if the data came through a DMQ message?

Currently I have in my config:
    # DMQ processing
    if(is_method("KDMQ") && $Rp == 5090) {

I have understood that no further processing happens then. So is my assumption correct that my other handling of REGISTER will not be used then?

As in, can you handle this in code that it will only store the register information in memory? Like this?

# Registration handling
route[REGISTRAR] {
    # If coming from DMQ, don't save to database
    if(dmq_is_from_node()) {
        save("location", "0x01")
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20211017/57432e8c/attachment.htm>

More information about the sr-users mailing list