Hi Gonzaio,
Thanks for the reply.
Yes the registrations are not updating to DB and info stays in cache. We are getting Register packets every two minutes (expires = 120) and we are using the default timer_interval value (60). What is the suggested timer_value value here ?
DB : Postgres
kamailio_settings=# select username,contact,socket,expires from location where username='varghesetest' ;
username | contact | socket | expires
----------+---------+--------+---------
(0 rows)
root@kamailio-registrar:/tmp# kamctl ul show varghesetest
Contact:: <sip:uf9bc7vo@123.201.209.17:49235;transport=ws>;q=;expires=47;flags=0x0;cflags=0x0;state=1;socket=<tls:10.171.145.73:5063>;methods=0x20F;received=<sip:123.201.209.17:49235;transport=WS>;user_agent=<WebSDK 0.3.1-devel-tag-v0.18.7>;
When we remove the registration in the cache then for the next Register packet it will update the registration status to DB.
root@kamailio-registrar:/tmp# kamctl ul rm varghesetestAfter the Register Packet it will update to DB
root@registrar-vhtkbz:~# kamctl ul show varghesetest
Contact::<sip:uf9bc7vo@123.201.209.17:49235;transport=ws>;q=;expires=118;flags=0x0;cflags=0x0;state=1;socket=<tls:10.171.145.73:5063>;methods=0x20F;received=<sip:123.201.209.17:49235;transport=WS>;user_agent=<WebSDK 0.3.1-devel-tag-v0.18.7>;kamailio_settings=# select username,contact,socket,expires from location where username='varghesetest' ;
username | contact | socket | expires
--------------------+------------------------------------------------+-------------------------+---------------------
varghesetest | sip:uf9bc7vo@123.201.209.17:49235;transport=ws | tls:10.171.145.73:5063 | 2014-10-09 08:22:07
(1 row)
Let me know if you need any more details.
Regards