- sr-users - kamailio.org

LCR GW
by Antoine DEBARRE 20 May '22

20 May '22

Hi, Is there a way to specify an outbound proxy for just a few lcr gateways added in table lcr_gw ? Thanks in advance ! Antoine

2 6

Path MTU issues over UDP/IPv6
by Rick van Rein 20 May '22

20 May '22

Hello, IPv6 routers never fragment packets. Rather, they drop a packet that is too large for a (local) MTU and send back ICMPv6 "Packet Too Big". This seems to cause loss of larger SIP messages when an ISP tunnels their IPv6 at the expense of the MTU. The pmtu_discovery flag sets Don't Fragment in IPv4 traffic; in IPv6 this is an implied property. Does Kamailio learn a lower MTU from any "Packet Too Big" for IPv6 even if pmtu_discovery is not set? Future resends can then be fragemented appropriately. The udp_mtu setting diverts to another protocol, but that would be a setting as low as the worst peer, impacting all. It would be a weird struggle with a telco serving many. PMTU would be better to rely on, but how does it work in Kamailio? Details on https://www.rfc-editor.org/rfc/rfc3542#section-11.3 https://stackoverflow.com/questions/38817837/how-does-mtu-retransmission-wo… Thanks, -Rick

3 4

Forwarding SIP status code to HTTP client
by Tim Anderson 19 May '22

19 May '22

Hi, I have a kamailio that is has an HTTP message server. Is it possible to send the SIP status code back in the HTTP reply? Is it possible to suspend an xhttp request while some other stuff happens and then send the reply later? The relevant bit of the config currently looks like event_route[xhttp:request]{ if($hu == "/sms"){ $uac_req(method)="MESSAGE"; $uac_req(ruri)="sip:1234@example.com"; $uac_req(furi)="sip:4567@example.com"; $uac_req(turi)="sip:1234@example.com"; $uac_req(body)=$rb; uac_req_send(); xhttp_reply("200", "OK", "text/plain", "Sent") } } Regards, Tim

2 1

Kamailio Stop Responding Randomly
by M Arqum CH 19 May '22

19 May '22

Kamailio first gives timeout on ctl unix socket as I am exporting data using prometheus exporter, after a few minutes it stops responding to any sip request on default/production udp port binded with multiple IP addresses for sip traffic. The other listing port which is used by keepalived check script for bing-pong keeps responding to option messages. Its very random behaviour occurs after a few days or after a few months, the system having max load 350 concurrent calls with load average 200-300. I am attaching core dump which is collected before restarting the process. Please let me know if more information is required. version: kamailio 5.4.1 (x86_64/linux) 2ca223 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: 2ca223 Thankyou in advance. -- Regards M Arqum

2 4

Relay wss to Asterisk
by Michal Hajek 18 May '22

18 May '22

Hello, can i configure kamailio for relay wss to asterisk/pjsip? WebRTC client ( chrome ) --> WSS -> Kamailio --> WSS -> Asterisk with pjsip Asterisk accept wss://ip_address:wss_port/ws Thanks Michal Hajek

2 3

Split audio and video into different calls
by Rüdiger, Christoph 18 May '22

18 May '22

Hi everyone, we are running a call center with really good to use hardphones and audio only up to this point. Because of changing regulation, we soon have to deal with video calls as well, but only for a fraction of the calls (below 1%). Instead of switching everyone to clumsy softphones for the rare case of a video call, I’m exploring the ability to branch an incoming call into a pure audio call to the hardphone and optionally a pure video call to the softphone. Has anyone done this in the past and can share some experiences/ideas on 1. Can it be done purely with Kamailio and rtpengine? I don’t have a clear picture of how to do it purely with Kamailio on the SIP side, because we end up with two independent legs (to the hardphone and the softphone). Or do I need to deploy an Asterisk, Yate, freeswitch, etc. and doing it as a 3-way conference where one party gets both RTP streams (the trunk) and the other two parties only get one RTP stream (either audio or video)? 2. Was it worth the effort or a steady candidate for troubles? I’m looking forward to your thoughts, especially on question b). Have a nice weekend, Christoph --- Christoph Rüdiger Digital Operations Architect DTX OU DACH M +49 152 3828 0376 | christoph.ruediger(a)tkelevator.com<mailto:christoph.ruediger@tkelevator.com> TK Aufzüge GmbH | Münchener Str. 100c | 45145 Essen | Deutschland | www.tkelevator.com/de<http://www.tkelevator.com/de> VORSITZENDE DES AUFSICHTSRATS Inge Delobelle | GESCHÄFTSFÜHRUNG Burkhard Schlenker (Vorsitzender) | Christian Fongern | Katja Schrafft | SITZ DER GESELLSCHAFT Neuhausen a. d. F. | REGISTERGERICHT Stuttgart HRB 731152 This e-mail (including any attachments) may contain confidential and/or privileged information. Any unauthorized use or dissemination of this message in whole or in part is strictly prohibited. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail.

