sr-users September 2020

sr-users@lists.kamailio.org

84 participants
107 discussions

Kamailio vulnerable to header smuggling possible due to bypass of remove_hf

by Yufei Tao

Hi, The security tests were done to find theoretically possible flaws and help make Kamailio "bullet proof". Well it's already a lot more robust than most others. I think Daniel and Henning have made it very clear about the scope of the bug. For me if it is something that's been there for so many years without being noticed, it would be a bit surprising if declared as a high risk problem. Plus isn't this something you should find out if you do your testing properly? If it were to create big troubles for anyone, that means they had never tested their deployment properly in the past 18 years?? That's where I get confused. Of course anyone can fork and build Kamailio themselves if they really need something urgently since it's open source. Cheers, Yufei

3 years, 10 months

Weird config parsing issues - 5.4

by Noah Mehl

All, I have built branch 5.4 from source, and I’m working with the default config. However, from time to time I get this error when launching kamailio: root@inbound-kamailio-test-02:~# /usr/local/sbin/kamailio -P /run/kamailio/kamailio.pid -f /usr/local/etc/kamailio/kamailio.cfg -m 128 -M 64 -E 0(1296) CRITICAL: <core> [core/cfg.y:3588]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 410, column 30-34: syntax error 0(1296) CRITICAL: <core> [core/cfg.y:3588]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 410, column 30-34: Invalid arguments 0(1296) CRITICAL: <core> [core/cfg.y:3591]: yyerror_at(): parse error in config file /usr/local/etc/kamailio/kamailio.cfg, line 410, column 35: ERROR: bad config file (3 errors) 0(1296) ERROR: <core> [core/ppcfg.c:234]: pp_ifdef_level_error(): different number of preprocessor directives: 1 more #!if[n]def as #!endif However, if I run a “make install” from the source directory, this error goes away. Has anyone run into this issue before? Configs attached. Thanks! ~Noah

3 years, 10 months

Fwd: Keep evapi bind address alive on kamailio restart

by Mehrdad EsmaeilPour

Hi all, I have a question about evapi module. Is it possible to keep the bind address of evapi alive on kamailio restarts? How can I achieve high availability for evpai's bind address? Many thnaks -- *Kind Regards, Mehrdad Esmaeilpour <https://www.linkedin.com/in/mehrdadep/>*

3 years, 10 months

worker processes

by Ali Taher

Hi, I just want to ask regarding the children number and listening interfaces set in Kamailio configuration. I am given to understand that the total number of worker processes there will be (children_setting * listeners) , so assuming I have set children=12 and listen=udp:172.16.1.12:5060 (which is the interface IP where the SIP packets as received), in this case there will be 12 worker processes and 12 database connections to postgresql (I'm using SQLOPS). My question is if I set listen=udp:0.0.0.0:5060 , knowing that I have 3 interfaces, in this case the number of worker processes will be 36. Is this good configuration ? will the other 24 processes be used or they are reserved to the 2 other interfaces which are not receiving any SIP packets and then will be useless ? Regards, Ali Taher

3 years, 10 months

kamailio coring ver 5.1.2

by Andrew Chen

Hey guys, Our monitoring system caught kamailio coring. I did a dmesg and gave me this: [Tue Sep 1 09:12:34 2020] kamailio[1375]: segfault at 1 ip 0000000000000001 sp 00007fff4203f098 error 14 in kamailio[563969b5a000+4a4000] [Tue Sep 1 09:12:34 2020] Code: Bad RIP value. [Tue Sep 1 09:12:34 2020] kamailio[1363]: segfault at 0 ip 0000000000000000 sp 00007fff4203f368 error 14 in kamailio[563969b5a000+4a4000] [Tue Sep 1 09:12:34 2020] Code: Bad RIP value. [Tue Sep 1 09:12:34 2020] kamailio[1377]: segfault at 1 ip 0000000000000001 sp 00007fff4203e308 error 14 in kamailio[563969b5a000+4a4000] [Tue Sep 1 09:12:34 2020] Code: Bad RIP value. After doing gdb bt, didn't tell me much except it can't access some parts of the memory: warning: Unexpected size of section `.reg-xstate/1624' in core file. Cannot access memory at address 0x7fb23433e148 Cannot access memory at address 0x7fb23433e140 Failed to read a valid object file image from memory. Core was generated by `/usr/sbin/kamailio -P /var/run/kamailio/kamailio.pid -f /etc/kamailio/kamailio.'. Program terminated with signal SIGSEGV, Segmentation fault. warning: Unexpected size of section `.reg-xstate/1624' in core file. #0 0x0000000000000001 in ?? () (gdb) bt full #0 0x0000000000000001 in ?? () No symbol table info available. Backtrace stopped: Cannot access memory at address 0x7fff4203e1f8 (gdb) quit Any idea on how to troubleshoot this further? Thanks. -- Andy Chen Sr. Telephony Lead Engineer achen@ <achen(a)thinkingphones.com>fuze.com -- *Confidentiality Notice: The information contained in this e-mail and any attachments may be confidential. If you are not an intended recipient, you are hereby notified that any dissemination, distribution or copying of this e-mail is strictly prohibited. If you have received this e-mail in error, please notify the sender and permanently delete the e-mail and any attachments immediately. You should not retain, copy or use this e-mail or any attachment for any purpose, nor disclose all or any part of the contents to any other person. Thank you.*

3 years, 10 months

Releasing Kamailio v5.4.1

by Daniel-Constantin Mierla

Hello, I am considering to release Kamailio v5.4.1 as the first patch release in the 5.4 series, likely to be done next week, on the 1st of September, 2020. There are a few issues reported on the tracker, hopefully they will be tackled till then. If you are aware of something else not working as expected, report them to issue tracker asap to give a better chance to be fixed till the release day. Cheers, Daniel -- Daniel-Constantin Mierla -- www.asipto.com www.twitter.com/miconda -- www.linkedin.com/in/miconda Funding: https://www.paypal.me/dcmierla

3 years, 10 months

Kamailio v5.4.1 Released

by Daniel-Constantin Mierla

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

3 years, 10 months

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 September 2020