Check your sip trace and makes sure clients connected over wireguard are not
offering SDP over IP address that is not routable over wireguard or not even
allowed over allowed-ips of wireguard client config.
Faced the same when clients connect over wireguard vpn long time ago and they
used to
El Sat, 20 Apr 2024 17:28:09 -
"christian.marinelli--- via sr-users" escribió:
> Hi all,
> i have a problem with my Kamailio SIP Server.
> I set up a Kamailio SIP server in a virtual machine on a private network and
> i connect to this with a WireGuard VPN. The problem is that i can connect
How about this new function that sets the algorithm?
-- Juha
iff --git a/src/modules/auth/auth_mod.c b/src/modules/auth/auth_mod.c
index 534ad9e20f..4e3a584d22 100644
--- a/src/modules/auth/auth_mod.c
+++ b/src/modules/auth/auth_mod.c
@@ -74,6 +74,10 @@ int w_consume_credentials(struct sip_msg
Hi all,
i have a problem with my Kamailio SIP Server.
I set up a Kamailio SIP server in a virtual machine on a private network and i
connect to this with a WireGuard VPN.
The problem is that i can connect to the SIP server throught different clients
and users and i can call the other users, the
Juha Heinanen via sr-users writes:
> Currently digest authentication hash algorithm (MD5 or SHA-256) is
> selected when auth module is loaded. How about allowing to select it
> also dynamically using the function flags?
Can't be done, since auth_db functions don't have flags parameter. Too
bad
Hi,
yes, in the next days i assumed that the first logrotate configuration was
wrong, and i need to use this command on the postrotate statement.
Thank you so much for you support
Christian
__
Kamailio - Users Mailing List - Non Commercial
Currently digest authentication hash algorithm (MD5 or SHA-256) is
selected when auth module is loaded. How about allowing to select it
also dynamically using the function flags?
-- Juha
__
Kamailio - Users Mailing List - Non Commercial