4 5

kamailio WebSocket not respond sometimes
by dolphin 18 May '22

18 May '22

Hello, kamailio could not respond to the question: This machine is on aws, there is no high load, there is an external ip listening to the WebSocket 443 port, and sometimes there are some unknown detection signals "SSTP_DUPLEX_POST" that will cause port 443 to fail to respond. Need to restart kamailio Then, it stopped responding again after about a month. Attach the detailed log details: root@sip1-aws:~# /home/pkg/kamailio/sbin/kamailio -V version: kamailio 5.3.9 (x86_64/linux) a5fd0a 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 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: a5fd0a compiled on 22:31:18 Mar 31 2022 with gcc 5.4.0 Thanks.

2 2

RabbitMQ hangs if connection lost
by Avremy Cohen 17 May '22

17 May '22

Hi When I Publish to RabbitMQ and the connection is down, the server just hangs and there is no timeout. I am using KEMI with python3 and have tried different timeout functions to circumvent the hanging but it doesn't seem to work 1. Is there a way to tell if RabbitMQ is connected? 2. using python is there a way to timeout a KSR function? Thanks guys!

1 0

Kamailio Crashed
by M Arqum CH 17 May '22

17 May '22

Dear Team, Kamailio instance got crashed, I found this error in logs. Please give advice on how I can avoid this in future. *kernel: [52641555.303165] kamailio[123814]: segfault at 30 ip 00007f42f70db770 sp 00007ffd5d95a9f0 error 4 in dialog.so[7f42f7033000+c9000]* version: kamailio 5.4.1 (x86_64/linux) 2ca223 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: 2ca223 compiled on 12:51:24 Sep 21 2020 with gcc 6.3.0 Thank you in advance. Regards M Arqum

2 2

Failing Audio stream on Kamailio+webrtc with integration to asterisk server
by Kelvin Ezenwaka 16 May '22

16 May '22

Summary: We have a Kamailio server as our sip proxy server, sip firewall with WebSocket and RTP engine configured on it (the Kamailio Server). But we experience one way audio, no audio, hang up after 30s, when we try making calls between internal extensions (eg extension 100 to call extension 105) and external calls (eg extension 100 to call mobile number 09056925668) as well. The call flow is as: Webrtc client<------->Kamailio1+rtpengine<-----Asterisk---->Kamailio2<-------->Telco Provider The asterisk communication between all three boxes is via local IP (All ports open between them). The Kamailio 1 box where we have our sip registration cache, has rtp ports and wss port open on the internet. Asterisk 18.9.0 Kamailio 5.5.3 + RTPengine 10.4.0.0 Debian 11 bullseye Kindly see attached below a diagram depicting the VoIP network flow and also attached are logs files for the webrtc client and server side. Ezenwaka Kelvin Arinze VOIP Engineer Tel: (+234) 9056925668 DISCLAIMER: The message and its attachments are for designated recipient(s) only and may contain privileged, proprietary and private information. If you have received it in error, kindly delete it and notify the sender immediately. PressOne accepts no liability for any loss or damage resulting directly and indirectly from the transmission of this e-mail message.

2 1

Question on pike_check_ip(ipaddr)
by Joel Serrano 13 May '22

13 May '22

