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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=17834 
====================================================================== 
Reported By:                oej
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   17834
Category:                   Channels/chan_sip/IPv6
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.8.0-beta3 
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-08-16 10:28 CDT
====================================================================== 
Summary:                    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.
====================================================================== 

---------------------------------------------------------------------- 
 (0125971) sperreault (developer) - 2010-08-16 10:28
 https://issues.asterisk.org/view.php?id=17834#c125971 
---------------------------------------------------------------------- 
I am unable to reproduce this on Linux. I tried with the 4 possible
combinations of dnsmgr={on,off} and srvlookup={yes,no}. All I manage to get
is this, which seems pretty normal:

    -- Executing [1 at default:1] Dial("SIP/pjsua-00000002", "SIP/peer") in
new stack
[Aug 16 11:26:46] DEBUG[19053]: chan_sip.c:24775 sip_request_call: Asked
to create a SIP channel with formats: 0x4 (ulaw)
[Aug 16 11:26:46] DEBUG[19053]: chan_sip.c:7151 sip_alloc: Allocating new
SIP dialog for 05a21454272720671bc31bc05497adc1@[::1]:0 - INVITE (No RTP)
[Aug 16 11:26:46] DEBUG[19053]: chan_sip.c:24877 sip_request_call: Cant
create SIP call - target device not registered
[Aug 16 11:26:46] DEBUG[19053]: chan_sip.c:5542 sip_destroy: Destroying
SIP dialog 05a21454272720671bc31bc05497adc1@[::1]:0
[Aug 16 11:26:46] WARNING[19053]: app_dial.c:2031 dial_exec_full: Unable
to create channel of type 'SIP' (cause 20 - Unknown)
  == Everyone is busy/congested at this time (1:0/0/1)
[Aug 16 11:26:46] DEBUG[19053]: app_dial.c:2705 dial_exec_full: Exiting
with DIALSTATUS=CHANUNAVAIL.
    -- Auto fallthrough, channel 'SIP/pjsua-00000002' status is
'CHANUNAVAIL' 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-08-16 10:28 sperreault     Note Added: 0125971                          
======================================================================