sr-users

sr-users@lists.kamailio.org

4 participants
37456 discussions

make Debian deb package + non kstandard modules
by Victor Velo 16 Apr '24

16 Apr '24

Hello, I would like to build some additional modules to the standard by following this guide (old) https://www.kamailio.org/wikidocs/install/4.0.x/debian/ and I don't get these additional .deb packages. Could someone please help. Thanks, Victor

1 0

Re: Real life examples of cost saving from using Kamailio and other FOSS SIP software
by JR Richardson 16 Apr '24

16 Apr '24

Hey Folks, What a great conversation, really enjoyed all the insight and feedback, other than what's already been said, which I agree with whole heartedly, I want to add some personal reflection. FOSS is exceptional for putting tools in your hands to build what your business can use to succeed. You will spend upfront $$ investment with man-hours learning, deploying, managing then cost trails off to realize the return on investment which is usually exponential compared to commercial drop-in voice switches. A key consideration is expected/targeted growth of the solution and operational expediency, how big with the subscriber base get, voice service is a high touch point for customer support. Once you (as in personally) deploy a FOSS solution in production, you are tied to that solution for its foreseeable existence, good luck finding competent and like-minded staff that see your vision and can support the solution as you do. Deployment guys will always have a deeper understanding/knowledge of the solution, architecture, configuration, pitfalls and work around than the operations support folks. If you don't have staff resources, having consultants you can rely on is crucial for success. I can't say enough about Kamailio for building call routing solutions, mature, stable, reliable, continued improvements, phenomenal developer and community base for support. Good luck whichever direction you go in! JR Richardson On Apr 14, 2024, at 12:25 PM, Alex Balashov <abalashov(a)evaristesys.com> wrote: > Medium to large organisations, in particular, tend to extract labour from consistent (if unextraordinary) output of everyday do-gooders, and not the more stochastic and volatile heroics of open-source superstars. Sorry, I meant to say "extract value" here, not "extract labour". But the larger point is that any successful formula heavily reliant on open-source is going to be a lot more dependent on culture, and on the strengths of individual people and their specific skills, than a formula reliant on a third-party vendor, all other things being equal. -- Alex -- Alex Balashov Principal Consultant Evariste Systems LLC Web: https://evaristesys.com Tel: +1-706-510-6800 End of sr-users Digest, Vol 227, Issue 36 *****************************************

1 0

Issue with MS Teams OPTIONS ping - no response
by Barry Flanagan 16 Apr '24

16 Apr '24

Hi Using Kamailio 5.6 and trying to get Teams integration working. Failing at the first step! I receive no reply from MS to my OPTIONS ping. AFAIK it is correect, here is the OPTIONs sent: OPTIONS sip:sip.pstnhub.microsoft.com;transport=tls SIP/2.0 Via: SIP/2.0/TLS msteams.domain.com:5061;branch=z9hG4bK0c2b.da69f3c3000000000000000000000000.0 To: <sip:sip.pstnhub.microsoft.com;transport=tls> From: <sip:msteams.domain.com>;tag=6d9effc2a8ec7e0b16377e93bd9e71e2-470e3c71 CSeq: 10 OPTIONS Call-ID: 6ea8091201db565b-605531(a)159.65.196.10 Max-Forwards: 70 Content-Length: 0 User-Agent: ABC SBC Contact: <sip:msteams.domain.com:5061;transport=tls> From the logs (below) I can see that w are accepting the MS cert OK but get no response and ends with a 408. The domain is configured in Teams, and a user with a license was added. MY Cert is issued by GeoTrust TLS RSA CA G1. Any idea if the issue might be on my side? 024-04-15T14:53:19.302610+00:00 msteams /usr/sbin/kamailio[605600]: DEBUG: tls [tls_domain.c:798]: sr_ssl_ctx_info_callback(): SSL handshake done 2024-04-15T14:53:19.302692+00:00 msteams /usr/sbin/kamailio[605600]: DEBUG: tls [tls_server.c:542]: tls_connect(): TLS connect successful 2024-04-15T14:53:19.302762+00:00 msteams /usr/sbin/kamailio[605600]: DEBUG: tls [tls_server.c:545]: tls_connect(): tls_connect: new connection to 52.114.14.70:5061 using TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384 256 2024-04-15T14:53:19.302824+00:00 msteams /usr/sbin/kamailio[605600]: DEBUG: tls [tls_server.c:550]: tls_connect(): tls_connect: sending socket: 159.65.196.10:0 2024-04-15T14:53:19.302868+00:00 msteams /usr/sbin/kamailio[605600]: DEBUG: tls [tls_server.c:418]: tls_dump_cert_info(): tls_connect: server certificate subject:/C=US/ST=WA/L=Redmond/O=Microsoft Corporation/CN=sip.pstnhub.microsoft.com 2024-04-15T14:53:19.302917+00:00 msteams /usr/sbin/kamailio[605600]: DEBUG: tls [tls_server.c:422]: tls_dump_cert_info(): tls_connect: server certificate issuer:/C=US/O=Microsoft Corporation/CN=Microsoft Azure RSA TLS Issuing CA 03 2024-04-15T14:53:19.470476+00:00 msteams /usr/sbin/kamailio[605606]: DEBUG: tls [tls_server.c:729]: tls_h_tcpconn_close_f(): Closing SSL connection 0x7fd3c77639c8 2024-04-15T14:53:28.770710+00:00 msteams /usr/sbin/kamailio[605591]: DEBUG: dispatcher [dispatch.c:3617]: ds_options_callback(): OPTIONS-Request was finished with code 408 (to sip:sip.pstnhub.microsoft.com;transport=tls, group 1) -Barry