Hello, One of our customers has lots of extensions that register to our platform using all the same IP. Sometimes they get caught in our pike velocity rules but if we increase the values to accommodate this client then all the others could abuse the system. I was wondering if pike_check_ip(ipaddr) needs strictly an IP as parameter or can it be a string? I was thinking of using pike instead of by $si by something like $fU-$si but I don't know if this would work? I need to either handle separately different extensions from the same IP or a way to adjust the pike config values just for one specific IP... I'm not sure either of these is possible with pike? My alternative is just use table and mimic the functionality myself which I don't think is too complicated, but I'd love to know if I'm missing a fast-path here... Thanks! Joel.

2 1

Accept IP/Domain Register
by Social Boh 12 May '22

12 May '22

Hello, maybe is a very basic question; How Kamailio can accept any kind of register, over IP or domains. Example, accept authenticate REGISTER from ip 1.2.3.4 or sip.domain.org or sip1.domain.org, domains associated with ip 1.2.3.4 Thank you in advance. Regards -- --- I'm SoCIaL, MayBe

3 5

Info: converting dokuwiki content to markdown files
by Daniel-Constantin Mierla 12 May '22

12 May '22

Hello, it was discussed a couple of times during the past Kamailio development meetings and several days ago the works started to convert the Kamailio Wiki content to markdown format and host the files on Kamailio github.com organisation. The Dokuwiki engine has served us very well during more than a decade and a half, but open editing had to be disabled many years ago due to bad actors pushing inappropriate content. The contributors had to make a dedicated account on our portal only for Wiki editing. More recently we had add another layer of protection requiring to grant manually edit permissions to newly created wiki accounts because bots started to work around CAPTCHA and other security extensions, posting again inappropriate content. All these added to operational overhead, but also made it difficult for new people to contribute, specially for small editing to fix typos or add usage examples. Thanks to Kenneth Stowe, who undertook the first big effort of converting the Dowkuwiki files to markdown format, we are now in the position of moving further with the plans of using github for hosting the content of the wiki and enable easier contributions via pull requests. The history of changes done via Dokuwiki show up now as git commits. The github repository for the wiki content is available at: * https://github.com/kamailio/kamailio-wiki It is still work in progress, therefore we ask for the help of community to speed up the conversion, among the tasks that need to be done: * convert relative links between wiki pages – the conversion tools used relative paths without file extensions, like: [Install Kamailio v4.4.x From GIT](/install/4.4.x/git) They have to be converted to relative path with .md extension in order to be able to browse directly :n the github.com portal — practically the leading / has to be removed and .md added at the end, like: [Install Kamailio v4.4.x From GIT](install/4.4.x/git.md) * some section heading markers were not detected/converted, onee may notice many equal signs (=) around a section name, it has to be replaced with the appropriate markdown format based on hash signs (#). For example: ======= Install And Maintain Kamailio v4.4.x From GIT ======= Should be converted to: # Install And Maintain Kamailio v4.4.x From GIT * some Dokuwiki paragraphs used special formatting based on plugins, for example the notes, warnings, … had special colors. The common markdown format does not specify a syntax to color the text, the propose solution is to use emoji at the start of the paragraph to signal its special purpose. For example, the Dokuwiki content: <color blue>//IMPORTANT: Content for older releases than 3.2.0 is available at the **Old Wiki Site**://</color> Has to be transformed to: :fire:*IMPORTANT: Content for older releases than 3.2.0 is available at the **Old Wiki Site**:* You are welcome to propose a better syntax for this kind of transformation. * review config examples and evaluate what improvements can be done (e.g., in terms of formatting and syntax highlighting) Any of these changes do not require any C programming knowledge, nor much Kamailio config knowledge. Can be your first contribution to the project and it will be very appreciated. It can also help you learn more about Kamailio, because you may discover documentation that you were not aware of. A very important decision is how to present the wiki markdown content on kamailio.org website. Besides being able to see it on github repository, we want to process the markdown pages somehow and make them available in html format on kamailio.org website for easier navigation and better indexing (e.g., with tables of content for large pages). If you are aware of a suitable cli or web app that can convert markdown to html and generate table of content, let us know. Any questions and suggestions should be addressed to sr-users(a)lists.kamailio.org mailing list. Looking forward to your contributions on this community effort! Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online * https://www.asipto.com/sw/kamailio-advanced-training-online/

5 15

