sr-users September 2012

sr-users@lists.kamailio.org

78 participants
138 discussions

pseudovariable values written from app_lua sometimes appear incorrect

by elactrum＠jamailca.com

Hi, I am using app_lua to frequently store some data in htable and avp entries, using sr.pv.sets. When I read the values using sr.pv.get immediately after writing them, they seem correct. However, when I read them later from Lua, I have noticed that sometimes the value is incorrect or nil. Am I doing something wrong? The following code uses rtimer to duplicate the problem on startup, printing the errors to syslog. Tested on version: kamailio 3.3.1 (i386/linux) 2d0f6f ############### # kamailio.cfg ############### loadmodule "pv.so" loadmodule "xlog.so" loadmodule "htable.so" loadmodule "rtimer.so" loadmodule "app_lua" modparam("htable", "htable", "status=>size=14;autoexpire=0;") modparam("rtimer", "timer", "name=ta;interval=10;mode=1") modparam("rtimer", "exec", "timer=ta;route=LUA_TEST") # the following path may need to change depending on filesystem setup modparam("app_lua", "load", "/etc/kamailio/kamailio.lua") route { route(LUA_TEST); } route[LUA_TEST] { $var(lua_test_key) = $(pp{s.toupper}) + "::"; lua_runstring("htable_test([[status=>$var(lua_test_key)]])"); lua_runstring("avp_test([[status=>$var(lua_test_key)]])"); } ---------------- -- kamailio.lua ---------------- -- Test of sr.pv operations in Lua function htable_test (namekey) local pvar_prefix = "$sht("..namekey pvar_test(pvar_prefix) end function avp_test ( name ) local pvar_prefix = "$avp("..name pvar_test(pvar_prefix) end function pvar_test ( pvar_prefix ) for value = 10000, 10050 do local pvar = pvar_prefix..value..")" --sr.log("info", "Lua attempting to set '"..pvar.."' to value '"..value.."'") sr.pv.sets(pvar, value) end for value = 10000, 10050 do -- now we check what was stored local pvar = pvar_prefix..value..")" local checkvar = sr.pv.get(pvar) if ( tostring(checkvar) ~= tostring(value) ) then sr.err(string.format("CHECK: Lua checking pvar '%s' and got value '%s' which is NOT '%s'", tostring(pvar), tostring(checkvar), tostring(value) )) end end end -- end of kamailio.lua Thanks, -Andrew

11 years, 9 months

Core fm_realloc function

by Bruno Bresciani

