- sr-users - kamailio.org

do MOD_<module name> keywords exist?
by Juha Heinanen 18 Oct '19

18 Oct '19

I have used in config file these kind of constructs: #!ifdef MOD_<module name> ... #!endif Is the MOD_xxx keyword automatically set when module xxx is loaded? Perhaps I have invented the whole concept in a dream? -- Juha

2 4

Failed AKAv1-MD5 authentication with Boghe
by Bao, Yin 18 Oct '19

18 Oct '19

I have a Boghe (v2.0.153.836) working fine with Kamailio with MD5 algorithm however fails to authenticate if I configure S-CSCF to use AKAv1-MD5. We have the same configuration on private user identity in FHoSS on both the succ MD5 run and failed AKAv1-MD5 run. I wonder if anyone has faced this issue before. Here are some details on message exchanges: * S-CSCF included the challenge in 401 Unauthorized – Challenging the UE: WWW-Authenticate: Digest realm="example.example.org", nonce="rzGnTBGPw3hE+mDPHrZ1PAAAAAAApAAAmfftHqYUuUA=", algorithm=AKAv1-MD5, ck="629d6d9a6a6befa509b1a9bb17a9c2a3", ik="32fcd14a102279de2e38200a2257efcb", qop="auth,auth-int"\r\n * The same header was seen when 401 Unauth travelled through I-CSCF and P-CSCF (shouldn’t P-CSCF strips out the ck and ik fields before sending to UE?) * UE responded with another register with response: Authorization: Digest username="bob(a)example.example.org",realm="example.example.org",nonce="rzGnTBGPw3hE+mDPHrZ1PAAAAAAApAAAmfftHqYUuUA=",uri="sip:example.example.org",response="6445f9df2b785eab3fa461849880b48d",algorithm=AKAv1-MD5,cnonce="34baf441e99a23e0fcb2bc001355c4bf",qop=auth-int,nc=00000001\r\n * S-CSCF failed the calculation and sent back 403 Authentication Failed I tried AKAv2-MD5 setting as default algorithm on S-CSCF and the result is the same as above. It seems that only MD5 works on my setup. What are the different configs in HSS (or other places) AKAv1-MD5 need? I checked the AMF/OP on both HSS and Boghe and they match. Boghe does not have SQN setting but I set HSS to start with 0. Any pointers are appreciated! Yin

2 1

IMC through HTTP
by Péter Barabás 18 Oct '19

18 Oct '19

Hi, I want to implement conference messaging functionality into a client. IMC module seems perfect. In our scenario, the rooms and members are managed in a different server bacause of other user management functionalities and the kamailio only uses the rooms to broadcast messages to members. Is it possible anyway to create rooms and join members from a separate server like through http protocol with XHTTP module? The idea is: 1. Create a room on server A with adding members. Server A store the room data. 2. Server A sends http message to kamailio with proper format, like POST .../createRoom with jsonBody { name: „room1” } 3. Kamailio receives the http request and process it with creating a room ’room1’. 4. Server A sends members of room like POST .../addMembers with json body { room: „room1”, members: [ username: „user1”, username: „user2” ] } 5. Kamailio receives the https request and process it with joining memers into room All commands should have the belonging http request. Is it possible? Regards, Peter

2 2

MySQL vs MariaDB support
by Sergey Safarov 18 Oct '19

18 Oct '19

At present time we create RPM packages using MySQL libs. May be need switch to MariaDB libs. What you think about it?

2 1

Need to suppress "200 cancelling" in kamailio
by amit Kumar 18 Oct '19

18 Oct '19

Hi All, As per our requirement, when A party send a cancel to B party we do not want "200 cancelling" message from Kamailio.We try to find any high-level flag to disable it. but could not able to find. Can you please help us on how to achieve this. A Party Kamailio B Party ---------------->INVITE------------------------> <---------180 Ringing<------------------------ ------------>CANCEL--------------------------> <---------200 canceling [we want to suppress this message and do not want kamialio to inform A party about progress status of cancel] <------------OK----------------------------------- Thanks, Amit