unable to get local issuer certificate
by Володимир Іванець 12 May '22

12 May '22

Hello all! I'm trying to establish TLS connection but getting the following error. Can anyone point me in the right direction, please? tls_dump_verification_failure(): verification failure: unable to get local issuer certificate Kamailio version is 5.5.1. System runs on CentOS 7. At the moment tls.cfg configuration file looks like this: [server:default] method = TLSv1+ require_certificate = no verify_certificate = no private_key = /var/kamailio/certificates/default/server/key.pem certificate = /var/kamailio/certificates/default/server/cert.pem ca_list = /var/kamailio/certificates/default/CA/cert.pem [client:default] method = TLSv1+ require_certificate = no verify_certificate = no private_key = /var/kamailio/certificates/default/server/key.pem certificate = /var/kamailio/certificates/default/server/cert.pem ca_list = /var/kamailio/certificates/default/CA/cert.pem ca_list file contains root and intermediate certificates. Certificate was issued by Sectigo. It can be successfully verified with OpenSSL tool: # openssl verify -verbose -CAfile /var/kamailio/certificates/default/CA/cert.pem /var/kamailio/certificates/default/server/cert.pem /var/kamailio/certificates/default/server/cert.pem: OK Here is a fragment of Kamailio debug output: May 5 06:51:03 server kamailio[3834]: 5(3844) DEBUG: <core> [core/tcp_main.c:1993]: tcp_send(): no open tcp connection found, opening new one May 5 06:51:03 server kamailio[3834]: 5(3844) DEBUG: <core> [core/ip_addr.c:577]: print_ip(): tcpconn_new: new tcp connection: 52.114.132.46 May 5 06:51:03 server kamailio[3834]: 5(3844) DEBUG: <core> [core/tcp_main.c:1175]: tcpconn_new(): on port 5061, type 3, socket -1 May 5 06:51:03 server kamailio[3834]: 5(3844) DEBUG: <core> [core/tcp_main.c:1498]: tcpconn_add(): hashes: 3678:784:0, 230 May 5 06:51:03 server kamailio[3834]: 5(3844) DEBUG: tls [tls_server.c:244]: tls_complete_init(): completing tls connection initialization May 5 06:51:03 server kamailio[3834]: 5(3844) DEBUG: tls [tls_server.c:207]: tls_get_connect_server_name(): xavp with outbound server name not found May 5 06:51:03 server kamailio[3834]: 5(3844) DEBUG: tls [tls_server.c:180]: tls_get_connect_server_id(): xavp with outbound server id not found May 5 06:51:03 server kamailio[3834]: 5(3844) DEBUG: tls [tls_server.c:187]: tls_get_connect_server_id(): outbound server id not set May 5 06:51:03 server kamailio[3834]: 5(3844) DEBUG: tls [tls_server.c:274]: tls_complete_init(): Using initial TLS domain TLSc<default> (dom 0x7f1cca178720 ctx 0x7f1cca29dbd0 sn []) May 5 06:51:03 server kamailio[3834]: 5(3844) DEBUG: tls [tls_domain.c:1208]: tls_lookup_private_key(): Private key lookup for SSL_CTX-0x7f1cca29dbd0: (nil) May 5 06:51:03 server kamailio[3834]: 5(3844) DEBUG: tls [tls_domain.c:778]: sr_ssl_ctx_info_callback(): SSL handshake started May 5 06:51:03 server kamailio[3834]: 5(3844) DEBUG: <core> [core/tcp_main.c:2888]: tcpconn_1st_send(): pending write on new connection 0x7f1cca41fe18 sock 11 (-1/517 bytes written) (err: 11 - Resource temporarily unavailable) May 5 06:51:03 server kamailio[3834]: 5(3844) DEBUG: tm [uac.c:686]: send_prepared_request_impl(): uac: 0x7f1cca40bd50 branch: 0 to 52.114.132.46:5061 May 5 06:51:03 server kamailio[3834]: 5(3844) DEBUG: <core> [core/onsend.c:50]: run_onsend(): required parameters are not available - ignoring May 5 06:51:03 server kamailio[3834]: 14(3853) DEBUG: <core> [core/tcp_main.c:3793]: handle_ser_child(): read response= 7f1cca41fe18, 5, fd 26 from 5 (3844) May 5 06:51:03 server kamailio[3834]: 14(3853) DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): DBG: io_watch_add(0xae4760, 26, 2, 0x7f1cca41fe18), fd_no=20 May 5 06:51:03 server kamailio[3834]: 14(3853) DEBUG: <core> [core/io_wait.h:782]: io_watch_chg(): DBG: io_watch_chg (0xae4760, 26, 0x1, 0xffffffff) fd_no=21 called May 5 06:51:03 server kamailio[3834]: 14(3853) DEBUG: <core> [core/io_wait.h:782]: io_watch_chg(): DBG: io_watch_chg (0xae4760, 24, 0x1, 0xffffffff) fd_no=21 called May 5 06:51:03 server kamailio[3834]: 14(3853) DEBUG: <core> [core/io_wait.h:600]: io_watch_del(): DBG: io_watch_del (0xae4760, 26, -1, 0x0) fd_no=21 called May 5 06:51:03 server kamailio[3834]: 14(3853) DEBUG: <core> [core/tcp_main.c:4457]: handle_tcpconn_ev(): sending to child, events 1 May 5 06:51:03 server kamailio[3834]: 14(3853) DEBUG: <core> [core/tcp_main.c:4130]: send2child(): selected tcp worker idx:3 proc:13 pid:3852 for activity on [tls:X.X.X.X:5062], 0x7f1cca41fe18 May 5 06:51:03 server kamailio[3834]: 13(3852) DEBUG: <core> [core/tcp_read.c:1737]: handle_io(): received n=8 con=0x7f1cca41fe18, fd=6 May 5 06:51:03 server kamailio[3834]: 13(3852) DEBUG: tls [tls_domain.c:1208]: tls_lookup_private_key(): Private key lookup for SSL_CTX-0x7f1cca29dbd0: (nil) May 5 06:51:03 server kamailio[3834]: 14(3853) DEBUG: <core> [core/io_wait.h:782]: io_watch_chg(): DBG: io_watch_chg (0xae4760, 25, 0x1, 0xffffffff) fd_no=20 called May 5 06:51:03 server kamailio[3834]: 13(3852) DEBUG: <core> [core/tcp_main.c:2706]: tcpconn_do_send(): sending... May 5 06:51:03 server kamailio[3834]: 13(3852) DEBUG: <core> [core/tcp_main.c:2739]: tcpconn_do_send(): after real write: c= 0x7f1cca41fe18 n=5103 fd=6 May 5 06:51:03 server kamailio[3834]: 13(3852) DEBUG: <core> [core/tcp_main.c:2740]: tcpconn_do_send(): buf= May 5 06:51:03 server kamailio[3834]: ? May 5 06:51:03 server kamailio[3834]: 13(3852) DEBUG: <core> [core/io_wait.h:375]: io_watch_add(): DBG: io_watch_add(0xb50560, 6, 2, 0x7f1cca41fe18), fd_no=1 May 5 06:51:04 server kamailio[3834]: 13(3852) DEBUG: tls [tls_domain.c:1208]: tls_lookup_private_key(): Private key lookup for SSL_CTX-0x7f1cca29dbd0: (nil) May 5 06:51:04 server kamailio[3834]: 13(3852) DEBUG: tls [tls_domain.c:790]: sr_ssl_ctx_info_callback(): SSL handshake done May 5 06:51:04 server kamailio[3834]: 13(3852) DEBUG: tls [tls_domain.c:794]: sr_ssl_ctx_info_callback(): SSL disable renegotiation May 5 06:51:04 server kamailio[3834]: 13(3852) DEBUG: tls [tls_server.c:542]: tls_connect(): TLS connect successful May 5 06:51:04 server kamailio[3834]: 13(3852) DEBUG: tls [tls_server.c:549]: tls_connect(): tls_connect: new connection to 52.114.132.46:5061 using TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384 256 May 5 06:51:04 server kamailio[3834]: 13(3852) DEBUG: tls [tls_server.c:552]: tls_connect(): tls_connect: sending socket: X.X.X.X:0 May 5 06:51:04 server kamailio[3834]: 13(3852) DEBUG: tls [tls_server.c:418]: tls_dump_cert_info(): tls_connect: server certificate subject:/CN=sip.pstnhub.microsoft.com May 5 06:51:04 server kamailio[3834]: 13(3852) DEBUG: tls [tls_server.c:422]: tls_dump_cert_info(): tls_connect: server certificate issuer:/C=US/O=Microsoft Corporation/CN=Microsoft RSA TLS CA 01 May 5 06:51:04 server kamailio[3834]: 13(3852) DEBUG: tls [tls_server.c:558]: tls_connect(): WARNING: tls_connect: server certificate verification failed!!! May 5 06:51:04 server kamailio[3834]: 13(3852) DEBUG: tls [tls_dump_vf.c:104]: tls_dump_verification_failure(): verification failure: unable to get local issuer certificate May 5 06:51:04 server kamailio[3834]: 13(3852) DEBUG: <core> [core/tcp_main.c:2706]: tcpconn_do_send(): sending... May 5 06:51:04 server kamailio[3834]: 13(3852) DEBUG: <core> [core/tcp_main.c:2739]: tcpconn_do_send(): after real write: c= 0x7f1cca41fe18 n=513 fd=6 May 5 06:51:04 server kamailio[3834]: 13(3852) DEBUG: <core> [core/tcp_main.c:2740]: tcpconn_do_send(): buf= Thank you very much!