Hi all, I observed two at 0x08173bf0 in fm_realloc (qm=0xb5f7d000, p=0xb61f0bc0, size=0) at mem/f_malloc.c:536. I don't know exactly what may be caused this core because the debug of kamailio is disabled, but looking at backtrace (gdb) and source code I could notice a relationship with TLS connection establishment (handshake). Other important fact is that core was generated by the kamalio itself with signal 6 (abort) because it can't find the pointer to memory realloc. I'd like to know if someone already observed this issue and if my analyse above is correct? Bellow is backtrace full with gdb: Core was generated by `/home2/local/kamailio/sbin/kamailio -P /var/run/kamailio.pid'. Program terminated with signal 6, Aborted. #0 0x00f30402 in __kernel_vsyscall () (gdb) (gdb) (gdb) (gdb) (gdb) bt full #0 0x00f30402 in __kernel_vsyscall () No symbol table info available. #1 0x009fec10 in raise () from /lib/libc.so.6 No symbol table info available. #2 0x00a00521 in abort () from /lib/libc.so.6 No symbol table info available. #3 0x08173bf0 in fm_realloc (qm=0xb5f7d000, p=0xb61f0bc0, size=0) at mem/f_malloc.c:536 f = (struct fm_frag *) 0xb61f0bb8 pf = <value optimized out> orig_size = 18 L=ÃbÂ¬Ã2n = (struct fm_frag *) 0xb61f0bd2 ptr = <value optimized out> hash = 23548 #4 0x0051a87f in ser_realloc (ptr=0xb61f0bc0, size=32) at ../../mem/shm_mem.h:266 No locals. #5 0x00460295 in OPENSSL_cleanse () from /lib/libcrypto.so.6 No symbol table info available. #6 0x004609f7 in CRYPTO_realloc () from /lib/libcrypto.so.6 No symbol table info available. #7 0x003efb22 in sk_insert () from /lib/libcrypto.so.6 No symbol table info available. #8 0x003efbaa in sk_push () from /lib/libcrypto.so.6 No symbol table info available. #9 0x007c2ac3 in ssl_bytes_to_cipher_list () from /lib/libssl.so.6 No symbol table info available. #10 0x007aa9f3 in ssl3_get_client_hello () from /lib/libssl.so.6 No symbol table info available. #11 0x007ab815 in ssl3_accept () from /lib/libssl.so.6 No symbol table info available. #12 0x007c1c3a in SSL_accept () from /lib/libssl.so.6 No symbol table info available. #13 0x005278e3 in tls_accept (c=0xb621af88, error=0xbf91dfc8) at tls_server.c:346 ret = <value optimized out> ssl = (SSL *) 0xb61c1878 cert = <value optimized out> tls_c = (struct tls_extra_data *) 0xb6208e58 tls_log = <value optimized out> #14 0x0052da8e in tls_read_f (c=0xb621af88, flags=0xbf91e200) at tls_server.c:1028 r = (struct tcp_req *) 0xb621affc bytes_free = 4095 bytes_read = 70 read_size = 4095 ssl_error = 0 ssl_read = 0 ssl = (SSL *) 0xb61c1878 rd_buf = "\026\003\001\000A\001\000\000=\003\001OÃ¿\vÂ¡ywP\fkÃDÃ 0/\000\a\000\005\001\000ÃÃÃÃ¯000\000\026\0009\0008\0005\000\026\000\023\000\n\0003\0002\00 202i<Ã¤<Ã¥Ã¾\031Ã¬234Â \237Ãª030Y){lÑ¶"...06Ã'Ãr9Ã¬Ã«Â¸{[Â©\t\205\037\036Ã¿HPH5Âµ\t(Ã©32Ã027Ã¦Ã²036Â¾\"\rÔ¤YÃ215uÂº\027)Ã¶000Ã±215\vÃÃ Ã©Ea\023xÃ©J\206T\204CÃ wr_buf = "\027\003\001\003Â wÂ²'\016Ñ¼Ã033ÃLÃ021Ã)Ã\220hnLÂ¦\020XÃª\236\200\tIhÃÂ¸Sf\234Ã\rÃ ?Â¯Â¼\024FÃ\200Âª/\2264RÃaÃÂ¤IpXÂ»Â¨Ã035Ã¤Qh\211Ã026Ã½4ÃU+\asrÂ£/`Â¤OÃ»1AÊ¹qUÜ¿Â·vÂ±Ã¼\205"... rd = {buf = 0xbf90dfa4 "\026\003\001", pos = 70, used = 70, size = 65536} wr = { buf = 0xbf8fdfa4 "\027\003\001\003Â wÂ²'\016Ñ¼Ã033ÃLÃ021Ã)Ã\220hnLÂ¦\020XÃª\236\200\tIhÃÂ¸Sf\234Ã\rÃ ?Â¯Â¼\024FÃ\200Âª/\2264RÃaÃÂ¤IpXÂ»Â¨Ã035Ã¤Qh\211Ã026Ã½4ÃU+\asrÂ£/`Â¤OÃ»1AÊ¹qUÜ¿Â·vÂ±Ã¼\205"..., pos = 0, used = 0, size = 65536} tls_c = (struct tls_extra_data *) 0xb6208e58 enc_rd_buf = (struct tls_rd_buf *) 0x0 n = 0 flush_flags = <value optimized out> err_src = 0x541a83 "TLS read:" x = <value optimized out> #15 0x08158ade in tcp_read_headers (c=0xb621af88, read_flags=0xbf91e200) at tcp_read.c:406 bytes = -1 remaining = <value optimized out> p = <value optimized out> r = (struct tcp_req *) 0xb621affc #16 0x08158fd4 in tcp_read_req (con=0xb621af88, bytes_read=0xbf91e204, read_flags=0xbf91e200) at tcp_read.c:871 bytes = <value optimized out> total_bytes = 0 resp = <value optimized out> size = <value optimized out> req = (struct tcp_req *) 0xb621affc dst = {send_sock = 0x1, to = {s = {sa_family = 57540, sa_data = "\221Â¿\020\000\000\000\000\000\000\000\020\000\000"}, sin = {sin_family = 57540, sin_port = 49041, sin_addr = {s_addr = 16}, sin_zero = "\000\000\000\000\020\000\000"}, sin6 = {sin6_family = 57540, sin6_port = 49041, sin6_flowinfo = 16, sin6_addr = {in6_u = {u6_addr8 = "\000\000\000\000\020\000\000\000\001\000\000\000\001\000\000", u6_addr16 = {0, 0, 16, 0, 1, 0, 1, 0}, u6_addr32 = {0, 16, 1, 1}}}, sin6_scope_id = 12}}, id = -1080958468, proto = 4 '\004', send_flags = {f = 0 '\0', blst_imask = 0 '\0'}} c = 10 '\n' #17 0x08159a0f in handle_io (fm=0x83296b0, events=1, idx=-1) at tcp_read.c:1150 ret = 4 n = 4 read_flags = 1 con = (struct tcp_connection *) 0xb621af88 s = 12 resp = <value optimized out> t = <value optimized out> #18 0x0815d653 in tcp_receive_loop (unix_sock=35) at io_wait.h:1091 No locals. ---Type <return> to continue, or q <return> to quit--- #19 0x0812885b in tcp_init_children () at tcp_main.c:4819 r = 3 reader_fd_1 = 35 pid = <value optimized out> si = <value optimized out> #20 0x080ad412 in main_loop () at main.c:1632 i = 4 pid = <value optimized out> si = (struct socket_info *) 0x0 si_desc = "udp receiver child=3 sock=192.168.166.31:5060 \000\221Â¿\002\000\000\000/\200\220\000\001\000\000\000\000\000H\000Â¨Ã¤21Â¿\001\000\000\000Â°Â¶Ã¨026Â¶\000\000\000\000\000ÃÂµ\030s2\b\002\000\000\000Ã¢f\b\000ÃÂµ\001\000\000\000\000\000\000\000\001\000\000\000\000\000\000\000Ã¿Ã¿Ã¿Ã¿Â¸Ã¤21Â¿" #21 0x080afbe7 in main (argc=3, argv=dwarf2_read_address: Corrupted DWARF expression. ) at main.c:2398 cfg_stream = (FILE *) 0x8a2d008 c = <value optimized out> r = 0 tmp = 0xbf91e674 "\212Ã¾\221Â¿\233Ã¾\221Â¿Â°Ã¾\221Â¿Â»Ã¾\221Â¿Ã\221Â¿Ã¹1Â¿\020Ã¿\221Â¿DÃ¿\221Â¿LÃ¿\221Â¿WÃ¿\221Â¿]Ã¿\221Â¿oÃ¿\221Â¿{Ã¿\221Â¿\202Ã¿\221 tmp_len = 10492229 port = 136192361 proto = -1080957480 ret = <value optimized out> seed = 21782655 rfd = 4 debug_save = <value optimized out> debug_flag = 0 dont_fork_cnt = 0 n_lst = <value optimized out> p = <value optimized out> Best Regards

