Hi,
I set up a transparent kamailo proxy for IPv4 and IPv6.
The PBX which should be reached can handle both. Now I have the case that the phone comes in on IPv6, but kamailio sends it out via IPv4. If I ping the PBX on the kamailio server (debian) I get the IPv6 address, since it is preferred.
Why does kamailio send to the IPv4 address of the PBX? And how can I change this?
There are only A and AAAA records in the DNS
dns_try_ipv6=yes
is set.
Debian 12.5 Kamailio 5.6.5
Any hint is welcome.
Best regards
Bernd
dns_cache_flags = 4
https://www.kamailio.org/wikidocs/cookbooks/5.6.x/core/#dns_cache_flags
On Mon, Apr 22, 2024 at 3:18 PM Bernd Krueger-Knauber via sr-users < sr-users@lists.kamailio.org> wrote:
Hi,
I set up a transparent kamailo proxy for IPv4 and IPv6.
The PBX which should be reached can handle both. Now I have the case that the phone comes in on IPv6, but kamailio sends it out via IPv4. If I ping the PBX on the kamailio server (debian) I get the IPv6 address, since it is preferred.
Why does kamailio send to the IPv4 address of the PBX? And how can I change this?
There are only A and AAAA records in the DNS
dns_try_ipv6=yes
is set.
Debian 12.5 Kamailio 5.6.5
Any hint is welcome.
Best regards
Bernd
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Hi Sergey,
you nailed it!
Thank you for your fast response. If you know where to look it appears simple. But if you have no idea from where the problem comes from ...
Best regards,
Bernd
But ...
now I have the opposite.
I always use IPv6 for outgoing.
I would like to use the same address family for outgoing as it is incoming. (if possible)
Bernd
Hi Bernd
I also use dual-stack.
When the destination has an ipv6 and ipv4 address in the DNS, then kamailio should be able to use either of those protocols to reach it.
So:
CPE => ipv4 => Kamailio => ipv6 => CPE
should work, if the involved CPE play along!
Example: Cisco SPA112 don't know about IPv6 IP addresses in SIP headers and their parser uses ':' as hostname:port separator completely breaking IPv6 addresses and building broken header in it's replies.
Also mind, the RTP stream. And ipv4 only CPE will not be able to exchange RTP with an CPE advertising ipv6. So using ICE might help and maybe even use rtpengine to tank different protocols on each leg.
Mit freundlichen Grüssen
-Benoît Panizzon-
-
Benoit Panizzon -
Bernd Krueger-Knauber -
Sergey Safarov