I think this issue (regression from a bug fix) should be fixed in 5.8.4. Please
update and give it a try.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4115#issuecomment-2597557089
You are receiving this because you are subscribed to this threa
### Description
After upgrading from Kamailio 5.7 to 5.8, we encountered an issue where SIP
messages fail to send over WSS, resulting in a 477 error.
The problem seems to be related to the addition of protocol validation logic in
tcp_main.c:
https://github.com/kamailio/kamailio/blob/master/s
We have core pattern so a static 8 children for tcp and for udp listeners.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4102#issuecomment-259637
You are receiving this because you are subscribed to this thread.
Message ID:
The structure is ok, so it should be no reason to crash, maybe the core was
overwritten, do you have one core per pid (or core pattern per process)
enabled? It may happen that many cores are generated and the one that was the
reason for the crash gets overwritten by the others generated as a sid
Regarding the overlapping of tables, we are probably having a similar issue
with the "location" table from #4108.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4110#issuecomment-2595928540
You are receiving this because you are subscribed to this
Was there a particular reason you only included a subset of the database tables
in the re-generation commit? E.g. the dbtext tables are missing.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4108#issuecomment-2595914523
You are receiving this bec
You can find the lists here: https://www.kamailio.org/w/mailing-lists/
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4107#issuecomment-2595771714
You are receiving this because you are subscribed to this thread.
Message ID: __
> [@henningw](https://github.com/henningw) I want to use C17 features in my
> kamailio module :)
I think you can create a new module with whatever standard you want if you set
the standard in it's own module `CMakeLists.txt`. CMake will respect the
standard set only for that module and whatever
@xkaraman thanks for your reply, I test it and compile correctly, where is
kamailio dev list?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4107#issuecomment-2595753973
You are receiving this because you are subscribed to this thread.
Message ID
Ok, thanks :)
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4106#issuecomment-2595750139
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio - Development Mailin
Hey @soroshsabz.
This change is indeed quite steep as @henningw said. If you want, though you
can try compiling kamailio with C17 by passing the option to `cmake`
configuration phase,
`cmake -S . -B build-folder -DCMAKE_C_STANDARD=C17
-DCMAKE_C_STANDARD_REQUIRED=True`. This will try to compile
Module: kamailio
Branch: master
Commit: fbf120d3696b63ecd90055b136fd40c87b5db68e
URL:
https://github.com/kamailio/kamailio/commit/fbf120d3696b63ecd90055b136fd40c87b5db68e
Author: Xenofon Karamanos
Committer: Xenofon Karamanos
Date: 2025-01-16T13:40:18Z
cmake: Add dbschema_xhttp_pi to have cons
The 6.1 release will be also considered a major release. Minor releases are
from 5.8.3 to 5.8.4.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4106#issuecomment-2595701134
You are receiving this because you are subscribed to this thread.
Messa
@soroshsabz commented on this pull request.
> @@ -2,6 +2,13 @@ cmake_minimum_required(VERSION 3.10)
# Use cmake -DCMAKE_SYSTEM_NAME .. for cross-compiling (inside build directory)
+# cmake_policy must be before project for working with toolchain together
+if(WIN32)
+ cmake_policy(SET CMP00
Thanks, merged
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4108#issuecomment-2595485896
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio - Development Mailing
Merged #4108 into master.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4108#event-15958479441
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio - Development Ma
Module: kamailio
Branch: master
Commit: a4f44ceaaf2203e79c8b2f1ea19a7ffc18c2712a
URL:
https://github.com/kamailio/kamailio/commit/a4f44ceaaf2203e79c8b2f1ea19a7ffc18c2712a
Author: Victor Seva
Committer: Henning Westerholt
Date: 2025-01-16T13:35:47+01:00
utils/kamctl: regenerate db table definit
Module: kamailio
Branch: master
Commit: f339eb7e5aee90229f3d6046d5f7586a1622f4bb
URL:
https://github.com/kamailio/kamailio/commit/f339eb7e5aee90229f3d6046d5f7586a1622f4bb
Author: Victor Seva
Committer: Henning Westerholt
Date: 2025-01-16T13:35:47+01:00
lib/srdb1/schema: ims_usrloc_pcscf defini
Migrating to new C version does not cause major version change? That's why I'm
asking if it's necessary to do this during the migration to version 6.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4106#issuecomment-2595472272
You are receiving t
@linuxmaniac pushed 2 commits.
0ec4c4485c10601576eb9944a5e0719e24759637 lib/srdb1/schema: ims_usrloc_pcscf
definitions
e1c52fb930364c2eda267265c205b9730b4c835f utils/kamctl: regenerate db table
definitions
--
View it on GitHub:
https://github.com/kamailio/kamailio/pull/4108/files/0d7d388182c
@lazedo many Windows first environment does not have WSL on Windows Server and
does not use Linux container and they use [Windows
Container](https://learn.microsoft.com/en-us/virtualization/windowscontainers/about/)
instead.
--
Reply to this email directly or view it on GitHub:
https://github.
@linuxmaniac commented on this pull request.
> +`protocol` INT(10) DEFAULT NULL,
+`mode` VARCHAR(10) DEFAULT NULL,
+`ck` VARCHAR(100) DEFAULT NULL,
+`ik` VARCHAR(100) DEFAULT NULL,
+`ealg` VARCHAR(20) DEFAULT NULL,
+`ialg` VARCHAR(20) DEFAULT NULL,
+`port_pc` INT(11)
isn't `docker` or `wsl` a valid alternative ? I think we don't need these
`windows` specific changes.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/4113#issuecomment-2595238961
You are receiving this because you are subscribed to this thread.
Me
@henningw commented on this pull request.
Thanks for the PR. I have reviewed and added only one comment, where I was not
sure if it was an intentional change. The CHAR to VARCHAR conversion is fine, I
think - we are using VARCHAR everywhere usually.
> +`protocol` INT(10) DEFAULT NULL,
+
@linuxmaniac thanks for your reply, many company use Windows environment for IT
infrastructure, so if I can port kamailio to Windows, and merge into main repo,
windows has come to second citizenship class of kamailio, and many companies
can use better kamailio with default their IT environment,
@henningw thanks for review my PR, `cross_strings.h` come from [our
company](https://github.com/BSVN), I can change copyright with anything that
you want. (_That change was because the previous one was outdated and now we
are making changes to the new company brand name_)
--
Reply to this ema
Module: kamailio
Branch: master
Commit: 5fe61ec6dbcd9d2dde3f2bd978dad5130ac5bff9
URL:
https://github.com/kamailio/kamailio/commit/5fe61ec6dbcd9d2dde3f2bd978dad5130ac5bff9
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2025-01-16T10:47:25+01:00
core: tcp - remove lev
I don't see the value of porting kamailio to windows. But if you want to do
it... no one will stop you from doing it, in your fork. Pushing changes just
because, makes no sense to me. This will just make things harder to maintain.
--
Reply to this email directly or view it on GitHub:
https://gi
Now the make clean executed in the build folder don't delete the READMEs from
the source folder anymore.
```
~/repositories/kamailio$ cmake --build build/
[..]
~/repositories/kamailio$ cd build/
~/repositories/kamailio/build$ make clean
~/repositories/kamailio/build$ cd ..
~/repositories/kamailio
After building the dbschema target the files are installed.
```
$ cmake -S . -B build -DCMAKE_INSTALL_PREFIX=/tmp/kamailio-build
[..]
$ $ cmake --build build/
[..]
$ cmake --build build/ -t dbschema
[..]
$ cmake --install build/
[..]
$ ls -la /tmp/kamailio-build/share/kamailio/dbtext/kamailio/
tot
Please address your questions on how to use Kamailio to our users mailing list
"sr-users". There is a special module for this
https://www.kamailio.org/docs/modules/devel/modules/sipt.html
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4112#issu
Closed #4112 as completed.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/4112#event-15953224278
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio - Development
Hello, before going further this way you should start a discussion e.g. on the
developer list or during one of the next online developer meetings. There will
be many changes necessary to really support Windows, and right now I am not
100% sure if this is really a feasible thing to do that will w
Hello, before going further this way you should start a discussion e.g. on the
developer list or during one of the next online developer meetings. There will
be many changes necessary to really support Windows, and right now I am not
100% sure if this is really a feasible thing to do that will w
34 matches
Mail list logo
