sr-users

sr-users@lists.kamailio.org

24 participants
37324 discussions

by Bernd Krueger-Knauber

Hi, I implemented an apple and android push server/proxy with kamailio 5.8.1. The server/proxy is transparent. It works fine with UDP, since the registration after the push comes from the same ip and port. So t_continue works without problems. (We use the new registration as signal thet the phone is ready) If we use tcp at the client, he gets the push, wakes up and send the new registration on an other port. The SIP stack uses now an other connection. t_continue fails, because it uses the old data of the original invite acccording to the first registration. Is it possible to change the stored connection values according to the new registration data? Best regards, Bernd

4 months

low performance with udp_children and async_workers

by elhar.mohamed＠gmail.com

Hello, Based on business requirements, 35% of invites should be handled by async_workers and 65% with be handled by main children. The target is 1500cps. I'm using the following conf : children=64 async_worker=128 when doing performance tests using SIPp, I figured out the 1500cps is well supported by the conf above, but when I updated the data in database to not use anymore async workers, the cps is getting decreased and it was between 200 and 500. This a client requirements is to be able to enable/disable feature that needs to be handled by async workers. Could you please help me on this? Thanks in advance

4 months, 1 week

Inbound call to webRTC failing with TCP/TLS connection (id: 0) for WebSocket could not be found

by hollis.rhonda＠gmail.com

We're seeing an issue where some webRTC clients are not receiving inbound calls. Kamailio logs show the following error: WARNING: {1 609669922 INVITE BW152025538120824-895739618(a)10.103.43.11}: <core> [core/msg_translator.c:3007]: via_builder(): TCP/TLS connection (id: 0) for WebSocket could not be found ERROR: {1 609669922 INVITE BW152025538120824-895739618(a)10.103.43.11}: <core> [core/msg_translator.c:2086]: build_req_buf_from_sip_req(): could not create Via header ERROR: {1 609669922 INVITE BW152025538120824-895739618(a)10.103.43.11}: tm [t_fwd.c:484]: prepare_new_uac(): could not build request ERROR: {1 609669922 INVITE BW152025538120824-895739618(a)10.103.43.11}: tm [t_fwd.c:1764]: t_forward_nonack(): failure to add branches DEBUG: {1 609669922 INVITE BW152025538120824-895739618(a)10.103.43.11}: tm [t_funcs.c:358]: t_relay_to(): t_forward_nonack returned error -2 (-2) DEBUG: {1 609669922 INVITE BW152025538120824-895739618(a)10.103.43.11}: tm [t_funcs.c:376]: t_relay_to(): -2 error reply generation delayed It seems to be happening after the client has been connected to Kamailio for more than 24 hours. The socket connection details look correct in the external DB and in the output of ws.dump, core.tcp_list, and ul.dump. A restart of Kamailio or a reload of the webRTC client, triggering a new websocket connection, will clear the issue. However, we haven't been able to determine exactly when and why a client ends up in this state. While a client is in this state, REGISTER requests are still handled successfully, they can make outbound calls and TCP keepalives from the client are working. I'm still working on trying to debug this with GDB so I can see what the value of send_info is in https://github.com/kamailio/kamailio/blob/master/src/core/msg_translator.c#…, but I wasn't having luck with multiple child processes running, and now my client has reloaded and is working again. I've restarted Kamailio with a single child process, so when it does start failing again, I may have better luck with GDB. Any thoughts on what might be causing clients to get into this state? Whatever additional information I can provide that might help, I'm happy to share. Thanks!

4 months, 1 week

secfilter (and more modules) in kamailio kemi

by bazrafshan.m.h＠protonmail.com

Hi guys, some modules are not shown in Kamailio Kemi's documentation, such as secfilter. Is there any way to load them and use them in Python? a way is to simulate the secfilter but it is not a general solution. (Sorry in advance for the obvious question)

4 months, 1 week

[http_client] KEMI use "curl_connect_post" send http request error

by 17603019528＠163.com

