June 2021 - sr-users - kamailio.org

AVPs in Switch/Case
by Joel Serrano 22 Jun '21

22 Jun '21

Hi guys, Quick question, are AVPs valid in "switch" as "case"'s? Example: $avp(var1) = "101"; $avp(var2) = "201"; switch($rU) { case "$avp(var1)": ... break; case "$avp(var2)": ... break; default: send_reply("403", "Forbidden"); exit; } For some reason I can't get the case to match, and I'm thinking it's not using the actual value of $avp(var1) and instead it's using literally "$avp(var1)" as a string. NOTE: I also tried without putting the AVPs in quotes, but Kamailio complains and doesn't start. Is this doable or do I need to use if..else if..else if..else for this? Thanks, Joel.

3 3

Web Sockets connection error: bad request, state=7, error=4
by Peter Manley 22 Jun '21

22 Jun '21

Hello, I'm using Kamailio 5.3.2 and am trying to establish a WebRTC connection for using SIP through Kamailio on port 8089. I am getting the following error in the Syslog: Jun 22 09:20:38 VRTPENGINE kamailio[43050]: ERROR: <core> [core/tcp_read.c:1535]: tcp_read_req(): bad request, state=7, error=4 buf:#012GET /ws HTTP/1.1#015#012Host: rtpengine.kombea.io:8089#015#012Connection: Upgrade#015#012Pragma: no-cache#015#012Cache-Control: no-cache#015#012User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.106 Safari/537.36#015#012Upgrade: websocket#015#012Origin: https://vicidev.kombea.io#015#012Sec-WebSocket-Version: 13#015#012Accept-Encoding: gzip, deflate, br#015#012Accept-Language: en-US,en;q=0.9#015#012Sec-WebSocket-Key: 1Pda50NxHxMenZaMW7cUkA==#015#012Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits#015#012Sec-WebSocket-Protocol: sip#015#012#015#012#012parsed:#012GET /ws HTTP/1.1#015#012Host: rtpengine.kombea.io:8089#015#012Connection: Upgrade#015#012Pragma: no-cache#015#012Cache-Control: no-cache#015#012User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.106 Safari/537.36#015#012Upgrade: websocket#015#012Origin: https://vicidev.kombea.io#015#012Sec-WebSocket-Version: 13#015#012Accept-Encoding: gzip, deflate, br#015#012Accept-Language: en-US,en;q=0.9#015#012Sec-WebSocket-Key: 1Pda50NxHxMenZaMW7cUkA==#015#012Sec-WebSocket-Extensions: permessage-deflate; client_max_window_bits#015#012Sec-WebSocket-Protocol: sip#015#012#015#012 Any idea on what would cause this? Thanks Peter H. Manley, Ph.D. Chief Software Architect KomBea Corporation 3400 North Ashton Blvd, Suite 470<https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> Lehi, Utah 84043<https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> www.kombea.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kombea.com_&d=DwMF-…> Office:+1.801.610.5808 Mobile +1.801.243.7773

2 2

execute callback every X minutes mid call
by Avremy Cohen 22 Jun '21

22 Jun '21

Hi I am trying to execute code every X min in active calls and I cant seem to find any way to do this. I basically have a function that checks if the user has balance and permission to carry on the call and the callback should trigger it every X mins. The call_control module doesnt work for me since A. It doesn't trigger a function it just ends the callback B. it uses an external application to calculate it any advice is appreciated Avi

3 3

Re: [SR-Users] Unable to establish TCP connection with Kamailio
by Peter Manley 17 Jun '21

17 Jun '21

