sr-users

sr-users@lists.kamailio.org

8 participants
37523 discussions

rfc: event route when kamailio starts
by Daniel-Constantin Mierla 12 Oct '15

12 Oct '15

Hello, based on a recent discussion with Alex Balashov (at Kazoocon this week), I pushed a patch that enables the execution of event_route[core:worker-one-init] when kamailio is started. It would be more like an alternative for event_route[htable:mod-init], for the cases when htable is not used, but also should ensure that all the modules are initialized. Moreover, because most of the modules close connection in mod init, I though of doing it when child one (udp receiver) initialization for all modules is finished, which means that all is ready for runtime, still this is before receiving any packet. On the other hand, forking is done by main process, so other children can start listening for sip. More or less what I want to ask here is whether the forking of the other children should wait until the event_route[core:worker-one-init] is finished (e.g., what is done in this event route is important before any sip packet is routed) or just leave it like it is. Worth to say that some modules do special processing in child init of worker one, like usrloc module loads the records from database to memory, which means that overall start of kamailio could be slower. Also, if there are time consuming actions in the event_route[core:worker-one-init], getting to the stage of routing sip packets will take longer. What would you find important, fork the other processes so routing sip will happen as soon as possible, or block until execution ofevent_route[core:worker-one-init] is finished. I guess that making it cusomizable in some way would be a solution, but knowing what use cases would be important may help in reducing the complexity to get it enabled. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com

3 2

Dialog keep alive options are with error parsing headers
by José Seabra 12 Oct '15

12 Oct '15