ALL: Hi, here is my lua script: ``` local body = '{"ip":"172.16.4.111", "ports":[5261, 5260]}' local resp = "" local code = KSR.http_client.curl_connect_post("configapi", "", "application/json", body, resp) ``` the error is : ``` 24(2406) DEBUG: app_lua [app_lua_api.c:1024]: sr_kemi_lua_exec_func_ex(): param[0] for: curl_connect_post is str: configapi 24(2406) DEBUG: app_lua [app_lua_api.c:1024]: sr_kemi_lua_exec_func_ex(): param[1] for: curl_connect_post is str: 24(2406) DEBUG: app_lua [app_lua_api.c:1024]: sr_kemi_lua_exec_func_ex(): param[2] for: curl_connect_post is str: application/json 24(2406) DEBUG: app_lua [app_lua_api.c:1024]: sr_kemi_lua_exec_func_ex(): param[3] for: curl_connect_post is str: {"ip":"172.16.4.111", "ports":[5261, 5260]} 24(2406) DEBUG: app_lua [app_lua_api.c:1024]: sr_kemi_lua_exec_func_ex(): param[4] for: curl_connect_post is str: 24(2406) ERROR: <core> [core/pvapi.c:429]: pv_cache_get(): invalid parameters 24(2406) ERROR: http_client [http_client.c:739]: ki_curl_connect_post(): failed to get pv spec for: ``` I know the error means: "resp" type is not right, what is the correct type ? I search google for this issue, no one knows, someone please help me. Thinks

4 months, 1 week

TLS module doesn't support TLSV1

by o.atef＠fiberme.com

Hello Brothers, I've installed kamailio throw "apt install" on Debian and it's installed version: kamailio 5.6.3 (x86_64/linux). Now I've a big problem that kamailio cannot running with TLSv1 and it has to be TLSv1.2+ as tls.cfg doc said: # We do not enable anything else than TLSv1.2+ # over the public internet. Clients do not have # to present client certificates by default. How could I avoid this restriction please to enable TLSv1? Thank you,

4 months, 1 week

[PHONENUM] Match with country on Lua/KSR

by João Silva

Hello everyone! The function phonenum_match_cn from module PHONENUM is not available on KSR. Is there any work around to use it on Lua config? Best regards, Joao

4 months, 1 week

Incoming call with one one way audio and ctting off after thirty seconds

by palany

I have integrated Microsoft teams and freepbx using Kamailio version 5.8 as my SBC. Calls from freepbx to teams are working fine with audio and I am having challenges with calls from teams to freepbx. The calls rings and after answering there is only way audio and the call drops off after thirty seconds. My pbx is behind a microtik router and I have port forwarded my sip port and rtp ports to freepbx and have also disabled sip alg. My Kamailio is hosted in AWS. I have attached both my pcap from Kamailio, freepbx and my Kamailio.cfg. I am thinking It's a misconfiguration challenge or something else. Please help I am failing to see my challenge. Best Regards,

4 months, 1 week

Authentication

by Vishal Pai

Hello All I am using kamailio sip account as gateway at Freeswitch side but when I enable caller id from = true then call from Freeswitch to kamailio didn’t authenticate As I check it’s about from header when I disable caller id from = false the call get authenticate since it get sip username and domain but when there is caller id the from header get callerid@ip address Can anyone guide me Thanks

4 months, 1 week

Kamailio hangs on get_profile_size method.

by satyaprakash ch

HI, We are facing a hang issue with Kamailio for the get_profile_size method. Randomly, the Kamailio got hangs, and the CPU went 100%. During the hanging time, we generated the TRAP and we could see that the hang happened on the get_profile_size method. We are getting this hang randomly in dlg_profile.c of the following lines: The hang occurs, causing the CPU to spike to 100% at one of the following lines randomly: 1. if(value->len == ph->value.len && memcmp(value->s, ph->value.s, value->len) == 0) { 2. ph = ph->next; 3. while(ph != profile->entries[i].first); During our analysis, we found that PROCESS ID 7608 gets a spike of 100% utilization. We suspect there may be an issue with the processing of the 'ph' variable, but we couldn't identify the root cause. I've attached the Kamailio TRAP for further details. Could you please suggest what might be causing this problem and how we can resolve it? Thank you.

4 months, 2 weeks

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