sr-users December 2015

sr-users@lists.kamailio.org

70 participants
110 discussions

by Juha Heinanen

for some reason once in a while kamailio processes fail to execute mysql queries while at the same time an mysql test script that is run once per second from cron works fine. kamailio executes mysql queries during normal sip message processing and also when it processes an OPTIONS ping test request: sql_query("sip_proxy", "SELECT table_version FROM version WHERE table_name='domain'", "result"); if ($rc == 1) { sql_result_free("result"); options_reply(); } else { xlog("L_ERR", "$rm <$ru> failed sql test\n"); sql_result_free("result"); send_reply("500", "Server Internal Error"); }; here is an example: ... Dec 15 00:51:08 proxy1 php: MySQL server test succeeded Dec 15 00:51:09 proxy1 php: MySQL server test succeeded Dec 15 00:51:10 proxy1 /usr/bin/sip-proxy[29894]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query Dec 15 00:51:10 proxy1 /usr/bin/sip-proxy[29894]: ERROR: db_mysql [km_dbase.c:145]: db_mysql_async_exec_task(): failed to execute query on async worker Dec 15 00:51:10 proxy1 php: MySQL server test succeeded Dec 15 00:51:11 proxy1 php: MySQL server test succeeded Dec 15 00:51:13 proxy1 php: MySQL server test succeeded Dec 15 00:51:13 proxy1 /usr/bin/sip-proxy[29891]: ERROR: db_mysql [km_dbase.c:123]: db_mysql_submit_query(): driver error on query: Lost connection to MySQL server during query Dec 15 00:51:13 proxy1 /usr/bin/sip-proxy[29891]: ERROR: <core> [db_query.c:291]: db_do_delete(): error while submitting query Dec 15 00:51:13 proxy1 /usr/bin/sip-proxy[29883]: ERROR: OPTIONS <sip:xxx:5060> failed sql test Dec 15 00:51:14 proxy1 php: MySQL server test succeeded Dec 15 00:51:14 proxy1 /usr/bin/sip-proxy[29886]: ERROR: OPTIONS <sip:xxx:5060> failed sql test Dec 15 00:51:15 proxy1 php: MySQL server test succeeded Dec 15 00:51:15 proxy1 /usr/bin/sip-proxy[29885]: ERROR: OPTIONS <sip:xxx:5060> failed sql test Dec 15 00:51:16 proxy1 php: MySQL server test succeeded Dec 15 00:51:17 proxy1 php: MySQL server test succeeded Dec 15 00:51:18 proxy1 php: MySQL server test succeeded ... all db_mysql module params are at their default values. any idea why kamailio at connection loss does not automatically create new connections? is there a means to somehow debug this further? -- juha

8 years, 11 months

Kamailio and Skype for Business (MS Lync)

by Grant Bagdasarian

Hello, Does anyone have any experience configuring Kamailio as a gateway for Skype For Business (Microsoft Lync)? Regards, Grant

8 years, 11 months

ACC module from_tag, to_tag and callid

by Gholamreza Sabery

In the ACC modules' database table (acc) in Kamailio sometimes from_tag, to_tag and callid of an INVITE and corresponding BYE completely match. But sometimes from_tag in INVITE is to_tag of BYE and to_tag of BYE will become from_tag of INVITE. Why this happens? Is this normal? Regards

8 years, 11 months

crash in version 4.0

by Juha Heinanen

