Daniel,
I studied a bit topos_redis source and noticed that it lacks x_context td and tt keys.
Is there something else missing in order to make spirals work also when redis backend is in use?
-- Juha
On 30.04.21 15:51, Juha Heinanen wrote:
Daniel,
I studied a bit topos_redis source and noticed that it lacks x_context td and tt keys.
Is there something else missing in order to make spirals work also when redis backend is in use?
The concept is a bit different for topos_redis on how the data is structured and indexed, I didn't get the time yet to look at it and see what is missing.
The idea was to try to optimize and tailor it for redis specific operation, otherwise you can try with topos+db_redis, which should give a more SQL-like approach and the columns in mysql tables should appear as attributes inside redis db. The db_redis was added after topos_redis, being generic and should be capable of replacing other db_* modules.
Cheers, Daniel
Daniel-Constantin Mierla writes:
The idea was to try to optimize and tailor it for redis specific operation, otherwise you can try with topos+db_redis, which should give a more SQL-like approach and the columns in mysql tables should appear as attributes inside redis db. The db_redis was added after topos_redis, being generic and should be capable of replacing other db_* modules.
There exists topos_d and topos_t schema files in /usr/share/kamailio/db_redis/kamailio directory, but is it also necessary to define "keys" parameters for these tables?
-- Juha
On 30.04.21 17:48, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
The idea was to try to optimize and tailor it for redis specific operation, otherwise you can try with topos+db_redis, which should give a more SQL-like approach and the columns in mysql tables should appear as attributes inside redis db. The db_redis was added after topos_redis, being generic and should be capable of replacing other db_* modules.
There exists topos_d and topos_t schema files in /usr/share/kamailio/db_redis/kamailio directory, but is it also necessary to define "keys" parameters for these tables?
I think the keys are useful to avoid full table scan, but I am not that familiar with db_redis to comment more.
Regarding topos_redis, I just pushed a commit to it in master branch, can you give it another try?
Cheers, Daniel
Daniel-Constantin Mierla writes:
Regarding topos_redis, I just pushed a commit to it in master branch, can you give it another try?
Still when A receives 183 Session Progress from P1 and send PRACK, P1 rejects it with 404 Not Found (pcap enclosed). Didn't have debug on, but can do if needed.
-- Juha