2 4

Using TLS in Kamailio behind AWS NLB
by Aditya Uppuluri 12 May '22

12 May '22

Hello Team, I want to understand if there is any recommendation on installing kamailio behind AWS NLB. I want to enable TLS at the NLB (using the certificate generated via Aws Certificate Manager) but still use the TLS module functionalities in kamailio (like listening on 443 port/updating the correct via header and all). Because NLB by default doesn't understand sips/TLS, I need a way to differentiate whether the request came on a secure line or on a plain UDP line. How do I configure this? Do I need to generate new certificates for kamailio ? Thanks in advance Regards, Aditya

1 0

Detect RTP stream end (Kamailio + rtpengine)
by Rawad Kassir 11 May '22

11 May '22

Hello, I am trying to play early media purely relaying on kamailio and i have accomplished that using the below: rtpengine_manage(); append_to_reply("Content-Type: application/sdp\r\n"); $var(body)= $(rb{re.subst,/(IP4.).*/\127.0.0.1/g}); set_reply_body($var(body), "application/sdp"); send_reply("100","Trying"); send_reply("183","Session In Progress"); play_media("totag=$ft file=/home/rawad/test.wav"); My problem is that once the RTP stream starts the call is kept open so my question is is there a way for kamailio to detect the end of rtp stream so that i can send BYE or can kamailio do that automatically.