Hello Ovidiu, Interestingly, that fixed the problem. I can now continue to make progress. Why does not forking and/or logging to stderr cause this to happen? Thank you! Regards, Peter Manley Ovidiu Sas osas at voipembedded.com<mailto:sr-users%40lists.kamailio.org?Subject=Re%3A%20%5BSR-Users%5D%20Unable%20to%20establish%20TCP%20connection%20with%20Kamailio&In-Reply-To=%3CCAND0LkvxyxE%3D5CPxZTe-Em43X6E5nep6z9n7a8f1zo3YbKksMw%40mail.gmail.com%3E> Thu Jun 17 23:05:14 CEST 2021 * Previous message (by thread): [SR-Users] Unable to establish TCP connection with Kamailio<https://lists.kamailio.org/pipermail/sr-users/2021-June/112759.html> * Messages sorted by: [ date ]<https://lists.kamailio.org/pipermail/sr-users/2021-June/date.html#112760> [ thread ]<https://lists.kamailio.org/pipermail/sr-users/2021-June/thread.html#112760> [ subject ]<https://lists.kamailio.org/pipermail/sr-users/2021-June/subject.html#112760> [ author ]<https://lists.kamailio.org/pipermail/sr-users/2021-June/author.html#112760> ________________________________ It seems that you have fork set to no, Let kamailio fork and collect logs via syslog (not via stderror). -ovidiu On Thu, Jun 17, 2021 at 16:26 Peter Manley <peter.manley at kombea.com<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>> wrote: > Hello, > > > > I'm running Kamailio Version 5.3.2 on Ubuntu 20.04. Here my build > information: > > > > version: kamailio 5.3.2 (x86_64/linux) > > flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, > DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, 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, 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: unknown > > compiled with gcc 9.2.1 > > > > I have the following configuration set in my kamalio.cfg file: > > > > ##!define WITH_MYSQL > > ##!define WITH_AUTH > > ##!define WITH_USRLOCDB > > ##!define WITH_TLS > > ##!define WITH_HOMER > > ##!define WITH_WEBSOCKETS > > ##!define WITH_ANTIFLOOD > > ##!define WITH_IPV6 > > ##!define WITH_BRIDGE_ON_FAIL > > ##!define WITH_LOCALHOST_WS > > ##!define WITH_LOCALHOST_SIP > > > > #!substdef "!MY_SIP_PORT!5060!g" > > #!substdef "!MY_SIPS_PORT!5061!g" > > #!substdef "!MY_WS_PORT!8088!g" > > #!substdef "!MY_WSS_PORT!8089!g" > > > > #!substdef "!MY_LOG_FACILITY!LOG_DAEMON!g" > > > > #!substdef "!MY_IP4_ADDR!172.16.0.57!g" > > #!substdef "!IP4_LOCALHOST!127.0.0.1!g" > > #!substdef "!MY_WS4_ADDR!tcp:MY_IP4_ADDR:MY_WS_PORT!g" > > #!substdef "!MY_WSS4_ADDR!tls:MY_IP4_ADDR:MY_WSS_PORT!g" > > #!substdef "!LOCALHOST_WS4_ADDR!tcp:IP4_LOCALHOST:MY_WS_PORT!g" > > #!substdef "!LOCALHOST_WSS4_ADDR!tls:IP4_LOCALHOST:MY_WSS_PORT!g" > > > > #!ifdef WITH_IPV6 > > #!substdef "!MY_IP6_ADDR![fe80::d6e4:2f5f:e5b7:7dff]!g" > > #!substdef "!IP6_LOCALHOST![::1]!g" > > #!substdef "!MY_WS6_ADDR!tcp:MY_IP6_ADDR:MY_WS_PORT!g" > > #!substdef "!MY_WSS6_ADDR!tls:MY_IP6_ADDR:MY_WSS_PORT!g" > > #!substdef "!LOCALHOST_WS6_ADDR!tcp:IP6_LOCALHOST:MY_WS_PORT!g" > > #!substdef "!LOCALHOST_WSS6_ADDR!tls:IP6_LOCALHOST:MY_WSS_PORT!g" > > #!endif > > > > #!substdef "!MY_DOMAIN!rtpengine.kombea.io!g" > > debug=10 // debug level (cmd line: -dddddddddd) > > children=4 > > #fork=yes > > force_rport=yes // Add recieved port to VIA > > #log_stderror=no // (cmd line: -E) > > > > // Uncomment these lines to enter debugging mode > > fork=no > > log_stderror=yes > > > > check_via=no // (cmd. line: -v) > > dns=no // (cmd. line: -r) > > rev_dns=no // (cmd. line: -R) > > > > log_facility=MY_LOG_FACILITY > > > > // Define the listening ports and addresses > > port=MY_SIP_PORT > > tls_port_no=MY_SIPS_PORT > > > > > > // Define TCP parameters > > tcp_children=4 > > tcp_no_connect=no > > tcp_rd_buf_size=16384 > > tcp_max_connections=2048 > > tcp_connection_lifetime=3605 > > disable_tcp=no > > #!ifdef WITH_TLS > > enable_tls=yes > > #!endif > > > > > > listen=MY_IP4_ADDR > > #!ifdef WITH_LOCALHOST_SIP > > listen=IP4_LOCALHOST > > #!endif > > #!ifdef WITH_IPV6 > > listen=MY_IP6_ADDR > > #!ifdef WITH_LOCALHOST_SIP > > listen=IP6_LOCALHOST > > #!endif > > #!endif > > > > #!ifdef WITH_WEBSOCKETS > > listen=MY_WS4_ADDR > > #!ifdef WITH_LOCALHOST_WS > > listen=LOCALHOST_WS4_ADDR > > #!endif > > #!ifdef WITH_IPV6 > > listen=MY_WS6_ADDR > > #!ifdef WITH_LOCALHOST_WS > > listen=LOCALHOST_WS6_ADDR > > #!endif > > #!endif > > #!ifdef WITH_TLS > > listen=MY_WSS4_ADDR > > #!ifdef WITH_LOCALHOST_WS > > listen=LOCALHOST_WSS4_ADDR > > #!endif > > #!ifdef WITH_IPV6 > > listen=MY_WSS6_ADDR > > #!ifdef WITH_LOCALHOST_WS > > listen=LOCALHOST_WSS6_ADDR > > #!endif > > #!endif > > #!endif > > #!endif > > > > force_rport=yes // Add received port to VIA > > > > loadmodule "pv.so" // Pseudo-Variable support > > loadmodule "xlog.so" // Formatted logging support > > loadmodule "sl.so" // Stateless request handling > > loadmodule "siputils.so" // SIP utility helpers > > loadmodule "sanity.so" // Sanity check > > loadmodule "maxfwd.so" // Support for Max-Forward header > > loadmodule "textops.so" // Text operations on SIP messages > > loadmodule "textopsx.so" // Extended Text operations on SIP messages > > loadmodule "sdpops.so" // SDP operations > > loadmodule "nathelper.so" // NAT traversal helpers > > loadmodule "rr.so" // Record Route handling > > loadmodule "outbound.so" // Outbound support > > loadmodule "path.so" // Path handling > > > > #!ifdef WITH_TLS > > loadmodule "tls.so" // TLS Support > > #!endif > > > > #!ifdef WITH_WEBSOCKETS > > loadmodule "xhttp.so" // XHTTP support > > loadmodule "websocket.so" // WebSocket support > > #!endif > > loadmodule "rtpengine.so" // RTPEngine control > > > > #!ifdef WITH_DEBUG > > loadmodule "debugger.so" > > #!endif > > > > When I start Kamailio, I see the following in the output to stderr: > > > > Listening on > > udp: 172.16.0.57:5060 > > tcp: 172.16.0.57:5060 > > Aliases: > > tcp: VRTPENGINE:5060 > > udp: VRTPENGINE:5060 > > > > WARNING: no fork mode > > 0(6299) INFO: <core> [core/tcp_main.c:5042]: init_tcp(): using epoll_lt > as the io watch method (auto detected) > > > > Here's the problem: > > > > When I connect via UDP, everything works fine. I can connect and see all > SIP traffic. > > > > However, if I try to connect via TCP, I see the initial SYN packet in > attempting to establish a connection. > > > > Kamailio responds with an [RST,ACK] message and the TCP connection is > never established. No further TCP traffic is sent. > > > > Any ideas on what I'm doing wrong? > > <https://www.google.com/maps/search/3400%0D%0A+North+Ashton+Blvd,+Suite+470+…> > > > > *Peter H. Manley, Ph.D.* > > Chief Software Architect > > KomBea Corporation > > 3400 North Ashton Blvd, Suite 470 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> > > Lehi, Utah 84043 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> > > www.kombea.com<http://www.kombea.com> > <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kombea.com_&d=DwMF-…> > > > > Office:+1.801.610.5808 > > Mobile +1.801.243.7773 > > > __________________________________________________________ > Kamailio - Users Mailing List - Non Commercial Discussions > * sr-users at lists.kamailio.org<https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users> > Important: keep the mailing list in the recipients, do not reply only to > the sender! > Edit mailing list options or unsubscribe: > * https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > -- VoIP Embedded, Inc. http://www.voipembedded.com<http://www.voipembedded.com/>