core dump occurred in kamailio version 4.0. does anyone remember if a bug causing such a crash would possibly have been fixed in some later kamailio version? -- juha ------------------------------------------------------------------------------ Dec 17 17:16:59 node5 /usr/sbin/sip-proxy[21089]: WARNING: db_mysql [km_dbase.c:85]: driver error on ping: Lost connection to MySQL server during query Dec 17 17:16:59 node5 /usr/sbin/sip-proxy[21116]: : <core> [pass_fd.c:293]: ERROR: receive_fd: EOF on 90 Dec 17 17:16:59 node5 /usr/sbin/sip-proxy[21016]: ALERT: <core> [main.c:788]: child process 21089 exited by a signal 11 Dec 17 17:16:59 node5 /usr/sbin/sip-proxy[21016]: ALERT: <core> [main.c:791]: core was generated ------------------------------------------------------------------------------ Program terminated with signal 11, Segmentation fault. #0 run_trans_callbacks_internal (cb_lst=<value optimized out>, type=512, trans=0x7f093593a9b0, params=0x7fff7a5289c0) at t_hooks.c:286 286 t_hooks.c: No such file or directory. in t_hooks.c (gdb) bt full #0 run_trans_callbacks_internal (cb_lst=<value optimized out>, type=512, trans=0x7f093593a9b0, params=0x7fff7a5289c0) at t_hooks.c:286 cbp = 0x3030 backup_from = 0x8a49d0 backup_to = 0x8a49d8 backup_dom_from = 0x8a49e0 backup_dom_to = 0x8a49e8 backup_uri_from = 0x8a49c0 backup_uri_to = 0x8a49c8 backup_xavps = 0x8a4ad0 #1 0x00007f0941ad3ddc in run_trans_callbacks_with_buf (type=1887007839, rbuf=<value optimized out>, req=<value optimized out>, repl=0x6565705f74736423, flags=0) at t_hooks.c:336 params = {req = 0x7f0935b32360, rpl = 0xffffffffffffffff, param = 0x7f0935940900, code = 408, flags = 408, branch = 0, t_rbuf = 0x7f093593aa70, dst = 0x7f093593aac0, send_buf = { s = 0x7f093594d180 "From: xxx <sip:xxx@xxx:5060;user=phone>;tag=262063958\r\nTo: xxx <sip:xxx@xxx:5060;user=phone>;tag=as2db5b848\r\nCall-ID: 2864df7e-1d31c032-6dd726"..., len = 462}} trans = 0x246 #2 0x00007f0941aef8cb in relay_reply (t=0x7f093593a9b0, p_msg=<value optimized out>, branch=<value optimized out>, msg_status=<value optimized out>, cancel_data=<value optimized out>, do_put_on_wait=<value optimized out>) at t_reply.c:1880 relay = 0 save_clone = 0 buf = 0x7f0943b3d140 "SIP/2.0 408 Request Timeout\r\nVia: SIP/2.0/UDP xxx:5060;branch=z9hG4bKterm-2b3acd-xxx-xxx-72778\r\nFrom: xxx <sip:xxx@xxx:5060;user=phone>;tag=17"... res_len = 462 relayed_code = 408 relayed_msg = 0xffffffffffffffff reply_bak = 0x13c400000050c7d3 bm = {to_tag_val = { s = 0x7f0943b3d259 "0b5775687262b458dc9c8d93773b9caa-d95c\r\nCall-ID: 1be7fd61-4cf116a3-62498d9c-8757@xxx\r\nCSeq: 1 INVITE\r\nServer: Kamailio (4.0.1 (x86_64/linux))\r\nContent-Length: 0\r\n\r\n", len = 37}} totag_retr = 0 reply_status = RPS_COMPLETED uas_rb = 0x7f093593aa70 to_tag = <value optimized out> reason = {s = 0x56dbc5 "Request Timeout", len = 15} onsend_params = {req = 0x0, rpl = 0x1, param = 0x7f093593ab18, code = 898869680, flags = 32521, branch = 0, t_rbuf = 0x7d9c88, dst = 0xfffffe22, send_buf = { s = 0x7f093593ab20 "", len = 1101857122}} #3 0x00007f0941af5ac1 in fake_reply (t=0x7f093593a9b0, branch=0, code=<value optimized out>) at timer.c:354 cancel_data = {cancel_bitmap = 0, reason = {cause = 0, u = {text = {s = 0x0, len = 898870080}, e2e_cancel = 0x0, packed_hdrs = {s = 0x0, len = 898870080}}}} reply_status = <value optimized out> #4 0x00007f0941af5ec8 in final_response_handler (ticks=1904446327, tl=0x7f093593ab40, p=<value optimized out>) at timer.c:526 prev_branch = -478 now = 0 #5 retr_buf_handler (ticks=1904446327, tl=0x7f093593ab40, p=<value optimized out>) at timer.c:584 rbuf = 0xfffffe22 fr_remainder = <value optimized out> retr_remainder = <value optimized out> retr_interval = <value optimized out> new_retr_interval_ms = <value optimized out> #6 0x00000000004fa080 in slow_timer_main () at timer.c:1151 n = 12 ret = 12 tl = 0x7f093593ab40 #7 0x0000000000458039 in main_loop () at main.c:1693 i = 16 pid = <value optimized out> si = 0x0 si_desc = "sctp receiver child=15 sock=xxx:5060\000\000\000\200\215Rz\377\177\000\000\000\000\000\000\000\000\000\000\003\000\000\000\000\000\000\000\001\000\000\000\004\000\000\000\005\000\000\000\000\000\000\000\020\000\000\000\000\000\000\000\002\000\000\000\000\000\000\000 \251\212", '\000' <repeats 13 times>, "\020\000\000\000\000\000\000" nrprocs = 16 #8 0x00000000004599fb in main (argc=17, argv=<value optimized out>) at main.c:2566 cfg_stream = <value optimized out> c = <value optimized out> r = 0 tmp = 0x7fff7a529f11 "" tmp_len = 0 port = <value optimized out> proto = <value optimized out> ret = <value optimized out> seed = 2572917976 rfd = <value optimized out> debug_save = <value optimized out> debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x7fff7a528d80 p = <value optimized out> (gdb)

