Hi Carsten,
a starting point could be:
modparam("db_redis", "keys",
"pua=entry:etag&pres:pres_id,pres_uri”)
I’ve tested it on Kamailio 5.3.3, with default schema definition:
# cat /etc/kamailio/db_redis/kamailio/pua
id/int,pres_uri/string,pres_id/string,event/int,expires/int,desired_expires/int,flag/int,etag/string,tuple_id/string,watcher_uri/string,call_id/string,to_tag/string,from_tag/string,cseq/int,record_route/string,contact/string,remote_contact/string,version/int,extra_headers/string,
7
and it seems to do the right thing, e.g. with having:
modparam("pua", "db_url", "redis://localhost:6379/42”)
modparam("pua", "db_table", "pua")
modparam("pua", "db_mode", 2)
modparam("pua", "db_table_lock_write", 0)
the changes to database are reflected immediately, i.e. my dialoginfo and reginfo records
are being written.
I have not checked yet what is the most efficient index structure for the pua but the BLF
is working with db_redis for me.
Hope this helps,
Andrew
On 19.03.2020, at 13:04, Carsten Bock
<carsten(a)ng-voice.com> wrote:
Hi,
quick question:
Did anyone ever attempt to use PUA with the new db_redis? If yes, could someone share the
definition for this?
Thanks,
Carsten
--
Carsten Bock I CTO & Founder
ng-voice GmbH
Trostbrücke 1 I 20457 Hamburg I Germany
T +49 40 524 75 93-40 | M +49 179 2021244 I
www.ng-voice.com
<http://www.ng-voice.com/>
Registry Office at Local Court Hamburg, HRB 120189
Managing Directors: Dr. David Bachmann, Carsten Bock
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users