Hi! As soon as adding a AAAA DNS record for my sipserver, ipv4 clients don't work properly.
Setting: sipserver: kamailio 3.1.1 (x86_64/linux) client: sofia-sip-1.12.11 Clients are connected via tcp (outbound) to the sipserver. When an ipv6 client initiates a call to a ipv4 client the call is properly established!! If ipv4 calls ipv6, the final ACK is not sent. The nta-debug output says: ----------------- tport_connected(0x1a736f0): events CONNECTED ERR nta_agent: tport: No route to host tport_close(0x1a736f0): tcp/[-- ipv6-sipserver address --]:5060/sip ----------------- Note, that the INVITE is sent via ipv4 to the sipserver, and the corresponding "Status: 200 OK" is properly sent back via the ipv4 tcp-connection, which has been established during registration. It seems, that for sending the ACK the already existing ipv4 connection is not used, but the client tries to establish a new one via ipv6. Probably, this has something to do with the Contact header, which contains the transport address which has been used for registration. However, if ipv6 invites ipv4, everything is fine. Note, that the ipv4 only host has a link-local ipv6 address but has no ipv6 connectivity to the Internet. Please advise me where and how the transport for an ACK is determined and where in the code this can be fixed. best regards, Florian ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