2 1

Unable to establish TCP connection with Kamailio
by Peter Manley 17 Jun '21

17 Jun '21

Hello, I'm running Kamailio Version 5.3.2 on Ubuntu 20.04. Here my build information: version: kamailio 5.3.2 (x86_64/linux) flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, 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, 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: unknown compiled with gcc 9.2.1 I have the following configuration set in my kamalio.cfg file: ##!define WITH_MYSQL ##!define WITH_AUTH ##!define WITH_USRLOCDB ##!define WITH_TLS ##!define WITH_HOMER ##!define WITH_WEBSOCKETS ##!define WITH_ANTIFLOOD ##!define WITH_IPV6 ##!define WITH_BRIDGE_ON_FAIL ##!define WITH_LOCALHOST_WS ##!define WITH_LOCALHOST_SIP #!substdef "!MY_SIP_PORT!5060!g" #!substdef "!MY_SIPS_PORT!5061!g" #!substdef "!MY_WS_PORT!8088!g" #!substdef "!MY_WSS_PORT!8089!g" #!substdef "!MY_LOG_FACILITY!LOG_DAEMON!g" #!substdef "!MY_IP4_ADDR!172.16.0.57!g" #!substdef "!IP4_LOCALHOST!127.0.0.1!g" #!substdef "!MY_WS4_ADDR!tcp:MY_IP4_ADDR:MY_WS_PORT!g" #!substdef "!MY_WSS4_ADDR!tls:MY_IP4_ADDR:MY_WSS_PORT!g" #!substdef "!LOCALHOST_WS4_ADDR!tcp:IP4_LOCALHOST:MY_WS_PORT!g" #!substdef "!LOCALHOST_WSS4_ADDR!tls:IP4_LOCALHOST:MY_WSS_PORT!g" #!ifdef WITH_IPV6 #!substdef "!MY_IP6_ADDR![fe80::d6e4:2f5f:e5b7:7dff]!g" #!substdef "!IP6_LOCALHOST![::1]!g" #!substdef "!MY_WS6_ADDR!tcp:MY_IP6_ADDR:MY_WS_PORT!g" #!substdef "!MY_WSS6_ADDR!tls:MY_IP6_ADDR:MY_WSS_PORT!g" #!substdef "!LOCALHOST_WS6_ADDR!tcp:IP6_LOCALHOST:MY_WS_PORT!g" #!substdef "!LOCALHOST_WSS6_ADDR!tls:IP6_LOCALHOST:MY_WSS_PORT!g" #!endif #!substdef "!MY_DOMAIN!rtpengine.kombea.io!g" debug=10 // debug level (cmd line: -dddddddddd) children=4 #fork=yes force_rport=yes // Add recieved port to VIA #log_stderror=no // (cmd line: -E) // Uncomment these lines to enter debugging mode fork=no log_stderror=yes check_via=no // (cmd. line: -v) dns=no // (cmd. line: -r) rev_dns=no // (cmd. line: -R) log_facility=MY_LOG_FACILITY // Define the listening ports and addresses port=MY_SIP_PORT tls_port_no=MY_SIPS_PORT // Define TCP parameters tcp_children=4 tcp_no_connect=no tcp_rd_buf_size=16384 tcp_max_connections=2048 tcp_connection_lifetime=3605 disable_tcp=no #!ifdef WITH_TLS enable_tls=yes #!endif listen=MY_IP4_ADDR #!ifdef WITH_LOCALHOST_SIP listen=IP4_LOCALHOST #!endif #!ifdef WITH_IPV6 listen=MY_IP6_ADDR #!ifdef WITH_LOCALHOST_SIP listen=IP6_LOCALHOST #!endif #!endif #!ifdef WITH_WEBSOCKETS listen=MY_WS4_ADDR #!ifdef WITH_LOCALHOST_WS listen=LOCALHOST_WS4_ADDR #!endif #!ifdef WITH_IPV6 listen=MY_WS6_ADDR #!ifdef WITH_LOCALHOST_WS listen=LOCALHOST_WS6_ADDR #!endif #!endif #!ifdef WITH_TLS listen=MY_WSS4_ADDR #!ifdef WITH_LOCALHOST_WS listen=LOCALHOST_WSS4_ADDR #!endif #!ifdef WITH_IPV6 listen=MY_WSS6_ADDR #!ifdef WITH_LOCALHOST_WS listen=LOCALHOST_WSS6_ADDR #!endif #!endif #!endif #!endif force_rport=yes // Add received port to VIA loadmodule "pv.so" // Pseudo-Variable support loadmodule "xlog.so" // Formatted logging support loadmodule "sl.so" // Stateless request handling loadmodule "siputils.so" // SIP utility helpers loadmodule "sanity.so" // Sanity check loadmodule "maxfwd.so" // Support for Max-Forward header loadmodule "textops.so" // Text operations on SIP messages loadmodule "textopsx.so" // Extended Text operations on SIP messages loadmodule "sdpops.so" // SDP operations loadmodule "nathelper.so" // NAT traversal helpers loadmodule "rr.so" // Record Route handling loadmodule "outbound.so" // Outbound support loadmodule "path.so" // Path handling #!ifdef WITH_TLS loadmodule "tls.so" // TLS Support #!endif #!ifdef WITH_WEBSOCKETS loadmodule "xhttp.so" // XHTTP support loadmodule "websocket.so" // WebSocket support #!endif loadmodule "rtpengine.so" // RTPEngine control #!ifdef WITH_DEBUG loadmodule "debugger.so" #!endif When I start Kamailio, I see the following in the output to stderr: Listening on udp: 172.16.0.57:5060 tcp: 172.16.0.57:5060 Aliases: tcp: VRTPENGINE:5060 udp: VRTPENGINE:5060 WARNING: no fork mode 0(6299) INFO: <core> [core/tcp_main.c:5042]: init_tcp(): using epoll_lt as the io watch method (auto detected) Here's the problem: When I connect via UDP, everything works fine. I can connect and see all SIP traffic. However, if I try to connect via TCP, I see the initial SYN packet in attempting to establish a connection. Kamailio responds with an [RST,ACK] message and the TCP connection is never established. No further TCP traffic is sent. Any ideas on what I'm doing wrong? Peter H. Manley, Ph.D. Chief Software Architect KomBea Corporation 3400 North Ashton Blvd, Suite 470<https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> Lehi, Utah 84043<https://urldefense.proofpoint.com/v2/url?u=https-3A__maps.google.com_-3Fq-3…> www.kombea.com<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.kombea.com_&d=DwMF-…> Office:+1.801.610.5808 Mobile +1.801.243.7773