3 3

Memory leaks - KEMI Lua
by Muhammad Danish Moosa 16 Apr '24

16 Apr '24

Hi, I am using kamailio with KEMI Lua. The script has some medium level complexity as it stores some information from the invite in redis cache during the call and uses that information during the call transfers (REFER and Invite triggered by REFER). Lua script itself creates/sets some variables, and sends/retrieves information during the flow for example KSR.ndb_redis.redis_cmd("srvN", "SET coreCI-" .. varCI .. " " .. KSR.pv.getw("$ci") .. " EX 3600", "r"); KSR.ndb_redis.redis_cmd("srvN", "GET refvar-" .. cid, "r"); reft=KSR.pv.getw("$redis(r=>value)"); I made a test call and disconnected, what I am observing is that even if the call is finished the used memory is slightly increased. before: < real_used: 844240 < real_used: 844088 < real_used: 844088 < real_used: 844088 < real_used: 844088 < real_used: 844088 < real_used: 844088 < real_used: 844088 after: > real_used: 846080 > real_used: 845864 > real_used: 846584 > real_used: 846304 > real_used: 846200 > real_used: 846120 > real_used: 845248 > real_used: 846168 My assumption is after finishing the call, memory used by variables and redis ops is released and should be back to original values but its not happening. In production this issue is causing some problems as I have to restart the kamailio process after every 3-4 weeks so that it starts breathing with more available memory. Initially I thought its Kamailio version issue as in my last posts in this forum people advised me to upgrade to the latest kamailio version (original one was 5.4.0) but the same issue is happening on 5.7.0. Can someone explain how to debug/troubleshoot this situation . I have a parallel lab environment, I do not see anything interesting in syslogs. -- Muhammad Danish Moosa " The core of mans' spirit comes from new experiences. "___ Christopher McCandless

3 4

About the operating environment of Kamailio
by 山本哲也 15 Apr '24

15 Apr '24

Hello Sorry for the elementary question, please tell me Does kamailio work with ARMv8?

5 5

Maintenance work overnight on kamailio.org server
by Daniel-Constantin Mierla 15 Apr '24

15 Apr '24

Hello, there is some planned work on the data center infrastructure hosting kamailio.org server that is going to affect briefly the web server (web site, wiki) and the mailing lists. The downtime is expected to be 10-15 minutes around 1:00am Western Europe time (CEST / GMT+2), but if it takes longer or repeats, be patient for a while. Cheers, Daniel -- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy, Training and Development Services -- asipto.com Kamailio World Conference, April 18-19, 2024, Berlin -- kamailioworld.com

1 0

Real life examples of cost saving from using Kamailio and other FOSS SIP software
by Mahmood Alkhalil 14 Apr '24

14 Apr '24

Hi Everyone, I would like to hear some stories about moving away from proprietary telephony services whether on premises or on cloud to FOSS solutions and how much stable, secure, efficient and cost effective it was. I would like to present to my managers such cases to convince them to move away from proprietary telephony as it is just huge amount of cost and technical debt. Thanks everyone and really appreciate any insights, also I am sorry if this is not the place to ask for such!

4 13

show final SIP INVITE before going out
by marek 11 Apr '24

11 Apr '24