Hello there, I'm using dialog module to send keep alive options to callee and caller in order to detect if dialog still up, but when kamailio generates the OPTION and parse it, gives the following errors: [root@c4-compute02-srv1 kamailio]# 37(1587) DEBUG: dialog [dlg_hash.c:614]: dlg_lookup(): ref dlg 0x7f89134c1d40 with 1 -> 3 37(1587) DEBUG: dialog [dlg_hash.c:616]: dlg_lookup(): dialog id=2210 found on entry 2350 37(1587) DEBUG: dialog [dlg_req_within.c:427]: dlg_send_ka(): sending OPTIONS to caller 37(1587) DEBUG: tm [uac.c:249]: t_uac_prepare(): DEBUG:tm:t_uac: next_hop=< sip:unknown@62.28.197.25:5060> 37(1587) DEBUG: <core> [dns_cache.c:3293]: dns_srv_sip_resolve(): (62.28.197.25, 0, 0), ip, ret=0 37(1587) DEBUG: tm [uac.c:150]: dlg2hash(): DEBUG: dlg2hash: 14692 37(1587) DEBUG: <core> [parser/msg_parser.c:606]: parse_msg(): SIP Request: 37(1587) DEBUG: <core> [parser/msg_parser.c:608]: parse_msg(): method: <OPTIONS> 37(1587) DEBUG: <core> [parser/msg_parser.c:610]: parse_msg(): uri: < sip:unknown@62.28.197.25:5060> 37(1587) DEBUG: <core> [parser/msg_parser.c:612]: parse_msg(): version: <SIP/2.0> 37(1587) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK4693.2af96e95000000000000000000000000.0>; state=16 37(1587) DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 37(1587) DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=2 37(1587) DEBUG: <core> [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the first via 37(1587) DEBUG: <core> [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: tag=90d40279ee5745d8851aa989e6fadfc2 37(1587) DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=29 37(1587) DEBUG: <core> [parser/msg_parser.c:173]: get_hdr_field(): DEBUG: get_hdr_field: <To> [64]; uri=[sip:unknown@62.28.197.6] 37(1587) DEBUG: <core> [parser/msg_parser.c:175]: get_hdr_field(): DEBUG: to body [<sip:unknown@62.28.197.6>] 37(1587) DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <0> <OPTIONS> 37(1587) DEBUG: <core> [parser/msg_parser.c:187]: get_hdr_field(): DEBUG: get_hdr_body : content_length=0 *37(1587) ERROR: <core> [parser/msg_parser.c:96]: get_hdr_field(): ERROR: get_hdr_field: bad header* 37(1587) DEBUG: <core> [parser/msg_parser.c:280]: get_hdr_field(): get_hdr_field: error exit *37(1587) INFO: <core> [parser/msg_parser.c:338]: parse_headers(): ERROR: bad header field [VC* *]* 37(1587) DEBUG: topoh [topoh_mod.c:232]: th_prepare_msg(): parsing headers failed37(1587) DEBUG: <core> [parser/msg_parser.c:606]: parse_msg(): SIP Request: 37(1587) DEBUG: <core> [parser/msg_parser.c:608]: parse_msg(): method: <OPTIONS> 37(1587) DEBUG: <core> [parser/msg_parser.c:610]: parse_msg(): uri: < sip:unknown@62.28.197.25:5060> 37(1587) DEBUG: <core> [parser/msg_parser.c:612]: parse_msg(): version: <SIP/2.0> 37(1587) DEBUG: <core> [parser/parse_via.c:1254]: parse_via_param(): Found param type 232, <branch> = <z9hG4bK4693.2af96e95000000000000000000000000.0>; state=16 37(1587) DEBUG: <core> [parser/parse_via.c:2642]: parse_via(): end of header reached, state=5 37(1587) DEBUG: <core> [parser/msg_parser.c:496]: parse_headers(): parse_headers: Via found, flags=2 37(1587) DEBUG: <core> [parser/msg_parser.c:498]: parse_headers(): parse_headers: this is the first via 37(1587) DEBUG: <core> [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: tag=90d40279ee5745d8851aa989e6fadfc2 37(1587) DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=29 37(1587) DEBUG: <core> [parser/msg_parser.c:173]: get_hdr_field(): DEBUG: get_hdr_field: <To> [64]; uri=[sip:unknown@62.28.197.6] 37(1587) DEBUG: <core> [parser/msg_parser.c:175]: get_hdr_field(): DEBUG: to body [<sip:unknown@62.28.197.6>] 37(1587) DEBUG: <core> [parser/msg_parser.c:153]: get_hdr_field(): get_hdr_field: cseq <CSeq>: <0> <OPTIONS> 37(1587) DEBUG: <core> [parser/parse_addr_spec.c:172]: parse_to_param(): DEBUG: add_param: tag=e34d43e164ad4b7392dc9c6e1058a983 37(1587) DEBUG: <core> [parser/parse_addr_spec.c:894]: parse_addr_spec(): end of header reached, state=29 37(1587) DEBUG: dialog [dlg_cseq.c:215]: dlg_cseq_msg_sent(): traking cseq updates 37(1587) DEBUG: dialog [dlg_hash.c:671]: internal_get_dlg(): ref dlg 0x7f89134c1d40 with 1 -> 4 37(1587) DEBUG: dialog [dlg_hash.c:674]: internal_get_dlg(): dialog callid='13208317017c42128fbf00e1685ee1b3' found on entry 2350, dir=2 37(1587) DEBUG: dialog [dlg_cseq.c:233]: dlg_cseq_msg_sent(): request not going downstream (2) 37(1587) DEBUG: dialog [dlg_hash.c:846]: dlg_unref(): unref dlg 0x7f89134c1d40 with 1 -> 3 37(1587) DEBUG: dialog [dlg_req_within.c:452]: dlg_send_ka(): keep-alive sent to caller 37(1587) DEBUG: dialog [dlg_req_within.c:427]: dlg_send_ka(): sending OPTIONS to callee I'm using the following dialog configuration: modparam("dialog","db_url", DBURL) modparam("dialog","db_mode", 0) modparam("dialog","enable_stats", 1) modparam("dialog","dlg_flag", DLG_FLAG) modparam("dialog","profiles_with_value","concurrentcalls") modparam("dialog", "detect_spirals", 1) modparam("dialog","dlg_match_mode", 2) modparam("dialog", "initial_cbs_inscript", 0) modparam("dialog", "default_timeout", 3600) modparam("dialog", "send_bye", 1) modparam("dialog", "timeout_avp", "$avp(s:timeout_dlg)") modparam("dialog", "track_cseq_updates", 1) modparam("dialog", "ka_timer", 10) modparam("dialog", "ka_interval", 30) I'm also using topoh module. Anyone can help me to identify if I'm doing the proper configuration? Thank you for your support Best Regards José Seabra

3 9

Startup Route in Kamailio
by Sunil More 12 Oct '15

12 Oct '15

