[asterisk-bugs] [Asterisk 0017913]: Unable to use IPv4 addresses for a TCP host when using IPv6

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17913 
====================================================================== 
Reported By:                lmadsen
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17913
Category:                   Channels/chan_sip/IPv6
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.8.0-beta4 
JIRA:                       SWP-2122 
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-25 10:26 CDT
Last Modified:              2010-09-09 15:48 CDT
====================================================================== 
Summary:                    Unable to use IPv4 addresses for a TCP host when
using IPv6
Description: 
This is kind of a weird edge case, and I think I might know why it's not
working.

I'm trying to "front end" my 1.6.2.10 Asterisk instance with Asterisk
1.8.0-beta4 for testing purposes and to allow IPv6 connectivity.

This is done on the same box.

The error I'm getting is the following:

..........SIP channel loading...
[2010-08-25 11:19:44] ERROR[20813]: netsock2.c:245 ast_sockaddr_resolve:
getaddrinfo("127.0.0.1", "(null)", ...): Address family for hostname not
supported
[2010-08-25 11:19:44] WARNING[20813]: acl.c:564 resolve_first: Unable to
lookup '127.0.0.1'




If I switch host=[some_ipv6_address] on the peer, the error goes away.
When using an IPv4 address, I get that error.

I've disabled srvlookup=yes and dnsmgr without success.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0017711 [patch] sip/reqresp_parser.c:sip_uri_cm...
====================================================================== 

---------------------------------------------------------------------- 
 (0126790) russell (administrator) - 2010-09-09 15:48
 https://issues.asterisk.org/view.php?id=17913#c126790 
---------------------------------------------------------------------- 
Well, for the scenario he's trying to implement, chan_sip already supports
multiple sockets (1 per transport).  It has one bindaddr for UDP and
another for TCP.  He's trying to bind UDP to IPv6 and TCP to IPv4.  That
seems like something that should work to me.  What am I missing? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-09-09 15:48 russell        Note Added: 0126790                          
======================================================================