hi, i have kamailio with TLS i dont have homer and voipmonitor with TLS decryption doesnt work how can i check final SIP INVITE (after all rewrites/modifications) before is send to the peer? tried onsend_route { if ($rm == "INVITE") { xlog("L_INFO", "Final SIP Message before Sending: $mbu\n"); } } but record-route/via are different than reality (checked with sngrep with TLS disabled) kamailio log Record-Route: <sip:;r2=on;lr;ftag=b0d1d4ce-... Record-Route: <sip:10.10.10.10;r2=on;lr;ftag=b0d1d4.. Via: SIP/2.0/UDP 30.30.30.30:5080;TH=div;rport;branch=z9hG4bK sngrep Record-Route: <sip:9.9.9.9;r2=on;lr;ftag=246bdf1c... Record-Route: <sip:9.9.9.9;line=sr-Jf7BrWSBdWSzrD Via: SIP/2.0/UDP 9.9.9.9;branch=z9hG4bKdb73.0735168f3e5f.... Via: SIP/2.0/UDP 9.9.9.9;branch=z9hG4bKsr-2y7Ud3XCMD4N6Vi8M-iCM-XGdWSBMDGzuhJZu-iGMh9ztEu7q..... 10.10.10.10 - private kamailio ip (fictional) 30.30.30.30 - ip of SIP PBX (caller) 9.9.9.9 - public kamailio ip Marek

2 1

Unable to remove/modify/replace "Contact SIP header'
by ramaseshi.kolli＠gmail.com 11 Apr '24

11 Apr '24

Hi All, My requirement is when incoming call comes from internal user in i want to put kamailio ip and port in Contact header and forward or dispatch request to sip trunk carrier but i am unable to do so using KEMI frame work LUA. Can someone please give some pointer please? KSR.textops.remove_hf("Contact"); KSR.textopsx.assign_hf_value("Contact","<sip:1234@4.5.6.7>"); KSR.rtpengine.rtpengine_manage0(); if KSR.tm.t_relay()<0 then KSR.sl.sl_reply_error(); end

3 5

503(service unavailable)
by masoud96＠mail.ru 11 Apr '24

11 Apr '24