2 1

ATIS-1000085 STIR/SHAKEN DIV PASSporT
by Steven Wheeler 17 Jun '21

17 Jun '21

My Google searches aren't turning up any results, probably because this standard isn't finalized yet, but is anyone aware of a module which implements DIV PASSporTs for diverted calls? More details on the standard here: https://transnexus.com/blog/2020/shaken-div-std-letter-ballot/ Steven Wheeler

3 5

Re: [SR-Users] Roadmap to the next major release - v5.5.0
by Henning Westerholt 16 Jun '21

16 Jun '21

Hello, If I remember correctly then in Debian Buster, the necessary library is not included and therefore the package cannot be build. You could use bullseye, the upcoming version, of compile by yourself. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: David Villasmil <david.villasmil.work(a)gmail.com> Sent: Wednesday, June 16, 2021 8:54 PM To: Henning Westerholt <hw(a)skalatan.de> Subject: Re: [SR-Users] Roadmap to the next major release - v5.5.0 I don't see the module in deb http://deb.kamailio.org/kamailio55 buster main Regards, David Villasmil email: david.villasmil.work(a)gmail.com<mailto:david.villasmil.work@gmail.com> phone: +34669448337 On Wed, Jun 16, 2021 at 9:12 AM Henning Westerholt <hw(a)skalatan.de<mailto:hw@skalatan.de>> wrote: Hello, if you are referring to the module, its available in this release: https://kamailio.org/docs/modules/5.5.x/modules/secsipid.html Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: sr-users <sr-users-bounces(a)lists.kamailio.org<mailto:sr-users-bounces@lists.kamailio.org>> On Behalf Of David Villasmil Sent: Wednesday, June 16, 2021 10:03 AM To: Kamailio (SER) - Users Mailing List <sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org>>; miconda(a)gmail.com<mailto:miconda@gmail.com> Subject: Re: [SR-Users] Roadmap to the next major release - v5.5.0 Hello Daniel, Is it possible at all to get secsipid in? Thanks David On Thu, 25 Feb 2021 at 15:21, Daniel-Constantin Mierla <miconda(a)gmail.com<mailto:miconda@gmail.com>> wrote: Hello, it is the time to plan a bit the road to the next major release, to be versioned 5.5.0. The 5.4.0 was release by end of July 2020, therefore we are approaching the end of our usual development cycle, also during the last online devel meeting we considered the 2nd part of spring 2021 as a target time frame for 5.5. To narrow it down, I would propose to freeze the development at the end of March 2021, test during April and maybe beginning of May, then release v5.5.0. So far we have a lot of development to existing components, by the freeze date I expect 3-5 new modules to be in the repo as well. If anyone wants a different time line towards 5.5.0, let's discuss and choose the one that suits most of the developers. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com<http://www.asipto.com> www.twitter.com/miconda<http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda<http://www.linkedin.com/in/miconda> Funding: https://www.paypal.me/dcmierla _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Regards, David Villasmil email: david.villasmil.work(a)gmail.com<mailto:david.villasmil.work@gmail.com> phone: +34669448337

2 1

Roadmap to the next major release - v5.5.0
by Daniel-Constantin Mierla 16 Jun '21

16 Jun '21

