sr-users May 2022

sr-users@lists.kamailio.org

49 participants
59 discussions

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

Development for v5.6.x is frozen
by Daniel-Constantin Mierla 05 May '22

05 May '22

Hello, the formal notification that the development for the next major version 5.6.0 is now frozen. The focus has to be on testing the master branch. Also, the master branch should not get commits with new features till the branch 5.6 is created, expected to happen in 2-4 weeks, a matter of how testing goes on. Meanwhile, the commits with new features in the C code can be pushed to personal branches, new pull requests can still be done, but they will be merged after branching 5.6. Can still be done commits with documentation improvements, enhancements to related tools (e.g., kamctl, kamcmd), merging exiting pull requests at this moment, exporting missing KEMI functions and completing the functionality of the new modules added for 5.6. Once the branch 5.6 is created, new features can be pushed again to master branch as usual. From that moment, the v5.6.0 should be out very soon, time used for further testing but also preparing the release of packages. If someone is not sure if a commit brings a new feature, just make a pull request and it can be discussed there on github portal or via sr-dev mailing list. A summary of what is new in upcoming 5.6 is going to be built at: * https://www.kamailio.org/wiki/features/new-in-5.6.x Upgrade guidelines will be collected at: * https://www.kamailio.org/wiki/install/upgrade/5.5.x-to-5.6.0 Everyone is more than welcome to contribute to the above wiki pages, especially to the upgrade guidelines, to help everyone else during the migration process from v5.5.x to 5.6.x. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda

1 2

unexpected error log when KSR.xhttp.xhttp_reply(404...)
by hanxiaofang 05 May '22

05 May '22

Hello Kamailio community kamailio v5.5.4 debian10 Lua Scripting Routing: listen=tcp:127.0.0.1:5060 tcp_accept_no_cl=yes loadmodule "xhttp.so" loadmodule "app_lua.so" modparam("app_lua", "load", "/etc/kamailio/kamailio.lua") cfgengine "lua" function ksr_xhttp_event() KSR.set_reply_no_connect() KSR.set_reply_close() KSR.xhttp.xhttp_reply(404, "Not Found", "text/plain", "Not Found") end curl http://127.0.0.1:5060 -vvv * Expire in 0 ms for 6 (transfer 0x555d93fd9fb0) * Trying 127.0.0.1... * TCP_NODELAY set * Expire in 200 ms for 4 (transfer 0x555d93fd9fb0) * Connected to 127.0.0.1 (127.0.0.1) port 5060 (#0) > GET / HTTP/1.1 > Host: 127.0.0.1:5060 > User-Agent: curl/7.64.0 > Accept: */* > < HTTP/1.1 404 Not Found < Sia: SIP/2.0/TCP 127.0.0.1:54944 < Content-Type: text/plain < Server: kamailio (5.4.4 (x86_64/linux)) < Content-Length: 9 < * Connection #0 to host 127.0.0.1 left intact The output of curl is OK, but have some unexpected error in kamailio.log ERROR: <core> [core/parser/parse_fline.c:271]: parse_first_line(): parse_first_line: bad message (offset: 16) ERROR: <core> [core/parser/msg_parser.c:681]: parse_msg(): ERROR: parse_msg: message=<HTTP/1.1 404 Not Found#015#012Sia: SIP/2.0/TCP 127.0.0.1:54946#015#012Content-Type: text/plain#015#012Server: kamailio (5.4.4 (x86_64/linux))#015#012Content-Length: 9#015#012#015#012Not Found> ERROR: <core> [core/msg_translator.c:3235]: build_sip_msg_from_buf(): parsing failed now change to Native Scripting Routing: listen=tcp:127.0.0.1:5060 tcp_accept_no_cl=yes loadmodule "xhttp.so" event_route[xhttp:request] { set_reply_close(); set_reply_no_connect(); xhttp_reply("404", "Not Found", "text/plain", "Not Found"); exit; } curl http://127.0.0.1:5060 -vvv everything is ok. here is the Navite config file: http://220.231.180.131:12296/kam/native/ here is the Lua config file: http://220.231.180.131:12296/kam/kemi/ hanxiaofang

1 0

sanity_reply not available from sanity module
by Patrick Karton 04 May '22

04 May '22

Hello , the sanity_reply function from sanity is not available in kamailio script so i get an error when i want to use it. in the module source i see this static cmd_export_t cmds[] = { {"sanity_check", (cmd_function)w_sanity_check, 0, 0, 0, REQUEST_ROUTE|ONREPLY_ROUTE}, {"sanity_check", (cmd_function)w_sanity_check, 1, fixup_igp_null, 0, REQUEST_ROUTE|ONREPLY_ROUTE}, {"sanity_check", (cmd_function)w_sanity_check, 2, fixup_igp_igp, 0, REQUEST_ROUTE|ONREPLY_ROUTE}, {"sanity_check", (cmd_function)w_sanity_reply, 0, 0, 0, REQUEST_ROUTE|ONREPLY_ROUTE}, {"bind_sanity", (cmd_function)bind_sanity, 0, 0, 0, 0 }, {0, 0, 0, 0, 0, 0} }; why is sanity_check linked again in w_sanity_reply ? is this an error ? i want to setup specific responses for some errors and let the default ones from module work as usual. Thanks.