2 1

Need to suppress "200 cancelling" in kamailio
by amit Kumar 18 Oct '19

18 Oct '19

Hi All, As per our requirement, when A party send a cancel to B party we do not want "200 cancelling" message from Kamailio. We try to find any high-level flag to disable it. but could not able to find it. Can you please help us on how to achieve this. A Party Kamailio B Party ---------------->INVITE------------------------> <---------180 Ringing<------------------------ ------------>CANCEL--------------------------> <---------200 canceling [we want to suppress this message and do not want kamialio to inform A party about progress status of cancel] <------------OK----------------------------------- Thanks, Amit

1 0

Kamailio v5.3.0 Released - new major version is out
by Daniel-Constantin Mierla 17 Oct '19

17 Oct '19

Kamailio v5.3.0 is out – it comes with 6 new modules and a considerable set of improvements touching more than 100 existing modules. You can read detailed release notes at: * https://www.kamailio.org/w/kamailio-v5-3-0-release-notes/ Many thanks to all developers and community members that made possible this release. v5.3.0 brings more flexibility and optimizations for KEMI interpreters, enhancements to load balancer, dialog tracking, uac remote registration and tls with libssl 1.1.x implementations, new variables, transformations and plenty of other new features. Enjoy Kamailio v5.3.0! Thank you for flying Kamailio! Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 1

Releasing Kamailio v5.3.0
by Daniel-Constantin Mierla 17 Oct '19

17 Oct '19

Hello, if there are no known major issues that need longer time to take care of them, in my opinion we could consider releasing the next major version 5.3.0 next week, for me Thursday, October 10 seems to work the best, still allowing a bit more than one week for testing. Any other suggestions? 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

3 4

catching tls errors
by Juha Heinanen 17 Oct '19

17 Oct '19

Sometimes I see in syslog errors like this: Oct 15 16:44:57 salmon /usr/bin/sip-proxy[2064]: ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:1417C086:SSL routines:tls_process_client_certificate:certificate verify failed Is it possible somehow to catch the error in config file, for example, to figure out from which IP address the connection attempt came from? -- Juha

3 6

Kamailio weighted dispatch problems
by Jasen Hall 17 Oct '19

17 Oct '19

I am trying to change our request dispatching from round-robin to a weight-based method (ds_select_dst() algorithm 9 vs. algorithm 4) and am having a hard time getting an asymmetrical dispatch pattern enabled. In testing, I'm dispatching to two Ringswitch servers and trying to send three times the traffic to one instance. My destinations list file previously set both endpoints in the same group and simply provided the SIP URI for each. My new list file adds the attribute `weight` to each endpoint and looks like this: >1 sip:10.0.0.1:5060 weight=3 >1 sip:10.0.0.2:5060 weight=1 However, when I throw a couple thousand calls at Kamailio, I always end up with an almost perfect split of calls to both ringswitches. Regardless of the weights I choose, I never see variation in the dispatched load. Does anyone have experience with this issue and have some guidance? Thanks in advance. -- Jasen Hall | Invoca *Site Reliability Engineer* www.invoca.com [image: See the list] <https://invoca.sigstr.net/uc/5cba111d3527a200469b9afd>

3 4

IMS Kamailio Diameter Charging Server
by Jack R 14 Oct '19

14 Oct '19

Hi All, We have installed Kamailio as IMS setup pcscf icscf scscf - 3 instances running on Ubuntu.. Referring to the link below, it mentioned about Diameter based Kamailio Charging Server. https://www.kamailio.org/events/2016-KamailioWorld/Day2/15-Carsten.Bock-Dia… Where to find it? How to install it? to make it work in Kamailio IMS set up as per below articles: https://www.kamailio.org/docs/modules/stable/modules/ims_charging.html https://kamailio.org/docs/modules/devel/modules/ims_ocs.html Regards, Jack.

2 2

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

10 Oct '19

