[asterisk-bugs] [Asterisk 0017834]: [patch] IPv6: System configured for only IPv4 tries sending to IPv6

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Sep 2 10:17:25 CDT 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17834 
====================================================================== 
Reported By:                oej
Assigned To:                russell
====================================================================== 
Project:                    Asterisk
Issue ID:                   17834
Category:                   Channels/chan_sip/IPv6
Reproducibility:            always
Severity:                   minor
Priority:                   high
Status:                     acknowledged
Target Version:             1.8.0
Asterisk Version:           SVN 
JIRA:                       SWP-2033 
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-08-11 05:13 CDT
Last Modified:              2010-09-02 10:17 CDT
====================================================================== 
Summary:                    [patch] IPv6: System configured for only IPv4 tries
sending to IPv6
Description: 
Running on a dual stack system, with a bind address set to 0.0.0.0
(indicating only IPv4 support), placing a call to a domain that only
resolves into an IPv6 server, Asterisk tries to send anyway with poor
results. This indicates a few things to me:
- Something is wrong in the code, since it doesn't act as documented in
sip.conf. (bindaddr 0.0.0.0 should only get IPv4 support)
- Many log messages are wrong
- Again, like in another issue, Asterisk tries sending SIP messages to a
NULL address. This is a bug in itself.

I have modified the host names in the log, can provide programmer with
proper addresses for testing.
====================================================================== 

---------------------------------------------------------------------- 
 (0126563) russell (administrator) - 2010-09-02 10:17
 https://issues.asterisk.org/view.php?id=17834#c126563 
---------------------------------------------------------------------- 
I have an Asterisk 1.8.0-beta4 instance running on Linux with a public IPv4
and IPv6 address.  I tried reproducing this and was unable to.  When
calling another PBX that has a AAAA record, it would only attempt to send
to the IPv6 address if I had configured Asterisk with bindport=::.  It
would _not_ attempt to send to that address with bindport=0.0.0.0.

So, this is looking like it may be a mac specific issue.  If that is the
case, I don't consider it a 1.8.0 release blocker, so I'm going to update
Mantis to reflect that. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-09-02 10:17 russell        Note Added: 0126563                          
======================================================================




More information about the asterisk-bugs mailing list