sr-users

sr-users@lists.kamailio.org

46 participants
37553 discussions

Re: [SR-Users] sr-users Digest, Vol 211, Issue 8
by Pooja Yadav 13 Dec '22

13 Dec '22

Hi Daniel and Everyone, Thanks for the inputs. We understand that Kamailio is a SIP signalling server irrespective of any core. But we have seen a thread in Open5Gs community where they established the call with Kamailio IMS. Below thread is for your reference. https://open5gs.org/open5gs/docs/tutorial/02-VoLTE-setup/ If you have any inputs on this it is most welcome. We just want to check the feasibility of establishing voice/video call with 5G core. Your inputs will be appreciated. … [View More]

2 1

Delays sending over WSS
by Alex Balashov 12 Dec '22

12 Dec '22

Hi, I’ve run into stubbornly persistent problems with packets not reaching WSS clients until some seconds (5-6s or more!) after they were supposedly sent. The symptom is that Kamailio logs the event as sent at 20:00:00, including in the onsend_route, but in actual reality it takes quite a bit longer to send at the OS network stack level. This happens occasionally and quite universally, with no discernible pattern tied to particular endpoints, networks, etc. For a long time, I’ve just assumed … [View More]

2 2

Kamailio SIP client registration issue
by Shiva Shankar Chittallu 09 Dec '22

09 Dec '22

Hi Team, I have installed kamailio sip server 5.5.5 version in ubuntu 20.04 in AWS instance with public IP. When im trying to register an device im getting below error in the syslog. Thanks & Regards Shiva 9100663346

2 1

Does Kamailio supports Voice and Video call support for 5G Core
by Pooja Yadav 09 Dec '22

09 Dec '22

Hi Kamailio community, We just want to check does Kamailio IMS supports the functionality of Voice and Video call support (Vo5G) with 5G core? If yes, please share the document reference. Else, please guide us when it will be available. Any plans in upcoming release to support HTTP2 based SBI interface between P- CSCF and PCF. Your inputs will be highly appreciated. Thanks & Regards, Pooja Yadav

4 4

Next online devel meeting - Thu, Dec 8, 2022, 15:00UTC
by Daniel-Constantin Mierla 08 Dec '22

08 Dec '22

Hello, to summarize what happened at the devel meeting in Dusseldorf a few weeks ago and plan the next steps for the project, we are planning an online development meeting on Thu, Dec 8, 2022, 15:00UTC. As usual, one of the targets is to sketch the roadmap to next major release so the developers and community members can syncronize and plan what should be done till Kamailio v5.7 (or 6.0) will be out as well as discuss about current state of the project, look for new ideas to improve … [View More]

1 3

Outgoing SIP/TLS connection error (msg_send_buffer(): tcp_send failed)
by Denys Pozniak 08 Dec '22

08 Dec '22

Hello! We use trunk with Twilio through a SIP/TLS. They establish incoming calls from random ports, like: (Twilio)3.3.3.3:54321 --> (Kamailio)2.2.2.2:5061 In case of sending in-dialog requests to them, Kamailio should establish an outgoing connection to the dst port 5061 (as per Route), like: (Kamailio)2.2.2.2 --> (Twilio)3.3.3.3:5061 But as per tcpdump traces and logs, Kamailio does not even try to establish an outgoing connection to Twilio. There should be no problems with routes and … [View More]the network on that server, as regular telnet to Twilio shows that 5061 is open. What could be the reason and how to debug? *Script:* onsend_route { xlog("L_ERR","[$cfg(route)]*RELAY ONSEND* $rm / $du / $fs / $fsn / [$ci]\n"); } *Syslog:* DEBUG <core> [core/resolve.c:1259]: srv_sip_resolvehost(): 3.3.3.3:5061 proto=3 DEBUG <core> [core/resolve.c:1371]: srv_sip_resolvehost(): returning 0x55acd63a63c0 (3.3.3.3:5061 proto=3) ERROR <script>: [DEFAULT_SEND]*RELAY ONSEND* REFER / sip:3.3.3.3:5061;transport=tls / tls:10.1.1.1:5061 / sip_wan_tls / [123] DEBUG tm [../../core/forward.h:277]: msg_send_buffer(): sending to: 3.3.3.3:5061, force_socket=4, send_sock=0x7f090049b8e8 DEBUG tm [../../core/forward.h:292]: msg_send_buffer(): tcp_send failed DEBUG tm [t_fwd.c:1568]: t_send_branch(): send to 3.3.3.3:5061 (3) failed WARNING: tm [t_fwd.c:1588]: t_send_branch(): sending request on branch 0 failed DEBUG tm [t_funcs.c:335]: t_relay_to(): t_forward_nonack returned error -1 (-477) DEBUG tm [t_funcs.c:353]: t_relay_to(): -477 error reply generation delayed DEBUG sl [sl_funcs.c:558]: sl_run_callbacks(): execute callback for event type 1 *Software:* - Kamailio is listening on (+udp, +tcp): tls: 10.1.1.1:5061 name sip_wan_tls advertise 2.2.2.2:5061 - OS is Debian 11.5 - # kamailio -v version: kamailio 5.6.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_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: unknown compiled with gcc 10.2.1 - # dpkg -l | grep ssl ii libssl1.1:amd64 1.1.1n-0+deb11u3 amd64 Secure Sockets Layer toolkit - shared libraries ii openssl 1.1.1n-0+deb11u3 amd64 Secure Sockets Layer toolkit - cryptographic utility -- BR, Denys Pozniak [View Less]