11 years, 10 months

TCP Path received quotes

by Spencer Thomason

Hello, I'm forwarding registrations to Freeswitch and adding a Path header using add_path_received() for endpoints behind NAT. When TCP is used, this results in a header like this: Path: <sip:a.a.a.a:5070;lr;received="sip:b.b.b.b:35430;transport=tcp"> Freeswitch doesn't like the transport protocol inside the quotations and refuses to route a call to the registered user. Constructing the header manually without the quotes such as: append_hf("Path: <sip:$Ri:$Rp;lr;received=sip:$si:$sp;transport=$pr>\r\n"); solves the problem. Is there a reason for the quotes? Best Regards, Spencer

11 years, 10 months

[Kamailio-Users] BYE message not relayed to caller

by Vikram Ragukumar

Hello, My setup includes a cellphone that uses Wi-Fi to hookup to the internet with IP 192.168.1.101. Cellphone app, tries to register with VOIPSwitch through an outbound proxy server(Kamailio + rtpproxy), which rewrites SDP to force rtp through an rtpproxy. I can make a call from the cellphone to a PSTN number. When the PSTN endpoint hangs up, VOIPSwitch relays a BYE message to the proxy that looks like : No. Time Source Destination Protocol Info 27 18.383929 IPaddr_VoipSwitch IPaddr_proxy SIP Request: BYE sip:1234@IPaddr_VoipSwitch Frame 27 (420 bytes on wire, 420 bytes captured) Ethernet II, Src: Unispher_40:b5:39 (00:90:1a:40:b5:39), Dst: Supermic_bd:b9:bc (00:30:48:bd:b9:bc) Internet Protocol, Src: IPaddr_VoipSwitch , Dst: IPaddr_proxy User Datagram Protocol, Src Port: sip (5060), Dst Port: 7160 (7160) Session Initiation Protocol Request-Line: BYE sip:1234@IPaddr_VoipSwitch SIP/2.0 Method: BYE [Resent Packet: False] Message Header Route: <sip:IPaddr_proxy:7160;lr=on;nat=yes> CSeq: 1 BYE Via: SIP/2.0/UDP IPaddr_VoipSwitch:5060; branch=z9hG4bk180242100434182912333954 From: sip:5678@IPaddr_VoipSwitch;tag=18024210041929123187506289 Call-ID: LUOyIDm-ecy36NcUfj5G3v1lM6g5snkM To: "1234" <sip:1234@IPaddr_VoipSwitch>;tag=9XHJmiuf58vTrF7.vwflEK-G63JVPQSi Content-Length: 0 The request URI in the above message is the IP address of VOIPSwitch itself, which causes the proxy to forward the BYE message back to VOIPSwitch. The cellphone never receives the BYE message and consequently never hangs up. Any suggestions on how i can get around this problem ? Thanks and Regards, Vikram.