Hello, Kamailio SIP Server v5.2.5 stable release is out. This is a maintenance release of the latest stable branch, 5.2, that includes fixes since the release of v5.2.4. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.2.x. Deployments running previous v5.2.x versions are strongly recommended to be upgraded to v5.2.5. For more details about version 5.2.5 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2019/10/kamailio-v5-2-5-released/ RPM, Debian/Ubuntu packages will be available soon as well. Many thanks to all contributing and using Kamailio! 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

3 3

SSL Offloading with AWS ELB or Google GSLB and Kamailio
by Joel Serrano 10 Oct '19

10 Oct '19

Hi everyone, I was giving a try to setup Kamailio with a Cloud TCP load balancer in front, taking advantage of the newly added proxy protocol compatibility and my initial tests went very well. Flow: client -> (tcp) -> load balancer -> (tcp) -> Kamailio TCP socket I then did another quick test and enabled TLS, also with good results: Flow: client -> (tls) -> load balancer -> (tls) -> Kamailio TLS socket So far so good, proxy protocol works as expected. I wanted to go one step further and see if I could somehow offload SSL operations at the load balancer level, and leave kamailio handling plain tcp. Flow: client -> (tls) -> load balancer -> (tcp) -> Kamailio TCP socket This partially worked, and before I start digging into what I have to do to get it completely working, I'd like to know if anyone already has a similar setup, or even if Kamailio is able to handle such a scenario, the reason I'm asking is because of the headers, etc. In this last scenario, I receive in a TCP socket, a request with TLS headers all over the place.. INVITE sip:14a84f2016944eb0854ef0e9b71bfa10@app.mydomain.com:60655 SIP/2.0 Via: SIP/2.0/TLS 192.168.1.16:60717;branch=z9hG4bK.KmUpamn5P;rport From: ... To: ... CSeq: 21 INVITE Call-ID: -j1QSnam9o Max-Forwards: 70 Route: <sip:sbc-test2.mydomain.com:443;lr> <http://sbc-test2.sbx.gii.me:443;lr>/> Supported: replaces, outbound Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, MESSAGE, SUBSCRIBE, INFO, UPDATE Content-Type: application/sdp Content-Length: 436 Contact: <sip:linphone@A.B.C.D:60717;transport=tls>;+sip.instance="<urn:uuid:fabcb441-a348-49a7-948d-72448d6840eb>" I then forward this request via UDP to subsequent proxies for further processing, on the replies, my payload information back to the client should be TLS, although sent via a TCP socket.. Is this something that will not work by design? Is there any hack I can take advantage of? The goal would be for Kamailio to handle TLS headers via TCP socket, as the client expects TLS information, but the actual traffic should go in plan TCP, and the load balancer will take care of re-encrypting before replying to the client. Any ideas/suggestions/comments? I hope this email is understandable, I find it complicated to detail the exact problem, feel free to ask any questions if you don't understand anything. Thanks, Joel.

3 5

PUBLISH ERROR
by Social Boh 10 Oct '19

10 Oct '19

Hello, Kamailio 5.2.5. I'm testing presence on my Kamailio using different Clients (Jitsi, Bria5, Linphone). when they send the PUBLISH to Kamailio, all receive the same answer: 400 Invalid Request On the LOG file: ERROR: {1 21 PUBLISH O8-BtqLnzw} presence [publish.c:421]: ki_handle_publish_uri(): No E-Tag and no body found I'm pretty sure same configuration work with 5.2.3 version. Any hint? Regards -- --- I'm SoCIaL, MayBe

2 4

centos7 rpm for evapi
by Aidar Kamalov 10 Oct '19

10 Oct '19

Hello, how can I install evapi for kamailio using rpm repo? # ls /usr/lib64/kamailio/modules | grep evapi | wc -l 0 # yum provides *evapi.so Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile * base: mirror.docker.ru * extras: mirror.linux-ia64.org * updates: mirror.corbina.net No matches found -- Aydar A. Kamalov

2 1

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

storing vars in htable
by David Villasmil 05 Oct '19

05 Oct '19

