Small question about IPV6

[Knuppalex2023]

Hello,
I’ve always used Asterisk with IPv4 until now, but I’m planning to make the move to (or at least also start supporting) IPv6. I currently have the following transports configured in pjsip.conf:

; — transports —
[transport-udp]
type = transport
protocol = udp
bind = 0.0.0.0:5060
[transport-udp6]
type = transport
protocol = udp
bind = ::
[transport-wss]
type = transport
protocol = wss
bind = 0.0.0.0:55435

Asterisk seems to work well with these UDP transport configurations. Users register both via IPv6 and IPv4, all normal. But something seems misplaced or misconfigured in the WSS transport because nobody can use WSS via IPv6; all registrations are done via IPv4. Here’s what my http.conf file looks like:

[general]
enabled=yes
enablestatic=no
bindaddr=0.0.0.0
bindport=55434
tlsenable=yes
tlsbindaddr=0.0.0.0:55435
tlscertfile=/etc/letsencrypt/live/myserver.mydomain.com.br/fullchain.pem
tlsprivatekey=/etc/letsencrypt/live/myserver.mydomain.com.br/privkey.pem

Any ideas on what I might be doing wrong?
Thank you in advance!

[Chano]

It might be as simple as the fact you’re using 0.0.0.0 as the bind IP in the wss config.

By most conventions 0.0.0.0 means all available IPv4 addresses, while :: usually means all available IPv4 and IPv6 addresses.

Also I’ve had problems getting the audio flowing over IPv6, even though the registration has happened over IPv6, audio seems to prefer flowing over IPv4 if available. I’ve also had the opposite happen, IPv4 registration, IPv6 audio, but usually only if IPv6 is NOT available on the client side.

As most of our users does not have native IPv6, it’s not problems we’ve spent a lot of time trying to fix, we just added an IPv4 only DNS to use in those cases, I suppose you could do the same in the IPv6 only scenario.

[Knuppalex2023]

Worked by changing “0.0.0.0:55435” to “[::]:55435”. Thank you!