Hello, it is the time to plan a bit the road to the next major release, to be versioned 5.5.0. The 5.4.0 was release by end of July 2020, therefore we are approaching the end of our usual development cycle, also during the last online devel meeting we considered the 2nd part of spring 2021 as a target time frame for 5.5. To narrow it down, I would propose to freeze the development at the end of March 2021, test during April and maybe beginning of May, then release v5.5.0. So far we have a lot of development to existing components, by the freeze date I expect 3-5 new modules to be in the repo as well. If anyone wants a different time line towards 5.5.0, let's discuss and choose the one that suits most of the developers. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla

3 3

Using Kamailio with Asterisk/pjsip outbound_publish - early state is not notified
by Barry Flanagan 15 Jun '21

15 Jun '21

Hi Using Kamailio 5.4 with Asterisk 18 and using the pjsip outbound-publish to allow Kamailio to handle BLF for phones. BLF sort of works, in that when a line is on a call, the BLF reflects that. However the early/ringing state does not generate a NOTIFY to the phone, although Asterisk is sending the Publish and is receiving a 200OK reply from Kamailio. I would presume that since basic BLF is working that this early state PUBLISH should generate a NOTIFY but it doesn't Module params are as follows: # ----- presence params ----- modparam("presence", "db_url", DBURL) modparam("presence", "server_address", "sip:192.168.245.250:5060") modparam("presence", "local_log_level", 3) modparam("presence", "publ_cache", 0) modparam("presence", "timeout_rm_subs", 0) modparam("presence", "sip_uri_match", 1) # ----- presence_xml params ----- modparam("presence_xml", "db_url", DBURL) modparam("presence_xml", "force_active", 1) modparam("presence_dialoginfo", "force_single_dialog", 0) modparam("presence_dialoginfo", "force_dummy_dialog", 1) Any help appreciated! -Barry

1 0

Kamailio v5.5.1 Released
by Daniel-Constantin Mierla 15 Jun '21

15 Jun '21

Hello, Kamailio SIP Server v5.5.1 stable release is out. This is a maintenance release of the latest stable branch, 5.5, that includes fixes since the release of v5.5.0. There is no change to database schema or configuration language structure that you have to do on previous installations of v5.5.x. Deployments running previous v5.5.x versions are strongly recommended to be upgraded to v5.5.1. For more details about version 5.5.1 (including links and guidelines to download the tarball or from GIT repository), visit: * https://www.kamailio.org/w/2021/06/kamailio-v5-5-1-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

1 0

Releasing Kamailio v5.5.1
by Daniel-Constantin Mierla 15 Jun '21

15 Jun '21

Hello, I am considering to release Kamailio v5.5.1 sometime next week, likely on Tuesday or Wednesday (June 15 or 16, 2021). This is the usual heads up notification to see if anyone is aware of issues not yet reported to bug tracker and if yes, do it as soon as possible to give them a chance to be fixed. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

2 3

Is Kamailio GPL or GPLv2
by Yan Gao 15 Jun '21

15 Jun '21

Hello, I have a question about the license of Kamailio. It is said to be GPL in https://www.kamailio.org/w/: "Kamailio® (successor of former OpenSER and SER) is an Open Source SIP Server released under GPL, able to handle thousands of call setups per second...." But GPLv2 in https://www.kamailio.org/w/info/ : "Kamailio is released under GNU Public License v2 (GPLv2). Beginning with 3.0.0, the application includes parts of code under BSD license that can be used such as individual components." Which one is the correct description? Thanks & Regards, Yan

2 2

vsf/vst question
by David Escartín 15 Jun '21

15 Jun '21

Hello all! as we knew vsf/vst were added to the RR header when using uac_replace for From/To headers. BUt we observed that some versions ago (we are using now 5.4) that stop happening with this setup modparam("uac", "restore_mode", "auto") modparam("uac", "restore_dlg", 1) modparam("rr", "enable_full_lr", 0) modparam("rr", "enable_double_rr", 1) modparam("rr", "append_fromtag", 1) and only ftag, did are added as param to RR However we have seen that when using multihomed kamailio instance and doing uac_replace, vsf/vst are included also with ftag and did params. Is that behaviour known or expected? thanks a lot and regards david -- <http://www.sonoc.io/> David Escartín NOC engineer *www.sonoc.io* <http://www.sonoc.io/> [image: LinkedIn] <https://www.linkedin.com/company/sonoc> [image: Twitter] <https://twitter.com/sonoc_> [image: Facebook] <https://www.facebook.com/SONOCio/> This e-mail is for the exclusive use of its recipients and may contain business secrets or other confidential or privileged information. Any unauthorised use, copying, publication or distribution of this e-mail is strictly prohibited. If you are not the intended recipient, please inform us immediately by replying to this e-mail and delete it, including any attachments or copies on your system. In accordance with the GDPR (EU) 2016/679 and the LOPDGDD 3/2018, we inform you that this e-mail address and/or any other personal data you have provided us with will be treated by SONOC with absolute confidentiality and with the only purpose of providing you with the requested services, due to your condition as a client, supplier or because you have requested information from us at any time. These data will only be kept for as long as required to comply with legal obligations. You can exercise your rights at any time by sending an e-mail to: *dataprotection(a)sonoc.io* <dataprotection(a)sonoc.io>*.* <dataprotection(a)sonoc.io>

2 2

using path in Subscriber table
by Thành Trần Duy 14 Jun '21

14 Jun '21