Hello guys, I'm storing some data in an htable, like so: $var(http_query) = "/default/en_US/send.html?u=user&p=pass&l=$var(next_channel)&n=$var(to)&m=$var(message)"; then i need to store it: $sht(http_requests=>$http_req_id) = $var(http_query); But what's stored is the actual vars, not the the values, it's stored like: sh store: /default/en_US/send.html?u=user&p=pass&l=$var(next_channel)&n=$var(to)&m=$var(message) Why is that? shouldn't the vars be parsed? Thanks Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 2

Re: [SR-Users] Call limit through shared database
by Olli Attila 04 Oct '19

04 Oct '19

Hello Henning, I tried the dialog profile sharing with dmq&dialog modules and now the syncing works between the two kam nodes. Thank you! Is there a way to keep the dialog profiles persistent (load from db if kam restarts)? I was thinking a scenario where kam1 has already the call limit maxed out and kam2 suddenly reboots and after reboot, kam2 should be aware of dialogs on kam1 to be able to limit calls again correctly. Cheers, Olli

3 3

Re: [SR-Users] Call limit through shared database
by Olli Attila 04 Oct '19

04 Oct '19

Hello, I had the following enabled in db_mode param and now it is actually working: *1 - REALTIME* - any dialog information changes will be reflected into the database immediately. Restarting either of the kam1 or kam2 proxies "on the fly" will result in retrieving dialog profiles correctly from database. Cheers, Olli

1 0

Record-Route management
by Duarte Rocha 03 Oct '19

03 Oct '19

Greetings, I have multiple IPs in my Kamailio. In some scenarios, the caller and the called connect to different IPs and in others, they use the same IP. Currently i'm running with the RR's module "enable_double_rr" parameter set so i can have one Record-Route for each IP used on the call. However, in the scenario that both caller and called have the same IP, i would like to only have on Record-Route in order to save on the pactet's size. Is this possible to have those two scenarios on the same Kamailio ? Best Regards

2 2

string manipulation
by David Villasmil 03 Oct '19

03 Oct '19

Hello guys, I'm receiving an http request via xhttp, something like: http://ip.com/request?value1=123&value2=2313&value3... Is it possible to get those values somehow? I also have a suri coming from a ds_select in _dsdst_, I need to get the host from that _dsdst_ Any way of doing this? Thanks all Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 2

Get destination out of _dsdst_
by David Villasmil 03 Oct '19

03 Oct '19

Hello guys, I've never used "ds_select" as opposed to "ds_select_dst", and i would like to get the actual destination out of _dsdst_ I've got modparam("dispatcher", "xavp_dst", "_dsdst_") and then i'm trying to do: if(!ds_select("100", "4")) { send_reply("404", "No destination"); exit; }else{ xlog("L_ERR", "[XHTTP]: The next destination for SMS is: [$xavp(_dsdst_)]\n"); ds_mark_dst("d"); } But that's coming up with The next destination for SMS is: [<<xavp:0x7fbe87acdbf0>>] I need to get the actual ip address out of the struct. Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 2

Development is open for future release of v5.4.x series
by Daniel-Constantin Mierla 03 Oct '19

03 Oct '19

Hello, the branch 5.3 was created late last evening, therefore the master branch is open for adding new features, to be part of future release series v5.4.x. Any bug fix committed to master that applies to 5.3.x or older stable branches should be backported as usual with "git cherry-pick -x ..." to appropriate branches like 5.3 or 5.2. Expect that v5.3.0 will be released in a few weeks from now. Based on the workflow used during the past years, the next future release v5.4.0 should be out after another 8-10 months of development, plus 1-2 months of testing, so sometime in close to the end of spring 2020 or afterwards. 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 0

Branch 5.3 has been created
by Daniel-Constantin Mierla 03 Oct '19

03 Oct '19

