Hi Ihor,
So, you say OpenSIPS picks the IPv6 address as destination (confirmed by
the err log), but you are not sure what interface is to be used (even if
you forced the ipv4 one, it may be discarded by the internal fwd logic).
Could you provide debug level logs for the relaying part ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 10.12.2025 17:58, Ihor Olkhovskyi wrote:
Hello!
I'm trying to build ipv4/ipv6 bridge with OpenSIPS 3.6.2.
I've declared the sockets like this:
# v4 addresses
socket=tls:OPENSIPS_IPV4_ADDR:TLS_PORT
socket=wss:OPENSIPS_IPV4_ADDR:WSS_PORT
# v6 addresses
socket=tls:[OPENSIPS_IPV6_ADDR]:TLS_PORT
socket=wss:[OPENSIPS_IPV6_ADDR]:WSS_PORT
dns_try_ipv6=yes
# Always listen on localhost v4
socket=tls:127.0.0.1:TLS_PORT
Means explicit to start on v4 and v6 addresses for lately to change
address family explicitly
OpenSIPS starts without any issues, but when I try to do socket
forcing with
$socket_out = "wss:OPENSIPS_IPV4_ADDR:WSS_PORT";
t_relay();
I'm getting
ERROR:proto_wss:ws_sync_connect: bind failed (22) Invalid argument
ERROR:proto_wss:ws_connect: connect failed
ERROR:proto_wss:proto_wss_send: connect failed
tm:msg_send: send() to EXTERNAL_IPV6(sic!) for proto wss/6 failed
tm:t_forward_nonack: sending request failed
So OpenSIPS is trying to send over IPv6. I guess that is cause network
address of RURI is v6 already, but DNS answers in dual-stack. If I
remove `dns_try_ipv6` it works, but how than I should work with v6?
What am I missing?
Thanks in advance!
--
Best regards,
Ihor (Igor)
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
