9 Oct
2014
9 Oct
'14
11:25 a.m.
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 varghesetest
After 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
Varghese Paul
On Thu, Oct 9, 2014 at 12:16 PM, Gonzalo Gasca <gascagonzalo(a)gmail.com>
wrote:
Hi Varghese,
When you mentioned some of the endpoint registrations are not updated
to Db, which Db type and command are you using to verify this?
Do you mean new registrations are not updated into Db and info stays in
cache?
I see you are using mode 1, check if "timer_interval" param makes a
difference.
In one of my webrtc PoC I'm using a shared db in mode 3 to force Db
only write and I use 0x04 flag: save("location", "0x04") to allow
only
1 record.
since I haven't implemented SIP replication across my Kamailio cluster.
This is what I get:
a) I register using webrtc client:
In both Servers I get:
#kamctl ul show gogasca
Contact:: <sips:gogasca@df7jal23ls0d.invalid
;rtcweb-breaker=no;transport=wss>;q=;expires=202;flags=0x0;cflags=0x0;state=1;socket=<NUL>;methods=0xFFFFFFFF;user_agent=<Llamato
client>;reg-id=0
mysql> use kamailiodb;
mysql>select username,contact,socket,expires from location;
+----------+-------------------------------------------------------------------+-----------------------+---------------------+
| username | contact
| socket | expires |
+----------+-------------------------------------------------------------------+-----------------------+---------------------+
| gogasca | sips:gogasca@df7jal23ls0d.invalid
;rtcweb-breaker=no;transport=wss
| tcp:172.31.27.85:5062 | 2014-10-09 06:32:56 |
+----------+-------------------------------------------------------------------+-----------------------+---------------------+
I unregister and in both servers I get:
root@ip-172-31-38-153:/etc/kamailio# kamctl ul show gogasca
404 AOR not found
Can you send us the output of what are you getting?
-Gonzalo
On Wed, Oct 8, 2014 at 10:01 AM, Varghese Paul <varghesepaul87(a)gmail.com>
wrote:
Hi all,
We are experiencing a strange problem in our Kamilio server. Some of the
webrtc endpoint registrations are not updated to the Database and there
is
no issue with the registration. Once we flushed
the registration for this
endpoint then it is updating to the DB for the new Register Packet.
Flushed the Registration for the endpont : kamctl ul rm <USERNAME>
Kamalio Version: 4.1.2
modparam("usrloc", "db_url", DBURL)
modparam("usrloc", "db_mode", 1)
modparam("usrloc", "nat_bflag", 3)
modparam("usrloc", "use_domain", 1)
Is there any other settings to avoid this issue ?
Regards
Varghese Paul
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users