sr-users September 2015

sr-users@lists.kamailio.org

82 participants
126 discussions

by Daniel-Constantin Mierla

Hello, I have some discount code for IIT RTC Conference & Expo, taking place in Chicago, IL, USA, during October 6-8, 2015. It gives an 100USD discount, which can save a bit or make some of the available tickets completely free (like Expo Plus admission). Should someone be interested, contact me directly via email. More details about the event can be found at: * http://www.rtc-conference.com/ I will be at the event during Oct 7 and 8, presenting on the morning of Oct 8, if anyone here coming to the event or happening to be in Chicago area and want to meet and chat about Kamailio, drop me an email as well. Cheers, Daniel -- Daniel-Constantin Mierla http://www.asipto.com

9 years, 2 months

assign_hf_value, hf_value_exists and exclude_hf_value broken in 4.3.2?

by Björn Bylander

Hello, 4.3.1 works well for us apart from the issue fixed by 93b297e16134b0e74cf83e3604da01355a52e700. Since 93b297e16134b0e74cf83e3604da01355a52e700 is included in 4.3.2 I tried upgrading one of our servers and now Kamailio won't even start as it apparently finds the way assign_hf_value, hf_value_exists and exclude_hf_value are used in our configuration to be incorrect. I enabled debug logging (WITH_DEBUG) and found the following: > 0(1894) DEBUG: <core> [route.c:872]: fix_actions(): fixing assign_hf_value() > 0(1894) ERROR: textopsx [textopsx.c:596]: fixup_hname_param(): ERROR: textops: cannot parse header near 'Privacy' > 0(1894) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:642 > 0(1894) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:644 > 0(1894) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:661 > ERROR: error -6 while trying to fix configuration Line 642 looks like this: assign_hf_value("Privacy", "id") Commenting it out leads to the following output: > 0(2217) DEBUG: <core> [route.c:872]: fix_actions(): fixing hf_value_exists() > 0(2217) ERROR: textopsx [textopsx.c:596]: fixup_hname_param(): ERROR: textops: cannot parse header near 'Privacy' > 0(2217) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1016 > 0(2217) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1019 > 0(2217) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1023 > ERROR: error -6 while trying to fix configuration Line 1016 looks like this: if (hf_value_exists("Privacy", "none")) { Commenting it out leads to the following output: > 0(2292) DEBUG: <core> [route.c:872]: fix_actions(): fixing exclude_hf_value() > 0(2292) ERROR: textopsx [textopsx.c:596]: fixup_hname_param(): ERROR: textops: cannot parse header near 'Accept' > 0(2292) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1020 > 0(2292) ERROR: <core> [route.c:1154]: fix_actions(): fixing failed (code=-6) at cfg:/etc/kamailio/kamailio.cfg:1023 > ERROR: error -6 while trying to fix configuration Lines 1020 and 1021 look like this exclude_hf_value("Accept", "application/media_control+xml"); exclude_hf_value("Accept", "application/x-broadworks-call-center+xml"); Commenting them out makes Kamailio start without complaining. Btw, "kamailio -c" thinks the configuration file is fine. So, is our use of assign_hf_value, hf_value_exists and exclude_hf_value incorrect (looking at the textopsx documentation I can't see how) or was a bug introduced with 4.3.2 which causes this behaviour? Regards, Björn Bylander

9 years, 2 months

Kamailio challenges repeatedly

by Austin Einter