1 0

Proxy for ACK
by Rick van Rein 09 May '22

09 May '22

Hello, RFC 3261 gives (by way of example) an ACK that is sent directly to a remote phone via its Contact: header address. Is this the _only_ way of doing this, or may ACK also be passed through a SIP proxy? I found that my Kamailio setup does not forward ACK, and I wonder why; whether that is a common refusal, or my fault in modifying the proxy script. I am working on an IPv4-only to IPv6-only translation proxy, and would like to leave the DNS-related work to a more advanced SIP proxy. The translator is supposed to be small/simple, so it can be integrated into home routers. I would like to avoid DNS resolution (and its delays) for Contact: URIs. Proxy script, https://gitlab.com/arpa2/mkroot/-/blob/master/contrib/sip-trunk/etc/kamaili… SIPproxy64 translator, https://gitlab.com/0cpm/sipproxy64 Thanks, -Rick

2 4

dns_query container no found
by David Villasmil 06 May '22

06 May '22

Hello guys, I'm trying to use: if(dns_query("$du", "xyz")) And all I get is dns_update_pv(): container not found: xyz Any ideas? I'm not really sure what that means. I know there's supposed to be a $dns(xyz) but it looks like it's not there? I'm using 5.0 BTW. Thanks all & Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 2

calling failure_route
by David Villasmil 06 May '22

06 May '22