Hello, the branch 5.3 has been created, to be used for releasing v5.3.x series. To check out this branch, the following commands can be used: git clone https://github.com/kamailio/kamailio kamailio-5.3 cd kamailio-5.3 git checkout -b 5.3 origin/5.3 Pushing commits in this branch: git push origin 5.3:5.3 Note that 5.3 is an official stable branch, so only bug fixes, missing kemi exports (discuss on sr-dev if not sure) or improvements to documentation or helper tools can be pushed to this branch. You may notice a bit of more activity on tls (some issue is under work) and siptrace (a bit of cleanup for coherence might be done) modules, but over all no new features will be pushed there. As usual, if there is a bug fixed, commit and push first to master branch and then cherry pick to 5.2 branch: git cherry-pick -x COMMITID In few weeks, the first release from branch 5.3 will be out, respectively Kamailio v5.3.0. 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 0

Branching 5.3
by Daniel-Constantin Mierla 02 Oct '19

02 Oct '19

Hello, if there are no strong opinions against, then it is time to branch 5.3 on git repository. I am considering to do it by the end of the day on Wednesday, October 2, 2019. After that, the master will be again open for new features, while 5.3 branch will continue to get the only fixes and improvements to documentation and tools. 2-3 weeks later we should release v5.3.0, the first stable version in 5.3.x series. 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

Unresolvable destination for new added users...
by Zhan Bazarov 02 Oct '19

02 Oct '19

I can't make call through kamailio between new added users. I get 478 ... But it works for older users (who was added couple weeks ago e.g.) SIP flow, location and subscriber table the same in both cases. Could you please shed any light on this issue? *2019/10/02 11:11:20.719834 10.2.1.198:5068 <http://10.2.1.198:5068> -> 10.4.1.14:50600 <http://10.4.1.14:50600>* SIP/2.0 *478* Unresolvable destination (478/SL) Via: SIP/2.0/UDP asterisk_ip:asterisk_port;branch=z9hG4bK18626d14;rport=50600;received=10.4.1.14 From: "Admin Admin" <sip:some_user@asterisk_ip:asterisk_port>;tag=as09b1f1f3 To: <sip:some_user@kamailio_ip :kamailio_port>;tag=a1384aaeda4d71b5edb13882669b943e.8468 Call-ID: *20e023254f1b3c942a61e47d63badfd6@10.4.1.14:50600 <http://20e023254f1b3c942a61e47d63badfd6@10.4.1.14:50600>* CSeq: 102 INVITE Server: MS Lync Content-Length: 0

3 5

BLF 'NOTIFY' not working
by Petarr Jones 02 Oct '19

02 Oct '19

Hi I am using Kamailio 5.2 with the following PRESENCE modules and parameters: loadmodule "presence.so" loadmodule "presence_xml.so" loadmodule "presence_dialoginfo.so" loadmodule "presence_reginfo.so" modparam("presence", "db_url", DBURL) modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "force_active", 1) modparam("presence_xml", "disable_bla", 0) modparam("presence_xml", "integrated_xcap_server", 1) I have a Yealink T28P phone which has two lines/extensions successfully registered with Kamailio 5.2. When I setup the BLF light to monitor one of the extensions, I get the correct SUBSCRIBE record but the NOTIFY record is sent over and over again until it fails. ----------------------------------------------------------------------------------------------------------- NOTIFY sip:101@192.168.1.123:5062 SIP/2.0 Via: SIP/2.0/UDP 45.45.45.45;branch=z9hG4bKd16c.03b5bc97000000000000000000000000.0 To: <sip:101@45.45.45.45>;tag=1366853594 From: <sip:104@45.45.45.45>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-e6c3 CSeq: 2 NOTIFY Call-ID: 594386350(a)192.168.1.123 Content-Length: 0 User-Agent: kamailio (5.2.4 (x86_64/linux)) Max-Forwards: 70 Event: dialog Contact: <sip:45.45.45.45:5060;transport=udp> ----------------------------------------------------------------------------------------------------------- When I register the phone with Freeswitch instead and run the same test, the NOTIFY works and I get a much longer NOTIFY message ----------------------------------------------------------------------------------------------------------- NOTIFY sip:100@192.168.1.123:5064 SIP/2.0 Via: SIP/2.0/UDP 66.66.66.66;rport;branch=z9hG4bK1mXej9r2605UB Route: <sip:55.55.55.55:5064>;transport=udp Max-Forwards: 70 From: <sip:102@66.66.66.66>;tag=xUoVghM5syHc To: "100" <sip:100@66.66.66.66>;tag=1720892352 Call-ID: 2583553127(a)192.168.1.123 CSeq: 1178415701 NOTIFY Contact: <sip:102@66.66.66.66:5060> User-Agent: FreeSWITCH-mod_sofia/1.10.1-release-12-f9990221e6~64bit Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE Supported: timer, path, replaces Event: dialog Allow-Events: talk, hold, conference, presence, as-feature-event, dialog, line-seize, call-info, sla, include-session-description, presence.winfo, message-summary, refer Subscription-State: active;expires=1800 Content-Type: application/dialog-info+xml Content-Length: 149 xml version="1.0"?> dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="0" state="full" entity="sip:102@66.66.66.66"> dialog-info> ----------------------------------------------------------------------------------------------------------- Should the message coming from Kamailio contain more data or is that not the issue. Should I be including other modules also? All guidance would be appreciated.