8 years, 11 months

rtpengine module rtpengine_disable_tout question

by Juha Heinanen

rtpengine readme tells: 4.2. rtpengine_disable_tout (integer) Once an RTP proxy was found unreachable and marked as disabled, the rtpengine module will not attempt to establish communication to that RTP proxy for rtpengine_disable_tout seconds. Default value is "60". does this mean that after 60 seconds is passed, rtpengine module will again try to use that RTP proxy, i.e., the RTP proxy does never become permanently disabled unless disabled by nh_enable_rtpp mi command? does the this param apply also if all RTP proxies of a set (perhaps consisting of only one proxy) are unreachable? -- juha

8 years, 11 months

Kamailio v4.1.9 Released

by Daniel-Constantin Mierla

Hello, Kamailio SIP Server v4.1.9 stable release is out. This is marking the end of maintenance for 4.1.x series. Kamailio project maintains the last two stable branches, at this moment these are 4.2 and 4.3. Therefore, anyone running older releases is advised to upgrade in the near future to the latest version of one of those branches, preferably 4.3, in order to benefit of proper maintenance. For more details about version 4.1.9 (including links and guidelines to download the tarball or from GIT repository), visit: * http://www.kamailio.org/w/2015/12/kamailio-v4-1-9-released/ RPM, Debian/Ubuntu packages will be available soon as well. Note: the latest stable branch is 4.3, at this moment with its latest release v4.3.4. See more details about it at: * http://www.kamailio.org/w/kamailio-v4-3-0-release-notes/ Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/miconda - http://www.linkedin.com/in/miconda

8 years, 11 months

websocket sometimes log errors after ws connect has closed

by Vasiliy Ganchev