Hello guys, Is it possible to call a failure_route like a normal route? i.e.: { t_on_failure("myroute"); } ... route("myroute"); failure_route[myroute] { ... } Let me explain: I have this scenario where a DNS name may get deleted and a dns resolution will fail. There's no pinging to that gateway so i need to: - skip that gateway when dispatching to the setid - detect whether the domain is up and available And failover to the next gateway. I don't know of any other way so on the DISPATCH route, I'm doing: route[DISPATCH] { # round robin dispatching on gateways group '1' if(!ds_select_dst("1", "4")) { send_reply("404", "No destination"); exit; } xlog("L_DBG", "--- SCRIPT: going to <$ru> via <$du>\n"); if(dns_query("$du", "xyz")) { t_on_failure("RTF_DISPATCH"); route(RELAY); } else { route(RTF_DISPATCH); } exit; } to try to resolve and if it fails, it will just go to the failover route. makes sense? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

3 4

BYE is being sent using the Dialog ID (did)
by mack＠dopensource.com 06 May '22

06 May '22

I configured the dialog module to match routing based on SIP elements versus the (Dialog ID) did. It looks like it’s using the callid SIP element, but it’s still looking it up using the dialog module. I was hoping it would route on the RURI of the BYE. But, it looks like it’s using the dialog lookup table, which has the wrong RURI because that was the original server we sent the request to. How can I get Kamailio to route based on the RURI within the BYE. May 5 06:28:13 sbc-atlanta /usr/sbin/kamailio[27066]: DEBUG: rr [rr_cb.c:94]: run_rr_callbacks(): callback id 0 entered with <lr> May 5 06:28:13 sbc-atlanta /usr/sbin/kamailio[27066]: DEBUG: dialog [dlg_hash.c:887]: internal_get_dlg(): ref dlg 0x7f6d97faf200 with 1 -> 3 May 5 06:28:13 sbc-atlanta /usr/sbin/kamailio[27066]: DEBUG: dialog [dlg_hash.c:891]: internal_get_dlg(): dialog callid='oeIojv5OA59S9FYCCu7BcQ..' found on entry 777, dir=2 to-tag='sip+3+f36a00a5+44b60208' May 5 06:28:13 sbc-atlanta /usr/sbin/kamailio[27066]: DEBUG: dialog [dlg_profile.c:536]: set_current_dialog(): setting current dialog [777:1428] May 5 06:28:13 sbc-atlanta /usr/sbin/kamailio[27066]: DEBUG: dialog [dlg_hash.c:1290]: next_state_dlg(): dialog 0x7f6d97faf200 changed from state 4 to state 5, due event 7 (ref 3) May 5 06:28:13 sbc-atlanta /usr/sbin/kamailio[27066]: DEBUG: dialog [dlg_hash.c:1071]: dlg_ref_helper(): ref op on 0x7f6d97faf200 with 1 from dlg_handlers.c:1441 May 5 06:28:13 sbc-atlanta /usr/sbin/kamailio[27066]: DEBUG: dialog [dlg_hash.c:1075]: dlg_ref_helper(): ref dlg 0x7f6d97faf200 with 1 -> 4 May 5 06:28:13 sbc-atlanta /usr/sbin/kamailio[27066]: DEBUG: dialog [dlg_handlers.c:1452]: dlg_onroute(): BYE successfully processed May 5 06:28:13 sbc-atlanta /usr/sbin/kamailio[27066]: DEBUG: dialog [dlg_hash.c:1091]: dlg_unref_helper(): unref op on 0x7f6d97faf200 with 2 from dlg_handlers.c:1476 May 5 06:28:13 sbc-atlanta /usr/sbin/kamailio[27066]: DEBUG: dialog [dlg_hash.c:1095]: dlg_unref_helper(): unref dlg 0x7f6d97faf200 with 2 -> 2 May 5 06:28:13 sbc-atlanta /usr/sbin/kamailio[27066]: DEBUG: dialog [dlg_hash.c:1091]: dlg_unref_helper(): unref op on 0x7f6d97faf200 with 1 from dlg_hash.c:1109 May 5 06:28:13 sbc-atlanta /usr/sbin/kamailio[27066]: DEBUG: dialog [dlg_hash.c:1095]: dlg_unref_helper(): unref dlg 0x7f6d97faf200 with 1 -> 1 Thanks in advance

