sr-users

sr-users@lists.kamailio.org

42 participants
37519 discussions

Kamailio modules that can be used in Lua
by Leonid Fainshtein 08 Feb '19

08 Feb '19

Hello, I am checking a possibility to replace the traditional cfg script with a Lua script. In the app_lua module documentation there is a relatively short list of modules that can be registered to Lua. The modules nathelper, rtpproxy, topoh and many others don't appear in the list. Does it mean that it is not possible to use that modules in Lua? Best regards, Leonid Fainshtein

3 2

Waiting for calls
by Mark Hall 08 Feb '19

08 Feb '19

Hi, I am using Kamailio as a gateway for inbound calls to a group of Asterisk servers. One particular call scenario involves matching pairs of calls. Originally I was just sending the calls through to Asterisk for processing (including the 'matching up'), but there is a further requirement that the first received call must not be answered until its matching call arrives - and this is a little awkward in Asterisk, especially if there will be many calls. I thought of t_suspend/t_continue functionality in Kamailio. I have implemented this: CallA arrives. Send 180-ringing Use ds_select_dst() to choose an Asterisk to handle the paired calls Store destination and other data in an htable so that I can match the call later. Invoke t_suspend() for CallA. What I have implemented when the matching call arrives is this: CallB arrives (and some logic matches it to the suspended CallA). Invoke t_continue('id','label','CONTINUE_CALL'); so that CallA is now released and the route ends in t_relay() to send it on to Asterisk. Set $du on CallB to match the destination, then t_relay() this call to send it on to the same Asterisk. The solution almost works, but there is a problem. The t_relay() for CallA is fine, and the call is forwarded. When the script runs the t_relay() for CallB, I get this logged: ERROR: tm [t_fwd.c:1728]: t_forward_nonack(): no branches for forwarding ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error reply used: I'm terribly sorry, server error occurred (6/SL) AND after each call I notice an extra transaction stuck in Kamailio (when I use kamctl rpc tm.list). Can anyone point out where my Kamailio/SIP understanding has let me down? Many Thanks, Mark Hall

2 2

Re: [SR-Users] TLS challenge
by Gertjan Wolzak 07 Feb '19

07 Feb '19

Hello Kamailions, Julien, thank you for the help, I have added the letsencrypt ca certificate to the ca list, still no dice. So, still got lots of questions, but after my last booboo going to do some more research and testing. When I have no more hair left will get back to the list. Thanks for now. Rgds, Gertjan Wolzak

2 1

ERROR : EAGAIN and write queue full or failed for tcp Connection
by YASIN CANER 07 Feb '19

07 Feb '19