2 2

FAILEDOVER ROUTING WITH DNS SRV Records
by Patrick Karton 04 May '22

04 May '22

Hello, im using kamaliio 5.5.3 and I want to do failedover routing with DNS SRV Records. in my lab i have these SRV records ;; ANSWER SECTION: voip.oov-obs-tools-dev.svc.cluster.local. 5 IN SRV 0 33 5060 100-68-7-74.voip.oov-obs-tools-dev.svc.cluster.local. voip.oov-obs-tools-dev.svc.cluster.local. 5 IN SRV 0 33 5060 100-68-7-75.voip.oov-obs-tools-dev.svc.cluster.local. voip.oov-obs-tools-dev.svc.cluster.local. 5 IN SRV 0 33 5060 100-68-7-76.voip.oov-obs-tools-dev.svc.cluster.local. ;; ADDITIONAL SECTION: 100-68-7-76.voip.oov-obs-tools-dev.svc.cluster.local. 5 IN A 100.68.7.76 100-68-7-75.voip.oov-obs-tools-dev.svc.cluster.local. 5 IN A 100.68.7.75 100-68-7-74.voip.oov-obs-tools-dev.svc.cluster.local. 5 IN A 100.68.7.74 my config script use_dns_cache=on use_dns_failover=on dns_srv_lb=on $du = "voip.oov-obs-tools-dev.svc.cluster.local"; t_relay(); after t_relay() is called the INVITE is send to one the 3 ips corresponding to fqdn but if the first ip does not send response. the two others ips are not tried. what i want is that all the ips resolved are tried until one succeeds. is there something to do to achieve that ? do i need to interact with failure route to try next ips ? Thanks for help. version: kamailio 5.5.3 (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

2 1

function 'sl_send_reply' is not available
by David Villasmil 04 May '22

04 May '22

Hello guys, I'm starting to try KEMI and i already hit a snag... right now i'm simply testing with: loadmodule "app_lua.so" modparam("app_lua", "load", "/etc/kamailio/myscript.lua") cfgengine "lua" route { lua_run("send_reply"); } But i'm always getting: 0(118) ERROR: app_lua [app_lua_api.c:1633]: sr_kemi_lua_modf(): function 'sl_send_reply' is not available I'm guessing that function is not exported by the module.. if that's the case, how can i use it? Regards, David Villasmil email: david.villasmil.work(a)gmail.com phone: +34669448337

2 3

Dispatcher SRV load balancing
by Nicolas Chapleau 03 May '22

03 May '22

Just having a hard time trying to see if the Dispatcher module does LB when SRV records are used as the destination. Will the destinations be picked based on the SRV list or will it simply use the first name received? Read lots of docs, but can't seem to figure it out Thanks, Nic.

1 0

Problem with Record-Route in Public to Private Network
by Carlos Escalona 03 May '22

03 May '22

Hello! I wish everyone who reads this message a good day. I would appreciate some guidance with the configuration of my Kamailio. Initially, I have the following architecture: Endpoints <----Public IP----> Kamailio (listen PrivateIP advertise PublicIP) <----Private IP----> Asterisk CONFIG: https://gist.github.com/Carlos-Escalona94/3a289af05b05c69ae563ab29c9ec4710 In general, calls initiated from outside the system work perfectly, but I have a problem with calls initiated from Asterisk. According to what I was able to investigate and understand, the problem arises from the fact that Kamailio uses the public IP for the entire routing system that involves the Record-Route and Route Headers. This in turn causes Asterisk to get lost trying to send messages outside of the INITIAL INVITE transaction, for example, the ACK response to the 200 Ok received from the Endpoint since it tries to use Kamailio's public IP to which Asterisk doesn't have access. I tried to force Asterisk to send all messages to Kamailio's private IP regardless of their nature, but it doesn't seem like an appropriate solution. On the other hand, I tried to modify the architecture a bit so that it was something similar to this: Endpoints <---- Public IP----> Kamailio (listen PrivateIP:P1 advertise PublicIP) <---- PrivateIP-----> Kamailio (listen PrivateIP:P2) <---- PrivateIP ----> Asterisk CONFIG: https://gist.github.com/Carlos-Escalona94/4d681bb189c6190941d291965e123889 It seems to me that this would solve the problem, but I have two doubts about this architecture, the first is that I would like to know if there is an easier way to solve the problem that I am not considering, and on the other hand, I have not found a way to identify from which interface is receiving the message to perform the routing properly. Thanks for the attention. -- *Esta mensagem pode conter informação confidencial ou privilegiada, sendo seu sigilo protegido por lei. Se você não for o destinatário ou a pessoa autorizada a receber esta mensagem, não pode usar, copiar ou divulgar as informações nela contidas ou tomar qualquer ação baseada nessas informações. Se você recebeu esta mensagem por engano, por favor, avise imediatamente ao remetente, respondendo o e-mail e em seguida apague-a. Agradecemos sua cooperação. ** * *This message may contain confidential or privileged information and its confidentiality is protected by law. If you are not the addressed or authorized person to receive this message, you must not use, copy, disclose or take any action based on it or any information herein. If you have received this message by mistake, please advise the sender immediately by replying the e-mail and then deleting it. Thank you for your cooperation. *

3 2

2026

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 May 2022