This issue is stale because it has been open 6 weeks with no activity. Remove
stale label or comment or this will be closed in 2 weeks.
--
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/3676#issuecomment-1912923358
You are receiving this because
Module: kamailio
Branch: 5.7
Commit: 2e6e879adc949b52cd2824fa233db901e5d045bc
URL:
https://github.com/kamailio/kamailio/commit/2e6e879adc949b52cd2824fa233db901e5d045bc
Author: S-P Chan
Committer: S-P Chan
Date: 2024-01-27T07:19:11+08:00
tls_wolfssl: fix ring buffer write
(cherry-pick from
Module: kamailio
Branch: master
Commit: 04ca08d0da622519578c479664a85563ec6db483
URL:
https://github.com/kamailio/kamailio/commit/04ca08d0da622519578c479664a85563ec6db483
Author: S-P Chan
Committer: S-P Chan
Date: 2024-01-27T07:09:19+08:00
tls_wolfssl: fix ring buffer write
---
Modified:
As an aside:
- A 180 (or any non-100 1xx message) doesn't inherently cause an early dialog
to come about; the distinguishing feature of a dialog-forming response is a
To-tag;
- A 200 response does not cause a dialog to be confirmed; it tentatively causes
it to be established, pending an
There are some real risks with taking dialog state transitions into your own
hands via this rather crude method.
The life cycle of a transaction, and therefore a dialog (insofar as a dialog
depends on the outcome of one or more transactions), can proceed, and
transition from stage to stage,
Hello,
I am thinking of making dlg_dmq_replicate_action() available to be called from
config, so one can do the following on the DMQ peer node:
def ksr_reply_route(self, msg):
if KSR.tm.t_check_trans() < 0:
if KSR.dialog.is_known_dlg():
if KSR.pv.get("$rs") == "180":
### Description
Kamailio fails to start after recent changes were made to improve support for
OpenSSL 3.X. The failure occurs for both OpenSSL 3.X and OpenSSL 1.1.X, and are
the same as failures I had been seeing on previous Kamailio versions when using
OpenSSL 3.X. These errors were not
Hi!
Sorry, I was sick last week...
> because of the flag for socket matching, record matching (ip, socket) is
> selected. Is this the desired behavior.
Yes, this is the desired behavior, because we can only have a target with an ip
and socket like this (it seems to be a valid configuration):
Module: kamailio
Branch: master
Commit: c286bacad82b84165753187a326952573fe5fc7a
URL:
https://github.com/kamailio/kamailio/commit/c286bacad82b84165753187a326952573fe5fc7a
Author: Kamailio Dev
Committer: Kamailio Dev
Date: 2024-01-26T11:16:15+01:00
modules: readme files regenerated - sdpops
Module: kamailio
Branch: master
Commit: faaefbb02563b8ba0827b23422a363a71259ad1e
URL:
https://github.com/kamailio/kamailio/commit/faaefbb02563b8ba0827b23422a363a71259ad1e
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2024-01-26T11:06:15+01:00
sdpops: added
Module: kamailio
Branch: master
Commit: 46e3727368f7e801b3731272d219cefdceebadde
URL:
https://github.com/kamailio/kamailio/commit/46e3727368f7e801b3731272d219cefdceebadde
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2024-01-26T11:06:15+01:00
sdpops: docs - listed
Module: kamailio
Branch: master
Commit: cab001e9677670585facf5cf2b7fd0c9889ac069
URL:
https://github.com/kamailio/kamailio/commit/cab001e9677670585facf5cf2b7fd0c9889ac069
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2024-01-26T11:06:15+01:00
sdpops: format module
Module: kamailio
Branch: master
Commit: fe9b8f04cacd2ca92bf3fac1dc2fac323b8cf62d
URL:
https://github.com/kamailio/kamailio/commit/fe9b8f04cacd2ca92bf3fac1dc2fac323b8cf62d
Author: Daniel-Constantin Mierla
Committer: Daniel-Constantin Mierla
Date: 2024-01-26T11:06:15+01:00
sl: format module
Module: kamailio
Branch: master
Commit: 247e6164cbacdcc5d260e98c1085c84ad93957ee
URL:
https://github.com/kamailio/kamailio/commit/247e6164cbacdcc5d260e98c1085c84ad93957ee
Author: Victor Seva
Committer: Victor Seva
Date: 2024-01-26T09:05:50+01:00
pkg/kamailio/deb: restore tls_wolfssl for
14 matches
Mail list logo