Hi all, First of all, I would like to present the system model we are applying: - dSIPRouter : Sip relay for all users connected from the internet (installed with RTPEngine to handle media data). - kamailio 5.3.5: core system, registration server. - Asterisk 17: SBC. Sorry if our model seems a bit backwards but we have so many users (>12k configured users, > 3k concurrent registered users, > 500 concurrent users at cps 10), I don't know of any solution that can work with such a large load. With call outbound (from user to PSTN via SBC), everything is fine. But with internal or inbound calls, it wasn't successful. I showed that: - After dSIPRouter, the register message has Path parameter in SIP Header, - Kamailio store sip:user@domain in column contact at location table. - Using modparam registrar with use_path=1, path_mode=0, path_use_received=1, I stored this parameter in DB. - When calling internal or inbound, for the search destination of a phone, I am using sip_trace() function. But the result is always column contact. - With this uri, kamailio wasn't known and sent the invite to proxy. - Final error message: 404. I need one of these solutions: - get path column when result of sip_trace() like sip:user@domain (with phone in internal network, it like sip:user@ipaddress). - write path value to column contact when the register message has it. - sip_trace can get a path instead of contact if it has. Or you can have other solutions, pls help me. We can talk and test via my Webex PMR. Many thanks, Thanh Duy Tran

3 3

set empty custom global variable
by Sergey Safarov 14 Jun '21

14 Jun '21

In Kamailio config I use empty global string variable local.trace_troubleshooting_net = "" descr "trace all SIP messages from given network" When I check variable value I get blank string kamcmd cfg.get local trace_troubleshooting_net I can set new value [root@host]# kamcmd cfg.sets local trace_troubleshooting_net "2600::/48" [root@host]# kamcmd cfg.get local trace_troubleshooting_net 2600::/48 Now I want to set the empty custom global variable using a command kamcmd cfg.sets group trace_troubleshooting_net "" But get error error: 400 - error at parameter 2: expected string type but record doesn't match type How to properly set empty values?

3 4

Kamailio 5.5.0 | CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 26
by Laurent Schweizer 11 Jun '21

11 Jun '21

Dear all, I setup a Kamailio 5.5.0 (from GIT) on a ubuntu Ubuntu 18.04.5 LTS and I have some error with the libssl/ libmysql, seems not happening every time. Regarding the config file, it's a config running correctly on a Kamailio 5.3.x on a centos 7 I have attached the returned error and the result of the core file. Any idea ? BR Laurent version: kamailio 5.5.0 (x86_64/linux) 66370c flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, 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_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: 66370c compiled on 07:23:15 Jun 11 2021 with gcc 7.5.0 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: loading modules under config path: /usr/local/lib64/kamailio/modules/ Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: Listening on Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: 80.132.9.112:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: 80.132.9.112:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: 80.132.9.112:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: 80.132.9.112:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tls: 80.132.9.112:5061 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: Aliases: Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tls: zrh02-srv03:5061 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: zrh02-srv03:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: tcp: zrh02-srv03:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: zrh02-srv03:6000 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: udp: zrh02-srv03:5060 Jun 11 21:35:45 zrh02-srv03 kamailio[7129]: *: sipbkp.demo.ch:* Jun 11 21:35:45 zrh02-srv03 /usr/local/sbin/kamailio[7135]: WARNING: tls [tls_init.c:793]: tls_h_mod_init_f(): openssl bug #1491 (crash/mem leaks on low memory) workaround enabled (on low memory tls operations will fail preemptively) with free memory thresholds 13107200 and 6553600 bytes Jun 11 21:35:45 zrh02-srv03 /usr/local/sbin/kamailio[7135]: NOTICE: tls [tls_domain.c:1136]: ksr_tls_fix_domain(): registered server_name callback handler for socket [:0], server_name='<default>' ... Jun 11 21:35:46 zrh02-srv03 kernel: [304361.950608] traps: kamailio[7147] general protection ip:7f5d209a344b sp:7ffe6ae5adb8 error:0 in libcrypto.so.1.1[7f5d207b5000+29b000] Jun 11 21:35:46 zrh02-srv03 systemd[1]: Started Kamailio SIP Server. Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7161]: CRITICAL: <core> [core/pass_fd.c:277]: receive_fd(): EOF on 26 Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7135]: ALERT: <core> [main.c:788]: handle_sigs(): child process 7147 exited by a signal 11 Jun 11 21:35:54 zrh02-srv03 /usr/local/sbin/kamailio[7135]: ALERT: <core> [main.c:791]: handle_sigs(): core was generated Jun 11 21:35:54 zrh02-srv03 systemd[1]: kamailio.service: Main process exited, code=exited, status=1/FAILURE Jun 11 21:35:54 zrh02-srv03 systemd[1]: kamailio.service: Failed with result 'exit-code'. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/. Find the GDB manual and other documentation resources online at: http://www.gnu.org/software/gdb/documentation/. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/local/sbin/kamailio...done. [New LWP 7147] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `/usr/local/sbin/kamailio -m 5000 -M 128 -P /run/kamailio/kamailio.pid -f /confi'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f5d209a344b in X509_LOOKUP_by_subject () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (gdb) bt #0 0x00007f5d209a344b in X509_LOOKUP_by_subject () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #1 0x00007f5d209a3a5b in X509_STORE_CTX_get_by_subject () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #2 0x00007f5d209a418d in X509_STORE_CTX_get1_issuer () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #3 0x00007f5d209a9207 in ?? () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #4 0x00007f5d209a9f96 in X509_verify_cert () from /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 #5 0x00007f5d20caf337 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #6 0x00007f5d20cd037b in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #7 0x00007f5d20cd2995 in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #8 0x00007f5d20ccc48c in ?? () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #9 0x00007f5d20cb84e4 in SSL_do_handshake () from /usr/lib/x86_64-linux-gnu/libssl.so.1.1 #10 0x00007f5d215cbdb1 in ?? () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #11 0x00007f5d2159f4de in mysql_real_connect () from /usr/lib/x86_64-linux-gnu/libmysqlclient.so.20 #12 0x00007f5d21b410b1 in db_mysql_new_connection (id=0x7f5d21ee2b30) at km_my_con.c:157 #13 0x00007f5d211456dc in db_do_init2 (url=0x7f5d1e9dd4e0 <ul_db_url>, new_connection=0x7f5d21b3f6a4 <db_mysql_new_connection>, pooling=DB_POOLING_PERMITTED) at db.c:317 #14 0x00007f5d211443f9 in db_do_init (url=0x7f5d1e9dd4e0 <ul_db_url>, new_connection=0x7f5d21b3f6a4 <db_mysql_new_connection>) at db.c:270 #15 0x00007f5d21b3459e in db_mysql_init (_url=0x7f5d1e9dd4e0 <ul_db_url>) at km_dbase.c:202 #16 0x00007f5d1e7a1987 in child_init (_rank=-1) at usrloc_mod.c:471 #17 0x000055ddd6c45602 in init_mod_child (m=0x7f5d21e03818, rank=-1) at core/sr_module.c:864 #18 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e03bb8, rank=-1) at core/sr_module.c:860 #19 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e04498, rank=-1) at core/sr_module.c:860 #20 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e056a8, rank=-1) at core/sr_module.c:860 #21 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e06390, rank=-1) at core/sr_module.c:860 #22 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e06b38, rank=-1) at core/sr_module.c:860 #23 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e06fb8, rank=-1) at core/sr_module.c:860 #24 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e075f0, rank=-1) at core/sr_module.c:860 #25 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e090c0, rank=-1) at core/sr_module.c:860 #26 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e09500, rank=-1) at core/sr_module.c:860 #27 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0a400, rank=-1) at core/sr_module.c:860 #28 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0aa70, rank=-1) at core/sr_module.c:860 #29 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0b0b0, rank=-1) at core/sr_module.c:860 #30 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0b5d8, rank=-1) at core/sr_module.c:860 #31 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0bdd0, rank=-1) at core/sr_module.c:860 #32 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0c968, rank=-1) at core/sr_module.c:860 #33 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e0f7f8, rank=-1) at core/sr_module.c:860 #34 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e105d8, rank=-1) at core/sr_module.c:860 #35 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e109b0, rank=-1) at core/sr_module.c:860 #36 0x000055ddd6c4521d in init_mod_child (m=0x7f5d21e10ea0, rank=-1) at core/sr_module.c:860 #37 0x000055ddd6c45ef9 in init_child (rank=-1) at core/sr_module.c:909 #38 0x000055ddd6b9eebe in fork_process (child_id=-1, desc=0x55ddd6ee7847 "slow timer", make_sock=1) at core/pt.c:337 #39 0x000055ddd6abaa62 in main_loop () at main.c:1814 #40 0x000055ddd6ac6095 in main (argc=9, argv=0x7ffe6ae5d298) at main.c:3053