Hi All, I am new to Kamailio world. I am trying to initialize some details at Kamailio startup, this requires some database queries from a few tables. I have read about the htable event, however sql queries are not working in this route. I have come upon following errors. Please suggest a solution for this. Route used: event_route[htable:mod-init] { xlog("L_INFO", "********Initailising the startup route ******\n"); sql_xquery("cb","SELECT id, media_server_port, name FROM domains","ra"); } error : Oct 8 13:28:32 P172 /usr/local/kamailio/sbin/kamailio[28735]: INFO: <script>: ********Initailising the startup route ****** Oct 8 13:28:32 P172 kamailio: ERROR: <core> [daemonize.c:303]: daemonize(): Main process exited before writing to pipe Thanking You, Sunil More Ph : 9503338275

2 1

Familiar topic about Kamailio with Asterisk behind NAT
by Dirk Teurlings - SIGNET B.V. 09 Oct '15

09 Oct '15

Hi, I found some existing topics on this but failed to get a solutions out of them. We're running into some issues with client devices connecting to our private addresses. The way it is setup now: CLIENTS <-> (NAT) <-> INTERNET <-> KAMAILIO(4.2.5) with RTPPROXY(v1) <-> PRIVATE LAN <-> ASTERISK (v1.8) Our Kamaialio and Asterisk are in a private address range, but Kamailio also has a public interface. Most of the clients (about 95%) work well with this setup, but a couple don't. We have one case now where the CLIENT tries to connect to the private address of ASTERISK. And of course, that doesn't work. I'm kind of stuck as to where I need to fix this. I tried using the externaddr option in Asterisk to solve it on that end. But that didn't help anything. The NAT options in Kamailio are not really suited for this, as they tend to fix client NAT problems. Any pointer or help would be greatly appriciated. Cheers, Dirk

8 16

[pua] Question to DB Mode 0
by Maciej Marczyński 09 Oct '15

09 Oct '15

Hi Guys, I have a question regarding pua module parameter 'db mode'. I run Kamailio (4.3.2) with sqlite and I tried to set the parameter to 0 but even then I received: > ERROR: db_sqlite [dbase.c:489]: db_sqlite_commit(): sqlite commit failed: NOT NULL constraint failed: pua.call_id > ERROR: db_sqlite [dbase.c:138]: db_sqlite_cleanup_query(): finalize failed: NOT NULL constraint failed: pua.call_id > ERROR: pua [pua.c:1179]: db_update(): while inserting in db table pua > > As far as I checked the documentation, it says that '0' means: > high speed memory based storage Does it still writes to DB anyway (on timer or whatever?) or just keep it in memory? Is there any way to disable writing to DB? The second thing is the reason of the ERRORs above. Why does pua think that my call_id is null? If you need any more information please let me know. Best regards and have a good weekend, Maciej

3 7

Siremis debug window
by Infinicalls Infinicalls 08 Oct '15

08 Oct '15

Hi, I have installed Siremis and modified it for public user registration. I have added a new user. When I try to log in it opens up a new (debug) window and prints "1". It doesn't allow me to log in. But I can log in as admin;admin. And siremis/user/register doesn't load properly. It redirects to the login page again. Kindly let me know how do I solve this. regards Ganesh Kumar

2 8

MySQL Connect Errors
by John Billings 08 Oct '15

08 Oct '15