11 years, 11 months

Getting started with Kamailio

by Joel Smith | VOZELIA

Hi, First of all say that I'm new to Kamailio. I've been working with asterisk for a while now and it's time to get started with the sip router project. My idea for a start is to reduce the load of our asterisk servers and once we have good knowledge on how kamailio works, migrate some of our services. I've setup a server in our lab with kamailio 3.3.0 and siremis 3.3.0, created a user (subscriber) and registered with a softphone. So far OK. Now I'm trying to make a call and route it through one of our asterisk servers for testing. To do this I need LCR module (thanks Sébastien, I wasn't subscribed to this list yet) and configure it. After reading http://kamailio.org/docs/modules/stable/modules/lcr.html#id2553110 I've added in kamailio.cfg: #!define WITH_LCR #!ifdef WITH_LCR loadmodule "lcr.so" #!endif #!ifdef WITH_LCR # ----- lcr params ----- modparam("lcr", "db_url", DBURL) modparam("lcr", "gw_uri_avp", "$avp(i:709)") modparam("lcr", "ruri_user_avp", "$avp(i:500)") modparam("lcr", "tag_avp", "$avp(lcr_tag)") #!endif And now I see LCR module being loaded at startup. But, I don't understand what gw_uri_avp, ruri_user_avp or tag_avp mean. Where can I find some doc/manual to understand what AVP means and does? (For example the $avp(i:709), etc.) I've added a LCR GW, LCR TARGET and LCR RULE with the following data (I have no idea if it's completely wrong): mysql> select * from lcr_gw; +----+--------+---------+--------------+--------------------------+------+--------+------------+-----------+-------+--------+------+-------+---------+ | id | lcr_id | gw_name | ip_addr | hostname | port | params | uri_scheme | transport | strip | prefix | tag | flags | defunct | +----+--------+---------+--------------+--------------------------+------+--------+------------+-----------+-------+--------+------+-------+---------+ | 1 | 0 | TEST | XX.XXX.XXX.X | test12345678.testing.com | 5060 | NULL | 1 | 1 | NULL | NULL | NULL | 0 | NULL | +----+--------+---------+--------------+--------------------------+------+--------+------------+-----------+-------+--------+------+-------+---------+ 1 row in set (0.00 sec) mysql> select * from lcr_rule; +----+--------+--------+----------+-------------+---------+---------+ | id | lcr_id | prefix | from_uri | request_uri | stopper | enabled | +----+--------+--------+----------+-------------+---------+---------+ | 1 | 1 | .* | | | 0 | 1 | +----+--------+--------+----------+-------------+---------+---------+ 1 row in set (0.00 sec) mysql> select * from lcr_rule_target; +----+--------+---------+-------+----------+--------+ | id | lcr_id | rule_id | gw_id | priority | weight | +----+--------+---------+-------+----------+--------+ | 1 | 1 | 1 | 1 | 1 | 1 | +----+--------+---------+-------+----------+--------+ 1 row in set (0.00 sec) mysql> Am I still missing basic stuff to be able to place a call ? (To get started I'd like to route all calls to our Asterisk server) I'm glad to read documentation so If all of this is already somewhere please guide me cause I haven't found too much... Thanks in advanced. Regards, Joel.

