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

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 List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla -- www.asipto.com
www.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