sr-dev October 2021

sr-dev@lists.kamailio.org

19 participants
243 discussions

[kamailio/kamailio] github/workflow: add CIFuzz integration (PR #2903)

by DavidKorczynski

Add CIFuzz workflow action to have fuzzers build and run on each PR. This is a service offered by OSS-Fuzz, on which Kamailio already runs. Signed-off-by: David Korczynski <david(a)adalogics.com>   #### Pre-Submission Checklist    - [x ] Commit message has the format required by CONTRIBUTING guide - [x ] Commits are split per component (core, individual modules, libs, utils, ...) - [x ] Each component has a single commit (if not, squash them into one commit) - [x ] No commits to README files for modules (changes must be done to docbook files in `doc/` subfolder, the README file is autogenerated) #### Type Of Change - [ ] Small bug fix (non-breaking change which fixes an issue) - [x ] New feature (non-breaking change which adds new functionality) - [ ] Breaking change (fix or feature that would change existing functionality) #### Checklist:  - [x ] PR should be backported to stable branches - [x ] Tested changes locally - [ ] Related to issue #XXXX (replace XXXX with an open issue number) #### Description  Add CIFuzz Github action to build and run fuzzers on pull requests. This will run the fuzzers for 600 seconds (split between all the fuzzers) in the CI when a pull request is made and is a service by OSS-fuzz. It can help with catching bugs early and catch regressions. Documentation for CIFuzz can be found here: https://google.github.io/oss-fuzz/getting-started/continuous-integration/ You can view, comment on, or merge this pull request online at: https://github.com/kamailio/kamailio/pull/2903 -- Commit Summary -- * <a href="https://github.com/kamailio/kamailio/pull/2903/commits/f10ba5c9e81f0ae0f2f6…">github/workflow: add CIFuzz integration</a> -- File Changes -- A .github/workflows/cifuzz.yml (26) -- Patch Links -- https://github.com/kamailio/kamailio/pull/2903.patch https://github.com/kamailio/kamailio/pull/2903.diff -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/pull/2903

2 years, 6 months

git:master:f10ba5c9: github/workflow: add CIFuzz integration

by David Korczynski

Module: kamailio Branch: master Commit: f10ba5c9e81f0ae0f2f6efc9c721ced5ce5207c0 URL: https://github.com/kamailio/kamailio/commit/f10ba5c9e81f0ae0f2f6efc9c721ced… Author: David Korczynski <david(a)adalogics.com> Committer: David Korczynski <david(a)adalogics.com> Date: 2021-10-27T11:26:15+01:00 github/workflow: add CIFuzz integration Add CIFuzz workflow action to have fuzzers build and run on each PR. This is a service offered by OSS-Fuzz, on which Kamailio already runs. Signed-off-by: David Korczynski <david(a)adalogics.com> --- Added: .github/workflows/cifuzz.yml --- Diff: https://github.com/kamailio/kamailio/commit/f10ba5c9e81f0ae0f2f6efc9c721ced… Patch: https://github.com/kamailio/kamailio/commit/f10ba5c9e81f0ae0f2f6efc9c721ced… --- diff --git a/.github/workflows/cifuzz.yml b/.github/workflows/cifuzz.yml new file mode 100644 index 0000000000..948ab18b88 --- /dev/null +++ b/.github/workflows/cifuzz.yml @@ -0,0 +1,26 @@ +name: CIFuzz +on: [pull_request] +jobs: + Fuzzing: + runs-on: ubuntu-latest + steps: + - name: Build Fuzzers + id: build + uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master + with: + oss-fuzz-project-name: 'kamailio' + dry-run: false + language: c + - name: Run Fuzzers + uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master + with: + oss-fuzz-project-name: 'kamailio' + fuzz-seconds: 600 + dry-run: false + language: c + - name: Upload Crash + uses: actions/upload-artifact@v1 + if: failure() && steps.build.outcome == 'success' + with: + name: artifacts + path: ./out/artifacts

2 years, 6 months

git:master:88af7f7f: Merge pull request #2903 from DavidKorczynski/cifuzz

by GitHub

Module: kamailio Branch: master Commit: 88af7f7fa91eb864ed57c2331bff05a9062f630e URL: https://github.com/kamailio/kamailio/commit/88af7f7fa91eb864ed57c2331bff05a… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: GitHub <noreply(a)github.com> Date: 2021-10-27T14:29:35+02:00 Merge pull request #2903 from DavidKorczynski/cifuzz github/workflow: add CIFuzz integration --- Added: .github/workflows/cifuzz.yml --- Diff: https://github.com/kamailio/kamailio/commit/88af7f7fa91eb864ed57c2331bff05a… Patch: https://github.com/kamailio/kamailio/commit/88af7f7fa91eb864ed57c2331bff05a… --- diff --git a/.github/workflows/cifuzz.yml b/.github/workflows/cifuzz.yml new file mode 100644 index 0000000000..948ab18b88 --- /dev/null +++ b/.github/workflows/cifuzz.yml @@ -0,0 +1,26 @@ +name: CIFuzz +on: [pull_request] +jobs: + Fuzzing: + runs-on: ubuntu-latest + steps: + - name: Build Fuzzers + id: build + uses: google/oss-fuzz/infra/cifuzz/actions/build_fuzzers@master + with: + oss-fuzz-project-name: 'kamailio' + dry-run: false + language: c + - name: Run Fuzzers + uses: google/oss-fuzz/infra/cifuzz/actions/run_fuzzers@master + with: + oss-fuzz-project-name: 'kamailio' + fuzz-seconds: 600 + dry-run: false + language: c + - name: Upload Crash + uses: actions/upload-artifact@v1 + if: failure() && steps.build.outcome == 'success' + with: + name: artifacts + path: ./out/artifacts

2 years, 6 months

git:master:a4b88342: etc: kamailio.cfg - updated version in comments

by Daniel-Constantin Mierla

Module: kamailio Branch: master Commit: a4b88342d2c715a151ef032996d1b71a482be00b URL: https://github.com/kamailio/kamailio/commit/a4b88342d2c715a151ef032996d1b71… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2021-10-27T13:24:59+02:00 etc: kamailio.cfg - updated version in comments --- Modified: etc/kamailio.cfg --- Diff: https://github.com/kamailio/kamailio/commit/a4b88342d2c715a151ef032996d1b71… Patch: https://github.com/kamailio/kamailio/commit/a4b88342d2c715a151ef032996d1b71… --- diff --git a/etc/kamailio.cfg b/etc/kamailio.cfg index c349fcf65c..56c1ea791e 100644 --- a/etc/kamailio.cfg +++ b/etc/kamailio.cfg @@ -1,6 +1,6 @@ #!KAMAILIO # -# Kamailio SIP Server v5.5 - default configuration script +# Kamailio SIP Server v5.6 - default configuration script # - web: https://www.kamailio.org # - git: https://github.com/kamailio/kamailio #

2 years, 6 months

TLS trouble

by Lorenzo Campo

Hi guys, We are quite newby about Kamailio and we are trying to use it as a load balancer. While installing certificates we started having problems. We use Kamailio (vers. 5.5) deployed on a VM (Ubuntu, 20.04 LTS). We cannot connect via TLS Kamailio VM with clients or other TCP VM. Our Kamailio currently exposes only port 5060 in UDP and TCP. Even doing a port scan on localhost, port 5061, used for the TLS protocol, is instead closed. There are 3 things worth noting: - All ports for all protocols are open on the firewall; - Before we set the disable_tcp option to "no", the 5060 was only reachable in UDP; - Even if you put a non-existent certificate, the system does not return an error so we cannot understand if the goodness of the certificates affects the opening of the door. Furthermore, we did not find any different behavior when switching from crt format (key for the private key) to PEM. If someone can help us would be very appreciated. Thank you very much Here is our tls configuration: kamailio.cfg #!define WITH_TLS 1 ... disable_tcp=no auto_aliases=no …. loadmodule "sl.so" loadmodule "tls.so" ... modparam("tls", "private_key", "/etc/kamailio/key.pem") modparam("tls", "certificate", "/etc/kamailio/crt.pem") modparam("tls", "ca_list", "/etc/kamailio/ca.pem") enable_tls=yes tls.config [server:default] method = TLSv1.2+ verify_certificate = no require_certificate = no private_key = /etc/kamailio/kamailio-selfsigned.key certificate = /etc/kamailio/kamailio-selfsigned.pem #ca_list = /etc/kamailio/tls/cacert.pem #crl = /etc/kamailio/tls/crl.pem [client:default] #method = TLSv1.2+ verify_certificate = no require_certificate = no *Sent with Shift <https://tryshift.com/?utm_source=SentWithShift&utm_campaign=Sent+with+Shift…>*

2 years, 6 months

git:master:b11a9835: etc: kamailio.cfg - added pplsip to user-agent list to drop

by Daniel-Constantin Mierla

Module: kamailio Branch: master Commit: b11a9835778cd2ddb60e743b8b8b2f1ff54ccdcc URL: https://github.com/kamailio/kamailio/commit/b11a9835778cd2ddb60e743b8b8b2f1… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2021-10-26T08:23:59+02:00 etc: kamailio.cfg - added pplsip to user-agent list to drop --- Modified: etc/kamailio.cfg --- Diff: https://github.com/kamailio/kamailio/commit/b11a9835778cd2ddb60e743b8b8b2f1… Patch: https://github.com/kamailio/kamailio/commit/b11a9835778cd2ddb60e743b8b8b2f1… --- diff --git a/etc/kamailio.cfg b/etc/kamailio.cfg index be71dbb54a..c349fcf65c 100644 --- a/etc/kamailio.cfg +++ b/etc/kamailio.cfg @@ -615,7 +615,7 @@ route[REQINIT] { } } #!endif - if($ua =~ "friendly|scanner|sipcli|sipvicious|VaxSIPUserAgent") { + if($ua =~ "friendly|scanner|sipcli|sipvicious|VaxSIPUserAgent|pplsip") { # silent drop for scanners - uncomment next line if want to reply # sl_send_reply("200", "OK"); exit;

2 years, 6 months

git:master:dfafbf6d: modules: readme files regenerated - textopsx ... [skip ci]

by Kamailio Dev

Module: kamailio Branch: master Commit: dfafbf6dc1269a059b4d7f90274288070cc5e9c9 URL: https://github.com/kamailio/kamailio/commit/dfafbf6dc1269a059b4d7f902742880… Author: Kamailio Dev <kamailio.dev(a)kamailio.org> Committer: Kamailio Dev <kamailio.dev(a)kamailio.org> Date: 2021-10-25T19:31:14+02:00 modules: readme files regenerated - textopsx ... [skip ci] --- Modified: src/modules/textopsx/README --- Diff: https://github.com/kamailio/kamailio/commit/dfafbf6dc1269a059b4d7f902742880… Patch: https://github.com/kamailio/kamailio/commit/dfafbf6dc1269a059b4d7f902742880… --- diff --git a/src/modules/textopsx/README b/src/modules/textopsx/README index 411653a92a..6216f40e19 100644 --- a/src/modules/textopsx/README +++ b/src/modules/textopsx/README @@ -37,14 +37,14 @@ Daniel-Constantin Mierla 2.16. hf_value_exists(hf, hvalue) 2.17. hf_iterator_start(iname) 2.18. hf_iterator_end(iname) - 2.19. textopsx.f.hf_iterator_next(iname) - 2.20. textopsx.f.hf_iterator_prev(iname) + 2.19. hf_iterator_next(iname) + 2.20. hf_iterator_prev(iname) 2.21. hf_iterator_rm(iname) 2.22. hf_iterator_append(iname, htext) 2.23. hf_iterator_insert(iname, htext) 2.24. bl_iterator_start(iname) 2.25. bl_iterator_end(iname) - 2.26. textopsx.f.bl_iterator_next(iname) + 2.26. bl_iterator_next(iname) 2.27. bl_iterator_rm(iname) 2.28. bl_iterator_append(iname, text) 2.29. bl_iterator_insert(iname, text) @@ -113,14 +113,14 @@ Chapter 1. Admin Guide 2.16. hf_value_exists(hf, hvalue) 2.17. hf_iterator_start(iname) 2.18. hf_iterator_end(iname) - 2.19. textopsx.f.hf_iterator_next(iname) - 2.20. textopsx.f.hf_iterator_prev(iname) + 2.19. hf_iterator_next(iname) + 2.20. hf_iterator_prev(iname) 2.21. hf_iterator_rm(iname) 2.22. hf_iterator_append(iname, htext) 2.23. hf_iterator_insert(iname, htext) 2.24. bl_iterator_start(iname) 2.25. bl_iterator_end(iname) - 2.26. textopsx.f.bl_iterator_next(iname) + 2.26. bl_iterator_next(iname) 2.27. bl_iterator_rm(iname) 2.28. bl_iterator_append(iname, text) 2.29. bl_iterator_insert(iname, text) @@ -161,14 +161,14 @@ Chapter 1. Admin Guide 2.16. hf_value_exists(hf, hvalue) 2.17. hf_iterator_start(iname) 2.18. hf_iterator_end(iname) - 2.19. textopsx.f.hf_iterator_next(iname) - 2.20. textopsx.f.hf_iterator_prev(iname) + 2.19. hf_iterator_next(iname) + 2.20. hf_iterator_prev(iname) 2.21. hf_iterator_rm(iname) 2.22. hf_iterator_append(iname, htext) 2.23. hf_iterator_insert(iname, htext) 2.24. bl_iterator_start(iname) 2.25. bl_iterator_end(iname) - 2.26. textopsx.f.bl_iterator_next(iname) + 2.26. bl_iterator_next(iname) 2.27. bl_iterator_rm(iname) 2.28. bl_iterator_append(iname, text) 2.29. bl_iterator_insert(iname, text) @@ -509,10 +509,10 @@ hf_iterator_start("i1"); hf_iterator_end("i1"); ... -2.19. textopsx.f.hf_iterator_next(iname) +2.19. hf_iterator_next(iname) Move the iterator to the next header. It must be called also after - bl_iterator_start() to get the first header. + hf_iterator_start() to get the first header. The return code is false when there is no other header in the list. @@ -532,7 +532,7 @@ hf_iterator_end("i1"); hf_iterator_end("i1"); ... -2.20. textopsx.f.hf_iterator_prev(iname) +2.20. hf_iterator_prev(iname) Move the iterator to the previous header. It must be called also after hf_iterator_start() and hf_iterator_next(). @@ -641,7 +641,7 @@ bl_iterator_start("b1"); bl_iterator_end("b1"); ... -2.26. textopsx.f.bl_iterator_next(iname) +2.26. bl_iterator_next(iname) Move the iterator to the next line in the body. It must be called also after bl_iterator_start() to get the first header.

2 years, 6 months

git:master:01434fa8: textopsx: docs - fixed title for sections

by Daniel-Constantin Mierla

Module: kamailio Branch: master Commit: 01434fa89bac3174ff68c08cf776dc73abb2eb2d URL: https://github.com/kamailio/kamailio/commit/01434fa89bac3174ff68c08cf776dc7… Author: Daniel-Constantin Mierla <miconda(a)gmail.com> Committer: Daniel-Constantin Mierla <miconda(a)gmail.com> Date: 2021-10-25T19:23:08+02:00 textopsx: docs - fixed title for sections --- Modified: src/modules/textopsx/doc/functions.xml --- Diff: https://github.com/kamailio/kamailio/commit/01434fa89bac3174ff68c08cf776dc7… Patch: https://github.com/kamailio/kamailio/commit/01434fa89bac3174ff68c08cf776dc7… --- diff --git a/src/modules/textopsx/doc/functions.xml b/src/modules/textopsx/doc/functions.xml index 3de3a6c8e6..7500cbaa85 100644 --- a/src/modules/textopsx/doc/functions.xml +++ b/src/modules/textopsx/doc/functions.xml @@ -559,11 +559,11 @@ hf_iterator_end("i1"); </section> <section id="textopsx.f.hf_iterator_next"> <title> - <function moreinfo="none">textopsx.f.hf_iterator_next(iname)</function> + <function moreinfo="none">hf_iterator_next(iname)</function> </title> <para> Move the iterator to the next header. It must - be called also after bl_iterator_start() to get the first + be called also after hf_iterator_start() to get the first header. </para> <para> @@ -594,7 +594,7 @@ hf_iterator_end("i1"); </section> <section id="textopsx.f.hf_iterator_prev"> <title> - <function moreinfo="none">textopsx.f.hf_iterator_prev(iname)</function> + <function moreinfo="none">hf_iterator_prev(iname)</function> </title> <para> Move the iterator to the previous header. It must @@ -757,7 +757,7 @@ bl_iterator_end("b1"); </section> <section id="textopsx.f.bl_iterator_next"> <title> - <function moreinfo="none">textopsx.f.bl_iterator_next(iname)</function> + <function moreinfo="none">bl_iterator_next(iname)</function> </title> <para> Move the iterator to the next line in the body. It must

2 years, 6 months

SIPtrace: Blocking processes

by Olle E. Johansson

Hi! I just stumbled into a hard-to-find problem with Kamailio. The symtom was that Kamailio simply did not read a lot of incoming messages, so they did not get any response. We saw traffic coming in on the interface with tcpdump, but not in the kamailio logs. Restarting Kamailio solved the problem for a while, then it started again. I noticed there was something related to the DB, so for testing I disabled all db-based functions, but missed siptrace that connected and operated in the background by the config settings, nothing in the routing script. I finally traced the problem to the siptrace module. The db table had grown way too big (due to attacks) and adding new records to it took way too much time. During that time, with SIPtrace waiting for confirmation, the process locked and packets where dropped. Kamailio still handled calls, but a lot of calls was dropped. I will solve this shortly by setting up a parallell smaller Kamailio that logs to database instead of running siptrace with DB in a production server. But in order for others not to find themselves in this very hard to find situation, is there something that can be done to the siptrace code so it doesn’t execute in the same process that listens for incoming SIP messages? It would be a huge improvement to just block a background process so that siptrace doesn’t work, instead of blocking a listen process and drop traffic. I don’t think I can write that code. Sorry. Otherwise it would have been a high priority, because these problems in production drove me almost insane. Restarting - all works fine. After a few hours the first packets are lost. Calls getting through for some customers all of the time. Sorry for a long post, but I want this in the archives to help others. Regards, /O

2 years, 6 months

[kamailio/kamailio] CDP / IMS Diameter Server Module- event_route[diameter:response] fails to receive/forward response (Issue #2900)

by w415384914

I config ims_diameter_server as below: ``` #!ifdef WITH_DIAMETER_SERVER # IMS_DIAMETER_SERVER event_route[diameter:request]{ xlog("L_INFO","ims Got diameter message"); # diameter_request("hss.ims.mnc001.mcc001.3gppnetwork.org", $diameter_application, $diameter_command, $diameter_request); diameter_request_async("hss.ims.mnc001.mcc001.3gppnetwork.org", $diameter_application, $diameter_command, $diameter_request); xlog("L_INFO","ims Forwarded Diameter Request"); } event_route[diameter:response] { xlog("L_INFO","ims Reply to Diameter request is $diameter_response\n"); } #!endif ``` And got a response from hss: ![image](https://user-images.githubusercontent.com/10116705/138629415-dd7f6266-7801-4ed3-8922-a0b9cba4089a.png) but got <null> response in log: > 90(124) INFO: <script>: ims Got diameter message90(124) DEBUG: ims_diameter_server [avp_helper.c:59]: avp2json(): AVP((nil) < 0x7f44c2ad16f0 >0x7f44c2ad0c08);code=263,flags=40; > 89(123) INFO: <script>: ims Reply to Diameter request is <null> $diameter_response is <null>, why, how to fix it? -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2900

2 years, 6 months

← Newer
1
...
12
13
14
15
16
17
18
...
25
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

sr-dev October 2021