2 2

KAMCTL error
by Govind Swamy 08 Dec '22

08 Dec '22

[image: Error in KAMCTL.png] Hi am unable to create using kamctl

3 2

Re: [SR-Users] uac_req_send() multi-process synchronization problem
by Henning Westerholt 08 Dec '22

08 Dec '22

Hello, please keep the list in CC. Not sure what you mean by multi-process safe. The functions are safe to use in a kamailio multi-process context, relevant sections should be protected by internal locks etc.. Regarding query location manually by SQL client, its better to use the provided functions from the usrloc/registrar module instead. Cheers, Henning -- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.com<https://gilawa.com/> From: riffs(a)sina.… [View More]cn <riffs(a)sina.cn> Sent: Thursday, December 1, 2022 10:47 AM To: Henning Westerholt <hw(a)gilawa.com> Subject: Re: Re: [SR-Users] uac_req_send() multi-process synchronization problem To confirm that. Are reg_fetch_contacts and unregister_ruid multi-process safe? ________________________________ riffs(a)sina.cn<mailto:riffs@sina.cn> From: riffs(a)sina.cn<mailto:riffs@sina.cn> Date: 2022-12-01 16:35 To: Henning Westerholt<mailto:hw@gilawa.com> Subject: Re: RE: [SR-Users] uac_req_send() multi-process synchronization problem Hello Thank you for your reply very much. My LOCATION is stored in the MYSQL database, and I also set the event_callback parameter of TCPOPS. modparam("tcpops", "event_callback", "ksr_tcpops_event") At the same time.I also deleted the contact inside the function function ksr_tcpops_event(evname) local tcpconnid = KSR.pv.get("$conid") or "0" if (evname == "tcp:reset" or evname == "tcp:closed") and (tonumber(tcpconnid) ~= 0) then local sql = string.format("select * from location where tcpconnid=%s", tcpconnid) local count, rows = execute_select(sql) if count > 0 then KSR.registrar.unregister_ruid("location", rows[1].contact, rows[1].ruid) end end return 1 end When I use use_req_send(), I use the following sql statement to query location string.format("select * from location where username='%s'", reciever) I think because the query sql is executed before the execution of unregister_ruid completes, the location of user A can still be queried. If unregister_ruid and reg_fetch_contacts are multi-process safe. I use reg_fetch_contacts query location to avoid this problem. Is that so? thanks very much ________________________________ riffs(a)sina.cn<mailto:riffs@sina.cn> From: Henning Westerholt<mailto:hw@gilawa.com> Date: 2022-11-30 18:18 To: Kamailio (SER) - Users Mailing List<mailto:sr-users@lists.kamailio.org> CC: 刘建峰<mailto:riffs@sina.cn> Subject: RE: [SR-Users] uac_req_send() multi-process synchronization problem Hello, not sure if I fully understand the problem. But regarding another user is registered with the same IP address as a previous user, there are several mitigations. To give two options: you could choose a really short re-registration time, you could use TCP and when you lose the connection you delete the contact. 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 ??? Sent: Wednesday, November 30, 2022 2:57 AM To: sr-users(a)lists.kamailio.org<mailto:sr-users@lists.kamailio.org> Subject: [SR-Users] uac_req_send() multi-process synchronization problem When I use uac_req_send() to send a MESSAGE to the client. Will the following occur? The result of the message sent to user A is that B has received it. From the logs, the address of user A in the location table is the same as the IP address and port of user B, and the information of user A in the location table is not deleted in time. I took the address of user A directly from the location table without using KSR.registrar.reg_fetch_contacts(). If I use KSR.registrar.reg_fetch_contacts() can this be avoided. This is a multi-process synchronization problem, after user A registers, the IP port information in the address is 172.16.22.222:12345, and then user A disconnects the link because of some abnormal conditions, but it is not normal to cancel the registration, the socket link has failed, but it has not had time to delete the location, at this time user B registers, whether will it get the same IP port information as user A 172.16.22.222 : 12345, if possible? User A's location still exists, Using KSR.registrar.reg_fetch_contacts() TO query user A's location, and then using uac_req_send() to send a message to user A, User B will receive the MESSAGE. Whether this problem occurs? 从 Windows 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>发送 [View Less]

2 2

Fosdem 2023 - CfP
by Daniel-Constantin Mierla 07 Dec '22

07 Dec '22

Hello, should anyone be interested to present or just go to FOSDEM 2023, note that it is going to take place in Brussels during February 4-5, 2023. With a increasing demand on topics to be covered, many more devrooms were accepted and Real Time Communication devroom has half a day available on the afternoon of February 5, 2023. The RTC Devroom call for presentations is open, more details at; - https://lists.fosdem.org/pipermail/fosdem/2022q4/003479.html Check also the other accepted … [View More]

1 0

Call drops after 1 minute
by Christian B Wiik 07 Dec '22

07 Dec '22

Greetings! I have a CentOS setup in AWS where all my calls are dropped after about a minute or so. I realize this typically is a NAT problem, but I can't see where my error is. Sound is fine both ways. Kamailio is set with WITH_NAT and I use rtpproxy like this: OPTIONS="-l 10.1.2.10 -s udp:127.0.0.1:7722 -d INFO:LOG_LOCAL5 -m 35010 -M 35110 -A 54.171.168.48" (10.1.2.10 is the local IP for CentOS) Tested with MicroSIP and Linphone and tried numerous configurations. It seems the receiving … [View More]

2 4

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