I am trying to register with Kamailio server from my custom endpoint. I have below call flows Register -> 401 Register -> 401 When I saw Kamailio log, I do not see any error. Looks auth response is fine. Then why 401 repeatedly. Log is given blow. Please guide to fix this issue. Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth_db [authorize.c:208]: get_ha1(): HA1 string calculated: 8749f9da135d71526725a337008df1d5 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [api.c:211]: auth_check_response(): check_response: Our result = '4aa70d676021329550b3d17e17238fac' Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [api.c:218]: auth_check_response(): check_response: Authorization is OK Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:81]: db_free_columns(): freeing 1 columns Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:85]: db_free_columns(): freeing RES_NAMES[0] at 0x7f8a24d5e1d0 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:94]: db_free_columns(): freeing result names at 0x7f8a24d7ceb0 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:99]: db_free_columns(): freeing result types at 0x7f8a24d7cef0 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:54]: db_free_rows(): freeing 1 rows Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_row.c:97]: db_free_row(): freeing row values at 0x7f8a24d5e260 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:62]: db_free_rows(): freeing rows at 0x7f8a24d5e218 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [db_res.c:136]: db_free_result(): freeing result set at 0x7f8a24d7ce18 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [challenge.c:127]: get_challenge_hf(): build_challenge_hf: realm='10.10.64.125' Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: auth [challenge.c:269]: get_challenge_hf(): auth: 'WWW-Authenticate: Digest realm="10.10.64.125", nonce="VfbImFX2x2yEeE8kEuL2IXqW2TgKu+eC"#015#012' Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: sl [sl.c:296]: send_reply(): reply in stateless mode (sl) Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [msg_translator.c:206]: check_via_address(): check_via_address(10.3.2.18, 10.3.2.18, 0) Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2283]: tcpconn_send_put(): tcp_send: send from reader (2650 (9)), reusing fd Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2518]: tcpconn_do_send(): tcp_send: sending... Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2552]: tcpconn_do_send(): tcp_send: after real write: c= 0x7f8a1c5dbe78 n=445 fd=9 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [tcp_main.c:2553]: tcpconn_do_send(): tcp_send: buf=#012SIP/2.0 401 Unauthorized#015#012Via: SIP/2.0/TCP 10.3.2.18:6970;branch=z9hG4bK1875333638#015#012From: < sip:262099922700000@10.10.64.125;user=phone>;tag=209355482#015#012To: < sip:+499922700000@10.10.64.125;user=phone>;tag=8345fd11d20ec1ca026994bf51313cb0.a2c6#015#012Call-ID: 1340939517(a)10.10.64.125#015#012CSeq: 3 REGISTER#015#012WWW-Authenticate: Digest realm="10.10.64.125", nonce="VfbImFX2x2yEeE8kEuL2IXqW2TgKu+eC"#015#012Server: kamailio (4.2.5 (x86_64/linux))#015#012Content-Length: 0#015#012#015#012 Sep 14 18:41:08 necs107 kamailio[2650]: DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil) Sep 14 18:41:08 necs107 kamailio[2650]: message repeated 5 times: [ DEBUG: <core> [usr_avp.c:643]: destroy_avp_list(): DEBUG:destroy_avp_list: destroying list (nil)]

9 years, 2 months

Hex to Dec conversion

by Yufei Tao

Hi, I want to convert a Hex number string into a Dec number string, e.g. Hex number "123" into Dec number "291". What is the best way? I didn't find any transformation for this. Thank you! Yufei

9 years, 2 months

Very high load average after upgrade to Kamailio v4.3.2

by M S

Hi, Over last weekend i upgraded one of my test servers from Kamailio v4.3.1-4d1b65 to latest stable release v4.3.2-07690f and now kamailio goes crazy even with single call (I am using same db and configuration of course). As soon as call establishes system load average (as seen in top command) starts increasing and soon it increases beyond 6.0 and system becomes completely unresponsive, sip messages are no longer being processed by kamailio service. Even after call hangup, system remains under high load. The "htop" indicates that IO Wait time has increased substantially. Any idea what is causing this? For now i have reverted by to v4.3.1-4d1b65 but can go to v4.3.2-07690f again if you need further info or testing. Thank you.

9 years, 2 months

Concurrent calls after forked invite

by Lukas Hauser