2 4

Call limit through shared database
by Olli Attila 01 Oct '19

01 Oct '19

Hello, I have 2 kam instances using one shared database and both kam servers running the same routing logic code. Kamailio servers are configured to use the same database as dialog backend. I am limiting the concurrent dialogs in the following way but it seems that kamailio is using its own memory to read profile size rather than the db. Second kam is not aware of the dialog profiles that the first kam wrote to the shared db. Is there a way to get multiple kam instances to read profile size from the same database when calling the get_profile_size function? modparam("dialog", "profiles_with_value", "concurrent_calls") modparam("dialog", "dlg_flag", 4) modparam("dialog", "db_url", DBURL) modparam("dialog", "db_mode", 1) route[LIMIT_CALLS] { if (!dlg_isflagset("1")) { # $td – gateways, $fu - user if (get_profile_size("concurrent_calls", "$fu", "$avp(calls)")) { if ($avp(calls) >= 3) { xlog("L_INFO", "Concurrent calls $fu at limit"); send_reply("503", "Calls limit reached"); exit; } else { dlg_manage(); dlg_setflag("1"); set_dlg_profile("concurrent_calls", "$fu"); } } } } Cheers, Olli

5 8

Kamailio Charging
by Jack R 01 Oct '19

01 Oct '19

Hi, Does Kamailio provide some charging functionality? If yes, then how do we go about setting it up? like what module/configuration? and Database tables to see/touch? I see these links: https://www.kamailio.org/docs/modules/4.2.x/modules/ims_charging.html https://www.kamailio.org/w/2013/07/documentation-on-charging-in-ims/ Or Do we need separate software like example cgrates for charging? (also a side question do we have any other open-source like cgrates) Any information would be helpful. Thanks and Regards, Jack.

3 3

Relay Request
by Maryam Baghdadi 29 Sep '19

29 Sep '19

Hello everyone, Is it possible to relay INVITE request to another server after receiving "180 Ringing" response ??? I would like to activate CRBT(ring back tone) service and according to my research after receiving 180 ringing media playing request should be sent to a media server .

3 2

Re: [SR-Users] Relay Request
by Mojtaba 29 Sep '19

29 Sep '19

Would you please keep "Users Mailing List" <sr-users(a)lists.kamailio.org> in tracking. :) That is straight froward. There is no change in sending the request from Kamailio to Asterisk. In Asterisk you could use Progress command to support Media-Relay. In additional use Dial command (with r or m option for supporting CRBT ). With Best Regards On Sun, Sep 29, 2019 at 8:52 AM Maryam Baghdadi <maryam.baghdadi(a)gmail.com> wrote: > Hello Mojtaba, > I chose asterisk as media server and some services like voice mail > provided ... about CRBT I know asterisk have this service but I don't know > how to send this request from kamailio to asterisk.. > do you know kamailio can provide this service itself or not??? > could you pls explain more > > thanks > > > On Sat, Sep 28, 2019, 1:48 PM Mojtaba <mespio(a)gmail.com wrote: > >> Hello, Some consideration would be needed: >> 1) SS7 for PSTN subscriber to support media-relay >> 2)Progress capability for SIP subscriber. >> 3) Media server to support ring-back VAS service >> You should check enabling this service or not during MO procedure. >> With Best Regards. >> >> On Sat, Sep 28, 2019 at 1:19 PM Maryam Baghdadi < >> maryam.baghdadi(a)gmail.com> wrote: >> >>> Hello everyone, >>> >>> Is it possible to relay INVITE request to another server after receiving >>> "180 Ringing" response ??? >>> I would like to activate CRBT(ring back tone) service and according to >>> my research after receiving 180 ringing media playing request should be >>> sent to a media server . >>> _______________________________________________ >>> Kamailio (SER) - Users Mailing List >>> sr-users(a)lists.kamailio.org >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >>> >> >> >> -- >> --Mojtaba Esfandiari.S >> > -- --Mojtaba Esfandiari.S

1 0

tcp_accept_haproxy questions
by Grant Bagdasarian 27 Sep '19

27 Sep '19

Hello, The docs mention regular TCP connections not being accepted anymore once this is enabled. I assume UDP is unaffected and both proxyprotocol and udp may live side by side? Also, does this play nicely with WebSockets? Taking into account the Websocket connection being setup through a proxy protocol supporting proxy. Regards, Grant

1 0

wiki on $sht(htable=>key)
by Juha Heinanen 27 Sep '19

27 Sep '19

Kamailio wiki does not tell what result $sht(htable=>key) gives if the key is not found in htable. It would be nice if it did. -- Juha

1 0

KEMI dialplan dp_replace returns not implemented yet
by Grant Bagdasarian 26 Sep '19

26 Sep '19

Hello, The dp_replace KEMI function is returning the message "not implemented yet". Function call: _.dialplan.dp_replace(1, _.pv.get("$rU"), "$var(dpr)") app_python3 ¡apy_kemi.c:872¿: sr_apy_kemi_f_pv_get_mode(): pv get: $rU <core> ¡core/pvapi.c:398¿: pv_cache_lookup(): pvar ¡$rU¿ found in cache app_python3 ¡apy_kemi.c:193¿: sr_apy_kemi_exec_func_ex(): execution of method: dp_replace app_python3 ¡apy_kemi.c:338¿: sr_apy_kemi_exec_func_ex(): not implemented yet app_python3 ¡apy_kemi.c:872¿: sr_apy_kemi_f_pv_get_mode(): pv get: $var(dpr) <core> ¡core/pvapi.c:371¿: pv_cache_add(): pvar ¡$var(dpr)¿ added in cache Using Kamailio 5.2.4 Docker image. version: kamailio 5.2.4 (x86_64/linux) flags: STATS: Off, USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, Q_MALLOC, F_MALLOC, TLSF_MALLOC, DBG_SR_MEMORY, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144 MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB poll method support: poll, epoll_lt, epoll_et, sigio_rt, select. id: unknown compiled with gcc 6.3.0 Regards, Grant

2 4

Kamailio Rasberry Pi benchmark results
by Henning Westerholt 26 Sep '19

26 Sep '19

Hello, as promised here the report on my Rasberry Pi benchmarks. The numbers were quite impressive! - 3000 registration requests per second (in-memory usrloc) - 300 calls per second for a p2p call (default cfg, only SIP traffic) - about 18 MBit/s incoming and 16 MBit/s outgoing SIP peak traffic could be processed All the details about the test setup and more numbers in the blog post: https://skalatan.de/blog/kamailio-rpi-benchmark Cheers, Henning -- Kamailio Merchandising - https://skalatan.de/merchandising/ Kamailio services - https://skalatan.de/services Henning Westerholt - https://skalatan.de/blog/

1 0

Kamailio v5.1.9 Released
by Daniel-Constantin Mierla 26 Sep '19

26 Sep '19

Hello, Kamailio SIP Server v5.1.9 stable release is out. This is a maintenance release of the previous stable branch, 5.1, that includes fixes since the release of v5.1.8. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.1.x. Deployments running previous v5.1.x versions are strongly recommended to be upgraded to v5.1.9 or to v5.2.x series. For more details about version 5.1.9 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2019/09/kamailio-v5-1-9-released/ RPM, Debian/Ubuntu packages will be available soon as well. Note: the branch 5.1 is the previous stable branch. The latest stable branch is 5.2, at this time with v5.2.4 being released out of it. Many thanks to all contributing and using Kamailio! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio World Conference - April 27-29, 2020 -- www.kamailioworld.com

2 1

ims_ipsec_pcscf: maybe core dump due to maximum count of connections
by Valentin Christoph 26 Sep '19

26 Sep '19

Hi, Doing some tests with the module ims_ipsec_pcscf, we encountered a core dump during startup of Kamailio and would like to understand the correct behavior. We assume the ipsec_max_connections parameter was the root cause --> how many max connections have been actually tested? Can it be that ipsec_client-port and ipsec_server_port were too close together (some overlapping)? Thx Christoph

2 1

install with kazoo
by Benoit Chesneau 26 Sep '19

26 Sep '19

Hi all, Can anyone share a simple configuration to use with kazoo or a link to it? I'm struggle in having it setup without using the defaults packages. Ideally it should dispatch messages to freeswitch. Any help is welcome :) Benoît

3 2

Planning the release of v5.1.9
by Daniel-Constantin Mierla 26 Sep '19

26 Sep '19

Hello, I am considering to release v5.1.9 out of the branch 5.1 during the next week, on Tuesday (Sep 24) or Thursday (Sep 26). As usual, if you are aware of issues not reported on tracker or commits that should be backported to branch 5.1, do report them asap in order to get them a chance to be sorted out. 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 2

Kamailio ARM support improved, tests
by Henning Westerholt 25 Sep '19

25 Sep '19

Hello, as part of the testing for 5.3.0 I looked into the ARM support in Kamailio. Previously the core used some deprecated assembler functions for atomic operations (locking etc..). There was also no native support for the ARM v7 architecture available. After several fixes and extensions both topics should be now much improved. I did today a lot of tests on Rasberry Pi and also some benchmarking (will send another e-mail when the report is ready). If you use Kamailio on another embedded ARM (>= v6) system it would be great if you also give it a try. Use git master revision ccc0eb6d12a1d (or newer) for your tests. Please report eventual issues to the sr-dev list. Cheers, Henning -- Kamailio Merchandising - https://skalatan.de/merchandising/ Kamailio services - https://skalatan.de/services Henning Westerholt - https://skalatan.de/blog/

1 0

Development for v5.3.x is frozen
by Daniel-Constantin Mierla 25 Sep '19

25 Sep '19

Hello, the formal notification that the development for the next major version 5.3.0 is now frozen. The focus has to be on testing the master branch. Also, the master branch should not get commits with new features till the branch 5.3 is created, expected to happen in 2-4 weeks, a matter of how testing goes on. Meanwhile, the commits with new features in the C code can be pushed to personal branches, pull requests can still be done, but they will be merged after branching 5.3. Can still be done commits with documentation improvements, enhancements to related tool (e.g., kamctl, kamcmd) and exporting missing KEMI functions to the modules already exporting most of the other functions (done for previous releases, because likely that was a fail to notice, all functions should be exported for a module at the same time). Once the branch 5.3 is created, new features can be pushed again to master branch as usual. From that moment, the v5.3.0 should be out very soon, time used for further testing but also preparing the release of packages. If someone is not sure if a commit brings a new feature, just make a pull request and it can be discussed there on github portal or via sr-dev mailing list. A summary of what is new in upcoming 5.3 is collected at: * https://www.kamailio.org/wiki/features/new-in-5.3.x Upgrade guidelines will be collected at: * https://www.kamailio.org/wiki/install/upgrade/5.1.x-to-5.3.0 Everyone is more than welcome to contribute to the above wiki pages, especially to the upgrade guidelines, to help everyone else during the migration process from v5.2.x to 5.3.x. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

3 8

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