Forgot to mention I am using version 5.2.2.

# kamailio -v
version: kamailio 5.2.2 (x86_64/linux) 67f967
flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144 MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: 67f967
compiled on 11:40:41 Mar 11 2019 with gcc 4.8.5

On Tue, 28 May 2019 at 16:26, Patrick Wakano <pwakano@gmail.com> wrote:

Hello list,
Hope you all doing well!

I am trying to use the extra attributes (xavp_contact) of the usrloc module to save some additional info about the user.
I am setting the value before the save() and doing a call to registered() (not lookup()) before trying to access these extra attributes. This works fine with db_mode=3 but does not work in case of db_mode=0.
Does anyone knows if it should also work with mode 0? I was expecting it to work but a call to kamcmd ul.dump show nothing related.....
I don't want to use the DB for the location purposes because I prefer to have multiple servers using the dmq_usrloc (that works like a charm!) and it conflicts with DB persistence of the location table (when the DMQ replication happens, all servers (sharing the same DB) try to save the same user info in the location table)

Thank you,
Kind regards,
Patrick Wakano