sr-users October 2019

sr-users@lists.kamailio.org

59 participants
83 discussions

Releasing Kamailio v5.2.5
by Daniel-Constantin Mierla 10 Oct '19

10 Oct '19

Hello, I am considering to release Kamailio v5.2.5 out of the latest branch 5.2 on Thursday, October 10. As usual, if you noticed any patch that should be backported or you are aware of some issue not yet reported, announce it to sr-dev or via bug tracker. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- https://asipto.com/u/kat

1 1

Testing kxlibssl prng for tls module
by Daniel-Constantin Mierla 09 Oct '19

09 Oct '19

Hello Marco, I am writing to see if you can test the kxlibssl prng that I just added for tls module. I want to see if exposes the same issue you reported in: * https://github.com/kamailio/kamailio/issues/2077 If you can't test with master branch, you need to backport two commits: * https://github.com/kamailio/kamailio/commit/99eafac2d92533ba93cd8244173aef0… * https://github.com/kamailio/kamailio/commit/a52f05087a211bfecd36300907d0bff… Then set: modparam("tls", "rand_engine", "kxlibssl") The latest branch 5.2 has the code for setting custom prng backported. The idea behind kxlibssl prng is to reuse the function of the default libssl v1.1.x prng, but guarded by a kamailio specific mutex. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- https://asipto.com/u/kat

2 2

Kamailio Developers Meeting, Nov 14-15, 2019, in Dusseldorf
by Daniel-Constantin Mierla 09 Oct '19

09 Oct '19

Hello, Kamailio SIP Server project is organizing another meeting of its developers during November 14-15, 2019, hosted again by sipgate.de in Dusseldorf, Germany. The event is intended to facilitate the interaction between Kamailio developers and to offer a convenient environment for working together on several topics of high interest for the project, including writing code for Kamailio and its tools, improving documentation, or discuss about future development. Everyone from the community is welcome to join. Please note we have a limited capacity of 20 seats in the meeting room. Also, very important to be aware that this is not an event to learn how to use Kamailio. More details about the event, the venue, how to register, are available at: * https://www.kamailio.org/w/developers-meeting/ Looking forward to those two intensive hacking Kamailio days in Dusseldorf! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- https://asipto.com/u/kat

1 1

Fred on FLOSS Weekly 16 Oct
by jungle boogie 09 Oct '19

09 Oct '19

Hi All, I'm happy to see friendly Fred Posner on FLOSS Weekly next Wednesday (16 October, 2019) to discuss Kamailio. If you can, tune in live and see how the interview goes. Recording is at 9:30am Pacific (-7 UTC) / 16:30 UTC. https://twit.tv/shows/floss-weekly Upcoming guests: https://docs.google.com/spreadsheets/d/1_dOHpYlzRlMb0JEzwUcAUflPz8PLq7dKkos… Thanks for being on the show, Fred! Best, j.b.

1 0

exit after www_challenge
by PICCORO McKAY Lenz 08 Oct '19

08 Oct '19

i have the code with an exit, i dont know if are correct that "exit" in that line? or not? help me please? # authenticate the REGISTER requests (uncomment to enable auth) #!ifdef WITH_ASTERISK if (!www_authorize("$td", "sipusers")) #!else if (!www_authorize("$td", "subscriber")) #!endif { www_challenge("$td", "0"); exit; } if ($au!=$tU) { sl_send_reply("403","Forbidden auth ID"); exit; } consume_credentials(); Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com

4 4

Error parsing parameter value
by Duarte Rocha 08 Oct '19

08 Oct '19

Greetings, I'm testing some parameters actions and i found a weird behaviour This is my code for the test : $var(Parameter_List) = "blue=twelve;green=twe\"lve\";yellow=\"twelve\""; xerr("Parameter List = $var(Parameter_List)"); xerr("Value of Parameter blue = $(var(Parameter_List){param.value,blue})"); xerr("Value of Parameter green = $(var(Parameter_List){param.value,green})"); xerr("Value of Parameter yellow = $(var(Parameter_List){param.value,yellow})"); The printed logs are the following : ERROR: <script>: Parameter List = blue=twelve;green=twe"lve";yellow="twelve" ERROR: <script>: Value of Parameter blue = twelve ERROR: <script>: Value of Parameter green = twe"lve" ERROR: <script>: Value of Parameter yellow = twelve I have also tried setting the string as : $var(Parameter_List) = 'blue=twelve;green=twe"lve";yellow="twelve"'; But the results were similar The "" are not recognized in some scenarios. Is this intended behaviour or should i submit it as a bug? Best Regards, Duarte Rocha