Great everyone! It often happens to me that the service completely fails and refuses to service calls. For example, yesterday there was such a situation. I looked at the logs and at the beginning of the incident I noticed this strange entry: kamailio[283008]: WARNING: {1 14714 ACK clMGFB7OWsiT4fQp9TPvV-RlvGqv2zPa} <core> [core/tcp_main.c:1297]: find_listening_sock_info(): binding to source address 109.68.232.40:15061 failed: Address already in use [98] kamailio[283008]: WARNING: {1 14714 ACK clMGFB7OWsiT4fQp9TPvV-RlvGqv2zPa} <core> [core/tcp_main.c:1441]: tcp_do_connect(): 10.241.60.46:15061: could not find corresponding listening socket kamailio[283008]: ERROR: {1 14714 ACK clMGFB7OWsiT4fQp9TPvV-RlvGqv2zPa} <core> [core/tcp_main.c:3078]: tcpconn_1st_send(): connect 10.241.60.46:15061 failed (RST) Connection refused kamailio[283008]: ERROR: {1 14714 ACK clMGFB7OWsiT4fQp9TPvV-RlvGqv2zPa} <core> [core/tcp_main.c:3087]: tcpconn_1st_send(): 10.241.60.46:15061: connect & send for 0x7f7107e01750 (sock 39) kamailio[283008]: CRITICAL: {1 14714 ACK clMGFB7OWsiT4fQp9TPvV-RlvGqv2zPa} <core> [core/forward.h:290]: msg_send_buffer(): tcp_send failed kamailio[283008]: ERROR: {1 14714 ACK clMGFB7OWsiT4fQp9TPvV-RlvGqv2zPa} sl [sl_funcs.c:415]: sl_reply_error(): stateless error reply used: Unfortunately error on sending to next hop occurred (477/SL) And after several such entries this begins: /usr/local/sbin/kamailio[283069]: ERROR: <core> [core/tcp_main.c:4787]: tcpconn_main_timeout(): connect 31.173.85.36:10588 failed (timeout) /usr/local/sbin/kamailio[283069]: ERROR: <core> [core/tcp_main.c:4787]: tcpconn_main_timeout(): connect 95.24.163.132:48075 failed (timeout) /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668011 (state: 0) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668304 (state: 0) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668309 (state: 0) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668316 (state: 0) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668192 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668228 (state: 0) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668236 (state: 0) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668427 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668428 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668429 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668430 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668431 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668432 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668433 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668434 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668435 (state: 3) - closing /usr/local/sbin/kamailio[282828]: CRITICAL: <core> [core/tcp_main.c:5526]: tcp_timer_check_connections(): message processing timeout on connection id: 22668436 (state: 3) - closing Such recordings go on for a very long time (5 minutes) and begin like this: /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 20, socket 273: queue full, 286 requests queued (total handled 2421746) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 29, socket 291: queue full, 286 requests queued (total handled 2419460) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 4, socket 241: queue full, 287 requests queued (total handled 2451838) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 5, socket 243: queue full, 287 requests queued (total handled 2445182) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 18, socket 269: queue full, 287 requests queued (total handled 2422113) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 20, socket 273: queue full, 287 requests queued (total handled 2421747) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 27, socket 287: queue full, 287 requests queued (total handled 2419986) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 29, socket 291: queue full, 287 requests queued (total handled 2419461) /usr/local/sbin/kamailio[283069]: CRITICAL: <core> [core/tcp_main.c:4361]: send2child(): tcp child 30, socket 293: queue full, 287 requests queued (total handled 2419979) Also, my eyes are distracted by such records and it’s difficult to understand the logs: 1) kamailio[282798]: CRITICAL: {2 12704 INVITE 4cb232e6-9b5a-4a5b-aa0e-1ed73539039f} tm [../../core/forward.h:290]: msg_send_buffer(): tcp_send failed 2) /usr/local/sbin/kamailio[282970]: ERROR: sl [sl.c:285]: send_reply(): failed to reply stateful (tm) 3) kamailio[283053]: CRITICAL: <core> [core/tcp_read.c:267]: tcp_read_data(): error reading: Connection reset by peer (104) ([217.66.156.172]:11604 -> kamailio[283053]: CRITICAL: <core> [core/tcp_read.c:270]: tcp_read_data(): -> [109.68.232.40]:15061) kamailio[283053]: CRITICAL: <core> [core/tcp_read.c:1523]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f71215bb610 r: 0x7f71215bb738 (-1) kamailio[283007]: CRITICAL: <core> [core/tcp_read.c:267]: tcp_read_data(): error reading: Connection timed out (110) ([188.170.204.16]:52148 -> kamailio[283007]: CRITICAL: <core> [core/tcp_read.c:270]: tcp_read_data(): -> [109.68.232.40]:15061) kamailio[283007]: CRITICAL: <core> [core/tcp_read.c:1523]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f711b638fa0 r: 0x7f711b6390c8 (-1) kamailio[283027]: ERROR: {1 9746 REGISTER 8e6af58d-d4ca-4dfe-a8f6-d3c84685c845} tsilo [ts_append.c:121]: ts_append_to(): transaction [23428:1443020265] not found 4) kamailio[282820]: CRITICAL: {1 2 UPDATE 6da65a87-3224-46a1-961f-8f9ee50348cc} tm [../../core/forward.h:290]: msg_send_buffer(): tcp_send failed kamailio[282820]: WARNING: {1 2 UPDATE 6da65a87-3224-46a1-961f-8f9ee50348cc} tm [t_fwd.c:1581]: t_send_branch(): sending request on branch 0 failed kamailio[282820]: ERROR: {1 2 UPDATE 6da65a87-3224-46a1-961f-8f9ee50348cc} sl [sl_funcs.c:415]: sl_reply_error(): stateless error reply used: Unfortunately error on sending to next hop occurred (477/SL) Once the queue is full, the system stops servicing new calls and freezes. kamailio -v version: kamailio 5.7.2 (x86_64/linux) 95629c flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MMAP, PKG_MALLOC, MEM_JOIN_FREE, 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_BLOCKLIST, HAVE_RESOLV_RES, TLS_PTHREAD_MUTEX_SHARED 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: 95629c OS: Debian 11, 64 cores, 125GB of DDR4 RAM; DB: MariaDB 10.5.15; udp_children: 30; tcp_children: 34; TLS: YES; async_workers: 64. Incoming calls are sent via push notifications( Federico Cabiddu method: https://www.voztovoice.org/sites/default/files/KamilioWorld2015%20-Federico…). NetBridging(for SIP and RTPEngine). ims_charging for billing (integration with our billing system using the Diameter protocol). As soon as the service starts responding with 503, it does not recover on its own, you have to restart. My server is powerful enough for the number of users of my service (what I mean is that there is no problem with resources). For example, 64 cores, 125GB of DDR4 RAM, 2TB of disk, of which 1TB SSD for the database, 10Gigabit channel, this is only a server for Kamailio for Rtpengines separate servers. Please help me figure out what causes a service failure!?

1 0

Jump to page:

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