We are using kamailio 4.2.0 with auth_db enabled and connected to a MySQL server. Occasionally, in the middle of the night when there is no activity we get the following errors out of the blue (the last three lines are repeated indefinitely). According to the MySQL site <http://dev.mysql.com/doc/refman/5.0/en/error-lost-connection.html>, this can be caused by a connect timeout that is too short (We verified that Aborted_connects is steadily rising). The kamailio server is right next to the database server so there is no network latency. We increased the db_mysql timeout_interval parameter, but we still see MySQL’s Aborted_connects counter incrementing. So it’s like kamailio is still timing out on connection attempts. Ideas? Thanks. Oct 1 02:34:49 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Oct 1 02:34:49 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: auth_db [authorize.c:175]: get_ha1(): failed to query database Oct 1 02:34:55 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'reading authorization packet', system error: 11 Oct 1 02:34:55 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Oct 1 02:34:55 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: auth_db [authorize.c:175]: get_ha1(): failed to query database Oct 1 02:35:01 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'reading authorization packet', system error: 11 Oct 1 02:35:01 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Oct 1 02:35:01 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: auth_db [authorize.c:175]: get_ha1(): failed to query database Oct 1 02:35:01 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'reading authorization packet', system error: 11 Oct 1 02:35:01 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Oct 1 02:35:01 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: auth_db [authorize.c:175]: get_ha1(): failed to query database Oct 1 02:35:07 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'reading authorization packet', system error: 11 Oct 1 02:35:07 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Oct 1 02:35:07 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: auth_db [authorize.c:175]: get_ha1(): failed to query database Oct 1 02:35:07 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server at 'reading authorization packet', system error: 11 Oct 1 02:35:07 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Oct 1 02:35:07 sip-proxy1 /usr/sbin/kamailio[9260]: ERROR: auth_db [authorize.c:175]: get_ha1(): failed to query database Oct 1 02:35:11 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Host ‘X.X.X.X' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts' Oct 1 02:35:11 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: <core> [db_query.c:132]: db_do_query_internal(): error while submitting query Oct 1 02:35:11 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: auth_db [authorize.c:175]: get_ha1(): failed to query database Oct 1 02:35:11 sip-proxy1 /usr/sbin/kamailio[9264]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Host 'X.X.X.X' is blocked because of many connection errors; unblock with 'mysqladmin flush-hosts' ...

2 1

TM not ending transactions
by Daniel Tryba 08 Oct '15

08 Oct '15

Running 4.3.x (both .1 and .2) I have seen it happening twice sofar that dialogs (the module) will not end, resulting in to calls failing due to call limits based on active dialogs. Accounting logged a BYE for all these calls. kamcmd tm.stats shows an increasing number of current/waiting transactions (as grphed in attachment). Has anyone seen this problem?

3 7

Questions about LCR
by Scott C. Fertig 08 Oct '15

08 Oct '15

Hello, Sorry to bother and if I sound like a newb thats because I am kind of new (but im trying =) ) I am having some issues getting started using LCR and was wondering if anyone could point me in the right direction and/or let me know what I am doing wrong. I began setting up the other day using kamailio (4.4.0-dev5) from git (maybe I picked the wrong version?) and am struggling to get lcr to work properly. So far I have been able to get the module to load, added the route to the config and have added some LCR values. Inbound calling is working perfectly to a registered device which is great so far. This is my config for the LCR: http://pastebin.com/LUF0Pgr1 I have the following values in my database for LCR: http://pastebin.com/bDpQug0J I was not sure if dumping all the text in the email would be appropriate if needed please let me know to resend with the configs in the email. Whats strange to me is that even with the xlog I do not get any messages to syslog at all, I have defined WITH_DEBUG, debug level at 3, and log facility set to LOG_LOCAL0 (Sorry if I'm bringing up multiple issues) Anyways back on point, I'm wondering if this is related to the avp's listed, I am not sure what the avps referenced are supposed to represent, when I try to dump all the avps I get a empty list, and it is querying the usr_preference table for these. Is there something I need to add within this table, or is there perhaps something wrong with my configuration? [root@localhost kamailio]# kamctl avp list database engine 'MYSQL' loaded Control engine 'FIFO' loaded Query: SELECT uuid,username,domain,attribute,type,value FROM usr_preferences ; Dumping AVPs Thank you!

2 2

Lost 180 Ringing Response
by John Billings 07 Oct '15

07 Oct '15

Hi Everyone, We are using Kamailio 4.2.0 with TLS. It’s setup so multiple phones can register to the same account and they all ring together. It always works great unless one of the phones is on a slower Internet connection. Occasionally that phone will start ringing after another phone has already picked up the call. The problem is that the INVITE to the slow phone is not followed by a CANCEL. So the phone keeps on ringing for a long time. When there is no problem, the logs on the phone show: Receive: INVITE Send: 180 Ringing Received: CANCEL Send: 200 Ok When the phone keeps ringing: Delay: up to several seconds Receive: INVITE Send: 180 Ringing The problem never seems to happen if I wait until all of the phones have received the INVITE. So is the late 180 response not getting handled by the right session? Any ideas on how to track this down?

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

sr-users