Hi Daniel,

Thank you very much for that information. The system is using an old version of Kamailio, so we'll suggest the owner upgrades in order to get the patches.

On 19 September 2018 at 21:29, Daniel-Constantin Mierla miconda@gmail.com wrote:

Hello,

that's generated internally, based on some attributes such as pid, startup timestamp, counter... If you ahave many kamailio instances writing to same db, then you have to set server_id global parameter so it is used in ruid and avoids some (very rare) potential conflicts.

If it is a single kamailio instance, then maybe a db operation failed in the middle (e.g., when it was a restart of db server) and the state in memory is not sync'ed with the db. You can remove the record from db.

I also pushed small patches to register/usrloc to use a safer version of ruid generation on a single instance, to cover cases when someone forks its own processes (not via kamailio code).

Cheers, Daniel

On 18.09.18 01:33, David Cunningham wrote:

Hello,

We are debugging an issue with location records having duplicate "ruid" values, which aren't allowed by the table index. Can anyone tell us where the "ruid" value comes from? Is it a function of some other variable?

Thanks in advance,

-- David Cunningham, Voisonics Limited http://voisonics.com/ USA: +1 213 221 1092 New Zealand: +64 (0)28 2558 3782

---

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

-- Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference -- www.kamailioworld.com Kamailio Advanced Training, Nov 12-14, 2018, in Berlin -- www.asipto.com