Your message dated Mon, 26 Apr 2010 21:33:14 +0200
with message-id <[email protected]>
has caused the report #578950,
regarding liblinphone3: Sends IPv6 addresses to IPv4 hosts when DNS name has A
to be marked as having been forwarded to the upstream software
author(s) [email protected]
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
bug+patch: Identifies with IP6 to IP4 hosts with dual AAAA/A DNS resource record
Lionel Elie Mamane
Mon, 26 Apr 2010 21:33:14 +0200
This is bug #578950 in the Debian bug tracker:
Please keep [email protected], [email protected]
and [email protected] as CC in the discussion (M-F-T is set).
- the SIP server has both A and AAAA records in DNS
- linphone is configured to use IPv4, not IPv6
linphone speaks over IPv4 to the server, but puts an IPv6 address in
the SIP messages. This, at least in the case where Asterisk is the
server (and probably for other servers that don't implement IPv6)
makes calls not work. (registration works)
The attached patch (against v3.2.1) fixes the issue.
Abstract from the debug log:
linphonec> call 500
ortp-message-Local interface to reach sip.mamane.lu is 2001:960:2:97::2.
First sign of trouble: linphone identifies its own IP as an IPv6...
ortp-message-getaddrinfo returned the following addresses:
ortp-message-188.8.131.52 port 5060
ortp-message-Message sent: (to dest=184.108.40.206:5060)
but OK, it still speaks to the server over IPv4
o=lionel 123456 654321 IN IP6 2001:960:2:97::2
c=IN IP6 2001:960:2:97::2
the IP6 address there makes Asterisk balk. The Asterisk log says:
WARNING chan_sip.c: Invalid host in c= line, 'IN IP6 2001:960:2:97::2'
and it returns this message to Linphone:
ortp-message-Received message: SIP/2.0 488 Not acceptable here
Description: Text document
--- End Message ---