Hey Guys,
I am in the process of testing the reloading of the uac registrations (thanks Daniel for that), and hit some issue: * when using uac_reg_info twice in a row, second command always hangs.
""" root@Dev2:/etc/kamailio# kamcmd -s tcp:127.0.0.1:2046 uac.reg_info l_uuid 301 { l_uuid: 301 l_username: 301 l_domain: pbx.example.com r_username: 301 r_domain: pbx.example.com realm: asterisk auth_username: 301 auth_password: check123 auth_proxy: sip:172.16.254.75 expires: 360 flags: 0 diff_expires: -1414052722 timer_expires: 0 } root@Dev2:/etc/kamailio# root@Dev2:/etc/kamailio# root@Dev2:/etc/kamailio# root@Dev2:/etc/kamailio# kamcmd -s tcp:127.0.0.1:2046 uac.reg_info l_uuid 301 ^C root@Dev2:/etc/kamailio# kamcmd -s tcp:127.0.0.1:2046 uac.reg_info l_uuid 301
"""
Do you see anything wrong with my data or did I hit a bug?
Since we are here and could not find much documentation around, is there a way to decrease the default 150 seconds blocking reloads from the database?
""" root@Dev2:/etc/kamailio# kamcmd -s tcp:127.0.0.1:2046 uac.reg_reload root@Dev2:/etc/kamailio# kamcmd -s tcp:127.0.0.1:2046 uac.reg_reload error: 500 - Failed to shift records - check log messages """ Syslog: """ Oct 23 10:32:17 Dev2 /usr/sbin/kamailio[2693]: ERROR: uac [uac_reg.c:369]: uac_reg_ht_shift(): shifting the memory table is not possible in less than 150 """
Thanks in advance for any kind of tip!
DanB
Hello,
are you using branch 4.2 or some tgz/package from 4.2.0 release? There was a fix related to such issue, so 4.2 branch must be used (or debian nightly builds for 4.2).
I will have to check the code how flexible that is, but afaik, the limit on reload interval was thought to avoid sending again registration requests while retransmissions from previous one can occur.
Cheers, Danel
On 23/10/14 10:38, Dan Christian Bogos wrote:
Hey Guys,
I am in the process of testing the reloading of the uac registrations (thanks Daniel for that), and hit some issue:
- when using uac_reg_info twice in a row, second command always hangs.
""" root@Dev2:/etc/kamailio# kamcmd -s tcp:127.0.0.1:2046 uac.reg_info l_uuid 301 { l_uuid: 301 l_username: 301 l_domain: pbx.example.com r_username: 301 r_domain: pbx.example.com realm: asterisk auth_username: 301 auth_password: check123 auth_proxy: sip:172.16.254.75 expires: 360 flags: 0 diff_expires: -1414052722 timer_expires: 0 } root@Dev2:/etc/kamailio# root@Dev2:/etc/kamailio# root@Dev2:/etc/kamailio# root@Dev2:/etc/kamailio# kamcmd -s tcp:127.0.0.1:2046 uac.reg_info l_uuid 301 ^C root@Dev2:/etc/kamailio# kamcmd -s tcp:127.0.0.1:2046 uac.reg_info l_uuid 301
"""
Do you see anything wrong with my data or did I hit a bug?
Since we are here and could not find much documentation around, is there a way to decrease the default 150 seconds blocking reloads from the database?
""" root@Dev2:/etc/kamailio# kamcmd -s tcp:127.0.0.1:2046 uac.reg_reload root@Dev2:/etc/kamailio# kamcmd -s tcp:127.0.0.1:2046 uac.reg_reload error: 500 - Failed to shift records - check log messages """ Syslog: """ Oct 23 10:32:17 Dev2 /usr/sbin/kamailio[2693]: ERROR: uac [uac_reg.c:369]: uac_reg_ht_shift(): shifting the memory table is not possible in less than 150 """
Thanks in advance for any kind of tip!
DanB
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users