Hello, Kamailio gave this error that couldnt bind tcp connection other side. Thanks Yasin CANER Kamailio IPv6:TCP: -----> IPv6:TCP Kamailio -----> X ERROR XXXX IPv6:TCP Kamailio IPv6::C IPv6::8 IPv6::5 LOGS: 7(15781) DEBUG: <core> [core/msg_translator.c:2937]: create_via_hf(): id added: <;i=1>, rcv proto=2 7(15781) DEBUG: <core> [core/msg_translator.c:162]: check_via_address(): (FD61:C23C:B3B6:0:0:0:0:C, [FD61:C23C:B3B6:0:0:0:0:C], 0) 7(15781) DEBUG: <core> [core/tcp_main.c:1977]: tcp_send(): no open tcp connection found, opening new one 7(15781) DEBUG: <core> [core/ip_addr.c:242]: print_ip(): tcpconn_new: new tcp connection: fd61:c23c:b3b6:0:0:0:0:5 7(15781) DEBUG: <core> [core/tcp_main.c:1229]: tcpconn_new(): on port 5060, type 2 7(15781) DEBUG: <core> [core/tcp_main.c:1539]: tcpconn_add(): hashes: 507:2382:0, 2 7(15781) DEBUG: <core> [core/tcp_main.c:2873]: tcpconn_1st_send(): pending write on new connection 0x7fd15b5e7c98 (-1/1483 bytes written) (err: 11 - Resource temporarily unavailable) 7(15781) ERROR: <core> [core/tcp_main.c:2891]: tcpconn_1st_send(): [FD61:C23C:B3B6:0:0:0:0:5]:5060: EAGAIN and write queue full or failed for 0x7fd15b5e7c98 7(15781) DEBUG: <core> [core/tcp_main.c:3153]: tcpconn_chld_put(): destroying connection 0x7fd15b5e7c98 (2, -1) flags 0060 7(15781) ERROR: tm [../../core/forward.h:251]: msg_send_buffer(): tcp_send failed 7(15781) DEBUG: tm [t_fwd.c:1549]: t_send_branch(): send to FD61:C23C:B3B6:0:0:0:0:5:5060 (2) failed 7(15781) WARNING: tm [t_fwd.c:1567]: t_send_branch(): sending request on branch 0 failed CONF: dns_try_ipv6=yes dns_retr_time=1 dns_retr_no=1 dns_cache_flags=4 tcp_source_ipv6 = [fd61:c23c:b3b6::8] tcp_async=yes tcp_rd_buf_size=65536 tcp_wq_blk_size=3000 listen=tcp:[fd61:c23c:b3b6::8]:5060 tcp_connection_lifetime=3605 listen=tcp:[fd61:c23c:b3b6::8]:5060 ..... route[]{ remove_hf("Route"); #loose_route(); if (!is_method("INVITE")) return; $du="sip: mykamailio1.test:5060;transport=tcp"; if(!t_newtran()){ xlog("L_WARN"," Couldnt create new transaction \r\n"); sl_send_reply("503", "Service not available"); exit; } if(!t_relay()){ send_reply("503", "Service not available"); exit; } exit; }

4 7

Keep requests order
by Duarte Rocha 07 Feb '19

07 Feb '19

Greetings, I'm having some problems with keeping the order of the messages in Kamailio. In some cases i'm receiving an ACK for the first INVITE and immediately after that a RE-INVITE is sent by the client. What is happening is that the the ACK took double the time of the RE-INVITE to process and as a consequence, the RE-INVITE was relayed before the ACK. I have two questions : 1 - Is there a way to keep the order of the messages in a dialog, and if so, what are the downsides to it? 2 - The machine wasn't in a load state (only one concurrent call) and the ACK and the RE-INVITE should go roughly through the same processing methods and should take took the same time to be be relayed. What can be the reason for this? Best Regards, Duarte Rocha

4 7

Kamailio with RTPengine, allow source port of RTP to change during a call
by Laurent Schweizer 06 Feb '19

06 Feb '19

Hello, I'm using the RTPengine with Kamailio and I have a question for a specific case. I have some customer that are changing the source port of the RTP stream during the call ( no re-invite) I think it's more a NAT issue that a user agent issue... I see in the doc that I can handle this case with the "media handover" but in that case the rtpengine will allow a change of the source port but also of the source IP. Any possibility to allow only a change of the source port so source IP must still be the same ? Thanks BR Laurent

2 1

Kamailio failure routing to SRV Record
by Jesse Strahn 05 Feb '19

05 Feb '19

Hi all, I am trying to route requests from Kamailio to a private SRV record in AWS Route 53. If I setup the record as an A record and put the 3 destination sip server IPs in the record, Kamailio routes perfectly round-robinning between the 3 servers. However, If I switch my dispatcher.list over to the SRV record, the calls do not route and I get a 404 No Destination in my pcap. When I perform a `dig _sip._udp.pool.sip.servers` from the Kamailio server, it properly returns the hostnames of the 3 sip servers that the SRV record points to. I'm not sure if something in the Kamailio routing has to be changed to accommodate SRV record routing rather than A record? I have scoured the internet and can't really find much of anything. Would greatly appreciate any guidance. Thanks, Jesse

3 3

Error UAS
by Nicolas Breuer 05 Feb '19

05 Feb '19

Hello, How can we avoid these errors ? Feb 5 11:21:39 proxy1 /usr/sbin/kamailio[29563]: ERROR: tm [t_reply.c:1301]: t_should_relay_response(): status rewrite by UAS: stored: 408, received: 200 Thanks

2 1

TLS challenge
by Gertjan Wolzak 05 Feb '19

05 Feb '19

Hello Kamailions, Ive beent trying to configure a tls connection between kamailio servers, but looks like Im missing some knowledge. The situation: phone1 <> internet <> kamailio1 <internet> kamailio2<> internet <> phone2 The phones are yealink phones, they are connected using TLS v1.2, phone 1 registers at kamailio1 and phone2 registers at kamailio2. Both kamailio servers have an letsencrypt certificate. When the connection between the two kamailio servers is set as sip, a call from a phone1 to phone2 the singnaling is forwarded and rtp flows. When I set the connection between the two kamailio servers to tls, things go wrong.. or better said I go wrong. The kamailio log on the receiving kamailio(kamailio2) shows that things go wrong and where, but I just cant figure out how to solve it. The log shows that the tls connection will be handled by the TLS Default configuration, the CA certificate is missing, well unknown. 15(7209) DEBUG: <core> [core/ip_addr.c:229]: print_ip(): tcpconn_new: new tcp connection: 116.203.53.212 15(7209) DEBUG: <core> [core/tcp_main.c:999]: tcpconn_new(): on port 44153, type 3 15(7209) DEBUG: <core> [core/tcp_main.c:1309]: tcpconn_add(): hashes: 1805:3331:3809, 3 15(7209) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xa77de0, 32, 2, 0x7ff9596d4b10), fd_no=23 15(7209) DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xa77de0, 32, -1, 0x0) fd_no=24 called 15(7209) DEBUG: <core> [core/tcp_main.c:4196]: handle_tcpconn_ev(): sending to child, events 1 15(7209) DEBUG: <core> [core/tcp_main.c:3878]: send2child(): selected tcp worker 1 8(7202) for activity on [tls:kamailio2:5061], 0x7ff9596d4b10 8(7202) DEBUG: <core> [core/tcp_read.c:1759]: handle_io(): received n=8 con=0x7ff9596d4b10, fd=9 8(7202) DEBUG: tls [tls_server.c:199]: tls_complete_init(): completing tls connection initialization 8(7202) DEBUG: tls [tls_server.c:228]: tls_complete_init(): Using initial TLS domain TLSs<default> (dom 0x7ff959498600 ctx 0x7ff9594b6430 sn []) 8(7202) DEBUG: tls [tls_domain.c:724]: sr_ssl_ctx_info_callback(): SSL handshake started 8(7202) DEBUG: <core> [core/tcp_main.c:2460]: tcpconn_do_send(): sending... 8(7202) DEBUG: <core> [core/tcp_main.c:2494]: tcpconn_do_send(): after real write: c= 0x7ff9596d4b10 n=2637 fd=9 8(7202) DEBUG: <core> [core/tcp_main.c:2495]: tcpconn_do_send(): buf= 8(7202) DEBUG: <core> [core/io_wait.h:380]: io_watch_add(): DBG: io_watch_add(0xac78a0, 9, 2, 0x7ff9596d4b10), fd_no=1 8(7202) ERROR: tls [tls_util.h:42]: tls_err_ret(): TLS accept:error:14094418:SSL routines:ssl3_read_bytes:tlsv1 alert unknown ca 8(7202) ERROR: <core> [core/tcp_read.c:1505]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7ff9596d4b10 r: 0x7ff9596d4b90 (-1) 8(7202) DEBUG: <core> [core/io_wait.h:602]: io_watch_del(): DBG: io_watch_del (0xac78a0, 9, -1, 0x10) fd_no=2 called 8(7202) DEBUG: <core> [core/tcp_read.c:1683]: release_tcpconn(): releasing con 0x7ff9596d4b10, state -2, fd=9, id=3 (kamailio1]:44153 -> [kamailio1]:5061) 8(7202) DEBUG: <core> [core/tcp_read.c:1684]: release_tcpconn(): extra_data 0x7ff9596d2ab0 15(7209) DEBUG: <core> [core/tcp_main.c:3308]: handle_tcp_child(): reader response= 7ff9596d4b10, -2 from 1 15(7209) DEBUG: tls [tls_server.c:667]: tls_h_close(): Closing SSL connection 0x7ff9596d2ab0 I assume I have configured tls.cfg partially correct, as the phones register and can make tls calls. What I find strange is this line: 8(7202) DEBUG: <core> [core/tcp_read.c:1683]: release_tcpconn(): releasing con 0x7ff9596d4b10, state -2, fd=9, id=3 (kamailio1]:44153 -> [kamailio1]:5061) Would the "[kamailio1]:5061" be the client configuration? So, what do I need to configure within the tls.cfg file so when a tls connection is initiated from the other server it will work. I have tried adding the other server as server within the tls.cfg, which does not work as kamailio is not listening on the ip address configured. When I add the server as a client in the tls.cfg as follows, the connection is handled by the default TLS configuration. [server:default] method = TLSv1.2 verify_certificate = no require_certificate = no private_key = /etc/letsencrypt/live/kamailio.kazlow.nl/privkey.pem certificate = /etc/letsencrypt/live/kamailio.kazlow.nl/fullchain.pem #ca_list = /etc/kamailio/tls/cacert.pem #crl = /etc/kamailio/tls/crl.pem [client:kamailio1:5061] method = TLSv1.2 verify_certificate = no require_certificate = yes certificate = /etc/kamailio/tls/fullchain.pem ca_list = /etc/kamailio/tls/cacert.pem # This is the default client domain, settings # in this domain will be used for all outgoing # TLS connections that do not match any other # client domain in this configuration file. # We require that servers present valid certificate. # [client:default] method = TLSv1.2 verify_certificate = no require_certificate = no ca_list = /etc/kamailio/tls/cacert.pem I have tried forcing the socket on the sending kamailio, but that does not work. Any feedback on what I am doing wrong or where I can find information to extend my knowledge would be appreciated. Rgds, Gertjan Wolzak

2 1

How to chain proxies with Route header and loose_route()
by Ivan Ribakov 05 Feb '19

05 Feb '19

Assuming there are several proxies that have to be hopped sequentially to deliver the request and the order is determined dynamically (!), how can one achieve that behaviour in Kamailio? My understanding was that Route header is used for that - it allows to keep R-URI intact but still route the egress message elsewhere. Documentation of the loose_route() from RR module seems to confirm that. But the catch is that loose_route() will not pick up any Route header that I might add in the config via append_hf() due to the delayed lump processing (as explained in https://sourceforge.net/p/openser/bugs/277/#5f42). Thanks in advance for any help or ideas. Regards, Ivan

2 1

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