sr-dev September 2015

sr-dev@lists.kamailio.org

37 participants
387 discussions

git:master:31c9b0c1: ims_usrloc_scscf: Implement overwrite oldest behaviour
by Carsten Bock 08 Sep '15

08 Sep '15

Module: kamailio Branch: master Commit: 31c9b0c16c3e2b14aa48d7ecdbe62ea6b9d1c6cc URL: https://github.com/kamailio/kamailio/commit/31c9b0c16c3e2b14aa48d7ecdbe62ea… Author: Carsten Bock <carsten(a)ng-voice.com> Committer: Carsten Bock <carsten(a)ng-voice.com> Date: 2015-09-08T20:50:46+02:00 ims_usrloc_scscf: Implement overwrite oldest behaviour --- Modified: modules/ims_usrloc_scscf/impurecord.c --- Diff: https://github.com/kamailio/kamailio/commit/… [View More]

1 0

git:4.3:262d3574: parser: fix start of search for long header names
by Daniel-Constantin Mierla 08 Sep '15

08 Sep '15

Module: kamailio Branch: 4.3 Commit: 262d3574790ea3a10c82cb8bc0e4a65429f25540 URL: https://github.com/kamailio/kamailio/commit/262d3574790ea3a10c82cb8bc0e4a65… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2015-09-08T17:40:31+02:00 parser: fix start of search for long header names - in parse_hname2_short(), used only for mod fixups, in the case header name given as function param was greater than 250 chars … [View More]

1 0

git:master:de8ba390: parser: fix start of search for long header names
by Daniel-Constantin Mierla 08 Sep '15

08 Sep '15

Module: kamailio Branch: master Commit: de8ba3900d6fef42e99ca9568044c7aefa44a5ea URL: https://github.com/kamailio/kamailio/commit/de8ba3900d6fef42e99ca9568044c7a… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2015-09-08T17:28:40+02:00 parser: fix start of search for long header names - in parse_hname2_short(), used only for mod fixups, in the case header name given as function param was greater than 250 … [View More]

1 0

git:master:be35e468: Makefile.defs: version set to 4.4.0-dev3
by Daniel-Constantin Mierla 08 Sep '15

08 Sep '15

Module: kamailio Branch: master Commit: be35e46818e98892b2981593b5b63017a2ab7743 URL: https://github.com/kamailio/kamailio/commit/be35e46818e98892b2981593b5b6301… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2015-09-08T16:22:16+02:00 Makefile.defs: version set to 4.4.0-dev3 --- Modified: Makefile.defs --- Diff: https://github.com/kamailio/kamailio/commit/be35e46818e98892b2981593b5b6301… Patch: https://… [View More]

1 0

git:master:6cd8cdc8: auth: fixed improper whitespacing
by Daniel-Constantin Mierla 08 Sep '15

08 Sep '15

Module: kamailio Branch: master Commit: 6cd8cdc80e5037b90f7e636c360c88eed1dcdcec URL: https://github.com/kamailio/kamailio/commit/6cd8cdc80e5037b90f7e636c360c88e… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2015-09-08T15:10:04+02:00 auth: fixed improper whitespacing (cherry picked from commit 20231f4936b5f79bcb2e3f64985953888391e570) --- Modified: modules/auth/nonce.c --- Diff: https://github.com/… [View More]

1 0

git: new commits in branch 4.3
by Daniel-Constantin Mierla 08 Sep '15

08 Sep '15

- URL: https://github.com/kamailio/kamailio/commit/d13e418a34cae70e68c3bb50ee0cef6… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2015-09-08T14:45:57+02:00 lib/srdb1: dummy string for null values pointed to static buffer - allow editing in upper layers, avoiding innaproriate access to a constant (cherry picked from commit d83fee0a31f292af731269cbd361db39be0a4b9b) - URL: https://github.com/kamailio/kamailio/commit/3742fe74e34eaed12c88107aad5d323… Author: Victor Seva … [View More]

1 0

Question on Verto
by Igor Bannicov 08 Sep '15

08 Sep '15

Hi, guys. Just a quick question - is there any support for Verto protocol or is it going to be? Best regards! Igor Bannicov.

