Working over IPv6

Hello, is it possible to configure FreePBX to work with IPv6?
If so, how can I do it?
Respectfully, AndAsh

Yes, but not exclusively.

You can configure the SIP channel driver to listen and initiate on IPv6 by defining an IPv6 transport.

The web server will also work over IPv6, and SSH too.

Unfortunately Sangoma facilities like mirror.freepbx.org are not on IPv6 so you cannot update FreePBX without IPv4.

This post about my setup of PJSIP has some information on how to configure the IPv6 transport.

This can be workarounded with NAT64 (for example: https://nat64.net/)

dig AAAA mirror.freepbx.org @2a00:1098:2b::1

; <<>> DiG 9.18.1-1ubuntu1.2-Ubuntu <<>> AAAA mirror.freepbx.org @2a00:1098:2b::1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24210
;; flags: qr rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
; COOKIE: 039d457a4ae185d30100000063c15baf33433f72e7279e75 (good)
;; QUESTION SECTION:
;mirror.freepbx.org.		IN	AAAA

;; ANSWER SECTION:
mirror.freepbx.org.	3502	IN	CNAME	mirror.freepbx.org.cdn.cloudflare.net.
mirror.freepbx.org.cdn.cloudflare.net. 202 IN AAAA 2a01:4f8:c2c:123f:64:5:ac43:2adf
mirror.freepbx.org.cdn.cloudflare.net. 202 IN AAAA 2a00:1098:2b::1:ac43:2adf
mirror.freepbx.org.cdn.cloudflare.net. 202 IN AAAA 2a00:1098:2b::1:6816:317f
mirror.freepbx.org.cdn.cloudflare.net. 202 IN AAAA 2a01:4f8:c2c:123f:64:5:6816:317f
mirror.freepbx.org.cdn.cloudflare.net. 202 IN AAAA 2a00:1098:2c::5:ac43:2adf
mirror.freepbx.org.cdn.cloudflare.net. 202 IN AAAA 2a01:4f8:c2c:123f:64:5:6816:307f
mirror.freepbx.org.cdn.cloudflare.net. 202 IN AAAA 2a00:1098:2b::1:6816:307f
mirror.freepbx.org.cdn.cloudflare.net. 202 IN AAAA 2a00:1098:2c::5:6816:307f
mirror.freepbx.org.cdn.cloudflare.net. 202 IN AAAA 2a00:1098:2c::5:6816:317f

;; Query time: 27 msec
;; SERVER: 2a00:1098:2b::1#53(2a00:1098:2b::1) (UDP)
;; WHEN: Fri Jan 13 14:25:03 CET 2023
;; MSG SIZE  rcvd: 378

I believe when the voip universe was being attacked they moved everything behind cloudflare which gives them ipv6. Anything not behind CF you may be sol without a workaround