Should this be merged?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3571#issuecomment-1748131804
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) -
If reusing `misc/scripts/` location does not seem a good option, I think it is
better at least to have the folder relocated to `pkg/kamailio/scripts/` instead
of `pkg/scripts/`.
--
Reply to this email directly or view it on GitHub:
I'm still waiting for @schiramchetty feedback
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3571#issuecomment-1748169931
You are receiving this because you are subscribed to this thread.
Message ID:
!-- Kamailio Pull Request Template --
!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable
The rfc7118 (https://www.rfc-editor.org/rfc/rfc7118.html) defines only
`transport=ws`, where have you met `transport=wss`?
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3588#issuecomment-1748147393
You are receiving this because you are
Is any work still planned on refactoring to a new algorithm? Maybe this can be
closed and a new PR created when it is done.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3531#issuecomment-1748152061
You are receiving this because you are
@space88man pushed 1 commit.
252dcffb5755edb09b42eec053a6b471af32202c pkg: RPM - add mock config for
EL8/EL9 based on alma+epel-(8|9)-x86_64
--
View it on GitHub:
!-- Kamailio Pull Request Template --
!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable
Closed #3591.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3591#event-10559290499
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Development Mailing
version: kamailio 5.5.6 (x86_64/linux) 21a9bc
Operating System: Debian GNU/Linux 11 (bullseye)
Kernel: Linux 5.10.0-22-amd64
we see this core it has repeated some times in different days
```
(gdb) bt
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1
There is one strange moment that I forgot to mention above, in the logs exactly
at the moment when the service began to refuse, the recording disappears
completely for 7 minutes, absolutely no entries, after which the recording of
the TSP queue overflow begins.
Oct 3 18:38:07 sip1-life3
Closed #3531.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3531#event-10564114959
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Development Mailing
@miconda i'll open this as a new PR when I can get back around to it, thanks!
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3531#issuecomment-1748937640
You are receiving this because you are subscribed to this thread.
Message ID:
Hello!
It often happens to me that the service begins to refuse service (503) and so
far I have not been able to understand the exact reason. Typically, before
clients start receiving 503, many before them receive a 408 code. As soon as
the service starts responding with 503, it does not
!-- Kamailio Pull Request Template --
!--
IMPORTANT:
- for detailed contributing guidelines, read:
https://github.com/kamailio/kamailio/blob/master/.github/CONTRIBUTING.md
- pull requests must be done to master branch, unless they are backports
of fixes from master branch to a stable
> If reusing `misc/scripts/` location does not seem a good option, I think it
> is better at least to have the folder relocated to `pkg/kamailio/scripts/`
> instead of `pkg/scripts/`.
Done and pushed.
--
Reply to this email directly or view it on GitHub:
@space88man pushed 1 commit.
2bd4a15c58a30d4abf3e4966095b087abd2f7efa pkg: RPM - add mock config for
EL8/EL9 based on alma+epel-(8|9)-x86_64
--
View it on GitHub:
hello all
I tried to set the machine default route to 87.1.1.1 but I still got messages
of that kind
I also tried to add force socket on cancel requests before the t_relay(), since
I saw that maybe when the error generated was when we have a CANCEL request
which seemed to not be processed the
@miconda SIP.js is including it in the contact header, then, the register
module keeps it. I think this is also happening with pjsip but I haven't had a
chance to properly verify it.
Also, IMHO, I think that this is still a misleading subject because, referring
to Iñaki's message in jssip:
@joelbax: I think RFC3261 mention the deprecation of `transport=tls` for `sips`
scheme (ie., end to end secure transmission), but it is defined in the grammar
(e.g., for hop-by-hop tls usage). See RFC3261 page 223:
```
transport-param = "transport="
( "udp" / "tcp" /
Closed #3588.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3588#event-10567664961
You are receiving this because you are subscribed to this thread.
Message ID: ___
Kamailio (SER) - Development Mailing
Module: kamailio
Branch: master
Commit: 022f0f4cfd49e7a46efb2b6b4e1b9640c399e535
URL:
https://github.com/kamailio/kamailio/commit/022f0f4cfd49e7a46efb2b6b4e1b9640c399e535
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2023-10-05T18:05:00+02:00
misc/examples/kemi:
Module: kamailio
Branch: master
Commit: e01d1cbfb61e0111a4f73e58e36a2bd689a2f91f
URL:
https://github.com/kamailio/kamailio/commit/e01d1cbfb61e0111a4f73e58e36a2bd689a2f91f
Author: Victor Seva
Committer: Victor Seva
Date: 2023-10-06T00:44:41+02:00
github: define DOCKER_REPO at alpine workflow
@themsley-voiceflex - I am able to reproduce OpenSSL crashes now with EL9 +
OpenSSL 3. I thought this had been fixed with the pthread locking work but it
seems more complicated than that.
To isolate the problem I have created a build kamailio of 5.7.2/EL9 with a
`tls_wolfssl` subpackage for
@space88man pushed 2 commits.
eaa519304dbef74a7ed02ceb6196264393c4dd69 pkg: add example script to create
tarball with submodules instantiated
7e85fcb8c75600bd2727b6a1456dd730b8a233f1 pkg: RPM - add mock config for
EL8/EL9 based on alma+epel-(8|9)-x86_64
--
View it on GitHub:
@space88man pushed 1 commit.
53aeaa370b52d06d69d5d45fd54b1de1ab77c24d pkg: RPM packaging add
kamailio-tls_wolfssl subpackage
--
View it on GitHub:
https://github.com/kamailio/kamailio/pull/3592/files/96bc6fa3a2f5ffd24ec9b31cdbcc222b081bedc0..53aeaa370b52d06d69d5d45fd54b1de1ab77c24d
You are
Module: kamailio
Branch: 5.7
Commit: c94a185e36709241438cb07f38b7c26f72f40e05
URL:
https://github.com/kamailio/kamailio/commit/c94a185e36709241438cb07f38b7c26f72f40e05
Author: S-P Chan
Committer: S-P Chan
Date: 2023-10-06T07:22:28+08:00
Update wolfSSL to v5.6.3-stable
---
Modified:
@space88man pushed 2 commits.
367dbfd380014a29dbf31ba717b1b8e073c44134 pkg: add example script to create
tarball with submodules instantiated
c3d694466d886cc46538165b376fd1247205f07d pkg: RPM - add mock config for
EL8/EL9 based on alma+epel-(8|9)-x86_64
--
View it on GitHub:
@space88man pushed 1 commit.
4290ca1ee811afde5521d61e1bbe6ccd1a5df787 pkg: RPM packaging add
kamailio-tls_wolfssl subpackage
--
View it on GitHub:
https://github.com/kamailio/kamailio/pull/3592/files/53aeaa370b52d06d69d5d45fd54b1de1ab77c24d..4290ca1ee811afde5521d61e1bbe6ccd1a5df787
You are
The scope of loading all configs in cascade is to allow overwriting on specific
options with home config, not to have the entire config there. Practically the
/etc config is the one with all options and then add a user home config only to
change specific options (e.g., have a different mysql
OK, though somehow I agree that not having wss in the transport is confusing,
because it is in Via, but I wanted to be sure I haven't missed any new specs
introducing it.
--
Reply to this email directly or view it on GitHub:
Many linux software packages uses a different behaviour, if one configuration
file is found, its using this and no merge of the values is done. Bash profile
loading does it differently indeed, but I would argue that kamctl is more like
a tool. But if people depend on this current behaviour,
@miconda our bad, SIP.js was configured to use transport=wss. Closing this PR.
I'm sorry for the inconvenience.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/pull/3588#issuecomment-1749508317
You are receiving this because you are subscribed to
33 matches
Mail list logo