12 years

Re: [SR-Users] RTPProxy with kamailio : How to get calls count?

by Alex Balashov

I'd be curious to know if your performance might actually be higher, owing to improved CPUs since the study was done, hyperthreading, more frames per NIC interrupt, etc. -- Alex -- Sent from my Samsung mobile, and thus lacking in the refinement one might expect from a proper keyboard. Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 Tel: +1-678-954-0670 Web: http://www.evaristesys.com/Mino Haluz <mino.haluz(a)gmail.com> wrote:Thank you, setting ulimits worked! And the performance is the same as stated in the document I mentioned! :) One more thing, I found these errors in syslog: Sep 13 18:38:18 perftest kamailio[5268]: ERROR: <core> [parser/sdp/sdp.c:211]: Invalid payload location Sep 13 18:38:18 perftest kamailio[5268]: ERROR: <core> [parser/sdp/sdp.c:227]: Invalid payload location Sep 13 18:38:18 perftest kamailio[5270]: ERROR: <core> [parser/sdp/sdp.c:227]: Invalid payload location This is possibly something related to my sipp scenario, this is the INVITE sent from sipp <![CDATA[ INVITE sip:800@perftest.vm SIP/2.0 Via: SIP/2.0/[transport] 10.0.2.36:[local_port];branch=[branch] From: "700" <sip:500@10.0.2.36>;tag=[call_number] To: <sip:800@perftest.vm> Call-ID: [call_id] CSeq: 1 INVITE Contact: "700" <sip:700@10.0.2.36:[local_port]> Max-Forwards: 70 Subject: Performance Test Content-Type: application/sdp Content-Length: [len] v=0 o=user1 53655765 2353687637 IN IP[local_ip_type] 10.0.2.36 s=- c=IN IP[local_ip_type] 10.0.2.36 t=0 0 m=audio [auto_media_port] RTP/AVP 8 a=rtpmap:8 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-11,16 ]]> Do you see something that could cause this error ? Otherwise the call is initiated ok, but I really dont understand what is so strange to kamailio in this INVITE. On Thu, Sep 13, 2012 at 6:37 PM, Peter Lemenkov <lemenkov(a)gmail.com> wrote: > 2012/9/13 Mino Haluz <mino.haluz(a)gmail.com>: >> You mean on the proxy side? I'm running rtpproxy as root, limits are >> still applied ? ulimit -s unlimited should do the trick ? > > Yes, they usually applied even for superuser, and yes - this should > help (if that's the issue). > > > -- > With best regards, Peter Lemenkov. > > _______________________________________________ > 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

12 years

[OT] the role of SBCs

by Daniel-Constantin Mierla

Hello, based on the outcome of the discussion carried in the thread: http://lists.sip-router.org/pipermail/sr-users/2012-August/074480.html I am looking again the clarify some aspects out there in the VoIP world. So, as mainly dealing with proxy/sip signaling deployments, it's very often to be the first one hit by support issues claiming things don't work. Then you investigate and end up in conclusions like in the above thread: "The problem was at the SBC, __where I did not expect it__." The underlined part heats me up a bit, because I never understood from where it comes this perception that SBC is a MUST-TO-HAVE and the PERFECT (never mistaken or breaking things) node in a VoIP networks. To some extent, the SBC is just a very costly SIP ALG, and a SIP ALG is there to break the things. I don't want to start like a flame war, but is it something that I am obviously missing in regards to what benefits a SBC can bring? I see only inconveniences: - another point of failure - it is a b2bua, therefore very unlikely to offer the same performances of a proxy - if transcoding is needed, a media server can be used behind the proxy, properly protected of attacks by the proxy and eventually deployed as a farm load balanced by the proxy - if topology hinding is wanted in the b2bua fashion (not the proxy fashion with encoding headers), then the b2bua can be behind the proxy, properly protected of attacks by the proxy and eventually deployed as a farm load balanced by the proxy - nat traversal was solved long time ago in proxy environment, being scalable by deploying a farm of rtp proxy I don't want to go to other features, including the transport layer, it's a clear win of the proxy in my experience (ok, being deep involved in this project). Then, what makes the SBC so desirable in many companies/voip deployments? If any SBC user here that can share, what was the reason to buy such a device? Any conceptual functionality that cannot be achieved with the proxy as the first hop in front of the (wild) clients? Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Kamailio Advanced Training, Berlin, Nov 5-8, 2012 - http://asipto.com/u/kat

12 years

is kamilio support RFC5626 now ?

by mike

dear kamilio developers : i read the kamilio 3.3.0' s new features , it say it support outbound , and i have place to handle reg-id and sip.instance . so , i wonder if the kamilio3.3.0 support RFC5626 now，so that the kamilio can be used as a edge proxy . i ask why because i can't find where kamilio add flow-token and path for the register request. thanks

12 years, 1 month

OpenSER/Kamailio Support? - Forwarding SIP INVITE Packets

by Eddie Elric

Hello fellow OpenSER/Kamailio users, I hope this is the right method of contact - I was unable to find a forum on which to post any queries. In essence, I've set up a Kamailio server of the latest version - logging on to clients works fine, etc. The idea of my setting up was for forwarding SIP messages to our test server, that's where I got stuck. The following link explains everything on Kamailio it seems - http://www.kamailio.org/wiki/cookbooks/3.3.x/core#forward So, I've added to the kamailio.cfg the following - forward("10.0.0.10","5060"); But you see, I'm not sure where I should have added it. I've tried adding to a variety of places, such as - route[SIPOUT] and onreply_route[MANAGE_REPLY] - but none are working. Cheers guys/girls. Best, Eddie

12 years, 1 month

compilation warnings

by Vieri

Hi, On a Gentoo Linux system I'm getting the following compile-time warnings (kamailio-3.3.1 ebuild): * python_msgobj.c:529:5: warning: dereferencing type-punned pointer will break strict-aliasing rules * ld_con.c:241:4: warning: implicit declaration of function 'ldap_simple_bind_s' * perl.c:340:2: warning: null argument where non-null required (argument 2) * perl.c:340:2: warning: null argument where non-null required (argument 1) Hopefully I can just ignore these messages. Thanks, Vieri

12 years, 1 month

Jump to page:

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 September 2012