Hello, I have two UACs registered to kamailio v4.0.4 with the same URI. (bob(a)example.com) Then a third registered UAC (alice(a)example.com) sends an invite to bob(a)example.com. Both bob UACs accept the call and respond with a 200 Ok. The statefull proxy now takes the first one and cancels the second one. In my case I need both responses to be send back to alice through the proxy. I want the Invite to be forked in parallel (works) and both calls to get connected concurrently (does not work). Is there such a feature in the statefull proxy? Can this be done using a stateless proxy? I stumbled on some proposal about a "New Dialog Module Design" [1]. This is excetly what I'm looking for. Is this still just a proposal? Thanks! Lukas PS: I also posted this question in stackoverflow [2] [1] http://www.kamailio.org/dokuwiki/doku.php/modules-new-design:dialog-module-… [2] http://stackoverflow.com/questions/32519551/kamailio-concurrent-calls-after…

9 years, 2 months

ha1 password authentication without plain text password

by Nabeel

Hi, My SIP client only uses the 'ha1' password column from the database to authenticate users. It does not require the 'password' column. However, I am not able to register without having the plain text password present in the 'password' column in the database. I need to change this behaviour so that user registration will occur using only the ha1 encoded password column. How can I make this change? I tried commenting out and changing the 'password_column' attribute in the config but could not get it to work.

9 years, 2 months

selecting memory manager at startup

by Daniel-Constantin Mierla

Hello, (cross-posting as it is relevant to user community as well). I just pushed a bunch of patches to master branch that will allow selecting the memory manger at kamailio startup, no longer needed to re-compile sources. There are two new command line parameters: * -x name: select the memory manager for shm * -X name: select the memory manager for pkg * if -x is provided but -X is not provided, then pkg uses same memory manager as shm * name can be: * fm - fast malloc (f_malloc) * qm - quick malloc (q_malloc) * default memory manager is fm (what was default so far) Both f_malloc and q_malloc are now compiled, selecting one or the other being possible. Other managers expected to be added in the list soon, especially TLSF, added not that long ago by Camille Oudot. Maybe reviving Doug Lea malloc (existing in dl_malloc.c) worth a try now that can be easily used. The debugging mode for each memory manager is controlled by DB_SR_MEMORY define via Makefile.defs -- right now it is enabled. All enabled memory mangers must be compiled either with or without DB_SR_MEMORY (it won't work to have one memory manger with DB_SR_MEMORY and another one without). Using system malloc for private (pkg) memory is possible by removing the define of PKG_MALLOC from Makefile.defs (same as it was before). This is a mode suitable for troubleshooting using external tools such as valgrind, because it does inline replacement of pkg_malloc() with malloc(), so those tools can track the place of allocation. I plan to add a system malloc custom manager, to allow selecting it with -X (system malloc won't work for shm management, because it is only for private memory). There is no performance impact at runtime, it is only the startup procedure that replaces the pointers to memory management functions. Hopefully with the new mechanism will be able to track easier memory issues -- e.g., qm malloc is better for troubleshooting, using it no longer requires recompilation, just starting kamailio with -x qm. Feedback, especially testing, will be very appreciated! Cheers, Daniel -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

9 years, 2 months

no response, re-route calls to a different address

by Al S

Hi, Can we make Kamailio to re-route calls from an address that does not respond to a different address? Thanks,Al

9 years, 2 months

Kamailio v4.3.2 Released

by Daniel-Constantin Mierla

Hello, Kamailio SIP Server v4.3.2 stable release is out. This is a maintenance release of the latest stable branch, 4.3, that includes fixes since release of v4.3.1. There is no change to database schema or configuration language structure that you have to do on previous installations of v4.3.x. Deployments running previous v4.x.x versions are strongly recommended to be upgraded to v4.3.2. For more details about version 4.3.2 (including links and guidelines to download the tarball or from GIT repository), visit: * http://www.kamailio.org/w/2015/09/kamailio-v4-3-2-released/ RPM, Debian/Ubuntu packages will be available soon as well. Cheers, Daniel -- Daniel-Constantin Mierla - http://www.asipto.com http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda

9 years, 2 months

← Newer
1
...
6
7
8
9
10
11
12
13
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 September 2015