2 1

Tips on picking random element from a list
by Joel Serrano 05 May '22

05 May '22

Hi Everyone, I have to implement a flow where outbound calls get their caller-id set with a random number from a pool. I've been looking around and, as most of the time, there are tons of ways to implement something like this... This is a simple implementation, the number pool is fixed and will not change (so I could have it hard-coded in the config if required). My initial approach was: 1- Try to keep it simple, with no dependencies, and all done in the config script. 2- If #1 is "ugly", then I'd probably go with some inline code using python/lua/etc 3- If #2 is "ugly", then I'd go with having the info in a DB and just run a query I think #2 and #3 might be overkill for something so "simple" but I haven't had to work too much with randomness in Kamailio, so any tips/suggestions on where to store the number list and how to pick one randomly would be awesome! Thanks!! Joel.

5 7

failover on dns resolve error
by David Villasmil 05 May '22

05 May '22

Hello guys, I have a scenario where a dns name I've added as a dispatcher endpoint may get removed completely, i.e.: dns resolution fails completely. How would you recommend implementing failover in this case? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

1 0

iterating over htable with lua
by David Villasmil 05 May '22

05 May '22

Hello guys, I'm trying to iterate over an htable in lus, this is what i have: =================================== loadmodule "app_lua.so" modparam("app_lua", "load", "/etc/kamailio/myscript.lua") modparam("htable", "htable", "mydata=>size=16;autoexpire=0;dbtable=mydata;dbmode=0;") route { lua_run("match_mydata"); } ... function match_mydata() KSR.htable.sht_iterator_start("i1", "mydata") while KSR.htable.sht_iterator_next("i1") do KSR.log("err","WHILE: iterating on: " .. KSR.htable.sht_get("mydata", "i1")) end KSR.htable.sht_iterator_end("i1"); end But i keep getting: 0(1255) DEBUG: app_lua [app_lua_api.c:666]: app_lua_run_ex(): executing Lua function: [[match_mydata]] 0(1255) DEBUG: app_lua [app_lua_api.c:668]: app_lua_run_ex(): lua top index is: 12 0(1255) ERROR: app_lua [app_lua_api.c:719]: app_lua_run_ex(): error from Lua: /etc/kamailio/myscript.lua:11: attempt to call field 'sht_iterator_start' (a nil value) 0(1255) ERROR: app_lua [app_lua_api.c:734]: app_lua_run_ex(): error executing: match_mydata (err: 2) This almost exact same thing works on the cfg: sht_iterator_start("i1", "msrn"); while(sht_iterator_next("i1")) { xlog("data: $shtitkey(i1)\n"); } sht_iterator_end("i1"); Anyone know what I could be doing wrong? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

1 1

Development is open for future release of v5.7.x series
by Daniel-Constantin Mierla 05 May '22

05 May '22

Hello, the branch 5.6 was created, therefore the master branch is open for adding new features, to be part of future release series v5.7.x (or whatever version is decided for next series). Any bug fix committed to master that applies to 5.6.x or older stable branches should be backported as usual with "git cherry-pick -x ..." to appropriate branches like 5.6 or 5.5. Expect that v5.6.0 will be released in a few weeks from now. Based on the workflow used during the past years, the next future release v5.7.0 should be out after another 6-10 months of development, plus 1-2 months of testing, so sometime by end of 2022 or in the first part of 2023. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 0

Branch 5.6 has been created
by Daniel-Constantin Mierla 05 May '22

05 May '22

Hello, the branch 5.6 has been created, to be used for releasing v5.6.x series. To check out this branch, the following commands can be used: git clone https://github.com/kamailio/kamailio kamailio-5.6 cd kamailio-5.6 git checkout -b 5.6 origin/5.6 Pushing commits in this branch: git push origin 5.6:5.6 Note that 5.6 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. As usual, if there is a bug fixed, commit and push first to master branch and then cherry pick to 5.5 branch: git cherry-pick -x COMMITID In few weeks, the first release from branch 5.6 will be out, respectively Kamailio v5.6.0. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - Online * https://www.asipto.com/sw/kamailio-advanced-training-online/

1 0

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