1 0

[kamailio] jsonrpc-c notification does not free shm memory (#296)
by zxcpoiu 08 Sep '15

08 Sep '15

#### Use Case Description: I'm trying to log "user last register status" using function `jsonrpc_notification` from module `jsonrpc-c` ##### invoke in kamailio.cfg: `jsonrpc_notification("last_reg", "{'user': '$au', 'data':['$Ts', '$au', '$ct', '$ua', '$sel(received.proto_ip_port)']}");` **according to [doc](http://kamailio.org/docs/modules/4.3.x/modules/jsonrpc-c.html#idp24639… jsonrpc_notification is *asynchronous delayed job* and *do not receive response* > notifications do not … [View More]receive a response. Script processing continues in the usual fashion as soon as the notification has been sent. The rpc server on localhost is implemented with Node.js which never return responses and never close connections ( it only support jsonrpc notification ) #### Observation and Test: ##### Crash occurs I found kamailio crashed periodically about 2-3 days. ( back trace attached at the end) **settings:** 1. the amount of total registered users are about 15k ~ 50k; register expiration is 1200 Secs. 2. kamailio start with parameter pkg 1G and shm 5G. 3. I had patched jsonrpc_io.c from #268 **json crash log:** ``` Aug 18 22:12:04 SIP-4 kernel: [50538943.565484] kamailio[84670]: segfault at 0 ip 00007f424a3ea3bf sp 00007fff8b3eab60 error 4 in libjson.so.0.1.0[7f424a3e6000+9000] Aug 18 22:12:23 SIP-4 /home/pkg/kamailio/sbin/kamailio[84620]: ALERT: <core> [main.c:728]: handle_sigs(): child process 84670 exited by a signal 11 Aug 18 22:12:23 SIP-4 /home/pkg/kamailio/sbin/kamailio[84620]: ALERT: <core> [main.c:731]: handle_sigs(): core was generated ``` sometimes it would not crash, but result in allocation failure. no new connections can be accept. ``` Aug 20 12:26:04 SIP-5 /home/pkg/kamailio/sbin/kamailio[181104]: ERROR: <core> [tcp_main.c:959]: tcpconn_new(): mem. allocation failure Aug 20 12:26:04 SIP-5 /home/pkg/kamailio/sbin/kamailio[181104]: ERROR: <core> [tcp_main.c:3977]: handle_new_connect(): tcpconn_new failed, closing socket ``` ##### Test use `sip-p` to start a stress test with RPS 2000 register and observing results both from `kamcmd core.shmmem` and `top` command Kamailio died quickly along with depleting shm memory. `top` shows kamailio SHR consumed 4.8G `kamcmd core.shmmem` shows **free** is less than 1MB ##### the more `jsonrpc_notification` call we've made, the quicker kamailio out of memory. #### MEMDBG switch on memdbg and shutdown kamailio to get mem status. see Memory still-in-use summary (shm): `shm_strdup` and `jsonrpc_notification` from jsonrpc_request.c ``` Aug 24 14:39:41 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: ----------------------------- Aug 24 14:39:41 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : <core> [main.c:569]: cleanup(): Memory still-in-use summary (shm): Aug 24 14:39:41 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: summarizing all alloc'ed. fragments: Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 96 size= 4608 bytes from dialog: dlg_var.c: new_dlg_var(97) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 96 size= 2016 bytes from dialog: dlg_var.c: new_dlg_var(106) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 96 size= 1152 bytes from dialog: dlg_var.c: new_dlg_var(116) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 40 size= 10568 bytes from tmx: tmx_pretran.c: tmx_check_pretran(264) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 40 size= 5520 bytes from tmx: tmx_pretran.c: tmx_check_pretran(243) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 993 size= 7960 bytes from dialog: dlg_handlers.c: dlg_get_iuid_shm_clone(279) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count=997818 size= 113547928 bytes from jsonrpc-c: jsonrpc_request.c: shm_strdup(158) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 1 size= 1024 bytes from tmx: tmx_pretran.c: tmx_init_pretran_table(90) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 3 size= 64 bytes from usrloc: udomain.c: build_stat_name(51) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 1 size= 8 bytes from <core>: pt.c: init_pt(110) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 1 size= 8 bytes from <core>: pt.c: init_pt(105) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count=498909 size= 40377480 bytes from jsonrpc-c: jsonrpc_request.c: jsonrpc_notification(135) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 1 size= 8 bytes from dialog: dlg_hash.c: init_dlg_table(269) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 1 size= 8 bytes from dialog: dlg_hash.c: init_dlg_table(262) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 1 size= 8 bytes from dialog: dlg_hash.c: init_dlg_table(257) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 3 size= 216 bytes from <core>: timer.c: register_timer(1011) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 1 size= 8 bytes from <core>: usr_avp.c: init_avps(90) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 1 size= 8 bytes from <core>: usr_avp.c: init_avps(89) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: count= 1 size= 8 bytes from <core>: mem/shm_mem.c: shm_mem_init_mallocs(179) Aug 24 14:39:42 SIP-6 /home/pkg/kamailio/sbin/kamailio[263619]: : fm_status: ----------------------------- ``` #### crash on jsonrpc back trace ``` #0 0x00007f424a3ea3bf in json_tokener_parse_ex () from /lib/x86_64-linux-gnu/libjson.so.0 No symbol table info available. #1 0x00007f424a3ebda6 in json_tokener_parse_verbose () from /lib/x86_64-linux-gnu/libjson.so.0 No symbol table info available. #2 0x00007f424a3ebdfe in json_tokener_parse () from /lib/x86_64-linux-gnu/libjson.so.0 No symbol table info available. #3 0x00007f424a5f4e1a in cmd_pipe_cb (fd=6, event=2, arg=0x7fff8b3eae60) at jsonrpc_io.c:152 cmd = 0x7f4304a93cf8 __FUNCTION__ = "cmd_pipe_cb" params = 0x1bc0aa0 payload = 0x3985b4d6 req = 0x304a9c5 json = 0x7fff8b3ead00 "0\f\274\001" ns = 0x7f4391ebdc60 "298:{ \"jsonrpc\": \"2.0\", \"method\": \"last_reg\", \"params\": { \"user\": \"597438910\", \"data\": [ \"1439907102\", \"597438910\", \"<sip:597438910@211.246.212.119:55430;transport=tcp>;+sip.instance=\\\"<urn:uuid:f1016"... bytes = 140735529528624 g = 0x7f424a1ac2f8 sent = 0 #4 0x00007f424a1af254 in event_base_loop () from /usr/lib/x86_64-linux-gnu/libevent-2.0.so.5 No symbol table info available. #5 0x00007f424a5f45ef in jsonrpc_io_child_process (cmd_pipe=6, _servers=0x7f4391aba578 "10.1.3.9:5013,3 10.1.3.10:5013,2 10.1.3.11:5013,1") at jsonrpc_io.c:92 __FUNCTION__ = "jsonrpc_io_child_process" pipe_ev = {ev_active_next = {tqe_next = 0x0, tqe_prev = 0x1bb9dc0}, ev_next = {tqe_next = 0x7f4391ebda20, tqe_prev = 0x1bc0c00}, ev_timeout_pos = {ev_next_with_common_timeout = {tqe_next = 0xffffffff, tqe_prev = 0x0}, min_heap_idx = -1}, ev_fd = 6, ev_base = 0x1bc0aa0, _ev = {ev_io = {ev_io_next = {tqe_next = 0x0, tqe_prev = 0x1bc0fd0}, ev_timeout = {tv_sec = 0, tv_usec = 0}}, ev_signal = {ev_signal_next = {tqe_next = 0x0, tqe_prev = 0x1bc0fd0}, ev_ncalls = 0, ev_pncalls = 0x0}}, ev_events = 18, ev_res = 2, ev_flags = 130, ev_pri = 0 '\000', ev_closure = 2 '\002', ev_timeout = {tv_sec = 140733193388081, tv_usec = 6631108320}, ev_callback = 0x7f424a5f4aa7 <cmd_pipe_cb>, ev_arg = 0x7fff8b3eae60} #6 0x00007f424a5fd50b in child_init (rank=0) at jsonrpc_mod.c:135 pid = 0 #7 0x0000000000596a41 in init_mod_child (m=0x7f4391ab0db8, rank=0) at sr_module.c:898 __FUNCTION__ = "init_mod_child" #8 0x0000000000596779 in init_mod_child (m=0x7f4391ab1110, rank=0) at sr_module.c:895 __FUNCTION__ = "init_mod_child" #9 0x0000000000596d55 in init_child (rank=0) at sr_module.c:924 No locals. #10 0x00000000004aafd3 in main_loop () at main.c:1650 i = 24 pid = 84647 si = 0x0 si_desc = "udp receiver child=23 sock=38.106.58.4:5063\000n\000\000\000~/q\000\001\000\000\000\260\344\213OB\177\000\000\020\261>\213\377\177\000\000\032\264N\000\000\000\000\000`\261>\213\377\177\000\000\000\224\351\221C\177\000\000 \333\330OB\177\000\000\260\344\213OB\177\000\000$!\314\a\000\000\000\000\260\210A\000\001\000\000" nrprocs = 24 __FUNCTION__ = "main_loop" #11 0x00000000004b0b5b in main (argc=13, argv=0x7fff8b3eb3d8) at main.c:2533 cfg_stream = 0x1b1a010 c = -1 r = 0 tmp = 0x7fff8b3ecd59 "" tmp_len = 32579 port = -767281296 proto = 0 options = 0x707db8 ":f:cm:M:dVIhEeb:l:L:n:vKrRDTN:W:w:t:u:g:P:G:SQ:O:a:A:" ret = -1 seed = 189487301 rfd = 4 debug_save = 0 debug_flag = 0 dont_fork_cnt = 0 n_lst = 0x76 p = 0x7fff8b3eb2de "" __FUNCTION__ = "main" quit ``` --- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/296 [View Less]

3 22

Re: [sr-dev] Is there a sense in calling run_onsend() after the msg_send() function?
by Lucian Balaceanu 08 Sep '15

08 Sep '15

Hi Daniel, I must admit this run_onsend() patch for stateful replies creation was not quite a success story. However, I think it serves a practical purpose, for example in Homer tracing and could be useful for the community. Again, I propose my past solution, with some questions: 1. I am unsure if the place I introduced the run_onsend call is appropriate since the buf used for msg_send is constructed build_res_buf_from_sip_req and build_res_buf_from_sip_res calls. 2. Also, we can maybe … [View More]unite these if call branches I created: send_res = msg_send(&uas_rb->dst, buf, res_len); send_res = SEND_PR_BUFFER( uas_rb, buf, res_len ); 3. Do you think a get_send_socket snippet as follows should be inserted before the /*if (onsend_route_enabled(SIP_REPLY)){*/ : if(dst.send_sock == NULL) { dst.send_sock=get_send_socket(msg, &dst.to, dst.proto); if (dst.send_sock==0){ LM_ERR("cannot forward reply\n"); } } Thank you, Lucian On 10/29/2014 02:15 PM, Daniel-Constantin Mierla wrote: > Hello Lucian, > > I applied your patch with some fixes. > > I haven't checked with stateful replies, at some point a function from > core should be used. You can go ahead and see if it works, if not, let > me know and I can look into it as well. You can follow the callbacks > for TMCB_RESPONSE_OUT or TMCB_RESPONSE_FWDED inside tm code, they > should lead to the place where a sip response is going to be sent out. > > Cheers, > Daniel > > On 27/10/14 12:51, Lucian Balaceanu wrote: >> Hello Daniel, >> >> I must admit I only saw your mail last Friday. Until the 10th of >> October I was also on vacation. I know that you actually committed >> some of the changes together with your comments on the 12th this month. >> >> I don't know if we can consider the topic of the patch closed. As far >> as I understand, the state-full replies have not been addressed, >> right? (There should be a change in the t_reply.c) I followed the >> code to the relay_reply but I did not yet come to find the send >> function. Should I pursue further? >> >> Thank you, >> Lucian Balaceanu >> >>> Hi Lucian, >>> >>> somehow I forgot to follow up on this. But we need to get sorted out >>> soon, before we release, so it works as expected with the new >>> version. See more comments inline. >>> >>> >>> On 17/09/14 18:09, Lucian Balaceanu wrote: >>>> Hi Daniel, >>>> >>>> Please forgive me for my delay in responding to your mail. >>>> Please find attached a second version of the onsend_route_reply >>>> patch (which again has some problems). As per your previous >>>> indications I did the following: >>>> >>>> *Issue1* >>>>> From performances point of view, there can be added a config >>>>> parameter to enable running of onsend_route for replies: >>>>> >>>>> onsend_route_reply = 0|1 >>>> >>>> Following >>>> http://www.asipto.com/pub/kamailio-devel-guide/#c08add_parameters I >>>> have tried to add onsend_route_reply parameter. The code compiles, >>>> but when trying to start kamailio with this parameter inside, the >>>> parsing fails with syntax errors signaling: >>>> >>>> / 0(1321) :<core> [cfg.y:3423]: yyerror_at(): parse error in config >>>> file kamailio-basic.cfg.4.1, from line 107, column 1 to line 108, >>>> column 0: syntax error >>>> 0(1321) : <core> [cfg.y:3423]: yyerror_at(): parse error in config >>>> file kamailio-basic.cfg.4.1, from line 107, column 1 to line 108, >>>> column 0: >>>> ERROR: bad config file (2 errors)/ >>> >>> The issue is: >>> >>> +<INITIAL>{ONSEND_RT_REPLY} { yylval.intval=atoi(yytext); >>> + yy_number_str=yytext; return NUMBER; } >>> >>> It should be: >>> >>> +<INITIAL>{ONSEND_RT_REPLY} { yylval.intval=atoi(yytext); >>> + yy_number_str=yytext; return ONSEND_RT_REPLY; } >>> >>>> >>>> *Issue2* >>>>> #define onsend_enabled(rtype) >>>>> (onsend_rt.rlist[DEFAULT_RT]?((rtype==SIP_REPLY)?onsend_route_reply:1):0) >>>> That is to say you see it best to take the chek for >>>> onsend_rt.list[DEFAULT_RT] from inside run_onsend() function and >>>> call this onsend_enabled(...) before the run_onsend()? >>> >>> This is to detect whether the onsend_route should be executed for >>> SIP replies. The condition being: >>> >>> - if is a sip reply and onsend_route is set and the >>> onsend_route_reply parameter is 1 >>>> >>>> *Issue3* >>>>> On the other hand, is onsend_route also executed for local >>>>> requests? I had in mind it is only for received requests that are >>>>> forwarded ... Iirc, on onsend_route, the sip message is the one >>>>> received, the outgoing content being accessible via $snd(buf). >>>>> >>>> I agree with you with taking out the locally generated requests and >>>> only left the run_onsend call in do_forward_reply function (inside >>>> forward.c). >>>> Could you point me to the reply relaying function that is called >>>> for state-full processing? >>> Stateful processing for replies is mainly done in t_reply.c from tm >>> module. At some point there should be a send buffer function call. >>> >>> Cheers, >>> Daniel >>>> >>>> Thank you and sorry again for my late answer, >>>> Lucian >>> >>> -- >>> Daniel-Constantin Mierla >>> http://twitter.com/#!/miconda -http://www.linkedin.com/in/miconda >>> >>> >> > > -- > Daniel-Constantin Mierla > http://twitter.com/#!/miconda -http://www.linkedin.com/in/miconda [View Less]

2 6

[kamailio] Return CSCF_RETURN_FALSE if AAR is not generated (#314)
by Federico Favaro 07 Sep '15

07 Sep '15

Differentiate the cases where AAR is not sent because of an error and the cases where AAR is not sent because it is logically wrong to sent them at that point of the transaction. In this way, in the routing script it is possible to distinguish between an error and (for example) send back an error to the UE and when AAR is not generated because (for example) the answer does not contain an SDP or you are not in a SIP reply. In this case, you should not send back an error but go ahead with your … [View More]

4 6

← Newer
1
...
29
30
31
32
33
34
35
...
39
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev September 2015