Hi list! firstly, the described below issue is harmless to us, and is just little bit annoying, but analysing the nature of issue decided to share the results, and hear the opinion of community. Scenario: - WebRTC client connected to Kamailio's websocket - after some time I close tab with WebRTC, in browser. - using "kamctl fifo ws.dump" and "netstat -npa |grep kama |grep tcp" I can see that the connection is closed - but Kamailio still triing to send keepalive to that connection, and in syslog I got errors: Dec 18 12:28:18 /usr/sbin/kamailio[4471]: WARNING: websocket [ws_frame.c:245]: encode_and_send_ws_frame(): TCP/TLS connection get failed Dec 18 12:28:18 /usr/sbin/kamailio[4471]: ERROR: websocket [ws_frame.c:797]: ping_pong(): sending keepalive Analysing sources, and using debug level 3 I see such logs (after the webrtc client is closed, and ) Dec 18 12:33:33 /usr/sbin/kamailio[4471]: ERROR: websocket [ws_conn.c:468]: wsconn_get_list(): counter wsc [0xb1acb270] prev => [(nil)] next => [(nil)] Dec 18 12:33:33 /usr/sbin/kamailio[4471]: ERROR: websocket [ws_conn.c:495]: wsconn_get_list(): wsc [0xb1acb270] id [2] ref++ Dec 18 12:33:33 /usr/sbin/kamailio[4471]: ERROR: websocket [ws_conn.c:504]: wsconn_get_list(): wsconn_get_list returns list [0xb666f410] with [1] members What is strange: in some tests, after unsuccessful sending of Ping, kamailio's "wsconn_get_list" clean up that connection, but in some tests, kamailio try sending Ping to old connection during 5-10 minutes (this time is not constant from test to test) Suddenly my current knowledge of C is not enough to find out were is the problem's root. General question is: is this correct list for such issuing? Or it should be in Dev list? once again - the problem is harmful (afetr some time, kamailio stop trying sending ping to inactive connection, but it is annoying to see errors in logs) Cheers! -- View this message in context: http://sip-router.1086192.n5.nabble.com/websocket-sometimes-log-errors-afte… Sent from the Users mailing list archive at Nabble.com.

8 years, 11 months

issue with BYE

by gerry kernan

Hi I'm looking for any pointers to resolve and issue I have . When callee does a hang-up the call terminates on kamailio and asterisk but the caller's phone handset doesn't receive the BYE and doesn't hang-up. If the caller does the hang up then the call terminates and the callee's handset hands up . My setup is Kamailio WAN -> Kamailio Lan -> Asterisk LAN I'm using Path and dispatcher modules to route the SIP traffic to the backup end asterisk server my the domain in the SIP request. Gerry Kernan Infinity IT | 17 The Mall | Beacon Court | Sandyford | Dublin D18 E3C8 | Ireland Tel: +353 - (0)1 - 293 0090 | E-Mail: gerry.kernan(a)infinityit.ie Managed IT Services Infinity IT - www.infinityit.ie IP Telephony Asterisk Consulting - www.asteriskconsulting.com Contact Centre Total Interact - www.totalinteract.com

8 years, 11 months

Releasing Kamailio v4.1.9

by Daniel-Constantin Mierla

Hello, I am going to release v4.1.9 later today, as last to be officially packaged version from branch 4.1. It is strongly recommended to migrate to a newer version, because the focus of developers is on the two most recent stable branches. Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com http://miconda.eu

8 years, 11 months

kamailio as simple sip forwarder / gateway / proxy

by Peter Gervai

Hello, I've been browsing the net and the (not so friendly) documentation but found no readily available solution. I have tried to fabricate on myself but it seems it's not that easy without getting deeply familarised with SIP protocol internals which I don't quite want know. The problem seems simple enough, maybe you can easily tell the solution. There is kamailio at ip 256.10.10.1. It's task is to accept connections from SIP clients and forward them to PBX at 256.20.20.1, and accept PBX packets and forward them to the clients. PBX handles registration, options, invites, everything. Kamailio does not authenticate, authorise, just forwards everything back and forth, like a mindless proxy. No NAT involved. [The reason is that K. have to call external scripts whenever an outbound call (towards the clients) is initiated, which the PBX is unable to. Please don't advise other solutions (which isn't able to call executables in-session).] I have created a simplistic config which is not expected to work and it doesn't quite (plenty of security stuff left out now): route { if(src_ip==myself) { add_path(); $du="sip:256.20.20.1:95060"; } else { if(src_ip!="256.20.20.1") { $du="sip:256.20.20.1:95060"; } else { #from gateway pkts aren't changed } if(!t_relay()) { sl_reply_error(); break; } } There is several possible problems, but it seems Contact: is one main one since it contains the client instead of the proxy. Possibly this may even be the almost-good solution. I'm sure there's an easy and pretty solution so before I start to make ugly ones I ask the wise people. Thanks, Peter

8 years, 11 months

← Newer
1
2
3
4
5
6
7
8
...
11
Older →

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 December 2015