3 8

Bad BYE request
by Duarte Rocha 08 Oct '19

08 Oct '19

Greetings, This is a repeated problem, but i have more info now. Please help understand if there is a problem on my code or if there is any kind of Kamailio bug. On the first INVITE of every call i apply uac_replace_from() and uac_replace_to() in order to normalize numeration. I have the restore_mode set as "auto". The original numeration is : To : 351250000000 From : 351211455000 The INVITE is sent to the client with To and From like this and with the Record-Route headers (Kamailio has 2 Ips and inserts 2 Record-Routes) containing vsf and vst parameters to help the future restores : To: <sip:+351250000000@111.111.111.111> From: <sip:+351211455000@111.111.111.111 >;tag=BD583030373631320511EAE6 Record-Route: <sip:111.111.111.111;r2=on;lr;ftag=BD583030373631320511EAE6;tbk_i=2_2_Y;tbk_o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJCnNyAwMcHwIdHQsWHwUMOA--;vst=AAAAABgGBAMHDQgJDQECA3RyAwMcHwIdGgQeHAIFOQ--;did=18e.5d62> Record-Route: <sip:111.111.111.111;r2=on;lr;ftag=BD583030373631320511EAE6;tbk_i=2_2_Y;tbk_o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJCnNyAwMcHwIdHQsWHwUMOA--;vst=AAAAABgGBAMHDQgJDQECA3RyAwMcHwIdGgQeHAIFOQ--;did=18e.5d62> My client, upon receiving the INVITE, also does some changes in the numeration and sends a 183 reply with the following headers : Record-Route: <sip:111.111.111.111;r2=on;lr;ftag=BD583030373631320511EAE6;tbk_i=2_2_Y;tbk_o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJCnNyAwMcHwIdHQsWHwUMOA--;vst=AAAAABgGBAMHDQgJDQECA3RyAwMcHwIdGgQeHAIFOQ--;did=18e.5d62> Record-Route: <sip:111.111.111.111;r2=on;lr;ftag=BD583030373631320511EAE6;tbk_i=2_2_Y;tbk_o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJCnNyAwMcHwIdHQsWHwUMOA--;vst=AAAAABgGBAMHDQgJDQECA3RyAwMcHwIdGgQeHAIFOQ--;did=18e.5d62> From: "+351211455000" <sip:I2116446I_500@111.111.111.111 >;tag=BD583030373631320511EAE6 To: <sip:+351250000000@111.111.111.111>;tag=as3e46f684 After Kamailio processes the reply, To and >From are restored to it's original values and the reply is relayed : From: <sip:351211455000@111.111.111.111 >;tag=BD583030373631320511EAE6 To: <sip:351250000000@111.111.111.111>;tag=as3e46f684 Here, the restore works perfectly. By the end of the call the client sends me a BYE request with Route, From and To like this : Route: <sip:111.111.111.111;r2=on;lr;ftag=BD583030373631320511EAE6;tbk_i=2_2_Y;tbk_o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJCnNyAwMcHwIdHQsWHwUMOA--;vst=AAAAABgGBAMHDQgJDQECA3RyAwMcHwIdGgQeHAIFOQ--;did=18e.5d62>,<sip:212.13.40.205;r2=on;lr;ftag=BD583030373631320511EAE6;tbk_i=2_2_Y;tbk_o=128_11_Y;vsf=AAAAABgGBAMDAAUBBQAJCnNyAwMcHwIdHQsWHwUMOA--;vst=AAAAABgGBAMHDQgJDQECA3RyAwMcHwIdGgQeHAIFOQ--;did=18e.5d62> From: <sip:+351250000000@111.111.111.111 >;tag=as3e46f684 To: "+351211455000" <sip:I2116446I_500@111.111.111.111 >;tag=BD583030373631320511EAE6 Here, the difference between 183 and BYE seems to be only in the Route\Record-Route are built (2 Headers or one header with 2 uri). Now, there are a couple of problems relaying the BYE that seem to me to be related to auto replace. This BYE message isn't logged on the onsend-route and it logs a couple of errors : ERROR: <core> [core/parser/msg_parser.c:164]: get_hdr_field(): bad to header ERROR: <core> [core/parser/msg_parser.c:337]: parse_headers(): bad header field [To: "+351211455000" <sip:Q4525417L_<:C212.13.38.148>;tag=3DC130303736313205201F18#015#012Call-ID: 020FAAC7] ERROR: dialog [dlg_handlers.c:666]: pre_match_parse(): bad request or missing CALLID/TO hdr :-/ ERROR: <core> [core/parser/parse_addr_spec.c:719]: parse_addr_spec(): unexpected char [<] in status 6: ["+351211455000" <sip:Q4525417L_] . Despite not being logged on onsend_route and creating some errors, the BYE is still relayed like this : From: < sip:351250000000@111.111.111.111>;tag=as3e46f684 To: "+351211455000" <sip:Q4525417L_<:C111.111.111.111>;tag=BD583030373631320511EAE6 This, naturally, generates a "400 Bad Request" reply from the next equipment. I've also logged the $tU values along the code for BYE requests and it always logs the "I2116446I_500", so i don't know if my code can be the cause of this. A couple of questions and comments - What can i do to better debug this issue? I want to be sure if the problem comes from my code of if it is a Kamailio issue. Right now i'm not sure where to look. - Can a request be sent without passing on onsend_route ? I have used this code to "catch" the BYE, which works for other BYEs - if( $rm == "BYE") {xerr("On send : To User = $tU");}

3 2

SIP-links adjacency
by Oleg Belousov 07 Oct '19

07 Oct '19

Hello. In our setup kamailio perfoms some logic depending on call direction, inbound or outbound. Call direction is identified by 2 SBC IP (IP_inbound/IP_outbound), we currently use for that 2 dispatcher groups and that is working fine. Now number of peer nodes increased from one SBC till few tens, but we still need to keep SIP-links adjacency, meaning that call which arrived from SBC_N IP_inbound need to be submitted via same SBC_N IP_outbound and vice versa. There could be few approaches to implement that requirement, I'm wondering if can use existing dispatcher function/select destination logic to support SIP-links adjacency. -- obelousov.tel

3 4

q_malloc crash on Kamailio 5.2.3 with http_async_query function
by Michal Škuta 07 Oct '19

07 Oct '19

Hello everyone, I am adding some new features to our Kamailio server, one of them is sending HTTP POST request after calls end. We created simple route like this and we are calling it from event_route[dialog_end]: route[HTTP_TEST_CALL_END] { t_newtran(); $http_req(body) = "TEST"; http_async_query("http://192.168.6.23:2080/cdr_http", "HTTP_TEST_REPLY"); } Problem is that Kamailio is crashing on line *http_async_query*, the log from crash: Oct 3 16:13:37 sip_server /opt/ipgate/kamailio/sbin/kamailio[5331]: CRITICAL: <core> [core/mem/q_malloc.c:149]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail overwritten(c0003032, abcdefed)[0x97a7ff3c:0x97a7ff58]! Memory allocator was called from http_async_client: hm_hash.c:82. Fragment marked by http_async_client: hm_hash.c:71. Exec from core/mem/q_malloc.c:384. In older Kamailio 4.4 I am using http_async_query with no problems. I opened issue on GitHub: https://github.com/kamailio/kamailio/issues/2091 I hope that is ok, more logs and core dump is in the issue. Any help or suggestion is welcomed. Sincerely Michal

2 2

using http_async_query
by David Villasmil 05 Oct '19

05 Oct '19

Hello guys, So, i'm using http_async_query to send out requests. It may happen that the request times out, in this case, i would like to try a new destination, i.e. with ds_select (NOT ds_delect_dest or ds_next, because i don't want the $du to be set, since in my case i don't actually have a SIP packet). Is is possible to get the original http request url in the http_async_query timeout route? Thanks! Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

1 1

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

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 October 2019