@sergey-safarov - commented in the other issue you opened. This one is closed
with 5.4 being branched.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #2381.
--
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/2381#event-3572990558___
Kamailio (SER) - Development Mailing List
As more and more installation requires dual-stack installation (IPv4 and IPv6).
So I suggest enabling `auto_bind_ipv6=1`.
If this not acceptable, then add this option as comment near of `listen`
directive.
--
You are receiving this because you are subscribed to this thread.
Reply to this email
I pushed the updated config, here are the comments of the commit (referenced
above):
- use force_rport() at the beginning of processing requests, note added
in the top comments to inform that config performs symmetric signaling
- load textopsx module and added define option to apply changes
@gedia - yes, I agreed with your remark about force_port(), if that was not
clear. The debug=4 was inherited from openser times when it was a valid value,
after merging core from SER project, the values shifted back with 1. Can be
changed now to 3 and 2.
--
You are receiving this because you
@miconda Regarding force_rport(), the point I was making was exactly that it
does NOT engage in REQINIT, even if WITH_NAT is enabled. For example, replies
to OPTIONS sent to kami will always be directed to address in first Via header
even for NATted devices, even with NAT support enabled in the
Do not forget that we have also the advanced (oob) and basic configs in
`misc/examples/pkg/`, which were supposed to be installed in the shared docs
(they were relocated from `etc/`, not sure we got to packaging them).
I am fine to add the systemd and prometeus to the advanced config, but for
Given that Prometheus is becoming quite common as a timeseries backend, what do
you think about conditionally (#!ifdef) loading xhttp_prom module?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
How about `systemdops` module loading by default via
`/etc/kamailio/kamailio.cfg`?
Looks as most of the supported dists use `systemd`.
Except Alpine. For Alpine I will disable this module loading.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly
+1 for path support by default
Some other random preliminary thoughts:
* Is there any reason for NATDETECT to precede retransmission processing? Also,
AFAIK Contact header is not (normally?) present in CANCELs so it doesn't need
to precede CANCEL processing either. If my hypotheses are correct,
Starting this issue to collect suggestions about what should be adjusted in the
default config or options (global or module parameters) in preparation for
Kamailio 5.4.0. The goal is not to recreate a completely new config, the
current one being a good starting point for new deployments, but to
11 matches
Mail list logo