1 0

Kamailio SBC+ Freeswitch as media server
by John Tuxies 09 Jun '21

09 Jun '21

in a Debian system i am running Kamailio 5.5 installed from repo and with the basic setup i have 2 users 101 & 102 to be able to call each other. So far so good. i added Freeswitch in the same system and tried to follow this guide http://kb.asipto.com/freeswitch:kamailio-3.1.x-freeswitch-1.0.6d-sbc even though it is old and there are many changes. Freeswitch is installed from deb repo as well. after following the guide i tried to adapt to newer versions of kamailio and freeswitch, but i am getting errors. The problem is that the users now are able to register to Kamailio, but unable to call each other. I can see users being registered in Kamailio: *root@kamfs: ~ $ kamctl online101102root@kamfs: ~ $* while when 101 calls 102 i am getting: *2021-06-08 10:35:19.015670 [NOTICE] switch_channel.c:1118 New Channel sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> [f3b8f5a0-652a-4640-b2d3-9b7cc21d7f91]2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Running State Change CS_NEW (Cur 1 Tot 5)2021-06-08 10:35:19.015670 [INFO] sofia.c:10362 sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> receiving invite from 192.168.1.15:5060 <http://192.168.1.15:5060> version: 1.10.6 -release-18-1ff9d0a60e 64bit call-id: ZDFiZWFkZmVmYjgxZDEwOTgyYTYxZjkxNzkwMzlmYmQ.2021-06-08 10:35:19.015670 [DEBUG] sofia.c:10456 verifying acl "domains" for ip/port 192.168.1.15:0 <http://192.168.1.15:0>.2021-06-08 10:35:19.015670 [WARNING] sofia.c:10569 IP 192.168.1.15 Rejected by acl "domains"2021-06-08 10:35:19.015670 [NOTICE] sofia.c:2445 Hangup sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> [CS_NEW] [CALL_REJECTED]2021-06-08 10:35:19.015670 [DEBUG] sofia.c:1549 Channel is already hungup.2021-06-08 10:35:19.015670 [DEBUG] sofia.c:1549 Channel is already hungup.2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:604 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State NEW2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Running State Change CS_HANGUP (Cur 1 Tot 5)2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:848 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Callstate Change DOWN -> HANGUP2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:850 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State HANGUP2021-06-08 10:35:19.015670 [DEBUG] mod_sofia.c:453 Channel sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> hanging up, cause: CALL_REJECTED2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:60 sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> Standard HANGUP, cause: CALL_REJECTED2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:850 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State HANGUP going to sleep2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:620 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State Change CS_HANGUP -> CS_REPORTING2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:585 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Running State Change CS_REPORTING (Cur 1 Tot 5)2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:936 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State REPORTING2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:174 sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> Standard REPORTING, cause: CALL_REJECTED2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:936 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State REPORTING going to sleep2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:611 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State Change CS_REPORTING -> CS_DESTROY2021-06-08 10:35:19.015670 [DEBUG] switch_core_session.c:1736 Session 5 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Locked, Waiting on external entities2021-06-08 10:35:19.015670 [NOTICE] switch_core_session.c:1754 Session 5 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Ended2021-06-08 10:35:19.015670 [NOTICE] switch_core_session.c:1758 Close Channel sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> [CS_DESTROY]2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:739 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) Running State Change CS_DESTROY (Cur 0 Tot 5)2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:749 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State DESTROY2021-06-08 10:35:19.015670 [DEBUG] mod_sofia.c:364 sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> SOFIA DESTROY2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:181 sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15> Standard DESTROY2021-06-08 10:35:19.015670 [DEBUG] switch_core_state_machine.c:749 (sofia/internal/101(a)192.168.1.15 <101(a)192.168.1.15>) State DESTROY going to sleepfreeswitch@kamfs>* i am attaching the kamailio.cfg file and the whole /etc/freeswitch folder, if someone could help me to solve this issue, please. Kind regards, John

