Hello, it is not supposed to do any DNS on IPv6 addresses, maybe only if you disabled IPv6 support.
Do you have the debug messages for such case? Also, what global parameters did you set related to iPv6? Cheers, Daniel September 17, 2019 3:30 PM, "Anthony Alba" <[email protected]> wrote: > Hi Daniel, > > In this test environment kamailio (SIP control plane) is IPv4 only; > rtpengine is configured on IPv4/IPv6 interfaces. > When the INVITE+SDP came in, it seems to to try to resolve the address > [2001:...] as a DNS name. > > To recap, this was trying an IPv4-control plane with dual-stack media. > > On Tue, Sep 17, 2019 at 8:49 PM Daniel-Constantin Mierla > <[email protected]> wrote: > >> Hello, >> >> I am not sure what do you mean with: >> >> """ >> I have noticed that if Kamailio is IPv4-only and it "sees" >> IPv6-addresses(Contact, Via headers??) it will try to resolve the >> IPv6-address as a DNS name! >> """ >> >> If it just that on the specific deployment Kamailio has to bind on IPv4 and >> run as an IPv4 >> application, or actually you mean that Kamailio does not support IPv6?!? >> >> For the later, Kamailio supports IPv6 for quite long time and should work >> fine on IPv6 only or >> mixed networks. >> >> Cheers, >> Daniel >> >> On Tue, Sep 17, 2019 at 3:22 AM Anthony Alba <[email protected]> wrote: >>> Hi folks, >>> >>> I'm wondering what you do to pass Apple app store tests (IPv6-only >>> NAT64/DNS64 scenario) with the iOS app likely to put IPv6 addresses in >>> the SDP, when Kamailio and your B2BUA(Asterisk, FreeSWITCH,...) are >>> IPv4-only endpoints. >>> >>> By "pass" I mean media flowing + SIP working - not sure the app store >>> gatekeepers would actually test media, but it would be nice to have a >>> robust solution. >>> >>> Strictly speaking, this is not a Kamailio's problem but a media >>> SDP/<your-rtp-proxy-of-choice> problem. But since everything is so >>> closely intertwined I'm wondering where you choose to the location the >>> "solution". >>> >>> I have noticed that if Kamailio is IPv4-only and it "sees" >>> IPv6-addresses(Contact, Via headers??) it will try to resolve the >>> IPv6-address as a DNS name! >>> >>> The Wikipedia article on NAT64 mentions 464XLAT(RFC 6877) and Port >>> Control Protocol (RFC 7225), but those seem to be deep rabbit-holes... >>> >>> Cheers >>> Anthony Alba >>> >>> _______________________________________________ >>> Kamailio (SER) - Users Mailing List >>> [email protected] >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> >> -- >> Daniel-Constantin Mierla - https://www.asipto.com >> https://twitter.com/miconda - https://www.linkedin.com/in/miconda >> Kamailio Advanced Training - https://www.asipto.com/u/kat >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> [email protected] >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > _______________________________________________ > Kamailio (SER) - Users Mailing List > [email protected] > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierla www.kamailio.org -- www.asipto.com _______________________________________________ Kamailio (SER) - Users Mailing List [email protected] https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