3 2

Any way to force socket used to reach databases ?
by David VILLAUME 08 Jun '21

08 Jun '21

Hello, I’m trying to initiate a redis connection in ndb_redis for topos_redis on a keepalived slave host, but host tries to use the VIP instead of the second socket I defined. Is there a way to influence the ‘database source socket’ so the server can connect with a secondary address even if it does not own the keepalived VIP (tried mhomed options without improvment) ? Regards, David

2 1

List of Header Names
by Evan Verma 07 Jun '21

07 Jun '21

hello! new to working with sip/kamailio. I am currently trying to get a list of all of the header names on the invite the SBC receives. I am having trouble finding a way to do this. Does anyone know of a good solution?

5 4

Problem NOTIFY in Presence module
by hamed r 07 Jun '21

07 Jun '21

hello dears ,i am using presence module and NOTIFY message are working properly. but when i put the database on another server , NOTIFY message will not be sent to subscribers. what is problem?

2 2

List of Header Names
by Evan Verma 05 Jun '21

05 Jun '21

hello! new to working with sip/kamailio. I am currently trying to get a list of all of the header names on the invite the SBC receives. I am having trouble finding a way to do this. Does anyone know of a good solution? -- Evan

2 1

STIR/SHAKEN
by David Villasmil 04 Jun '21

04 Jun '21

Hello guys, So I'm testing secsipid with made up certificates, basically: [image: Untitled.png] The verification _always_ comes back OK, event if I create the Identity with different From numbers, should that fail? Thanks all, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 2

Info: ClueCon Weekly about Kamailio 5.5 series - Jun 4, 2021, 10:00am CT
by Daniel-Constantin Mierla 04 Jun '21

04 Jun '21

Hello, short announcement to let everyone know that next Friday, Jun 4, 2021, at 10:00am CT (17:00 Berlin), I will join ClueCon Weekly to discuss about latest Kamailio 5.5 series. If you have questions about or just want to be part of the discussions, consider to join the live video conference session, more details at: * https://www.cluecon.com/cclive-6-4/ Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online - June 7-10, 2021 (America Timezone) * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 1

About Kamailio ass authentication service
by Nael Silega 04 Jun '21

04 Jun '21

hi, i have a question, can i use Kamailio as a authentication service? i´m traing to set up STIR/SHAKEN framework and im looking for a server that work as authentication service

3 2

Questions on http_async_query() in event_route[xhttp:request] and async best practices for Kamailio
by James Aylett 04 Jun '21

04 Jun '21

Hi, I am using Kamailio v5.2 as a WebRTC proxy for SIP clients, as part of my setup I call a REST API before calling ws_handle_handshake() in event_route[xhttp:request] using http_client_query() to authenticate and retrieve some user details (routing etc) for the user connected via WebSockets. This worked fine until increased load on the system meant API responses were slow, this caused a knock-on effect to existing connected users. Specifically, we saw mass WebSocket disconnects for existing connected users - believed to be due to using too aggressive proxy timeout settings on our reverse proxy in front of Kamailio. My understanding is that event_route[xhttp:request] uses the shared SIP TCP worker threads, so potentially could slow API requests over the network block all the handlers? Could this potentially impact the keepalive processes used by the WebSocket module to check existing WebSocket connections? We were using ping keepalives, again with pretty aggressive timers... To resolve this issue, I am looking at whether I can call API requests asynchronously so that TCP workers are not blocked, my first thought was to use http_async_query() in event_route[xhttp:request] and call ws_handle_handshake() in the HTTP_REPLY route when the API call had completed, but I get "ERROR: websocket [ws_handshake.c:143]: ws_handle_handshake(): retrieving connection". I presume then this approach is a deadend, looking at newer kamailio versions 5.5, there doesn't seem to be any way to do this, correct? Instead of using http_async_query() in event_route[xhttp:request], I presume I could set a short timeout in http_client_query(), but my concern is new WebSocket connections could still impact and block existing ones in this case... My other thought was to move my API call out from the event_route[xhttp:request] into my route handler for REGISTER requests, thinking I could offload new register requests to async workers and move the API call there so as to not block existing connections. Does this seem like a reasonable approach to the problem? Given my current script does not use any async workers, how would one go about optimising the number of plain SIP TCP workers to async workers, are there any guides for this? In general, for any potentially blocking "APIs" or calls over the network, is it best practice to offload them into async workers. For example, we run RTPEngine on separate hosts to Kamailio so should I be wrapping rtpengine_offer/answer calls into async workers in case of a slow network? Apologies for the long text, but I would really appreciate any help to understand these problems. Thank you

2 1

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 June 2021